I messed up my tab after I rooted it and used an app that lowers the DPI setting. Now I can't see anything after I restart my tablet. It's just a black screen. I can hold down power and the down button to get to the screen where the android is showing it's guts and can choose between Recovery and Power off.... but not clock work recovery. I tried pressing the up button as it powers on but nothing. It was rooted using the on click root option which was also supposed to install CWR but it's not working. Can anyone explain how to flash the original rom back to the device without using CWR just using the PC?
Thanks.
i'm very noob at this but i thought there was somehing with ADB?
download & install the android SDK from google, developer.android.com/sdk/index.html, & follow their instructions to configure it
download the stock ROM from google, developers.google.com/android/nexus/images, and follow the instructions
pretty straight forward, done it twice already
Come on. Please use the search, this is what it's there for.
http://forum.xda-developers.com/showthread.php?t=
Sent from my Nexus 7 using xda premium
tehSmoogs said:
download & install the android SDK from google, developer.android.com/sdk/index.html, & follow their instructions to configure it
download the stock ROM from google, developers.google.com/android/nexus/images, and follow the instructions
pretty straight forward, done it twice already
Click to expand...
Click to collapse
Thanks! I will follow the steps.
kind3rgarten said:
Come on. Please use the search, this is what it's there for.
http://forum.xda-developers.com/showthread.php?t=
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I apologize. I tried to do a search but what came up was confusing me more.
tehSmoogs said:
download & install the android SDK from google, developer.android.com/sdk/index.html, & follow their instructions to configure it
download the stock ROM from google, developers.google.com/android/nexus/images, and follow the instructions
pretty straight forward, done it twice already
Click to expand...
Click to collapse
I've downloaded the SDK and the rom file and have extracted it.
It says to run the ./flash-all.sh script. But it's not associated with any programs. I assume that I load this file into the SDK?
I think flashing the entire image might be overkill. You (or the app, I guess) presumably only messed with the build.prop, right? If so, should only have to find and reflash a working build.prop.
Warning: the above is noob advice. I'm just guessing here.
thebobp said:
I think flashing the entire image might be overkill. You (or the app, I guess) presumably only messed with the build.prop, right? If so, should only have to find and reflash a working build.prop.
Warning: the above is noob advice. I'm just guessing here.
Click to expand...
Click to collapse
Thanks. But I think my problem is bigger than that. I can't see the tablet on my computer anymore. After the Google logo with the unlocked sign on the bottom goes away, I assume this is the point where I'm supposed to see the Nexus logo. It doesn't get that far. When I tried to connect it to the USB on the computer, I hear a connection signal but the tablet never pops up in Windows. I was only able to get to the CWR screen once. Don't know how I did it but when I tried to select Wipe Data/Factory Reset, it just shows me an icon of a top hat and a circle underneath it. Pressing the power button just brought me back to the CWR screen and any other choice will give me the top hat screen. I haven't been able to get back to CWR screen again. I can get to the main screen where I can select start/restart bootloader/recovery but selecting recovery doesn't get me back into the CWR screen.
thebobp said:
I think flashing the entire image might be overkill. You (or the app, I guess) presumably only messed with the build.prop, right? If so, should only have to find and reflash a working build.prop.
Warning: the above is noob advice. I'm just guessing here.
Click to expand...
Click to collapse
Yeah.
Protip: Backup Build.prop before messing with it.
If you would have just backed it up you could have done a simple adb push.
Sent from my Nexus 7 using xda premium
I didn't do that. That's probably why I get the top hat when I tried to do a factory wipe from CWR
At this point I think it's not going to be able to connect to the computer. I'll exchange it for another one and not use that app!
If you're willing, give this a go.....
You'll need to copy flash-all.sh, bootloader-grouper-3.34.img and image-nakasi-jrn84d.zip files to the "C:\Program Files (x86)\Android\android-sdk\platform-tools\" folder - thats if the sdk installed to the same place as mine.
Start a command prompt and change directory to the platform-tools folder.
Check that the tablet is accessible by doing a "fastboot devices" - it should display a hex string - if you don't get this then you'll be beyond my help......
The flash-all.sh file is the unix equivalent of a ".bat" file, all you need to do is rename it to "flash-all.bat" and then run it from the commnd prompt.
When you run it you should see something like this:-
erasing 'boot'...
OKAY [ 0.104s]
finished. total time: 0.104s
erasing 'cache'...
OKAY [ 0.130s]
finished. total time: 0.130s
erasing 'recovery'...
OKAY [ 0.105s]
finished. total time: 0.105s
erasing 'system'...
OKAY [ 0.176s]
finished. total time: 0.176s
erasing 'userdata'...
OKAY [ 1.251s]
finished. total time: 1.251s
sending 'bootloader' (2072 KB)...
OKAY [ 0.284s]
writing 'bootloader'...
OKAY [ 1.168s]
finished. total time: 1.452s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: xxxxxxxxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
sending 'boot' (4884 KB)...
OKAY [ 0.663s]
writing 'boot'...
OKAY [ 0.328s]
sending 'recovery' (5228 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.268s]
sending 'system' (432360 KB)...
OKAY [ 52.602s]
writing 'system'...
OKAY [ 21.431s]
erasing 'userdata'...
OKAY [ 1.041s]
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 [ 24.636s]
erasing 'cache'...
OKAY [ 0.115s]
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.808s]
rebooting...
finished. total time: 103.718s
At that point you should be booting back to stock.
Good luck!
CyberChulo said:
I didn't do that. That's probably why I get the top hat when I tried to do a factory wipe from CWR
Click to expand...
Click to collapse
i just messed mine up the exact same way, but hopefully we'll figure it out instead of returning a product that we specifically killed
tehSmoogs said:
If you're willing, give this a go.....
At that point you should be booting back to stock.
Good luck!
Click to expand...
Click to collapse
Thanks for all your help but the computer does not recognize any usb device connected. I've returned it and waiting on another one to come in. I sure as hell won't be messing around with dpi settings anymore!
CyberChulo said:
Thanks for all your help but the computer does not recognize any usb device connected. I've returned it and waiting on another one to come in. I sure as hell won't be messing around with dpi settings anymore!
Click to expand...
Click to collapse
Okay, for one, LCD modder has been known not to work with the N7, use ROM toolbox or manually edit the prop yourself.
Two, do you possibly have the phone plugged into a USB 3.0 port? ADB and the drivers do not like USB 3.0 ports. Is there also possibly a driver or something that is not installed? Look at the link I posted on the first page.
Sent from my Galaxy Nexus using xda premium
kind3rgarten said:
Okay, for one, LCD modder has been known not to work with the N7, use ROM toolbox or manually edit the prop yourself.
Two, do you possibly have the phone plugged into a USB 3.0 port? ADB and the drivers do not like USB 3.0 ports. Is there also possibly a driver or something that is not installed? Look at the link I posted on the first page.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
All drivers were installed initially when I ran the One click Root procedure. I did have it plugged into a USB 3.0 port at home but at work I only have 2.0 ports. None of them recognized the device other than showing that a USB device was connected. It has trouble finding the MTP driver.... after I had modded the dpi setting.
Related
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?
Someone at Google's mess the links. Here are the correct ones...
NEXUS 5 hammerhead:
https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz
NEXUS 7 2013 razor:
https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz
NEXUS 7 2013 razorg
https://dl.google.com/dl/android/aosp/razorg-kot49h-factory-49789b24.tgz
NEXUS 4 occam:
https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz
NEXUS 10 mantaray:
https://dl.google.com/dl/android/aosp/mantaray-kot49h-factory-174ba74f.tgz
NEXUS 7 2012 nakasi:
https://dl.google.com/dl/android/aosp/nakasi-kot49h-factory-5e9db5e1.tgz
NEXUS 7 2012 nakasig:
https://dl.google.com/dl/android/aosp/nakasig-kot49h-factory-83d93b5f.tgz
How did u found the correct links?
btw, downloading, THANKS
C4SCA said:
How did u found the correct links?
btw, downloading, THANKS
Click to expand...
Click to collapse
The last 8 chars of the link really are the first 8 chars of the SHA-1 Checksum (that is correct).
You rock man! Thanks!
Does google release odex versions ?
Sent from my SM-N900T using Tapatalk
alleyezondisromo said:
Does google release odex versions ?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Yes, these images are odexed.
thanks [email protected]!!!!
flashing!
Thanks pal. really needed this.
Thanks! Was just about to flash my phone when I realized the links on Google's website doesn't work!
Sfkn2 said:
Thanks! Was just about to flash my phone when I realized the links on Google's website doesn't work!
Click to expand...
Click to collapse
lol me too...I was all excited, then I realized I just get a 404 error. I actually thought they just hadn't finished uploading the images and jumped the gun posting links. Glad I saw this thread!!
Thank you. I downloaded Android SDK, copied the dll's and fastboot/adb from the platform-tools folder to C:\windows\syswow64\ and then extracted the occam-kot49h tgz and modified the flash-all.bat as to remove the "-w" (wipe) command from the fastboot update command and then I threw my phone into fastboot mode and opened up a command prompt and ran that flash-all.bat, upgraded from 4.4 to 4.4.2 seamlessly with no data loss. Of course I did lose root as expected and I suppose I should have removed/commented out the flashboot radio command line so I could have kept LTE, oh well I'll fix that later. Thanks again.
hi thanx for the links
after downloading i had this error:
Code:
[email protected]:~/occam-kot49h$ sudo sh flash-all.sh
sending 'bootloader' (2203 KB)...
OKAY [ 0.104s]
writing 'bootloader'...
OKAY [ 0.766s]
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 2.128s]
writing 'radio'...
OKAY [ 2.805s]
finished. total time: 4.934s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0216337d9153f835
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.334s]
sending 'recovery' (6888 KB)...
OKAY [ 0.344s]
writing 'recovery'...
OKAY [ 0.392s]
erasing 'system'...
OKAY [ 0.716s]
sending 'system' (713960 KB)...
OKAY [ 33.568s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 47.589s
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)
activexda said:
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)
Click to expand...
Click to collapse
Are you using the latest SDK? That error usually means that the version of the fatsboot command isn't one liked by the bootloader.
VivaErBetis said:
Are you using the latest SDK? That error usually means that the version of the fatsboot command isn't one liked by the bootloader.
Click to expand...
Click to collapse
ok i will download the "SDK Tools Only" package, thats all what i need right?
activexda said:
ok i will download the "SDK Tools Only" package, thats all what i need right?
Click to expand...
Click to collapse
Yes, and inside it the latest “platform tools“.
VivaErBetis said:
Yes, and inside it the latest “platform tools“.
Click to expand...
Click to collapse
ok, after trying with latest sdk i still have the same problem
is there anybody managed to install the factory image?
Maybe you messed up the script.
gm007 said:
Maybe you messed up the script.
Click to expand...
Click to collapse
i don't think so
script:
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.98.img
fastboot reboot-bootloader
sleep 5
fastboot update image-occam-kot49h.zip
Maybe download the file again.
activexda said:
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)
Click to expand...
Click to collapse
gm007 said:
Maybe download the file again.
Click to expand...
Click to collapse
I would definitely download the file again. Did you check the MD5 sum?
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
Direct download link:
https://dl.google.com/dl/android/aosp/occam-lmy47o-factory-cae68e81.tgz
md5sum: 293a98009cfbcb5d398c05302a86ee8c
sha1sum: cae68e81d5a1758f92b77520f829400da205111f
Goggle's Factory Images page:
https://developers.google.com/android/nexus/images
Tip for those upgrading without flashing via factory image. After you flash cache.img boot into your custom recovery of choice and wipe the cache partition. Otherwise you're going to be stuck on the lollipop circles for a long time. This is specific to nexus 4.
Sent from my Nexus 7 using Tapatalk
How can i root it ?
Virtxer said:
How can i root it ?
Click to expand...
Click to collapse
You're kidding right?
Yep
Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app
Zehlek said:
Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Hi there, long time no see
I was gonna do a flashable version but my pc was acting up again so i'll see if I can do it tomorrow after work if someone else doesn't do it by then :good:
does only me have problem with - remote partition table doesn't exist,when try to install twrp,or this is a comon isue?
i install stock image(unzip it with 7z),install with flash all. everything pass ok. when i turn on usb debuging and try to install twrp with fastboot i get this error.
i try to install stock image manuallu with fastboot. in that case i must to do a factory resset when boot,or phone will stuck with boot. also this pass ok,but fasboot cant install only twrp. old version,new,same error. fastboot recognize nexus,commands working,
Zehlek said:
Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I'm using the latest Simple AOSP for Nexus 4 (Android 5.1.0), which was built today, with the LMY47O binary file, no random reboot so far.
Here is everything you need: http://chromloop.com/2015/04/how-to-install-android-5-1-lollipop-custom-rom-nexus-4/
5.0.1 (LRX22C) factory to 5.1.0 (LMY47O) factory
My bootloader was already un-locked. Hold the volume down key and hit the power button to power on the phone into fastboot mode.
Windows 7
Front USB 2.0 ports
7-zip
[TOOL]Updated ADB (version 1.0.32) and Fastboot [16-OCT-14]
http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
extract - fastboot_adb(1.0.32)_071114_r21.rar
extract - occam-lmy47o-factory-cae68e81.tgz
extract - occam-lmy47o-factory-cae68e81.tar
Move all of the files into the fastboot_adb(1.0.32)_071114_r21 folder.
Open the folder. Hold down the shift key and right click. Click on "open command windows here"
type in: flash-all.bat or fl and hit the tab key.
FAIL:
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>flash-all.bat
< waiting for device >
sending 'bootloader' (2264 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
OKAY [ 0.281s]
finished. total time: 0.374s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.560s]
writing 'radio'...
OKAY [ 2.480s]
finished. total time: 4.040s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 854497332 bytes
error: update package missing system.img
Press any key to exit...
Extract image-occam-lmy47o.zip into the fastboot_adb(1.0.32)_071114_r21 folder.
Run the following commands.
There is no need to update the bootloader and modem. You can see on the screen the current bootloader and modem build were updates from the last step.
Commands found via http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img ***took apx 8 mins before seeing anything being written to the screen and phone.***
fastboot flash boot boot.img
fastboot flash recovery recovery.img *** don't do this if you have TWRP installed ***
fastboot format cache
fastboot reboot
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery recovery.img
sending 'recovery' (6956 KB)...
OKAY [ 0.234s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash boot boot.img
sending 'boot' (6394 KB)...
OKAY [ 0.250s]
writing 'boot'...
OKAY [ 0.374s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash system system.img
erasing 'system'...
OKAY [ 0.827s]
sending 'system' (834470 KB)...
OKAY [ 50.747s]
writing 'system'...
OKAY [ 46.519s]
finished. total time: 98.140s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash boot boot.img
sending 'boot' (6394 KB)...
OKAY [ 0.250s]
writing 'boot'...
OKAY [ 0.374s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery recovery.img
sending 'recovery' (6956 KB)...
OKAY [ 0.265s]
writing 'recovery'...
OKAY [ 0.374s]
finished. total time: 0.640s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot format cache
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
erasing 'cache'...
OKAY [ 0.078s]
sending 'cache' (10984 KB)...
OKAY [ 0.437s]
writing 'cache'...
OKAY [ 0.608s]
finished. total time: 1.139s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot reboot
rebooting...
finished. total time: -0.000s
It took apx 11 mins to boot up. It was optimizing the 100+ apps. All my apps and config settings were there.
Optional....
I powered off and when back into fastboot mode to flash TWRP so I can create a backup image.
http://dl.twrp.me/mako/
fastboot flash recovery twrp-2.8.6.0-mako.img
Use the arrow keys to reboot into recovery mode to boot into TWRP. Do not boot into the system.
Ok, managed to get my laptop working again. Rom is uploading, will post a link to the thread when done :good:
EDIT: Thread link: http://forum.xda-developers.com/nexus-4/development/rom-stock-flashable-rom-t3084656
If you get ANY Errors during Updating via the flash-all script - try to update ADB itself. I was using an old version and got errors until i downloaded and used a new ADB version.
Where is the 5.1.1?
Mirkoitalia said:
Where is the 5.1.1?
Click to expand...
Click to collapse
I don't know. When did you see it last?
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
GuardianUSMC said:
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
Click to expand...
Click to collapse
No, you cannot ad root to the image before flashing.
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
gee2012 said:
No, you cannot ad root to the image before flashing.
Click to expand...
Click to collapse
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
Click to expand...
Click to collapse
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
GuardianUSMC said:
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
Click to expand...
Click to collapse
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
gee2012 said:
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
Click to expand...
Click to collapse
Got it, thank you very much for your assistance.
Too bad the Factory Images from Google are not already rooted.
GuardianUSMC said:
So the factory images provided directly by Google are NOT at root already either?
Click to expand...
Click to collapse
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
So for example on a linux machine you will have the root directory:
/
Within root, you will have other directories such as:
/bin
/etc
/usr
See here for more information:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
So root is kind of like the C:\ drive on a Windows PC. Everything to do with the OS and User directories are within there.
Your Android device is the same, however, /bin, /etc (etc) are not at the root of the device. They sit within the system partition, which sits within root. so /system/bin, /system/etc. When you flash a factory image, it flashes the images to /system, /cache, /userdata (and a few other places) where as the root of the device remains largely untouched.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
@rootSU,
Excellent mini tutorial. I wish this could be stickied on the General roll up thread. Thank you very much.
rootSU said:
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
Click to expand...
Click to collapse
I appreciate that and forgive me I know I used the terms interchangeably and that's my bad.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
Click to expand...
Click to collapse
yes I am familiar with that and I was using the term to mean having root privileges, again my bad.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
Click to expand...
Click to collapse
Understood, I have done that and my device is currently rooted. I was more looking into making an image that is already rooted, to borrow a term from Windows, slipstream the root functionality pre-flashing. I was told not going to happen, that's fine. Although when I had my HTC Evo 4G, I had pre-rooted images that I had created with the bloat removed and I was flashing them with root functionality out of the box, but that's another story, I guess Nexus 6 is a different animal and dealing with Lollipop probably more difficult than Gingerbread.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
Click to expand...
Click to collapse
No but I appreciate you taking the time, thank you.
Right now mostly I am frustrated with the fact that the factory images provided by google will not flash right and keep *****ing about missing .sig files. I have tried flashing them individually by taking the root, system, recovery images out of the zip file and doing them individually as been suggested all over the place but no luck there there, keeps *****ing about the partitions instead, makes no sense. The bootloader and radio images go through without a hitch but the rest is just a mess.
Just to share, I am trying to flash the factory image that I mentioned in my original post, so I won't repost it. Here is what did so far to no avail, so any assistance would be greatly appreciated:
I issue the command adb reboot bootloader and it successful reboots the phone into the bootloader
Extracting the folder shamu-lmy47i containing the following files:
bootloader-shamu-moto-apq8084-71.08.img
flash-all.bat
flash-all.sh
flash-base.sh
image-shamu-lmy47i.zip
radio-shamu-d4.0-9625-02.95.img
Opening the batch file you see the following (I have removed the copyright header for sake of brevity)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
echo Press any key to exit...
pause >nul
exit
Since the only thing I want to add to this is root, I add this after the image update:
Code:
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
So we let it rip and this is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
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.548s]
finished. total time: 0.674s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.720s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.102s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
downloading 'boot.img'...
OKAY [ 0.393s]
booting...
OKAY [ 0.024s]
finished. total time: 0.419s
Press any key to exit...
As we can see, bootloader image flashes just fine
The radio image flashes just fine
System image on the other hand does not update complaining about missing .sig files:
fastboot -w update image-shamu-lmy47i.zip said:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
Click to expand...
Click to collapse
The files inside this system zip are:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Ironically the SuperSU image flashes just fine and reboots the phone
I am frustrated by the fact that the system image update step fails and nothing out there explains why? I have even tried to extract each of those images from the zip file and flashing them individually using the fastboot flashall but getting the same error as well as other errors.
Can anyone lend an assist on this and help me figure out how to overcome that hurdle PLEASE?
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Evolution_Freak said:
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Click to expand...
Click to collapse
I did provide everything step by step the only thing I didn't provide was the errors on the individual images that are within the update zip file. Which I suppose is my bad:
Code:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
and I have tried flashall last because documentation states it will do boot, recovery and system but I have also done them using individual commands too. But more on that after I take a look at what you posted in the link. Stay tuned. Thank you.
Alright, good news, it worked and thank you for pointing to the resource that allowed me to figure out why I was getting the partition errors, now I know.
I modified the batch file as follows:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
adb reboot bootloader
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
echo Press any key to exit...
pause >nul
exit
it went through the whole process and here is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
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.508s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.722s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.110s]
finished. total time: 3.834s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 536870912 bytes
sending sparse 'system' (522196 KB)...
OKAY [ 22.442s]
writing 'system'...
OKAY [ 7.691s]
sending sparse 'system' (510114 KB)...
OKAY [ 21.723s]
writing 'system'...
OKAY [ 6.674s]
sending sparse 'system' (514997 KB)...
OKAY [ 21.128s]
writing 'system'...
OKAY [ 7.778s]
sending sparse 'system' (189177 KB)...
OKAY [ 7.652s]
writing 'system'...
OKAY [ 2.328s]
finished. total time: 97.428s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 11.844s]
sending 'userdata' (138868 KB)...
OKAY [ 4.518s]
writing 'userdata'...
OKAY [ 1.949s]
finished. total time: 18.315s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.247s]
writing 'boot'...
OKAY [ 0.110s]
finished. total time: 0.359s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.116s]
finished. total time: 0.384s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.013s]
sending 'cache' (6248 KB)...
OKAY [ 0.204s]
writing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.318s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
OKAY [ 0.035s]
finished. total time: 0.436s
Thank you for everyone's input and assistance here, you rock.