Database Info

[Q] ICS Update Problems

Help! I have downloaded and was in the process of installing the OTA update for ICS on my Transformer TF101. The installation got to the end of the progress bar and a triangle with an "!" appeared. The tablet would not do anything. I rebooted the tablet and now it is just stuck at the Eee Pad screen. when I hold down the power button, it just continuously reboots. I contacted Asus and they say I have to send it back in. I just got it back a few weeks ago from a service repair. Is there anything I can do to get this working again or am I stuck with sending it back to Asus?
Thanks

I am getting the Triangle, but I'm able to restart the unit with a long press on the power button. So, no ICS for me yet, but I'm still able to get back to the old setup. I'm sorry for your loss.

Follow the instructions here: http://forum.xda-developers.com/showpost.php?p=22905630&postcount=3

That worked...thanks! So is there any way to root it again now that I have ICS installed? or do I need to wait?

aamon17 said:
Follow the instructions here: http://forum.xda-developers.com/showpost.php?p=22905630&postcount=3
Click to expand...
Click to collapse
Does this still apply to someone without cwm
Sent from my Transformer TF101 using XDA Premium HD app

Same Issue
I too am having this issue but now I am stuck at work with no WIFI to try this above. But I am running stock ROM, Recovery and no Root. I had root but the last OTA I got removed it. I downloaded it this morning and ran it failed with the Triangle and then re-downloaded it by tethering to my phone at work and it still didn't work. Is it saved on the device anywhere? Or will you have to downloaded it every time? This is pretty frustrating that I waited to ROM or anything due to waiting on ICS and now that it is here I can't get it.
P.S. What the Guy above me asked.

My update issue is due to the SRS_config file that I modified to fix the speaker volume balance. I discovered this after trying the CWM update method.

adude007 said:
My update issue is due to the SRS_config file that I modified to fix the speaker volume balance. I discovered this after trying the CWM update method.
Click to expand...
Click to collapse
I figured this would happen if someone got CWM to work, which I cant even figure out how to properly install CWM to begin with. ntm I left my usb cable at home.

vectorized said:
I figured this would happen if someone got CWM to work, which I cant even figure out how to properly install CWM to begin with. ntm I left my usb cable at home.
Click to expand...
Click to collapse
vectorized:
I had trouble getting CWM to install via the Recovery installer.apk method that is available in the dev section. The trick was to COPY, REPEAT COPY, SU from system/bin to system/xbin and then that program recognized root. I used root explorer. Seriously copy don't move.
You can get that APK one click method here:
http://forum.xda-developers.com/showpost.php?p=22359727&postcount=218
Edit: On review it looks like you probably want the second link. That will install the newer CWM which allows for internal & SD Card ZIP files to be flashed
Then I had to use the full install CWM version of our OTA update:
http://forum.xda-developers.com/showthread.php?t=1514658
Edit: Option B to be clear.
I hope this helps.

I ended up going to the original transformer rom and flashing every firmware update from that. It took a while. now I've got ice cream sandwich. Now I just need root
Sent from my Transformer TF101 using XDA Premium HD app

[Q] NVFlashable Recovery?

I have a B40 on Stock Honeycomb, rooted.I decided I was going to try and ota update to ICS again. However, it seems though that the firmware update corrupted at some point. Part way through its flash the little android came up with the exclamation mark. I rebooted and it booted fine and said that the update failed and things were being reverted. It lied . While the system boots and runs fine. My stock recovery is broken. If I volume down then up to select recovery. It just hangs. I tried to flash a different recovery using Gnufabios installer. It said I don't have root(which is also not true). So I tried CWM. It said it flashed ok and it even says Im currently using Cwm. However, again on trying to select recovery during boot it hangs. So I'm curious if there is a straight flashable recovery via nvflash or if its just easier to flash the entire prime package for example. Loss of data doesnt bother me. Everything important is on my microSD.
Also, if someone could send me the NVflash program/package as it seems the original host site is forever busy.
Any and all help/advice is appreciated.
Tim

Team Rouge has an nvflash version of there recovery. Look in dev section

ok awesome ty. Now to just click "retry download" at filefactory.com for nvflash until my eyes bleed.

/facepalm. Need apx Drivers. Why can nothing be easy?

Nvflash upload here
http://forum.xda-developers.com/showpost.php?p=23222380&postcount=414
Should have apx driver in the package

Ya that's where I have been trying to download it from since last night. (Download slots are always full) I know dev's don't take kindly to unauthorised mirrors. However, I kinda wish there was a mediafire one right now.

WIN! Downloaded an old rootkit and extracted the drivers from there. Recovery is back up and working.
Baseballfanz. Tyvm This is the third time you have helped me since I have been here in my short time. But who's counting/
Cheers!

tcolec540 said:
Ya that's where I have been trying to download it from since last night. (Download slots are always full) I know dev's don't take kindly to unauthorised mirrors. However, I kinda wish there was a mediafire one right now.
Click to expand...
Click to collapse
Are you sure, I just check and was able to download in about 30 sec from here
https://rapidshare.com/#!download|5...p|6939|R~677E71B13409D91BE5ED7644C9C3EAD0|0|0

baseballfanz said:
Are you sure, I just check and was able to download in about 30 sec from here
https://rapidshare.com/#!download|5...p|6939|R~677E71B13409D91BE5ED7644C9C3EAD0|0|0
Click to expand...
Click to collapse
Lol. Go figure. I did search. Obviously, I failed. You know you don't have to show me up AFTER I solve my issue. Trust me ill give you more opportunities in the future to do it
Sent from my Transformer TF101 using XDA

tcolec540 said:
Lol. Go figure. I did search. Obviously, I failed. You know you don't have to show me up AFTER I solve my issue. Trust me ill give you more opportunities in the future to do it
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
LOL, sorry didn't see the post that you solved it.

[Q] CWM and boot problems

So I might very well get crap for this since I know this has been brought up in numerous locations, however none of the answers seem to quite fit my direct problem and the information is so entirely scattered around the forums that it's a wee bit hard piecing it all together. I do apologize in advance if there is some post that details this already, it's rather late and I'm at my wits end.
So I decided to root the old Transformer today and toss on CWM to flash Revolver (yeah you guys see where this problem is headed). Upon loading up CWM and flashing the rom, I promptly rebooted, at which point it just hung on the title screen. After figiting with it a bit I got it to the point that it simply boot loops into CWM directly now (not sure if that would be what we call an improvement). Now, most solutions to this problem involve cold booting linux (this seems to work for most people) however for me it just hangs. NVflash (is that it?) doesn't seem to be an option since I'm one of the unlucky ones that it wont work for (b80 serial) and I'm not sure where to go from here.
Windows won't recognize it at any stage (CWM/hung at linux boot) however I can load it into APX mode and can successfully run Root Toolkit (though I'm not sure that will help me much).
Now I promise I have at least a wee bit of intelligence, I'm not asking for a complete walkthrough or anything but at the very least if there is an answer buried on the forums somewhere, could someone point me in the right direction?

First of all nvflash now work almost all model of TF101 even above B60. You check in general thread..
Sent from my awesome rooted Defy: 2.3.6 XDA premium

Thank you thank you!
Ysed wheelie and a stock rom file to get back to safety, used peri to get root and recovery back, tried to reflash revolver and BAM same problem lol. Guess I'll be giving another ROM a shot.
farsight73 said:
First of all nvflash now work almost all model of TF101 even above B60. You check in general thread..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse

dotpkmdot said:
Thank you thank you!
Ysed wheelie and a stock rom file to get back to safety, used peri to get root and recovery back, tried to reflash revolver and BAM same problem lol. Guess I'll be giving another ROM a shot.
Click to expand...
Click to collapse
What version of CWM are you using?

The rogue touch recovery that the PERI installs.

Are you completely wiping your TF before installing the ROM? You MUST wipe before installing anything in CWM generally.

dotpkmdot said:
The rogue touch recovery that the PERI installs.
Click to expand...
Click to collapse
Huh. Did you factory reset and wipe data/cache?

Without looking at the options, wiping data/factory reset option, wipe cache, wipe dalvic cache.
Afterwards installing Revolver and next the update.
Tried the whole process again without doing the update, results the same.

Try installing a different ROM and see if you get the same result, if you do I'd reflash everything except the SOS partition stock.

Will do, downloading Revolution now to try and give it a shot.

Thing O Doom said:
Try installing a different ROM and see if you get the same result, if you do I'd reflash everything except the SOS partition stock.
Click to expand...
Click to collapse
So, different rom, same results. After flashing and rebooting, I simply get stuck at the Eee Pad screen. Is there any where you can point me to so I can read up on what I would need to do to reflash everything? I'd rather not turn the tablet into a nifty paperweight.

Search for
'wheelie NvFlash'
You can use that to reflash everything, or if you can Cold-Boot into Android (Hold volume-down then press power and wait 30 seconds, still holding volume-down)
You can use dd if=/sdcard/blob of=/dev/block/mmcblk0p4 (Staging partition) to reflash a blob.
See blob tools for extracting partitions from stock blobs to reflash, it's probably EBT (bootloader) that is messed up.

TWRP ecrypted after CROMI update HELP!

Hey guys. Semi newb here. I unlocked my TF300t a while back on the first offical JB update from ASUS. I then followed all the steps to unlock it and use fastboot to install TWRP. This was months back. I have been steadily updating CleanROM Inheritance as the revisions are released.
This latest revision to 3.4.4 flash was easy....as always. I wiped all and installed. When the system came back up I noticed my wifi was broken. I couldnt get it to initialize. So I booted to recovey so I could wipe all and reflash again just in case. Well, TWRP asked me for a password. Ive never encrypted my tablet nor have I used passwrods in the past as I know they can cause issues with access or permissions. I can hit cancel and use twrp but it wont mount anything or allow me to do anything until I 'decrypt' it. Not sure where to go from here. I guess Id like to flash the new official 4.2 from asus but I need advice on how to do this using fastboot.
Any help or pointers are welcomed. I only used the fastboot once to install twrp so I dont completely remember how to use it or if I can use it to flash a full ROM to hopefully reset the tablet. Thanks for any help! Cause I am stumped...
EDIT:
So I tried to turn off the tablet and pressed VOL DN + PWR to get to recovery options and choose fastboot, it just boot loops back to the asus logo twice then goes back in to TWRP. I cant even get into the OS now like I could. I need to unlock TWRP. PLEASE HELP!
EDIT 2:
I just wanted to add that by no means am I putting any blame on the ROM. Its a badass ROM that I love. The issue I am having is most definitely due to the bootloader and TWRP I suspect. I just dont know what I can do in TWRP locked down the way it is to regain some control...or at least fastboot.

cubaniche1 said:
Hey guys. Semi newb here. I unlocked my TF300t a while back on the first offical JB update from ASUS. I then followed all the steps to unlock it and use fastboot to install TWRP. This was months back. I have been steadily updating CleanROM Inheritance as the revisions are released.
This latest revision to 3.4.4 flash was easy....as always. I wiped all and installed. When the system came back up I noticed my wifi was broken. I couldnt get it to initialize. So I booted to recovey so I could wipe all and reflash again just in case. Well, TWRP asked me for a password. Ive never encrypted my tablet nor have I used passwrods in the past as I know they can cause issues with access or permissions. I can hit cancel and use twrp but it wont mount anything or allow me to do anything until I 'decrypt' it. Not sure where to go from here. I guess Id like to flash the new official 4.2 from asus but I need advice on how to do this using fastboot.
Any help or pointers are welcomed. I only used the fastboot once to install twrp so I dont completely remember how to use it or if I can use it to flash a full ROM to hopefully reset the tablet. Thanks for any help! Cause I am stumped...
EDIT:
So I tried to turn off the tablet and pressed VOL DN + PWR to get to recovery options and choose fastboot, it just boot loops back to the asus logo twice then goes back in to TWRP. I cant even get into the OS now like I could. I need to unlock TWRP. PLEASE HELP!
EDIT 2:
I just wanted to add that by no means am I putting any blame on the ROM. Its a badass ROM that I love. The issue I am having is most definitely due to the bootloader and TWRP I suspect. I just dont know what I can do in TWRP locked down the way it is to regain some control...or at least fastboot.
Click to expand...
Click to collapse
It sounds like you flashed the 4.2 update, as that has a new bootloader which causes the behavior you describe. Did you update it to 4.2 before flashing? If so, then check the threads associated with rooting/recovery with 4.2. Basically, you need to install a patched TWRP 2.4.4.0.

jimpmc said:
It sounds like you flashed the 4.2 update, as that has a new bootloader which causes the behavior you describe. Did you update it to 4.2 before flashing? If so, then check the threads associated with rooting/recovery with 4.2. Basically, you need to install a patched TWRP 2.4.4.0.
Click to expand...
Click to collapse
Hey thanks for the reply! Actually, no I was not installing 4.2. I would like to install a newer version of twrp but I cant do anything in twrp because it says its encrypted. I did read that other thread but all the options given are not available to me. I cant get to fastboot.
BUT heres an update:
I got the PC to recognize my device as a Transformer. But I couldn't get the naked drivers nor the newer Asus drivers to work. So I modified the .ini file for both the MTP install and USB driver install to include the Hardware ID shown in windows under device manager properties for the device. Basically I modded the .ini so that it also looks for the device ID, then saved and had windows look at the folder I gain to install the driver and this time is installed. So now I am going to try to use a fastboot command....Ill update if this works. Otherwise I may need to try adb and Im a total newb at adb...

UPDATE:
Got the driver installed but 2 issues:
1: Device manager says Device Cannot Start
2: I cant get recovery menu to show. Tablet goes right into TWRP recovery after looping through the ASUS boot screen twice.
I am stumped. I don't want to give up but I think I may have to

UPDATE
Just an update for those who were following:
I can boot into APX but since I never loaded NVFLASH I was screwed. Nothing I did to try to force it into download mode worked. Bootloader must be screwed. In any case, I went on ebay and bought a TF300T mainboard that was pulled from a damaged screen unit. It was 80 bukcs and should be here soon. I figure 80 bucks is better that 180 from ASUS or drop another 300-400 on a new tablet. I wish there was a JIG for the tablet. I used it on a SG SII once.

cubaniche1 said:
Just an update for those who were following:
I can boot into APX but since I never loaded NVFLASH I was screwed. Nothing I did to try to force it into download mode worked. Bootloader must be screwed. In any case, I went on ebay and bought a TF300T mainboard that was pulled from a damaged screen unit. It was 80 bukcs and should be here soon. I figure 80 bucks is better that 180 from ASUS or drop another 300-400 on a new tablet. I wish there was a JIG for the tablet. I used it on a SG SII once.
Click to expand...
Click to collapse
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.

chanhny said:
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
Click to expand...
Click to collapse
Nexus 10 has it's drawbacks too, I love my TF300T.
UPDATE:
Installed new mainboard and got her back up and running quickly. Already updated to 4.2.1. I like it. Well done ASUS!

chanhny said:
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
Click to expand...
Click to collapse
Lol. I love my TF300T. Sure, i can buy a better tablet but I would also have to spend a lot more money. I've only got $299 invested in my 32gb tablet plus $49 in my dock. I'm a happy camper. My tablet , when connected to the dock, will last almost twice as long as the Nexus on one charge. I can also keep using the tablet while the dock is charging. I really never even need to put the tablet itself into the charger. You can't do that with the more expensive Nexus 10.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

This feature is one of the reasons I love this tab. I'm having the same problem as op. I can still get into my 4.2 is though but cannot get recovery to read anything. Maybe ill have to wait for a twrp update.
For now as long as the tab works I can deal with it. I would like to get it working the right way again though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

klownin5643 said:
This feature is one of the reasons I love this tab. I'm having the same problem as op. I can still get into my 4.2 is though but cannot get recovery to read anything. Maybe ill have to wait for a twrp update.
For now as long as the tab works I can deal with it. I would like to get it working the right way again though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Have you added the patch yet? This will allow TWRP to pick up your sd card.

I tried flashing the patched one via fastboot but it did not seem to take. Its still encrypted. I'm thinking its not flashing properly. I'm not the only one having this issue. Hopefully I can just wait it out till a fix is found. I'm afriad of screwing it up to where its completely unuseable.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

[Q] screwed something while installing cromi4.0 need some direction

ok so i installed the asus 4.2 no problem. bootloader is unlocked. i then flashed twrp 4.2, then realized i needed to do push 4.4 twrp instead. so i did that. i was able to boot to the asus rom no problem. i then rebooted into twrp, and it starts asking me for a password, all i could do was hit cancel. Nothing will mount, no sdcards no external, no internal memory. so i did a bit of reading and someone said a factory reset from the bootloader screen would fix twrp. that was a big nope.
so, now the tablet will only boot into twrp, but not read anything, and i cant even get to the fastboot menu so that i can push anything. when i reset it says install super user??/ but it also says no os installed. i have a rom on my sd card i could load if i can get twrp to read it, but i tried mounting, and unmounting, and pretty much every option in every menu.
anyone have any insite?
Thank you
Mike

Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.

bythewayr said:
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
Click to expand...
Click to collapse
Did you use twrp from their site.or the modded one here on the forums
Sent from magical jelly bean.

Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app

klownin5643 said:
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's your issue.you need the modded one
Sent from magical jelly bean.

kaos420 said:
That's your issue.you need the modded one
Sent from magical jelly bean.
Click to expand...
Click to collapse
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?

bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
Not sure why I stayed on 4.1 boot loader with 4.2.2 cm10.1 just not worth it to me until a o.c kernel appears
Sent from magical jelly bean.

bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
You might want to dig through the forums. I believe I did read about a trick using the little reset hole (About an inch below the microSD).
From there it might be possible to flash the modded TWRP. From there you should be able to get back into your JB.
I'd be very careful with flashing ROMs, I still don't see anything that confirms we can use one safely on our newest model/version.

I would be totally fine. Just installing stock Asus jellybean for now. Just so I works. I found the thread on the reset hole. I'm going to try it this afternoon.
Sent from my Galaxy Nexus using xda app-developers app

As long as fastboot still works you're not bricked. If you can't boot to download mode try adb in recovery mode and send
Adb reboot download
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend

I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app

klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Check if ADB still works, it should since you have TRWP!
and try:
adb reboot bootloader

klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's why I said to execute adb from recovery.
Code:
adb reboot download
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

ok so the adb reboot bootloader worked. and i was finally able to reboot into the os. turns out it was still on there even though twrp said it was not. so now, i suppose im going to reboot into fastboot, and push the new modded twrp from fastboot. and we should be good? Im going to try it. ill report back. now that i know my adb works correctly, im not so scared of getting stuck. back in a few. thank you guys for the help. and direction. i only hope this helps someone else not get as stuck as i was.
edit:
yeah so that is no good. downloaded the modded one from the thread. though it appears that its the same as the one from twrp site. except the link in the cromi 4.0 first post points to an androidfiledownload site. i pushed it via fastboot. except when executing the reboot command, it simply booted back to the twrp screen with it still asking for a password. so now i guess im looking at reflashing the asus stock rom and letting rewrite the recovery? and starting fresh? can i do that via adb? im still learning adb and fastboot stuff. Thanks.

Can't check this adb command solution till next Thursday but I sure hope it'll work for me, too.
As far as I understand this whole TWRP problem is that it doesn't have permission to do anything which thankfully should keep the original OS safe.
Keep us posted klownin5643. At this point I'm also mostly concerned with getting back the original recovery program.

Same issue here! Happened to me a few weeks back:
http://forum.xda-developers.com/showthread.php?t=2197895
Only when mine booted directly into TWRP connecting it to the PC didnt yeaild me any results, even after I was able to get the PC to install the naked drivers. The PC would error and say, unable to start device so ADB would not work for me either and trying 'adb devices' didnt return any results. The ONLY thing that worked for me was booting into ADX but that did me no good as I had not installed NVFLASH prior to the brick.
The resolution for me was to replace the mainboard. I got it off of eBay for 88 dollars shipped. I replaced it the same day it came in and Im up and running on the new stock 4.2.1 ASUS release. Paying the 88 dollars was better than shopping for a new tablet
Good luck with your troubleshooting OP! :good:

I'm wondering at this point, can I even flash a new recovery? Or even reflash a new ROM thru fast boot? Someone else said they tried thru adb but the files just disappeared. Or was that cause he was just pushing it to the memory card? I had the os running but I got a freeze and reboot. And it went right back to the direct loading of twrp. I don't wanna have to do that every time I restart. What would be the ASB command or fast boot to flash a new rom.?
Sent from my Galaxy Nexus using xda app-developers app

I know I'm not the only one with this problem. But has anyone flashed the stock blob over top and got everything back to normal?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Refering to your question about pushing files with ADB. I pushed them to internal memory, but that was in recovery mode with locked twrp. If you can get out of recovery with "adb reboot bootloader" then it wouldn't be directly applicable.
If you really have functional fastboot commands ( i.e. commands working instead of "waiting for device" ) then flashing a new ROM or recovery should be, more or less, straightforward. One thing I'm not sure about myself is whether new recovery can be named whatever or should it be called "twrp.blob" again. Technically, yoou're giving a "flash recovery" command so it should replace the current one, whatever it is but I'd rather not brick my device for good with a bad flash. Either way, like I mentioned, I have to wait till thursday to try anything.
I have to read more about fastboot to help with the right commands but there's a lot of guides out there.

I can give the flash recovery command and it will be fine. When I give the reboot command it freezes.
Sent from my Galaxy Nexus using xda app-developers app