I had everything all set - CWM working, New Rom, New OC Kernel - all working fine.
Then I used LCD Modder to change the LCD to tablet mode and installed the play store. After the reboot I get ZILCH - no CWM boot to recovery, no boot up no nothing!
Is there a way to get this going using USB from my W7? Can someone point me to a link that shows what to do or am I screwed?
Please help!
I am an expert user, just need the steps to recover from scratch from the PC.
Download the image from https://developers.google.com/android/nexus/images
Boot into the bootloader and flash the files via fastboot.
Sent from my Galaxy Nexus using xda premium
Should have read through this thread first man.. check out this post
You can find the factory images here .. flash with fastboot
Thanks!
There seems to be 2 choices - Nakasi and 4.1
Do you know which I should use?
Yup its the one for Nakasi, 4.1 JRN84D. Once you are flashed you can take the update to 4.1.1.
So I was able to get back recovery using the Root Toolkit 1.1 app.
Then I was able to clear and reload the tweaked ROM and then the OC Kernel and I am BACK!!!
This was with way less pain.
Related
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.
hi im new to the whole nexus 7 scene just got it today and its also my first nexus device. came from a highly locked down dx2 then to htc and now im trying this. i used the nexus root toolkit v1.5.5 to unlock and root and flash custom recovery. but when i hold power down+volume down i get into the boot loader and i choose recovery then GOOGLE splash screen comes up and it does absolutly nothing while no usb chord plugged in. with usb chord it stays at the google splash screen for but a moment then just boots into android.
i tried the advance utilities and flash the cwm that way but same results. im still on 4.1.0 jrn84d. what am i doing wrong? i don't fully understand adb so if there is quite litteraly a step by step please give me a link or write it down if no such link exists. my last hdd that had adb all setup and ready crashed so its not setup and i was talking to someone who helped me get it going. all i know is i need to use command prompt but getting it into adb and then using it to push and get into cwm i have no clue.
i would love to make a nandroid and then install a kernal to gget the full power out of this thing. it is unlocked and rooted already.
They using ROM Manager app to install CWM and also boot into recovery. Will work for sure as long as you're rooted.
Sent from my SPH-L710 using xda app-developers app
dante32278 said:
They using ROM Manager app to install CWM and also boot into recovery. Will work for sure as long as you're rooted.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you follow the steps correctly, it should have a custom recovery installed. check if your rom is actually rooted.
EDIT: What the hell are you doing on 4.1.0? I thought factory stock was 4.1.1.
Use this:
http://forum.xda-developers.com/showthread.php?t=1809195
Get GooManager from the play store. It can download and install TWRP recovery which I prefer. GooManager will let you reboot into recovery too.
Sent from my Paranoid Nexus 7 using XDA Premium
cakessi said:
EDIT: What the hell are you doing on 4.1.0? I thought factory stock was 4.1.1.
Use this:
http://forum.xda-developers.com/showthread.php?t=1809195
Get GooManager from the play store. It can download and install TWRP recovery which I prefer. GooManager will let you reboot into recovery too.
Sent from my Paranoid Nexus 7 using XDA Premium
Click to expand...
Click to collapse
lol i dunno just came with it. its the 16gb version dunno why it came with 4.1.0 but it did. and when i installed rom manager i flashed cwm with that then choose to boot into recover that way and it worked. i am unlocked and rooted and now have a nandroid. have yet to try going to cwm with power+volume down being pressed i will give it a shot later on and make another nandroid before i accept the update im being propted for.
ty guys for the help.
There was a bug that required the N7 to be connected to a PC-USB connection before it would work. They didn't fix the bug until 4.1.2.
Your best bet, if you can boot into Android, is to download a Reboot-to-Recovery app or use CWM or GooManager to reset into recovery. If you are boot looping, throw a USB connection into the mix when trying to do it. I believe it is VolDown+Power+USB connection. Drivers may also be a factor.
Thanks for the reply. I finally updated it. Had to do three updates though. First to 4.1.1 then to 4.1.2 and then to 4.2. I have a nandroid at 4.1.0 so if I need to do anything I'm just going back. I used ota root keeper and the cwm that's from rom manager allows you to choose to protect your custom recovery as well as root. But I don't know if that was working in tandem with ota root keeper since I made sure to back it up first before I did anything.
Sent from my Nexus 7 using xda app-developers app
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
The robot lying on it's back is the stock recovery. You need to flash CWM/TWRP before you can do a Nandroid
itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
Do yourself a favour and learn how to use ADB instead of toolkits that do more harm than good if used by inexperienced users and you`ll learn to do it the right way.
Look here http://forum.xda-developers.com/showthread.php?t=1474956 for how to.
Youtube tutorial link http://www.youtube.com/watch?v=ZY4KSrgi-rE.
itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
If you have Rom Manager Installed and are rooted you should be able to install CWM thru it.
don't have flash recovery on rom manager
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?
itayze said:
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?
Click to expand...
Click to collapse
according to ROM Manager you already have CWM installed and its up to date. Have you tried booting into recovery using ROM Manager?
When I press reboot to recovery directly from rom manager it works...
I'm just affraid that in case that I brick or mess up something I won't be able to get to stock recovery mode.
volume down + power button = bootloader (android on his back) also called fastboot mode
use volume buttons to scroll to recovery then press power button to select it
you should then be in CWM recovery if its installed correctly.
If you are using a custom recovery your stock recovery is gone. You would have to use fastboot to flash the stock recovery image back onto the phone. Its rather simple to do as is flashing the stock image file back onto the phone.
that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Edit: I posted before you edited your comment.
even though I don't know adb, should I learn and follow this guide?
http://www.androidauthority.com/nexus-4-clockworkmod-recovery-134114
itayze said:
that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Click to expand...
Click to collapse
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312
kzoodroid said:
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium
El Daddy said:
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I call it a bug because its an annoying feature. There are a number of threads no how to remove it but using a toolkit to do it is just as easy.
thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !
itayze said:
thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !
Click to expand...
Click to collapse
Glad you got it working. I would still learn adb and fastboot. Though I too use the tool kit every now and then out of convenience.
I flashed TWRP to make backups and am finding I want to revert to stock recovery for whenever the next OTA is pushed. I'm on stock 4.2.2. Is there a repository to flash the stock recovery specific to the version of android I'm on or other way to backup/re-flash stock android prior to installing custom recovery?
ravenofdoom said:
I flashed TWRP to make backups and am finding I want to revert to stock recovery for whenever the next OTA is pushed. I'm on stock 4.2.2. Is there a repository to flash the stock recovery specific to the version of android I'm on or other way to backup/re-flash stock android prior to installing custom recovery?
Click to expand...
Click to collapse
The stock Android recovery cannot make entire system (NANDROID) backups like TWRP or CWMR can. If your looking to re-install stock Android 4.2.2 for the Nexus 10 you can download and flash the Nexus 10 factory image from here (I would recommend taking a look at this great guide if your are unfamiliar with how to flash factory images). If you just want to reflash the Nexus 10 stock recovery you can download it from here, boot into fastboot mode and then flash it with the following command:
Code:
fastboot flash recovery path/to/recovery-stock-manta.img
After it completes you can reboot into recovery mode and you should now have the stock Nexus 10 recovery image installed. For flashing the stock recovery you should try and match it to the Android version so if your on Android 4.2.2 try and flash the recovery.img that was pulled from the Android 4.2.2 factory image. However usually you can get away with flashing 4.2 or 4.2.1 version of the stock recovery.img as it is unlikely that anything major changed with the stock recovery image in those small incremental Android updates.
Is there a repo or other way to make a backup of stock recovery before flashing custom (TWRP/CWMR). If I'm on the go and want to interchange between custom recovery and previous stock recovery without the aid of a computer nearby, how would I do that? Is there an app that can save/snapshot my current stock recovery before flashing custom recovery (and then can later let me re-flash that saved recovery)?
Flashing stock recovery wont make me lose any data will it? because 4.3 was released for s4 google edition so im sure nexus 10 is close and i want to be ready.
abdel12345 said:
Flashing stock recovery wont make me lose any data will it? because 4.3 was released for s4 google edition so im sure nexus 10 is close and i want to be ready.
Click to expand...
Click to collapse
Correct flashing stock recovery won't make you loose any data. But as always when your flashing anything and if you have even the slightest hesitation backup any data you wouldn't want to loose.
Sent from my SCH-I535 using xda premium
Alright thanks man. I already used my 8 for today but ill thank you tomorrow and ill back up my apps with titanium backup
OK what is the command to use to flash because the one from the previous page didn't work it said something about not finding it or something are there any drivers that need to be installed or something I'm missing? I connected it to my CPU and turned it on while holding power and volume and it went menu where you see tablet info? Any help please
Sent from my Xperia Play (r800x)
ravenofdoom said:
Is there a repo or other way to make a backup of stock recovery before flashing custom (TWRP/CWMR). If I'm on the go and want to interchange between custom recovery and previous stock recovery without the aid of a computer nearby, how would I do that? Is there an app that can save/snapshot my current stock recovery before flashing custom recovery (and then can later let me re-flash that saved recovery)?
Click to expand...
Click to collapse
Don't know if you still need this info, but you can use flash_image to flash recoveries without having to connect to a PC. So if you save the recovery image files, you can switch easily. Have a look here:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I haven't done this on my N10, but I've used the method several times on my HTC Vivid phone.
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
Don't know if you still need this info, but you can use flash_image to flash recoveries without having to connect to a PC. So if you save the recovery image files, you can switch easily. Have a look here:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I haven't done this on my N10, but I've used the method several times on my HTC Vivid phone.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That actually helped me out with my problem thanks because I couldn't get it to flash from cpu
Sent from my Xperia Play (r800x)
abdel12345 said:
That actually helped me out with my problem thanks because I couldn't get it to flash from cpu
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Cool. :thumbup:
Sent from my Nexus 10 using Tapatalk HD
@bruce7373 it didnt work it just tells me flash_image not found when i put in the command and i checked and its there on the sd card
abdel12345 said:
@bruce7373 it didnt work it just tells me flash_image not found when i put in the command and i checked and its there on the sd card
Click to expand...
Click to collapse
The IMG file is not found or flash_image itself isn't there? If you don't have flash_image, you can download it (I think there's a link on that page I referenced, or just Google it). If the former, you need to first navigate to the folder flash_image is in (/system/bin with the ROM I have on my N10), then run the command, making sure the IMG file is in the root of /sdcard.
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
The IMG file is not found or flash_image itself isn't there? If you don't have flash_image, you can download it (I think there's a link on that page I referenced, or just Google it). If the former, you need to first navigate to the folder flash_image is in (/system/bin with the ROM I have on my N10), then run the command, making sure the IMG file is in the root of /sdcard.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
OK I'll try yhat
Sent from my Xperia Play (r800x)
I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.
OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.