Related
I wouldn't think so, but I'm really clueless about what's going on...
I have Cyanogen 3.9.8
I want 4.0.2
When I use the CM Updater, I get the dreaded acore Force Close.
So I try the manual approach, putting the 4.0.2 zip file on my SD card's root, then I reboot into recovery, and I perform a Nandroid backup (I run Linux on my computer, and don't use ADB).
Then I do a wipe, before I install the 4.0.2 zip.
Finally, I do I Nandroid restore.
Rebooting takes a long time, which tells me something has been done in the ROM department.
But when I have it up and running, everything seems just as they were before the operation, and when I start CM Updater it says "Running version: CyanogenMod-3.9.8"
I tried again, this time I booted the phone before I did the Nandroid restore, was met with the "factory fresh" Google account login screen (so it looked wiped to me...), then did a reboot to recovery and a Nandroid restore, reboot, checked CM Updater: "Running version: CyanogenMod-3.9.8".
Maybe I need to tweak my ROM updating routines..?
I have 3 partion SD card, so apps2sd is running.
Any help is highly appreciated.
Thanks,
Christopher
I'm kinda confused here, it's Monday morning. Since your trying to upgrade why do you keep doing a nandroid restore? You only want to restore nandroid if you want to go back to that previous point when you made the restore point. If you are just upgrading, just upgrade without restoring nandroid.
do exactly what you did without doing the nandroid restore at the end
Nandroid Restore is pretty simple.
Say you have ROM1 installed and there is an experimental ROM2beta out. So you want to try it.
Do a nandroid backup and it saves it to your sdcard.
The files that are saved are:
recovery.img
data.img
system.img
cache.img
misc.img
boot.img
This is almost every part of your phone except the spl and radio.
When you do a ROM upgrade MOST of the time it only updates the system and boot (some ROMs like Hero wipe/update the system, data, cache and boot.) But if your going from Cyan1 to Cyan2 then the only things being changed are system.img and boot.img. Unless you wipe, everything else should remain the same.
With all that said... you flash from ROM1 to ROM2beta and then do a restore from the ROM1 backup. So what does that mean for your phone? Is it possible to have ROM2beta ROM with the ROM1 system.img and boot.img? No. Since system.img is restoring the key elements for the ROM1 over your newly flashed ROM2beta. Bottom line. You'd be right back to where you started.
Binary100100 said:
With all that said... you flash from ROM1 to ROM2beta and then do a restore from the ROM1 backup. So what does that mean for your phone? Is it possible to have ROM2beta ROM with the ROM1 system.img and boot.img? No. Since system.img is restoring the key elements for the ROM1 over your newly flashed ROM2beta. Bottom line. You'd be right back to where you started.
Click to expand...
Click to collapse
Which explains what I am experiencing.
Thanks, 36!
That means I have misunderstood what Nandroid does.
I thought it would just take a backup of "user changed" files, like application data, configurations, call logs, that sort of things - like MyBackup Pro, more or less.
Guess I will get back to using MyBackup Pro before I upgrade my ROM.
Thanks, this really clarified things - I'm sorry I had to post such a n00b question, but I haven't found any other Nandroid postings telling me in such details what Nandroid backs up (and restores) - but then again I probably haven't looked hard enough! ;-)
~Christopher
Seems I had the same misconception and it seems that Nandroid is not nearly as useful as I had been led to believe by all the posts harping on about it. What I want is a backup of all my user data which I can restore to the updated ROM. Luckily I suspected Nandroid wasn't going to do this and used MyBackup Pro too
MikLSP said:
Seems I had the same misconception and it seems that Nandroid is not nearly as useful as I had been led to believe by all the posts harping on about it. What I want is a backup of all my user data which I can restore to the updated ROM. Luckily I suspected Nandroid wasn't going to do this and used MyBackup Pro too
Click to expand...
Click to collapse
nandroid can do this you just have to do a backup flash youre rom then push youre data.img
I understand you push the data.img but.....
how...
please
Perform a nandroid backup
Locate the backup on your sdcard under the foler "Nandroid"
Navigate to the last folder (this should be your latest)
Copy all or at least the folder that you want to push back (in this case just data.img to a directory say c:\nandroidbackup)
Open the cmd prompt and make sure that you have your fastboot.exe file in your pc's system32 directory.
If your phone is already on type "adb shell reboot recovery" in the cmd prompt to get to the bootloader and ready for FASTBOOT and then type "exit" to quit the adb shell.
If not then power on your phone while holding the camera button to get to the bootloader and then press the back button on your handset to get to FASTBOOT mode.
On your cmd prompt type "cd" along with the location of the data.img file (example cd c:\nandroidbackup) to move the command prompt to the backup location.
On the cmd prompt type fastboot flash userdata data.img and hit enter.
You should see "sending" followed by "writing" once complete type fastboot reboot and hit enter.
That should do it.
Now mind you that pushing your data across different builds may not work. If you are trying to restore your data on Hero that was previously saved from Cupcake then you're wasting your time. And vice versa. Always store a backup or two on your pc for quick and easy access in case something doesn't work.
In the event that it does not work simply wipe and follow the above directions to restore.
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
Thanks great thanks mate!!
On the cmd prompt type fastboot flash userdata data.img and hit enter.
Click to expand...
Click to collapse
This step fails for me during the "verifying signature" phase. I believe this is todo with my spl.
Is it possible to use adb to do this? or will the spl still prevent it?
I keep on getting an error when I try to do a nandroid restore. something about adb
Take the .img files out of the nandroid backup folder, toss them into the /tools folder of the SDK, boot into fastboot and manually flash them.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
Just charge your phone. The battery is probably too low. Needs to be >40% for restore or it will throw an adb error (well a suggestion actually).
djmcnz said:
Just charge your phone. The battery is probably too low. Needs to be >40% for restore or it will throw an adb error (well a suggestion actually).
Click to expand...
Click to collapse
Thanks!
10char
When i type the dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash over the clockworkmod, into my command promt it says 'cannot open for read: No such file or directory' and i dont know what im doing wrong.
I mean everything else seemed to workout fine. i downloaded the recovery image it said to save it but it was already saved to my computer after i downloaded it so i dont know if this could be the problem.
Then i used the adb push recovery.img/data command to push the recovery image to my phone, i think this might be where i messed up. After i put in the command a long list of text pops up on the command prompt. It starts out showing 'Android Debug Bridge version 1.0.26' then is followed by a long list of adb commands. Idk know if this is what its supposed to show.
Next i did the adb shell, su, dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 command and that worked fine it said 2560+0 records out, 2560+0 records in 10485760 bites transfered in 0.413 secs and i actually found that file on my sdcard. So i think i did that right.
Next i tried to use the command 'dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096' and like i said earlier it just says 'cannot open for read: No such file or directory'
Lastly i tried the rm /data/recovery.img command and it said rm failed for /data/recovery.img, No such file or directory in the command prompt.
Im sorry i am new at this but i thought i followed the directions perfectly and any help anyone could give me would be greatly appreciated.
First off, before someone else says it, you shouldn't start a new thread for something we already have a topic for. But anyways,
Sounds to me like recovery.img never got pushed to /data. Not sure if its a typo in your post but 'adb push recover.img/data' should be 'adb push recovery.img /data'. The space is important. On your phone use a root file explorer and go to your /data partition and see if recovery.img is there. You may need to either change permissions for /data or just put recovery.img on your sdcard and move it to /data with a root explorer.
Sent from my LG-P925 using Tapatalk
Well im sorry im new to this kind of thing, i didnt want to make anyone mad i just wanted some help and i apologize if ive ticked somone off. How would i change the permissions for the data? And could you tell me how to use the root explorer to put the recovery image in the right place? Again i appreciate any help you can offer.
Is recover.img in the same folder as adb? Because the instructions assume your recovery.img is in the same folder you are working from. So if you have to cd to your adb folder to use adb then recovery.img should be in that folder as well. Look at your cmd window, whatever directory/ folder it says you are in that is where you should put recovery.img.
If you saw a bunch of commands it means the .img did not go through your command did not work. You dont have the recovery.img in /data either put the file on your sdcard and use a root explorer to move it to /data or try the adb push again, you most likely made a typo or something.
You would put recovery.img on your sdcard through your computer. Open root explorer and navigate to your sdcard, long press on the recovery.img select move, go to/ data on the root of the phone, not the one on either sdcard it MUST be /data not /mnt/sdcard/data or anything like that once there paste file to /data and finish up in adb shell.
Alright i copied the recovery image to the /data folder and finished up in command prompt and everything worked out like it was supposed to. what was i supposed to do next to put it into cwm recovery mode? I held power, volume down, 3d button but i just went into normal recovery mode. then i went to rom manager to try and put it into cwm recovery that way but it just rebooted my phone. And when i went back into the /data folder i couldnt find the recovery image there anymore and i did a search on my root explorer and couldnt find it anywhere.
Hold vol down + 3D + power when lg logo appears release power but keep vol down +3D held down until recovery pops up. If you still don't boot into cwm try flashing recovery.img again. Do NOT use rom manager at all to install cwm on this phone.
Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.
powers.jereme said:
Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.
Click to expand...
Click to collapse
rm is the command to remove. So yes, recovery.img is supposed to disappear after that command. Put it back on /data and run the whole process from the CWM thread again making sure you do every step. Sounds like you may have accidentally skipped a step.
Sent from my LG-P925 using Tapatalk
Double post.
Ugh...keep selecting quote instead of edit on Tapatalk...Triple post...
Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks
powers.jereme said:
Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks
Click to expand...
Click to collapse
Yea just do it all again. Worst case is you flash cwm back over cwm
Sent from my LG-P925 using Tapatalk
I got it to work Urabewe was right i just needed to put the recovery image in the correct folder and everything worked perfect. Thanks guys.
Hey all,
A few of us are attempting to put together a solution to unlock the bootloader of the N4 without wiping, and we need your help.
We need dumps of the misc partition of the N4 both in a bootloader locked and unlocked state. I've explained below what we need and how to do it.
Note, this will require you to re-lock and unlock your bootloader, (which will cause your data to be wiped) so do a nandroid and copy it off your device for a later restore.
Novice instructions:
1) You need to start off with an unlocked bootloader.
2) Boot into fastboot mode and plug into your PC.
3) If you don't have ADB and fastboot on your PC, download the attachment from this post and extract the contents to a directory.
4) If you don't have CWM or TWRP flashed, download CWM from here and save as cwm.img in the same directory as in step 3.
5) Open a command prompt in the same directory as in step 3 (i.e., hold the shift key and right click in a blank space in that folder).
6) Flash CWM: fastboot flash recovery cwm.img
7) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
8) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
exit
adb pull /sdcard/misc-unlocked.img
adb reboot bootloader
fastboot oem lock
fastboot reboot-bootloader
9) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
10) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
exit
adb pull /sdcard/misc-locked.img
11) Now you have two files (misc-unlocked.img and misc-lock.img) in the directory you created in step 3. Zip them up and upload them in this thread.
12) Your bootloader is now locked. If you want it unlocked, unlock it using the normal method of "fastboot oem unlock" which will wipe your data, but all you have to do is restore your nandroid, and you will be back to where you started.
Advanced user instructions:
1) Start with an unlocked bootloader
2) Dump the misc partition: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
3) Lock your bootloader
4) Dump the misc partition again: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
5) Upload the files to this thread.
For advanced users only (this has not yet been tested), if you want, you can try flashing the unlocked misc partition:
Code:
adb shell "dd if=/sdcard/misc-unlocked.img of=/dev/block/mmcblk0p19"
to see if it will unlock your device without wiping. But as I said, this has not been tested yet, so do the last step at your own risk.
Edit: nvm
Here is the dump. Thanks for your work.
KyraOfFire said:
Does it wipe sdcard? It need to know if I have to copy everything to the computer.
Thanks,
Click to expand...
Click to collapse
To be safe, you should copy everything to your computer.
Our theory is, once you lock your bootloader with "fastboot oem lock", you should be able to unlock it again without wiping anything just by flashing the misc partition that you dumped when your device was unlocked.
So, the steps themselves will not wipe anything. But, if you use "fastboot oem unlock" to unlock your bootloader (once you have completed all the steps), then it will wipe everything including /sdcard. If you use the command in the "advanced users instructions", the idea is that it won't wipe anything.
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
Great thanks!
Did you try re-flashing the unlocked misc.img (while you were locked) to see if it unlocked?
I can't flash the misc-unlocked.img
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell "dd if=/sdca
rd/misc-unlocked.img of=/dev/block/mmcblk0p19"
dd: can't open '/sdcard/misc-unlocked.img': No such file or directory
Click to expand...
Click to collapse
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
KyraOfFire said:
I can't flash the misc-unlocked.img
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
Click to expand...
Click to collapse
Try this:
1) Copy the file to /sdcard
2) Reboot into CWM
3) Type in the command
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
KyraOfFire said:
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
Click to expand...
Click to collapse
Not sure why your directories are messed up.
Find where the file is saved, and use that path for the "if" part of the command. For example, if it is saved in /storage/emulate/0, then use this command:
adb shell "dd if=/storage/emulate/0/misc-unlocked.img of=/dev/block/mmcblk0p19"
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
adb shell "dd if=/system/misc-unlocked.img of=/dev/block/mmcblk0p19"
Click to expand...
Click to collapse
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
KyraOfFire said:
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
Click to expand...
Click to collapse
Great, thanks for the confirmation.
Very strange that /sdcard did not work. It worked fine on mine, but we will certainly look into it.
Thanks again.
Glad I could help. Now folks have less things to worry about when they decide to root
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q? If so, I don't think that will help us too much. I dumped mine when I was on JOP40C (and I will do so again with JOP40D). If you do upgrade, then new dumps would be appreciated.
By the way, could you list the following from your device:
ROM version:
Bootloader:
Radio:
Thanks.
EDIT: If you want to follow the progress, you can have a look at this thread.
efrant said:
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q?
Click to expand...
Click to collapse
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
KyraOfFire said:
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
Click to expand...
Click to collapse
Hmm. Thanks for the offer, but don't bother going through the hassle. If you are already running JOP40D, then it should be ok. Weird that your dump had JVP15Q in it. I'll wait until a couple of the other guys have a look at it (in this thread).
For science
KyraOfFire said:
For science
Click to expand...
Click to collapse
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
osm0sis said:
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
Click to expand...
Click to collapse
I have a feeling that it has something to do with history/logging. My N4 came with JOP40C out of the box, and I would bet that KyraOfFire's came with JVP15Q out of the box.
So i kind of got a situation here , i originally wanted to be rooted and have my nexus 6 non encrypted so i had unlocked and rooted my phone. After i ran the "./fastboot erase userdata" command i flashed the custom recovery again and booted into it. From there i thought i would be able to "./adb sideload" a stock custom rom non encrypted but for some reason i was having difficulty running that command. My laptop was not seeing the phone, so after about 30 min of playing around with it trying to get it to work i figured id just start over fresh. From this point i dont have an OS installed so i knew i would have to download the appropriate files for the nexus 6 so i did. I tried both methods, the "./flash-all.sh" command and flashing everything one by one rebooting the bootloader in between flashes and still kept getting this same error
fastboot(1561,0xa04aa1d4) malloc: *** mach_vm_map(size=1681293312) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679613116 bytes
error: update package missing system.img
and now im stuck in fastboot mode at least, but cannot revert back to stock unless im missing something here. Can someone help please
AnthonyAldrete said:
So i kind of got a situation here , i originally wanted to be rooted and have my nexus 6 non encrypted so i had unlocked and rooted my phone. After i ran the "./fastboot erase userdata" command i flashed the custom recovery again and booted into it. From there i thought i would be able to "./adb sideload" a stock custom rom non encrypted but for some reason i was having difficulty running that command. My laptop was not seeing the phone, so after about 30 min of playing around with it trying to get it to work i figured id just start over fresh. From this point i dont have an OS installed so i knew i would have to download the appropriate files for the nexus 6 so i did. I tried both methods, the "./flash-all.sh" command and flashing everything one by one rebooting the bootloader in between flashes and still kept getting this same error
fastboot(1561,0xa04aa1d4) malloc: *** mach_vm_map(size=1681293312) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679613116 bytes
error: update package missing system.img
and now im stuck in fastboot mode at least, but cannot revert back to stock unless im missing something here. Can someone help please
Click to expand...
Click to collapse
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
funny i just did this exact same thing like you instructed and was about to reply to this post saying i resolved it hahah. Thanks anyways though =), i dont understand why i was getting that though because i had every file in the same place
No worries glad you got it working
qnc said:
No worries glad you got it working
Click to expand...
Click to collapse
Also found out that you Dont do the ./fastboot erase userdate command because it puts 0s in and leaves the phone unbootable which was my root cause for my phone being stuck. Instead, after flashing the boot.IMG you do the ./fastboot partition userdata instead and it will do a factory reset and when booting it will not encrypt the phone.
qnc said:
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
Click to expand...
Click to collapse
And I was having the same issues executing the flash all command too until I opened the command in a text editor and for every command put the "./" in front and was able to execute it but this is the first time I've gotten an error. My nexus5 worked with this command no problem
worked for me but still could not decrypt
qnc said:
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
Click to expand...
Click to collapse
so all of this worked for me and its back up and running, but my phone still says that its encrypted