First connect to WiFi and make sure you can access the web.
Next put the N4 into airplane mode.
Then go to Settings > Apps > All > Google Services Framework > Clear data
Take the N4 out of airplane mode and let it connect to WiFi.
After a few minutes, you will be prompted to install the OTA update.
If you are not prompted within 10 minutes, open the dialer and force a "checkin" by typing: *#*#2432546#*#*
After "checkin succeded" message, you should be prompted to install the update.
Enjoy!
Doesn't work for me.
Sent from my Nexus 4 using Tapatalk 2
You have to be standing in the bathroom for it to work.
No. But for real. Updates are pushed out in waves. If your device is not on the current wave you will not get the update. That's it.
Don't want to wait. Do it manually.
albundy2010 said:
You have to be standing in the bathroom for it to work.
No. But for real. Updates are pushed out in waves. If your device is not on the current wave you will not get the update. That's it.
Don't want to wait. Do it manually.
Click to expand...
Click to collapse
http://www.androidpolice.com/2012/11/27/manual-download-android-4-2-1-update-jop40d-for-the-nexus-4/
This is the easy way reboot to cwm and flash done
Sent from my Nexus 4 using xda premium
bline007 said:
This is the easy way reboot to cwm and flash done
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
"Easy" is a relative term. Not everyone here, especially in the "General" forum is comfortable yet with flashing alternative recoveries or using abd, etc. This is meant for the novice and/or purist who does not want to alter the phone in order to receive and apply the update. This method does in fact work. Quite often the device is ready to receive the update, but the built in automatic & manual checkin fails to trigger the process. Clearing the GSF data forces the device to initiate it almost immediately, as opposed to waiting an undetermined amount of time for the device to resolve the issue on its own.
My advice to the audience who this is intended for: If this did not work for you now, try it again in a few hours or tomorrow, I assure you it will be much faster than waiting for it to happen naturally. In fact, to prove my point further, go ahead and try the manual checkin (under settings > about phone > system updates) first, each time, before you try this. You'll eventually see what I mean. FYI - Every Nexus device has behaved this way.
How come I can't get the update to install either in CWM or from OTA?? If I do OTA the phone reboots into CWM and I get an "assert failed" and installation aborted.... And if I manually go into CWM and "update from SD card" option I get the same issue!
Sent from my Nexus 4 using xda premium
Girn said:
How come I can't get the update to install either in CWM or from OTA?? If I do OTA the phone reboots into CWM and I get an "assert failed" and installation aborted.... And if I manually go into CWM and "update from SD card" option I get the same issue!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
If you changed your build.prop it will fail. U need to have stock build.prop.
I see your point skillllz
Sent from my Nexus 4 using xda premium
I have a stock build prop.. All I've done is Root and cwm
Sent from my Nexus 4 using xda premium
Girn said:
I have a stock build prop.. All I've done is Root and cwm
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Try wiping cache and dalvik then flash. It worked first time for me. Some custom Roms change build prop. I'm on stock rom
Sent from my Nexus 4 using xda premium
Thanks! Worked perfectly (on 1st try) to get 4.2.0 on my Galaxy Nexus finally.
Still doesn't work and I did a factory reset just now.. Get assert failed something about genie widget.odex then all these numbers and the file name then installation failed status 7
Sent from my Nexus 4 using xda premium
Worked here. Thanks.
Sent from my Nexus 4 using xda app-developers app
Girn said:
Still doesn't work and I did a factory reset just now.. Get assert failed something about genie widget.odex then all these numbers and the file name then installation failed status 7
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That means you removed genie widget.odex . put the file back or any other that you deleted and it will go through. I deleted currents, books, earth, genie, videos and a few more and it failed on the update and its because you have to have the same build prop or same apps back
Sent from my Nexus 4
worked a charm for me! thanks
Don't work for me
Worked. Thanks.
Sent from my Nexus 4 using xda app-developers app
You only need to clear data of google services framework, then check for updates. Rinse and repeat until it works - usually 1-5 times.
All those other steps aren't necessary.
bline007 said:
If you changed your build.prop it will fail. U need to have stock build.prop.
Click to expand...
Click to collapse
For those who have altered build.prop, any way to fix beside completely going back to the original Google ROM img?
Worked for me thanks.
As I have CWM, CWM asked if I want to flash untrusted update - I said yes. After isntall, I rebooted back to Recovery (as it said something about restoring stock recovery while installing update). CWM was still there. I told CWM to reboot and it said 'you may have lost root'. I selected yes to fix root and it rebooted. all seems fine now.
Worked nicely!! Thanks
Related
Just readon the moto forums that the update is rolling out and can now be pulled via about phone > updates. I updated previously but has anyone not in the soak test got the update yet?
Sent from my DROID3 using XDA App
Yes, i'm downloading it now
Sent from my DROID3 using XDA App
I checked for the update and it's available. I don't want to lose root though. Will someone post details after updating? Root, bloat, good or bad?
PyroHoltz said:
I checked for the update and it's available. I don't want to lose root though. Will someone post details after updating? Root, bloat, good or bad?
Click to expand...
Click to collapse
You will want to re-bloat your phone before updating or it will fail. Root will be lost but 1-click root still works on the update.
Sent from my DROID3 using XDA App
I tried checking, and get the message "Check for update is not available at this time. Try again later."
It seems something is definitely up, as normally I would just receive a message that my system is up to date.
I don't see why you guys just haven't used the fastboot or .zip already... been available for a month.
Sent from my DROID3 using xda premium
jweber228 said:
You will want to re-bloat your phone before updating or it will fail. Root will be lost but 1-click root still works on the update.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Is there a simple way to avoid the update?
PyroHoltz said:
I checked for the update and it's available. I don't want to lose root though. Will someone post details after updating? Root, bloat, good or bad?
Click to expand...
Click to collapse
It will fail if you removed/froze any apps.
Androidsims said:
I don't see why you guys just haven't used the fastboot or .zip already... been available for a month.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It's something I was just waiting to be ota personally. A lot of the issues it is said to fix never really bothered me except for the blue tint in pictures.
Sent from my DROID3 using XDA App
Assuming you did not remove any stock apps besides the two Gameloft demos and just froze the apps using Titanium:
1. Unfreeze the apps using batch mode in Titanium
2. Install the update
3. Reroot using the one click method. I unfroze and updated at work and now just finished rooting again.
Yeah it's random. Have two non-rooted D3's one of them got pushed the update and the other one is stuck checking for the update. Came here to see what was up.
Got the ota update this morning on my stock D3. Downloaded and installed and the install failed and then the home screen came up but with no 3G connection. Pulled the battery and nothing happened. Called Verizon and they had me pull the battery and then do a hard reset. Still no 3G connection. Got Motorola on the phone and they had me do a manual reset, but still no 3G connection. Verizon is sending me a replacement phone overnight.
Fail. Lol
uncle650 said:
Got the ota update this morning on my stock D3. Downloaded and installed and the install failed and then the home screen came up but with no 3G connection. Pulled the battery and nothing happened. Called Verizon and they had me pull the battery and then do a hard reset. Still no 3G connection. Got Motorola on the phone and they had me do a manual reset, but still no 3G connection. Verizon is sending me a replacement phone overnight.
Click to expand...
Click to collapse
Sent from my MB525 using XDA App
wnemay said:
It will fail if you removed/froze any apps.
Click to expand...
Click to collapse
I unfroze the apps before trying. Nothing was previously removed. Anything that was frozen has unfrozen properly.
EDIT: Found the reason for the message: Social applications was set to "sync over wifi only" which was causing the message. Now I get the "checking for available update. Please wait..." and it's been going about 3 minutes so far, no update found. Does not look like data is being sent/received while it's checking, either.
Yesterday, Verizon approved Jelly Bean for the DROID 4 as build 98.72.18, but as is typical, Motorola sent the first wave of updates out to members of their feedback network (soak testers) this morning. And since that happened, the file has been pulled and made available to everyone with the device.
We have instructions for you below, so if you do not feel like waiting for the update to be pushed to your device, feel free to jump below.
The official changelog can be found here. here
Instructions:
*These are the instructions from the RAZR HD update, but they should work for the DROID 4 as well.
*You have to be running the official Ice Cream Sandwich (Android 4.0.4) update of build 6.16.217. You also have to be completely stock.
1. Download the update file here: here
2. Drop that file on your SD card, not internal storage.
3. Turn phone off, and reboot into recovery.
*Hold both Volume Up and Down along with Power until you see the boot menu. Use Volume Down to hover over “Recovery.” Press Volume Up to select it.
*Once you see the Android and Exclamation point, press both Volume Up and Down at the same time.
4. Select “apply update from external storage.”
*Use Volume keys to highlight, Power button to select.
5. Then select the file you downloaded from above. It should already be on your SD card.
6. Watch as the update applies.
7. Once finished, choose the “reboot” option and enjoy!
DON'T FORGET TO SAY THANKS!
got this from droid-life
FYI, you will lose root if you do this without Voodoo unrooting first, as I just mistakenly did
rorytmeadows said:
FYI, you will lose root if you do this without Voodoo unrooting first, as I just mistakenly did
Click to expand...
Click to collapse
yes ots's will cause you to loose root
So do I need to De-root and remove safestrap before installing this, or can I just install and then root this?
bluri said:
So do I need to De-root and remove safestrap before installing this, or can I just install and then root this?
Click to expand...
Click to collapse
Safeboot and restore complete stock ICS. Don't worry about losing root. RAZR blade method is confirmed to work. Unless u have no access to PC then yes backup root with voodoo only if u are using super user latest binary. Restore root after jb update.
Sent from my DROID4 using xda app-developers app
does anyone know if this changes the kernel as with gingerbread to ics? curious to know if my ics custom rom will work in safestrap still or if its a done deal
Sorry for spamming on this topic, but just tried to install this after disabling safestrap and done factory reset.
got to recovery and chose the file, it started install but then gave error
"Assert failed: apply_patch_check("/system/bin/logwrapper", "aHASHCODE" ,"ANOTHER HASHCODE")
E:Error in /tmp/sideload/package.zip
Status 7
Installation aborted."
EDIT: OK I have to flash it completely stock with RSDlite and clean package, just downloading it..
EDIT2: Just installing this update, clean ICS with RSDlite helped
rorytmeadows said:
FYI, you will lose root if you do this without Voodoo unrooting first, as I just mistakenly did
Click to expand...
Click to collapse
azrael293 said:
does anyone know if this changes the kernel as with gingerbread to ics? curious to know if my ics custom rom will work in safestrap still or if its a done deal
Click to expand...
Click to collapse
i have not upgraded yet as i allways wait for some type of working sbf..sence this will upgrade your device to jellybean i am sure it will include new kernels
Is it possible to revert to the OEM 4.0.4 (6.16.217) firmware via the existing SBF?
Just curious, I haven't made the jump to JB yet.
rruleford said:
Safeboot and restore complete stock ICS. Don't worry about losing root. RAZR blade method is confirmed to work. Unless u have no access to PC then yes backup root with voodoo only if u are using super user latest binary. Restore root after jb update.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Do you have a link? I
I did something wrong in the process and vodoo wouldn't restore root for me
bdbraaten said:
Do you have a link? I
I did something wrong in the process and vodoo wouldn't restore root for me
Click to expand...
Click to collapse
It'll be on the RAZR forum
Sent from my DROID4 using xda app-developers app
---------- Post added at 07:25 PM ---------- Previous post was at 07:23 PM ----------
Or here. http://vulnfactory.org/public/razr_blade.zip
Sent from my DROID4 using xda app-developers app
does anyone know how to reflash after update? i mean to reflash the entire phone, not just do a factory rest/wipe. or is that my only option?
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
jmagi said:
does anyone know how to reflash after update? i mean to reflash the entire phone, not just do a factory rest/wipe. or is that my only option?
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Wait for the jb xml
Sent from my DROID4 using xda app-developers app
jmagi said:
does anyone know how to reflash after update? i mean to reflash the entire phone, not just do a factory rest/wipe. or is that my only option?
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Like rruleford said the only way to totally wipe/flash the entire phone would be to wait for the xml fastboot files. What you COULD try is placing the JB OTA update on your external sd card, then booting into stock recovery, wiping data and cache, and then re-flashing the update manually. It should be able to flash over top of itself just fine. Not sure if it would fix anything but might be worth a shot.
Sent from my Droid 4 - Eclipse JB
ok thanks you all, i guess i can wait for the fastboot files then.. it hasnt rebooted on me all day so far. might have been a glitch with apps i installed that no longer work well on jb as they did on ics
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
aah dang sussed it. seems u can now reboot the fone by holding power button for 3-4 seconds. mine gets stuck once in a while so thats what i think was causing the reboots. any chance there's a way to turn that off?
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
jmagi said:
does anyone know how to reflash after update? i mean to reflash the entire phone, not just do a factory rest/wipe. or is that my only option?
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2207384
ovelayer said:
http://forum.xda-developers.com/showthread.php?t=2207384
Click to expand...
Click to collapse
Thanks for the link, this method is not working for me and I have stock ICS installed, removed safestrap and all, but I get a code 7 validation error of the current version that is installed.. maybe because im dutch and have an adjusted build.prop and apnsconf for data
komani86 said:
Thanks for the link, this method is not working for me and I have stock ICS installed, removed safestrap and all, but I get a code 7 validation error of the current version that is installed.. maybe because im dutch and have an adjusted build.prop and apnsconf for data
Click to expand...
Click to collapse
yes i believe that is what is going on
Safestrap Talk
Basically, we can use this thread for any info/help regarding Safestrap and keep Hashcodes thread clean for him and testers that know what their talking about
Thanks HASHCODE for your hard work !!!!!!!!
I'm running X Note 6 on the At&t Galaxy Note 3 100% flawless.
Special Thanks to》 Hashcode for Safestrap >http://forum.xda-developers.com/showthread.php?t=2572978
drakeymcmb >1st Flash method we had> http://forum.xda-developers.com/showthread.php?t=2554411
evilpotatoman >For Restore and going out of his way to help >http://forum.xda-developers.com/showthread.php?t=2559715
Raiderman >For his tech help/themes>http://forum.xda-developers.com/showthread.php?t=2534671
bri315317 >For his help and script thread>http://forum.xda-developers.com/showthread.php?t=2574137
Without y'all, I would of sold this phone.
KNOWN ISSUES:
No Aroma installer support. This is due to the stock Note 3 kernel framebuffer. To build a recovery which worked, it needed QCOM patches. So will Aroma.
If you try a .zip file with an Aroma installer, it will most likely just hang.
If you're stock ROM is modified then the "Reboot Recovery" function from inside Safestrap APK may / may not work.
Right now flashing / booting ROMs on rom-slots is broken. I'm debugging best I can.
EXFAT support seems broken right now (64gb SD cards)
Here is how we are using it now, but please read and follow instructions.
>bri315317 >http://forum.xda-developers.com/showthread.php?t=2574137
We are not responsible for your phone messing up. If your scared then go to church.
J/K > We have a restore thread if you make a mistake by > evilpotatoman >For Restore>http://forum.xda-developers.com/showthread.php?t=2559715
Did you activate that rom slot once you installed a rom to it or was the stock slot still active?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
P1Tater said:
Did you activate that rom slot once you installed a rom to it or was the stock slot still active?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It was active but I just rebooted after flashing. I did not click on activate again. Should I do that after flashing and wiping the C/D ?
Worth a shot in my opinion
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I installed SS made a back up. That worked great. Tried to install galaxymans theme SS showed failed. What am I doing wrong?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
P1Tater said:
Worth a shot in my opinion
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, I downloaded the theme again and booted into recovery. Selected the Stock Slot (already checked).
I installed the theme and went to select the slot again but its already selected so I just wiped cache and dalvik cache.
Rebooted phone and nothing. Same stock look.
I wonder if it would work without wiping?
c-mack said:
I installed SS made a back up. That worked great. Tried to install galaxymans theme SS showed failed. What am I doing wrong?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Mine doesn't say failed. It installs but no theme when rebooting. ABout to try again
Have you tried just powering off after its installed and then just boot the phone up manually?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Nope. Reading some info from the Themes thread now
Sent from my SAMSUNG-SM-N900A using Tapatalk
So I have never posted here I just lurk. But I wanted to post this info up and as I get more info and testing done I'll update. Going to try and flash a couple roms this evening but here is where I am so far. If someone could post this in the dev thread that would be awesome. Post 1 for me.
CURRENT TESTS:
TEST #1: Hijack stability to enter recovery on every boot. RESULT: untested.
TEST #2: Reboot to recovery functionality RESULT: pass every time, either through safe strap app or manually.
TEST #3: Recovery removal leaves device in clean state RESULT: pass. Uninstalled recovery after 2 reboots into safe strap and worked fine.
TEST #4: ADB access from recovery RESULT: untested.
TEST #5: ROM-slot creation RESULT: pass. created 3 with default values. No issues.
TEST #6: Backup stock ROM RESULT: pass. Done in 167 seconds for roughly 3300mbs.
TEST #7: Restore stock ROM backup to stock slot: pass. No issues
TEST #8: Initial 2nd-init ROM installation on rom-slot RESULT: untested
TEST #9: Custom ROM flash on rom-slot RESULT: untested
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Still no luck for me tried a few times. Not that it matters but I've tried starting SS from both touch wiz and nova launcher. SS says failed both times.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
hey
akdrift said:
So I have never posted here I just lurk. But I wanted to post this info up and as I get more info and testing done I'll update. Going to try and flash a couple roms this evening but here is where I am so far. If someone could post this in the dev thread that would be awesome. Post 1 for me.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
I posted it in there for you sir....
c-mack said:
Still no luck for me tried a few times. Not that it matters but I've tried starting SS from both touch wiz and nova launcher. SS says failed both times.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
You have to turn the phone off or just regular reboot and then the option will pop up to boot in recovery. This will happen if you clicked "install recovery" inside the SS apk.
Sent from my SAMSUNG-SM-N900A
dirtydroidx said:
You have to turn the phone off or just regular reboot and then the option will pop up to boot in recovery. This will happen if you clicked "install recovery" inside the SS apk.
Sent from my SAMSUNG-SM-N900A
Click to expand...
Click to collapse
>> C MACK
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
I installed SS as soon as it went up and everything has gone smoothly. It's worth mentioning that I used the original De La Vega root and never updated because I had zero problems afterwards. I never tried any of the dirty workarounds to flashing roms. I rebooted into recovery from the app (flawlessly) and made a backup. Then decided to g3t ballsy and install galaxyman's theme while wiping caches. It only appeared to partially work. Then I remembered that I had partially themed my phone using Wanam/X-Blast. I turned those off and viola! My phone looks ultraslick.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
---------- Post added at 12:39 PM ---------- Previous post was at 12:37 PM ----------
My only question now is:
Can we flash T-Mobile roms and swap modems or are there other important differences? I'd really like to just hijack their dev section.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Also SS is meant to be a failsafe recovery, meaning your active slot should be your current setup. You should not flash anything to your stock rom slot unless your comfortable. If you want to flash a rom like Encore that's in the development section , create a new rom slot and flash to it; Then if **** hits the fan you always have your stock rom to switch back to.
Sent from my SAMSUNG-SM-N900A
Boraltis said:
I installed SS as soon as it went up and everything has gone smoothly. It's worth mentioning that I used the original De La Vega root and never updated because I had zero problems afterwards. I never tried any of the dirty workarounds to flashing roms. I rebooted into recovery from the app (flawlessly) and made a backup. Then decided to g3t ballsy and install galaxyman's theme while wiping caches. It only appeared to partially work. Then I remembered that I had partially themed my phone using Wanam/X-Blast. I turned those off and viola! My phone looks ultraslick.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
---------- Post added at 12:39 PM ---------- Previous post was at 12:37 PM ----------
My only question now is:
Can we flash T-Mobile roms and swap modems or are there other important differences? I'd really like to just hijack their dev section.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I started with Mj5....Did the install ROM without recovery a couple of times.
Did the restore Mj5 Thread a bunch.
Before I installed Safestrap, I restored back to stock rooted and installed SS.
Can't flash themes yet.
Maybe I should start all over again but this time restore twice and go to system settings/back up factory reset.
The last time i did the factory reset option after a restore, the phone was perfect.
Maybe I will just do that and start over...Will report back.
Hey guys, I've held off from any exploits thus far including root. However, I am now interested in using safestrap. I am on MJ5, is my only option for root kingo?
Sent from my SAMSUNG-SM-N900A using Tapatalk
theROMinator said:
Hey guys, I've held off from any exploits thus far including root. However, I am now interested in using safestrap. I am on MJ5, is my only option for root kingo?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
I wonder if you can try this. It worked for me but only after I got into a bootloop
http://forum.xda-developers.com/showthread.php?t=2559715
At the end of all steps, the last step is an easy "put files here" and it rooted. (after a reboot twice)
Just follow instructions
When I reboot and the safestrap screen comes up where I can choose to enter recovery or enter regular system. In red it says safestrap disabled. Is this typical?
I know safestrap is installed and running as I created a backup did a factory reset then then did a back up from the recovery I created.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Introduction
This kit is designed to update Stock rooted Nexus 5 devices to Android 4.4.4 while retaining all user data as well as root permissions. This will also work on non-rooted devices with an unlocked Bootloader.
Before you Start
# This kit is designed to update without wipe but anything is possible, so I strongly urge you
to back up all data. Also I am not liable for any lost information.
# Please configure all ADB drivers
# Place phone in Fastboot mode. Power down the device; (Press and hold Power + Volume Down)
until the device boots into Fastboot.
# Extract all files, open the Unfathomable EXE file in the provided folder and follow the prompts Carefully.
Instructions
Run the EXE. After your device reboots, boot your Nexus into recovery. TWRP recovery should boot. Select the reboot option and reboot system.
You will be prompted "Swipe to flash SuperSU". This will restore all Root permissions.
*Also in the event that your device is stuck in a bootloop, just wipe the cache and you should be good to go!
Downloads
Nexus 5 Auto Updater 4.4.4 by Unfathomable.zip
The Kit can also be downloaded at this Dev Host URL
http://d-h.st/mRY
[Nexus 5 Auto Updater 4.4.4 By Unfathomable.zip - 451.78 MB]
Other Information
The Nexus 7 Wi-Fi Auto-Updater 4.4.4 can be found at this URL
http://forum.xda-developers.com/showthread.php?t=2791773
XDA:DevDB Information
Nexus 5 Auto-Updater, Tool/Utility for the Google Nexus 5
Contributors
Unfathomable
Version Information
Status: Beta
Created 2014-06-29
Last Updated 2014-06-29
Got to be one of the slowest downloads for such a small file in the history of man.
Painful to say the least.
For me, almost half a gig is something other than small.
TiltedAz said:
For me, almost half a gig is something other than small.
Click to expand...
Click to collapse
Still slow to download. Had faster larger files.
Sent from my SM-G900F using XDA Premium 4 mobile app
@home said:
Still slow to download. Had faster larger files.
Sent from my SM-G900F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And you're complaining in the OP's thread, why? Blame Dev-Host not them. Lol.
Not complaining, just stating a fact.
Sent from my SM-G900F using XDA Premium 4 mobile app
With all do respect to opinions I would greatly appreciate if this thread is used for and remains a hub for questions and support. With that being said I have taken the liberty of uploading the file into XDA's server for downloading. Please respect my wishes as I have taken my own personal time to provide the community with this tool and many more to come. Thank you all! If you have any concerns, feedback or need support please feel free to contact me at [email protected].
Sent from my Nexus 5 using XDA Premium 4 mobile app
Thanks for do us a easy way to update to v4.4.4 with stock rom! :good:
Just want to thank the op for making it so easy
It's a good idea but a little long winded when you can just flash a rooted stock ROM.zip via recovery.
Sent from my Nexus 5 using Tapatalk
Hello guys,
I am a newbie in this. I have Nexus 5 with Stock rooted 4.4.2. Will this method work for me to update to 4.4.4?
Thank you!
miserableboy said:
Hello guys,
I am a newbie in this. I have Nexus 5 with Stock rooted 4.4.2. Will this method work for me to update to 4.4.4?
Thank you!
Click to expand...
Click to collapse
Yes, it is not a requirement to be running 4.4.3. Let me know if you have any difficulties.
Out of Memory
I'm getting "error: out of memory" shortly after the update starts. It sends and writes the bootloader then reboots into the bootloader and gives me the error. What am I doing wrong?
ddukatz said:
I'm getting "error: out of memory" shortly after the update starts. It sends and writes the bootloader then reboots into the bootloader and gives me the error. What am I doing wrong?
Click to expand...
Click to collapse
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Unfathomable said:
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same thing here. Already wiped cache but no memory message appears.
Unfathomable said:
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Click to expand...
Click to collapse
Not sure which one but one of these things fixed it for me.
Thanks!
ddukatz said:
Not sure which one but one of these things fixed it for me.
Thanks!
Click to expand...
Click to collapse
Thank you for bringing the issue to my attention, and no problem I'm glad I was able to help.
I also don't want to offend the developer as he did spend a lot of time on this. I do respect him, but I wanted to share my opinion. The last couple of OTA's I just downloaded the update straight from the OTA thread to my phone, I then flashed them in TWRP. I didn't loose TWRP and it even gives an option to install SuperSU binaries if it doesn't see them.
However, I do want to stay on topic. I'm curious, for people who use xposed, would this tool allow an update without needing to uninstall modules? I'm just trying to see the differences between your method and flashing an OTA. Also, would people with custom kernels be able to update as well? If they can, then this would prove useful for those with custom kernels.
Again, I don't mean to offend the OP. I'm just curious about the differences/benefits.
PsychDrummer said:
I also don't want to offend the developer as he did spend a lot of time on this. I do respect him, but I wanted to share my opinion. The last couple of OTA's I just downloaded the update straight from the OTA thread to my phone, I then flashed them in TWRP. I didn't loose TWRP and it even gives an option to install SuperSU binaries if it doesn't see them.
However, I do want to stay on topic. I'm curious, for people who use xposed, would this tool allow an update without needing to uninstall modules? I'm just trying to see the differences between your method and flashing an OTA. Also, would people with custom kernels be able to update as well? If they can, then this would prove useful for those with custom kernels.
Again, I don't mean to offend the OP. I'm just curious about the differences/benefits.
Click to expand...
Click to collapse
It flashes the image not an OTA
Sent from my Nexus 5 using Tapatalk
rootSU said:
It flashes the image not an OTA
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh ok. That would make sense why the file is so big. So then, isn't this basically deleting the -w from the batch file and flashing normally? Well and retaining root.
Hello XDA, I recently rooted / unlocked my N6. I used WugFresh NRT to do so. However, I did not like the process of rooting so I (using NRT) flashed stock + unrooted and then factory reset followed by an OEM lock. Reading about lollipops new way of OTA, can I perform OTAs? Or is it too late?
Sent from my Nexus 6 using XDA Free mobile app
Hi,
As long as you are now stock, no system partition changes and Stock recovery, you should get and be able to install an OTA.
But, I don't own the device, so I'll have your thread moved to your device section in case there's something I don't know about the N6 in particular.
Good luck!
Thanks! I'm a newb to this whole technology stuff. My first nexus device as well. I soft bricked it too while attempting to remove a ROM.
Sent from my Nexus 6 using XDA Free mobile app
TheSkillfulTroll said:
Thanks! I'm a newb to this whole technology stuff. My first nexus device as well. I soft bricked it too while attempting to remove a ROM.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Not sure if this is of any value to you but considering the device apps are similar it may be used.
http://forum.xda-developers.com/google-nexus-5/general/stock-checker-zip-prepare-ota-t2927865
Oh to be honest I'm done with rooting for now. Ill wait till 5.0.2 comes out if I OTA good then great but if it fails (hopefully ill still be able to access phone if it does) I'll then flash and root. Hopefully its not the latter
Sent from my Nexus 6 using XDA Free mobile app
TheSkillfulTroll said:
Oh to be honest I'm done with rooting for now. Ill wait till 5.0.2 comes out if I OTA good then great but if it fails (hopefully ill still be able to access phone if it does) I'll then flash and root. Hopefully its not the latter
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
If your completely stock and unrooted their is nothing to worry about. You will indeed get updates.
Even with lollipops new way of checking?
They check blocks
Sent from my Nexus 6 using XDA Free mobile app
if you are rooted and on TWRP. Just download the 5.0.1 image. Extract it till you see the system.img and boot.img. Also download twrp and run
fastboot flash system system.img
fastboot flash boot boot.img
I then reboot and then run
fastboot flash recovery whateverthefilefortwrpis.img
after that restart to system and twrp will ask if you want to install supersu. I let it install and now i'm on 5.0.1. Everything is intact and no wipe is required.
I don't think you quite understand what I am asking... I had 5.0.1 , I rooted and unlocked using NRT. I installed a ROM, didn't like it and attempted to remove. At the attempt to remove it, I screwed up and the setup wizard wouldn't start, so I FORCE FLASHED USING NRT Stock and unrooted. This allowed me to start the phone and use it, I factory reset then relocked the OEM. I do not want to root nor unlock, I am asking if that, after these events, and lollipops new way of OTA, will I be able to update via OTAs?
Sent from my Nexus 6 using XDA Free mobile app
What is the new way lollipop handles OTA's?
Sent from my Nexus 6 using Tapatalk 4
Back then, it used to check file by file which was easily avoidable. Now, it checks a whole block of a partition, if it sees something as small a byte changed, it aborts. You can read more NY just googling Nexus 6 OTA root.
Sent from my Nexus 6 using XDA Free mobile app
TheSkillfulTroll said:
Back then, it used to check file by file which was easily avoidable. Now, it checks a whole block of a partition, if it sees something as small a byte changed, it aborts. You can read more NY just googling Nexus 6 OTA root.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It's not hard to understand, actually quite simple. If you have flashed the stock image then there is nothing to worry about and there is no need for assumptions. Yes, you will receive OTAs. No need for the "what if" and "how about," if you aren't willing to accept an answer, don't ask a question.
If you're 100% stock then you will get ota.
Oh okay, thanks for the help! Once 5.0.2 rolls out, if it does not work, I'll just have to do it within NRT
Sent from my Nexus 6 using XDA Free mobile app