Database Develop

Problem rooting - Failed: Too many links

I'm having a problem rooting my Nexus One (I have also read the newbie FAQ and searched the forum to no avail) - I have followed the instructions listed on the androidandme site.
When I try to unlock using fastboot I get this returned:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFOErasing userdata...
FAILED (status read failed (Too many links))
When I start the phone in fastboot mode it now says *** UNLOCKED *** at the top of the screen. I then flashed Amon-Ra's recovery image, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-
RA-nexus-v1.6.2.img
sending 'recovery' (3954 KB)... OKAY
writing 'recovery'... OKAY
I assumed everything was going to be fine despite the issues unlocking. On trying to boot into recovery mode all I get is a screen with an exclamation mark and the android robot.
On turning the phone on as usual it seems that I can not run "Root required" apps such as the N1 torch.
I have tried running the OEM unlock command again but it seems to think that it has worked, as below:
C:\....\Desktop\android-sdk-windows\tools>fastboot oem unlock
... INFODevice was already unlocked!
OKAY
It would seem from the newbie guide that I still need to flash the recovery image but that seems to be going fine. I can't see that I've messed up so far so is there some way to "unroot" my phone or go through the OEM unlock process again?
Thanks.

You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.

jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
I tried this, but still don't have root permissions - any thoughts?
I have read and searched and read some more and searched some more, and now just need some help...
Thanks in advance.

2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.

jongie123 said:
2 options, either install superboot from the Modaco's site to gain su, or flash Cyanogen's google adon.
Click to expand...
Click to collapse
I suggest One thing. Pay 15.47 american Usd, at Online Kitchen for Modaco, Viola, Your done, always rooted.. Always Su'd up..
The Bootloader is simple on a windows machine, and so is root.. On Modaco's site there is a whole tutorial on this.. Plus search the threads, a whole ish load too..
i"d pay the 15.47.. Just Nike it, Just do it.. It's so much easier.. Just click-click, bake, download, flash, done..
Go..Go..!

jongie123 said:
You already unlock your bootloader, now put your rom of choice in the root of your sdcard, now flash again
AmonRa recovery, but this time don't reboot, after you you flash the recovery, flash the rom, and reboot.Now you should have su permition. Remember to nandroid backup before flashing the rom.
Click to expand...
Click to collapse
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?

If you just need root, get 'superboot'. It needs to be flashed to the "boot" partition (after unlocking the bootloader).
What it does is copy the root files to the data ROM and sets up permissions the first time the phone is booted (runs some sort of script I guess).
Link to superboot (free), make sure you get the right version:
http://android.modaco.com/content/g...erd79-epe54b-superboot-rooting-the-nexus-one/

look up "get root back".... Try these commands via ADB:
adb remount
adb shell chmod 6755 /system/xbin/su
....This should "fix_permision" and get you root back, IF you ever had it....

papermonk said:
Thanks, I managed to flash the custom ROM this way, however I can't boot into recovery mode unless I boot from fastboot. Is this to be expected or should I be able to just turn on the phone, unconnected to the computer, while holding volume-down and boot into recovery mode?
Click to expand...
Click to collapse
Using adb you can issue "adb reboot recovery" and wind up in recovery mode. You can also hold down the power button and trackball (connected or disconnected from the computer) and enter fastboot. From there, select bootloader and then recovery.

I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.

sadhuKashmir said:
I am trying to unlock g1 but it fails showing "too many links". It does not do anything else.
Click to expand...
Click to collapse
If you are rooting a G1, correct me if I am wrong, but couldn't you just use one of the one click root methods?
I thought all of the patches denying one click root were contained in official FW's of GB and the G1 did not get it.

[Q] CM5 install prob- not booting into custom recovery?!

Hi,
I've owned and ROM'd two Android phones, but not a G1 and wanted to help out a friend to get her stock 1.6 G1 to CM5. We ran into problems which led me to not want to continue before they are sorted out. I looked for answers to this but couldn't find any, so please don't flame me if I overlooked any. I tried to go by the instructions in the CM wiki.
This is what we did:
- We installed ClockWorkMod Recovery through the ROM Manager app
- We rebooted into that recovery and via adb flashed AmonRA recovery
- we rebooted into the AmonRA recovery which worked (I *think* just regularly holding Home while powering on)
- we flashed the appropriate radio update for her US TMo G1
- the documentation said "phone will reboot during update". I think it did, but it seemed stuck on "formatting cache" in recovery.
- when holding Home on reboot after that, it did from there on NOT reboot into the custom recovery
- instead, it rebooted into what looks like "bootloader" mode on my Moto Milestone, a screen with a phone and an exclamation point. We could get into stock recovery with Alt-L, but I don't think that is what we wanted.
At this point, it seemed to not reliably boot into custom recovery, so I didn't want to continue the process. I assume I could have gone down the same of flashing a custom recovery, but I wasn't sure what would happen with/after installation of the DangerSPL if booting into recovery wouldn't work.
So - is the "booting into bootloader instead of recovery" a known issue? Am I too much of a noob on the G1 and did totally miss something? Could or should we proceed to the DangerSPL / CM5 installation with this going on?
Any help would be much appreciated!
W0nk0

Flashing a new recovery from CM5 or CM6 is not working well. Try flashing the recovery image / radio image / ... from fastboot and you should be fine.
Edit: I did not read well the first time. Now I notice, that you are still on stock SPL, sorry. But re-reading well I've got a question: Are you sure you flashed already successfully a new recovery? For me it seems you are still on a plain stock G1.
Sent from my Htcclay's Superfly G1 using XDA App

Thanks a lot for your help!
We _were_ on a custom recovery twice, after flashing it from ROM manager (Clockworkmod then) and on the AmonRA recovery after that. As the recoveries clearly had non-stock things like nandroid I'm quite positive.
The problem seems to be that they didn't "stick" - we flashed the radio ROM upgrade from Amonra recovery, but after a reboot with Home pressed landed in the exclamation point screen again (which seems to indicate stock recovery as you can get to that with Alt-L from there).
If fastboot is indeed the way to go, where do I get the drivers for the windows/pc side of it? The noob guide I found had no help there :/.
Thanks again,
W0nk0
Sent from my Dell Streak using Tapatalk

Few things;
1) if you have the OEM system image, then, indeed, the recovery will be overwritten by the OEM recovery image upon reboot into the system.
2) You say that you've written a RADIO image.... ***WHAT*** radio image did you write? You should have written a radio with a version number that starts with a "2".
3) Have you written a new SPL? The SPL you should write is 1.33.2003. DO NOT install deathSPL, no matter how many RETARDS suggest it. There is ABSOLUTELY NO USE in it. 1.33.2003 is SAFE to install (unlike 1.33.2005), and the ONLY benefit of 1.33.2005 has been GREATLY EXCEEDED, making that "benefit" entirely pointless.
Note that with the stock SPL (0.95.0000), there IS NO FASTBOOT. 1.33.2003 has a very strong fastboot capable of writing ALL partitions, including the radio image. Fastboot is the safest way to write the radio and SPL, but prior to installing an SPL with a strong fastboot mode, obviously you can't use this feature.
Steps:
1) Reinstall custom recovery,
2) reboot into recovery and write 1.33.2003 SPL.
3) DO NOT let it boot into regular system prior to installing 1.33.2003 SPL, or it will overwrite that custom recovery.
4) After installing the good SPL, it would still overwrite the custom recovery by booting into the regular system, but by this time, you will have FASTBOOT, so it doesn't matter.
5) Now do what you want... but once you have a 2.x radio and 1.33.2003, do NOT write any other radio or SPL, and for F SAKES DO NOT RUN ANY NBH FILES EVER NO MATTER WHAT!!!

[Q] Is Fastboot the answer to my woes?

I want to flash a new radio and kernel to my G1 that is running CM6. My signal is atrocious and I get a few random oddities each day.
I have tried the recovery flash for the radio at least 6 times now in various ways following various guides and every time I do it it crashes my phone and I end up flashing the image, rooting, etc, to get back to CM6. it takes me over an hour to get back to normal and it just plain sucks!
So my question is..... Can I use fastboot flash to flash the image files for the radio and the kernel without being on the special Hboot 1.33.0013d and such?
I was planning to use the instructions from the ezterry kernel page and just want to check that I wont bork up my phone. I seem to recall that the fastboot flash bypasses all the need for FR-remove and such but want a second opinion before I take the dive this way.

Not trying to drive you away from CM 6, but have you tested other ROM to see if it has the same problem or similar.
I personally myself could not get CM6 to work properly on my G1 back when I was trying to use it.

I couldn't get the radio to recovery flash even on the stock ROM after rooting.
I guess I could try a different ROM.
I just now have proven to myself that i cant flash the EzTerry kernel from Rom Manager and clockwork recovery as I am in the midst of yet another image flash, re-root, and such after it wouldn't go past the reboot screen afterwards
This phone is just an extra toy but I am determined to figure it out.
I suppose I will just try the radio.img flash from fastboot tonight when I get home.
As long as I dont brick it I can always start over from scratch.

so I copied the image I want to flash onto the root of my sd card
did the camera+power boot
pressed the back key and I am at the screen with the red fastboot usb box
I plug into the computer (adb already installed and working fine) and go to the command prompt and type
fastboot flash hboot hboot-1.33.0013d.img
the screen says error: cannot load 'hboot-1.33.0013d.img'
Did I put the image file in the wrong place?
Edit: I put it in the root of the computers c: drive and typed
fastboot flash hboot c:\hboot-1.33.0013d.img
seems to have worked.

FireRaider said:
so I copied the image I want to flash onto the root of my sd card
did the camera+power boot
pressed the back key and I am at the screen with the red fastboot usb box
I plug into the computer (adb already installed and working fine) and go to the command prompt and type
fastboot flash hboot hboot-1.33.0013d.img
the screen says error: cannot load 'hboot-1.33.0013d.img'
Did I put the image file in the wrong place?
Edit: I put it in the root of the computers c: drive and typed
fastboot flash hboot c:\hboot-1.33.0013d.img
seems to have worked.
Click to expand...
Click to collapse
do the same thing with the radio and recovery

maximo360 said:
do the same thing with the radio and recovery
Click to expand...
Click to collapse
I got the recoveryand the hboot to flash but damned if I can get any radio to flash.
I get
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
this is with both version of the radio downloaded from the links in the EzTerry thread
What in the world am I doing wrong that I cannot flash a new radio?

installed the spoofSPL... didnt help
edit: Started over again from scratch, rooted, flashed RA recovery, dangerSPL, then fastbooted and managed to install the hboot and the new radio. I guess CM6 hates the newer radios.
edit: Pretty sure CM6 does hate the radio because now its hung up on the install screen.
off to do more research.

People ... you should read before flashing around.
Ok, let me try to help.
1) As long as you have a fastboot enabled SPL, there is no need to 're-root'. Boot into hboot and flash the things you want.
2) Going to 1.33.0013d you *lose* most of your fastboot capabilities, e.g. flashing a new SPL/radio/recovery is no longer working. The only chance is to flash a signed nbh-file (e.g. fully signed rom)
I suggest you to read Terry' thread carefully (a link is in my signature) and then to retry ...
Btw: If you have installed the "new" radio/spl combo you need an adopted kernel, too, otherwise you will get bootloops.
Sent from my Gingerbread on Dream using XDA App

AndDiSa said:
People ... you should read before flashing around.
Ok, let me try to help.
1) As long as you have a fastboot enabled SPL, there is no need to 're-root'. Boot into hboot and flash the things you want.
2) Going to 1.33.0013d you *lose* most of your fastboot capabilities, e.g. flashing a new SPL/radio/recovery is no longer working. The only chance is to flash a signed nbh-file (e.g. fully signed rom)
I suggest you to read Terry' thread carefully (a link is in my signature) and then to retry ...
Btw: If you have installed the "new" radio/spl combo you need an adopted kernel, too, otherwise you will get bootloops.
Sent from my Gingerbread on Dream using XDA App
Click to expand...
Click to collapse
I managed to get everything work and am running CM6.1+2708 and 0013d with the .27 radio.
Why do we go to the 0013d if it screws up the fastboot? I notice in your signature you are running it also?
And say I want to flash a different rom now? I can only do it from RA recovery, Correct?
But as it stands now I ought to be able to experiment around with the other radio and other roms using recovery without any more issues? Or do they need to have certain parameters?

Once rooted, (to my knowledge) you do not required to re-root it again.
You can use RA Recovery to flash other ROMs with out having to re-root. (as to what I was told) And I recommend RA Recovery instead of ROM Manager/ClockMod Recovery (bad experience with it personnaly).
So as long as the ROM that you want to try is compatible with your current SPL/radio. You should be fine.

[Q] lost root after 2.3.6 update

hi there every one i updated my nexus one to 2.3.6 (GRK39F) from stock 2.3.4 (GRJ22) sorry but i did not read the post for to upgrade and keep root before upgrading to 2.3.6 and now i am suffering and thought it is not a good idea to post a question there so posting here
my problem is when i upgraded 2.3.6 i was rooted and had clockworkmod recovery image and i had a backup from rom manager as well but before upgrade i wiped the partition and cache and after upgrade i dont have SUPER USER permission nor the clockworkmod recovery tried to flash su.zip from sd card but no luck please can anyone help me get my root back pleaseeeee i need help ....

You'll have to passimg back to an earlier version of Froyo, root, restore your backup, and then flash the update and su zip...

danger-rat said:
You'll have to passimg back to an earlier version of Froyo, root, restore your backup, and then flash the update and su zip...
Click to expand...
Click to collapse
Thankyou very much danger-rat really appriciate your help but today was a bit lucky day for me
I tried to flash a recovery image through ADB and then it went well and then flashed the su.zip from sdcard that gave me superuser permission again thanks again for your help
@0mpranav

No need to flash the system partition, no need to use ADB, just flash Superboot:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/

If your bootloader is unlocked all you have to do is reboot into fastboot mode. Flash a custom recovery such as RA or CWM, reboot directly into revovery and flash su.zip or whatever flash zip you used to root your device before. Reboot and you are rooted once again.
The following thread has a step by step how to do it. It's fast and easy.
http://forum.xda-developers.com/showthread.php?t=1019759

jboxer said:
If your bootloader is unlocked all you have to do is reboot into fastboot mode. Flash a custom recovery such as RA or CWM, reboot directly into revovery and flash su.zip or whatever flash zip you used to root your device before. Reboot and you are rooted once again.
The following thread has a step by step how to do it. It's fast and easy.
http://forum.xda-developers.com/showthread.php?t=1019759
Click to expand...
Click to collapse
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.

GldRush98 said:
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
Click to expand...
Click to collapse
I have purchased two second hand Nexus Ones. The first thing I did after receiving them and charging the battery was to reboot into fastboot mode and issue "fastboot oem unlock" command. Since they were purchased second hadn I didn't thing I had a warranty anyway so unlocking the bootloader seemed to be a non brainer.

GldRush98 said:
Yup. This is the way every one should be doing it. It's sort of the whole point of the Nexus One. It has an unlockable bootloader.
Click to expand...
Click to collapse
Will any version of su.zip, and fastbook.zip work? What about recovery-RA-passion-v2.2.1.img? or should we be using a different version?
If we should be using different versions of those, could you link to where we could get them?
I've had my Nexus one half-rooted since 2.3 came out, and I haven't been able to root it back.

why mess with 2.3.6 just use oxygen 2.3.7...

kuljit55 said:
why mess with 2.3.6 just use oxygen 2.3.7...
Click to expand...
Click to collapse
I'm sorry I have no idea what that is. I don't even know if its helpful at all. Again, I don't even have root, or a custom recovery. Presently, I have an unlocked bootloader, ADB on my PC, and a half-rooted nexus one from before 2.3.
I have absolutely no idea how to do anything presently, and when someone tells me that trying to root on 2.3.6 is futile and to just use a custom update, it doesn't make any more sense to me.
Care to elaborate past one line that doesn't help at all? Hell when using shell commands through adb, it keeps on saying "permission denied" any time I type in su.

You have an unlocked bootloader, so flash a custom recovery via fastboot, and use the custom recovery to flash the su zip...

danger-rat said:
You have an unlocked bootloader, so flash a custom recovery via fastboot, and use the custom recovery to flash the su zip...
Click to expand...
Click to collapse
Thanks Danger-rat. Although I know you said nothing different that what was already said in this thread, I figured that since you didn't give me specific info about whether or not there were multiple versions of su.zip or fastboot.zip, I figured I should take that as a "No.", so I went for it. All re-rooted now.
I appreciate the help.
EDIT: So if you are as new to this stuff as I am, anyone else who's reading-
You can DL su.zip from http://www.google.com/url?sa=t&sour...ZxOuf9Kw_URvtvh9Q&sig2=Hj72LDNoiBq2Zoa4QquZWQ
and fastboot.zip from http://www.mediafire.com/?ttdkgamud3j
and amon Ra 2.2.1 from http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-passion-v2.2.1.img
then follow the directions here: http://forum.xda-developers.com/showthread.php?t=1019759
** Note: again, these are for people who have unlocked bootloaders. For that info, you'll have to go elsewhere, but it should be readily available, such as this stuff is. I'm just linking it again because I know how frustrating it can be for people like me who aren't too well versed in rooting/unlocking yet.

Downgrade 2.3.6 to 2.2.2 - Nexus One
Problem:
I would like to downgrade my Nexus One to 2.2.2, because I've had non-stop problems with Gingerbread.
So I've gone through the Bootloader -> Recovery -> apply sdcard:update.zip steps, and it fails. This begs the question, how do I go from 2.3.6 to 2.2.2?
Fix:
Generally, phone manufacturers will not allow you to downgrade for various reasons. The stock recovery does indeed validate the update image, so that it's of a greater (or same) version than the installed system. With the Nexus One being a developer phone, you can unlock the bootloader and replace the recovery image with the one that doesn't perform this check, and will allow installation of any image. The caveat is that unlocking the bootloader voids your warranty with the carrier (and sometimes the manufacturer too,) and wipes all user data off the device.
Unlocking the N1 is dead easy. Just install Android SDK and the USB drivers (located in "google-usb_driver" directory.) Then restart the phone in bootloader mode by shutting it off and powering on while holding down the trackball, hook it up to the computer via USB, and in command prompt issue the following command: C:\<path to Android SDK>\tools\fastboot oem unlock. You will be presented with a confirmation screen with further instructions. Upon successful unlock, you can flash a custom recovery that will allow you to install any custom ROM, including downgrade to 2.2.x stock version of Android OS.
To flash ClockworkMod recovery, download the latest version for Nexus One from here, reboot into bootloader mode (power on while holding the trackball down,) and in command prompt issue command C:\<path to ANdroid SDK>\tools\fastboot flash recovery C:\<path to downloaded img>\recovery-clockwork-3.0.0.5-passion.img
Reboot to bootloader mode again, and then use the Volume keys to highlight the "Recovery" option and press Power button. You are now in ClockworkMod recovery, and can flash any custom ROMs via the "Install zip from sdcard" option.
Here is a "stock" 2.2.2 ROM (with root) off XDA-developers forum.
http://forum.xda-developers.com/showthread.php?t=927935
source:http://android.stackexchange.com/questions/13933/downgrade-2-3-6-to-2-2-2-nexus-one
Try It & Report Back...

Bootloader version 3.41 problems

I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34

I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.

how do you flash the old bootloader? if you don't mind me asking.

I have been on boot loader 3.41 for a few days and no issues with twrp. I have flashed a few things since and all is good? Sorry not sure why its not working for some.

ls3c6 said:
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
Click to expand...
Click to collapse
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Sent from my Galaxy Nexus

You are not alone in this issue, me too, and others more, http://forum.xda-developers.com/showthread.php?t=1932063

I update to 4.1.2 using CWM, didn't lose root. Then changed back to TWRP 2.2.2.0 with bootloader 3.41, now I just updated to TWRP 2.2.3. Everything went smooth even though I'm android noobie.

anotherxyz said:
how do you flash the old bootloader? if you don't mind me asking.
Click to expand...
Click to collapse
Code:
fastboot flash bootloader bootloader-3.34-grouper.img
(or whatever the actual filename is). Then you do:
Code:
fastboot reboot-bootloader
You should at that point see the correct version listed in fastboot
masully84 said:
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Click to expand...
Click to collapse
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root).
If you have stock recovery and no root, your only option is fastboot. And that fastboot flash and boot commands do not work. They look like they work - but they don't. So if you already HAVE a custom recovery, it probably won't even break it.
If you really want to do a proper test / prove this, go back to stock recovery with 3.41. Turn the tablet off completely. Boot up holding the three buttons and go into recovery to see that it can go into the stock recovery console. Then reboot with the three buttons again (don't boot AndroidOS), and run the fastboot boot command to run a custom recovery. If that works, I'll eat my hat.
(well, really all that means is that the problem isn't occurring on all systems. Doesn't mean it's not happening to me and many others)
The problem might not be that 3.41 can't boot to recovery -it might just be that 3.41 can't FLASH or BOOT a recovery console through fastboot. Many people will never notice that because:
A). They already have a recovery console flashed, so it still works
B). They flash their recovery from ROM Manager, GooManager, or whatever
If you lose root, you no longer have B as an option. If you also lose your recovery console, you can't get root access back without fastboot, so you have to use fastboot.

Se7enLC said:
Code:
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root)[...]
[/QUOTE]
Not sure you've got it right. At least on my N7. My first try was flashing the update.zip in another thread without updating my ROM at all. Running Paranoid Android (2.1799 then) and TWRP. Not sure when in the mix I updated TWRP though.
Thought it might have been a problem with the update.zip, so downloaded the full update.zip from google and tried installing bootloader*.img from that via fastboot.
No change. Reverted to 3.34 without any playing around with deleting files and all is good.
Click to expand...
Click to collapse

Se7enLC said:
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
Click to expand...
Click to collapse
Found the solution to the the issue (sorta), I too went through all this trouble as you did in your OP.
I did not have to do anything other then straight up flash this version "recovery-clockwork-touch-6.0.1.5.b8147-grouper.img" via fastboot and bam! recovery works. Link - http://forum.xda-developers.com/showpost.php?p=32810167&postcount=228
Problem is with previous versions of 6.0.1.0 (Official) and TWRP 2.3.1
I still prefer TWRP, but hey This is better then the alternative (No recovery at all)
Now we need to figure out what changed between CWM 6.0.1.0 and 6.0.1.5 and get the other guys (TWRP) to fix their **** for us poor saps that seem to be a minority in the Nexus 7 world having this issue.
I would love to know what actually the fix is and why only some have these issues with older versions of CWM and TWRP.