Database Users

I'm bricked .. Getting worries. (Yes I've read the forums ...)

Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "ADB reboot loader" or ..."fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!

Rovon said:
Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!
Click to expand...
Click to collapse
Use Wugfresh's toolkit and press "return to stock"

rohan32 said:
Use Wugfresh's toolkit and press "return to stock"
Click to expand...
Click to collapse
"I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen. "

Here's an update:
I think I've made it worse ...
Nothing will boot now and it's currently locked. Any time I hit "Start" it says "Booting Failed"
My CMD now says; Error: Cannot Load "Bootloader Grouper-3.34.img"
I'm seriously lost. I've been working on this for about 6 hours now ....

Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??

markj338 said:
Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??
Click to expand...
Click to collapse
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"

Rovon said:
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"
Click to expand...
Click to collapse
Where does it say boot failed? On the device?

markj338 said:
Where does it say boot failed? On the device?
Click to expand...
Click to collapse
Yes. Top left hand corner.

Rovon said:
Yes. Top left hand corner.
Click to expand...
Click to collapse
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?

markj338 said:
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?
Click to expand...
Click to collapse
No I can't get into the recovery at all. When I turn on the device I don't even need to use the rocker keys to get into bootloader either. Actually my bootloader is a bit different now too. I have the 'Google' logo and at the top the regular options for Start, Recovery, Power Off, etc.
In simple terms: I can't even get to the animated splash screen anymore

Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.

Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app

Alkaloid said:
Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I've followed the instructions in the file. From previous research, I've had these files. My device does communicate with Fastboot. When I give the command for Devices it gives me my serial. Also, when I ask it to reboot-bootloader in CMD it does.
My issue is when I get to "Fastboot flash bootloader-grouper-3.34.img". CMD states "Error: Cannot load bootloader-grouper-3.34.img"
I've followed the commands previous to that. (Erase boot, cache, recovery, system, userdata)
Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.
Click to expand...
Click to collapse
Yes my device is unlocked again, but I still can't get into recovery mode. It just tells me "Recovery Failed" in small text in the upper left hand corner of my N7.

UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.

Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
For the love of God..stop using the toolkit from here on out.. learn how to use ADB and Fastboot so you can avoid these issues.
Sent from my Galaxy Nexus using Tapatalk 2

So you erased the recovery then wonder why you could not boot into recovery....
You flashed or tried to flash the bootloader. You already had the same bootloader installed and there was no need to do so to try and fix your issue.
You still don't know what you're doing and are back using the tool that lead you to this issues. A toolkit. Learn what you're doing and you wont face this type of silly issue again.

Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
I think you should reread this post and hit the thanks button of everyone who took the time to help you out of this mess - its good manners. Oh, and learn how to use adb & fastboot
Sent from my Nexus 7 using xda premium

Inaccessible boot loader :/
If you try to fastboot flash all you get nothing?
Sent from my Nexus 7 using xda app-developers app
---------
nvm you fixed it, good job
Don't use toolkits. Most people don't have a clue what the toolkit is actually doing so if something goes wrong they aren't in a good position

Its always nice to see threads like these where the N7 in the face of death but in the end with cutting edge medical technology it is brought back to life and healthy.

[Q]Manually updated to 4.2.2... Now locked out of adb and recovery. Help.

I'm in a bit of jam. I flashed the official zip from google to update to 4.2.2 and the flash seemed to work fine. I cleared both caches after the update
However, now I seem to be completely locked out of adb and the phone doesn't prompt me for authorization (the new feature in 4.2.2) http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ . I am showing connected but offline just like this article. I have tried multiple reboots (phone/computer) as well as different USB ports. I have not tried another computer yet.
When I try to go to recovery I get a red exclamation point dead robot as I assume the flash wiped TWRP and I can't reflash TWRP without adb/root.
I would like to try to avoid a complete internal memory factory reset from the rom which I'm not sure would work anyway.
Please help.

update your adb / sdk.

bodh said:
update your adb / sdk.
Click to expand...
Click to collapse
Fortunately, I was able to reflash TWRP using fastboot w/o using adb. At the bootloader, I ran
Code:
fastboot flash recovery recovery.img
which got my recovery back up and running.
I decided to do a factory wipe and even after that adb was showing as offline and not prompting. I am very confident that your suggestion of updating the platform tools is going to fix my issue.
Thank you.

Locked on 4.2.2
My Nexus 7 is locked on 4.2.2. I tried to Unlock with Nexus Root Toolkit and I get "adb offline". I did the command "adb devices" and the device showed up, but when I tried to unlock again, it gets stuck on "checking adb status". I updated SDK and copied the new adb.exe, fastboot.exe, etc into the platform-tools folder and it still doesnt work. So basically my oem is locked on 4.2.2 and I can get adb or the toolkit to work properly.. Is there a way to downgrade back to 4.2.1 or get the Wugfresh Nexus Toolkit to actually unlock my Nexus 7 on 4.2.2??

Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.

bodh said:
Yea, there's a way to downgrade if you have a nandroid and know what you're doing. The toolkit will need to be updated, and it helps to know how to do it manually first.
Click to expand...
Click to collapse
If you know the steps or can link me to a page, that would be much appreciated. I want clear steps.

Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.

Why cant people wait..
lol

Bronk93 said:
Basically the same thing just happened to me. I updated to the newest android sdk then followed the steps here http://forum.xda-developers.com/showthread.php?t=2010312
I had to restore the complete stock image first, then I sideloaded the update. I made sure all of my files were in C:\Development\sdk\platform-tools (thats the directory I used, yours may be different). Open a command prompt on the platform-tools folder and run fastboot devices, if you see a number there you are good to go. Just follow the steps in the link above to flash each file.
Click to expand...
Click to collapse
I'm going to try this. Can i just type "fastboot devices" in the command prompt and it'll work?
EDIT: I found a simple fix for anyone with this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.

AJ Bryant said:
I'm going to try this. So would I have to copy a fastboot.exe into the platform-tools folder? Or can i just type "fastboot devices" in the command prompt and it'll work?
Click to expand...
Click to collapse
If you downloaded the new android sdk fastboot should already be in there

I found a simple fix for this problem: CREATE A BACKUP FIRST, THIS WILL ERASE EVERY THING
1. Go into the platform-tools and open the command prompt by pressing Shift + Right Click.
2. Type in "adb reboot bootloader"
3. Then type in "fastboot oem unlock"
4. WALA! It'll take a while to start up, don't worry. Set up your device and that's all.
---------- Post added at 12:05 PM ---------- Previous post was at 11:55 AM ----------
XX-RAZOR-XX said:
Why cant people wait..
lol
Click to expand...
Click to collapse
No need to wait because I found the fix, by myself.

Can't wait to get home and try this. I got stuck last night at adb offline
Sent from my Nexus 4 using xda app-developers app

But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895

bodh said:
But with oem unlock, you'll still be on 4.2.2. This thread should offer good info on flashing, albeit for a galaxy nexus, but it should be mostly applicable for a nexus 7. http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
That's the point; we want to be unlocked and rooted on 4.2.2. I previously thought that in order to get an unlocked and rooted Nexus, I'd have to be on 4.2.1, unlock and root, then upgrade to 4.2.2 but that's not the case. I just unlocked and rooted via ADB since the Nexus Root Toolkit wasn't working for 4.2.2. I (and probably others) kept getting the "adb offline" error even after allowing USB debugging between the device and PC. Point is, if you're on 4.2.2 with a locked bootloader, you'll need to unlock and root using ADB commands. I don't know how many people have this issue but if someone requests it, I'll just post the steps on how to unlock and root 4.2.2 jelly bean using the ADB commands.

Re: [Q]Manually updated to 4.2.2... Now locked out of adb and recovery. Help
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app

Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.

bodh said:
Place su.zip on sdcard. Reboot in fastboot mode, probably volume up+down+power. In terminal on pc, fastboot boot cwm.img for your device, install zip from sdcard.
Click to expand...
Click to collapse
What do u mean by terminal on my PC fast boot cwm.img
Sent from my Nexus 4 using xda app-developers app

Rooting Jelly Bean 4.2.2 via ADB
DowntownJeffBrown said:
What if I'm on 4.2.2 completely stock but with an unlocked boot loader. I get the adb offline message when I try to root using a toolkit. How would I go about rooting?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.

AJ Bryant said:
1. Download the SuperSU.zip from here: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip and place it on your device in the sdcard. I'm assuming you already enabled USB debugging.
2. Download the recovery-clockwork-touch-6.0.1.0-grouper.img from here: https://www.dropbox.com/s/v4hjsb4lse3dwtc/cwm6010touch_INSTALL.zip and place it in the platform-tools folder. Assuming you know where it's located on your PC
3. Locate the "platform-tools" folder on your PC, open it, and press Shift + Right Click & Open the command prompt there.
4. Type in the command "Adb reboot bootloader"
5. Then type in the command "fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img"
6. Now go to Recovery Mode on your Nexus and install the CWM-SuperSU-v0.98.zip from there.
7. Reboot the device once you're done and you have a rooted Nexus 7 via adb. Hope this helps.
Click to expand...
Click to collapse
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app

DowntownJeffBrown said:
What about for a nexus 4. Do u know where I can get that cwm?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
For the Nexus 4 use this cwm image instead: http://download2.clockworkmod.com/re...0.2.3-mako.img
When youre doing the fastboot recovery, put in the name of this img file at the end. "fastboot flash recovery [name of the download file].img

[Q] Re-root after 4.3 OTA update?

I sideloaded the 4.3 OTA and it worked great but now I've lost root.
When I start SuperSU i tells me to re-root but how do I do that? My boot loader is already unlocked so do I lock it and then unlock it again (and loose all my data) or is there another way?

No need to lock/unlock or lose any data. You have to flash the updated su zip file through a custom recovery.
Sent from my Nexus 4 using xda premium

mbeltoft said:
I sideloaded the 4.3 OTA and it worked great but now I've lost root.
When I start SuperSU i tells me to re-root but how do I do that? My boot loader is already unlocked so do I lock it and then unlock it again (and loose all my data) or is there another way?
Click to expand...
Click to collapse
Get ChainFires last SuperSU and flash in recovery.

can i do it via adb? - i really don't wanna install a custom recovery
EDIT:
fastboot should be able to do it using this command: fastboot update UPDATE-SuperSU-v1.43.zip but i get the error:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

mbeltoft said:
can i do it via adb? - i really don't wanna install a custom recovery
EDIT:
fastboot should be able to do it using this command: fastboot update UPDATE-SuperSU-v1.43.zip but i get the error:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
If you don't want to install a custom recovery, you can use fastboot to just boot to it once and install supersu, without actually flashing the recovery. Just download the recovery (I've always used Cwm for this), put it in the folder with fastboot, boot to the bootloader, and type fastboot boot imagename.img. You'll reboot to the custom recovery, but it won't flash it.
Sent from my Nexus 10 using XDA Premium HD app

nyijedi;43986325ust download the recovery (I've always used Cwm for this) said:
Thank you for helping out...I have the same issue but I cannot figure out what to do with your instructions above. Would you be kind enough to provide a more detailed manual of what this means (ie for noob like me)? My nexus 7 was rooted and working fine using SuperSU until I did 4.3 update by OTA. Also, will this delete my user data?
Many thanks
Well for anyone interested, I sorted this by using WugFresh and selected root device. I did not delete my data. Perfect tool for noob.
Click to expand...
Click to collapse

How can I root 4.3 on nexus 10 without losing data. My boot loader is locked and all the instructions need an unlocked boot loader which will delete data to do. In stuck. I had my boot loader unlocked but I licked it with bootlocker from play store before ota update and I used voodoo root keeper but obviously that failed so now I can't reunlock my boot loader and I can't get root. Any help please?
Sent from my Xperia Play (r800x)

fcna72 said:
Thank you for helping out...I have the same issue but I cannot figure out what to do with your instructions above. Would you be kind enough to provide a more detailed manual of what this means (ie for noob like me)? My nexus 7 was rooted and working fine using SuperSU until I did 4.3 update by OTA. Also, will this delete my user data?
Many thanks
Well for anyone interested, I sorted this by using WugFresh and selected root device. I did not delete my data. Perfect tool for noob.
Click to expand...
Click to collapse
You need to download a recovery .img, and in a command prompt/terminal, run:
fastboot boot recovery <path-to-recovery.img> (obviously, if you're running fastboot from an .exe, you'll need to run fastboot.exe boot recovery <path-to-recovery.img> instead). That will send the custom recovery image to the device, load it into memory, and boot once.
abdel12345 said:
How can I root 4.3 on nexus 10 without losing data. My boot loader is locked and all the instructions need an unlocked boot loader which will delete data to do. In stuck. I had my boot loader unlocked but I licked it with bootlocker from play store before ota update and I used voodoo root keeper but obviously that failed so now I can't reunlock my boot loader and I can't get root. Any help please?
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Until we see another locked-bootloader tool like motochopper, you're stuck. I would try using a tool like Helium to grab your backups and then bite the bullet and do an unlock. Given the changes in Android 4.3, the recovery flash is the only known way to get full root right now.

Rirere said:
You need to download a recovery .img, and in a command prompt/terminal, run:
fastboot boot recovery <path-to-recovery.img> (obviously, if you're running fastboot from an .exe, you'll need to run fastboot.exe boot recovery <path-to-recovery.img> instead). That will send the custom recovery image to the device, load it into memory, and boot once.
Until we see another locked-bootloader tool like motochopper, you're stuck. I would try using a tool like Helium to grab your backups and then bite the bullet and do an unlock. Given the changes in Android 4.3, the recovery flash is the only known way to get full root right now.
Click to expand...
Click to collapse
Actually I was able to root without unlocking using n-crys nexus toolkit. Then from there I unlocked my bootloader using the boot unlocked app so I still have all my data
Sent from my Nexus 10 using xda app-developers app

abdel12345 said:
How can I root 4.3 on nexus 10 without losing data. My boot loader is locked and all the instructions need an unlocked boot loader which will delete data to do. In stuck. I had my boot loader unlocked but I licked it with bootlocker from play store before ota update and I used voodoo root keeper but obviously that failed so now I can't reunlock my boot loader and I can't get root. Any help please?
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
I have locked bootloader and rooted after 4.3. (Stock recovery and everything)
How i did it was pretty easy:
- Reboot to bootloader (Either manually or "adb reboot bootloader")
- "fastboot boot recovery.img" (latest cwm recovery or whichever you prefer)
- then install latest superSU.zip (either directly from internal memory or via sideload)
- then reboot and you're done (ROM overwrites the "temporary" recovery with stock again when booting)
At least this as far as i understand it, and it works perfectly for me.

Drood said:
I have locked bootloader and rooted after 4.3. (Stock recovery and everything)
How i did it was pretty easy:
- Reboot to bootloader (Either manually or "adb reboot bootloader")
- "fastboot boot recovery.img" (latest cwm recovery or whichever you prefer)
- then install latest superSU.zip (either directly from internal memory or via sideload)
- then reboot and you're done (ROM overwrites the "temporary" recovery with stock again when booting)
At least this as far as i understand it, and it works perfectly for me.
Click to expand...
Click to collapse
Look at the post right above you and you will see I already solved it lol but thanks anyways.
Sent from my Xperia Play (r800x)

abdel12345 said:
Look at the post right above you and you will see I already solved it lol but thanks anyways.
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Haha, yeah true.. sorry about that My eyes aren't what they used to be i guess.. hehe

because we all don't won't someones toolkit...
abdel12345 said:
Look at the post right above you and you will see I already solved it lol but thanks anyways.
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
I'm actually really glad drood posted his method as it doesn't rely on any so called toolkits written by anybody and explains how to just do it with adb and booting one time into a custom recovery. I too am in this same position and have always used chainfires root-keeper to get root back after doing an upgrade.
I've always thought it was pretty cool having bootloader locked, stock recovery, always getting all the OTA's directly and having ROOT! :victory:

Drood said:
I have locked bootloader and rooted after 4.3. (Stock recovery and everything)
How i did it was pretty easy:
- Reboot to bootloader (Either manually or "adb reboot bootloader")
- "fastboot boot recovery.img" (latest cwm recovery or whichever you prefer)
- then install latest superSU.zip (either directly from internal memory or via sideload)
- then reboot and you're done (ROM overwrites the "temporary" recovery with stock again when booting)
At least this as far as i understand it, and it works perfectly for me.
Click to expand...
Click to collapse
fastboot boot recovery.img no longer works on the Nexus 4 because of a change in 4.3. I assume it no longer works on the Nexus 10 also. The new command for the Nexus 4 is fastboot -c "lge.kcal=0|0|0|x" boot recovery.img. I don't know if the same string works on the Nexus 10 or not. Replace recovery.img with the name of the recovery image you want to boot to.

xda6969 said:
fastboot boot recovery.img no longer works on the Nexus 4 because of a change in 4.3. I assume it no longer works on the Nexus 10 also. The new command for the Nexus 4 is fastboot -c "lge.kcal=0|0|0|x" boot recovery.img. I don't know if the same string works on the Nexus 10 or not. Replace recovery.img with the name of the recovery image you want to boot to.
Click to expand...
Click to collapse
Fastboot boot recovery.img worked fine on my N10.
Sent from my Nexus 10 using xda app-developers app

On my N10 when supposed to reboot to recovery is just power down?

Drood said:
I have locked bootloader and rooted after 4.3. (Stock recovery and everything)
How i did it was pretty easy:
- Reboot to bootloader (Either manually or "adb reboot bootloader")
- "fastboot boot recovery.img" (latest cwm recovery or whichever you prefer)
- then install latest superSU.zip (either directly from internal memory or via sideload)
- then reboot and you're done (ROM overwrites the "temporary" recovery with stock again when booting)
At least this as far as i understand it, and it works perfectly for me.
Click to expand...
Click to collapse
The above method worked for me too. :good: No issues with fastboot as descrived above on my nexus 10 with locked bootloader. No data lost. :laugh:
Thank you.

help
PuroKaibil said:
The above method worked for me too. :good: No issues with fastboot as descrived above on my nexus 10 with locked bootloader. No data lost. :laugh:
Thank you.
Click to expand...
Click to collapse
I must be missing something , but I get the following error when i try and boot the recovery,
./fastboot boot openrecovery-twrp-2.6.0.0-mako.img
downloading 'boot.img'...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.010s
Yes my boot loader is locked and im all stocked, but it seems others can do this so im more sure what I'm doing wrong, or have I missed something any help would be great thanks
G/
Nexus 4 & 7 running 4.3 both were rooted, but lost during OTA

Nexus 10 update
Reading through this thread I started to wonder something.
My nexus 10 already downloaded the update to 4.3 and wants to install it.
My nexus 10 is unlocked and rooted, what's the best way to install the update?
I get the feeling the OP installed the update without locking and unrooting, is that okay to do? Or may that cause complications?

Tangonaf said:
Reading through this thread I started to wonder something.
My nexus 10 already downloaded the update to 4.3 and wants to install it.
My nexus 10 is unlocked and rooted, what's the best way to install the update?
I get the feeling the OP installed the update without locking and unrooting, is that okay to do? Or may that cause complications?
Click to expand...
Click to collapse
I'm pretty sure you can just go ahead and install the update.
You will loose root though, but can easily re-root using the earlier mentioned method.
---------- Post added at 04:35 PM ---------- Previous post was at 04:29 PM ----------
gymmy said:
I must be missing something , but I get the following error when i try and boot the recovery,
./fastboot boot openrecovery-twrp-2.6.0.0-mako.img
downloading 'boot.img'...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.010s
Yes my boot loader is locked and im all stocked, but it seems others can do this so im more sure what I'm doing wrong, or have I missed something any help would be great thanks
G/
Nexus 4 & 7 running 4.3 both were rooted, but lost during OTA
Click to expand...
Click to collapse
I'm far from an expert here, and have never seen that error, but maybe try cwm recovery instead of twrp could be worth a try?
And, downloading the latest adb/fastboot, if you haven't already?
Just brainstorming here =)

[Q] How can I root a stock nexus 4 kitkat 4.4.2 KOT49H?

Hello fellow XDA. I was wondering if anyone was successful at unlocking and install twrp on a stock NEXUS 4 running 4.4.2 KOT49H? I have searched ang googled but have no luck on a legitimate guide. Any information is appreciated. Thanks for reading.

Try the toolkits available on the forum
Sent from my Nexus 5 using Tapatalk

jyuuken said:
Try the toolkits available on the forum
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I never used the toolkit when I rooted the nexus 4 running stock jelly bean a while back, it just seem unreliable when I read up on it. I used Fastboot instead. Anyway, looks like no one in this forum who has successfully rooted a stock kit kat 4.4.2 yet it seems .

How to Root Nexus 4 and Get a Custom Recovery: http://youtu.be/7mHy32B-GFM

Good on you for not using toolkits. First make sure you have the correct drivers installed, as well as latest versions of adb and fastboot. Then you have to unlock the bootloader (wipes your device). Go into bootloader mode either by using the command 'adb reboot bootloader' (with usb debugging enabled) or by switching your phone off, holding both volume keys then pressing the power button. Then use the command 'fastboot oem unlock'
Next flash a custom recovery. (I suggest TWRP as it has root function built in and seems to work best.) 'fastboot flash recovery "nameofrecovery.img"'
Then boot into your custom recovery. From there reboot to system and TWRP will prompt you to root your device, alternatively you could sideload supersu http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip.

DrFredPhD said:
Good on you for not using toolkits. First make sure you have the correct drivers installed, as well as latest versions of adb and fastboot. Then you have to unlock the bootloader (wipes your device). Go into bootloader mode either by using the command 'adb reboot bootloader' (with usb debugging enabled) or by switching your phone off, holding both volume keys then pressing the power button. Then use the command 'fastboot oem unlock'
Next flash a custom recovery. (I suggest TWRP as it has root function built in and seems to work best.) 'fastboot flash recovery "nameofrecovery.img"'
Then boot into your custom recovery. From there reboot to system and TWRP will prompt you to root your device, alternatively you could sideload supersu http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip.
Click to expand...
Click to collapse
Seems like it's the same step when I rooted when it was at jellybean. I'm just making sure since certain android version might require other method of rooting. I will try and let you guys know. Thanks again for all input.

Hey guys I just unlocked, rooted, and installed the latest TWRP recovery on my phone. Yay-ugh :victory: Anyway I wanted to install a couple rom that works with this 4.4.2 KITKAT. I have the Paranoid Android 3+ with that awesome pie feature before when I was in jelly bean, but I was wondering if that rom is compatible with my currents stock rooted kitkat? Also any suggestion on compatible kernel that goes with it? Please let me know which kernel version as well.

Can flashifly w/o boot unlock?

Hey
I have a HP slate 7 extreme on 4.2.2 , rooted by vroot. Still have boot loader lock and no custom recovery, can I just use flashify to flash cwm or twrp? I tried all ways to get boot loader unlock but can't see device. Would love some input
Thx

Sazz said:
Hey
I have a HP slate 7 extreme on 4.2.2 , rooted by vroot. Still have boot loader lock and no custom recovery, can I just use flashify to flash cwm or twrp? I tried all ways to get boot loader unlock but can't see device. Would love some input
Thx
Click to expand...
Click to collapse
with bootloader lock, i think that impossible

Well, that really sucks, been trying many ways to unlock bootloader to install cwm or twrp.....my HP slate 7 extreme 4.2.2 not been see by my computer and can't issue cmd to OEM unlock using tom`s super tool.

Sazz said:
Well, that really sucks, been trying many ways to unlock bootloader to install cwm or twrp.....my HP slate 7 extreme 4.2.2 not been see by my computer and can't issue cmd to OEM unlock using tom`s super tool.
Click to expand...
Click to collapse
u can do this by the cmd. download the super tool. in option 8 install drivers. exit of super tool, open cmd and type fastboot devices.
if appear a letters and number, your device has recognized
type fastboot oem unlock, in your device will appear if you want unlock. confirm and reboot device

Thx for replying, but I am using the super tool. Did all that driver thing with impactor and use cmd to OEM unlock but my com doesn't recognize it so can't unlock bootloader. This were I am stuck. Thought being rooted might make it much easier to install custom recovery .

Have you checked HPs site to see if they have drivers? The only piece of this puzzle that you're missing are the drivers... the rest should work just fine afterward.

Sazz said:
Thx for replying, but I am using the super tool. Did all that driver thing with impactor and use cmd to OEM unlock but my com doesn't recognize it so can't unlock bootloader. This were I am stuck. Thought being rooted might make it much easier to install custom recovery .
Click to expand...
Click to collapse
See my HP Slate 7 Extreme Root post: http://forum.xda-developers.com/showthread.php?t=2850893