Stuck in fastboot, can't boot recovery. - G 2014 Q&A, Help & Troubleshooting

Hello everybody, I need help-
I erased /system, /cache, and dalvik cache, and then powered the device off by mistake. Now I can only boot to fastboot, and using
fastboot boot recovery_image.img
doesn't work. Nor it does selecting 'recovery from the fastboot menu. Using either of them will end in the device being stuck at bootloader logo.
I just need to get into TWRP, or power off the device. How can I do so?
Thanks in advance.

totalnoob34 said:
Hello everybody, I need help-
I erased /system, /cache, and dalvik cache, and then powered the device off by mistake. Now I can only boot to fastboot, and using
fastboot boot recovery_image.img
doesn't work. Nor it does selecting 'recovery from the fastboot menu. Using either of them will end in the device being stuck at bootloader logo.
I just need to get into TWRP, or power off the device. How can I do so?
Thanks in advance.
Click to expand...
Click to collapse
I suppose you have XT1068.
It's better to flash the stock firmware.
You can try with this: http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612

I think it should be
Fastboot flash recovery recovery_image.img
Boot in recovery and flash a ROM.
If fail try flashing stock again

dani.galla said:
I suppose you have XT1068.
It's better to flash the stock firmware.
You can try with this: http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
Click to expand...
Click to collapse
fburgos said:
I think it should be
Fastboot flash recovery recovery_image.img
Boot in recovery and flash a ROM.
If fail try flashing stock again
Click to expand...
Click to collapse
I tried flashing the stock image following this tutorial,
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
but the version of the system image is the same so it should be the same. The phone boots fine, but SystemUI crashes after setting the thing up, and I can't boot into recovery, there is no recovery, only dead android. The phone works, but something in the software is not working.
If I reboot the device, it hangs at Upgrading Android...
Also, if I try to lock the bootloader(from status 3 to status 2), after flashing stock image, fastboot reboots and says 'failed to validate system image'. Do you think following the xda tutorial would change anything? Do you think there would be anything I can do about it? I could return it to Amazon, but I don't know if the warranty is still valid. It may be void, but the phone really has something wrong.
EDIT: Yes, XT1068 model, dual sim 8gb.
EDIT: The phone WORKS. I mean, I can download apps, use everything as normal. Just no homescreen. Installing Nova Launcher makes the thing flawless, until I reboot. Then, it gets stuck at Updating Android... Really don't know what to think.

totalnoob34 said:
I tried flashing the stock image following this tutorial,
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
but the version of the system image is the same so it should be the same. The phone boots fine, but SystemUI crashes after setting the thing up, and I can't boot into recovery, there is no recovery, only dead android. The phone works, but something in the software is not working.
If I reboot the device, it hangs at Upgrading Android...
Also, if I try to lock the bootloader(from status 3 to status 2), after flashing stock image, fastboot reboots and says 'failed to validate system image'. Do you think following the xda tutorial would change anything? Do you think there would be anything I can do about it? I could return it to Amazon, but I don't know if the warranty is still valid. It may be void, but the phone really has something wrong.
EDIT: Yes, XT1068 model, dual sim 8gb.
EDIT: The phone WORKS. I mean, I can download apps, use everything as normal. Just no homescreen. Installing Nova Launcher makes the thing flawless, until I reboot. Then, it gets stuck at Updating Android... Really don't know what to think.
Click to expand...
Click to collapse
I suggest you to use the guide that I posted you, because is better.
For locking bootloader, before flashing you must type something like: oem begin lock and after flashing oem lock.
Maybe you have problems because the file you download has some problems

dani.galla said:
I suggest you to use the guide that I posted you, because is better.
For locking bootloader, before flashing you must type something like: oem begin lock and after flashing oem lock.
Maybe you have problems because the file you download has some problems
Click to expand...
Click to collapse
Ok, I'll download the file you posted and let you know. If you can, follow this thread so that we can sort this out.
Thanks so much for helping.

totalnoob34 said:
I tried flashing the stock image following this tutorial,
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
but the version of the system image is the same so it should be the same. The phone boots fine, but SystemUI crashes after setting the thing up, and I can't boot into recovery, there is no recovery, only dead android. The phone works, but something in the software is not working.
Click to expand...
Click to collapse
Dead android is the stock recovery you have to press a key combination to get the menu.
Flask twrp and wipe cache

fburgos said:
Dead android is the stock recovery you have to press a key combination to get the menu.
Flask twrp and wipe cache
Click to expand...
Click to collapse
Can I format a partition from fastboot? I believe that is the problem. In the toolkit, while running, it says that /system and /cache are in 'raw data format', so I think they should be formatted, not erased.
EDIT: Yea, the problem's definitely some unpartitioned space. Posting the toolkit's output:
erasing 'userdata'...
OKAY [ 0.443s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting
File system type raw not supported.
OKAY [ 0.019s]
erasing 'cache'...
OKAY [ 0.129s]
formatting 'cache' partition...
Erase successful, but not automatically formatting
File system type raw not supported.
OKAY [ 0.017s]
finished. total time: 0.624s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.059s]
writing 'partition'...
OKAY [ 0.327s]
finished. total time: 0.397s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.140s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.076s]
finished. total time: 1.224s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.103s]
writing 'logo'...
OKAY [ 0.111s]
finished. total time: 0.224s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.421s]
writing 'boot'...
OKAY [ 0.805s]
finished. total time: 1.234s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.812s]
finished. total time: 1.250s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 8.588s]
writing 'system'...
OKAY [ 13.357s]
finished. total time: 21.954s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 8.472s]
writing 'system'...
OKAY [ 13.080s]
finished. total time: 21.557s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 8.635s]
writing 'system'...
OKAY [ 12.768s]
finished. total time: 21.412s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 8.473s]
writing 'system'...
OKAY [ 12.729s]
finished. total time: 21.210s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 1.111s]
writing 'system'...
OKAY [ 1.531s]
finished. total time: 2.644s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 1.667s]
writing 'modem'...
OKAY [ 1.761s]
finished. total time: 3.434s
erasing 'modemst1'...
OKAY [ 0.024s]
finished. total time: 0.026s
erasing 'modemst2'...
OKAY [ 0.037s]
finished. total time: 0.042s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.082s]
writing 'fsg'...
OKAY [ 0.099s]
finished. total time: 0.191s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.125s]
finished. total time: 0.129s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.481s]
finished. total time: 0.486s
cat /proc/mounts outout:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=447036k,nr_inodes=111759,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=447036k,nr_inodes=111759,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=447036k,nr_inodes=111759,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=447036k,nr_inodes=111759,mode=755,gid=1000 0 0
none /dev/memcg cgroup rw,relatime,memory 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,nobarrier,active_logs=6 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,context=ubject_r:firmware_file:s0,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/pds /pds ext4 rw,defcontext=ubject_rds_file:s0,seclabel,nosuid,nodev,noatime,nodiratime,errors=remount-ro,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/fsg /fsg ext4 ro,context=ubject_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/data/media /mnt/shell/emulated esdfs rw,relatime,upper=0:1028:660:771,derive=legacy,nosplit 0 0
/data/media /storage/emulated/legacy esdfs rw,relatime,upper=0:1028:660:771,derive=legacy,nosplit 0 0
df output:
Filesystem Size Used Free Blksize
/dev 436.6M 60.0K 436.5M 4096
/sys/fs/cgroup 436.6M 0.0K 436.6M 4096
/sys/fs/cgroup/memory: Permission denied
/mnt/asec 436.6M 0.0K 436.6M 4096
/mnt/obb 436.6M 0.0K 436.6M 4096
/system 1.1G 1.0G 27.5M 4096
/data 5.5G 782.6M 4.7G 4096
/cache 525.7M 8.9M 516.8M 4096
/persist 4.9M 4.1M 796.0K 4096
/firmware 62.4M 46.5M 15.9M 4096
/pds 1.9M 1.0M 923.0K 1024
/fsg 638.0K 637.0K 1.0K 1024
/mnt/shell/emulated 5.5G 782.6M 4.7G 4096
/storage/emulated/legacy 5.5G 782.6M 4.7G 4096

totalnoob34 said:
Can I format a partition from fastboot? I believe that is the problem. In the toolkit, while running, it says that /system and /cache are in 'raw data format', so I think they should be formatted, not erased.
EDIT: Yea, the problem's definitely some unpartitioned space. Posting the toolkit's output:
erasing 'userdata'...
OKAY [ 0.443s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting
File system type raw not supported.
OKAY [ 0.019s]
erasing 'cache'...
OKAY [ 0.129s]
formatting 'cache' partition...
Erase successful, but not automatically formatting
File system type raw not supported.
OKAY [ 0.017s]
finished. total time: 0.624s
FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.059s]
writing 'partition'...
OKAY [ 0.327s]
finished. total time: 0.397s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.140s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.076s]
finished. total time: 1.224s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.103s]
writing 'logo'...
OKAY [ 0.111s]
finished. total time: 0.224s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.421s]
writing 'boot'...
OKAY [ 0.805s]
finished. total time: 1.234s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.812s]
finished. total time: 1.250s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (258868 KB)...
OKAY [ 8.588s]
writing 'system'...
OKAY [ 13.357s]
finished. total time: 21.954s
target max-sparse-size: 256MB
sending 'system' (254994 KB)...
OKAY [ 8.472s]
writing 'system'...
OKAY [ 13.080s]
finished. total time: 21.557s
target max-sparse-size: 256MB
sending 'system' (260623 KB)...
OKAY [ 8.635s]
writing 'system'...
OKAY [ 12.768s]
finished. total time: 21.412s
target max-sparse-size: 256MB
sending 'system' (255649 KB)...
OKAY [ 8.473s]
writing 'system'...
OKAY [ 12.729s]
finished. total time: 21.210s
target max-sparse-size: 256MB
sending 'system' (32272 KB)...
OKAY [ 1.111s]
writing 'system'...
OKAY [ 1.531s]
finished. total time: 2.644s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (49364 KB)...
OKAY [ 1.667s]
writing 'modem'...
OKAY [ 1.761s]
finished. total time: 3.434s
erasing 'modemst1'...
OKAY [ 0.024s]
finished. total time: 0.026s
erasing 'modemst2'...
OKAY [ 0.037s]
finished. total time: 0.042s
target max-sparse-size: 256MB
sending 'fsg' (651 KB)...
OKAY [ 0.082s]
writing 'fsg'...
OKAY [ 0.099s]
finished. total time: 0.191s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.125s]
finished. total time: 0.129s
ERASING USERDATA.......
erasing 'userdata'...
OKAY [ 0.481s]
finished. total time: 0.486s
cat /proc/mounts outout:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=447036k,nr_inodes=111759,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=447036k,nr_inodes=111759,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=447036k,nr_inodes=111759,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=447036k,nr_inodes=111759,mode=755,gid=1000 0 0
none /dev/memcg cgroup rw,relatime,memory 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,nobarrier,active_logs=6 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,context=ubject_r:firmware_file:s0,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/pds /pds ext4 rw,defcontext=ubject_rds_file:s0,seclabel,nosuid,nodev,noatime,nodiratime,errors=remount-ro,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/fsg /fsg ext4 ro,context=ubject_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/data/media /mnt/shell/emulated esdfs rw,relatime,upper=0:1028:660:771,derive=legacy,nosplit 0 0
/data/media /storage/emulated/legacy esdfs rw,relatime,upper=0:1028:660:771,derive=legacy,nosplit 0 0
df output:
Filesystem Size Used Free Blksize
/dev 436.6M 60.0K 436.5M 4096
/sys/fs/cgroup 436.6M 0.0K 436.6M 4096
/sys/fs/cgroup/memory: Permission denied
/mnt/asec 436.6M 0.0K 436.6M 4096
/mnt/obb 436.6M 0.0K 436.6M 4096
/system 1.1G 1.0G 27.5M 4096
/data 5.5G 782.6M 4.7G 4096
/cache 525.7M 8.9M 516.8M 4096
/persist 4.9M 4.1M 796.0K 4096
/firmware 62.4M 46.5M 15.9M 4096
/pds 1.9M 1.0M 923.0K 1024
/fsg 638.0K 637.0K 1.0K 1024
/mnt/shell/emulated 5.5G 782.6M 4.7G 4096
/storage/emulated/legacy 5.5G 782.6M 4.7G 4096
Click to expand...
Click to collapse
what have flashed before this? Because it's very strange that you partitions have changed
Edit: Seems that only your userdata partition anche cache have changed

dani.galla said:
what have flashed before this? Because it's very strange that you partitions have changed
Edit: Seems that only your userdata partition anche cache have changed
Click to expand...
Click to collapse
You mean that the other partitions, apart from userdata and cache, were not flashed?
The phone works flawlessly, I'm using it currently. There is no recovery, and it does not read external sdcards either. WHat do you think?

totalnoob34 said:
You mean that the other partitions, apart from userdata and cache, were not flashed?
The phone works flawlessly, I'm using it currently. There is no recovery, and it does not read external sdcards either. WHat do you think?
Click to expand...
Click to collapse
Before this problems have you flashed a custom rom?
The partitions should be:
Main storage: storage/emulated/0
Sdcard: storage/sdcard1
Try with a file manager if your's are in thus way

dani.galla said:
Before this problems have you flashed a custom rom?
The partitions should be:
Main storage: storage/emulated/0
Sdcard: storage/sdcard1
Try with a file manager if your's are in thus way
Click to expand...
Click to collapse
The whole thing started when I was running BlissPop, then the phone stopped recognising sdcard1 (the external one), even in TWRP. So I formatted via TWRP /system, /cache and dalvik, then I stupidly powered the phone off.
EDIT: The phone can't read the MicroSD, it says 'empty or unsupported file system'. It is read fine on my PC.

totalnoob34 said:
The whole thing started when I was running BlissPop, then the phone stopped recognising sdcard1 (the external one), even in TWRP. So I formatted via TWRP /system, /cache and dalvik, then I stupidly powered the phone off.
EDIT: The phone can't read the MicroSD, it says 'empty or unsupported file system'. It is read fine on my PC.
Click to expand...
Click to collapse
What file system is the SDCard formatted for? i.e. ext4, fat32 etc?

pastorbob62 said:
What file system is the SDCard formatted for? i.e. ext4, fat32 etc?
Click to expand...
Click to collapse
The SD is formatted in FAT32 (I believe). Anyway, it was used for more than two months in that phone without problems.

totalnoob34 said:
The SD is formatted in FAT32 (I believe). Anyway, it was used for more than two months in that phone without problems.
Click to expand...
Click to collapse
Never hurts to double check.
FWIW I had an SDcard that I used for over a year. I began to have unexplainable issues after a ROM update and it turned out to be the card. It worked great in my PC but would not read consistently in my phone. Reformated and it works like a dream now.

pastorbob62 said:
Never hurts to double check.
FWIW I had an SDcard that I used for over a year. I began to have unexplainable issues after a ROM update and it turned out to be the card. It worked great in my PC but would not read consistently in my phone. Reformated and it works like a dream now.
Click to expand...
Click to collapse
Ok, I'll do that, thanks a lot. Meanwhile, I tried all sorts of combinations of flashing and booting .img, but I can't get this thing to boot in recovery. Nor the stock one, nor TWRP. Doesn't matter if the bootloader is unlocked or locked, it doesn't boot in recovery.
Only the dead android with the red triangle pops up, and I've tried all combinations of keys, I thought it was PWR+VOL+ but the recovery menu doesn't show up.
The phone is usable, in fact I've used it for over a day with absolutely no problems whatsoever. It boots fine, and correctly installs applications, and so on.
I can't root it now, since I only have access to fastboot. Any piece of advice you can give me?
EDIT: I'm formatting the SDcard now, it was formatted in FAT32.

totalnoob34 said:
Ok, I'll do that, thanks a lot. Meanwhile, I tried all sorts of combinations of flashing and booting .img, but I can't get this thing to boot in recovery. Nor the stock one, nor TWRP. Doesn't matter if the bootloader is unlocked or locked, it doesn't boot in recovery.
Only the dead android with the red triangle pops up, and I've tried all combinations of keys, I thought it was PWR+VOL+ but the recovery menu doesn't show up.
The phone is usable, in fact I've used it for over a day with absolutely no problems whatsoever. It boots fine, and correctly installs applications, and so on.
I can't root it now, since I only have access to fastboot. Any piece of advice you can give me?
EDIT: I'm formatting the SDcard now, it was formatted in FAT32.
Click to expand...
Click to collapse
The recovery stock first shows the green android, so it's ok. You must use the right combination of buttons for the right time!
Try to keep pressed vol + and power for 7 secs, and then release them both.
The boot.img is the kernel, so why are you flashing it?
If you want to flash the recovery:
- download twrp.
- enter in fastboot mode
- flash recovery namerecovery.img
Before doing this things check the bootloader status (must be unlocked = status 3)

dani.galla said:
The recovery stock first shows the green android, so it's ok. You must use the right combination of buttons for the right time!
Try to keep pressed vol + and power for 7 secs, and then release them both.
The boot.img is the kernel, so why are you flashing it?
If you want to flash the recovery:
- download twrp.
- enter in fastboot mode
- flash recovery namerecovery.img
Before doing this things check the bootloader status (must be unlocked = status 3)
Click to expand...
Click to collapse
Yes, I know that, I was just saying that I've tried both flashing the recovery
fastboot flash recovery recovery.img
and booting it,
fastboot boot recovery.img
But in both cases I couldn't get TWRP to boot.

totalnoob34 said:
Yes, I know that, I was just saying that I've tried both flashing the recovery
fastboot flash recovery recovery.img
and booting it,
fastboot boot recovery.img
But in both cases I couldn't get TWRP to boot.
Click to expand...
Click to collapse
You can't enter with fastboot in recovery,
you can only reboot your phone.
use the keys after flashing recovery
Edit: you can enter with adb
adb reboot recovery

dani.galla said:
You can't enter with fastboot in recovery,
you can only reboot your phone.
use the keys after flashing recovery
Edit: you can enter with adb
adb reboot recovery
Click to expand...
Click to collapse
Yes, doing that brings me to the dead android screen, and pressing vol+ and power does nothing. Just reboots infinitely the phone (like, boot logo, vibration, screen off, boot logo, and so on.) The strange this is that I've never been able to boot in TWRP that way. I could only get there by 'adb reboot recovery'. Selecting recovery in fastboot or using the key combination never worked.
Does your device behave this way too?

Related

Nexus 2012 Omni ROM WiFi grouper.

I have a problem with my nexus 2012 WiFi version
I put twrp recovery 2.7.0.0 and omini ROM 4.4.2. Since then I have been unable to wipe anything on the device. I wipe or format in twrp when reboot every thing is same. Even with fastboot I format internal SD or wipe everything. It says it is OK but when u boot nothing is wiped. I can install apps but when I reboot they are erased and only apps which were there earlier stay. Please help. Another guy in the forum has same problem. I updated from slim ROM to omni and the problem started Now I can't even delete anything in twrp recovery or update twrp recovery in fastboot. It says its done but when I reboot to twrp its not updated.
Also in fastboot I can't lock boot loader by fastboot OEM lock . The command goes through in fastboot but when I reboot its still unlocked. Please any hep is appreciated from any one on XDA.
Default Can't wipe or factory reset Nexus 7 (2102) using multiple methods
A month or so ago my Nexus 7 (2012) started rebooting itself after a minute or so of turning on - I think this may have been during OTA upgrade from JWR66Y to new release. I tried to fix this by clearing app data and booting into CWM recovery and deleting cache and dalvik cache but the problem persisted. So I decided to reset the Nexus 7 back to factory image and have tried every means of doing so but every time I keep getting back to my original data and the app crashes and reboot continues. I have never had any issues connecting to the device on USB and ADB so this is not a driver issue. Things I have tried:
* Hard reset on phone from recovery (plus endless deleting of cache and dalvik)
* Hard reset using Wugfresh toolkit (plus near every other tool on there)
* Hard refresh from recovery mode
* Hard refresh using ADB and deleting user data etc.
* Flash recovery from ADB (also using Wugfresh as per above)
* ADB sideload from recovery of factory images, bootloaders and other ROM's
* Lock/unlock/root/unroot - using ADB commands as well as Wugfresh and other toolkits
* Delete data, system, cache
It seems like the Nexus 7 going into read only mode? Erasing /data and everything else in recovery has no effect and also when trying to overwrite the bootloader I get "writing 'bootloader'... FAILED (remote: (InvalidState))" using Wugfresh toolkit as per below. The device is still running JWR66Y.
I'm totally stuck now as to how I get my Nexus 7 back again! I have seen other people having issues with the JWR66Y bootloader (http://forum.xda-developers.com/show....php?t=1907796) but have tried all the workarounds and can't seem to find a way to overwrite the bootloader...
*** Trying with ADB manually ***
C:\android-sdk\platform-tools>adb devices
List of devices attached
4df17c816ec76f25 device
C:\android-sdk\platform-tools>adb devices
List of devices attached
015d165c520bf80f device
C:\android-sdk\platform-tools>adb reboot-bootloader
C:\android-sdk\platform-tools>fastboot devices
015d165c520bf80f fastboot
C:\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\android-sdk\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.344s]
writing 'bootloader'...
OKAY [ 0.594s]
finished. total time: 0.938s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\android-sdk\platform-tools>fastboot -w update image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 95.203s]
writing 'system'...
OKAY [ 27.500s]
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 38.453s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 2.203s]
rebooting...
finished. total time: 165.625s
*** Now using Wugfresh tool ***
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.031s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031s
sending 'bootloader' (3911 KB)...
OKAY [ 0.609s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.828s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d165c520bf80f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.781s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (5532 KB)...
OKAY [ 0.844s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.016s]
sending 'system' (625382 KB)...
OKAY [ 96.078s]
writing 'system'...
OKAY [ 27.484s]
erasing 'userdata'...
OKAY [ 0.031s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [148.516s]
erasing 'cache'...
OKAY [ 0.016s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 3.266s]
rebooting...
finished. total time: 1197.719s
Thanks[/QUOTE][/QUOTE]

[Q] EFI issues?

Phone was on charger overnight, went to use it and just boot loops. Was fine the day before. so I tried to flash a rom to no prevail, so I loaded NRT to flash 5.1 only to keep getting Failed bootloader and radio install. I can get to bootloader and recovery, but data, cache and storage cannot be mounted. the following are my NRT results:
Flash Stock + Unroot...
------------------------------------------------------------------
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.125s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 0.398s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.750s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
(bootloader) Failed to flash partition versions
(bootloader) Failed to flash versions
FAILED (remote failure)
finished. total time: 3.320s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.266s]
writing 'boot'...
OKAY [ 0.047s]
finished. total time: 0.313s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.016s]
sending 'cache' (6248 KB)...
OKAY [ 0.203s]
writing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.281s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.286s]
writing 'recovery'...
OKAY [ 0.063s]
finished. total time: 0.348s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending sparse 'system' (522112 KB)...
OKAY [ 18.386s]
writing 'system'...
OKAY [ 3.252s]
sending sparse 'system' (510197 KB)...
OKAY [ 18.144s]
writing 'system'...
OKAY [ 3.211s]
sending sparse 'system' (515601 KB)...
OKAY [ 18.700s]
writing 'system'...
OKAY [ 3.356s]
sending sparse 'system' (188485 KB)...
OKAY [ 6.640s]
writing 'system'...
OKAY [ 1.172s]
finished. total time: 72.878s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.016s]
sending 'userdata' (138868 KB)...
OKAY [ 4.466s]
writing 'userdata'...
OKAY [ 0.896s]
finished. total time: 5.378s
rebooting...
finished. total time: -0.000s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
Press any key to exit...
Any Help?
Use fastboot to flash the 5.1 images. Flash each individually and ensure you wipe data
still no go
Command Prompt for manual input...
------------------------------------------------------------------
Try typing "adb help" or "fastboot help" for a full cmd list and syntax info.
Enjoy...
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot dev
ices
ZX1G322NKQ fastboot
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot era
se boot
erasing 'boot'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.000s]
finished. total time: 0.016s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot era
se cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot era
se recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot era
se system
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot era
se userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.008s]
finished. total time: 0.008s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot fla
sh bootloader bootloader-shamu-moto-apq8084-71.08.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 0.403s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot reb
oot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
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
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot reb
oot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot fla
sh radio radio-shamu-d4.0-9625-02.95.img
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.752s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
(bootloader) Failed to flash partition versions
(bootloader) Failed to flash versions
FAILED (remote failure)
finished. total time: 3.315s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot -w
update image-shamu-lmy47d.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot reb
oot
rebooting...
finished. total time: 0.000s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>
Going to do each seprately still, but that EFI is still there.
Definitely looks like a warranty return to me.
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot -w
flash bootloader bootloader-shamu-moto-apq8084-71.08.img
target reported max download size of 536870912 bytes
Creating filesystem with parameters:
Size: 59743535104
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14585824
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3646496 inodes and 274946/14585824 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'bootloader' (3807 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 0.425s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot reb
oot
rebooting...
finished. total time: 0.003s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot -w
flash radio radio-shamu-d4.0-9625-02.95.img
target reported max download size of 536870912 bytes
Creating filesystem with parameters:
Size: 59743535104
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14585824
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3646496 inodes and 274946/14585824 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'radio' (85422 KB)...
OKAY [ 2.762s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
(bootloader) Failed to flash partition versions
(bootloader) Failed to flash versions
FAILED (remote failure)
finished. total time: 3.316s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot reb
oot
rebooting...
finished. total time: 0.000s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot -w
flash boot boot.img
target reported max download size of 536870912 bytes
Creating filesystem with parameters:
Size: 59743535104
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14585824
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3646496 inodes and 274946/14585824 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'boot' (7681 KB)...
OKAY [ 0.241s]
writing 'boot'...
OKAY [ 0.069s]
erasing 'userdata'...
OKAY [ 0.010s]
sending 'userdata' (141063 KB)...
OKAY [ 4.517s]
writing 'userdata'...
OKAY [ 0.973s]
erasing 'cache'...
OKAY [ 0.007s]
sending 'cache' (6248 KB)...
OKAY [ 0.207s]
writing 'cache'...
OKAY [ 0.039s]
finished. total time: 6.072s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot fla
sh recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.276s]
writing 'recovery'...
OKAY [ 0.053s]
finished. total time: 0.330s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot fla
sh system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (522112 KB)...
OKAY [ 18.419s]
writing 'system'...
OKAY [ 3.259s]
sending sparse 'system' (510197 KB)...
OKAY [ 18.074s]
writing 'system'...
OKAY [ 3.206s]
sending sparse 'system' (515601 KB)...
OKAY [ 18.729s]
writing 'system'...
OKAY [ 3.346s]
sending sparse 'system' (188485 KB)...
OKAY [ 6.604s]
writing 'system'...
OKAY [ 1.167s]
finished. total time: 72.851s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot fla
sh cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.000s]
sending 'cache' (6248 KB)...
OKAY [ 0.218s]
writing 'cache'...
OKAY [ 0.038s]
finished. total time: 0.258s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot fla
sh userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.016s]
sending 'userdata' (138868 KB)...
OKAY [ 4.469s]
writing 'userdata'...
OKAY [ 0.903s]
finished. total time: 5.388s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>
fail
Still stuck on Beanstalk 5.0 animation, recovery is still TWRP 2.8.3.1. I've tried to format to different formats (ie; fat, ext2, ext3) nothing is working
didn't think it would warranty since unlocked, custom boot anim and custom recovery
Did you solve this problem? I The same problem happened to me.

[Q] XT1100 soft brick

Phone is staing in bootloader- i cant boot any other function like at normal boot, recovery, qcom, bp tools...nothing. Device is LOCKED!!!'Allow OEM Unlock' in developer options is UNCHEKED!!!
BL: moto-apq8084-71.08 (sha-32g8854, 2014-12-09 14:00:26)
Baseband: D4.0-9625-02.95
Product/Variant: shamu XT1100 64GB P3AO
Code:
c:\adb>Fastboot oem lock begin
...
(bootloader) fastboot oem lock currently disabled!
OKAY [ 0.002s]
finished. total time: 0.002s
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.012s
downloading 'boot.img'...
OKAY [ 0.469s]
booting...
FAILED (remote failure)
finished. total time: 0.479s
c:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.026s]
sending 'cache' (6248 KB)...
OKAY [ 0.249s]
writing 'cache'...
OKAY [ 0.141s]
finished. total time: 0.426s
c:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 59743535104
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14585824
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3646496 inodes and 274946/14585824 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.700s]
sending 'userdata' (141063 KB)...
OKAY [ 5.993s]
writing 'userdata'...
OKAY [ 3.731s]
finished. total time: 11.434s
c:\adb>
c:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (522112 KB)...
OKAY [ 24.621s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.648s
c:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytessending 'boot' (7681 KB)...
OKAY [ 0.299s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.315s
Seriously, do you guys not search ANYWHERE? There are tons of threads regarding bricked Nexus 6s, there's even an unbricking thread about this in this very section! http://forum.xda-developers.com/showthread.php?t=3059518
brando56894 said:
Seriously, do you guys not search ANYWHERE? There are tons of threads regarding bricked Nexus 6s, there's even an unbricking thread about this in this very section! http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
read carefully- my phone not detect like HS-USB QDLoader it is like adb bootloader interface. This happened after rewrite files into /dev/block/. Backups all those files i have. Question- how to write them back?
Duumon said:
read carefully- my phone not detect like HS-USB QDLoader it is like adb bootloader interface. This happened after rewrite files into /dev/block/. Backups all those files i have. Question- how to write them back?
Click to expand...
Click to collapse
Cannot.
rootSU said:
Cannot.
Click to expand...
Click to collapse
I found the way to connect phone as HS-USB QDloader device. All filles of blank-flash.bat flashed, but phone stil dont turn on
Duumon said:
I found the way to connect phone as HS-USB QDloader device
Click to expand...
Click to collapse
How?
rootSU said:
How?
Click to expand...
Click to collapse
testpoint
Duumon said:
testpoint
Click to expand...
Click to collapse
You created a "testpoint" cable?
That's interesting - @efrant
@Duumon - are you still following this thread? http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
@Duumon - are you still following this thread? http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Click to expand...
Click to collapse
yes-all those steps passed, but phone stil in locked bootloader. I think need flash boot and sysstem by qualkomm tool but.....how?
Duumon said:
yes-all those steps passed, but phone stil in locked bootloader. I think need flash boot and sysstem by qualkomm tool but.....how?
Click to expand...
Click to collapse
Did you also read post 94 (and related posts) of that thread?
@randy6644 got it to work.
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518/post59650346
What is a testpoint cable?
Doesn't helped. Phone have cid-dead and status unlock-not supported. In photo at attach not full the last log- system and boot .img flashed with error Preflash validation failed
still dead...any ideas?
Duumon said:
I found the way to connect phone as HS-USB QDloader device. All filles of blank-flash.bat flashed, but phone stil dont turn on
Click to expand...
Click to collapse
Same Problem. Can you explain how you create the testpoint cable?
Gesendet von meinem LG-D855 mit Tapatalk

Phone continues to bootloop.

Good morning everyone.
So my phone has been constantly boot looping. It restarted one night by itself and has been stuck restarting at the google logo every time. I did a flash stock soft brick with wugs rootkit and still with no success. Here is what the command prompt is saying during the process. Any assistance would help, thank you.
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) Motoboot: Preflash validation for aboot
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.280s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (67169 KB)...
OKAY [ 2.308s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.922s]
finished. total time: 3.233s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.010s
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (7624 KB)...
OKAY [ 0.319s]
writing 'boot'...
OKAY [ 0.148s]
finished. total time: 0.477s
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.030s]
sending 'cache' (6248 KB)...
OKAY [ 0.200s]
writing 'cache'...
OKAY [ 0.118s]
finished. total time: 0.369s
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (8198 KB)...
OKAY [ 0.262s]
writing 'recovery'...
OKAY [ 0.124s]
finished. total time: 0.402s
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (524140 KB)...
OKAY [ 19.200s]
writing 'system' 1/4...
OKAY [ 7.028s]
sending sparse 'system' 2/4 (508171 KB)...
OKAY [ 19.254s]
writing 'system' 2/4...
OKAY [ 6.791s]
sending sparse 'system' 3/4 (519126 KB)...
OKAY [ 20.194s]
writing 'system' 3/4...
OKAY [ 7.098s]
sending sparse 'system' 4/4 (88808 KB)...
OKAY [ 3.422s]
writing 'system' 4/4...
OKAY [ 1.114s]
finished. total time: 84.283s
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.831s]
sending 'userdata' (139061 KB)...
OKAY [ 4.672s]
writing 'userdata'...
OKAY [ 2.600s]
finished. total time: 8.102s
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.022s]
sending 'cache' (6248 KB)...
OKAY [ 0.216s]
writing 'cache'...
OKAY [ 0.099s]
finished. total time: 0.338s
rebooting...
finished. total time: 0.016s
Assuming it's a Nexus 6 and Twrp-recovery is installed.
Download a stock lite rom prerooted and copy it to internal memory of the N6. In zip formaT.
Boot in bootloader and choose -recovery
( press power button and volume buttons )
In twrp wipe system, and caches and data.
Choose install.
Navigate to the downloaded zip and flash it.
http://forum.xda-developers.com/showthread.php?p=59561445/
Thank you for responding so quickly!
Unfortunately when I go into the bootloader, when I choose recovery or any of the options, it just continues to bootloop.
NLBeev said:
Assuming it's a Nexus 6 and Twrp-recovery is installed.
Download a stock lite rom prerooted and copy it to internal memory of the N6. In zip formaT.
Boot in bootloader and choose -recovery
( press power button and volume buttons )
In twrp wipe system, and caches and data.
Choose install.
Navigate to the downloaded zip and flash it.
http://forum.xda-developers.com/showthread.php?p=59561445/
Click to expand...
Click to collapse
khanhathan said:
Thank you for responding so quickly!
Unfortunately when I go into the bootloader, when I choose recovery or any of the options, it just continues to bootloop.
Click to expand...
Click to collapse
When boot Twrp-recovery isn't possible, you need to flash with 'fastboot' everything again.
Best is to flash manually bootloader, Twrp-recovery, radio and system.
There are several guides on XDA. You could start here:
http://forum.xda-developers.com/showthread.php?p=41374534/
No luck =[.
NLBeev said:
When boot Twrp-recovery isn't possible, you need to flash with 'fastboot' everything again.
Best is to flash manually bootloader, Twrp-recovery, radio and system.
There are several guides on XDA. You could start here:
http://forum.xda-developers.com/showthread.php?p=41374534/
Click to expand...
Click to collapse
khanhathan said:
No luck =[.
Click to expand...
Click to collapse
When you have ' adb ' and ' fastboot ' dtivers correctly installed on a PC it is possible to reboot in bootloader mode with the bootloader on the PC. You have to learn the basics of adb and fastboot.
http://forum.xda-developers.com/showthread.php?p=42970252/
http://forum.xda-developers.com/showthread.php?p=57607286/
Try without wanting an unencrypted boot. Then it should work. Also read up on flashing with adb/fastboot to get a clear understanding of what is done. Tool kits are great and wugs is awesome. But you still need to know the fundamentals.

How could I recovery my Nexus 6

Hi,
I was trying to update my Nexus 6 to Android Nougat(nbd90z) today, the system image failed to be flashed. And then I locked the device by mistake. Then I became unable to flash any images.
If I tried to flash any image, it failed and the message is below.
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
If I tried to unlock the device, it failed and the message is below.
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
And because the system image failed to flash, so I can't boot the device to check the 'Allow OEM Unlock'.
Is there any way to recovery my device? Thanks very much for the help.
Below is the text from the command terminal where I tried.
<pre>
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.528s]
finished. total time: 0.657s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.609s]
finished. total time: 5.226s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.21
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: ZX1G22H7C4
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8535 KB)...
OKAY [ 0.269s]
writing 'boot'...
OKAY [ 0.161s]
sending 'recovery' (13921 KB)...
OKAY [ 0.439s]
writing 'recovery'...
OKAY [ 0.208s]
sending sparse 'system' (508909 KB)...
OKAY [ 16.031s]
writing 'system'...
OKAY [ 7.247s]
sending sparse 'system' (524036 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 28.751s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot devices
ZX1G22H7C4 fastboot
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem lock
...
^C
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem lock
...
(bootloader) Device state transition will erase userdata.
(bootloader) Are you sure you want to continue this transition?
(bootloader)
(bootloader) Press POWER key to continue.
(bootloader) Press VOL UP or VOL DOWN key to cancel state transition.
(bootloader) State transition confirmed!
(bootloader) Phone is locked successfully!
OKAY [ 24.319s]
finished. total time: 24.319s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.132s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.21
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: ZX1G22H7C4
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8535 KB)...
OKAY [ 0.269s]
writing 'boot'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.288s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
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
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ geany flash-base.sh
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-base.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.132s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem --help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
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
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.001s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot reboot
rebooting...
finished. total time: 0.151s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot flash radio radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot devices
ZX1G22H7C4 fastboot
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ cd /home/zhiming/Project/Nexus/Images/shamu-mob31e/
[email protected]:~/Project/Nexus/Images/shamu-mob31e$ ls
bootloader-shamu-moto-apq8084-71.18.img flash-all.bat flash-all.sh flash-base.sh image-shamu-mob31e.zip radio-shamu-d4.01-9625-05.34+fsg-9625-02.111.img
[email protected]:~/Project/Nexus/Images/shamu-mob31e$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.327s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.332s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'radio' (115508 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
--------------------------------------------
Bootloader Version...: moto-apq8084-71.21
Baseband Version.....: D4.01-9625-05.42+FSG-9625-02.113
Serial Number........: ZX1G22H7C4
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'moto-apq8084-71.21'.
Update requires 'moto-apq8084-71.18'.
finished. total time: 2.498s
[email protected]:~/Project/Nexus/Images/shamu-mob31e$ cd /home/zhiming/Project/Nexus/Images/shamu-nbd90z/
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ls
bootloader-shamu-moto-apq8084-71.21.img flash-all.bat flash-all.sh flash-base.sh image-shamu-nbd90z.zip radio-shamu-d4.01-9625-05.42+fsg-9625-02.113.img
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ ./flash-base.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.135s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.113s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.617s]
writing 'radio'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 3.622s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.151s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$ fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.001s
[email protected]:~/Project/Nexus/Images/shamu-nbd90z$
</pre>
ZhimingWU said:
Is there any way to recovery my device? Thanks very much for the help.
Click to expand...
Click to collapse
Flash an OTA image. They're intended to be flashed even on locked systems.
Strephon Alkhalikoi said:
Flash an OTA image. They're intended to be flashed even on locked systems.
Click to expand...
Click to collapse
Thank you for the reply. Does flashing OTA images needs to boot system normally? My phone is unable to boot system normally due to failure of flashing system image.
Strephon Alkhalikoi, thank you very much. I got my device recovered.
I followed the instructions at https://developers.google.com/android/nexus/ota, except replacing Step 3 by below steps to boot into recovery mode.
a. Hold Volume Down key and press Power key to enter fastboot mode.
b. Press Volume Down key to navigate to "Recovery mode" and press Power key.
ZhimingWU said:
Thank you for the reply. Does flashing OTA images needs to boot system normally? My phone is unable to boot system normally due to failure of flashing system image.
Click to expand...
Click to collapse
Do you have recovery installed?
If yes and hopefully TWRP which is best option, just go to recovery, mount phone, transfer OTA image, factory reset, and flash it.
Also, if upgrading from 6.x.x to 7.0.0 you must flash the Nougat bootloader img. which in order to do it, i recommand using Nexus toolkit which you could access only via phone being on.
So what i do recommand is the next thing:
download 6.x.x ota and install it.
boot into phone, unlock developer options and usb debugging, also check the "oem unlocking".
plug the phone to the pc while using an adb program like nexus tookit, unlock bootloader.
then download the Nougat bootloader img, and radio img (not a must). into the pc, and flash it via nexus root toolkit once again.
After your'e done flashing, all you have to do is go to recovery mode and flash the Nougat rom.
And before all that, make sure you have the latest TWRK recovery.

Categories

Resources