So I currently have a 4.3 Purity Rom Nexus 4 and wish to do a fresh update to 4.4 (s). I'm in Fastboot and am unlocked.
I downloaded the factory image from Google, extracted, took the .tar file and dropped it in the 'google factory image to flash' folder in 'Unified Android Toolkit"... As I selected to flash my factory image, everything loaded fine and checked out on Skipsoft, it even flashed the radio with no fuss, but each time I try it always stops and says: "error: cannot opening system.img"
Is there something I'm doing wrong here?
raysalmon said:
So I currently have a 4.3 Purity Rom Nexus 4 and wish to do a fresh update to 4.4 (s). I'm in Fastboot and am unlocked.
I downloaded the factory image from Google, extracted, took the .tar file and dropped it in the 'google factory image to flash' folder in 'Unified Android Toolkit"... As I selected to flash my factory image, everything loaded fine and checked out on Skipsoft, it even flashed the radio with no fuss, but each time I try it always stops and says: "error: cannot opening system.img"
Is there something I'm doing wrong here?
Click to expand...
Click to collapse
I suggest you to try the wugfresh nexus toolkit , I found it to be more easy to use most of the time than skipsoft's .You don't have to extract the factory image while using wugfresh ,and it is normal to see two error like missing img ..I don't remember the exact error but in the process wugfresh toolkit mentions that.
Related
Hi everyone!
I have come to a slight problem, trying to flash an android L preview port for my N4. I rooted properly, but when CWM asked me if I wanted to fix boot, I unfortunately replied with Yes. After I lost my root, I tried rerooting, when I accidently selected a wipe all function. So, now I have no rom Just a CWM recovery.
I have downloaded a tar.gz factory image file for N4 (4.4.4) and tried adb pushing to the device. The transfer is successful, but when I try to install it from the sdcard (cwm), it reports failure. I googled and read a lot, but not much seems to be helping.
I am using a Mac, btw.
Thanks in advance!!
You cant install a .tgz via recovery. Instead you should download a flashable .zip of your rom. Try this.
CCody said:
You cant install a .tgz via recovery. Instead you should download a flashable .zip of your rom. Try this.
Click to expand...
Click to collapse
Yes, I keep trying to do that but without success.
O tried factory kitkat zip and I tried an L android I downloaded.
Could you provide me witha link to a flashable zip?
Then tell me what you want. A factory image or a custom rom. I would recommand you cyanogenmod. Downloaf the zip for your device. http://www.cyanogenmod.org/
To install stock do this:
Extract .tar.gz (using 7Zip) until you come up with folder named "occam-xxxxx"
Copy the files within it to your fastboot.exe folder
Reboot into boot-loader
Hit flash-all.bat
But you may download latest CM from https://download.cyanogenmod.org/?device=mako and install it via flash .zip in CWM (however I recommend Philz Touch Recovery)
I'd like to flash Nexus 4 port for Android L. I had downloaded android l zip file but when I try to flash it, installation aborted keeps popping up.
And once again, people keep mentioning fastboot.EXE and run a batch file, but again... I am on a Mac. It would mean a great lot if the instructions given were for a mac.
Thanks!
Here's what I did:
1. Install Wugfresh's NRT (search online for it)
2. Download the factory image from the Google website
3. Connect your phone in Recovery mode
4. Open NRT and let it update if it has to
5. Hit "Flash stock + Unroot"
6. The usage is clearly explained at every stage. You should ideally have no problems restoring your phone to a working state. Your data however is most likely lost. Sorry.
(PS: I don't usually recommend toolkits because they take away the fun in messing with the phone manually, but sometimes it becomes necessary to use them. This is one of those times )
I tried flashing CM 11 snapshot M8 release, but it gave me status 7, install failed. I tried to fix it by removing asserts and rezipping, and failed again, without a status.
I am trying to revert back to stock now, nothing else works, and neither will this, so it seems.
EDIT:
I flashed new bootloader and new radio, but when I tried to flash a stock rom, it failed again.
I don't know what to do anymore, I feel like throwing a phone against the wall and just getting a Nexus 5.
to flash the n4 L port, download the zip in the port thread and flash it in recovery. that's all. wipe before you flash.
there was no official L preview for the n4, so you can't flash it from the factory IMG, that's for the nexus 5.
simms22 said:
to flash the n4 L port, download the zip in the port thread and flash it in recovery. that's all. wipe before you flash.
there was no official L preview for the n4, so you can't flash it from the factory IMG, that's for the nexus 5.
Click to expand...
Click to collapse
Cwm reports unable to mount... i updated to 6.0.5.0 cwm, changed to twrp even using fastboot... But nothing is helping.
Hello guys,
I own a nexus 4
i would require help in ota issues.
previously when google had launched the 4.4.4 update
my device showed me an error of code 7
the android with exclamatory mark stating update failed
then i had contacted google regarding the issue they told me to flash factory images
but inspite of backup i lost few data
now the same thing is happening with 5.0
i got notification saying update avilable and after download and install twice i get an error code 7
in 4.4.4 issue my device was non rooted with boot loader unlocked
in 5.0 issue my device is rooted with boot loader unlocked
i am on completely stock android only rooted no tweaks or changes to the rom
now if i flash factory image i loose my data for sure.
if at all i backup entire rom in cwm custom recovery
then move that .zip created by backup to my pc
then flash factory image
custom recovery then restore data
will it work
i am very concerned about my phone data as well as the ota
please guys need help
thanks and regards
-AK
hey i had also some error 7 problem.
this helped me.
http://forum.xda-developers.com/showpost.php?p=56916654&postcount=3344
The link says
I resolved the fingerprint Problem (set_metadata_recursive: some changes failed) by flashing the factory Images without the Wipe command
1. Download Factory IMG for Android 5.0 for*Nexus*4
2. Unpack the file and open the folder (make sure the zip file is in the same folder as your ADB/Fastboot folder)
3. Open the flash-all with an EDITOR (flash-all.sh for Linux or Mac flash-all.bat for Windows
4. Remove the -w option from the last line: The line should now read:*
fastboot update image-occam-lrx21t.zip
5. Reboot your phone to the bootloader and execute the flash-all file
But if I edit -w
And flash it
Will it remove all my data
Or its just a kind of ota
Also
Yesterday I tried to backup from twrp
And flashed all of lollipop without editing
Then flashed twrp and selected to restore only data
When rebooted it got into boot loop
Thanks bro fixed the issue with the help of that link without losing my data
Hi,
Currently on build LRX21P. (5.0 for the 2012 Nexus 7 wifi)
I recently received a notification that an OTA update to 5.0.2 was available.
When I tried to install it, the tablet would reboot into TWRP and stay there.
It looks like the update installed a file /cache/a6645eee89af34f58db74f6a1ad93fe400fcfc7b.signed-nakasi-LRX22G-from-LRX21P.a6645eee.zip but TWRP can't install it. I have attached the logfile from TWRP.
Any suggestions? I would much rather do an upgrade than wipe in order to install the 5.0.2 image.
Thanks!
Download the factory image from Google's website. Extract the system.img file from the zip. Use fastboot to flash: "fastboot flash system system.img". It worked fine for me.
On other devices I have been advised to NOT take an OTA if I had a custom recovery, even with a stock ROM. So one had to flash back to stock recovery before taking the OTA.
I have been trying to see if the same is true for the Nexus 7 with Android 5.x, but haven't found a definitive answer yet.
jbaumert said:
Download the factory image from Google's website. Extract the system.img file from the zip. Use fastboot to flash: "fastboot flash system system.img". It worked fine for me.
Click to expand...
Click to collapse
That worked perfectly. (used WUG toolkit to flash).
Thanks!
I have got a very different situation here. I was using 4.4.4 (KITKAT). I skipped 5.0.0 (LOLLIPOP) OTA update cause there were lots of rumours about the device going into a bootloop. Last week I DIRECTLY (HOW IS THIS EVEN POSSIBLE??) got a "5.0.1" OTA. I mistakenly installed it. So basically I skipped "5.0.0" update and directly installed "5.0.1" and now my Nexus 4 "UNROOTED" device is bootlooping. What should I do?
1. Should I downgrade to 4.4.4 with deleting/editing "-w" thing in "flash-all.bat"? I read somewhere that downgrading wipes all the data. What are my options going back to KITKAT?
3. What should I do to backup? I don't want to flash all my data.
4. Will the deleting "-w" thing work on "5.0.1" factory image?
5. Will the deleting "-w" thing work on "4.4.4" factory image?
6. Do I have to download SDK to perform all the tasks?
Any reply would be greatly appreciated. Thanks in advance. Cheers!
First download official nexus 4 5.0.1 factory image from here https://developers.google.com/android/nexus/images and extract all files till you have separate img files like boot.img, system.img etc.
Then download and install Wugfresh toolkit and install all necessary drivers.
Finally use the toolkit to install all img one by one, except the userdata.img.
At the end you will have a full stock working 5.0.1 system, with no data loss.
As above. While the phone technically works I cannot flash the latest stock rom (the set about unlocking, rooting, installing a custom recovery) as it loops....ive dropped back to the original stock image (4.4.4) which boots fine....I then went back up to LMY47V which loops and currently downloading KTU84 to see if that works....now just to add to all of this I was given the phone with a cracked screen which ive replaced but it came to me dead so I don't know the previous history....and thought that the advent of me fitting the screen caused it which I doubt....but the thought was there.....
The only other option if KTU84P doesn't work is to drop back to 4.4.4 and go up gradually......
Anyone else had this...?
Well, so far, nothing works apart from the stock image (tried a few other stockers) but nothing - tried installing custom recovery TWRP 3.x which installs fine....just wont boot...
Try stock flashing using Nexus root kit and check Soft bricked radio button
Sent from my Nexus 4 using Tapatalk
I'm using the Nexus Root toolkit - is that the one youre talking about ( as I cant see the "softbricked radio button") - ive got "Softbricked/bootloop" but tried that which didn't work....
I did try the original 4.4.4 image (the first one) which does boot. And then tried manually flashing the radio separately but that didn't work (but TBH I'm not sure that I did it correctly) - so, do you think its a radio issue - the reason it wont boot??
Yes, that will be the right radio button. There is only one for stock flash section. Which radio are you flashing? If its Nexus LTE zip then it's only for Lollipop ROMs 5+. Try flashing latest Lollipop stock and if it boots then flash radio. That's what I did.
If not then back to KK.
Sent from my Nexus 4 using Tapatalk
Try this: flash the latest stock ROM using fastboot commands and, after flashing the last partition, flash the userdata.img file, use the buttons to boot directly to recovery from fastboot, perform a factory wipe, and reboot.
Ok - thanks for that - haven't done the fast boot commands for a while...! ill try it now....
The other thing I noticed was the battery is draining really fast (while in bootloop) the back of it is very hot....so much so that plugged into the laptop wasn't enough to keep it running - had to transfer it to a charger....
Looking at my file I downloaded from google... (I was just about to start) I noticed I don't have the radio firmware? so, all this time while ive been reflashing and trying different images from google (stock images) ive not been flashing the radio firmware - I thought they would have included that!! am I right in thinking that's why its been bootlooping as the radio firmware is at stock (the reason why only the original base image boots)??
Well, while I was installing I flashed twrp3 as the recovery and used that when I went in to manually reset it gave me the error "cache invalid argument" - would that have any bearing??
Well, tried that and it sat there....thought id try jumping ahead a little....flashed a cm13 nightly along with a radio firmware file (a .zip) using twrp...but still the same....missing something somewhere....
I presume you have NRT installed and tried; it downloads and extracts factory images before flashing. If you are flashing latest official stock lmy48t check contents of the downloaded image. Should be
cd C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Factory_Images\occam-lmy48t-factory-416938f1
dir /b
bootloader-mako-makoz30f.img
flash-all.bat
flash-all.sh
flash-base.sh
image-occam-lmy48t
image-occam-lmy48t.zip
radio-mako-m9615a-cefwmazm-2.0.1701.07.img
Batch file that NRT runs is flash-all.bat; third line is radio flashing
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.07.img
fastboot reboot-bootloader
fastboot -w update image-occam-lmy48t.zip
Executing fastboot commands manually should achieve same result
Yep - using the wugfresh stuff tried it about a dozen times with different stock images....never had a problem like this before....
tried as you said - tried to flash manually and also tried using the bat file....still the same - flashed back to jdq39 and it boots straight back up...weird....
Can I ask silly question? Was bootloader unlocked?
Sent from my Nexus 4 using Tapatalk
If the bootloader was not unlocked, no ROM could be flashed to the phone.
Exactly. So if all fastboot commands in flash_all.bat run error free phone should boot OK. NRT runs log in a separate window so any error is easily noticeable. The only thing that comes to mind is how long it takes to boot after rom flash; I think mine took close to 20 min of bouncing balls before I saw Android logo. So may waiting for longer time will resolve it.
Yep - unlocked the bootloader (and relocked it) hoping that would shift it into life!! but no...
Ive tried the waiting game....left it on at the office at the end of the day, came back in the next day to see it still "trying to boot..."
Came across a procedure on how to pull log during bootloop. Check it out if interested. I haven't tested it. http://forum.xda-developers.com/general/xda-university/universal-test-rom-build-didnt-boot-t3258818
Sent from my Nexus 4 using Tapatalk
Yep - will do - just for the record I reflashed back to 4.2.2 relocked, booted, let the phone download a 4.3 update and flash...totally stock....just sat there.....just had a look at that link (looks promising) so I'm going to go back upto the latest build and then install twrp then flash the file to see if I can see whats going on behind....