Hey guys, will the android update 4.2.2 erase everything on my nexus?I am rooted and unlocked, so if the main update thing does erase all of my data is there another way to update without loosing any of my data? I used the nexus toolkit to root, and I know there was an option to reinstall android without erasing data, but is that possible with a newer version of android..
Thanks
Micro
No it will not erase everything.
Because you are rooted, there is a chance that the OTA will not succeed, depending on how close to stock you are. (Some root apps appear to diddle a variety of things in /system, and if any of these things are targets of the OTA patching process, the OTA will fail). Also if you have a custom kernel, this particular OTA will not succeed.
If the OTA fails, no worries - it always fails during initial verification steps when it is checking to make sure that the checksums of targeted files exactly matches what it expects, before anything on your tab has been altered. So, if it fails don't freak out - everything on your tablet is the same as before the OTA started.
If it succeeds, you will loose root as a result of the setuid/setgid permissions of the "su" binary getting reset by the OTA installer script. You can either manually fix that with a "chmod" command (via adb with the custom recovery running and /system mounted) or you can simply re-flash the same SuperSU (or Superuser) root installer kit that you used when you originally rooted. The OTA also flashes a new stock recovery in place, so you will need to re-flash your custom recovery back into place after it has finished. That should be no problem so long as you know how to do so, using either fastboot directly or a toolkit.
I'm not sure you needed to start a new thread on this - scroll through a few pages here and see just how many "4.2.2. update question" threads there have been recently.
good luck.
PS If your OTA fails and you want to try patching things by hand, read through all the trouble threads in here before posting. Each time it runs, it will report the source of the error in /cache/recovery/recovery.log. As always, make a Nandroid backup before you begin.
Sorry what exactly does ota mean? And so your saying there's no way to update without loosing my data? If that's the case I'm not updating because I'm filled to the max with data
Thanks
Micro
microzee said:
Sorry what exactly does ota mean? And so your saying there's no way to update without loosing my data? If that's the case I'm not updating because I'm filled to the max with data
Thanks
Micro
Click to expand...
Click to collapse
Which part of this:
bftb0 said:
No it will not erase everything.
Click to expand...
Click to collapse
did you find confusing?
I said that it will either succeed or fail, and if it fails it will do so in a way where nothing changes. If it succeeds, it will change some things, but not the things you are referring to as "my data".
OTA = Over The Air (update)
I used rootkeeper, temp unroot then installed ota update by toching on it. But after successfully updating my tablet is still on 4.2.1. Pls help. Even after updateing application msg on boot ithas not updated.
Sent from my Nexus 7 using xda app-developers app
sukhjit_bhullar said:
I used rootkeeper, temp unroot then installed ota update by toching on it. But after successfully updating my tablet is still on 4.2.1. Pls help. Even after updateing application msg on boot ithas not updated.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I was wondering if RootKeeper would work or not.
---------- Post added at 06:02 PM ---------- Previous post was at 05:46 PM ----------
Wait....I just tried usig RootKeeper to temporarily un-Root the device then upgrade to 4.2.2 and it seems to have worked without an issue. I let it run through the entire upgrade, it rebooted, I looked to see what version I was on, it shows as 4.2.2, I then used RootKeep to restore Root, it worked like it was supposed to and it looks like it kept 4.2.2 as well.
I've tested a few apps that need Root and they worked just fine.
Hi all,
I've the same Problem here. the OTA-Update fails on my Nexus 7 (rooted). The message is only the green Robot with "Error". After restarting I can see that the version is still 4.2.1 :crying:
This is not the mainpoint (I've read up to now some threads which describing this issue). My point is: I can not restart the OTA-Update. There is no message whicht tolds me, that there is an update avalible... neither in the statusbar nor in the Settings.
Additionaly I can not find the log-file, which was some times described, where the error will be explained (I think it was deleted after the second restart).
Can someone explain me, how I can restart the OTA? Is it possible with the Framework-data deletion-trick? If I use this trick, what will be deleted in the Framework? Is there a place where the file /cache/recovery/recovery.log will be backuped?
If here is the wrong place for my questions, I'll make a new thread, but I think the thread which I've chosed fits it more or less
BR
SolarPlexus said:
Can someone explain me, how I can restart the OTA? Is it possible with the Framework-data deletion-trick? If I use this trick, what will be deleted in the Framework?
Click to expand...
Click to collapse
it's the framework data deletion trick*, yes. If you find solution to the update error problem, please keep us posted, cause i have the same issue...
*settings->apps->all->google service framework->force close->clear data. After that you go to the update menu (settings->about tablet->system updates) and tap on check now.
Related
Hi guys, after a 6 months period with HTC Wildfire S, i decided it was time to upgrade my device, so here i am, a newbie Nexus S user.
The first things i did with my new toy were unlocking the bootloader, gaining root permissions and installing CWM.
But i noticed that Market isn't updating, it's stuck to THIS version (i think it's 2.13)
Has this anything to do with root and cwm? Or it's just a matter of time and i'll eventually get the update?
Same thing with firmware: at the moment i'm running 2.3.3: looking for updates, and even using the *#*#checkin#*#* code, provided the same result: no FOTA available. Is this due to the root+cwm or i just need to wait?
I know this has already be discussed in the faq, but i find them quite confusing.
I mean, i know i could do a manual update, but i'd like to know whether if i'll ever receive a fota update or if i've lost this chance after root.
Q: I'm rooted with Clockwork and can't install the OTA! I updated to 2.3.1 and lost root! What gives?
most of the time, official OTAs will not install through custom recoveries because of their tendency to break root or restore things like the stock recovery. Also if you've made any modifications to the system files such as replacing the default Mms.apk(messaging) with the custom Black Mms.apk found in the Themes & Apps section, or deleted any .odex files from the system partition, it will not install. The easiest way to update to 2.3.1 is to flash a custom rom such as one of the custom ROMs or use the 2.3.1 Stock NANDROID backup found in the development section. And yes, 2.3.1 "broke root." To regain it, simply follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=884499 (All credit goes to the original author(s) of the linked thread!). The aforementioned procedure is only needed on the Stock Nandroid Backup, not any of the custom ROMs.
Click to expand...
Click to collapse
Thanks in advance for the answers!
There is no update due to the root, i advice you to manually update your phone to the latest version 4.0.3 using cwm, after that root again. finally you will have rooted ics on your nexus s.
uhm, you say i won't receive updates.
FAQ says most of the time i won't receive them.
THIS thread says i will receive them.
I am confused.
from what I can make sense of, it sounds like you should be getting updates. The FAQ you posted says that if you try to install one of the official OTA updates through CWM, it will fail most of the time.
i don't know how reliable that "checkin" trick is, and it may depend on your carrier as well.
if you've already rooted your device, then i would just flash one of the custom roms, you won't want to go back to the OTA after...
Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification
albundy2010 said:
Root/cwm recovery/unlocked boot loader etc has nothing at all to do with your device receiving the ota update notification
Click to expand...
Click to collapse
Thats correct. It has only to do with the install. (It will fail).. if you dont get the notification for an ota i dont know whats wrong...
Sent from my Nexus S using xda premium
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
If you had 2.3.3 the update was probably the 2.3.6 and after that you would have received the 4.0.3 update....anyway from what I remember the version of the ota update is showed in the notification bar...isn't it?!
Sent from my Nexus S using XDA
SavageButcher said:
Ok, finally tonight something started to move.
I received a message saying "A software update is available. Reboot the device to begin the installation" or something like that.
I rebooted and a CWM screen appeared, saying that the update could not be installed due to problems with the signature, sorry i can't remember word by word.
So... how can i know what the update was? I tried to browse the root folder in search for a .zip, but with no success. Any clue?
Click to expand...
Click to collapse
1. I assume it was the a step up from 2.3.3 to a max of 2.3.6 as OTA updates to 4.0.3 are currently on hold due to battery drain issue
2. your OTA install is failing because you have custom recovery (CWM) but the OTA updates require the stock recovery (3e)
if you really really want to install OTA updates, you gonna have to go back to stock recovery (do a nand restore, hope you have one) then flash the OTA updates for your device
Hi,
I am new to this forum and android stuff.
Please forgive me if I asked noob question.
I tried to search but got no complete answer.
My condition:
Nexus 7
build number JRO03S
used Nexus root toolkit 1.5.3
to unlock and root
used TWRP to install poitee kernel for usb dac.
Then:
The 4.1.2 updates notification show up
I pressed yes ... accidentally.
Now:
The build number becomes JRO03S
but the Android version is still 4.1.1
Question:
a. How to update to 4.1.2?
b. How to update without wiping any data and apps?
c. Do I have to reinstall the pointee kernel?
d. Will flashing rom ( updating to newer version ) wipe all things?
Sorry for so many questions,
For my situation it is a mixed up that I can't find similar condition on the internet yet.
Please kindly help and advise.
Much Thanks!
Btw,
I done below, no success:
1. quickboot
2. TWRP recovery
3. install nakasi-JZO54K-from-JRO03S.zip (from /sdcard)
4. error --> "Status 7" shown.
Cannot update.
Please Please help....
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
There is a modified version of the update that someone made. It doesn't perform the system checks that cause so many peoples devices to fail. If you can't run the update because you changed or deleted a system apk, read this post: http://forum.xda-developers.com/showpost.php?p=32752631&postcount=20
Don't run this if you're just not sure of why your update is failing.
vinny86 said:
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
Click to expand...
Click to collapse
Understood and Thanks a lot!!!:good:
that means all in all,
I still have to go through
the route of "Backup all --> Flash Stock & unroot --> Root --> Restore all".
However, considering the latest update seems don't have anything important or useful to me
So I just wait for the next more important update.
and save the drudgery next time.
vinny86 said:
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
Click to expand...
Click to collapse
He doesn't need to lock his bootloader, and he'll still not be able to run the update the natural way as long as he's got twrp or cwm installed. He can flash the factory rom and push the update through using custom recovery though.
Visa Declined said:
There is a modified version of the update that someone made. It doesn't perform the system checks that cause so many peoples devices to fail. If you can't run the update because you changed or deleted a system apk, read this post: http://forum.xda-developers.com/showpost.php?p=32752631&postcount=20
Don't run this if you're just not sure of why your update is failing.
Click to expand...
Click to collapse
Thanks for you advise,:highfive:
it is very kind of you to help.
I think may be the Status 7 error could be caused by the Custom Kernel Installed (poitee)
I better ask him in detail later on.
But mine is JRO03S,
May be it is safer to Return to Stock Rom completely and go for OTA later.
Sadly, This 4.1.2. seems got no very useful component to me,
I solely use it as a second PDA and Music Player with USB DAC.
I will have to wait for better solution then.....
pleaseabcd said:
However, considering the latest update seems don't have anything important or useful to me
Click to expand...
Click to collapse
The latest update allows you to boot into recovery mode without being plugged into usb. Now, if I get stuck in a bootloop, I don't have to look for something to plug my device into to restore. This feature alone is worth whatever hassle one may have to do to update.
Visa Declined said:
The latest update allows you to boot into recovery mode without being plugged into usb. Now, if I get stuck in a bootloop, I don't have to look for something to plug my device into to restore. This feature alone is worth whatever hassle one may have to do to update.
Click to expand...
Click to collapse
O'really.....em...then it is a different story..(Safer for the future...)
Perhaps, I just:
1. use Titanium Backup to back up everything --> copy the "Back up" to PC (just in case)
2. use Wugfresh Nexus Root Toolkit 1.5.4 to Flash Stock n Root
3. if can Flash to 4.1.2 stock rom directly, OK
4. if can't --> flash back to 4.1.1 stock rom (JRO03S) and then OTA
5. Finally, use Titanium backup to restore Everything.
Have to Thank You you guys again!
I know I am a newbie... but I am learning......
Hate to be limited to what I was given......while I can experiment and make mistake to grow up !:laugh:
Hey guys,
I'm hoping this should be a relatively simple question for you to answer. I rooted my Nexus 7 using Wug's Toolkit (on 4.1.1) quite some time ago and received an OTA notification just the other day for 4.1.2. Without thinking, I allowed it to download and let it reboot to install. That was when it booted into Clockwork and there was a signature verification fail. It gave me the option to disable it, but remembering now that I was rooted, I cancelled the update as I figured an OTA wasn't the most sensible thing to do without checking first. My device rebooted fine and is still running 4.1.1 with full root.
After doing some research, I see now that if I use an app like OTA Runkeeper, I can safely run the OTA (or just run it, lose root and then root again).
The problem is that the OTA won't come up anymore. I've tried manually checking for updates a few times but it thinks my device is up to date. What would you suggest I do?
Is there somewhere I can manually download the update and install via Clockwork etc?
Any assistance would be much appreciated!
jazacoop said:
Hey guys,
I'm hoping this should be a relatively simple question for you to answer. I rooted my Nexus 7 using Wug's Toolkit (on 4.1.1) quite some time ago and received an OTA notification just the other day for 4.1.2. Without thinking, I allowed it to download and let it reboot to install. That was when it booted into Clockwork and there was a signature verification fail. It gave me the option to disable it, but remembering now that I was rooted, I cancelled the update as I figured an OTA wasn't the most sensible thing to do without checking first. My device rebooted fine and is still running 4.1.1 with full root.
After doing some research, I see now that if I use an app like OTA Runkeeper, I can safely run the OTA (or just run it, lose root and then root again).
The problem is that the OTA won't come up anymore. I've tried manually checking for updates a few times but it thinks my device is up to date. What would you suggest I do?
Is there somewhere I can manually download the update and install via Clockwork etc?
Any assistance would be much appreciated!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1764794
wbbigdave said:
http://forum.xda-developers.com/showthread.php?t=1764794
Click to expand...
Click to collapse
I saw that, but it was posted back in July, and seemed smaller than the original OTA.
Nevermind... I didn't see the October update to the post further down.
Cheers!
So my Nexus 7 has downloaded the OTA firmware before I realized that Google was doing a roll-out. The Nexus 7 want me to reboot and do the FW upgrade but I don't want to upgrade the tablet. There does not appear to be a easy way to retain Root, and i'm not interested in teh steps for CFW, etc so it easier for me to stay on v4.2.x. Is there a way to prevent the upgrade? can I delete the downloaded OTA update or something? What is the path to the OTA update files? I would like to know before rebooting as I'm not sure if rebooting will just force the update. I have rooted the tablet but no other hacks such as unlocked boot loader have been performed on the device. I did a web search but did not see a in dept conversation on how to refuse the update once it has been downloaded onto the device
You could try a root keeper app that will retain root after the update. As for preventing the update, I'm not sure how that would work. Should be easy enough to keep root though.
Sent from my Nexus 7 using Tapatalk 4 Beta
A RootKeeper does not work with 4.3 due to the way that secuirity is implemented in the new FW. This has been noted in the description of the RootKeeper app on the Play store
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Sound Anarchist said:
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Click to expand...
Click to collapse
I checked the cache folder using es explorer and it showed no data files(zip) in that folder. maybe the file was not downloaded yet or was already applied and the device is just waiting for a reboot to consummate the upgrade
Or you could just flash CleanROM and have 4.3 and root.
Sent from my NookColor using xda app-developers app
u could take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1998378
Thanks for all of the input. I resolved this issue. I just enabled root in es explorer which showed the hidden OTA zip file in the Cache folder. I renamed the file, but the OS deleted it after the rename so I could not even save a copy of the file. I have since rebooted and the OTA did not re-download (which is a good thing) although I still get an icon in notification indicating that the OTA is ready to install.
I'm just not interested in updating to the latest 4.3 build due to lack of time. I have many Android devices and spending the time to Root and or unlock the boot loader on each device is just taking to much of my time. So I'll just stay on the current build until I have time to tinker again. Thanks again everyone for your input
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
downwiththebanksters said:
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
Click to expand...
Click to collapse
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
timnik said:
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
Click to expand...
Click to collapse
I wish I had seem this warning earlier too. I blindly accepted the OTA update yesterday thinking "Oh hey Android 4.3! Awesome!" and now I'm running in a whole load of problems and glitchs. I'm also not rooted yet which makes another problem because I can't find anything to root 4.3 yet. Also can't find anything on how to restore back to stock Android 4.2.2. Does anyone know anything about this? Will factory reset do the trick? I have all my stuff backed up.
Hi all,
I received the OTA upgrade notice recently and I let it upgrade the device. The installation process can be initiated after reboot, but after a while I get the "Error" screen with the android logo lying down with a triangle exclamation mark at its stomach. It then gets stuck there for a couple of minutes, and then reboot to the original operating system.
Since there isn't any information on the error screen, I can't tell what causes the error. Has anyone encountered this and what should I do (or just wait)?
Thanks!
davidpage said:
Hi all,
I received the OTA upgrade notice recently and I let it upgrade the device. The installation process can be initiated after reboot, but after a while I get the "Error" screen with the android logo lying down with a triangle exclamation mark at its stomach. It then gets stuck there for a couple of minutes, and then reboot to the original operating system.
Since there isn't any information on the error screen, I can't tell what causes the error. Has anyone encountered this and what should I do (or just wait)?
Thanks!
Click to expand...
Click to collapse
If you are on a custom rom/kernel/recovery i.e. not 100% stock, OTA will fail. Even if you are completely stock and rooted, OTA may fail.
venu123 said:
If you are on a custom rom/kernel/recovery i.e. not 100% stock, OTA will fail. Even if you are completely stock and rooted, OTA may fail.
Click to expand...
Click to collapse
It's completely stock. I once used Kingo Root to root my phone, but had soon reversed the operation. Not sure if that is a possible cause, but apart from that I didn't make any material change to the core system.
davidpage said:
It's completely stock. I once used Kingo Root to root my phone, but had soon reversed the operation. Not sure if that is a possible cause, but apart from that I didn't make any material change to the core system.
Click to expand...
Click to collapse
Try to install via adb sideload. A brief guide here:
http://www.reddit.com/r/Android/comments/2mgh8o
Another one here
http://forum.xda-developers.com/nexus-4/general/official-lollipop-5-0-ota-nexus-4-t2942228
venu123 said:
Try to install via adb sideload. A brief guide here:
http://www.reddit.com/r/Android/comments/2mgh8o
Another one here
http://forum.xda-developers.com/nexus-4/general/official-lollipop-5-0-ota-nexus-4-t2942228
Click to expand...
Click to collapse
Thanks for the links. I tried what they suggested but during the update it says the following:
Installing update...
Verifying current system...
"/system/xbin/dexdump" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
What should I do now? Seems more complicated than I'd like it to be
Nope, OTA is a no go on your phone. Flash the factory image.
updating to Lollipop
venu123 said:
Nope, OTA is a no go on your phone. Flash the factory image.
Click to expand...
Click to collapse
i was just offered the OTA update for my Nexus 4 in the UK. i accepted the update and as far as i can tell, it downloaded it, then went to install it. however, that didn't seem to happen. after going through the motions and wanting to reboot, which i obviously allowed, the phone still displays as being v4.4.4 when i check for updates though, it tells me the phone is up to date.
i dont know what to do now, so would be glad of any assistance offered, please
just offered and accepted the download again. same result. it appears to be 2 things preventing the update from happening. the first one is about accepting an untrusted/ zip package (or something like that) and the 2nd is about fixing root. i have tried doing 'yes' to both of them and 'no' to both as well. same result, the download downloads but wont install.
could i upgrade using the Android Toolkit? i have paid for it, so have the pro features, but the update wasn't offered through it earlier
Prettygrim said:
i was just offered the OTA update for my Nexus 4 in the UK. i accepted the update and as far as i can tell, it downloaded it, then went to install it. however, that didn't seem to happen. after going through the motions and wanting to reboot, which i obviously allowed, the phone still displays as being v4.4.4 when i check for updates though, it tells me the phone is up to date.
i dont know what to do now, so would be glad of any assistance offered, please
just offered and accepted the download again. same result. it appears to be 2 things preventing the update from happening. the first one is about accepting an untrusted/ zip package (or something like that) and the 2nd is about fixing root. i have tried doing 'yes' to both of them and 'no' to both as well. same result, the download downloads but wont install.
could i upgrade using the Android Toolkit? i have paid for it, so have the pro features, but the update wasn't offered through it earlier
Click to expand...
Click to collapse
Do you have a custom recovery? CWM gives that untrusted package message if you have signature verification turned on. If yes, you need to revert to stock and also unroot. Supersu does have the option of unrooting so you could try that. You could check out the toolkit, at least it can be used for backing up your data to the PC.
tnx for the info, venu123. progress made so far. i downloaded the Lollipop image and put it into the folder within Android Toolkit. i then let it do it's thing. the phone is now updated but i am struggling to get root again and also need some instructions on how to get it to sync again as a lot of the apps i had on the phone are not there now. anyone able to help with this please?
gonna have another try to get root on the phone. if successful, willpost back
---------- Post added at 08:12 PM ---------- Previous post was at 07:47 PM ----------
ok then. Android Toolkit didn't work. i can only assume that it's something to do with the Lollipop image not being in the program. however, i did get root by using the latest wugfresh app. many tnx to you for your efforts, wugfresh.
the one thing left for me to do now is somehow get the apps i had before the Lollipop update on the phone again. any help would be great, as i cant even see an option to sync the phone.
venu123 said:
Nope, OTA is a no go on your phone. Flash the factory image.
Click to expand...
Click to collapse
Is there a way to flash without wiping my data? Clearing my data is the last thing I'd want to do and, if this is unavoidable, I might just stay put.
I have a thought: since the message is telling me that dexdump has unexpected contents (that file actually doesn't seem to be there, as I've just checked), is it possible to just replace this file to bypass the problem? Thing is I cannot find this file anywhere for download.
Nevermind.. I copied that file from the factory image and the installation went smoothly!