Database Users

I think I bricked my nexus (my fault) please help!

Hello all,
I think I may have bricked my nexus one. It is completely my fault for attempting things that I knew little about, so flame away But after the flaming, if anyone is willing to help I would be sooooo thankfull...
I successfully rooted my phone following the instructions on this page: (all links edited with a double asterisk as I don't believe I can post links)
h**p://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Then successfully installed cyanogenmod (which is awesome!) following this page:
h**p://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
All was well, I even got the modaco desire rom up and running, and was happily switching back and forth using the recovery screen. I had nand backups for specific setups, etc.
Then I decided it would be good to know how to go back to stock, and found this page:
h**p://**w.androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
I followed the instructions to the letter (I think) except for erasing userdata (it said "failed: remote not allowed"). I thought that things would be ok, since I'd recently wiped, so I followed the page till the end.
The phone rebooted, and I got the original nexus boot animation - but it's in an endless loop! What's worse, it that now when I try to go to the bootloader or recovery mode, I get the exclamation triangle with the little android.
Is there any way through a command prompt (or other method) that I can fix this? I tried to re-flash the RA recovery image through the command prompt, but the response was, "waiting for device."
ANYTHING that anyone can suggest to help, I would be so thankful! I've been loving the nexus, and hate to think that I crippled it
Thanks in advance,
Randy

I doubt its bricked.
Noticed you didnt mention that fast boot doesnt work? (power button+trackball) try it.
Once you get to fastboot you can flash any ROM back. (fastboot flash **** commands from a command shell)

Did you ever perform a Nand Backup from Recovery?

It's not bricked, the only way to brick is to interrupt power when flashing a Radio image

Connect phone to PC. Open command prompt.
adb reboot recovery
Wipe, reflash.

So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One

nexus5894 said:
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
Click to expand...
Click to collapse
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404

Paul22000 said:
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Click to expand...
Click to collapse
............................

It worked!!!!!
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
​
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!

Randy Malkoski said:
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
​
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Click to expand...
Click to collapse
Glad to hear it. You learn the most by trial and error.

I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....

revonomics said:
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
Click to expand...
Click to collapse
Tell me what i need to download again and how to go about it...i really need my phone working again ((((

[Q] Formatted Nexus 10

So I had the latest version of Paranoid Android on my rooted nexus 10. The keyboard was messing up so i wanted to run a factory reset and go all the way back to stock 4.2.1. In the process I accidentally wiped both the Rom and stock from my nexus 10 leaving it with no OS and nothing but the boot-loader. If i try and go to recovery mode all i get is the android laying down with an exclamation mark in a red triangle in it's stomach or the word Google with and unlocked padlock underneath it.
Any advice/help would be amazing! Thanks!

Download the factory image from Google: https://dl.google.com/dl/android/aosp/mantaray-jop40c-factory-0d641789.tgz
If you don't have fastboot already you need that too: http://downloadandroidrom.com/file/tools/fastboot.zip
Unzip the factory image tgz I linked to with 7zip/winrar etc
Unzip the fastboot.zip contents into the folder you just extracted
open a command prompt in the folder you just unzipped (mantaray-jop40c)
Boot your device into the bootloader by holding down BOTH volume keys and the power button
Connect your Nexus 10 to your PC
At the command prompt type
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader [wait for the device to reboot back to the bootloader]
fastboot -w update image-mantaray-jop40c.zip
This will wipe, repartition and install 4.2 straight from Google back to your device.. You will be prompted to update by Google to install the 4.2.1 update shortly after you boot up.
If you didn't have Fastboot already and had to download the zip I linked to, it's highly suggested to download and install the Android SDK so you have it and more native tools at your disposal. You can do that after the fact though and optional but highly suggested if you plan on learning your device more.

Will this work even if my device WAS Android 4.2.1 JOP40D?

Jamocobi said:
Will this work even if my device WAS Android 4.2.1 JOP40D?
Click to expand...
Click to collapse
Yep.

styckx said:
Yep.
Click to expand...
Click to collapse
Awesome thanks, I'll give it a shot once the files downloaded!

You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock

styckx said:
You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock
Click to expand...
Click to collapse
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?

Jamocobi said:
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?
Click to expand...
Click to collapse
How did you unlock and root this device in the first place?

styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
With the WugFresh Nexus Root Toolkit (Sorry, Can't post a link yet)

styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!

Jamocobi said:
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!
Click to expand...
Click to collapse
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...

styckx said:
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...
Click to expand...
Click to collapse
Sorry about that, i was hoping you'd see it in time! You're definitely right about that, i was just worried i would totally mess it up if i did it myself but i can do that anyway with a toolkit so next time ill give it a shot without one.
Okay thanks, I'll take note of that one for sure! Really appreciate the help, thought i was doomed! haha!

You're welcome man.. It's no fault of your own for using the toolkit. To new users they're attractive and promise quick results.
Side note. It's extremely, insanely, stupidly hard to permanently screw up a Nexus device by flashing. There is always a way back from `the grave'.
Take care

[Q] Fastboot Reason: Sticky bit factory_fastboot?

I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.

Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app

skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.

OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app

You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y

skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.

cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?

Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!

More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.

Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.

Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful

Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!

Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:

Edit : Sorry I asked stupid question!

Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.

Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick

[Q] Before I install Kit Kat I would like to root my phone

Hello
My phone tells me that it is ready to update to Kit Kat.
Before I install Kit Kat I would like to learn how to go back to Jelly Bean if things go t1ts-up.
So, I would like to learn how to root my phone?
I would also like to learn how to backup everything including the Jelly Bean operating system, and I would like to know how to revert my phone back to Jelly Bean?
Please forgive my ignorance, but this whole process genuinely scares me. I have only ever rooted my Samsung Ace phone once and the experience left a bitter taste in my mouth.
I did manage to root my phone. I also thought that I had created a backup but when I tested the backup I discovered that my phone got wiped and I ended up with a brick. I eventually found an official Samsung ROM but it wasn't the one I wanted and it caused a few problems, especially with the Bluetooth feature.
I hope you can understand or appreciate my apprehension with even contemplating such a task on my expensive Nexus 4.
Cheers muchly

the lemming said:
Hello
My phone tells me that it is ready to update to Kit Kat.
Before I install Kit Kat I would like to learn how to go back to Jelly Bean if things go t1ts-up.
So, I would like to learn how to root my phone?
I would also like to learn how to backup everything including the Jelly Bean operating system, and I would like to know how to revert my phone back to Jelly Bean?
Please forgive my ignorance, but this whole process genuinely scares me. I have only ever rooted my Samsung Ace phone once and the experience left a bitter taste in my mouth.
I did manage to root my phone. I also thought that I had created a backup but when I tested the backup I discovered that my phone got wiped and I ended up with a brick. I eventually found an official Samsung ROM but it wasn't the one I wanted and it caused a few problems, especially with the Bluetooth feature.
I hope you can understand or appreciate my apprehension with even contemplating such a task on my expensive Nexus 4.
Cheers muchly
Click to expand...
Click to collapse
You might want to check out the Wugfresh's toolkit if you are not incline with technical stuff. The toolkit is in the Development section.

Hello
I have no idea what Wugfresh's tool-kit is.
Sorry

the lemming said:
Hello
I have no idea what Wugfresh's tool-kit is.
Sorry
Click to expand...
Click to collapse
I would suggest that you study up and follow this guide here. http://forum.xda-developers.com/showthread.php?t=2010312
I was like you when I first got the nexus. Didn't know what to do and the steps seems to be so complicated. Hell..I even took couple of days to finally succeed in installing the drivers. And for me I think it is better to learn the basics of using adb before trying out the toolkits. If you start with toolkits and you will later on rely entirely on the toolkits. This is not good as some problems, the toolkits might not be able to solve it for you.
Btw, look into original android development for wug's toolkits. It is pinned there. Should be easy to find.
Sent from my Nexus 4 using xda premium

You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
Its very very very easy in Nexus Devices.
Here is my attempt to make you learn :-
1. Say Bye Bye to your phone OS version.
2. Open Command Prompt or Terminal.(Assuming, you have SDK & Drivers installed)
Code:
adb devices
It shall return you the device id.
3. Reboot to BootLoader
Code:
adb reboot-bootloader
4. Check for your device's recognition in FastBoot Mode.
Code:
fastboot devices
5. I assume you have all the files(Factory Image tar.gz extracted to a folder)
just type :-
Code:
flash-all.bat
BOOM...
You are now on stock KitKat !
Now, To get a Custom Recovery (IMHO go with TWRP),
1. Download latest recovery from the official website.
2. Type when in FastBoot Mode.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.4-mako.img
(Or whatever the name is)
3. Reboot your device.
Now, to get the ROOT ACCESS, after booting up the device,
1. Download the latest UPDATE-SuperSU zip from here.
2. Keep it somewhere in DEVICE STORAGE.
3. open TWRP RECOVERY
4. FLASH that ZIP
5. HIT THANKS !
Have Fun ...
Welcome to the Flashing Fraternity !!! LOL

miku3191 said:
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
BOOM...
You are now on stock KitKat !
Click to expand...
Click to collapse
Hello
Thank you for replying but I fear that I will not be following your advice at the moment.
I initially asked how to ROOT my phone so that I can learn how to do backups and recoveries. My phone is ready for the Over The Air official upgrade.
I want to take things one step at a time rather than causing problems by blindly following code.
Sorry

the lemming said:
Hello
Thank you for replying but I fear that I will not be following your advice at the moment.
I initially asked how to ROOT my phone so that I can learn how to do backups and recoveries. My phone is ready for the Over The Air official upgrade.
I want to take things one step at a time rather than causing problems by blindly following code.
Sorry
Click to expand...
Click to collapse
If you want official OTA update of KitKat you should update it, and after that unlock bootloader and root phone. That way nothing will go wrong.
If you unlock bootloader and root your phone OTA update will cause problems like stuck in bootloop(your phone will be stuck on nexus logo and it will never boot into android)
If you want to learn about rooting I suggest you this http://forum.xda-developers.com/showthread.php?t=2367406
this is excelent tutorial how to root your nexus 4 http://forum.xda-developers.com/showthread.php?t=2018179
and if you are more comfortable to hear and see somebody do it you can check out this page it have video of full process and pictures for every step http://nexus4root.com/nexus-4-root/how-to-root-nexus-4-windowsmac-osxlinuxubuntu/
Good luck!:cyclops:

miku3191 said:
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
Its very very very easy in Nexus Devices.
Good luck!:cyclops:
Click to expand...
Click to collapse
This process is an absolute nightmare.
All I want to do is back-up my Jelly Bean phone operating system and have it safe in case the OTA Kit Kat goes wrong. I thought that this was sensible and safe practice before doing any updates, especially something as serious as a system update?
I have now tried several Tutorials on how to root my phone and all I have succeeded in doing is wiping my phone clean and returning it to Factory Settings. The latest Tutorial was here
http://forum.xda-developers.com/showthread.php?t=2010312
I followed the following advice to this point
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
I then get to the bit about rooting
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
http://www.clockworkmod.com/rommanager/
http://www.clockworkmod.com/rommanager/developers/mako?name=Google Nexus 4
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.

the lemming said:
This process is an absolute nightmare.
All I want to do is back-up my Jelly Bean phone operating system and have it safe in case the OTA Kit Kat goes wrong. I thought that this was sensible and safe practice before doing any updates, especially something as serious as a system update?
I have now tried several Tutorials on how to root my phone and all I have succeeded in doing is wiping my phone clean and returning it to Factory Settings. The latest Tutorial was here
http://forum.xda-developers.com/showthread.php?t=2010312
I followed the following advice to this point
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
I then get to the bit about rooting
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
http://www.clockworkmod.com/rommanager/
http://www.clockworkmod.com/rommanager/developers/mako?name=Google Nexus 4
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
The point you are missing is that your fear is clouding your ability to simply read and comprehend the proper steps to take. My friend rooting your phone with a toolkit is a simple task but you ask what is Wugs toolkit instead of taking the time to search for it an read up. YOu do not want to root your phone but to have someone do it for you. I used to do this for people back in the days where I would log into their pc and root their phones from my home.
My friend its simple your bootloader is unlocked and now all you need to do is push a recovery over to your phone. Now go to the TWRP thread and download the image file and follow the instructions given to you to flash the recovery. I fear if following these simple directions are too much for you maybe you should simply leave your phone alone before the next step is you calling Google with an issue or having to buy another phone...
Sorry but thats my honest opinion....
Edit: Boot into bootloader and check to see if its says unlocked. If so then all thats left is flashing a recovery

the lemming said:
This process is an absolute nightmare.
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
Reading your posts, I understand your frustration. Here are my suggestions, 1) step away from your PC for a few minutes or an hour or get a cup of water, 2) put the phone aside, 3) read and re-read the information in Google Nexus 4 threads just to get the knowledge first and then start working on your phone. You will be doing fine. BTW, you should have a back up phone that you can use while working on your Nexus 4.

playya said:
Edit: Boot into bootloader and check to see if its says unlocked. If so then all thats left is flashing a recovery
Click to expand...
Click to collapse
Thank you for this useful bit of information.

the lemming said:
Thank you for this useful bit of information.
Click to expand...
Click to collapse
You got it man I know but sometimes the truth hurts... You have been given all the information laid out for you in the posts above. If this is still too difficult for you your only other task is to actually have somebody do it for you this is nothing more than simply reading and taking your time. I tell you this with all sincerity I would rather see you stop now than later see another thread created by you saying possibly bricked
Sent from my Nexus 4 using Tapatalk
---------- Post added at 02:51 PM ---------- Previous post was at 02:51 PM ----------
playya said:
You got it man I know but sometimes the truth hurts... You have been given all the information laid out for you in the posts above. If this is still too difficult for you your only other task is to actually have somebody do it for you this is nothing more than simply reading and taking your time. I tell you this with all sincerity I would rather see you stop now than later see another thread created by you saying possibly bricked
Take care
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Sent from my Nexus 4 using Tapatalk

the lemming said:
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
I trust that you have read the entire guide from that link you post. To get you see this clearly. Rooting is very easy. You just have to:
1. Install driver, download platform-tools (if you don't wanna download the entire android sdk) and SuperSU I trust that all the links are given in that guide.
2. Make sure you device is detected in adb. Copy SuperSU.zip into your device.
3. Unlock your device.
4. Push recovery. fastboot flash recovery recovery name.img
5. Reboot into recovery and flash SuperSu.zip
6. Reboot. Done.
Really..this is all it takes to perform a simple rooting. But if you're not the one who likes to read..and try to understand the steps. I suggest you not to mess with your device. You are more likely to brick it than make it better. The truth hurts but it is for your own good. Unless you prove me wrong. Then you are awesome instead
Sent from my Nexus 4 using xda premium

8.1 OTA **UPDATED/FIXED** New OTA files available

UPDATE -- ISSUE RESOLVED
*** New OTA available ***
See links below
Updated zip confirmed working here:
https://plus.google.com/100708818877715770270/posts/dEyVgqmURw2
Android Beta Program:
https://g.co/androidbeta
OTA Download:
NEW (fixes both OTA and sideload failures)
https://ota.googlezip.net/packages/.../1c0e174d9aeefbb176b4dd38b48270a0fd4082d9.zip

pangolin.rollin said:
For those experiencing issues updating to 8.1 on locked n stock f/w there is now a fix!!!
Source and Credit goes to "AC" : [url]https://issuetracker.google.com/issues/68264793[/URL]
See post #64 and #71
FIX SUMMARY
1. Enroll in beta ota
2. Download ota
3. Enable Developer mode
4. When update screen says "Reboot to update" DON'T click it but rather issue "adb reboot recovery"
5. Once in bootloader go to recovery like normal and ensure it says recovery 8.1
6. You may then enable update from adb for sideload.
7. When pixel is in ready to receive update issue "adb sideload <update.zip>"
8. Profit
Android Beta Program:
https://g.co/androidbeta
OTA Download:
[url]https://ota.googlezip.net/packages/ota-api/google_sailfish_sailfish/42c4425cf03125fe7c535e39cbac7d17c1a2f65a.zip[/URL]
Please post your success stories or issues.
I was on OPR3.170623.008 when this was done.
Click to expand...
Click to collapse
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
Although i commend you trying to summarize the steps, they are wrong
adb reboot recovery is not a valid command ; i believe what you meant was
Code:
adb reboot bootloader
And i am not sure about this, but i think turning on developer mode is entirely optional.

NoobInToto said:
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
...
And i am not sure about this, but i think turning on developer mode is entirely optional.
Click to expand...
Click to collapse
Oops yeah updated to bootloader, hadn't seen the post before or anything on XDA. Been following the normal circles. Can't hurt to spread the news!
The whole reason for suggesting the "optional" part of developer mode is cause if you try just the regular reboot /key press combo and miss it you have to redo the OTA download which is rather annoying. Rather just remove that possibility.

NoobInToto said:
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
Although i commend you trying to summarize the steps, they are wrong
adb reboot recovery is not a valid command ; i believe what you meant was
Code:
adb reboot bootloader
And i am not sure about this, but i think turning on developer mode is entirely optional.
Click to expand...
Click to collapse
adb reboot recovery is definitely a valid command (assuming you're running a current version of ADB).
Enabling developer mode was not part of my original post, I don't think it is required, but then I was running it anyway. Entering recovery through a command rather than having to catch it at exactly the right moment with the key command is definitely easier, but I hadn't tested it that way when I did this originally. Glad this works too, it's much easier.
Also, glad people are finding this useful!

pangolin.rollin said:
Oops yeah updated to bootloader, hadn't seen the post before or anything on XDA. Been following the normal circles. Can't hurt to spread the news!
The whole reason for suggesting the "optional" part of developer mode is cause if you try just the regular reboot /key press combo and miss it you have to redo the OTA download which is rather annoying. Rather just remove that possibility.
Click to expand...
Click to collapse
Ah, now I get it. I forgot you needed usb debugging for adb when booted in system.
Anyways, booting in bootloader mode was easy, it is very hard to miss. One has to press power+volume down immediately after first bootloop, when the screen is back, and i was able to get into bootloader mode within 1 second.
---------- Post added at 05:11 AM ---------- Previous post was at 05:09 AM ----------
ACastanza said:
adb reboot recovery is definitely a valid command (assuming you're running a current version of ADB).
Enabling developer mode was not part of my original post, I don't think it is required, but then I was running it anyway. Entering recovery through a command rather than having to catch it at exactly the right moment with the key command is definitely easier, but I hadn't tested it that way when I did this originally. Glad this works too, it's much easier.
Also, glad people are finding this useful!
Click to expand...
Click to collapse
I had checked adb reboot recovery when booted in system. It did not work in 8.0.0.

Woops, I only read the first part of your post. Nevermind.

NoobInToto said:
I had checked adb reboot recovery when booted in system. It did not work in 8.0.0.
Click to expand...
Click to collapse
Your right it doesn't work in 8.0. That's why I specified to do it when it says "reboot to update" because when the system "pre-loads" the OTA it switches the active boot slot for next reboot. That's why doing it this way works as well.

ACastanza said:
Woops, I only read the first part of your post. Nevermind.
Click to expand...
Click to collapse
Huh? lol..
Anyways man didn't mean to steal your thunder. Just glad we're on 8.1.
You're the best! :good:

pangolin.rollin said:
Huh? lol..
Anyways man didn't mean to steal your thunder. Just glad we're on 8.1.
You're the best! :good:
Click to expand...
Click to collapse
No worries! Just glad people are getting updated without needing to factory reset.
(ADB rebot recovery actually does work on 8.0 but you need to have adb debugging enabled and need a new-ish version of the ADB binary).

ACastanza said:
No worries! Just glad people are getting updated without needing to factory reset.
(ADB rebot recovery actually does work on 8.0 but you need to have adb debugging enabled and need a new-ish version of the ADB binary).
Click to expand...
Click to collapse
Oh, yeah, the latest one not only has reboot recovery, but direct reboot to sideload options too....sweet
Btw there is a second workaround. It involves adb sideloading the same build (8.0.0) and then sideloading the Dev preview.

This worked for me. Looked like it was bootlooping again at first, but eventually booted into 8.1.0. Thanks!

invisibro said:
This worked for me. Looked like it was bootlooping again at first, but eventually booted into 8.1.0. Thanks!
Click to expand...
Click to collapse
Yup, strangely enough, that is the expected behavior for this workaround. @pangolin.rollin should include info about it in the OP post.

What am I missing here? I enrolled in the beta (Verizon locked bl) yesterday and within about an hour I had a notification to update to the beta. I clicked download and install and on the reboot I was running 8.1. What's all this about bootlooping, slots, rebooting bootloader? I did none of that and it worked flawlessly.

NoobInToto said:
Yup, strangely enough, that is the expected behavior for this workaround. @pangolin.rollin should include info about it in the OP post.
Click to expand...
Click to collapse
Updated op thanks
** Fixes "parse error -22" and update not installed, while this works first boot looks like it's looping. **

bobby janow said:
What am I missing here? I enrolled in the beta (Verizon locked bl) yesterday and within about an hour I had a notification to update to the beta. I clicked download and install and on the reboot I was running 8.1. What's all this about bootlooping, slots, rebooting bootloader? I did none of that and it worked flawlessly.
Click to expand...
Click to collapse
Your lucky then! Not sure of the official cause of the errors and why some work and some don't. But seems some devices have issues verifying. That's why Google even pulled ota images.

So I presume that the only problems were with sideloading? I never do that on my Pixel since I just like it updating in the background, reboot and done. With a locked bootloader I can't take a chance of doing something wrong. If they send me an image or OTA that bootloops then it's not my problem and they have to either fix it or replace it. Nonetheless, it's working very well and the reboot wasn't long at all. Might be the better way to go.

I did this fix and although it did work, now when I wake the device back up it takes a long time to do so. Double tapping the screen doesn't work at all, and when I hit the power button it takes about 5 seconds before the screen turns on. I'm going to try to sideload the ota again and see if it fixes it.
EDIT: Nope, still having the same issue

cred05 said:
I did this fix and although it did work, now when I wake the device back up it takes a long time to do so. Double tapping the screen doesn't work at all, and when I hit the power button it takes about 5 seconds before the screen turns on. I'm going to try to sideload the ota again and see if it fixes it.
EDIT: Nope, still having the same issue
Click to expand...
Click to collapse
Haven't heard of this problem yet.. were you on stock OPR3 with locked bootloader?

There is a new OTA (for same build, but new working OTA) for 8.1 rolling out.
https://plus.google.com/100708818877715770270/posts/dEyVgqmURw2
Please can someone grab the OTA URL?
Settings > System > Developer Options > Take Bug Report > Full Bug Report, then email it to yourself (or PM it to me) and search for the URL ending with ".zip".
I don't have a sailfish device on me right now to do it myself. Thanks!
Edit: here it is
https://ota.googlezip.net/packages/.../1c0e174d9aeefbb176b4dd38b48270a0fd4082d9.zip

pangolin.rollin said:
Haven't heard of this problem yet.. were you on stock OPR3 with locked bootloader?
Click to expand...
Click to collapse
I was on stock 8.0 OTA, locked bootloader. The issue seemed to have gone away by itself. Very strange