[Q] Can't flash stock image. - Nexus 4 Q&A, Help & Troubleshooting

Hello guys!
I downloaded the factory image for my device.
I'm currently running PA 5 Alpha 2 and Hellscore, using TWRP, rooted and unlocked of course.
I'm trying to flash the factory image with no success, I got "boot.img file not found" error.
I just edited the flash-all.bat file and deleted the -w because I want to keep my data.
Any ideas? What am I doing worng?

Every file must be in the same folder otherwise it wont work.

CCody said:
Every file must be in the same folder otherwise it wont work.
Click to expand...
Click to collapse
So I have to extract the .zip file in the folder after the first exctract?

Please read this thread. I think all your questions will be answered there.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

Related

Cant Update to 4.2.2

Hey guys,
my phone just informed me that i could update to 4.2.2 but i am/was running a rooted n4 with stock rom and franco kernel. Franco posted how to properly upgrade to 4.2.2 (flash stock kernel, remove power.xxxx.so (cant remember the name atm)and rename power.xxxx.so.fbak, then reboot and flash zip) but it didnt work for me. i flashed stock kernel and removed the power file + renamed the backup power file but when i try to flash the update.zip im getting an error that looks like this:
assert failed apply_patch_check( /system/lib/hw/power.default.so
Error in /sdcard/update.zip (the .zip i downloaded right from google servers) (status 7)
what could the reason be? id appreciate any help!
and yes....i did look up the other threads that had similar problems but that didnt fix it.
thanks in advance!!
Your "/system/lib/hw/power.xxxxx" file didn't pass the check.
I guess the original one was overwritten with a custom one before being renamed, by a different kernel install.
well i did exactly what was stated in the guide:
1. Download stock kernel from here:
forum.xda-developers.com/show....php?t=2024982
2. Flash it in recovery.
3. Boot into android.
4. Go from root explorer to system/lib/hw and
i) Delete power.msm8960.so
ii) Remove .fkbak extension from power.msm8960.so.fkbak so it looks like, power.msm8960.so
iii) Fix the permissions to rw-r--r--
5. Reboot
i even tried it with the .so file from here: http://forum.xda-developers.com/showthread.php?t=2147427
nick2knife said:
well i did exactly what was stated in the guide:
1. Download stock kernel from here:
forum.xda-developers.com/show....php?t=2024982
2. Flash it in recovery.
3. Boot into android.
4. Go from root explorer to system/lib/hw and
i) Delete power.msm8960.so
ii) Remove .fkbak extension from power.msm8960.so.fkbak so it looks like, power.msm8960.so
iii) Fix the permissions to rw-r--r--
5. Reboot
i even tried it with the .so file from here: http://forum.xda-developers.com/showthread.php?t=2147427
Click to expand...
Click to collapse
i dunno, it should pass the check.
you did unpack the .rar file ? and not rename it.. just checking
afnsteer you
yeah did :/
i flashed cwm now instead of teamwin and still the same error but cwm now also provides some hash numbers. are they any helpful?
nick2knife said:
yeah did :/
i flashed cwm now instead of teamwin and still the same error but cwm now also provides some hash numbers. are they any helpful?
Click to expand...
Click to collapse
You need to reflash the system image. That's where it is failing.
Read here: http://forum.xda-developers.com/showthread.php?t=2010312
Specifically question #1 in the Q&A Section. Then look at Section C.
Try this one.
I got it from a 4.2.1 rom.zip i have had on my desktop for 2 months.
El Daddy said:
You need to reflash the system image. That's where it is failing.
Read here: http://forum.xda-developers.com/showthread.php?t=2010312
Specifically question #1 in the Q&A Section. Then look at Section C.
Click to expand...
Click to collapse
reflash the whole system? well im not a developer but thats surely not the fault. maybe im just using the wrong .so file.
and which Q&A Section are u referring to?
@mean: isnt that exactly the same one as on the other thread?
so heres the exact error msg:
assert failed: apply_patch_check ("system/lib/hw/power.deafault.so", "83172fb........." , "480b896dff..........")
E: Error in /sdcard/...... (the update zip.file)
(Status 7)
Installation aborted.
nick2knife said:
reflash the whole system? well im not a developer but thats surely not the fault. maybe im just using the wrong .so file.
and which Q&A Section are u referring to?
@mean: isnt that exactly the same one as on the other thread?
Click to expand...
Click to collapse
It seems like you are having trouble locating the exact files the need to be replaced. An easy solution is to re-flash the system.img in fastboot. You won't lose any data.
The Q&A section at the bottom of the OP.
any zip flashable version of the system.img around? couldnt find that one
I am having this exact issue. Any luck?
Sent from my Nexus 4 using xda premium
after some trying i got sick of it and just flashed a nandroid backup. but now im facing another issue.... im using wugfresh's kit and usually that kit performs every reboot into bootloader etc. itself but somehow it doesnt :/ i manually have to shut down / start the fastboot mode then it works. but i really dont like that solution.... just looks like smth is broken to me any idea abotu that?
That did the trick
Have same issue as OP'er. Flashing system.img via fastboot did the trick. I was then able to install the OTA no issues. No data loss.
El Daddy said:
It seems like you are having trouble locating the exact files the need to be replaced. An easy solution is to re-flash the system.img in fastboot. You won't lose any data.
The Q&A section at the bottom of the OP.
Click to expand...
Click to collapse

Returning to stock, cant flash system, now wont boot from backups

OK, so i'm returning my N4 to Stock from Dirty Unicorns as i am possibly selling it. i Downloaded a copy of stock 4.2.2 from Google and extracted the images from the .tgz as instructed in this thread.
i re flashed the bootloader and radio fine, i had changed the radio previously to fix signal issues, but when i try to flash system it hangs on writing.
now when i boot into my recovery and restore an old backup it doesn't get past the boot screen.
any help with this would be really appreciated
cheers
Airhn
Make sure you are in the correct folder location when flashing. Depending how you unzipped the tar, your system, boot, userdata and recovery img files might be in another folder. cd your way to the correct location then it should work.
I shift+right click to open a cmd prompt in the folder. I can send the files to the phone no problem but it hangs when trying to write it
Sent from my C6903 using xda app-developers app
Airhn said:
I shift+right click to open a cmd prompt in the folder. I can send the files to the phone no problem but it hangs when trying to write it
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Maybe switch cables and USB ports to make sure it's not one of those things. Check MD5 sum of the tar if you didn't before you started?
hi thanks for the help Jawmail. i managed to get it working. i ended up loading a odexed jdq39 rom from the forums and then forcing an ota update.
still no idea why it wouldnt flash the sysem image originally though
:good:

Nexus 7 2012 trwp and cwp and side load android 4.4 zip flash error

Hello xda, I unfortunately have an issue with flashing the android 4.4 factory zip. I know there are many different problems including the "status 7" issue which is ticking of some people. But I have a different error,
no md5 file found..
verifying current system..
"/system/app/Currents.apk" has unexpected contents.
E: Error executing updater binary in zip...
Can someone please explain this error and the solution for me? I have tried everything I could find, I'm rooted with trwp and I even tried cwp and adb side load to flash the android 4.4 factory zip but the same error always appears.
Someone help me.
I must of deleted Google currents by accident. And I couldn't even flash the android 4.3 factory zip without getting the same error.
Sent from my Nexus 7 using XDA Premium HD app
Please help guys
Sent from my Nexus 7 using XDA Premium HD app
the same as me
GoldenNexus7 said:
Please help guys
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I also receive update via OTA but it still error, so i try adb sideload but the error is
Code:
"/system/app/Currents.apk" has unexpected cotents
Error (status 7)
Installation aborted
Use a file manager to check to see if you have the Currents.apk in the /system/app directory, if it is missing just copy the attached one to /system/ap and change the permissions to rw-r-r to match the other files. The attached Currents.apk is from the JWR66V file system.
GMPOWER said:
Use a file manager to check to see if you have the Currents.apk in the /system/app directory, if it is missing just copy the attached one to /system/ap and change the permissions to rw-r-r to match the other files. The attached Currents.apk is from the JWR66V file system.
Click to expand...
Click to collapse
Not sure how to change permissions but I'll try that thanks.
Sent from my Nexus 7 using XDA Premium HD app
GMPOWER said:
Use a file manager to check to see if you have the Currents.apk in the /system/app directory, if it is missing just copy the attached one to /system/ap and change the permissions to rw-r-r to match the other files. The attached Currents.apk is from the JWR66V file system.
Click to expand...
Click to collapse
That worked well but then when I tied to flash it again in both twrp and cwm recovery it gives a new error,
"/System/bin/app-process" has unexpeted contents
E:error in /tmp/update.zip
PLEASE HELP ME ON THIS,SOMEONE SAID THIS MIGHT HAVE SOMETHING TO DO WITH XPOSED AND I SHOULD DELETE FRAMEWORK FIRST. not sure what he meant by remove framework.
Sent from my Nexus 7 using XDA Premium HD app
GoldenNexus7 said:
That worked well but then when I tied to flash it again in both twrp and cwm recovery it gives a new error,
"/System/bin/app-process" has unexpeted contents
E:error in /tmp/update.zip
PLEASE HELP ME ON THIS,SOMEONE SAID THIS MIGHT HAVE SOMETHING TO DO WITH XPOSED AND I SHOULD DELETE FRAMEWORK FIRST. not sure what he meant by remove framework.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
For permissions, if using ES File Explorer, long press on the app, press “more” in the bottom right corner, select “Properties,” then press the change box that is next to permissions. If you are using Root Explorer, long press on the file, and then select “Permissions.”
If you continue to receive errors, I recommend downloading the following stock JWR66V ROM, HERE. You can then pick out each file that you need, or you can just dirty flash it to restore all the needed files.
Attached is that file, you just need to unzip the file, and then change the permission on the file too rwxr-xr-x.
GMPOWER said:
For permissions, if using ES File Explorer, long press on the app, press “more” in the bottom right corner, select “Properties,” then press the change box that is next to permissions. If you are using Root Explorer, long press on the file, and then select “Permissions.”
If you continue to receive errors, I recommend downloading the following stock JWR66V ROM, HERE. You can then pick out each file that you need, or you can just dirty flash it to restore all the needed files.
Attached is that file, you just need to unzip the file, and then change the permission on the file too rwxr-xr-x.
Click to expand...
Click to collapse
Alright, thank you , I'll try to flash the ROM but if the same error appears again when I flash it I'll let you know.
Sent from my Nexus 7 using XDA Premium HD app
I have similiar issue on 2012 3g, stock, locked, no root, stock recovery. Did a side load, but during system verification i got "/system/media/bootanimation.zip" has unexpected contents. Error in /sdcard/0/ update.zip. (Status 7)". I'm on jrw66y tried to reflash, successfuly, tried 4.4 ota again, same error. I recived two OTA's for 4.3 and had no issues. I can understand errors for apks, but for a stock bootanimation i just can't... Does someone have a idea what next? Thanks in advance.
Востани Сербие, востани царице
GMPOWER said:
For permissions, if using ES File Explorer, long press on the app, press “more” in the bottom right corner, select “Properties,” then press the change box that is next to permissions. If you are using Root Explorer, long press on the file, and then select “Permissions.”
If you continue to receive errors, I recommend downloading the following stock JWR66V ROM, HERE. You can then pick out each file that you need, or you can just dirty flash it to restore all the needed files.
Attached is that file, you just need to unzip the file, and then change the permission on the file too rwxr-xr-x.
Click to expand...
Click to collapse
OK I reinstalled the old android 4.3 factory zip and then updated to the second 4.3 update and then the 4.4 , when I update I'm quarter way, it said error, boot animation has unexpected contents, I need the old boot animation back because when I turn on my nexus it doesn't have the traditional "x" boot animation anymore. I guess this new boot animation is from the JWR66V factory zip for rooted devices you gave me from before. Can you please give me the old boot animation file, I hope this is the only error I'm gonna get.
Sent from my Nexus 7 using XDA Premium HD app
Now You have same issue as i do. I tried to dig it from several roms but in vain - couldn't find appropriate. Next question is if i get that file, can i put it to /system/media w/o root. I think i can't. Anyway @GoldenNexus7, if You aquire that bootanimation pls notice me, I'll notice You if I get it first.
Востани Сербие, востани царице
I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk
slif24 said:
I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
Will the flashing system.img and boot.img wipe the data?
Unlocking bootloader wipes data. Flashing system and boot won't . But, sometimes device won't boot if data is not wiped. Now, as i wage lurking around for a solution or rooting and wipe data, I'm much closer to 2nd solution.
Востани Сербие, востани царице
slif24 said:
I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
I installed the OTA and I don't know what happened, I got stuck on the Kitkat logo screen (boot animation). I am unlocked and have CWM installed. Now I can't get past that screen. I can access adb and also CWM recovery.
I am also planning to try this method now. Is it okay if I have CWM Recovery installed? Do I have to remove it in order for this to work?
Loreane Van Daal said:
Now You have same issue as i do. I tried to dig it from several roms but in vain - couldn't find appropriate. Next question is if i get that file, can i put it to /system/media w/o root. I think i can't. Anyway @GoldenNexus7, if You aquire that bootanimation pls notice me, I'll notice You if I get it first.
Востани Сербие, востани царице
Click to expand...
Click to collapse
Not sure if it would make a big difference, it will probably give me a different error once I try to update to 4.4 again.
SIGH
Sent from my Nexus 7 using XDA Premium HD app
slif24 said:
I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
Which factory image should I download? Is it the kit Kat one?
Sent from my Nexus 7 using XDA Premium HD app
alfred_heaven said:
Will the flashing system.img and boot.img wipe the data?
Click to expand...
Click to collapse
No. "userdata.img" wipes your data. I had that fear, but no problem.
hardikrajgor123 said:
I installed the OTA and I don't know what happened, I got stuck on the Kitkat logo screen (boot animation). I am unlocked and have CWM installed. Now I can't get past that screen. I can access adb and also CWM recovery.
I am also planning to try this method now. Is it okay if I have CWM Recovery installed? Do I have to remove it in order for this to work?
Click to expand...
Click to collapse
The Factory Image include 4 files: boot.img, system.img, userdata.img (this wipes your data) and recovery.img (if you use a Custom Recovery, you don't have to flash this, if you don't, you must to flash it. In addition, your recovery isn't important. You only have to reboot your device in bootloader mode (Turn on pressing Power+VolUp+VolDown) and connect it to your PC. Finally you have tu follow the steps. Simply and clear. Your device has been updated.
GoldenNexus7 said:
Which factory image should I download? Is it the kit Kat one?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
You must to download KitKat image.
nakasi (Wi-Fi): https : // dl. google. com /dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
nakasig (3G): https : // dl. google. com /dl/android/aosp/nakasig-krt16s-factory-1e882585.tgz
Erase spaces. I can't publish links.
Hope this help you
slif24 said:
No. "userdata.img" wipes your data. I had that fear, but no problem.
The Factory Image include 4 files: boot.img, system.img, userdata.img (this wipes your data) and recovery.img (if you use a Custom Recovery, you don't have to flash this, if you don't, you must to flash it. In addition, your recovery isn't important. You only have to reboot your device in bootloader mode (Turn on pressing Power+VolUp+VolDown) and connect it to your PC. Finally you have tu follow the steps. Simply and clear. Your device has been updated.
You must to download KitKat image.
nakasi (Wi-Fi): https : // dl. google. com /dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
nakasig (3G): https : // dl. google. com /dl/android/aosp/nakasig-krt16s-factory-1e882585.tgz
Erase spaces. I can't publish links.
Hope this help you
Click to expand...
Click to collapse
For some reason I lost root, but my nexus 7 is still unlocked so I can root again using root tool kit.
Sent from my Nexus 7 using XDA Premium HD app
GoldenNexus7 said:
For some reason I lost root, but my nexus 7 is still unlocked so I can root again using root tool kit.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have the same problem. I've tried to flash it from Custom Recovery (TWRP) and no root. I'm investigating that. I post if I found a solution. Recovery maybe the guilty.
Enviado desde mi Galaxy Nexus mediante Tapatalk

[Q] Need unmodified JWR66Y build.prop file

Hello,
I kind of messed up with my nexus 4's build.prop file and forgot to back up
Will someone be kind enough and upload their unmodified build.prop file (JWR66Y).
Thanks.
avi619 said:
Hello,
I kind of messed up with my nexus 4's build.prop file and forgot to back up
Will someone be kind enough and upload their unmodified build.prop file (JWR66Y).
Thanks.
Click to expand...
Click to collapse
Go to https://developers.google.com/android/nexus/images and download the 4.3 factory image, then extract the build.prop file
Desno365 said:
Go to https://developers.google.com/android/nexus/images and download the 4.3 factory image, then extract the build.prop file
Click to expand...
Click to collapse
How do I extract the .img file? 7zip does not seem to work.
avi619 said:
How do I extract the .img file? 7zip does not seem to work.
Click to expand...
Click to collapse
I forgot the img file sorry.
I will upload it for you, wait a moment
Desno365 said:
Go to https://developers.google.com/android/nexus/images and download the 4.3 factory image, then extract the build.prop file
Click to expand...
Click to collapse
Desno365 said:
I forgot the img file sorry.
I will upload it for you, wait a moment
Click to expand...
Click to collapse
I found a tool here and extracted the image via linux reader. Replaced the build.prop file and when I restarted my phone it went completely blank.
The google logo also did not show. I think I bricked it
avi619 said:
I found a tool here and extracted the image via linux reader. Replaced the build.prop file and when I restarted my phone it went completely blank.
The google logo also did not show. I think I bricked it
Click to expand...
Click to collapse
Don't worry you didn't brick it, how do you replace the build.prop file?
Desno365 said:
Don't worry you didn't brick it, how do you replace the build.prop file?
Click to expand...
Click to collapse
ES File Manager. My phone is rooted.
avi619 said:
ES File Manager. My phone is rooted.
Click to expand...
Click to collapse
Did you set the correct permissions (rw-r--r--)? Maybe this is the problem.
If your phone doesn't boot, restore a nandroid backup or flash a ROM
Desno365 said:
Did you set the correct permissions (rw-r--r--)? Maybe this is the problem.
If your phone doesn't boot, restore a nandroid backup or flash a ROM
Click to expand...
Click to collapse
No I did not set those permissions. Just replaced the build.prop file. I don't know what nandroid backup is but I have TWRP installed.
PS: The phone is still on the blank screen.
avi619 said:
No I did not set those permissions. Just replaced the build.prop file. I don't know what nandroid backup is but I have TWRP installed.
PS: The phone is still on the blank screen.
Click to expand...
Click to collapse
If you have a ROM in sdcard flash it, if you haven't you have to flash a ROM with adb sideload or a factory image with fastboot (the factory image will erase your data!)
Desno365 said:
If you have a ROM in sdcard flash it, if you haven't you have to flash a ROM with adb sideload or a factory image with fastboot (the factory image will erase your data!)
Click to expand...
Click to collapse
Thanks, I m going to flash 4.4 stock rom from http://forum.xda-developers.com/showthread.php?t=2535728
Alright, quick update:
I used adb sideload to flash the rom from my above post. Worked like a charm, and I have Kitkat running with root. Also, no data was lost.
First thing I am gonna do now is backup my build.prop and data
Thanks for the help.
Cheers.
avi619 said:
Alright, quick update:
I used adb sideload to flash the rom from my above post. Worked like a charm, and I have Kitkat running with root. Also, no data was lost.
First thing I am gonna do now is backup my build.prop and data
Thanks for the help.
Cheers.
Click to expand...
Click to collapse
Great!
I made the same mistake before, when I hide the softkeys
just for reference, you could have fixed it easily, just by using TWRP's File manager:
1. Mount System
2. Replace with the original Build.prop inside the system directory
3. Click the file -> Change file permissions chmod 775

Can't Update to 4.4

I got a Nexus 4 today. It is currently on 4.3. I've rooted the phone and installed TWRP recovery. I tried flashing the 4.4 zip and I get a failed message. I can't figure out why. Can someone help?
Yes.
Don't even bother trying to figure out why. You just got the phone. Flash the factory images for 4.4.2.
Not sure why you would get a phone and root it / modify it first, instead of just updating.
But anyways. Your bootloader is already unlocked. Flash factory images. Reroot and do whatever you want after.
albundy2010 said:
Yes.
Don't even bother trying to figure out why. You just got the phone. Flash the factory images for 4.4.2.
Not sure why you would get a phone and root it / modify it first, instead of just updating.
But anyways. Your bootloader is already unlocked. Flash factory images. Reroot and do whatever you want after.
Click to expand...
Click to collapse
It wouldn't update. I thought about doing that first but it said the update was "waiting to download". Where can I get the factory image to 4.4.2?
ILowry282 said:
It wouldn't update. I thought about doing that first but it said the update was "waiting to download". Where can I get the factory image to 4.4.2?
Click to expand...
Click to collapse
The "factory image" from google is a tgz file. Not a zip file. WTF?
Factory images are flashed with fastboot, not a custom recovery or stock recovery.
Extract that file. Take everything that comes out and put it in your directory that has fastboot in it.
Put the phone in fastboot..... Run the flashall. Bat
That will wipe everything off the phone and put stock on it. If you don't want it to wipe your data ( not sure why you wouldn't since you just got it and probably don't have all your junk on it...) you can edit that script by removing the - w part in it.
It's very simple.
albundy2010 said:
Factory images are flashed with fastboot, not a custom recovery or stock recovery.
Extract that file. Take everything that comes out and put it in your directory that has fastboot in it.
Put the phone in fastboot..... Run the flashall. Bat
That will wipe everything off the phone and put stock on it. If you don't want it to wipe your data ( not sure why you wouldn't since you just got it and probably don't have all your junk on it...) you can edit that script by removing the - w part in it.
It's very simple.
Click to expand...
Click to collapse
Haha! Simple maybe for you. What exact commands to I type in terminal (I have a mac)? I know all commands need to start with ./fastboot-mac
ILowry282 said:
The "factory image" from google is a tgz file. Not a zip file. WTF?
Click to expand...
Click to collapse
Unzip the file with 7zip. Run the flash -all file. Let it do its magic.
Sent from my Nexus 4 using Tapatalk
badboy47 said:
Unzip the file with 7zip. Run the flash -all file. Let it do its magic.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I get a text file.
It's a script which is text. If it doesn't run automatically in terminal or bash ( whatever the hell they call it these days on osx) then make it run with it
As long as your fastboot file itself is there it will run.
I think you need to be completely stock (other than unlocked bootloader) to receive OTA updates.
I was on CM10.2 and needed to return the phone to stock. I flashed back to stock 4.3 and was able to update to 4.4.2 with no problems.

Categories

Resources