yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] NCguy:
I'm not sure you can do it with the kit but I often boot into CWM and run the backup without needing to flash the recovery at all. Assuming you can do the same with TWRP
[Nexus 5 Android Development] lasha117:
Hi :) does auto root work on 5.0.1?

on 5.0 it had some problems at first :)
[Nexus 5 Android Development] CrEdge:
Once again, premature failure. This time it's on Flashing Stock. Live Log doesn't indicate anything, but the process was incomplete and way too fast. I fear what rooting will do to my Nexus 5...

*Oh yeah, No Wipe Mode was enabled. Not going to try without it. Next up will be Force Flash Mode.

*It worked! The kinks of early updating...
[Nexus 5 Android Development] oo03sjw:
Sideload

Sorry if covered already, have searched.

Trying to use the toolkit to sideload OTA update, boots to stock then fails with Status 7 error.

Any help please?
[Nexus 5 Android Development] NCguy:
Wugfresh, with the new 5+ OTA requirements we need a routine to automate return to stock, apply OTA, reroot and possibly custom recovery in a single step without losing data. Here is the greatest opportunity ever to justify using a Kit. Can you help?
[Nexus 5 Android Development] mchu6am4:
Uninstall 1.9.4

Hi Wug,

I'm struggling to uninstall version 1.9.4 from my PC - it keeps coming up with the attached message during uninstall!

Any ideas how I can get rid of it please as it won't update to latest version or uninstall!

Thanks, Ash
[Nexus 5 Android Development] Falconite:
now im using Stock ROM 5.0 without any modifications at all

and now i want to update it to 5.0.1 without delete my datas at all

can i use this kit to do that ?

if yes,how to do that ?

thankyou
[Nexus 5 Android Development] fatspirit:
You can choose OTA sideload, for example.
[Nexus 5 Android Development] GamerGuy80:
I also tried to sideload the OTA update and also got a fail with Status 7 error. Can anyone please help the both of us. Is there something we may be doing wrong? Will the toolkit be updated to also provide us to update to the most current lollipop version 5.0.1?
[Nexus 5 Android Development] RodKahx:
+1
[Nexus 5 Android Development] howard bamber:
Great package it is as well. Just used it. Ended up with tons of bugs on last flash so redid and got my camera back, ya!
[Nexus 5 Android Development] oo03sjw:
sorted mine, flashed stock and unroot with the tool kit, with the no wipe option, all good now on 5.0.1 :)
[Nexus 5 Android Development] GamerGuy80:
what file did you use to get to 5.0.1, did you sideload the ota update zip?
[Nexus 5 Android Development] oo03sjw:
I used the flash stock and unroot button and selected 5.0.1

Then just rooted again with the root and custom recovery button.

Worked for me, hope that helps.
[Nexus 5 Android Development] GamerGuy80:
thanks for the reply when i had looked the option to flash stock 5.0.1 wasnt showing up but now it is awesome thanks for the heads up
[Nexus 5 Android Development] g1b50n:
I have 5.0.0, can i flash 5.0.1 without wiping data?

I saw that moving from kit kat to lolipop is highly recommended to wipe all data, but what about in lolipop update to 5.0.1?

Btw. There is changelog which describe what was fixed in 5.0.1?

~sent via n5
[Nexus 5 Android Development] Gregor250385:
Flashing 5.0.1 went wel, but my system memory is 0MB. Anyone knows how to fix it?
[Nexus 5 Android Development] philosopherssage:
Sorry to tell you but only way I know to fix is factory rest or delete user partition. Both will remove all installed apps and data.
[Nexus 5 Android Development] Gregor250385:
I have done that, it remains 0MB. I had to remove some Google Apps to get some extra space. Thank you four your answer
[Nexus 5 Android Development] cadbomb:
Boy was I barkin' up the wrong tree! That did it, thanks a ton!
[Nexus 5 Android Development] mhardyman:
Via parallels?

Trying to get it working via parallels 8.0 (MAC) and having no luck, get stuck at step 3 of the full driver config. Anyone done this successfully?

thanks

M
[Nexus 5 Android Development] thegrantonstarcause:
Does USB otg work with the root method in this toolkit?
[Nexus 5 Android Development] Globespy:
Can't get ADB to work

I had exactly the same issues with my N4, and once again pulling my hair out with this toolkit.

I've followed the driver install instructions to the 't', and yet as with my N4, the N5 is not found.

I even tried uninstalling the drivers and trying the option#3 for Samsung drivers (which I already have on this laptop for use with my GF's SGS3), and still no luck - the toolkit says I should uninstall all the Samsung driver stuff, but I don't see how that will help, when those drivers are for my samsung devices?? And besides, when I tried the option#3 for samsung drivers it still fails anyway! Tried unchecking MTP, but that just drops the phone's connectivity and I can't see it so that is of no help.

Also tried installing the latest 'naked' ADB drivers via option#4, but no dice with this toolkit either.

I'm at a complete loss as to why this toolkit just won't play nice with my phones, yet MrSkips Toolkits work flawlessly - he doesn't have one yet for the N5.

Someone mentioned something about adding a 'signature' to their device to get around this, but I'm not sure what that means? When my N5 is connected via USB, it shows up clearly as an ADB device in device manager, and when I click the icon in the taskbar to safely disconnect the phone, it says "Eject Nexus 5". Clearly my computer sees the phone, yet the toolkit seemingly doesn't.

I'm running Win 7 64-bit.
[Nexus 5 Android Development] droidmeup:
Amazing as usual :D had to use raw driver option for adb to work. Thanks a lot!
[Nexus 5 Android Development] Globespy:
How exactly did you get this working?

What drivers did you use? Link?

When I uninstall and delete the existing drivers in device manager, then reboot, windows just installs them again automatically as soon as I connect the device, even though I deleted them. Pretty sure it's doing this via internet. I read that device manager should read 'ADB composite device' but it always ends up being 'Google nexus ADB device' no matter what I try. And this seems to stop the toolkit working.

Appreciate any advice.

Running Win 7 64-bit.

As I mentioned in a previous post, had same issues with my N4 and ended up using MrSkip toolkit as it must have either installed a different driver or just worked better. I need to see if I can isolate whatever driver that toolkit installed to make ADB work.
[Nexus 5 Android Development] Lownita:
I had no problems following the instructions for driver installation on Windows 7 64bit. Cleaned up everything as described, installed universal drivers option #1. Then the first driver test did not work directly, so I unplugged the phone, restarted the toolkit and then got the adb authorization on the phone which then made the test run with no problems. Overall this toolkit is very user friendly.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Android Development] carlese:
Can I flash recovery twrp 2.6.3.2 with this tool?
[Nexus 5 Android Development] Globespy:
Thanks. Did you only delete the specified files (18d1 and the other one beginning with e)?

Then reboot and restart toolkit, install option one, plug in your N5, get no response, so unplug and restart toolkit?

I'll give this a try......
[Nexus 5 Android Development] WugFresh:
After you root you can use a root user app for otg cable use like Stick Mount.

{{ WugFresh }}
[Nexus 5 Android Development] WugFresh:
Yes. You can check the box to flash custom recovery when rooting.. Or you can use advanced utilities flash recovery button.

{{ WugFresh }}
[Nexus 5 Android Development] federikk90:
i followed step by step to install driver but i'm not being able to connect my N5 to my pc in debug... windows 7 64 nit
[Nexus 5 Android Development] WugFresh:
http://www.wugfresh.com/faq/adb-device-not-found/
[Nexus 5 Android Development] kydkupa:
Thanks I'll try those.

**Update** That worked like a charm. Thanks for the heads up!!!
[Nexus 5 Android Development] Lownita:
Here is how I solved my issues with driver install. I found that it is very important to stick to a certain order while installing the drivers (koush universal driver in my case), because somehow MTP and ADB are messing with themselves and the drivers:

Stick exactly to this order!

1. Connect phone to the PC (activate USB debugging), go to windows device manager, right click and uninstall drivers from anything android related there - should be 2 devices while booted into android (for MTP and ADB). If there is a yellow ! already, doesn't matter, just uninstall and also check the option to delete driver files if possible.

1.1 Boot into fastboot mode and do the same as in 1.

1.2 If you have drivers installed, also uninstall them from windows control panel.

2. Unplug the phone

3. Use USBDeview (google it) to uninstall anything android/google related showing up there. In particular look for devices with Vendor ID "18d1" and "04e8" (props to wugfresh toolkit)

4. Reboot PC and go to your phone-->developer options and use the option to delete authorized computers for USB debugging (right beneath the option for USB debugging itself).

5. Connect your phone to the PC again, MTP should set up, driver install for ADB should fail

6. Disconnect phone

7. Install koush universal ADB driver http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi

8. Plug in your phone again, ADB should install

9. Accept the prompt on your phone to authorize your computer (if this does not pop up, something is probably wrong)

10. Boot into fastboot mode, let those driver install as well

11. ???

12. Profit!

Hope it works for you! :D
[Nexus 5 Android Development] Shftup:
Thanks Wug! Your Sh$t is Tight. So Simply yet So Effective.
[Nexus 5 Android Development] Globespy:
I give up......I've spent 4 hours on this, tried every possible combination and version of drivers (Koush, Universal, Minimal ADB, Google USB etc) and this toolkit refuses point blank to see my N5, just as it did with my N4.

From this screenshot, clearly the ADB interface is installed and connected (purple indicates it's enabled and functioning, but you must use the safe removal process before disconnecting), yet the toolkit keeps saying ADB is not found.

Surely for the love of all that is good, it should be simpler than this????
[Nexus 5 Android Development] VenomGBR:
Everytime I try and flash something it gets stuck saying "downloading..." on my phone, and "waiting for device" on the toolkit.

Can anyone help?

Thanks in advance.
[Nexus 5 Android Development] Globespy:
Followed this also......everything happened as it should in your guide (the only thing was that after reconnecting the phone after installing the universal drivers the phone did not ask for permission. It asked on the next boot though, so I went back into fastboot mode and plugged in - nothing happened except I can see an 'Android Device' in the taskbar.

Booted phone backup again and plugged in - I can browse the contents of the phone without issue in Windows 7 64.

Opened the toolkit and once again ADB is not detected.

Something is very wrong........I give up, but thank you for your efforts!

I'll await MrSkip releasing his version hopefully in the coming week and I'll be good to go, just like I was with my N4 when the same issues plagued me.
[Nexus 5 Android Development] WugFresh:
Sorry to hear you were unsuccessful doing the initial setup - unfortunately this is a prerequisite for all kits and manual methods. I provided as much info and tools as possible to explain how to configure them and I even included pictures. There is really nothing else I can do besides configure them myself. I did not make the drivers. Google and the device manufacturers did. And I did not make Windows. Microsoft did.

My advice to you would be to try configuring your N4 again with whatever worked for you. Then try plugging in your N5. Personally I didn't have to reconfigure anything with my N5.. Maybe I was just lucky but it worked first shot with the same RAW Google drivers I included in previous toolkit releases to setup my Gnex.

If you can't get it working you can try adding me on gchat. If I have free time I can help. Cheers.

{{ WugFresh }}
[Nexus 5 Android Development] chief2842:
Where is the no wipe option in the tool kit? I see the Flash Stock + Unroot button.
[Nexus 5 Android Development] nightfishing:
under options

---------- Post added at 12:04 AM ---------- Previous post was at 12:03 AM ----------

Thanks (again) WugFresh!

Flash stock+unroot (no wipe) and update from 5.0 to 5.01 went smoothly on my N5.

only hiccup I ran into was that the factory image the toolkit downloaded was incomplete (zip file was incomplete). I just dl'd the factory image from google and extracted it into the proper dir and the flash went fine.

if anyone gets an e0CD error check the zip file and see if it is ok.
[Nexus 5 Android Development] WugFresh:
Site is temp down. For mirrors: https://plus.google.com/113329792100896065459/posts/cTJeV68ChFJ

{{ WugFresh }}
[Nexus 5 Android Development] CuriousTux:
I've been able to use the app and go from 5.0 to 5.0.1 with the no data wipe update option. My problem is I'm trying to root now and when it trys to use the TWRP v2.8.1.0 it's asking me for my password which I"m guessing is my encryption password which is numbers and when I put it in it says it's not correct and I can't continue any further. Any suggestions on what to do
[Nexus 5 Android Development] amlamarra:
Wug, thanks SO much for making this. I've been having a bit of a problem though.

My phone was encrypted before I updated to Android 5.0. I can't root the phone with your toolkit yet (at least not when I tried a week ago). Anyway, I decided to backup & wipe the phone to start fresh. Last weekend I was able to backup just fine. However, I didn't have time to wipe & restore the phone. Now I'm backing up again but getting 0 MB backup files. Do you know what's going on? I don't have any custom ROMs and I haven't been able to update to Android 5.0.1 OTA.
[Nexus 5 Android Development] azlan96:
Was trying to unroot properly so that I can update to 5.0.1 without an issue, already ticked No Wipe and Force flash. NRT detects ADB fine but not fastboot, It says fastboot device was not found. but when using a terminal, fastboot device can easily be seen.
[Nexus 5 Android Development] wadado:
no success in flushing while bootloop

Hi,

I am on 5.0.1

TWRP

something went wrong after installing a zip file.

so I got into bootloop.

tried to install the 5.0.1 via the toolkit.

something is not working.

see attched photo.

What should I do?
[Nexus 5 Android Development] donnabelmartie:
Did you try to press any key?
[Nexus 5 Android Development] WugFresh:
Enable force flash and repeat. Option can be found in toolkits options menu.
[Nexus 5 Android Development] wadado:
I was thinking of using the force flash but the warning seemed a bit too....

So I used the ADB method and all is well.

Now I wonder if I should use the Toolkit to root and install TWRP,

I've read in other forums that Chainfire's Superuser is not quite ready for the 5.0.1.

What say you?
[Nexus 5 Android Development] michianamcr:
Use chainfire's beta 2.40 with 5.0.1

---------- Post added at 09:10 PM ---------- Previous post was at 09:05 PM ----------

Use 2.8.2.0 instead of 2.8.1.0 for use with encryption. NRT doesn't seem to know about 2.8.2.0 for the nexus 5, but you can use the advanced menu and choose the file manually to flash to recovery after downloading it outside of NRT.
[Nexus 5 Android Development] donnabelmartie:
So if ever problems are encountered, just do force flash?

Don't worry, the developer of the toolkit is really trusted and he has put a lot of work and still is, so there's no room for such (worry and all). Moreover, [MENTION=3110798]WugFresh[/MENTION] is very nice and helpful.

I just flashed 5.0.1 the other night and rooted as well. 2.37 works flawlessly :)

Twrp should work fine as long as no encryption.
[Nexus 5 Android Development] WugFresh:
Thank you :)

I will try and make the warning message seem less scary.

Force flash is entirely safe, it just flashing the img files individually. It's only "dangerous" if the user mistakenly picked the wrong device. As long as you selected the correct device, then force flash will overcome a lot of potential issues, like the "missing system.img" error, or any issues about 'required file versions'.

Regarding v2.40 SuperSU. Just hit "Update" in the kit, and in the toolkit options disable "use beta supersu". < Beta was set as the default option in v1.9.9 because it was released at a time when Chainfires beta's were all that worked on Lollipop. This option will not be default in v2.0.0, since these new SuperSU's are [Stable] status.

The TWRP stuff is tricky. openrecovery-twrp-2.8.2.0-hammerhead.img is built to work with encryption, but it has a bug where it will just boot to system (if mtp was enabled prior to flashing) rather than TWRP due to a kernel panic. For that reason I have kept openrecovery-twrp-2.8.1.0-hammerhead.img as the default (doesn't work with encryption). I have been hoping TWRP would release a fix by now, but they haven't. I can't knowingly include an unstable/bug version of TWRP in the kit.

If you are encrypted, you can try to flash that openrecovery-twrp-2.8.2.0-hammerhead.img, and use that to root.

Cheers.

{{ WugFresh }}
[Nexus 5 Android Development] Sinistar83:
OTP update problems.

I just updated to the v1.9.9 version of the tool to updated my stock/unlock/rooted Android 5.0 to 5.0.1: hammerhead LRX22C from LRX21O using ZIP file linked from here http://www.androidpolice.com/2014/12/15/flash-all-the-things-lollipop-ota-update-zip-file-roundup/

Having issues with the ADB Sideload OTA update portion of the tool, after I select the ZIP and choose the option on the script that I'm unlocked, it reboots with the screen with the android on its back with exclamation point. The script popup window says its the prescreen to stock recovery. So I hold down Power and Volume Up, and the Nexus 5 and the menu never comes up to let me select apply update from ADB, it just keeps rebooting with the Google logo with the unlock icon.

Any ideas what's going on? I have the the correct phone model selected in the program.

Thanks in advance.
[Nexus 5 Android Development] WugFresh:
Sounds like you are doing the button combination incorrectly:

While holding the*Power*button, tap the*Volume Up*button once.

You don't hold them both down together at the same time simultaneously.
[Nexus 5 Android Development] wadado:
Try:

while holding the power, just tap (don't hold....just press & release) the Volume up button.

It should take you to the menu.

Sometimes you might need to tap more than once.

Once it took me 10 taps. Someone reported 38 times.

---------- Post added at 07:59 AM ---------- Previous post was at 07:05 AM ----------

I just noticed that the twrp manager in play store was fixed for flashing recovery on 5+.
[Nexus 5 Android Development] Sinistar83:
Thanks! That worked!

Though after I chose the ZIP I downloaded ( http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-LRX21O.785a2f7a.zip ) and tried to apply the update from ADB, got an error

"/system /bin/install-recovery.sh" has unexpected contents.

E:Error in /sideload/package.zip

(status 7)

Installation aborted.
[Nexus 5 Android Development] WugFresh:
Means your system is modified. If you were rooted or anything, this would happen. Lollipop checks the entire system blob. Use flash stock + unroot with 'force flash " and 'no wipe' mode enabled.
[Nexus 5 Android Development] occtec:
[MENTION=3110798]WugFresh[/MENTION] just an update TWRP Recovery has finally been fixed ? and now updated to version 2.8.3.0 ?
[Nexus 5 Android Development] WugFresh:
Woot. Will add the second I get back from the gym. Crushing deadlift PR's right now! :)
[Nexus 5 Android Development] occtec:
Haha, half your luck! Don't workout to hard ?
[Nexus 5 Android Development] Sinistar83:
Thanks for the reply Wugfresh, but from the main NRT window in v1.9.9 I see an Flash Stock & Unroot button but when I click on it, it shows the popup warning about it will completely wipe the device. I'm not seeing the force flash or no wipe option.

Also, there's a whole thread on the Google Support forums here: https://productforums.google.com/fo...ooter#!topic/nexus/svgo7hsNMMQ[201-225-false]

about the 5.0.1 Update not working for a lot of Nexus owners (both rooted and non-rooted). Apparently there's a 13 meg "bad" OTA update and a 35 mg update that's supposed to work, but I haven't found a good download ZIP file for the 35 meg "correct" update yet.
[Nexus 5 Android Development] wadado:
" I'm not seeing the force flash or no wipe option."

They are in the options menu.
[Nexus 5 Android Development] wadado:
no SU binary installed

mistake
[Nexus 5 Android Development] c4sh:
Quick question, I wanted to upgrade my rooted nexus 5 to 5.0.1 So I used the NRT to do a backup both a regular app+data as well as a system app + data. However when I went to restore the regular app+data I noticed most of my data for my apps were there except for whatsapp (my most needed) I was thinking to try and restore the system app data backup and see if that made a difference? Would this not work since I am now on a different version? (5.0.1) Also any insight on why it may not have backed up my whatsApp this time?
[Nexus 5 Android Development] WugFresh:
Android backup files backup free apps + all app data. If I remember correctly, whatsapp was once a paid app? If so, you may have to download the app from the playstore first. Then restoring your ab file should restore its data. I don't think your data for whatsapp will be in the system one. Nor is recommended to restore system data from legacy versions of android to newer versions.
[Nexus 5 Android Development] rickyq12:
Ha...

Keeping up with XDA and hitting the gym...awesome.

Keep up the great work with Android and the gym WUG.
[Nexus 5 Android Development] c4sh:
Thank you for your response. Yes it was a paid app previously, however The app was installed through the google backup after my new flash of 5.0.1. I just found it strange because previously when I restored a backup that was done through NRT on 5.0 about a month ago it had saved as well as restored my whatsapp perfectly. Which is why I was wondering if I did something wrong. Lucky for me I did a titanium backup of my system last month which included my whatsapp data so I just restored that so at least I have my messages up to a month ago. I also did a nandroid backup through twrp so I guess if I really wanted to I could restore that and then do a titanium backup of my system and flash stock unroot etc. all over again. I mainly did the update just to get rid of that OTA notification. So folks it's a good idea to do a titanium backup instead of fully relying on the ab backup!

TL;DR I used NRT backup and restore option it had saved everything except for whatsapp, If you don't already you should use titanium backup in the future as it saves and restores everything like a boss.
[Nexus 5 Android Development] WugFresh:
Yeah. Google's adb backup is really not the best. I wish it would give you a detailed status report at the end or something, it really keeps the user in the dark. I have been using titanium backup since my first android device, its what I rely on as well. I use NRT for adb backup sometimes for simple batch restore operations, but Titanium backup gives you more control and reliability.
[Nexus 5 Android Development] donnabelmartie:
Tried avoiding to download the twrp 2.8.3.0 but I guess though the toolkit performed its job, the locking, unlocking, and rooting were not successful. Like when doing the unlock script, it didn't ask me to choose yes to unlock the boot loader and when rooting, SuperSU and busybox were not installed. So I guess all files should be updated first...