yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] wiswis:
does this work with windows 8
[Nexus 4 Original Android Development] Persechini:
Yes it does, I've done all my unlocking and rooting in win8 with this toolkit
[Nexus 4 Original Android Development] lotherius:
Why wouldn't it?

For the record it does.
[Nexus 4 Original Android Development] RASTAVIPER:
2 days ago that I had to unroot and reroot, Supersu was already installed at the end.

Didn't check if it was 1.6 though, as now I have this version for sure and I don't remember if I did a Play store update or not.

Unleashed by my Nexus 4
[Nexus 4 Original Android Development] Splaktar:
I just came looking for the same information, but the last answer to that appears to be from Jan 2013: http://www.wugfresh.com/faq/is-there-a-mac-nexus-root-toolki/

To summarize, the application was written in AutoIt which only runs on Windows. The creator was hoping to re-write the application in another language, but there is no ETA.
[Nexus 4 Original Android Development] steviemch:
Excellent toolkit, rooted and installed TWRP with no problems, thanks!
[Nexus 4 Original Android Development] scrumpypaul:
Hello

Very quick q - will this work on my wifes new Nexus 4 which we have updated to 4.3?
[Nexus 4 Original Android Development] RASTAVIPER:
It works with any Nexus.

Unleashed by my Nexus 4
[Nexus 4 Original Android Development] scrumpypaul:
Thank you Rastaviper - all rooted and ROM'd with Liquid Smooth.
[Nexus 4 Original Android Development] aaatoel:
I tried paranoid android but I want to return back to stock rom. I am trying to do it, but the operations don't seem to complete. I have downloaded to occam-jwr66y-factory-74b1deab.tar from the google site, the toolkit seems to recognize it and after a few seconds my device reboots into fastboot mode (the one with the big green robot lying down with my device specs on the bottom) and this command prompt window opens:

I have waited for more than 15 minutes but nothing seems to happen. Any advice on how to proceed? Thanks! :)
[Nexus 4 Original Android Development] reo4ua:
Just did mine yesterday and was a breeze thanks to Wug's Toolkit.
[Nexus 4 Original Android Development] ritchea:
I believe this can be corrected by enabling force flash mode in the toolkit's options menu. After enabling repeat the flash.
[Nexus 4 Original Android Development] edbertin:
You are right i faced same issue before.

This msg appears when you don't meet the requirements to flash stock, like wrong bootloader (ie. :Android 4.3 needs 4.23 bootloader and so on) .

Using force flash mode will bypass the checks.
[Nexus 4 Original Android Development] vibrantliker:
Unlock bootloader

I'm new to the N4, so wondering if the N4 comes unlocked, why do you have to unlock bootloader. Is that different?
[Nexus 4 Original Android Development] RASTAVIPER:
Unlocked phone is the carrier company, meaning you can use any SIM around the world.

Unlocked bootloader is totally other issue, concerning safety of data and system integrity of device.

Unleashed by my Nexus 4
[Nexus 4 Original Android Development] aaatoel:
A big thank you to both for taking your time to help me. I actually used this very easy and effective method to make a clean install and gain root access. :)
[Nexus 4 Original Android Development] samuelrf:
delete please

Enviado desde mi Nexus 4
[Nexus 4 Original Android Development] wiswis:
i have a question, if i ever decide to go back to stock do i just use the toolkit or do i install some other files?
[Nexus 4 Original Android Development] aaatoel:
Just look two posts above you, mate.
[Nexus 4 Original Android Development] punk2x:
Root works great on JWR66Y :good:
[Nexus 4 Original Android Development] NYLimited:
FYI - TWRP now includes an option to encrypt the created backups with a password.

You may wish to consider adding this switch to the toolkit..
[Nexus 4 Original Android Development] steviemch:
Yep it's different, the N4 comes carrier unlocked, meaning you can use it with any provider, the bootloader loads the operating system. You need this unlocked to root.
[Nexus 4 Original Android Development] killswitch11:
OK, I'm confused. I was rooted and used the toolkit to return to stock and flash the JWR66Y build. When I use the root and custom recovery option, my phone does not gain root access. I've tried several times, but no luck. I am definitely unlocked, but no joy using toolkit. Did I miss something?
[Nexus 4 Original Android Development] ctbearz:
Android 4.3 Build JWR66Y

After Rooting (w/ Custom Recovery selected), SuperSU gives me the following error when opening app:

"There is no SU binary installed and SuperSu cannot install it. This is a problem.If you have upgraded to 4.3 you need to manually re-root.."

Went to update the app in Play Store to version 1.65 and still same error. App store page now shows the following disclaimer:

"NOTE: If you just upgraded to Android 4.3, you need to manually re-root, as just updating the app may not suffice."

I reflashed to stock/unroot and tried rooting again with the same results. How should I proceed from here to get properly rooted on 4.3 Build JWR66Y? TYIA
[Nexus 4 Original Android Development] RASTAVIPER:
Do you have latest version of toolkit installed?
[Nexus 4 Original Android Development] Javierinnn:
Same here, problems with SU after rooting
[Nexus 4 Original Android Development] ctbearz:
Yep..version 1.7.2, everything is updated for the toolkit as well.
[Nexus 4 Original Android Development] RASTAVIPER:
In my case , first I did the Unroot through Supersu application, then updated to 4.3 and then rerooted and installed TWRP recovery through toolkit.

Unleashed by my Nexus 4
[Nexus 4 Original Android Development] ctbearz:
I started out with completely stock 4.3 Build JWR66Y (unlocked, no root). I then proceeded to use the tool kit to root + install custom recovery and that resulted in SuperSU throwing the binary missing error:

There is no SU binary installed and SuperSu cannot install it. This is a problem.If you have upgraded to 4.3 you need to manually re-root..
[Nexus 4 Original Android Development] _suke_:
Re-root again with toolkit without install custom recovery, for me it´s work.
[Nexus 4 Original Android Development] NYLimited:
Make sure your custom recovery is up to date and working.

Download

Chainfire's SuperSU

(flashable zip file)

Install through the custom recovery (CWM or TWRP)
[Nexus 4 Original Android Development] ctbearz:
This is a new phone. Everything is stock and so it is running Stock Recovery Mode. Only the bootloader is unlocked at this point.
[Nexus 4 Original Android Development] NYLimited:
In your first post you said you installed custom recovery.

How did you get back to stock recovery again?

Anyway, you can probably use the toolkit (or some other method you wish) to install a custom recovery and root the device.

Don't forget to check the box for Custom recovery!

If after that you get the SuperSU error again make sure you have SuperSU 1.65 flash-able (I gave you the link already) and use your custom recovery to flash it. Check it by booting the device and running SuperSU.

Install/update Busybox and you should be good to go..

That is, assuming you actually want to root the device...............
[Nexus 4 Original Android Development] ctbearz:
I just checked and it is only stock recovery...perhaps it did not install properly. I did reflash back to stock rom/unroot, which is the state the phone is in now (if that makes a difference).
[Nexus 4 Original Android Development] NYLimited:
If your bootloader is still unlocked you can simply do the above steps and gain root quickly and (relatively) pain free. :)
[Nexus 4 Original Android Development] ctbearz:
Thank you sir! It did indeed work as you said. Now I finally have proper root and busyboy setup and can proceed to setup LTE for t-mobile.
[Nexus 4 Original Android Development] IronJacob:
Hi.

I need a quick help please. I just unlocked my nexus4 with latest android version, and trying to root it, but it is about 15-20 minutes always on "pushing root files to your device...". Could someone help me please?
[Nexus 4 Original Android Development] Rev4:
So how did u actually solve this issue?

I^m having the same problems here unlocked and rooted but SuperSU binary cannot install.

Im on 4.3.
[Nexus 4 Original Android Development] RASTAVIPER:
If you managed to flash custom recovery, just download Supersu from previous posts and flash it through recovery.

Then run Busybox, install required files and you are ready!

Unleashed by my Nexus 4
[Nexus 4 Original Android Development] ctbearz:
I did exactly what RASTAVIPER and NYLimited are suggesting.
[Nexus 4 Original Android Development] NYLimited:
TWRP 2.6.3.0

FYI -

TWRP 2.6.3.0

has been posted for mako (also tilapia, etc).

It fixes the SuperSU permissions nag on exit (among other things).
[Nexus 4 Original Android Development] PlacidoFerreira:
ADB device was not found.

The same is happening with me. In step 2, I installed the Universal drivers. However, when I click "Full Driver Test" message appears: ADB device was not found.

What did you do to solve this problem?

Help me. :fingers-crossed:
[Nexus 4 Original Android Development] nemanja066:
Try PDA Driver. Works for me! :)
[Nexus 4 Original Android Development] ritchea:
Setting up ADB can be tricky, but first thing to check is to make sure you have ADB enabled in your Nexus settings. Is your cable a problem? If you're good on those, you probably need to check your computer to remove any android drivers and start again.
[Nexus 4 Original Android Development] PlacidoFerreira:
ADB enabled

What should I do to enable or How do I check if I have ADB enabled in settings my Nexus? ;)

The cable is perfect. Makes one day got my Nexus :victory:
[Nexus 4 Original Android Development] ritchea:
Settings>developer's options then USB debugging.
[Nexus 4 Original Android Development] RASTAVIPER:
Make sure that the cable that you are using is the original one from the package of the device.

Unleashed by my Nexus 4
[Nexus 4 Original Android Development] lotherius:
For some (unknown to me) reason, many of us have found that to get ADB working, you also have to change Storage Settings USB Computer Connection from MTP (media) to PTP (camera) mode before the device will show up on ADB.
[Nexus 4 Original Android Development] qbanways:
So I got everything to work after going through this forum. I couldn't get the ADB drivers using option 1, so I did option 4, raw drivers, since I have windows 8. Once I did that I was able to unlock and root. Now my problem is that I cant mount the phone to transfer files (like rom and su update). I try putting it in MTP, but it doesn't do anything. The only option I have is PTP which only gives me access to the camera folders. When I plug the phone to the pc, I can see the device in device manager but I am unable to access the device to transfer files. I try using the recovery menu to mount the device, but that did nothing.

Any advice?
[Nexus 4 Original Android Development] datboy143:
http://xdaforums.com/showthread.php?t=2232471&page=2

Post #14
[Nexus 4 Original Android Development] mo976:
I used the toolkit for two phones the other day. For my nephew, I went the whole full backup, root and restore route. For my wife's brand new Nexus 4 a straight unlock/root. Both went smooth as butter and the whole program in general worked like a charm.

Thanks Wug!:D
[Nexus 4 Original Android Development] kahila:
I recently watched a video about This program which had All the necessary information about rooting. Now I'm unable to find it. Is anyone familiar with this video? Thanks!
[Nexus 4 Original Android Development] Blackherted:
http://www.youtube.com/watch?v=ukTPmVnFD4E

http://www.youtube.com/watch?v=COZL_jUH_BE&list=PLXre9DsZzDoBt7ReUwwkeERr-qDyFK9zF

and you can also just type "wugfresh" in youtube and watch whichever one you want
[Nexus 4 Original Android Development] cmajetic:
OLD PROBLEM:

thanks for the tool, everything well explained but i have a problem:

the driver test fails even if i see in device manager "Android Phone > Google Nexus ADB Interface"

so i guess it should work even if the test fails everytime?

i am sure that i deleted all old drivers, installed the ones from koush, they were recognised by windows and the device shows what i wrote above. i am also using the right cable and so on, using the latest 4.3 and selected correctly, windows 7, 64 bit

EDIT: needed to change from MTP to Camera, then everything was alright
[Nexus 4 Original Android Development] sir_fz:
I used Nexus 4 Toolkit V2.0.0 to root my new 4.2.2 Nexus 4, then I got the prompt to upgrade to 4.3.0 which I did. Now I lost my root, tried to use Wug's Nexus Root Toolkit to re-root my device but it fails. Always stuck at the Google logo after exiting Fastboot and never boots (I have to power down and then power up for it to boot normally). After the process finishes, I check SuperSu which says that there is no SU binary installed. How can I fix that?
[Nexus 4 Original Android Development] RASTAVIPER:
Download the su zip that is mentioned before and flash it through custom recovery to root again.

Unleashed by my Nexus 4
[Nexus 4 Original Android Development] hardrockk:
Good.....thank you

Enviado desde mi GT-I9001 usando Tapatalk 2
[Nexus 4 Original Android Development] lalec:
This toolkit is absolutely badass. Not only for unlocking and rooting but also great for fixing soft bricked devices.

Sent from my SGH-M919
[Nexus 4 Original Android Development] Svid:
Trying to update to 4.3, kickes me out on baseband flash

EDIT: Manually flashed latest radio, now works fine (i hope)
[Nexus 4 Original Android Development] Blackherted:
If I Press "Install Custom Reovery" Which version of TWRP will it install?
[Nexus 4 Original Android Development] RASTAVIPER:
Latest 2.6.3

Unleashed by my Nexus 4
[Nexus 4 Original Android Development] victortangocharlie:
It installs TWRP 2.6.2.0 and not 2.6.3.0
[Nexus 4 Original Android Development] Redmed427:
Well, I have been trying to get it to work all afternoon, No go. When it tries to boot twrp the screen just stays black and the phone reboots itself. Any ideas?
[Nexus 4 Original Android Development] Wesleylau:
Same thing happened to me, it seems it is not able to boot into temporary TWRP recovery.

Edited: Rebooted my PC solved the problem.
[Nexus 4 Original Android Development] samuelrf:
please can you also make a Ubuntu version? I need this but in Ubuntu...:( [MENTION=3110798]WugFresh[/MENTION]
[Nexus 4 Original Android Development] flintdragon:
I'm running completely stock and unlocked. I'm trying to root the device. The ADB checker checks ok and when I go to root, every time I get to the fastboot mode screen, NRT tries to upload something to the device and waits at "Waiting for your device". On the phone, I see a "downloading..." text at the bottom and that's it. nothing happens.

Any ideas?

---------- Post added 2nd October 2013 at 12:00 AM ---------- Previous post was 1st October 2013 at 11:50 PM ----------

nevermind. I was using the wrong cable. Why would the OEM cable matter?

Next question... I'm rooted but the directions for installing busybox says to change the path from /system/bin to /xbin. Should that be /system/xbin or just straight up /xbin?
[Nexus 4 Original Android Development] nlabrad:
I have just one request.

Is it possible to remove the default focus from the "accept/cancel" buttons when a warning comes up? I was typing something in another window and the warning came at the moment i pressed space and bam, gone.

Thanks.
[Nexus 4 Original Android Development] ImperatorShade:
Best toolkit I've used. Extremely user friendly!!
[Nexus 4 Original Android Development] hx4700 user:
Thoroughly confused by size of "all apps" backup

Nexus 4 running cyanogenmod latest stable

I updated this morning to the latest version. The first backup I did was of "Backup all apps" and it was 88Mb. That did not seem a lot considering the number of apps I have. So I did it again, and the backup was 121Mb. The third time, 120Mb. Each time, the phone rebooted immediately the complete window popped up on my PC.

How can there be different sizes to the backup when I have not done anything in between?

Maybe it is the timeout. I have now changed the timeout in the Settings/Display from 2 minutes to 5 minutes, and the backup process continues a lot longer. The screen switched off after about 4 minutes, but I was able to press the on button and re-open the phone. Because the backup process takes over, I could not touch the screen to keep it alive.

THE FOURTH BACKUP IS 805MB. That is a bit different. Could there be something put in the app to at least warn that the backup was not in fact complete? If I had relied on the first three backups I did, I'd have a pointless backup. Also, the phone did not reboot after the fourth.

---------- Post added at 11:23 AM ---------- Previous post was at 11:10 AM ----------

Nexus 4 running latest stable cyanogenmod

I don't know what I am doing wrong here. I've managed to backup my apps, and SMS and Call logs and contacts.

When I try to backup the virtual SDcard, all looks to be working but then it says finished but it is 0 bytes.

Can anyone help please?
[Nexus 4 Original Android Development] norwoodesteel:
when it happened to me it was a recovery problem, went to a previous version of TWRP. the version in the toolkit works fine for me.
[Nexus 4 Original Android Development] Mohit12:
I'm doing this for the first time and so far it has gone well bar one last thing.

I unlocked it (successful), and tried to root it (also flash TWRP) and everything seemed to be going well till I opened SuperSU and it gave me an error saying "there is no SU binary installed, and SuperSU cannot install it. This is a Problem!

If you just upgraded to Android 4.3 you need to manually reroot consult the relevant forums for your device"

However, TWRP did get installed successfully and I can access it. I don't know if my device is rooted though.

Now I want to flash Paranoid Android. Should I go ahead with it without SuperSU working (or possibly even without having root)?

And is there any way to fix my error?

(I tried to use search but search isn't available at the moment)
[Nexus 4 Original Android Development] norwoodesteel:
Flashing the latest supersu.zip should work I think it's 1.65

---------- Post added at 03:27 PM ---------- Previous post was at 03:26 PM ----------

Wiping and installing paranoid would probably work too
[Nexus 4 Original Android Development] Slymobi:
I've stopped using the kit to root, I unlock bootloader and flash twrp only. As most custom ROMs include root anyway so I just need twrp to flash the ROM.

1 thing I have noticed and thought i would mention because ive not seen any comment on here is when reverting back to stock via the force flash ( because I use the older bootloader ) my device always ends up as an 8GB partition !!! its an easy fix of just factory resetting from android settings but quite annoying. Just letting you know Wug just in case it can be fixed on a future release.

Sent from my Nexus 4
[Nexus 4 Original Android Development] wiswis:
i used the nandroid backup in the toolkit, and now my nexus is stuck at a black screen and theres a window on my pc that says waiiting for the backup to complete... what should i do
[Nexus 4 Original Android Development] WugFresh:
To clarify, this is happening to you when force flashing any factory image. Or a specific build?

{{ WugFresh }}
[Nexus 4 Original Android Development] threi_:
As it is right now trying to temporarily boot a custom recovery on the nexus 4 on 4.3 (not flash but just boot) results in a blank screen. According to this thread you have to specify a kernel commandline now for it to boot properly (although it only seems to affect my nexus 4, my nexus 7 still works fine)

The new command is:

fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img

I was just wondering if this change will be implemented into the toolkit?
[Nexus 4 Original Android Development] Slymobi:
Hi wug

I've only tried with stock Google 4.3 JWR66Y build. Every time it has done it ( x4 )

Cheers.

Sent from my Nexus 4
[Nexus 4 Original Android Development] WugFresh:
I actually had implemented that in a previous toolkit version and then ended up changing it back. Based on feedback (For whatever reason), it wasn't working consistently for NRT end users. And with the help of some N4 users I tested both commands and confirmed that the basic "fastboot boot" cmd worked. The blank screen TWRP may have been related to an older TWRP version, not yet optimized for 4.3 devices.

Like I said, I have tested fastboot boot, on numerous N4 devices with success. I am not sure why you are having that issue. What version of TWRP are you using? What android build are you running on your N4? Have you tried booting the IMG from cmdline with that syntax you quoted? If not, please try it - you can use the "Launch CMD prompt" button in advanced utilities.

Cheers.

{{ WugFresh }}
[Nexus 4 Original Android Development] SweetPant:
(Help)

I have successfully unlocked my nexus 4 with this toolkit but when I tried to root (with custom recovery) it was not successful.

It says fastboot device was not found. But before I did that, I have tested driver but it said successful.

This is show in the toolkit during root process and my nexus 4 stuck at bootloader screen.

I am desperate. :(

PS: I think it might be problem with ADB driver. I tried with Universal ADB Driver given in toolkit and it didn't work too.

EDITED: I changed USB port and it now work but when I opened SuperSU it says: There is no SU library installed...
[Nexus 4 Original Android Development] NYLimited:
If you have already installed custom recovery you can just flash

SuperSU 1.65

from Chainfire's download page.

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 4 Original Android Development] threi_:
Yes I have tried using "fastboot boot" from a command line, which also gives a blank screen, same as if i try using the "boot image" or "boot temporary custom recovery" options from your toolkit currently. That is the reason I went hunting for a fix, which took me to that thread. Using the modified command, however, works for me. I've tried it with TWRP 2.6.3.0 and 2.6.2.0. My nexus 4 currently is on stock rooted JWR66Y.
[Nexus 4 Original Android Development] SweetPant:
I have tried rooting again but the SU binary problem still occurs. I strictly followed the guide given in the toolkit. Not sure what I did wrong.

I'm afraid if it's impropope root and make my phone in unstable state :(

Edited: I deselected "Custom Recovery" and clicked Root. Now the SU binary problem is gone.
[Nexus 4 Original Android Development] NYLimited:
Try installing only recovery (TWRP or CWR) and not root it.

If that is successful, use the new recovery to install the zip file I had in my previous post.

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 4 Original Android Development] WugFresh:
Thank you for the info. I really wish I knew why it works for some users and not for others. I guess the best solution would be to make it an option of which syntax to use in the toolkits main settings menu.

{{ WugFresh }}
[Nexus 4 Original Android Development] WugFresh:
I will see if I can reproduce the problem you had. Not sure why it didn't work with custom recovery checked.. It really makes no sense to me as the root procedure is identical.. It just has one extra step of flashing custom recovery. Either way, I will do some more testing.

{{ WugFresh }}
[Nexus 4 Original Android Development] threi_:
Even weirder than that is that I have no issue when I use your toolkit with my nexus 7, only when I use my nexus 4 (and yes i make sure to switch devices beforehand)
[Nexus 4 Original Android Development] ricstone:


Just used this on my Nexus 7 an it done the exact thing. Also just rerun root with recovery unchecked an it worked great.
[Nexus 4 Original Android Development] GrandMstrBud:
Latest version of 4.3 and it goes through the whole process however when I open SuperSU it fails with the message of "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

I thought it was supposed to work with the latest version?