Database Users

Nexus S4G might be bricked, please help

I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks

Go look in the developer section, one of the stickies, the one that talks about the nexus s 4g cdma. You might have flashed something that was meant for the gsm nexus s. It has links to correct files and guides for the sprint version of the nexus.

Pm me and I will help u over the I'm client of your choice.

Basically, I have no service, and no card, so since I can access Fastboot Mode, and unlocked, is there a way to push a rom direct onto Sprint phone.
I looked in Developers Forums, I am not ready to jump in with custom rom yet (I have used extensively on other phones) but would like to start with stock, go with root and programs as needed.
So how would I push to phone via computer? and what programs, again, no idea of commands to use.

Have you flashed CWM yet? You can use that to reflash the stock ROM. Worst case you can use this thread:
http://forum.xda-developers.com/showthread.php?t=1072698
That will bring you to 100% out of the box factory settings

If you can get into fastboot, then you didn't brick it. You'll be fine, you just need to get in touch with someone that can walk you through the process of fixing it. Or search around, read, and take your time to figure out what to do.
It's not hard. The worse thing you can do is panic or rush to fix it.

Basically what you did when using superboot was you actually installed a boot.img file not meant for your device on your phone. What you should do is, go through the guide for your specific phone...you will have to install a recovery image and then install a custom rom or stock rom.
I do not know if you know your way around with fastboot....basically you could also ask a dev to send you the original boot.img and flash it using fastboot but the first stepi described is easier.
Sent from my Nexus S using Tapatalk

nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse
If you are going to waste your brand new phone by being stupid how about giving it to me instead! Ill take good care of it.
Sent from my PC36100 using XDA App

Here Try this and let me know if it work:
1.Download this platform-tools.zip and extract it to your desktop
2.Connect your phone to the PC and enter bootloader mode
3.Press and hold Shift while right-clicking the folder you extracted 'platform-tools'
4.Click 'Open command window here' from the pop-up menu. cmd.exe window will open.
5.If the Bootloader is Unlocked continue to the next step. Type in the cmd.exe window 'Fastboot oem unlock' and follow the steps on the phone screen.
6.Type in the cmd.exe window 'fastboot flash boot boot.img'.
7.Type in the cmd.exe window 'fastboot reboot'.
nmoreman said:
I need help, I got the Nexus (sprint) and have tried and tried to unlock. I had fits, read many forums, and was directoed to an unlocker forum. I used Superboot GR140. I had downloaded su 2.3.6.1 to my phone.
Using this method, it unlocked but now I am stuck. I cannot get anything else to load.
I'm not sure if I used an incorrect Superboot method (meaning for a different phone since the forums aren't split).
I have access to Fastboot Mode Screen, phone is recognized, but when using cmd, it shows C:\Superboot. I do not know what else to do to direct it to files I have on my computer or how to download these, 2.3.4 back to my phone. I'm stuck and really need help.
I will gladly push the Thanks button for any help I can get to get me up and
running again.
Thanks
Click to expand...
Click to collapse

THANK YOU, for answer, but it didn't work.
I downloaded, opened, opened cmd from there.
My phone is unlocked, setting there with unlock screen, put it in bootloader mode, but when I type in instructions, it comes back "not recognized as internal, external command, program, batch file"
This is the problem I had when trying to unlock, so reading, used Superboot, probably wrong phone, so now it is wiped and empty.
I also read another thread suggesting Odin in this situation. Have downloaded that, SamsungSimpleDL, followed those directions, that doesn't work either. I have hacked and rommed Epic, very familiar with that, if it works, but cannot point to proper files (pda, pit, or bootloader).
So any other ideas, I am very good at directions, that is how I learned

My Phone is Fixed - YEAH
This did not work, but this link did
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
Basically used Odin (my old backup from Samsung Epic) and it worked when all these suggestions wouldn't.
I couldn't unlock easily, like all of these, therefore used Superboot. Would recommend no one touches that!!
I couldn't run any of the commands before this, and still couldn't use these.
So the instructions to dig thru the Developers section is correct, but so hard with so many customs, phones, carriers, to choose from. Makes it difficult
So use this link if stuck like me, I am just glad I con't have a brick, and I'm still pushing the Thanks button for all who helped, that's what will make this fun.

1 Click root brick?!

So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Motorola published the factory files for Xoom awhile back so if you still have fastboot, you can recover from it.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard

I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.

Stop using one click crap. If you don't know what you're then you should not be messing with your device.

Sent from my DROIDX using XDA App

I can. Just won't.

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.

albundy2010 said:
I can. Just won't.
Click to expand...
Click to collapse
And this is rude and uncalled for

The OP stated he read quides etc and none of it made sense to him etc. So instead of asking for help a explanation he tries a one click method. Which is stupid. He than softbricks the device and asked for help here.
Then he is told that moto released the factory images and use fastboot if he still has it to recover the device. He then decides to ignore that entirely and go back and try to unroot/restore with the one click BS again. Then he tries to use it again to go back to where he was. Just flat out stupid. He did something when he had no idea wtf he was doing. Was told what to do. Did not do it. He even said it is like Chinese to him.
So I told him to stop messing with one click crap. Which is correct. I told him to stop messing with the ****ing thing. Which is also correct. He needs to learn/understand wtf he is doing. Instead of basically button mashing/trying crap and hoping it will basically fix itself.
On top of that this posted in the wrong section. Uncalled for my ass. He is the one that was rude when told to not mess with the one click or the device. Now this part is rude. **** his stupid ass.

csseale said:
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
Click to expand...
Click to collapse
How do i get to that ..and where do i type it at ..i looked in device manager & does recognize the xoom..it says "Motorola USB Device:Motorola Flash Interface"..In properties under "Driver" it has options for driver details..update driver..disable & uninstall.Can i do anything with them?
I tried opening SDK manager but it never lets me type anything in the box as it's always trying to do some kind of update in another window so when i close the window it closes all of the windows.

Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If they didnt make sense to you in the first place you probably shoud not be attempting to root... U went straight to an old method that even the developer has marked in hs thread can full brick you and should not be used. The xoom costs like 600 bucks... Why wouldnt you do extensive research on how to root? If you did not understand the terms why didn't you research the methods and learn it?
I hope you can flash the factory imagines back through fastboot and adb, but i just do not understand why people attempt this stuff when they have no idea what the terms even mean...
You need to have sdk, hook up to usb on your computer, and follow one of the unlock guides posted on this site... A real one using adb... Then you need to follow a root one...
Sorry that is not more helpful, but half of this experience is that you need to learn what you are doing and the instructions are out there. If they do not make sense at this point im afraid you are stuck. Now the way your device is you have to figure it out...

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Please check out this thread.It is called Root heaven for a reason. Just about every viable rooting guide, all the files and explanations you will need are here.
http://forum.xda-developers.com/showthread.php?t=1209341
I urge you to just calm down, read about what is the sdk, what is adb, how to recover from a soft brick and so on. The xda xoom forum is all about learning and teaching. We were all noobies once. The Xoom is a very complex device with many models and vesions and one clicks just don't cut it. There are rooting methods that are relatively simple but you really need to be prepared before you get started.
Good luck and don't despair. You'll get there.

Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App

Arun01 said:
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
at first, make sure you install android sdk correctly. then go to android sdk-folder in your computer, u will find a folder named platform-tool. Press shift+ right click on it, then choose open command window here. After that, type in "adb devices" or "fastboot devives" to check if your xoom is connected. If yes,you good to go. If no, check your android sdk installed process

After i type in abd devices it says list of devices attached but shows nothing..i did copy the sdk tools folder to the c drive like i was told.

@OP
If you can't do it yourself, getting somebody to help you (in person) is always an option. If you live in a major city, advertise on Craigslist or some equivalent. Offer $50 for debricking + some tutorial.

In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
That's good advice...no reason to re-lock. But get back to square one so that you're functional and then when you're ready to try again, do it the right way.
Again, good luck!

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
Thanks a lot.I was able to unlock it then it rebooted & stopped at the Motorola screen then i started the 1st command: fastboot flash boot boot.img & it says waiting on device..but nothing happens so far.Should i move on to the next step or retry?

Just got a Xoom, want help.

So I want root my new Xoom wifi running 3.2.1. I've searched and found ways of rooting it but not sure what's best for my version and device. I saw a thread about rooting no matter what Xoom or version, but have never used adb or fastboot and it doesn't explain how to do that part.
Does anyone know of a complete step by step manual on how to do this, or is someone willing to help???
I am familiar with rooting, roming, and recoveries, as I have my D1 rooted. But not sure about the Xoom.
Sent from my DROID using XDA App

This is the method I used to root my xoom. I only used the "easy adb install" section. it was my first time using adb and had no problems.
http://www.xoomforums.com/forum/mot...windows-7-64-bit-other-windows-platforms.html
then follow this other guide
http://www.xoomforums.com/forum/mot...-universal-xoom-root-any-xoom-any-update.html

Thank you for the links. I, gonna do some more research to make sure I don't screw something up, lol.

Use the second link, it is far superior. That way you can avoid adb (which is really quite simple to use) entirely. Just get fastboot. Get solarnzs recovery, flash it, and install root zip.
I wish you the best of luck

I use that but doesn't one need to "unlock" the device first? I don't have an unlock.exe or fastboot in this directory anywhere.

Upon playing around with this further, I can do an "adb devices" when the Xoom is running and it shows in my command prompt. I can successfully do an "adb reboot bootloader" and the device boots to fastboot protocol support. However, when trying to do the fastboot oem unlock, I get the error that the command is not recognized. Upon doing a "adb devices" at this point, it is not visible to the computer. Windows see's the device in the device mangler and I hear the tones for a new device being plugged in, but nothing shows up in command prompt. Idea??
EDIT: nm. Got it. Had to download a seperate fastboot.exe file: android-roms.googlecode.com/files/fastboot-win32.zip My SDK didn't install it. Unlocked. Whew. What a PITA trying to figure out what the problem was.

I rooted my xoom using this tutorial http://forum.xda-developers.com/showthread.php?t=1249798 the instructions are very easy to follow. I rooted my xoom in minutes using that tutorial.

DroidVPN said:
I rooted my xoom using this tutorial http://forum.xda-developers.com/showthread.php?t=1249798 the instructions are very easy to follow. I rooted my xoom in minutes using that tutorial.
Click to expand...
Click to collapse
Me too. Followed it to the letter and used the alternative ADB setup mentioned in the guide. Worked like a charm and I'm hopeless with command prompts.

Fool proof nexus 10 root

Hello there
Got myself a nexus 10 and to say I'm jealous of some of the homescreen posts is an understatement it really has me salivating when I see those custom icon packs coupled with a 2560x1600 resolution. I'm reasonably tech savvy myself but find the task of rooting my device a daunting one. I Find it difficult to follow all the steps and I'm afraid to mess it up and to be left with a device the won't even power on and as I live in Ireland it will prove difficult to send back for repair. Device still not available here officially. Anybody know an extremely easy reliable root?.just wanna run flash and customise the appearance a bit and maybe a little over clocking Any suggestions are welcome.
Thanks in advance
Thanks
Sent from my GT-I9300 using xda premium

rdsreference said:
Hello there
Got myself a nexus 10 and to say I'm jealous of some of the homescreen posts is an understatement it really has me salivating when I see those custom icon packs coupled with a 2560x1600 resolution. I'm reasonably tech savvy myself but find the task of rooting my device a daunting one. I Find it difficult to follow all the steps and I'm afraid to mess it up and to be left with a device the won't even power on and as I live in Ireland it will prove difficult to send back for repair. Device still not available here officially. Anybody know an extremely easy reliable root?.just wanna run flash and customise the appearance a bit and maybe a little over clocking Any suggestions are welcome.
Thanks in advance
Thanks
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Check the original android development section there's a nexus 10 toolkit that will unlock the bootloader and root along with a bunch of other features. Of course, learning how to use adb commands are best, but if you want a quick fix, use the toolkit.

If you mess up, as long as you managed to get as far as flashing a custom recovery you can fix just about any mistake. And even if you broke it all (which is HIGHLY unlikely) before you even flashed a custom recovery, you can still fix just about any problems you made. I actually just helped another guy who screwed up his tablet pretty bad if you want to read my post on how to get out of a jam:
http://forum.xda-developers.com/showpost.php?p=37019359&postcount=10
As for unlocking, if you follow the first few steps of my other post you will have the Android SDK downloaded and the files you need in an easy to access folder. From there you will just want to download a custom Recovery .img file, like this one here:
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.3.3.0-manta.img
and do the commands:
fastboot oem unlock
Then follow the couple steps on your tablet to confirm the unlock. Copy that recovery .img file you downloaded into your Android-SDK folder, and then use the command:
fastboot flash recovery blahblahblah.img (where blahblahblah is the actual file name of the recovery image you downloaded)
Once done then use the volume buttons to go down the fastboot menu on your tablet until it says "Recovery", press the power button to confirm booting into recovery.
Then download this file and place it in the Android-SDK-Windows directory:
http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip?retrieve_file=1
and use the command:
adb push CWM-SuperSU-v0.98.zip /data/media/0
Which will push the file to your tablet (or alternatively instead of pushing through ADB just start your tablet like normal and copy the file the normal way from your computer to your internal storage)
Once the file is copied/pushed then in your recovery go to the install menu and flash it. This will flash root to your current ROM. Then you should be dine, you are now unlocked on the stock ROM with root. Alternatively, instead of flashing root, you can just go straight away to flashing a custom ROM since those already have root access anyway.
It really is quite easy and simple. Should take 5-10 minutes tops. If you want to lock the tablet again then find a completely stock ROM (or google how to reset and flash the original RUU) and flash it to your tablet and then do the same thing as unlocking but use the command: "fastboot oem lock"

http://forum.xda-developers.com/showthread.php?t=2015467
Wugfresh has a toolkit that's foolproof. As long as you follow the directions and slowly go through each step, ensuring you're reading everything carefully, you'll be fine. In the OP of the link I provided is another link that takes to to a YouTube video of the Nexus 10 being unlocked and rooted using the toolkit. It goes step-by-step, so follow along with the video, do EXACTLY as he does, and you'll have no problems.

Just use cf-root, takes less than 10 sec and very straight forward
Sent from my Nexus 10 using Tapatalk HD

Does the name qbking77 mean anything to you??
Sent from my Galaxy Nexus using Tapatalk 2

Just use superboot, you won't loose data and won't need to unlock bootloader or install a custom recovey...

gmfeny said:
Does the name qbking77 mean anything to you??
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The link I provided has a link to qbking77's YouTube video showing the Nexus 10 being unlocked and rooted using Wugfresh's toolkit.

Rodeojones said:
The link I provided has a link to qbking77's YouTube video showing the Nexus 10 being unlocked and rooted using Wugfresh's toolkit.
Click to expand...
Click to collapse
Yea I know that's what I used when I rooted mines!
Sent from my Galaxy Nexus using Tapatalk 2

how to flash(format) N4.

Is lg or Google providing flasher for N4.if yes then how to get it.
If no then which is safest way to flash N4.
I an not having any idea about android . N4 is my first android device so please help me.

http://developer.android.com/sdk/index.html
Then read the many tutorials around here.. Stay away from Toolkits..

Toolkits are for begginers. He's not gonna know how to fastboot flash that fast either. But I recommend that being your last option.
Sent from my Nexus 4 using xda premium

styckx said:
http://developer.android.com/sdk/index.html
Then read the many tutorials around here.. Stay away from Toolkits..
Click to expand...
Click to collapse
I am reading couple of tread but I can't stuck to one of the method.now I am reading efrant method shall i try this. basically i am not understand collecting drivers and flashing .is their any method just installing pc suit & all legal work which we use for older devices. one more how to launch command prompt do i type it in "RUN".

I dont understand why he should stay away from toolkits, I mean that f he doesn't want to learn how to develops roms than toolkits are the best for him
Sent from my Nexus 4 using xda app-developers app

Odp: how to flash(format) N4.
OH cmon guys. Toolkits are good for noobs. I tried to use those all tutorials and i didn't even install proper drivers correctly. IF he screw up smth he will be dissapointed. My opinion first toolkit than learn and do it manualy if you want.
Sent from my Nexus 4 using xda app-developers app

GS150R said:
I am reading couple of tread but I can't stuck to one of the method.now I am reading efrant method shall i try this. basically i am not understand collecting drivers and flashing .is their any method just installing pc suit & all legal work which we use for older devices. one more how to launch command prompt do i type it in "RUN".
Click to expand...
Click to collapse
- Install the Naked usb drivers 0.72 from here http://forum.xda-developers.com/showthread.php?t=1996051
- Install the Platform-tools from here http://developer.android.com/tools/sdk/tools-notes.html.
- Connect the phone with the pc and install the drivers you downloaded.
Set up adb, here is a how to http://forum.xda-developers.com/showthread.php?t=1590800
Open cmd and type : adb devices, you should see a serial number now.
Type the command and hit enter.
Some Adb commands:
See if the adb drivers are installed correctly: adb devices
Reboot: adb reboot oem
Bootloader: adb reboot bootloader
See if the fastboot drivers are installed correctly: fastboot devices
Unlock bootloader: fastboot oem unlock
Flash recovery: fastboot flash recovery recovery-name.img
Flash kernel: fastboot flash boot name boot.img.
I hope this is a kind of a start to get familiar with this stuff, the problem with toolkits is that you will stay a noob forever and when a problem occurs people have no idea how to fix it because they often have no clue whats happening.
Using a toolkits is like watching tv all the time, it prevents you to think and it softens the brain

Odp: how to flash(format) N4.
Open command and write: adb devices. Nothing happen. I got installed drivers correctly because i root my phone already. Wrong command or filename.
Sent from my Nexus 4 using xda app-developers app

Adikbzik said:
Open command and write: adb devices. Nothing happen. I got installed drivers correctly because i root my phone already. Wrong command or filename.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
first type: cd c:\android-sdk\platform-tools or wherever you installed the sdk. The sdk folder must be installed directly on the C (or other) drive and NOT in a map/folder.
Here is a tutorial to set up adb: http://www.youtube.com/watch?v=oaNM-lt_aHw

Adikbzik said:
OH cmon guys. Toolkits are good for noobs. I tried to use those all tutorials and i didn't even install proper drivers correctly. IF he screw up smth he will be dissapointed. My opinion first toolkit than learn and do it manualy if you want.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
toolkits are great, but every single time ive used them for nex4 i had a broken phone afterwards. even for such simple things like flashing a recovery. fastboot is such a simple tool, i would also recommend using that instead.

molesarecoming said:
toolkits are great, but every single time ive used them for nex4 i had a broken phone afterwards. fastboot is such a simple tool, i would also recommend using that instead.
Click to expand...
Click to collapse
Everything you know or are able to do is easy
The first time you do this however is always a search and trial and error thing.

I agree, efrants guide is kinda confusing if your completely new to android. But its very complete, here's another way you can go about using it...
1st, follow steps 1-8 (stop after unlocking boot loader) in this root tutorial. http://www.androidrootz.com/2012/11/how-to-root-nexus-4-on-windows.html?m=1 . this is an easy way to get your fastboot folder set up. Power off phone when done.
Next, download the nexus 4 Occam image here: https://developers.google.com/android/nexus/images#occamjdq39 . use 7-zip to extract it anything that is a zip file. Youll probably have to extract 2-3 times to get all 6 .img files you need. Once you get all 6 img files, move them to the Rootnexus4 folder.
Last, power your phone back into the boot loader by holding the vol buttons + power. Go back to efrants tutorial, go back to your command prompt, and start with part D) 6 (the part about flashing boot loader). Keep on following the instructions from there and u should be good to go http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using xda app-developers app

I got SDK working now. Thanks for video, nowhere says to add path in Computer properties that's why my command didn't read adb. Now i can use brain to flash :victory: