Hi,
I tried to update to Android 4.2 (from 4.1.2) today, but it failed at the stock recovery saying:
[..]
assert failed: apply_patch_check("/system/app/Books.apk", ........
Installation aborted.
Screenshot: https://www.dropbox.com/s/b8lk0n147cbcfuv/20121114_121646_4_bestshot.jpg
Using Titanium Backup I used to make Google Books a Userland application and uninstalled it a while ago, because I wanted to remove some bloatware. I installed the backup I had and made it a system-application again, but its still giving me that error. Even factory reset didnt help.
What options do I have? How can I flash the full image?
Kind regards
Alex
Nevermind, I found the factory image at
https://developers.google.com/android/nexus/images#nakasijop40c
Downloaded it, did a titanium backup, flashed image via flash-all.bat, restored root, restored backup and 4.2 with root is all up and running now.
Same problem with apply_patch_check error bij update.
Also try to flash full factory image 4.2 by fastboot.
After install and reboot, Google icon in screen, doesn't startup.
That 5x but no success.
Same install with factory image 4.1.2 and no problem.
Help!
---------- Post added at 01:10 PM ---------- Previous post was at 01:02 PM ----------
Hello Alex,
You said, flashed bij Flash-all.bat.
How does that work? You may have a brief description of how you do it?
Thank you!
In the .zip you downloaded, there is a file called flash-all.bat. For example it does this for the WiFi version:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jop40c.zip
echo Press any key to exit...
pause >nul
exit
Check your version an run it in platform-tools with all content beeing there of course. Its quite easy
You sense about PATH I do not understand.
The rest I have indeed done in cmd
I have indeed PlatformTools and I have all five files in that folder.
Same folder where adb.exe also capable.
I've done in cmd in the platformtools path:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jop40c.zip
Then start the nexus7 but remains on the startup screen on the google logo.
Am I forgetting something?
whats the output of the fastboot commands from above?
I have the same problem but with GooglePinyinime.apk.
Have just worked out how to sideload using adb and am getting stuck on this error.
I did freeze this app using titanium pro, then unfroze it when I upgraded to 4.1.2 ota successfully, so can't understand why its pulling up an error now?
Am a bit of a noob with these commands so would be very grateful for any help.
Am on stock rom, rooted and no custom recovery.
Thanks.
Sent from my Nexus 7 using Tapatalk 2
simacca said:
I have the same problem but with GooglePinyinime.apk.
Have just worked out how to sideload using adb and am getting stuck on this error.
I did freeze this app using titanium pro, then unfroze it when I upgraded to 4.1.2 ota successfully, so can't understand why its pulling up an error now?
Am a bit of a noob with these commands so would be very grateful for any help.
Am on stock rom, rooted and no custom recovery.
Thanks.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Do you have fastboot installed on your computer? I am not in front of my development computer so I can't give you specific details but I had a several modifications to /system so I didn't bother trying to reverse them and instead flashed the original 4.1.2 system.img.
The (rough) procedure for this is:
1. Backup your current 4.1.2 rom in case you can't live with 4.2
2. Plug the nexus into your computer and boot into the bootloader (up vol + down vol + power)
3. On your computer, download the 4.1.2 factory image from https://dl.google.com/dl/android/aosp/nakasi-jzo54k-factory-973f190e.tgz
4. Unzip the image and then unzip the zip file that was inside the image (I can't remember the name but I believe there is only one)
5. If you unzipped everything correctly you should have a system.img file, open a command window and navigate to the directory that contains the system.img file and type:
Code:
fastboot flash system system.img
Sorry I don't have the specific details. If no one else has filled in the missing file names by the time I get home and you are comfortable with this procedure I will update this with the proper names.
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-group
er-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 1.252s]
finished. total time: 1.548s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\android-sdk-windows\platform-tools>fastboot -w update image-nakasi-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015d2578a3140811
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.599s]
writing 'boot'...
OKAY [ 0.405s]
sending 'recovery' (5444 KB)...
OKAY [ 0.660s]
writing 'recovery'...
OKAY [ 0.348s]
erasing 'system'...
OKAY [ 0.155s]
sending 'system' (477136 KB)...
OKAY [ 60.010s]
writing 'system'...
OKAY [ 23.794s]
erasing 'userdata'...
OKAY [ 1.092s]
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 [ 27.895s]
erasing 'cache'...
OKAY [ 0.119s]
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 [ 1.940s]
rebooting...
finished. total time: 117.197s
C:\android-sdk-windows\platform-tools>
Nexus root toolkit works
Nexus root toolkit works like a champ for restoring stock if you need it.
Works flawlessly in windows 7 for me.
http://www.wugfresh.com/nrt/
The real issue with the the assert errors is that you changed something you should not have. The 4.2 update hash checks the original system apps for consistency. If you changed any of the System apps outside of an official update you get the assert errors when trying to flash the new update.
Have the same problem...
[..]
assert failed: apply_patch_check("/system/app/Books.apk", ........
Installation aborted.
Anyone manage ti fix it without restoring original rom would be nice....
alex2308 said:
Nevermind, I found the factory image at
https://developers.google.com/android/nexus/images#nakasijop40c
Downloaded it, did a titanium backup, flashed image via flash-all.bat, restored root, restored backup and 4.2 with root is all up and running now.
Click to expand...
Click to collapse
Hi Alex,
Did flashed factory image returned our Nexus like a new phone or just restoring system files? I want to flash factory image but afraid if it's like a factory reset
everyday_ said:
Hi Alex,
Did flashed factory image returned our Nexus like a new phone or just restoring system files? I want to flash factory image but afraid if it's like a factory reset
Click to expand...
Click to collapse
Its like a full factory reset, everything is gone (also the /sdcard folder with the downloads and stuff). Restoring was pretty easy, I copied the /sdcard stuff via USB to my computer and used titanium backup to backup the apps with settings (and copied that too to my computer). The only thing I had to setup again was WiFi, Homescreen and Email (although you can backup them via Titanium, which I didnt).
Mathijs17 said:
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-group
er-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 1.252s]
finished. total time: 1.548s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\android-sdk-windows\platform-tools>fastboot -w update image-nakasi-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015d2578a3140811
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.599s]
writing 'boot'...
OKAY [ 0.405s]
sending 'recovery' (5444 KB)...
OKAY [ 0.660s]
writing 'recovery'...
OKAY [ 0.348s]
erasing 'system'...
OKAY [ 0.155s]
sending 'system' (477136 KB)...
OKAY [ 60.010s]
writing 'system'...
OKAY [ 23.794s]
erasing 'userdata'...
OKAY [ 1.092s]
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 [ 27.895s]
erasing 'cache'...
OKAY [ 0.119s]
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 [ 1.940s]
rebooting...
finished. total time: 117.197s
C:\android-sdk-windows\platform-tools>
Click to expand...
Click to collapse
Did you do a erase or just flash over them?
Related
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]
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
I had my nexus 6 rooted and unlocked then wanted to unroot to be able to upsdate to M.
Although when I tried to re-flash it ended up not being able to boot back up. now i have a nexus in bootloader but cannot get the system.img to flash.
I have tried doing all indiviually as well as using the flash all.bat . and i get this error everytime
sending sparse 'system' (522932 KB)...
FAILED (data transfer failure (Unknown error))
I have also tried using twrp to move over the .zip of the factory 5.1.1 and it just stops transferring about a 3rd of the way through.
I am fairly certain that i have the latest fastboot as well as all the latest from the sdk tools manager
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.133s]
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.363s]
finished. total time: 0.497s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (85419 KB)...
OKAY [ 2.790s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.142s]
finished. total time: 3.932s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
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.10
Baseband Version.....: D4.0-9625-02.101
Serial Number........: ZX1G22CVC4
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.003s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (7741 KB)...
OKAY [ 0.250s]
writing 'boot'...
OKAY [ 0.109s]
sending 'recovery' (8331 KB)...
OKAY [ 0.297s]
writing 'recovery'...
OKAY [ 0.125s]
sending sparse 'system' (522932 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 21.199s
Press any key to exit...
It looks like a connection problem somewhere. Are you able to try a new cable or USB port?
If you have the SDK installed make sure it's updated or use mfastboot either one will work with the larger file sizes.
http://mark.cdmaforums.com/ADB.htm
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.
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.