Database Info

[Q] Need Fix To Green Bot of ! Problem

A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?

microi said:
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
Click to expand...
Click to collapse
How about reverting to stock 3.0.1, then OTA updating to 3.2 and then rooting/flashing recovery and custom rom/kernel. I would think the issue is with the 3.2.1 OTA update itself.

I'm not completely sure I understand but if u can try this,
Download the universal root update zip and put it on your xoom
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Flash the universal root.zip and boot up and use a root file manager to delete those two file and clockwork should stick through a reboot
Sent from my ADR6400L using Tapatalk

Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?

bandit197 said:
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
Click to expand...
Click to collapse
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.

okantomi said:
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
Click to expand...
Click to collapse
Cheers, I went ahead with it and it worked out no problems, unlocked, rooted and I can access recovery. Ill post the details in the guide thread to keep everything in the one place.

Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Click to expand...
Click to collapse
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi

microi said:
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
Click to expand...
Click to collapse
by not letting it boot I mean don't let it boot into the rom, and both of those methods u stated will work just fine to reboot
And flash it using whatever method you desire, but I forgot to mention that you may need to flash clockwork again after you boot and delete those files because the install recovery.sh obviously flashes the stock recovery and the point of my method is to keep a custom recovery on your device
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Sent from my Xoom using Tapatalk

superchilpil said:
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Click to expand...
Click to collapse
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.

teameos said:
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
Click to expand...
Click to collapse
I'm getting more and more confused the more times I read this.!!
I have done the update then unlocked to find I now have the green bot!!!!!
Someone please send a simple step by step with some file links to revert back to stock 3.2!
Thanks

I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.

willysp said:
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
Click to expand...
Click to collapse
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?

Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G

okantomi said:
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Click to expand...
Click to collapse
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
bwcorvus said:
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.

willysp said:
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.

ydaraishy said:
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
Click to expand...
Click to collapse
Thanks, that helps explain what they are. So, if an OTA (like 3.2 apparently) wants to patch/replace stock recovery, those are the files that do it on next boot. Would be nice if they deleted themselves when done (from a hacker's POV), but for people running stock, I guess it makes sense for the OS to check the recovery partition at each boot and overwrite it with stock recovery if needed.

willysp said:
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.

okantomi said:
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
Click to expand...
Click to collapse
Sure - glad to.

Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G

bwcorvus said:
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Thanks for the info.

Another Recovery

If anybody need recovery, full worked with new 4.1.1 JB get it here.
Moderator Edit:
Link removed as it is proven this recovery can damage your device.

Gigabyte0 said:
If anybody need recovery, full worked with new 4.1.1 JB get it here
Click to expand...
Click to collapse
What exactly is that, where is it from?
Recovery shouldn't have anything to do with installed Android version.
Sent from my GT-I9000 using xda app-developers app

pawitp said:
What exactly is that, where is it from?
Recovery shouldn't have anything to do with installed Android version.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
If I were to guess, it's a different CWM recovery using JB Kernel?. It probably came from 4pda.ru which is a russian site. HAs a lot of android tablet stuff.
Just a guess. Might research it a little and see what I come up with.
It's not exactly the easiest site to navigate through.
MD

Moscow Desire said:
If I were to guess, it's a different CWM recovery using JB Kernel?. It probably came from 4pda.ru which is a russian site. HAs a lot of android tablet stuff.
Just a guess. Might research it a little and see what I come up with.
It's not exactly the easiest site to navigate through.
MD
Click to expand...
Click to collapse
I don't exactly see the need of a new recovery, since it works independent of the Android version. An "unknown" recovery would be possibly unsafe as well.

Gigabyte0 said:
If anybody need recovery, full worked with new 4.1.1 JB get it here
Click to expand...
Click to collapse
this one save´d my TAB!!!
i was able to reanimate it after i messed up ..
THX a lot

pawitp said:
I don't exactly see the need of a new recovery, since it works independent of the Android version. An "unknown" recovery would be possibly unsafe as well.
Click to expand...
Click to collapse
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery

Gigabyte0 said:
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Click to expand...
Click to collapse
You should give some info when posting, otherwise it is "unknown".
The boot.img contains the kernel not the bootloader. The kernel source is yet to be released by Acer and we don't know if Acer has blocked the dangerous emmc wipe command (which will randomly brick tablets, the more you wipe, the riskier you are) like I did on my kernel or not.

This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Click to expand...
Click to collapse
But what it does not, it does not flashes. Freezes and hangs. Have my tab after 30 minutes. removed and restarted, now it hangs in APX mode. Do you have a solution for this?

Hi There
after i recovered my Tab to work, i´ve done a flash with this Recovery and it freezes.
After this i only was able to turn off the Decvice.
Now it seem´s that i can´t turn on, Black Screen, no LED, only thing the Computer tells an USB Device want´s to install.
Try to install APX drivers an failed.
some ideas?

meier2009 said:
Hi There
after i recovered my Tab to work, i´ve done a flash with this Recovery and it freezes.
After this i only was able to turn off the Decvice.
Now it seem´s that i can´t turn on, Black Screen, no LED, only thing the Computer tells an USB Device want´s to install.
Try to install APX drivers an failed.
some ideas?
Click to expand...
Click to collapse
"This recovery" meaning mine or Gigabyte0's?
If you're in APX mode, you're out of luck and the service center will probably need to replace your mainboard.

"This recovery" meaning mine or Gigabyte0's?
If you're in APX mode, you're out of luck and the service center will probably need to replace your mainboard.
Click to expand...
Click to collapse
Yes, it meant the version of Gigabyte0. Does not sound good.

Spread the word please:
ONLY USE PAWITP'S RECOVERY UNLESS YOU WANT A BRICKED TABLET
If pawitp's recovery is not working for you, then wait. The Recovery released by Gigabyte0 and found on 4PDA is built with Acer's kernel and Acer still has not fixed the brick bug!
Again, do NOT use Gigabyte0's recovery!

NoThrills said:
Spread the word please:
ONLY USE PAWITP'S RECOVERY UNLESS YOU WANT A BRICKED TABLET
If pawitp's recovery is not working for you, then wait. The Recovery released by Gigabyte0 and found on 4PDA is built with Acer's kernel and Acer still has not fixed the brick bug!
Again, do NOT use Gigabyte0's recovery!
Click to expand...
Click to collapse
And I will concurr. So far, Pawitp's has caused 0 issues.
Why somebody would want to install an unheard of recovery, with absolutely 0 information about it, is just asking for trouble.
I'll toss in a note to the FSM, and have him deal with Gigabyte0 on what to do with this link.
MD

Moscow Desire said:
And I will concurr. So far, Pawitp's has caused 0 issues.
Why somebody would want to install an unheard of recovery, with absolutely 0 information about it, is just asking for trouble.
I'll toss in a note to the FSM, and have him deal with Gigabyte0 on what to do with this link.
MD
Click to expand...
Click to collapse
Maybe you can also let this know on 4PDA.ru, as I am not Russian (and you are) you can probably explain it better:
In the Acer 3.0 Android kernel the command MMC_CAP_ERASE, which has caused all the old bricks, is still present. At least it is in the A110 3.0 kernelsource and I have no reason to believe they would remove it in the A700 3.0 kernelsource but not in the A110 one.
When this command exists in the kernel, and the Recovery also allows it (Recovery can also disable it, but the current A700 recovery doesn't do that), you are almost guarantueed a brick.
If you could translate that to 'the Russians' I guess we can save a few more people from bricking.

Thread Closed

Can't mount any partition

Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
also in the bootloader i can see this
Code:
Key driver not found... Booting OS
Android cardhU-user bootloader <1.00 e> released by "WW_epad-10.6.1.8-20130225" A03

matt95 said:
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
Click to expand...
Click to collapse
As long as you can use fastboot, replace it with the version that works on your bootloader:
TWRP 2.4.4. 0-4.2.
CAREFUL: A lot of people bricked their tablets in this state.
Read one of the many threads on this particular issue.
Sent from my TF300T using Tapatalk HD

i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)

matt95 said:
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
Click to expand...
Click to collapse
Weird.
Are you using fastboot to flash?
What messages are you getting from fastboot?
Sent from my TF300T using Tapatalk HD

Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change

matt95 said:
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
Click to expand...
Click to collapse
OK, so flashing fails silently for some reason.
Do you see the blue flash bar on the bootloader screen, when fast boot says "writing"?
Never had any fastboot issues on Linux, but I have seen lots of people having issues with drivers on Windows. If you are using Windows, you might want to read up, how to make sure you have the proper drivers installed.
Short of that, no idea. :-/
Maybe can you post the full output of fastboot?
Should not be more than a couple of lines, right?
Sent from my TF300T using Tapatalk HD

i'm not at home now, i'll post them as soon as i get to it...
anyway i used MacOs, Linux and Windows

Make sure you're using the newest fastboot. There may be a bug on your current version.
Back in August I soft-bricked my tablet - no recovery and no ADB access. Fastboot would turn on on the tablet, but fastboot on my computer (Debian) kept hanging on "waiting for device". I had used fastboot on the same computer a couple weeks earlier to flash a recovery, and lsusb showed all the correct device info, so I thought fastboot was broken on the tablet and I was SOL. Well, fastboot got added to the Debian repos at some point, and I installed that version. 8 months and 2 fastboot updates went by before I even attempted to fix my tablet again (2 weeks ago), but somehow it worked, and I now have an awesome tablet to play with. I have no idea what happened with fastboot when my tablet first bricked, but I can only assume that one of the fastboot updates fixed a nasty bug that only showed up when I bricked the tablet.
I know your device is being recognized by fastboot, and your situation is much different than mine was, but you could be experiencing a completely different bug.

EndlessDissent said:
Make sure you're using the newest fastboot.
Click to expand...
Click to collapse
Good point!
matt, any progress?

http://forum.xda-developers.com/showthread.php?p=40809070
mb it will help you

sorry guys today i was very busy, i'll try to solve it tomorrow

matt95 said:
sorry guys today i was very busy, i'll try to solve it tomorrow
Click to expand...
Click to collapse
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3

CBank said:
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
Click to expand...
Click to collapse
at first i didn't install the correct TWRP but now i can't even flash the correct one that's my problem

I believe this may be the same issue that alot of devices suffered from when the 4.2.1 update first came out.
Here is a thread on the issue
http://forum.xda-developers.com/showthread.php?t=2179874
From what I understand it seems that the 4.2.1 bootloader changed the way that the partition table was setup and thus all previous versions of custom recoveries could not mount any partitions (twrp would ask for password & not be able to mount any partition & cwm also not able to mount any partition) and a new twrp-4.2 version had to be made specifically for the 4.2.1 bootloader.
Still not sure as to why this caused the fastboot issue with the majority of people that flashed an incompatible version of twrp or cwm.
The fastboot issue I am talking about is that when you use the "flash" command everything will seem to go fine , it will say writing... and successful on the command prompt but you will not get any blue progress bar on the tablet itself and after the flash command has completed the fastboot reboot command will not reboot the tablet. Which I find very odd as other fastboot commands will still work without issue.
The only know solution if this is the issue you have is to replace the motherboard.

pjc21 said:
The only know solution if this is the issue you have is to replace the motherboard.
Click to expand...
Click to collapse
bad news

matt95 said:
bad news
Click to expand...
Click to collapse
Well, don't give up yet. That there is no known solution does not mean we can't find any.
If fastboot is broken, can you access via adb, while in recovery?
Also there was a thread on unbricking with fastboot issues. Might try that:
http://forum.xda-developers.com/showthread.php?t=2236885
Sent from my TF300T using Tapatalk HD

i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me

matt95 said:
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
Click to expand...
Click to collapse
Just shows that it can happen to the best of us!
Why don't you try the method from the thread in my last post?
Seems the guy had the same issue with fastboot and solved it.
Sent from my TF300T using Tapatalk HD

i'll definitely try that method! i'll let you know, thanks guys

matt95 said:
i'll definitely try that method! i'll let you know, thanks guys
Click to expand...
Click to collapse
I'm in the same situation that you're in. I can send simple fastboot and ADB commands to the tab but as soon as I try to write anything, it just freezes and requires a hard reset. You'll find that you will be able to erase and send simple reset/info request but no write commands. You'll be able to erase your recovery partition but you will not be able write anything new to it. Good luck!
I ordered a MB from ebay last night. Now I just need to find a guide on replacing it.....

TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader

TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader
TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader error 0x00000000"
bootloader error is 0x00000000
I can gain access to fastboot and atx mode. No recovery though. Need someone to help me. Give me a tutorial if this is possible to fix. Am moderately familiar with fastboot but prefer instructions with the code so I can just copy and paste. I think if I could get a kernel on it I'd be good. And maybe there is hope since the computer sees it. Windows vista x86. tf700t firmware 10.6.1.14.1-20130329 A03.
Thank you in advance.
Cole:crying:

33colburn said:
TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader error 0x00000000"
bootloader error is 0x00000000
I can gain access to fastboot and atx mode. No recovery though. Need someone to help me. Give me a tutorial if this is possible to fix. Am moderately familiar with fastboot but prefer instructions with the code so I can just copy and paste. I think if I could get a kernel on it I'd be good. And maybe there is hope since the computer sees it. Windows vista x86. tf700t firmware 10.6.1.14.1-20130329 A03.
Thank you in advance.
Cole:crying:
Click to expand...
Click to collapse
Reading is your friend
http://forum.xda-developers.com/showthread.php?t=1926286
Seriously though, you can use those directions to flash the recovery. Replace the recovery-jb-touch.img with twrp or whatever recovery you want to use.

Tried Fastboot Kernel/Recovery but Failed
dasunsrule32 said:
Reading is your friend
http://forum.xda-developers.com/showthread.php?t=1926286
Seriously though, you can use those directions to flash the recovery. Replace the recovery-jb-touch.img with twrp or whatever recovery you want to use.
Click to expand...
Click to collapse
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole

33colburn said:
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole
Click to expand...
Click to collapse
Tell us what you did that cause this issue?? make sure you stated what software version, bootloader/cwm version during the incident.

33colburn said:
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole
Click to expand...
Click to collapse
I had this too, when flashing with the 700 attached to a back USB port (which is the primary set, should be fine in tiself), but via an extension cable (apparently NOT OK). I really recommend playing around with your ports and cables -- it gained me my NvFlash blobs after an evening of hair-pulling.
What driver(s) shave you been using/trying?

Thank you.
MartyHulskemper said:
I had this too, when flashing with the 700 attached to a back USB port (which is the primary set, should be fine in tiself), but via an extension cable (apparently NOT OK). I really recommend playing around with your ports and cables -- it gained me my NvFlash blobs after an evening of hair-pulling.
What driver(s) shave you been using/trying?
Click to expand...
Click to collapse
I exchanged the tablet for a new one. I still think I could have brought it back from the dead. One of the questions I asked in another thread was "would it be possible to make a blob with my device specific code from a TWRP backup"? I also understand that nvflash can only be used with the 9.x.x.x bootloaders but those are not compatible with Jelly Bean 4.2. Kinda stinks since I would have liked to stayed on a 9.x.x.x bootloader but, AFAIK you have to update the bootloader to 10.x.x.x in order do install Jelly Bean.
I am only asking for the sake of knowledge as I am one who does not like not being able to solve a problem. Also maybe the infromation contained in a TWRP backup file does not go deep enough to rebuild a blob from it to restore your device?
Thanks for the help.
Cole:good:

33colburn said:
"would it be possible to make a blob with my device specific code from a TWRP backup"?
Click to expand...
Click to collapse
You mean a blob for wheelie&nvflash that contains your bootloader? No.
33colburn said:
I also understand that nvflash can only be used with the 9.x.x.x bootloaders
Click to expand...
Click to collapse
Not true. You can only create the blob file for wheelie with a hacked 9.4.5.30 bootloader, and to install that, you must be on a <= 9.4.5.26 bootloader. After you have this blob and the other backup files, you can upgrade to whatever bootloader you want and still use nvflash with your saved blob. Just don't ever lose it, it's your unique key to nvflash.

twrp problem - cannot see files

So I installed ASUS 4.2.1 Build 10.6.1.15.3. I followed the instructions for installing the twrp.blob via fastboot. All of this worked.
Now when boot into recovery mode, TWRP sees no files. If you click the log on the upper right hand side, it's filled with errors like:
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/staging'
E:Unable to find partition size for '/data'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
E:Unable to mount '/cache'
And so on... I cannot see the files that I have placed in the folders both for internal storage and for a 8GB Micro SD. I'm at a loss. At this point, I'm not even sure how to reflash the ASUS image so that I might start completely over, though I don't know why I'd want to. Any ideas?

I was having the same issue and this worked for me http://forum.xda-developers.com/showthread.php?t=1672108&page=76&nocache=1. its a couple of post down.

Sounds like you flashed a recovery with -JB at the end instead of -42. The -JB recoveries are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader (OTA version 10.6.x). ASUS changed a bunch of important filesystem stuff in the 4.2 bootloader. When you flashed the 4.1 recovery, it erased all your device nodes (the file representation of the hardware on the system, specifically where each filesystem partition resides), so as far as your recovery is concerned, you don't have any internal storage. That's why it can't open anything.
So far, nobody has been able to recover a tablet in this condition.
Also, this is the wrong section. This thread belongs in the Q&A section. It has nothing to do with development.

EndlessDissent said:
Sounds like you flashed a recovery with -JB at the end instead of -42. The -JB recoveries are for the 4.1 bootloader (OTA version 10.4.x). You are on the 4.2 bootloader (OTA version 10.6.x). ASUS changed a bunch of important filesystem stuff in the 4.2 bootloader. When you flashed the 4.1 recovery, it erased all your device nodes (the file representation of the hardware on the system, specifically where each filesystem partition resides), so as far as your recovery is concerned, you don't have any internal storage. That's why it can't open anything.
So far, nobody has been able to recover a tablet in this condition.
Also, this is the wrong section. This thread belongs in the Q&A section. It has nothing to do with development.
Click to expand...
Click to collapse
I used fastboot and rewrote the recovery with the "42" one and it fixed my issues.

Ah. I apologize for picking the wrong section. So there's no way to reflash my device via fastboot?

maddog94d said:
I used fastboot and rewrote the recovery with the "42" one and it fixed my issues.
Click to expand...
Click to collapse
Wow. Ok, let me give that a shot.

maddog94d said:
I used fastboot and rewrote the recovery with the "42" one and it fixed my issues.
Click to expand...
Click to collapse
That doesn't work for most people. Typically, the tablet freezes as soon as fastboot tries to write anything. The correct recovery can never be flashed. Maybe you got lucky. Maybe your situation was slightly different.
Also, the link you posted doesn't seem to lead to a post with any sort of guide. On my phone, in the XDA Premium app, it opens the last page of the TWRP thread, specifically to f69m's most recent post, in which he says that this situation has caused lots of bricks. Ironic, IMO.

sorry bout where the link lead to. it was on the last page explaining what happened. maybe i did get lucky, all i did was the same method for fastboot for the recovery install.

And it worked. Thanks for the head's up. Sorry again for choosing the wrong forum.

I didn't use the link. I just reflashed the 42 twrp using fastboot and it worked.

Glad it worked for you.... maybe 2 of us got lucky lol

maddog94d said:
sorry bout where the link lead to. it was on the last page explaining what happened. maybe i did get lucky, all i did was the same method for fastboot for the recovery install.
Click to expand...
Click to collapse
Other than one poor soul being told that his tablet might be bricked, there is nothing on that page dealing with the OP's problem. The other posts are about flashing a -42 recovery on the 10.6.1.8 OTA and having to update to the 10.6.1.15.3 OTA to fix it.
Edit: it seems like I'm trying to argue something. I'm not. I'm just confused about exactly where the link should have gone.
Also, maybe the fact that you and the OP are on the newest OTA made a difference. Almost everybody I've seen with that problem did it on the first 4.2 OTA. Maybe ASUS fixed something in the newest updates. The newest updates fixed custom recoveries in general, so it could have had other fixes, like for fastboot.

The real question now, is it safe to use custom ROM's on top of this 4.2.2 JB? I suddenly am worried about messing with it...

strakajagr said:
The real question now, is it safe to use custom ROM's on top of this 4.2.2 JB? I suddenly am worried about messing with it...
Click to expand...
Click to collapse
As long as you pay attention to which recovery you're using, there shouldn't be a big problem. That is, if you're positive that the fix worked. Have you made any backups or tried wiping cache/Dalvik? The recovery no longer gives you "can't mount" errors?
If it seems to be working properly, flashing ROMs shouldn't be an issue, but I don't blame you for being cautious. If in doubt, just stick to the stock ROM.

Right, I'm in business. I already used it to flash superuser, and then verified that I have root. Everything seems to be in order.
I'd been using 10.6.1.15.3, so maybe that's why this worked.

Same thing happened to me. It ended up being that i was on the older OS. I followed this thread to the T
http://forum.xda-developers.com/showthread.php?t=2187982
Works perfect!
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

Hi!
Also, here has been described the same situation, in the simplest way possible !
Good luck !

I don't have fastboot or adb available to use, am I out of luck?
Mine just boots into twrp every time. Cannot mount anything. No recovery available on boot. I just get the unlocked message in the top left corner on boot. I can't even stop the boot using the volume buttons. How can I get fastboot/adb back?

Hmmmm....
strakajagr said:
I didn't use the link. I just reflashed the 42 twrp using fastboot and it worked.
Click to expand...
Click to collapse
Two folks who "got lucky." Interesting.

Thread moved,
Please keep all questions to the Q&A section, the development section is for development threads only