Database Users

Weird stuff while rooting

Hello. I was rooting my Nexus 7 today and decided to do my Nexus 4 too, fresh out of the box I plugged it into my PC and went to work. Now I downloaded the Nexus 4 toolkit and unlocked my boot loader and rooted, hoping to flash some CM10 on it, I decided to boot into recovery, only to find that I have the stock one. So I did the step in the toolkit that supposedly makes the custom recovery stick and it doesn't work. I can get past the step to make it stick but then when I try to put CWM on it it doesn't let me. I'm confused on what to do here...
My Nexus 7 was fine, but now I have problem after problem with this.
Sent from my Nexus 4

Your first problem is you used a toolkit.
Android has a built in recovery, recovery feature and that's what your hitting.
Go to clockworks website if that is what you choose to use and download the correct recovery. Then go download a ROM. CM10.1 or whatever, even just a rooted deodexed stock ROM is fine. Put it on your phone.
Google Fastboot.exe download it from a reputable site, it'll probably link you somewhere here.
Take the downloaded fastboot file and drop it into your Windows folder.
Now boot your phone into the bootloader (I'm unsure on the key combinations since I have a Galaxy Nexus.)
Type "fastboot devices" (without the quotes of course)
You should get a response with a bunch of numbers, that's what you want. If its blank you need to install drivers.
Once you get a response, locate your clockwork file. It should be nameed something like:
Clockwork-touch-recovery-(version number).img (it must be a IMG file as you do NOT want a zip file.
Type this command:
Fastboot flash recovery (recovery file name as mentioned above)
You should get a few lines of code showing it as complete. Select boot into recovery from the phone and flash your ROM.. Be sure to include GAPPS if the ROM you choose doesn't have it.
Sent from my Nexus 7 using Tapatalk HD

altimax98 said:
Your first problem is you used a toolkit.
Android has a built in recovery, recovery feature and that's what your hitting.
Go to clockworks website if that is what you choose to use and download the correct recovery. Then go download a ROM. CM10.1 or whatever, even just a rooted deodexed stock ROM is fine. Put it on your phone.
Google Fastboot.exe download it from a reputable site, it'll probably link you somewhere here.
Take the downloaded fastboot file and drop it into your Windows folder.
Now boot your phone into the bootloader (I'm unsure on the key combinations since I have a Galaxy Nexus.)
Type "fastboot devices" (without the quotes of course)
You should get a response with a bunch of numbers, that's what you want. If its blank you need to install drivers.
Once you get a response, locate your clockwork file. It should be nameed something like:
Clockwork-touch-recovery-(version number).img (it must be a IMG file as you do NOT want a zip file.
Type this command:
Fastboot flash recovery (recovery file name as mentioned above)
You should get a few lines of code showing it as complete. Select boot into recovery from the phone and flash your ROM.. Be sure to include GAPPS if the ROM you choose doesn't have it.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks. I'll try that. I always thought toolkits were better than anything else. Though I've only ever used them on my Nexus devices, on my old phones I did it differently
Sent from my Nexus 4

Orange_furball said:
Thanks. I'll try that. I always thought toolkits were better than anything else. Though I've only ever used them on my Nexus devices, on my old phones I did it differently
Sent from my Nexus 4
Click to expand...
Click to collapse
Not better at all.
Toolkit is like walking into a university campus blindedly, it will carry you from the entrance to where you need to be. But what happens if it's relocated? You don't know where it is, and then you ask questions to the people in your surroundings to help.
Doing it yourself is like having a map and you are able to analyze the situation and then you will know what to do without asking questions. You'll ask questions, but you'll feel more comfortable as you know what's going on.
You get the point. It's not fun flashing and doing things to your phone blindedly, then mistakenly saying your phone is bricked when it isn't and they don't know how to do fastboot restore.

zephiK said:
Not better at all.
Toolkit is like walking into a university campus blindedly, it will carry you from the entrance to where you need to be. But what happens if it's relocated? You don't know where it is, and then you ask questions to the people in your surroundings to help.
Doing it yourself is like having a map and you are able to analyze the situation and then you will know what to do without asking questions. You'll ask questions, but you'll feel more comfortable as you know what's going on.
You get the point. It's not fun flashing and doing things to your phone blindedly, then mistakenly saying your phone is bricked when it isn't and they don't know how to do fastboot restore.
Click to expand...
Click to collapse
That makes sense. I usually try things myself but I was feeling lazy.
Sent from my Nexus 7

Orange_furball said:
That makes sense. I usually try things myself but I was feeling lazy.
Sent from my Nexus 7
Click to expand...
Click to collapse
No problem. I've used Toolkits before but only on HTC devices where getting S-Off required a lot of lines of code and messing one up meant a bricked device.
Nothing is easier then getting a Nexus device rooted. Once your setup you can usually go from stock/locked to rooted/unlocked/custom rom in under 5 minutes.
Sent from my Nexus 7 using Tapatalk HD

Orange_furball said:
That makes sense. I usually try things myself but I was feeling lazy.
Sent from my Nexus 7
Click to expand...
Click to collapse
Laziness gets people in to awkward positions and tend to make really bad situations and soft brick their phone. Nor necessarily during using the toolkit but what they do to their phone afterwards. Thinking and reading are imperative
I completely agree with the post above. If it's a long process then by all means use the toolkit but the nexus is simple as if is. If people can't manually unlock their bootloader then they don't deserve access to tinker with their phone, to me it's like a exam. Pass it, you get bootloader unlock. Fail, repeat
Sent from my Nexus 4 using xda premium

I got it resolved. Thanks everyone, I just had to use the Samsung ADB drivers, the use command prompt to flash CWM:good:

Cool.. Glad to hear it all worked out for you
Sent from my Nexus 7 using Tapatalk HD

4.2.2 root is impossible :(

I been at it all day guess I should just wait till something comes out for 4.2.2?
Sent from my Nexus 7 using xda app-developers app

If you don't know how to search on forums, there is something called "Google".
You ask, Google gives the answer. Easy stuff

I am backing up my n7 and setting to factory everything, including locked bootloader just to prove its possible

Code:
C:\temp\nex7>fastboot flash recovery openrecovery-twrp-2.4.1.0-grouper.img
sending 'recovery' (7182 KB)...
OKAY [ 0.951s]
writing 'recovery'...
OKAY [ 1.760s]
finished. total time: 2.718s
flashing recovery works fine

Code:
C:\temp\nex7>adb shell
[email protected]:/ $ su
su
[email protected]:/ #
yep. rooting works just like every other nexus device on any version.

Rooting via Nexus Root Toolkit v1.6.2 for 4.2.2
Hey all,
It seems like the OP may not have too much experience like me based on his post count. The responders on the other hand seem like guru's.
Well I did some troubleshooting after 4.2.2 to try to get the rooting to work (yes, i used google search). Just for the record I'm new to all this, but I've been doing a lot of goog'ling and figured the time I spent troubleshooting may be of help to other novices.
Apparently the rooting issue is well known if you're using the Nexus Root Toolkit v1.6.2 to try and do your rooting. There's a fix available which is described on the main webpage (between the red lines)
google wugfresh for homepage (I can't post links yet)
Just download the zip file and unzip in the folder described, overwriting what's already there there. Make sure your drivers are working . They were acting really finicky for me when using the toolkit but I finally troubleshooted it. If you're having issues you may want to try the newest PdaNet driver, although I didn't have to. Once your drivers are fine, select the Android "any" option and hit root with Custom Recovery checked. I dunno about everyone else but my Custom Recovery was gone/messed-up after upgrading to 4.2.2
If you don't use Nexus Root Toolkit, I recommend it for the less computer savvy ppl out there, like me. Hopefully they'll come out with an update.
Hope this helps.
One newB question I have is can I install my 4.2.1 custom ROMs after upgrading to 4.2.2? I'm not sure if there's some kind of firmware component of 4.2.2 that'll render my Nexus 7 incompatible with the 4.2.1 custom ROMs out there. If it's not okay is it possible to downgrade back down to 4.2.1 from a factory image and then install these custom ROM's?
Thanks ahead of time.

Here's a tip, it seems like your a noob with the nexus 7. In order to mod this thing you should familiarize yourself with command prompt.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jesus people hate noobs here, why doesnt some just show them how to get adb and fastboot going, instruct on how to properly instal the adt and jdk bundles inc path etc. there are no easy tutorials for noobs, if people are expect to learn then teach them, dont forget we were all noobs once.
Sent from my Nexus 7 using XDA Premium HD app

This might help. Go to this link and download the 4.1.2 (JZO54K) image for nexus7 wifi only if that's the one you got and downgrade everything to that and then root and download and install Chainfires SuperSU and SuperSU-Pro from the market and after you install that open SuperSU and check mark Survival Mode and then do the OTA update and you will still have root. Yes you can downgrade. I had to downgrade back to 4.2.1 and do what i said above. You have to have SuperSU Pro installed to use survival mode. its worth the price it cost.
https://developers.google.com/android/nexus/images#nakasi
After downloading the correct images from the link above
Follow these instructions
Nexus 7 Back to Stock
Step 1. fastboot erase boot
Step 2. fastboot format cache
Step 3. fastboot erase recovery
Step 4. fastboot format system
Step 5. fastboot format userdata
Step 6. fastboot flash bootloader bootloader-grouper-x.xx.img
Step 7. fastboot reboot-bootloader
Step 8. fastboot -w update image-nameofzip.zip
Step 9. fastboot reboot-bootloader
After you downgrade your device doing all the steps above then go and root the nexus 7 and install SuperSU and SuperSU-Pro check mark survival mode in superSU and Install busybox also from the google playstore and then do the ota update.
Unlock Boot Loader
fastboot oem unlock
fastboot reboot-bootloader
Lock Boot Loader
fastboot oem lock
fastboot reboot-bootloader

I was 4.2.1 would this still work?
Sent from my Nexus 7 using xda app-developers app

gastonwalpole said:
jesus people hate noobs here, why doesnt some just show them how to get adb and fastboot going, instruct on how to properly instal the adt and jdk bundles inc path etc. there are no easy tutorials for noobs, if people are expect to learn then teach them, dont forget we were all noobs once.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
We don't like noobs because we don't like seeing the same posts over and over and over. I remember when I was a noob, I had no help. I wasn't a member of xda so I learned everything on my own, lots of soft bricks, lots of Googling, and lots of sleepless nights. That's how everyone should learn. You learn more by figuring it out yourself, not being told how. This guy has been told how to root in about every thread he's posted but wont listen. Look at the 5 other posts he's posted, you'll understand why we're annoyed.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

lol
fastboot oem unlock it
fastboot flash a custom recovery
then in that recovery flash the supersu zip from chainfire's thread. I just did this from fully stock and now its rooted

Class_of_punk26 said:
I been at it all day guess I should just wait till something comes out for 4.2.2?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I dunno whats all this fuss about, root 4.2.2 via Nexus 7 toolkit.
I checked today, installed stock 4.2.1, and ota to 4.2.2 than rooted via Nexus 7 toolkit. Select 2nd option, and 2nd option again "install root and busy box". :good:

markj338 said:
lol
fastboot oem unlock it
fastboot flash a custom recovery
then in that recovery flash the supersu zip from chainfire's thread. I just did this from fully stock and now its rooted
Click to expand...
Click to collapse
Sorry i was just trying to help.

AndroidSmitty said:
Sorry i was just trying to help.
Click to expand...
Click to collapse
Hey I wasn't hating on you
I was just saying that if the OP already has 4.2.2 its easy to do it by flashing the supersu zip.

spitfire2425 said:
We don't like noobs because we don't like seeing the same posts over and over and over. I remember when I was a noob, I had no help. I wasn't a member of xda so I learned everything on my own, lots of soft bricks, lots of Googling, and lots of sleepless nights. That's how everyone should learn. You learn more by figuring it out yourself, not being told how. This guy has been told how to root in about every thread he's posted but wont listen. Look at the 5 other posts he's posted, you'll understand why we're annoyed.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Spitfire, it may have occurred to you that not everybody wants to go through that process, reinventing the wheel. Granted, the best way to learn something is doing it and making mistakes, but not always so for someone who just wants to get the job done rather than understand. This is why people here create guides.
If noobs annoy you so much, just let it go and do something else. Leave those with a better temperament to help them.

What's really annoying about this cat is that he has a minimum of 5 threads that he opened for the same issue.
you think thats acceptable behavior?

gastonwalpole said:
jesus people hate noobs here, why doesnt some just show them how to get adb and fastboot going, instruct on how to properly instal the adt and jdk bundles inc path etc. there are no easy tutorials for noobs, if people are expect to learn then teach them, dont forget we were all noobs once.
Click to expand...
Click to collapse
You've probably noticed by now that ROM devs and kernel devs rarely step in over here. There's a reason for that - what they do takes serious amounts of time (usually apart from their day jobs or studies) - and for every one of them there are literally hundreds of less skilled folks asking questions. If they tried to help, they simply wouldn't accomplish their positive contributions.
The other difficulties are:
(1) Forums organize info into a horrible format for learning
(2) The pace of technological change tends to invalidate even valuable posts rather quickly.
That first assertion (1) is made even worse by a flood of posts that scroll valuable (non-stickied) threads off to infinity.
Paradoxically, newbs that insist on creating their own threads for issues that closely resemble the issues covered in other threads are actually, yes, making the site worse for others - especially other newbs that seem to avoid using search.
In the case of this particular OP, he had threads closed and was issued a warning by a mod for exactly the behavior being repeated again here.
Well, if YOU want to create a tutorial, I would encourage you to do so ... & also try to get a mod to sticky the thing.
But don't come in here and say "somebody besides me should do this for the newbs". That's just lame.

The easiest way for beginners is to use Wug's toolkit. All you have to do it update the adb files in the install directory and it will all work. http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 <-- Look there

im not an expert yet mate, just started using xda, what i know ive researched, its hard for noobs to find the info required, i dont understand why it has to be so hard for people, if info already exist here why doesnt anyone point them in the right direction, i just dont want others to go through what i went through, people dont talk to each other with respect here, id like to see if they are that up front face to face. once im more confident i will help others dont worry about that, i am trying to already.
cheers
Sent from my Nexus 7 using XDA Premium HD app

[Q] (HELP) Rooting 4.2.2 Nexus 7

Hi, now most people here are smart with this type of thing soooo i wanted to ask you how i can root the nexus 7 running 4.2.2. I tried to use the wugfresh NRT but when I was installing drivers a problem occurred. Instead of having ADB drivers or something like that I had ADB Composite drivers installed even though i followed the guide completely and I have tried several times to correct this but i havent found a solution. Also i attempted to carry on the rooting process but it said i did not have the correct drivers installed and etc. So can someone give me a fool proof way of getting the right drivers for this thing so i can root so i can finally install some kernels and use the sixaxis controller app! sorry for the essay and all help is appreciated

hrsedJe Something
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.

How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.

phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.

Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
Dude, most commands for doing stuff on the N7 manually are four words. It really isn't a lot to remember. Also I don't think you understand the purpose of this site/forum.
..That being said.
Use Wug's toolkit and update the adb files in its install directory. Then just use the 4.2.1 settings if 4.2.2 doesn't show.
Here is a post with the files: http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650

sucks that the toolkit is only for windows, sucky windows

Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk

http://forum.xda-developers.com/showthread.php?t=2019519

had the same problems
Just google fastboot files for n7, get sdk and pack files AND the recovery into the sdk tool folder.
Shift+right click -> start command here
Fastboot flash recovery recovery.img
Start tab abd sideload the SU.zip (google superuser)
Flash
Done ))
Did it yesterday no issues!

phonic said:
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk
Click to expand...
Click to collapse
Well said phonic. I prefer the manual way as well. It is always good to know what you are doing, but knowing how it works and learning something is always better.
I would much rather learn something than to have someone do it for me. If ever I need help and ask someone, they say I'll do it for you I say no, please show me how to do it!
Sent from my Nexus 7 using Tapatalk 2

kidujp said:
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.
Click to expand...
Click to collapse
You may receive an error message "ABD" is offline, in this case download the latest Android SDK manager and upgrade all USB drivers before using the toolkit again.
Sent from my Nexus 7 using xda app-developers app

phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Never ceases to amaze me how many pretentious pricks use XDA.... Reminds me of Apple snobs.

command line is the way to go
command line is the way to go m8!!
cheers,
geek endangered

[Q] Problem rooting with Nexus Root Toolkit

I rooted my Nexus 7 with Nexus Root Toolkit without any problems but I've just bought a Nexus 4 and can't seem to root it.
I let it update to Android 4.2.2 then ran NRT (v1.6.3) on my PC. After a few goes the drivers installed and it passed the final driver test so I assume all is well there. I then unlocked it without any trouble but I ran into problems when I came to root it.
It seemed to be going smoothly until it reached "Booting TWRP temporarily" but nothing happened, it just sat in the bootloader screen and didn't move on, although the message changed to "Rooting" and then "Waiting for your device to finish booting back up". In the end I pressed the power button which rebooted the 'phone and appeared to finish the procedure but it hadn't rooted or installed SuperSU or BusyBox.
I tried flashing it back to stock and re-rooting it but it was the same, I even re-locked it and went through the procedure again but it was the same.
Can anyone help please?

:sly:
Sent from my Nexus 4 using Tapatalk 2

SimonP2 said:
I rooted my Nexus 7 with Nexus Root Toolkit without any problems but I've just bought a Nexus 4 and can't seem to root it.
I let it update to Android 4.2.2 then ran NRT (v1.6.3) on my PC. After a few goes the drivers installed and it passed the final driver test so I assume all is well there. I then unlocked it without any trouble but I ran into problems when I came to root it.
It seemed to be going smoothly until it reached "Booting TWRP temporarily" but nothing happened, it just sat in the bootloader screen and didn't move on, although the message changed to "Rooting" and then "Waiting for your device to finish booting back up". In the end I pressed the power button which rebooted the 'phone and appeared to finish the procedure but it hadn't rooted or installed SuperSU or BusyBox.
I tried flashing it back to stock and re-rooting it but it was the same, I even re-locked it and went through the procedure again but it was the same.
Can anyone help please?
Click to expand...
Click to collapse
Yes, uninstall and forget about root kits and look and (most importantly) learn from here http://forum.xda-developers.com/showthread.php?t=2010312.

This is also a good source to read: http://forum.xda-developers.com/showthread.php?t=1469909

Thanks for the suggestions, guys. I still don't know why Nexus Root Toolkit didn't do the job when it worked so well and easily on my Nexus 7 but in the end I used the hippowise.com rooting instructions (using Google Nexus 4 Toolkit) and it worked a treat so I'm a happy bunny again
http://hippowise.com/how-to-unlock-root-and-install-a-custom-recovery-on-a-nexus-4/
I know it's more sensible to do it manually so that I know what has happened but in this case I just wanted the job done as quickly and easily as possible. I'll look into exactly what happened when time permits.
Cheers,
Simon.

^^ Learning opportunity lost.

Ditto, I've heard nothing good about toolkits and never used them, and consequently have never had the weird problrms I hear associated with them. Set up fast boot, setting it up can be a pain sometimes but its a one time thing. Using it is too easy and it never fails.

I do get what you guys mean and I will be interested to look into the procedures to see what's going on and how it unlocks and roots when time permits but, aside from being short of time at the moment, these toolkits are just automating the list of commands that you would issue manually so as long as someone has seen it working on the device and OS that you want, they should be fine so I'm happy to use them and learn more if/when I need to resolve problems. I am techie by nature but I'm not familiar with *nix and the inner workings of Android so it's a lot to study for something that only needs doing occasionally.
Anyway, thanks again for pointing me in the right direction and encouraging me to not be so lazy

SimonP2 said:
I do get what you guys mean and I will be interested to look into the procedures to see what's going on and how it unlocks and roots when time permits but, aside from being short of time at the moment, these toolkits are just automating the list of commands that you would issue manually so as long as someone has seen it working on the device and OS that you want, they should be fine so I'm happy to use them and learn more if/when I need to resolve problems. I am techie by nature but I'm not familiar with *nix and the inner workings of Android so it's a lot to study for something that only needs doing occasionally.
Anyway, thanks again for pointing me in the right direction and encouraging me to not be so lazy
Click to expand...
Click to collapse
To be honest, the learning curve with manual rooting is very straightforward. Heck, I found it quicker to unlock and root manually than through toolkits. You are literally just inputting a few lines into command prompt.
Sent from my Nexus 4 using Tapatalk 2

I can confirm that I have the same problem. Stuck at "Booting TWRP Temporarily" logo, doesn't move... Nexus 7 2012 Grouper 16GB.

[Q] Bricked nexus 4, need help finding drivers?

A while back i hard bricked my N4, and got it replaced, but i kept the broken one, hoping to get it working again. It shows up as "qhsusb_dload" on my computer and says i need the drivers for it. But i cant seem to find the drivers for qhsusb_dload, so if anyone could give me a link for those drivers, it would be a great help.

sinndissension said:
A while back i hard bricked my N4, and got it replaced, but i kept the broken one, hoping to get it working again. It shows up as "qhsusb_dload" on my computer and says i need the drivers for it. But i cant seem to find the drivers for qhsusb_dload, so if anyone could give me a link for those drivers, it would be a great help.
Click to expand...
Click to collapse
There are no drivers. That's what shows up when you're hard bricked.
Sent from my Nexus 5

Try this method http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060

Tried flashing stock image through fastboot?

No fastboot, no recovery, no anything. /:

I know its a hard brick, but there are drivers for this for other models of android, and ive read of people having success with some phones once they get the drivers for it.

sinndissension said:
I know its a hard brick, but there are drivers for this for other models of android, and ive read of people having success with some phones once they get the drivers for it.
Click to expand...
Click to collapse
Well good luck with that. You're not going to find any drivers
Sent from my Nexus 5

jd1639 said:
Well good luck with that. You're not going to find any drivers
Sent from my Nexus 5
Click to expand...
Click to collapse
Give him a break. The least you can do is not be an asshole.
OP: Linux might help you, you don't need drivers on Linux.
I've tried some Linux recovery tool for my old galaxy player 5.0, however i wasn't successful. I'm not sure is there any recovery tool based on Linux for the Nexus 4

Mashed_Potatoes said:
Give him a break. The least you can do is not be an asshole.
OP: Linux might help you, you don't need drivers on Linux.
I've tried some Linux recovery tool for my old galaxy player 5.0, however i wasn't successful. I'm not sure is there any recovery tool based on Linux for the Nexus 4
Click to expand...
Click to collapse
Dude, jtag is his only option. He's not going to find drivers. I'm not trying to be an a-hole just stating the facts.
Sent from my Nexus 5

qhsusb_dload is what is used to initially load firmware onto the phone. (From what ive read so far) so i cant imagine the company that does this are the ONLY people that the software to do so, unless theres some hardware stuff they do, (which i havent found any proof of this). Still worth a shot to me, and like i said, im just trying to give it a SHOT. Not looking for people to just say, "oh its not possible" unless they have experience with this sort of thing. Thanks.