yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] penzoilguy:
Thanks Man....really guide me through the root process :fingers-crossed:
[Nexus 4 General] pcoruganti:
Thank you much....................
[Nexus 4 General] suttaroom:
will this work for 4.2.2 ?!?!?1
[Nexus 4 General] digitallysick:
Anyway to do this without wiping the device? I would like to root while keeping everything i have as it is?
[Nexus 4 General] adbshell:
anyone knows?
[Nexus 4 General] lopri:
oncevent rifk

I am curious about it, too, although it isn't too big a deal since I don't have much on my Nexus 4 yet.

But what I would really like is to have my Nexus 4 rooted without custom recoveries. I know many here scorn at the "stock" ROM, but I had an unpleasant experience with a custom recovery in the past and if possible I would like to avoid custom recoveries. I got it done on my Nexus 7 (stock ROM, rooted, no custom recovery) but I haven't found a straight-forward guide for Nexus 4 yet. (that doesn't mention custom recoveries)
[Nexus 4 General] yuki71:
would also like to know as my buildJDQ39 is not an option
[Nexus 4 General] El Daddy:
To everyone quoted here. Use fastboot. Read the stickies in both general and Q&A. All the info you need is there. Its incredibly easy.
[Nexus 4 General] Khaiyan:
QFT.

When I first joined the Android scene (coming from an iPhone 4), I was instinctively drawn to the 'toolkits' because they offered something similar to the iOS jailbreak programs. A one-click solution. However, I have come to learn that rooting, unlike jailbreaking, is a far more delicate procedure and you cannot take shortcuts.

As a matter of fact, now that I am familiar with ADB and fastboot, I find them a lot easier and quicker to use than the toolkits! You literally just type a few lines and watch the magic happen. It's also far more rewarding than just typing a number into a keyboard.

Having said all this, I think toolkits should still be used as a fall-back option and/or for people comfortable with ADB and fastboot, so kudos to the OP for the informative video.
[Nexus 4 General] asb123:
Whats the easiest root method for Macbook's/OSX?
[Nexus 4 General] scottcwhite:
Waiting for mine to get here in the mail tomorrow so thanks for putting this together.
[Nexus 4 General] yuki71:
fastboot adb

thanks for the advice of using fastboot cmds

now rooted

thanks
[Nexus 4 General] here4info:
whats the fastboot method? is it different from this video? (on youtube page OP mentions that we have to wipe the device and I would like to avoid that)

any links?
[Nexus 4 General] fcb-1899:
Amazing tutorial!! Thanks, it really helped me :D
[Nexus 4 General] crocodanser:
Thanks, sounds like exactly what I need!
[Nexus 4 General] yuki71:
fastboot

my device bootloader was locked which when i followed this tutorial i failed at flashing

used something like oem unlock-search forum its there

but you loose everything so backup
[Nexus 4 General] idealxfit:
root?

i followed video until 15:50 and tool kit has stopped progressing. it says its waiting for usb debugging to be enable. it is. thats as fare as i can get. any suggestions. bootloader is unlocked, it think. not sure what to do next
[Nexus 4 General] vicstarman:
See the opening of the video, seconds 20-35. Jared is clear that this is just a way to get started to see if people like the whole concept of rooting, etc. I had to start there too. Learning every day.... That's the ultimate goal for us all. I've begun to gain understanding of the HOWS and WHYS through my recent sna-foo, but learning the higher-tech methods isn't for everyone who just wants to root and use the privileges therein. I'm all for learning the "old school" way... from the ground up, etc. But mskip's toolkit is flawless and fail proof. So while it may irk those who "had to learn the old fashioned way", it's simply the next wave. The way things are now. I sell Opus One to people who know NOTHING about wine every day (if they did, they wouldn't buy opus one and I'd be out of a job).

My final theory on it is, why stop at the level you feel is "appropriate"? Why not say that noobs have to go back to coding and programming, rather than the modern convenience of using Fastboot, ADB, etc? Why stop there? None of us would have fun with our devices if we couldn't access developer options to modify our Android. And if we didn't want to modify, we'd all imprison ourselves with Apple products. ;)

I don't know.... I feel like I usually go with the "we did it this way, and that's the way the kid's should have to do it" mentality in so much in my life. I'm totally an old grouch sometimes. But with this topic, I just think easier is better, and if people wanna throw Mskip a few bucks to use his superb toolkit, then why not?

Mph... catch me on a different day and I'll probably rant differently. But I just know that i'm grateful to Mskip, Jared, and others out there who helped me get a jump start on a topic I don't have all the time in the world to research and learn like a 2nd career.

Oh, and I am ESPECIALLY indebted to efrant for helping me really grasp and utilize the Fastbook / ADB / Sideloading methods to restore my janked up device recently.
[Nexus 4 General] El Daddy:
???? Didn't I just spent half an evening helping you out a few days ago? You even commented on my thread saying you agreed with me. Now this? I don't get it.
[Nexus 4 General] Caseyy:
Does this work for 4.2.2?

Thanks :)
[Nexus 4 General] jamh77:
work fine...tanks
[Nexus 4 General] tspirtle:
Yes, but you'll need to do some updates. See this post:

http://xdaforums.com/showpost.php?p=37989017&postcount=956
[Nexus 4 General] crachel:
Reading this and it's clear that you still don't quite understand what El Daddy is telling you and the reason for this is the Toolkits themselves. They muddy the water, plain and simple. There is no "old school" or "ground up" method to learn, that's a nonsense idea created by Toolkits. The Toolkits are the wrong way, the scenic route that appears easy at first but cause nothing but problems in the long run. That "jump start" you claim you're grateful for was the reason that you are now indebted to efrant for showing you the correct way. If you would have read efrant's guide from the beginning there would have been no "janked up" device. The only people who have Nexus phones and believe a "janked up" device is even a possibility are the people who use Toolkits.
[Nexus 4 General] VOLTAGEROCK:
My Nexus 4 along with the Orb comes in Monday, 2/25/2013 !!

Aww yeah. One thing that was mentioned to me from a friend who has this phone is prior to Rooting it, make sure you use it for a day or two, making sure you play around with everything you possibly can before Rooting. Don't bother customizing your folders and screens in this time as you will have to do all of that again after rooting. The reason for this is to make sure your Nexus 4 works properly stock before you go ahead to the customization stage in case you have to return it. Then you don't have to unroot with all that BS involved.

I too have a lot to learn about Android still as I was sucked into the Palm Pre with Sprint from the moment it came out. I have been an Android user since July 2012 buying the Nexus S from someone on Craigslist. I did root and flashed a ROM for the Bean back then. I also have had the Galaxy Nexus from Sprint too in August 2012. Finally, after not being able to stand Sprint after 7 years, I switched to AT&T in December and got the cheapest phone they have available in anticipation for the Nexus 4 which I finally have coming in. I currently have the Pantch Burst which isn't the worst, but i can't stand the skin they put on it. The Nexus is going to be so great and I'm trying to prepare to Root prior to the phone arriving. I do most likely need help, but Rogerpodacter in these forums is the man and he will most likely help out. I also hope that you guys can help with whatever I don't understand when the time comes.

The other thing is the Orb (or now known as the Nexus 4 wireless charger). I have been reading like a champion and have been disappointed to to find out that there are no magnets in the Orb, like the Palm Pre touchstone had, nor are there any metal discs inside the Nexus. It relies strictly on a rubberized ring to keep the Nex from falling off. Also, I read that the rings collect a lot of dust very quickly. This is a buzzkill as I had my Touchstone in my car and was hoping to replace it with the Orb so I can drive with the Nexus held in place with magnets and not have to worry about it ever falling off like the Pre. I just feel as though it's going to be a disappointment.

Oh well, I'll be back here once the phone and orb arrives and do a real review of the orb as I owned and still own the Touchstone. But this time, I just removed the discs and put it on the Pantech battery cover. I may do this to the Nex 4 if I want to ruin the clean look. At least the Nex is black whereas the Pantech is red, so you won't see the black disc cover as easily on the Nex. By the way, the induction coils where obviously removed on that disc cover as I really didn't feel like trying to get it to work like I did with the Nexus S. A quick proof of the Touchstone working with Sprint's Nexus S can be seen on You Tube here: http://www.youtube.com/watch?v=nvYxCR2MSaQ or look up voltagedingbat and search for the Nexus S working on Palm's Touchstone vid. Anyway, I've ranted enough. Pea soup everyone.
[Nexus 4 General] adbshell:
Thanks for the clarification. Will update adb and try :o
[Nexus 4 General] dpkPT:
I'm stuck in "waiting for USB debug mode to be enabled" even though its already enabled in my phone... Anyone know whats wrong? 4.2.2 Nexus, Toolkit updated

EDIT: nevermind i didnt notice that even though the toolkid finds an update it does not update automaticly, did it manually and all worked fine ;)
[Nexus 4 General] ergalle2:
Thanks for the guide :good:
[Nexus 4 General] domii666:
Thx for the great Tutorial!
[Nexus 4 General] shahrulghani:
I have a newbie question here and I'm sorry if this is going to sound silly. Here goes...

I've downloaded the toolkit and also the patch for it to be used on the 4.2.2 update. I've watched the tutorial video and I am fully confident that I can follow exactly as what was shown in the video. So far I have installed the toolkit and also the drivers on my PC. I am also able to see that my phone is already detected by my PC as the serial number for my device is appearing on top of the main menu for the toolkit.

However I am still fearful of the fact that I might brick my Nexus 4. I used to have a HTC One X and somehow I did managed to accidentally messed up the rooting process, resulting in the device being unable to boot. I did managed to fixed it by flashing the original RUU on the device. This was a really bad experience for me and I certainly do not want this to happen again as I will have no idea how to fix my device if anything goes wrong.

My question:

What could go wrong in the process explained in the video that could actually lead to my phone being 'bricked' or unable to boot?

If indeed it is bricked, is there a way for me to un-bricked it back to normal?

Thank you in advance for any replies or feedback :)
[Nexus 4 General] VOLTAGEROCK:
After now having my Nexus 4 and Orb, and loving it more than my girl. Whoops I mean not even near the love I have for her! I know she's gonna see this post now. Get to the screen of all the number prompts and go to donate and follow the instructions. Anyway, I had to donate using I believe option 24? Just follow the instructions to a T and pause the video as you do your steps. After you donate, you are given a code in your email. As far as I remember, after you donate, you have to restart the program so you can get back to the screen where it will allow you to enter your code from your email. After that, you have to restart the program and type yes when it asks you to check for updates. Mine updated to 1.7. I believe the OP gave everyone 1.3? Anyway it will then install the new version and after that you have to restart the program again as it will not only ask you if you have Version 2.1, it has three versions. I don't remember the first two, but the third one is Version 4.2.2 and you enter the number 3 on the question and hit enter. I'm sorry that I forget many steps in this process as it was one of those things that I had to to a lot of trial and error. Fortunately you don't need the phone to be plugged in until after the donating and installing of the new software. Just remember to follow what's exactly stated in the video. Unfortunately, and no disrespect to the OP, there isn't a video on the entire process showing the donating, entering the code, and updating the software and finally rooting the phone.

I should've just answered "Yes" to your post!! Just kidding. I hope my post is helpful in some sort of way. Just for clarification, you need to donate, enter the code, update the software, and run the new software following the video steps and choosing 4.2.2 when prompted. Good luck and let me know how it turns out. You guys have probably already figured it out anyway!
[Nexus 4 General] juan_carlos__007:
On the video 7:40 "It's vibrating very lovely". I wonder where all his battery juice get drained into.
[Nexus 4 General] shahrulghani:
Hi guys. The toolkit says "Adb is out of date". How do I solve this? I uninstalled the drivers and installed it back on but during the rooting process, the same message pops up. Any help here?
[Nexus 4 General] shahrulghani:
I have finally managed to root my device. The 'ADB' problem I had at home did not occur with my workstation in the office. I am now running on a rooted device :)
[Nexus 4 General] rebornsoul89:
thanks for the great help! :good:
[Nexus 4 General] xsrcivic:
This was very helpful. Thanks!
[Nexus 4 General] rorio:
Hi, i've done all the steps given in mskip's post, but the required device version and build (Android 4.2.2 Build JDQ39) doesn't show up. I'd love to post on mskip's thread but i don't have enough post to do it. Also, sadly i'm not a donator.

so probably anyone here can help me on this. thanks
[Nexus 4 General] shahrulghani:
Have you downloaded the 4.2.2 ADB?
[Nexus 4 General] rorio:
Hi, if you are referring to the files from this link

hxxp:/xxx.skipsoft.net/download/toolkit/New_adb_fastboot_files_for_4.2.2.zip

the answer is yes i have, and i have extracted the files to the 'nexus 4 toolkit' folder
[Nexus 4 General] scottcwhite:
Toolkit says it can root only up to 4.1.2

What about if we have a stock N4 on 4.2.2
[Nexus 4 General] arimus:
I need help please, I followed your video but near the end after reboot and enabling USB debugging my phone does nothing just sits there, the toolkit is waiting for USB debugging to be enabled but I did enable i put the chekc mark

what do I do next ? hope its not bricked
[Nexus 4 General] jinkly:
Hello,

I have a question after watching the video: installing the drivers procedure on your computer needs to have the phone plugged and on fastboot mode?

I read that you must have your phone unplugged on the toolkit screen. But it remains plugged on that drivers install proces on the video.

Thanks,
[Nexus 4 General] !GreddyZC76:
great video!
[Nexus 4 General] dougrb:
Awesome video, worked pretty darned well for me, using Parallels on a Mac. No issues really, but had a bit of back and forth installing drivers. All done, and was wondering if there was an equally good video or tutorial showing how to install custom ROM's? Although, I'm not sure if it's really a ROM that I need. What I'm looking for is to keep the stock ROM, but put back the tethering abilities that I had prior to 4.4.2 and possibly add an LTE radio? The thing is, I've looked at various sources explaining how to install ROMS, and some seem to revolve around the type of custom recovery one has, or the way in which they rooted. So, I'm looking for the easiest way to cut my teeth on this sort of thing, after having used the methods in this video. I used the exact recovery and other thing that was recommended by the OP in the video (just because I wasn't sure if the version #'s would be up to day otherwise, and despite the OP saying that he loved a particular method, and using another for the purposes of the video).

Hope that makes sense? I guess the other question is, will having 4.4.2 negate being able to do any of this? Is the version too new? Should I go back to an earlier version?

Thanks much,

D.
[Samsung Galaxy Nexus] tbguy:
Hi, I was trying to compile CM 10.1 for toro and was following this guide http://wiki.cyanogenmod.org/w/Build_for_toro

I couldn't find extract-files.sh so I skipped it and used the blobs from https://developers.google.com/android/nexus/drivers#toro

It compiles all the way through and generates a zip file but it just causes a blank screen when it tries to boot.

Does anybody know where I can find extract-files.sh? I did repo sync a few times and even deleted my entire directory and started over. It never shows up in the directory stated in the guide.

I'm also using ubuntu 12.04
[Samsung Galaxy Nexus] boype:
Have you completed every step successfully before you are supposed to execute the extract-files.sh?

Also: which java version and toolchain do you use for compiling?
[Samsung Galaxy Nexus] hiepgia:
you can get blob here: https://github.com/TheMuppets/proprietary_vendor_samsung
[Samsung Galaxy Nexus] boype:
If it still fails after that, just get the google android NDK and use the provided 4.6 toolchain. Also, do not use Java 7 for compiling, use Java 6 instead (oracle Java always worked good for me, dunno about openJDK).
[Samsung Galaxy Nexus] MaceBewley:
BUMP, having the same problem with the blank screen after building. No problems with completing the guide. Everything is as it should be

just get the blank screen after the google splash.....
[Samsung Galaxy Nexus] boype:
What Java and GCC toolchain are you using?
[Samsung Galaxy Nexus] MaceBewley:
Java 6, not sure about the toolchain. Kinda of frustrating cause my grouper builds boot fine...
[Samsung Galaxy Nexus] tbguy:
I'm also using Java 6. And when I enter "gcc --version", I get 4.6.3

I tried using the blobs from the link above and still getting the same black screen.

I had also tried manually running generate-blob-lists.sh in devices/common. it took forever but it created extract-files.sh. It didn't even compile after that so I deleted my source directory again and used the blobs from hiepgia's link.
[Samsung Galaxy Nexus] beekay201:
lunch a eng build, then LOGCAT! You'll know why it's bootlooping. And you know you need to run extract-files.sh from a toro running CM right? 'make clobber', then brunch.

Sent from my Nexus
[Samsung Galaxy Nexus] crpeck:
Looking at the source tree at github, I see an extract-files.sh for maguro, but, no such file exists in the toro branch.

https://github.com/CyanogenMod/android_device_samsung_maguro/tree/cm-10.1

https://github.com/CyanogenMod/android_device_samsung_toro/tree/cm-10.1

After my repo sync finishes I'm going to go thru the steps again, if there is still no extract-files.sh (which I'm sure will be the case, unless it get's generated somehow), I'll try copying the maguro one in (with requisite changes)...
[Samsung Galaxy Nexus] cupfulloflol:
I assume it doesn't exist due to toro officially not being able to be above 4.1.1 with OTAs. Making CM10 and CM10.1 problematic with the older binaries...etc people potentially would be pulling from their device with the script.

https://github.com/TheMuppets <-- as mentioned previously that is what I use to get the proprietary stuff for my toro. You can make a local_manifest.xml in your .repo directory, then a repo sync with download them all for you.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="http://github.com/" name="gh" revision="master" />
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_imgtec" path="vendor/imgtec" remote="gh" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="gh" revision="cm-10.1" />
<project name="TheMuppets/proprietary_vendor_invensense" path="vendor/invensense" remote="gh" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_toro" path="device/samsung/toro" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_device_samsung_tuna" path="device/samsung/tuna" remote="github" revision="cm-10.1" />
</manifest>
[Samsung Galaxy Nexus] crpeck:
OH sweet - sorry I missed that before... Very nice fix..
[AT&T Samsung Galaxy S II SGH-I777] buickgnx:
Since flashing CM 10.1 nightlies back in december i hav't been able to connect it to any computers. It'll charge off usb just fine but wont connect for file transfer. I have Siyah v7.6.8-S for the i777 and everything works great except the usb functions like data transfer and usb teather. Anyone else have similar problems?

Edit: Right now i have the 20130208 nightly but none of the other cm10.1's have workd, but cm 9 and 10 both did. Also i've tried on my laptop which is ubuntu and other windows machines to no avail.
[AT&T Samsung Galaxy S II SGH-I777] Phalanx7621:
Using the Samsung version of the kernel on an aosp based Rom? Interesting choice. (Although the differences most likely are just Wi-Fi hot spot related). Also make sure you have all the drivers installed for your device on the computer. And of course try different usb ports.
[Android Q&A, Help & Troubleshooting] OZHK:
Hi,

I got s5360 rooted

OTA 4 works great, but OTA 5 is too big and can't get it to reduce on screen so may apps don't fit, the clock is part missing, all the fonts too big. I rolled back to OT4.

I can't post in the developer forum yet.

Any ideas?
[Android Q&A, Help & Troubleshooting] dar_santiago:
Jelly blast OTA 5 prob

when I install this update I encountered some problem. The battery icon bar is not accurate with the percentage. and also when I scroll down the notification area, it force closes. Does anyone encountered these kinds of problem. Is there any way I can correct this problems or any way that this can be fixed. Please help.. hope for your reply thank you
[AT&T, Rogers HTC One X, Telstra One XL] mikelebz:
I know that this is a noob question and I feel semi-embarrassed for asking since I've been around so long, but better safe than sorry.

I plan on installing 4.2 soon, so I will be starting fresh with all of the wipes. My SD card is getting rather cluttered. Is it safe to just delete EVERYTHING (aside from the rom zip in question and a backup, of course) without any issues? I don't care about losing game data and what not. I'm assuming/hoping that flashing the rom will put back whatever is needed.

If there is anything in particular I should leave on the SD, please let me know.

Thanks for the input!
[AT&T, Rogers HTC One X, Telstra One XL] InflatedTitan:
Every Sunday I format my sdcard o.O

I like it to be light.. I like to enter recovery and mount SD, format my card in windows. Then when its done I simply drag a rom back on there and flash it.. Its usually fast as sh|t

The rom you flash will install all the necessary files you need. Good luck mike!
[AT&T, Rogers HTC One X, Telstra One XL] mikelebz:
Thanks for the fast reply!
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Since you don't intend to keep any app data, you can basically delete everything (aside from the ROM zip, TWRP backup, and Titanium folder). Any folders needed by Android will be created automatically. Same thing with any apps you re-install.
[HTC One X+] Fidelio_o:
Anyone working on getting Google wallet working on our phones? I installed Modacos, modded apk, plus changed the build.prop to a nexus 4 and galaxy nexus. no dice. wont passed searching for google account.