Database Users

stock at google page...please help

I tried to root my new nexus s that i got last friday.....
tey must be some thread about this but my english is not in top shape...
i am now stuck at google page when turning on my phone. must be something about my boot....
I live in Canada and my provider is roger here all the information that i found :
in fastboot mode:
product name: herring
hw version : rev 16
bootloader version : i9020xxka3
baseband version : i9020uckb2
carrier info : att
on my box:
model: gt-i9020fsrrwc
Please i realy need help.....
Vbob

Describe steps you have taken to root in detail.

i know this is not the right place to start, but i did't know....
hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
i was stock after "fastboot flash boot rootboot.img" i was ubable to reboot
Vbob

any one can help me?
Vbob

Download this first
http://www.mediafire.com/?0pzz830oc0xa0e7
Rename it to rootboot.img and overwrite the one in C:\nexusroot
Try
Code:
fastboot flash boot rootboot.img
again.

ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob

thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob

im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you

vbobmac said:
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
Click to expand...
Click to collapse
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
redlilcivic said:
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
Click to expand...
Click to collapse
You need to describe the steps you have taken, and describe the problem with more detail.

If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
Click to expand...
Click to collapse
i did a update yesterday, and now i think i dont have the right system recovery.
now when clicking system recovery, i get a "!" whit the android character...

vbobmac said:
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
Click to expand...
Click to collapse
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?

[email protected]_OC said:
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
Click to expand...
Click to collapse
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App

reddv1 said:
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.

[email protected]_OC said:
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
Click to expand...
Click to collapse
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App

reddv1 said:
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes, i can mount my phone, but when i try to install the default rom, but it's not working. I have an error.
At least the manipulation is working, i can mount on my computer the nexus.
Do you have a rom 2.3.4 for Nexus i9023 please? Maybe i don't flash with a good rom?
Thanks again for your help.

I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".

[email protected]_OC said:
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
Click to expand...
Click to collapse
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App

reddv1 said:
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
And I think, i don't have the good bootloader.
My phone is a Nexus S i9023, but since i try to root my phone, my bootloader version is the "i9020XXKA3".
You think, i have to change the bootloader first?
For flashing bootloader and clocwork recovery, i have to do it from Windows?
Waiting for your answer.
Thank's a lot

[email protected]_OC said:
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
Click to expand...
Click to collapse
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App

reddv1 said:
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash the recovery, and now i have the v4.0.0.2, but i still can't flash a rom.
I still have the same message:
"assert failed: file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.2/GRH78C/93600:user/release-keys" ||
file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.3/GRI40/102588:user/release-keys"
E: Error in /sdcard/update 2.3.3.zip
(Statut 7)
Installation aborted.
Don't you think it's because my bootloader is not the good one?
Can flash it too, from Windows?

New Nexus 7 User needing Unlocking/Root advice

Hey XDA
Iv had my Nexus 7 for a day now and am dying to root and mabe install CM10
i currently have a Samsung Galaxy S3 with CM10 on it...thot its extremly buggy sadly... anyways i have been looking up on how to root the nexus 7 but i need to know if i can instead of using toolkit can i instead just use odin to flash stock rom and cwm and so on instead of having to unlock the device?
i am used to using odin for flashing and cwm but here the nexus is close to the same with htc one x in the way it has that fastboot thing and from what iv heard the nexus 7 requires unlock before it can be rooted, also is the tookit the best way to unlock and root the device?
also does unlocking break the warrenty and if i ever decide to return to stock unroot how do i flash stock rom back onto the device? am not sure where i would find the stock roms for it and also can odin be used to flash it...:S
i hate sounding like a noob lol

ok iv used the toolkit 2.0 and its worked great so far...im stuck at not being able to boot into cwm recovery
it installed fine thru the toolkit but whenever i try to hold up and power i cant get it to boot into cwm recovery...
i tryed to reinstall again but still cant get it to boot into cwm am i doing something wrong?

Doing the following won't cause you to loose warranty:
- Unlocking the bootloader
- Rooting
- Flashing custom ROM's and Kernels (however, if you flash a custom kernel that causes your device to explode... I'm somewhat certain this won't be covered)
However, if you are doing anything like that, and have to send the device in for warranty, you "should" factory restore it. Google provides Factory Images for the Nexus 7, which can be restored to your device with semi-ease.
I use this guide to factory restore: http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html Some filenames might need changed though since I think that guide is based off an older factory image (instructions are the same though).
There is a good chance a toolkit also has an easy method for factory restoring, but I don't recommend this at all.

Stop using toolkits.
Sent from my Nexus 7 using Xparent White Tapatalk 2

ÜBER™ said:
Stop using toolkits.
Click to expand...
Click to collapse
Amen, +1. http://forum.xda-developers.com/showthread.php?t=1830108

encryptioncsta said:
ok iv used the toolkit 2.0 and its worked great so far...im stuck at not being able to boot into cwm recovery
it installed fine thru the toolkit but whenever i try to hold up and power i cant get it to boot into cwm recovery...
i tryed to reinstall again but still cant get it to boot into cwm am i doing something wrong?
Click to expand...
Click to collapse
I've never used a toolkit before (until this issue had me stuck). I'm unable to get the Nexus 7 to book into recovery (CWM) after flashing it via fastboot. After giving up, I rooted it using the toolkit.. scariest thing I've ever done.. it did work.. but I'd like to get to the bottom of why a number of people like me seem to be having issues flashing and booting CWM on the Nexus 7.

Did you rename the original system/recovery to .bak first?

Travisdroidx2 said:
Did you rename the original system/recovery to .bak first?
Click to expand...
Click to collapse
No, I flashed it as I normally do.. using the .img file. In this case, CWM.. recovery-clockwork-6.0.1.0-grouper.img
Why would renaming it to .bak be needed?

xyzulu said:
No, I flashed it as I normally do.. using the .img file. In this case, CWM.. recovery-clockwork-6.0.1.0-grouper.img
Why would renaming it to .bak be needed?
Click to expand...
Click to collapse
Its not actually.
Sent from my Nexus 7 using Xparent White Tapatalk 2

I had to rename the stock recovery under system to .bak before I could get twrp to work. Or else when I went into recovery it would get stuck on the android.
But I see you are using fast boot it should write over it.

Travisdroidx2 said:
I had to rename the stock recovery under system to .bak before I could get twrp to work. Or else when I went into recovery it would get stuck on the android.
But I see you are using fast boot it should write over it.
Click to expand...
Click to collapse
I didn't have to. Flashed twrp and forgot to put a ROM on it and went back into recovery and it was twrp still.
Sent from my Nexus 7 using Xparent White Tapatalk 2

I should of just flashed the image file and flashed it myself but I was in a hurry and used goo im and it bit me in the ass. Lesson learned.

[Q] Nexus 7 (4.1.2) can't root

Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message

IAmNice said:
usb debugging on? Have you checked that?
Click to expand...
Click to collapse
Hi. Yes mam (usb debugging on) have a look to the attachment.
Toolkit me boot into fastboot then reboot then for something to fastboot loaded and back to android and trying to upload the files but nothing superuser is not recorded because of (read-only file system).
have a look on the attachment is there to see everything ...

yep same issue here - problem with the forum regs is unless you have enough posts you can't actually address the issue to the appropriate person can you? Anyway, able to unlock but then is unable to root and rest due to a permissions problem. have tried as administrator but of coure this doesn't make any difference.

NexusTropers said:
Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message
Click to expand...
Click to collapse
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.

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

comminus said:
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.
Click to expand...
Click to collapse
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.

bazabaza said:
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.
Click to expand...
Click to collapse
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.

comminus said:
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.
Click to expand...
Click to collapse
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.

NexusTropers said:
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
Click to expand...
Click to collapse
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
NexusTropers said:
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.
Click to expand...
Click to collapse
I'm not really sure what you're trying to say...

I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.

comminus said:
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
I'm not really sure what you're trying to say...
Click to expand...
Click to collapse
1. THX u i try it.
2. AH sorry translator make crazy text.
homerbrew said:
I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.
Click to expand...
Click to collapse
Oki THX u i try this tool...

I'm also having this same problem but here's my story:
Using the Nexus 1.5.4 Toolkit, I Unrooted + Flashed jzo54k, success. I locked OEM, success. I unlocked again, success. Then I ran the root process again, and it keeps freezing at the android recovery screen. Following the prompt in the toolkit, I walked away for a few hours hoping time would resolve the issue.
If you're wondering why I unlocked + rooted, and decided to unroot, lock, unlock, and root again, its because I'm super-noob to anything android related after version 1.5, I wanted to learn the processes after I found out I was having troubles with certian things after my Nexus 7 updated from 4.1 to 4.1.2

I am having the same issue as you. 4.1.2 is not rooting for me. I can't install CWM or TWRP because it needs to rename recovery files, and to do that you need to be rooted. If I boot in recovery I always get stock

Having the same issue with a stock 4.1.2. I can unlock no problem but I cannot get it rooted. Everything appears to have worked, but it is not rooted. If I revert back to 4.1.1 I can unlock, root, etc. without issue. I was able to root 4.1.1 and use the root keeper app to then update to 4.1.2 and I was rooted still. However, it would not let me install CWM or anything. ROM Manager says it was installed, but booting to recovery always too me to stock.
Any ideas?

Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app

MetalMadness said:
Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I used Nexus Root Toolkit v1.5.4 and selected the "Flash Stock + Unroot" option. When prompted I choose the default 4.1.1 option and away it went.

To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.

hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!

hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Indy1204 said:
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!
Click to expand...
Click to collapse
Thanks. I did this earlier and it didnt work, but I checked boot instead of flash
FLASH THE OLDER BOOTLOADER DON'T BOOT IT!!!

[Q] Iam not able to install a custom recovery

Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?

Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?
Click to expand...
Click to collapse
What you are doing wrong is using a toolkit. Follow these instructions. http://forum.xda-developers.com/showthread.php?t=2018179

I use mskip's Nexus 4 Toolkit without any issues. So far I've used it to root, install clockworkmod recovery and flash the stock image after messing up a build prop edit. Saved me a lot of headaches as I haven't used adb or fastboot commands in over a year, don't even have the sdk installed any more. This is the first phone since I got my Incredible in 2010 that I actually wanted to put a custom recovery on and play with.
Here are some basic questions. Did you unlock your boot loader? Do you have usb debugging enabled? Does your device show up when when your plugged in and booted up into fastboot? Do you have the correct drivers installed? Which recovery are you trying to install and did you try the other one available? Did you use the toolkit to root and did it work?

Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp.
But everytime it comes up with the android figure and a red warning.
Seems that every tool kit like the 1.6. nexus root toolkit or the Google Nexus 4 ToolKit is not able to install/flash a recovery.
Am i doing anything wrong?
Click to expand...
Click to collapse
After you root the device using the toolkit, it is easiest to download ROM Manager or Goo.im from the Play Store to install your custom recovery.
As Ed Daddy said, it's best to use ADB, however, it would save you some times and a few headache if you could just go ahead and download ROM Manager. Sometimes people forget there are *really easy* ways to do stuffs.

KyraOfFire said:
After you root the device using the toolkit, it is easiest to download ROM Manager or Goo.im from the Play Store to install your custom recovery.
As Ed Daddy said, it's best to use ADB, however, it would save you some times and a few headache if you could just go ahead and download ROM Manager. Sometimes people forget there are *really easy* ways to do stuffs.
Click to expand...
Click to collapse
While I agree there are "really easy" ways to do things, I was trying to point him in the direction of learning.
Obviously since they don't know how to flash a recovery, they probably aren't familiar with much else.
Learning how to do things properly never hurt anyone.
Sent from my Nexus 4

Toobie said:
Hey, just got my N4 yesterday.
I rooted my device today.
I also wanted to install a custom recovery like cwm or twrp...
...Am i doing anything wrong?
Click to expand...
Click to collapse
El Daddy is correct.
Toolkits are silly on Nexus devices, for Nexus the simplest way is flashing via faboot. At the very least take the time to learn from the guide that El Daddy provided a link to. With that knowledge you'll be able to resolve issues like this and help others who get stuck.

Actually I unlocked my bootloader, rooted the device. Using normal OTA 4.2.1
But it seems that every toolkit cannot flash the recovery.
I will try it now with using adb commands...

All the toolkits are are scripts that run the fastboot and adb commands for you, they're nothing complicated and IMO from someone with experience I prefer using them now as I no longer have the sdk installed. Gave up on custom ROMs, my own and others, a long time ago.
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
Toobie said:
Actually I unlocked my bootloader, rooted the device. Using normal OTA 4.2.1
But it seems that every toolkit cannot flash the recovery.
I will try it now with using adb commands...
Click to expand...
Click to collapse
Actually it's fastboot not adb that you use to flash recoveries, two different animals. and to the poster recommending ROM Manager, its kind of borked right now and I wouldn't use it to flash anything.
Edit: spoke too soon on ROM Manager looks like Koush updated it and it appears to be working properly. This was the first app I ever bought back in 2010 when I first rooted my Eris and couldn't get clockworkmod recovery to install, the moderators at the time recommended ROM Manager to me to get it installed as nothing else worked.

Yeah, but both didn't work.
I used now the adb commands on my one, still remembering them from my Nexus One, and see it works

For sure fastboot and adb will work. I used it very recently when my n4 updated. Just make sure to download the latest cwm. Had a boot loop the first time as I used an old one. Hehehe
Edit: actually not sure if it was the old fastboot files or cwm that caused the error. Anyway I updated my sdk so everything works well
Sent from my Nexus 4 using Tapatalk 2

Actually all the tools booted the phone fine in the fastboot mode, telling me flashing the recovery is fine.
But every time i wanted to reboot in the recovery i got this android roboter with the red alarm...
with the normal adb commands everything was really fine!

You're getting that because flashing custom recovery alone without modifying a file or two generates stock recovery every after a reboot. Go to your /system folder and look for recovery-from-boot.p and rename that to whatever you like then flash the custom recovery again
Sent from my Nexus 4 using Tapatalk 2

thephantom said:
You're getting that because flashing custom recovery alone without modifying a file or two generates stock recovery every after a reboot. Go to your /system folder and look for recovery-from-boot.p and rename that to whatever you like then flash the custom recovery again
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Sounds great, will try that.
Thank you.

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!