I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
wrong advice, my mistake... thanks for the reminding simms22.
But I wanna stay rooted
Sent from my Nexus 4 using xda app-developers app
You don't have to unroot. Just download and flash TWRP 2.6.3.2. On that build, they fixed the issues of 4.4 ROMS incorrectly flashing. Using it myself with no problems. Its in Original Android Development if I'm not mistaken
Flashing 4.4 Factory Image issues
Currently on my Nexus 4.
Android 4.3 Unlocked and Rooted
Kernel Version: 3.4.0-perf-gf43c3d9
Build: JWR66Y
Baseband: M9614A-CEFWMAZM-2.0.1700.84
Using ClockWorkMod Recovery v6.0.4.3, when trying to flash the 4.4 factory image .zip file on the SD Card I keep getting an "Installation Aborted" error after "Installing update..." step and the red Triangle on the android figure.
When attempting to sideload using stock recovery, getting a "Signature Verification Failed"
Any Suggestions? Thanks
darkfire2040 said:
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you haven't already tried it, under Mount uncheck system, that solved the problem for me.
Yeah I wanna stay in twrp so I will try flashing the latest. The error I'm getting is. Error while trying to update binarys
Sent from my Nexus 4 using xda app-developers app
will_chrome said:
you've got to unroot and back to stock rwcovery 1st if I'm not mistake. the guide to flash stock rom can be found in http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
wtf??? never ever give advice on android ever again!
op, all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
simms22 said:
all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
Click to expand...
Click to collapse
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
ph37rd said:
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
simms22 said:
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
Click to expand...
Click to collapse
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
ph37rd said:
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
simms22 said:
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
Click to expand...
Click to collapse
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
ph37rd said:
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
na. really the only 100% working fix is to delete the recovery, then reflash.
simms22 said:
na. really the only 100% working fix is to delete the recovery, then reflash.
Click to expand...
Click to collapse
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
ph37rd said:
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
simms22 said:
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
Click to expand...
Click to collapse
OK that confuses me. If using fastboot to place a new boot loader, radio, recovery and ROM are onto the phone and I have to 'fastboot flash recovery recovery.img' to replace the stock recovery that doesn't wipe out the stock recovery? Fabulous sentence structure.
Sent from my Nexus 4 using Tapatalk
Related
Hi
I am on stock 4.1.2 unlocked and rooted and I was on TWRP recovery then I changed to CWM 6.0.1.0 because there are some problems in it an yesterday I flash the new TWRP 2.3.1.0 with goo manager and rebooted to TWRP and I did a backup of the rom and rebooted the tablet and I trasfer the paranoidandroid rom to my SD card and open the goo manager and select reboot recovery , it didn't reboot to recovery i I don't know why I did it a couple of times the tablet just rebooted normally like there are no recovery and I go to flash the CWM 6.0.1.0 and it is the same the phone rebooted normally it didn't rebooted to recovery
Somebody help me please
Sent from my Nexus 7 using xda app-developers app
Anybody
Sent from my Nexus 7 using xda app-developers app
You should be able to use fastboot to flash a recovery img or use a toolkit.
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
You should be able to use fastboot to flash a recovery img or use a toolkit.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I did but it is the same it is reboot normally
Sent from my Nexus 7 using xda app-developers app
sharjackmission said:
I did but it is the same it is reboot normally
Click to expand...
Click to collapse
Did you remember to change the recovery-from-boot.p file after you did the 4.1.2 update?
iElvis said:
Did you remember to change the recovery-from-boot.p file after you did the 4.1.2 update?
Click to expand...
Click to collapse
Yes after I update to 4.1.2 OTA those problems came
And now I managed to reboot to CWM by wug's toolkit but I can't enter to recovery from the bootloader
Sent from my Nexus 7 using xda app-developers app
sharjackmission said:
Yes after I update to 4.1.2 OTA those problems came
And now I managed to reboot to CWM by wug's toolkit but I can't enter to recovery from the bootloader
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
This is a problem many Nexus 7 owners are experiencing since the 4.1.2 update, whether by OTA or flashed from sd card. There apparently is an issue with the bootloader (version 3.43). One solution that I have seen on t his forum and on another is to flash the last version of bootloader (3.31 I think). I have tried every conceivable method to get into either stock recovery or custom recovery to no avail...flash, 2 different toolkits, ROM Manager, TWRP...you name it, I've tried it to no avail. I have not tried to flash back to the old bootloader though...just doesn't sound like a good idea...although I have not heard of problems being encountered by those who have flashed the old bootloader...yet. There are a couple thread in this sub forum on the subject if you want to read the 100 different ways users have tried to get a recovery.
jpcalhoun said:
This is a problem many Nexus 7 owners are experiencing since the 4.1.2 update, whether by OTA or flashed from sd card. There apparently is an issue with the bootloader (version 3.43). One solution that I have seen on t his forum and on another is to flash the last version of bootloader (3.31 I think). I have tried every conceivable method to get into either stock recovery or custom recovery to no avail...flash, 2 different toolkits, ROM Manager, TWRP...you name it, I've tried it to no avail. I have not tried to flash back to the old bootloader though...just doesn't sound like a good idea...although I have not heard of problems being encountered by those who have flashed the old bootloader...yet. There are a couple thread in this sub forum on the subject if you want to read the 100 different ways users have tried to get a recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=32918876
I found this and I didn't tried it because it may not work see for your self
I just wondering when the android 4.2 will be released to solve all those problems
Sent from my Nexus 7 using xda app-developers app
I think my bootloader is 3.41 and I have no issues but I flashed the factory image from Google because my touchscreen didn't respond after the 4.1.2 OTA.
Try flash the bootloader and see if it works and if not then flash the factory image.
Just note that if you use the script/batch file to flash it all automagically it will wipe your SD so flash each image separately and don't flash userdata.img
flashing factory fixes any software problem, its the best thing about owning a nexus.
Sent from my Nexus 7 using xda premium
found it
if you are on the latest bootloader vesion
reboot to booloader
fastboot erase cache
fastboot flash recovery nameofrecovery.img
fastboot erase cache
fastboot reboot
thank you all
Hi all,
I'm freaking out here. I was trying to install a kernel on my N4 using the Toolkit and somehow it said it was done successfully but then my phone got stuck on the Google screen and was never able to start up again.
I do have a Nandroid back up but unfortunately it's on my computer and not on my phone.
I tried using the toolkit AND adb to push the files to my phone but I get the same message: "failed to copy to sdcard: No such file or directory".
I'm completely stuck now and am panicking. Somebody please help!
And this is why we don't use toolkits.
Read up on how to use fastboot and how to boot into fastboot.
Then read up on where to find stock images and how to flash them in fastboot. Then do it.
Sent from my Nexus 4 using Tapatalk 2
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Might also be helpful if you specified which kernel you flashed. As long as you didn't flash a kernel for a different device (e.g. nexus 7) you can definitely recover. To reiterate what others have mentioned, fastboot is your friend. There are numerous tutorials on his to install and use it. Check the stickies.
Crisisx1 said:
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah I can get into fast boot and even into CWM. I tried factory resetting in CWM but it still gets stuck on the Google screen.
The reason I used the toolkit and not CWM to flash the kernel is because CWM kept failing to flash the kernel, giving me some error and "(bad)" message. It is the kernel to improve Nexus 4 sensitivity directly from another thread.
Can someone please provide me with specific links or detailed instructions?
Crisisx1 said:
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
My main problem is I need to get my Nandroid backup onto my phone. For some reason, because it's stuck on the Google screen, it's not able to write to the sdcard. Can someone please help me get my files from my computer to my phone?
Flash stock first.
Follow Efrants guides.
http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda premium
Unjustable said:
Flash stock first.
Follow Efrants guides.
http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for your help. I've successfully follows the instructions and got back to Android 4.2.2.
I still want to restore my previous Nandroid though. Although I have placed it in the Clockworkmod backup folder, it's not being seen by CWM recovery. I tried backing up a new nandroid just to test and CWM sees the one it backs up.
Anyone know how I can get CWM to recognize the Nandroid which was done through the toolkit?
Thanks!
darkwolf1789 said:
Yeah I can get into fast boot and even into CWM. I tried factory resetting in CWM but it still gets stuck on the Google screen.
The reason I used the toolkit and not CWM to flash the kernel is because CWM kept failing to flash the kernel, giving me some error and "(bad)" message. It is the kernel to improve Nexus 4 sensitivity directly from another thread.
Can someone please provide me with specific links or detailed instructions?
Click to expand...
Click to collapse
If the kernel wasn't installing in the first place you probably shouldn't of flashed it via toolkit
Sent from my Nexus 4 using xda app-developers app
Crisisx1 said:
If the kernel wasn't installing in the first place you probably shouldn't of flashed it via toolkit
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah I realize that now. But any idea how to get CWM to recognize my Nandroid that I did with the toolkit? Anyone?
joshnichols189 said:
And this is why we don't use toolkits.
Read up on how to use fastboot and how to boot into fastboot.
Then read up on where to find stock images and how to flash them in fastboot. Then do it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
There isn't really anything wrong with a toolkit for certain things, I just think it's a bit strange he tried to use it for something as trivial as this.
skezza said:
There isn't really anything wrong with a toolkit for certain things, I just think it's a bit strange he tried to use it for something as trivial as this.
Click to expand...
Click to collapse
Ok well to solve the problem I did download the stock images and flash them according to Effrants guide:
http://forum.xda-developers.com/show...php?p=34552123
Then the reason that CWM wasn't recognizing my Nandroids was because I had them in /sdcard/clockworkmod/backups, but they should be in /data/media/clockworkmod/backup.
I recovered everything and I'm back! Thanks for your help everyone.
I flashed the clockworkmod touch zip from my recovery.
It didn't give me the touch recovery, I thought "whatever" and booted back into my rom.
It wouldn't boot.
I went back into recovery and flashed PA rom and gapps.
They weren't booting, I decided to give them a few minutes.
It finally booted.
It no longer connects to wifi or tmobile.
I can't transfer files over usb.
Wugfresh's toolkit couldnt return it to stock.
I thought the recovery might have gotten messed up when I tried to flash CWM touch, so I flashed TWRP from Wugfresh's toolkit.
I used adb sideload to flash a stock rooted rom.
It still took forever to boot, and is still not connecting to wifi/network.
TL;DR I can boot into fastboot and recovery and even the rom but I have no network connection... help guys :'(
It says BASEBAND VERSION - N/A... could that be the problem? If so, how do I fix it?
This is why we don't use toolkits. Return to stock using ADB and do it again...
Sent from my Nexus 4 using xda premium
When I try to fastboot flash the stock image it says "does not contain recovery.sig" "does not contain boot.sig" and only updates the bootloader.
Did you dl the image right from Google?
Sent from my Nexus 4 using xda premium
ethan.r.besbris said:
Did you dl the image right from Google?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yup.. this one https://developers.google.com/android/nexus/images#occam
So I just flashed the radio by itself and its working fine now thanks for your help man.
No problem. Glad you're up and working.
Sent from my Nexus 4 using xda premium
*****
Does anyone know where I can get a flashable OTA file that will keep root for the Wifi OG Nexus 7? I have seen it posted for the Nexus 4 and new Nexus 7, but cannot find it anywhere for Grouper.
VAVA Mk2 said:
Does anyone know where I can get a flashable OTA file that will keep root for the Wifi OG Nexus 7? I have seen it posted for the Nexus 4 and new Nexus 7, but cannot find it anywhere for Grouper.
Click to expand...
Click to collapse
There is a flashable ota at the link below. You may need to flash superuser 1.51 after to get root back.
http://forum.xda-developers.com/showthread.php?t=1745781
Sent from my GT-I9505 using xda app-developers app
gsmyth said:
There is a flashable ota at the link below. You may need to flash superuser 1.51 after to get root back.
http://forum.xda-developers.com/showthread.php?t=1745781
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
OK I tried that but I got a Status 7 error message and it aborted install. I have everything stock that I can think of. No custom kernel. No nothing. Any suggestions other than flashing back to stock completely via Wug's toolkit then doing the OTA through the tablet itself and then restoring everything with Titanium Backup?
VAVA Mk2 said:
OK I tried that but I got a Status 7 error message and it aborted install. I have everything stock that I can think of. No custom kernel. No nothing. Any suggestions other than flashing back to stock completely via Wug's toolkit then doing the OTA through the tablet itself and then restoring everything with Titanium Backup?
Click to expand...
Click to collapse
If you check that thread I linked to above, there a few people with the status 7 error and a few different fixes, worth a try before wiping anything, hope it helps.
Sent from my GT-I9505 using xda app-developers app
gsmyth said:
If you check that thread I linked to above, there a few people with the status 7 error and a few different fixes, worth a try before wiping anything, hope it helps.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks I appreciate it!
VAVA Mk2 said:
OK I tried that but I got a Status 7 error message and it aborted install. I have everything stock that I can think of. No custom kernel. No nothing. Any suggestions other than flashing back to stock completely via Wug's toolkit then doing the OTA through the tablet itself and then restoring everything with Titanium Backup?
Click to expand...
Click to collapse
You don't need to flash the stock image and lose your data, but even if you are on stock 4.3 you still need two things: stock recovery (if you don't already have it installed) AND you need to unroot! Being rooted will throw the Status 7 error.
Here's what I did:
First flash the stock recovery for JWR66V in fastboot.
Then use the "Full unroot" option inside SuperSU.
Apply the JWR66Y update using ADB sideload.
Then reinstall TWRP and install UPDATE-SuperSU-v1.51.zip using TWRP.
After rebooting you may be surprised to see that the SuperSU app needs to be installed again (seems to be a quirk a lot of us are having). Just head over to Google play and after that all should be good.
Sent from my Nexus 7 using xda app-developers app
CatThief said:
You don't need to flash the stock image and lose your data, but even if you are on stock 4.3 you still need two things: stock recovery (if you don't already have it installed) AND you need to unroot! Being rooted will throw the Status 7 error.
Here's what I did:
First flash the stock recovery for JWR66V in fastboot.
Then use the "Full unroot" option inside SuperSU.
Apply the JWR66Y update using ADB sideload.
Then reinstall TWRP and install UPDATE-SuperSU-v1.51.zip using TWRP.
After rebooting you may be surprised to see that the SuperSU app needs to be installed again (seems to be a quirk a lot of us are having). Just head over to Google play and after that all should be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, I'm looking forward to doing this step since I really want to get that OTA installed in my device. Mine is on stock ROM, rooted via wugfresh toolkit. My concern is, after doing this step, will I lose all data? Also could you please explain how to do the first step- "First flash the stock recovery for JWR66V in fastboot."? I'm still a bit new to all these things, so please bare with me.
Thanks!
http://forum.xda-developers.com/showthread.php?t=1745781&page=53
Check out this thread. I flashed the Grouper.zip file, which is the OTA modified by commenting out the validation check that results in the Status 7 error. I copied it to /sdcard along with the Supersu 1.51 zip. The ota flashed perfectly using TWRP recovery. After booting and going back into TWRP, I flashed the supersu1.51 and regained root. You do not need to unroot or flash stock recovery to get this update. No data loss. I'm stock rom & kernel, rooted with TWRP recovery.
choybel said:
Hi, I'm looking forward to doing this step since I really want to get that OTA installed in my device. Mine is on stock ROM, rooted via wugfresh toolkit. My concern is, after doing this step, will I lose all data? Also could you please explain how to do the first step- "First flash the stock recovery for JWR66V in fastboot."? I'm still a bit new to all these things, so please bare with me.
Thanks!
Click to expand...
Click to collapse
You won't lose data if you repeat the steps I took. However since you are asking how to flash a recovery in fastboot I would seriously be careful and do a bit of homework on how fastboot works. All the instructions you'll ever need can be found by searching xda. It really isn't as daunting as it sounds but you definitely need to understand how it works before trying it.
Or you could try the link that Groid posted if you aren't concerned about skipping the validation check. The process is definitely is simpler if you're "new to all these things".
I'm not opposed to using WugFresh's toolkit, he's a brilliant developer, but it's never a bad idea to learn about what happens in the background and see it with your own eyes.
Sent from my rooted GSM Galaxy Nexus
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.