[Toolkit] Wug's Nexus Root Toolkit v2.1.4 [Updated 01/16/16]: Nexus 4 Thread

[WugFresh]

Any external link to 1.6.6?
Goo.im is killing me...

Mediafire: http://goo.gl/9sBdIO
Dev-host: http://goo.gl/0pRaXT

Enjoy! ^_^

{{ WugFresh }}

 

[elyashiv1994]

i used 1.6.6 and i have the same problem...supersu dont find su binary and can't install it....
its also said that it will install custom recovery but i dont want how i check which recovery i have?

 

[WugFresh]

i used 1.6.6 and i have the same problem...supersu dont find su binary and can't install it....
its also said that it will install custom recovery but i dont want how i check which recovery i have?

Check the options menu. Not sure why you are having that problem. If the supersu zip gets flashed then you should have root on your n4.

{{ WugFresh }}

 

[elyashiv1994]

Check the options menu. Not sure why you are having that problem. If the supersu zip gets flashed then you should have root on your n4.

{{ WugFresh }}

what to check in the options?
and its inatall me custom recovery?

 

[WugFresh]

Its important to note that based on user feedback, it appeared that temp booting twrp 2.6.0.0 on 4.3 nexus4 didn't work, so I modified the toolkit to also be able to use flashed recovery. So twrp will get flashed to complete the procedure and if you don't have the flash custom recovery checkbox checked, then afterwards the script will reflash stock recovery.

This option can be changed in the toolkits options menu when new twrp file becomes available.

{{ WugFresh }}

 

[imeem]

I'm planning to go back to full stock 4.2.2. and then update to 4.3 vita OTA. Will i lose everything on my " SD card " whne i go back to stock?

 

[WugFresh]

I'm planning to go back to full stock 4.2.2. and then update to 4.3 vita OTA. Will i lose everything on my " SD card " whne i go back to stock?

Yes, unfortunately for the Nexus line of devices they don't have an sd-ext partition, so everything gets wiped. Backup your important data first.

{{ WugFresh }}

 

[andrewk2x]

Hello,i have full stock 4.3 from OTA..With this tool can i have full backup(apps,sd files),then unlock bootloader,root my device and restore my files??I will have any problem??

 

[parmijo11]

Hello,i have full stock 4.3 from OTA..With this tool can i have full backup(apps,sd files),then unlock bootloader,root my device and restore my files??I will have any problem??

I'm wondering the same, just got my nexus a week ago so these tools are new to me. Thanks in advance for any help.

Sent from my Nexus 4 using Tapatalk 2

 

[aaatoel]

Its important to note that based on user feedback, it appeared that temp booting twrp 2.6.0.0 on 4.3 nexus4 didn't work, so I modified the toolkit to also be able to use flashed recovery. So twrp will get flashed to complete the procedure and if you don't have the flash custom recovery checkbox checked, then afterwards the script will reflash stock recovery.

This option can be changed in the toolkits options menu when new twrp file becomes available.

{{ WugFresh }}

There weren't any issues with this so far, right? I mean with the whole re-flashing of the stock recovery.

Great job by the way!

 

[david251]

Just got a second nexus 4 last night and let it update OTA to Android 4.3.

I already had NRT on my pc because I used it to unlock/root my first Nexus 4 that was on Android 4.2.2 - great, great tool!! Anyway, I opened NRT today and it updated. Chose my phone from the dropdown and chose Android 4.3.0 Build JWR66V.

Unlocked the bootloader fine, as far as I can tell. Went to root it, and it seems to go through the process of rebooting and giving messages of pushing files, rooting, etc - but toward the end, the phone shows Android laying on it's back with the hood open and a red triangle with an exclamation mark. Stays there for 2 to 3 minutes, then reboots.

Afterward, the phone seems to work fine, but there is no bootloader and I have no root access. I've tried it several times, both with the custom recovery option checked and unchecked.

So.... what am I doing wrong?

 

[paul_viado]

Just got a second nexus 4 last night and let it update OTA to Android 4.3.

I already had NRT on my pc because I used it to unlock/root my first Nexus 4 that was on Android 4.2.2 - great, great tool!! Anyway, I opened NRT today and it updated. Chose my phone from the dropdown and chose Android 4.3.0 Build JWR66V.

Unlocked the bootloader fine, as far as I can tell. Went to root it, and it seems to go through the process of rebooting and giving messages of pushing files, rooting, etc - but toward the end, the phone shows Android laying on it's back with the hood open and a red triangle with an exclamation mark. Stays there for 2 to 3 minutes, then reboots.

Afterward, the phone seems to work fine, but there is no bootloader and I have no root access. I've tried it several times, both with the custom recovery option checked and unchecked.

So.... what am I doing wrong?

you have a bootloader, you meet you have no recovery. go to the cmd prompt and manually push recovery through fastboot.

 

[david251]

As far as I can tell, I have no bootloader. If I hold the vol-down/power, it brings me to a start screen. At the top, "Start" is in green. Using the volume key to scroll, "Restart Bootloader" and "Recovery Mode" is in red - pushing the power on either of these returns me to the original "Start" screen. At the bottom of that screen, it does list "BOOTLOADER VERSION - MAKOZ20i" - but I can't get into a bootloader like can on my other rooted Nexus 4.

Maybe I'm stupid - just telling ya what I'm seeing.

Thanks for the reply.

 

[flava69]

As far as I can tell, I have no bootloader. If I hold the vol-down/power, it brings me to a start screen. At the top, "Start" is in green. Using the volume key to scroll, "Restart Bootloader" and "Recovery Mode" is in red - pushing the power on either of these returns me to the original "Start" screen. At the bottom of that screen, it does list "BOOTLOADER VERSION - MAKOZ20i" - but I can't get into a bootloader like can on my other rooted Nexus 4.

Maybe I'm stupid - just telling ya what I'm seeing.

Thanks for the reply.

just had same problem mate,not sure wot to do?

 

[ashik992]

Mediafire: http://goo.gl/9sBdIO
Dev-host: http://goo.gl/0pRaXT

Enjoy! ^_^

{{ WugFresh }}

Thanks.
I already got it form your thread in Nexus 7 (2013).

 

[maigre]

Just got a second nexus 4 last night and let it update OTA to Android 4.3.

I already had NRT on my pc because I used it to unlock/root my first Nexus 4 that was on Android 4.2.2 - great, great tool!! Anyway, I opened NRT today and it updated. Chose my phone from the dropdown and chose Android 4.3.0 Build JWR66V.

Unlocked the bootloader fine, as far as I can tell. Went to root it, and it seems to go through the process of rebooting and giving messages of pushing files, rooting, etc - but toward the end, the phone shows Android laying on it's back with the hood open and a red triangle with an exclamation mark. Stays there for 2 to 3 minutes, then reboots.

Afterward, the phone seems to work fine, but there is no bootloader and I have no root access. I've tried it several times, both with the custom recovery option checked and unchecked.

So.... what am I doing wrong?

I had the EXACT same problems, so this is not an isolated event. But it ran deeper than using NRT with those non-results. I tried to use fastboot on a Mac from the command line to root. I've done that and used NRT multiple times with minimal difficulty on four different Nexus devices over the last year. But 4.3 has given me all sorts of problems with a pair of N4s.

After using 1.6.4 to go to a stock installation of 4.2.2 the other day so that I could do the 4.3 OTA (I couldn't successfully do the OTA, even after reflashing stock recovery and kernel — I'd been using Franco Kernel.), I couldn't flash custom recovery from the command line on the Mac, couldn't do it by any of the interface choices with NRT and couldn't reroot with NRT as per david251's problems. Finally, I was able to install TWRP custom recovery from the command line through NRT. Then, the rest was easy enough through TWRP. But that's after hours of failure on various levels and going so far as to completely return to stock, unrooted and locked again.

Now, I want to update another N4, but I'm fearing major hassles because it's been my daily driver the last 5 months and I don't want to have to start over again if I can avoid it. But it won't take an OTA, even after flashing stock recovery and stock kernel. In the meantime, since those flashes, I've had occasional slow, laggy performance. Really slow. At least I have and will update a backup and have found a road to success with the N4 I mentioned above.

---------- Post added at 03:41 PM ---------- Previous post was at 03:28 PM ----------

david and flava posted since mine. Both of you should try installing custom recovery via the command line from NRT. That's what worked for me.

Get the device into fastboot. Launch CMD Prompt from the Advanced Utilities window of NRT. Then, from the command line that appears, navigate down to the /Recovery_Custom/TWRP dir or the folder for whichever custom recovery you want to install.

From there, run the following command:

fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img

That's assuming you're using TWRP recovery.

After that, reboot into recovery and use TWRP to flash a zip. Navigate to the !ReadyToFlash/root_files folder on the N4. Select SuperSU and Busybox and install them. Then, reboot the phone. There's a command to do that in TWRP. When you're booted back up, you should be rooted. Run SuperSU and Busybox and you'll be good to go.

If you need more detail, ask. I'm doing this from memory, so some of my wording may be a bit off.

 

[david251]

Finally got mine done (sort of). I can tell you what I did, but not why it worked. Anyway, I ran a flash stock/unroot (everything I mention was through NRT). Powered the phone off, then held the vol.down/power keys which brought me to the start screen I mentioned earlier. Restart Bootloader and Recovery were still in red text, however, pushing the power on the recovery screen did take me into TWRP - so I got that. Rebboted and got a notice that SuperSU had an update, so I got the update but still didn't have root access. Went back to NRT and ran the root again with the custom recovery option checked (I figured... "why not.") It ran through the process again, but this time it did briefly go into TWRP during the process, which it hadn't done that before. Rebooted the final time of that process and got a notification this time that Busy Box had an update. Updated it, installed it and... I have root access.

So now I have TWRP and root access, but still no bootloader that I can get into. Even using Quick Boot to reboot into bootloader won't take me there. Also, when my phone is on and I push the power button, I'm given the option to turn the phone off or put it in airplane mode, but no option to reboot is given as it is on my other nexus 4.

Anyway, hope this will help someone out or inspire ideas.

 

[Dany-69]

As far as I can tell, I have no bootloader. If I hold the vol-down/power, it brings me to a start screen. At the top, "Start" is in green. Using the volume key to scroll, "Restart Bootloader" and "Recovery Mode" is in red - pushing the power on either of these returns me to the original "Start" screen. At the bottom of that screen, it does list "BOOTLOADER VERSION - MAKOZ20i" - but I can't get into a bootloader like can on my other rooted Nexus 4.

Maybe I'm stupid - just telling ya what I'm seeing.

Thanks for the reply.

Finally got mine done (sort of). I can tell you what I did, but not why it worked. Anyway, I ran a flash stock/unroot (everything I mention was through NRT). Powered the phone off, then held the vol.down/power keys which brought me to the start screen I mentioned earlier. Restart Bootloader and Recovery were still in red text, however, pushing the power on the recovery screen did take me into TWRP - so I got that. Rebboted and got a notice that SuperSU had an update, so I got the update but still didn't have root access. Went back to NRT and ran the root again with the custom recovery option checked (I figured... "why not.") It ran through the process again, but this time it did briefly go into TWRP during the process, which it hadn't done that before. Rebooted the final time of that process and got a notification this time that Busy Box had an update. Updated it, installed it and... I have root access.

So now I have TWRP and root access, but still no bootloader that I can get into. Even using Quick Boot to reboot into bootloader won't take me there. Also, when my phone is on and I push the power button, I'm given the option to turn the phone off or put it in airplane mode, but no option to reboot is given as it is on my other nexus 4.

Anyway, hope this will help someone out or inspire ideas.

What are you talking about man? -__-'
Someone already said you that you're already looking at the "bootloader", but it seems you don't want to understand.
That screen with the big android lying down, all the info, the green "Start", the red "Restart Bootloader", the red "Recovery mode" and the white "Power off".. THAT is your bootloader, even known as fastboot mode.
And if you had no bootloader, you could serenely hurl your N4 out of the window because it wouldn't be able to do ANYTHING, an event even known as HARD BRICK and that can be solved only by an hardware flashing procedure called "Jtag", or maybe with some qualcomm tool..
So please stop soiling the 3d with questions already answered and certainly inappropriate for the "original android development" section..
Then dont' complain if the developers vanish in the dark of the night, tired of answering to the same already answered noob questions.

About the problems with the recovery, every toolkit on XDA seems to have some problems with the 4.3
I hope in a fast fix, but you can temporarily use the fastboot command to flash the recovery, and then flash the zip for root.

 

[david251]

What are you talking about man? -__-'
Someone already said you that you're already looking at the "bootloader", but it seems you don't want to understand.
That screen with the big android lying down, all the info, the green "Start", the red "Restart Bootloader", the red "Recovery mode" and the white "Power off".. THAT is your bootloader, even known as fastboot mode.
And if you had no bootloader, you could serenely hurl your N4 out of the window because it wouldn't be able to do ANYTHING, an event even known as HARD BRICK and that can be solved only by an hardware flashing procedure called "Jtag", or maybe with some qualcomm tool..
So please stop soiling the 3d with questions already answered and certainly inappropriate for the "original android development" section..
Then dont' complain if the developers vanish in the dark of the night, tired of answering to the same already answered noob questions.

About the problems with the recovery, every toolkit on XDA seems to have some problems with the 4.3
I hope in a fast fix, but you can temporarily use the fastboot command to flash the recovery, and then flash the zip for root.

My bad, bro. But I did give a disclaimer in the post stating that maybe I'm stupid - so if you got bent out of shape... I warned ya. My experience with this thing is extremely limited and I thought perhaps the person who said I had a bootloader misunderstood what I was trying describe, mostly because of my own inability to communicate it. But I'll tell ya why I was thinking I didn't have one. The last time (a few months ago?) I was messing with my Nexus - my first one that still has 4.2.2 on it, if I went into bootloader, it looked completely different - white background and as I pressed the volume keys to navigate, it moved down a list on the same screen rather than changing screens. So I guess I was expecting to see that again. However, I now see what you guys are saying and appreciate the lesson.

 

[maigre]

My bad, bro. But I did give a disclaimer in the post stating that maybe I'm stupid - so if you got bent out of shape... I warned ya.

I wouldn't worry about it, david251. There's no reason for anyone to be insulting. You had a question and looked for an answer. That's not my definition of stupid. This stuff can be a little complicated. Then, when it doesn’t work like it might, as we're seeing with 4.3, it's all the more difficult.