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.

adb "protocol failure" and ROM woes

So, much of the stuff in this and other threads has been a tremendous help. I did pretty much exactly what OP did in this thread http://forum.xda-developers.com/showthread.php?t=1779080.
I was having trouble getting my computer to recognize the usb drivers. I was able to finally get ADB to see the tablet by following this thread., Now, when I go to push the stock rom, I get an error message of "Protocol Failure" in cmd.
Any ideas?

I am trying the Universal Naked Drivers, as I have other android devices. I'm shooting in the dark with that though.

I noticed it says adb out of date. Have you tried updating the sdk?
Any chance you have a HTC phone with htc sync installed on the PC? Read that adb version isn't compatible

same thing happened to me using windows. i tried it using ubuntu and i was able to successfully adb push the rom to the tf300 without any problems.
Sent from my ASUS Transformer Pad TF300T

atomicblue said:
same thing happened to me using windows. i tried it using ubuntu and i was able to successfully adb push the rom to the tf300 without any problems.
Sent from my ASUS Transformer Pad TF300T
Click to expand...
Click to collapse
I tried ubuntu and ADB worked perfectly. I was able to go back to .30 stock.
Now though, whenever I try to flash ASUS-HYDRO 3.7 all I get is a bootloop. I am following each step verbatim.

when you flashed the base did you get any bootloops? the bootloop is probably caused because maybe you flashed both the base and the update at the same time. you were supossed to to flash the base and boot into it then flash the update after the base booted atleast once.
Sent from my ASUS Transformer Pad TF300T

atomicblue said:
when you flashed the base did you get any bootloops? the bootloop is probably caused because maybe you flashed both the base and the update at the same time. you were supossed to to flash the base and boot into it then flash the update after the base booted atleast once.
Sent from my ASUS Transformer Pad TF300T
Click to expand...
Click to collapse
That was the base, not the update. I also get hardlocked at boot if I try with CleanROM.
The only ROM that works is Stock .30. I have also verified that I am running stock after booting in stock, checking kernel version.
Ive tried wiping system multiple times before installing, Ive tried cache, and Dalvik. I also factory reset. Same results every go. Ive redownloaded the zips just incase as well.

which version of CWM are you using?
I had many problems with the touch or TWRP.
If you are not already on it, try 5.5.0.4

mikaole said:
which version of CWM are you using?
I had many problems with the touch or TWRP.
If you are not already on it, try 5.5.0.4
Click to expand...
Click to collapse
I'm using 5.5.0.4.
I go from this stage, install CWM 5.5.0.4 via fastboot, and let it reboot. I restart again in CWM and follow the instructions listed on the ASUS-Hydra page.
-1.you must be unlocked (bootloader) and must have CWM.
Click to expand...
Click to collapse
Check.
-2 reboot to recovery
Click to expand...
Click to collapse
Check
-3.format system under mounts and storage
Click to expand...
Click to collapse
Check
-4.wipe data factory reset
Click to expand...
Click to collapse
Check
-5. choose install zip
Click to expand...
Click to collapse
Check
-6. install and reboot
Click to expand...
Click to collapse
After doing this, the tablet boots to the screen that says This Device is unlocked, and has ASUS in the middle. It sits there for a couple minutes, and then reboots, repeating over and over.
I eventually force shutdown, reenter CWM, and flash .30 back on it, and then fastboot CWM back on. I go through the setup process with .30, and everything works with stock, including wifi and camera.

[Q] Cannot flash any rom

Hi all, it's my first post here.
I have TF101G (B90, WW). I tried to flash CyanogenMod 10, but something went wrong. Now I'm without any rom, and I cannot flash something else (even Asus stock rom), because of Status 7 error. I have TWRP 2.5. I can jump between twrp 2.0, twrp 2.3, cwm 3.2.0.1, cwm 5.8.1.8 and others, but upgrade or downgrade each recovery doesn't work. Still Status 7 error.
How to resolve this issue?

Use Easyflasher to get TWRP working
http://forum.xda-developers.com/showthread.php?t=1688012
Flash ROM from TWRP recovery

trewq21 said:
Hi all, it's my first post here.
I have TF101G (B90, WW). I tried to flash CyanogenMod 10, but something went wrong. Now I'm without any rom, and I cannot flash something else (even Asus stock rom), because of Status 7 error. I have TWRP 2.5. I can jump between twrp 2.0, twrp 2.3, cwm 3.2.0.1, cwm 5.8.1.8 and others, but upgrade or downgrade each recovery doesn't work. Still Status 7 error.
How to resolve this issue?
Click to expand...
Click to collapse
From what I have read, to fix a status 7 error you need a different (working) recovery, but that is not helping it seems. Not sure what to tell you.
Have you tried flashing a new recovery using ADB (using dd command)?
*Detection* said:
Use Easyflasher to get TWRP working
http://forum.xda-developers.com/showthread.php?t=1688012
Flash ROM from TWRP recovery
Click to expand...
Click to collapse
EasyFlasher does not work with the TF101G as it is not SBK v1 or SBK v2. APX/NVFlash/Wheelie are not going to work.

frederuco said:
From what I have read, to fix a status 7 error you need a different (working) recovery, but that is not helping it seems. Not sure what to tell you.
Have you tried flashing a new recovery using ADB (using dd command)?
EasyFlasher does not work with the TF101G as it is not SBK v1 or SBK v2. APX/NVFlash/Wheelie are not going to work.
Click to expand...
Click to collapse
Missed the G, my bad

*Detection* said:
Missed the G, my bad
Click to expand...
Click to collapse
It's all good. Easy to miss that sneaky letter.

So what is the way out from this situation? Only RMA?
That's all command during flashing Asus Rom:
Finding update package...
Opening update package...
Installing update...
assert failed: package_extract_file("blob", "/tmp/blob")
E:Error is /sdcard/WW_epad-user-9.2.2.6.zip
(Status 7)
* Verifying filesystems...
* Verifuing partition sizes...
Error flashing zip ' /sdcard/WW_epad-user-9.2.2.6.zip
Anyone?

Hey guys,
The issue has been solved.
I just switched to another SD card. Lol.

Same issue
trewq21 said:
Hey guys,
The issue has been solved.
I just switched to another SD card. Lol.
Click to expand...
Click to collapse
Hi, I have the same issue. I have tried EasyFlasher 0.8.3 on Windows 8. The driver (...Naked... 0.72) was installed and the device shows in device manager. However if I run the "Flash" button. Then I see a command window flashing and then the success message. But nothing happens on the tablet.
You mentioned another SD card. Does that have affect the process. None of the steps mentioned anything about configuring an SD card
Regards
Jaco

jacodv said:
Hi, I have the same issue. I have tried EasyFlasher 0.8.3 on Windows 8. The driver (...Naked... 0.72) was installed and the device shows in device manager. However if I run the "Flash" button. Then I see a command window flashing and then the success message. But nothing happens on the tablet.
You mentioned another SD card. Does that have affect the process. None of the steps mentioned anything about configuring an SD card
Regards
Jaco
Click to expand...
Click to collapse
The sd card was an issue with TWRP after EasyFlasher completed.
Are you sure you have the proper SBK selected?

frederuco said:
The sd card was an issue with TWRP after EasyFlasher completed.
Are you sure you have the proper SBK selected?
Click to expand...
Click to collapse
I have tried both SBK2 and SBK1. My serial starts with B90, So I selected the SBK2 initially. But from what I read in the forums, the TF101G cannot be flashed with EasyFlasher. Is that assumption correct?

jacodv said:
I have tried both SBK2 and SBK1. My serial starts with B90, So I selected the SBK2 initially. But from what I read in the forums, the TF101G cannot be flashed with EasyFlasher. Is that assumption correct?
Click to expand...
Click to collapse
That is correct. The TF101G has a different SBK than the TF101 and it is unknown.
If you want to root the TF101G, use PERI by Thing O Doom.

frederuco said:
That is correct. The TF101G has a different SBK than the TF101 and it is unknown.
If you want to root the TF101G, use PERI by Thing O Doom.
Click to expand...
Click to collapse
Thanks, So this will allow me to get 4.2 / 4.3 on the device? Do you have a link to a step by step?

[Q] Force OTA udpate?

Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!

Nikojiro said:
Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!
Click to expand...
Click to collapse
I'm having the same issue. No idea, we might just have to wait a while.

Delete Data from Google Framework Apk and then start the Update Checker.

UNCUT88RAW said:
Delete Data from Google Framework Apk and then start the Update Checker.
Click to expand...
Click to collapse
Aah didn't think of that trick, it works, <thank you> pressed :laugh:

Could someone please give me a link to the Stock Recovery and maybe a description what the best way is to flash it instead of the Custom Recovery? Thanks ...

I have had no problems flashing updates with ClockWorkMOD revocery.
However if you have the 1.0 version from http://forum.xda-developers.com/showthread.php?t=2390389 the update will fail with an error.
1.0 had a name wrong that makes it think the update are for a different device.
the command to flash the stock recovery (if every thing is in the correct place) is "fastboot flash recovery recovery.img"

chevyowner said:
1.0 had a name wrong that makes it think the update are for a different device.
Click to expand...
Click to collapse
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!

fquadrat said:
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!
Click to expand...
Click to collapse
When I was checking to see if I had 1.1 I found the naming error is still there.
This brings me to my next point. I had edited the ramdisk on 1.0 to correct the naming error, and not updated to 1.1
Here is a link to 1.1 with the edited ramdisk.
Update
I messed up the link in Google drive i think i fixed it now.

chevyowner said:
Here is a link to 1.1 with the edited ramdisk.
Click to expand...
Click to collapse
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.

fquadrat said:
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.
Click to expand...
Click to collapse
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"

chevyowner said:
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
Sorry, I just flashed stock recovery and my Shield is installing Android 4.3 right this second ...

chevyowner said:
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?

desertflame said:
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?
Click to expand...
Click to collapse
should be

TWRP doesnt seem to be working.. and dual screens..

Tried to boot in to recovery to flash a root zip..
When i volume up to enter recovery, screen goes black. I hit power button and TWRP opens but its unusable and dual screen..top and bottom. Slide to unlock is on the screen but nothing works. Only way out is to hold down power and reset.
Help!

Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!

DatacomGuy said:
Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!
Click to expand...
Click to collapse
What bootloader are you on (its in settings app)

cmendonc2 said:
what bootloader are you on (its in settings app)
Click to expand...
Click to collapse
10.6.1.8-20130225

DatacomGuy said:
10.6.1.8-20130225
Click to expand...
Click to collapse
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.

cmendonc2 said:
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.
Click to expand...
Click to collapse
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?

DatacomGuy said:
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?
Click to expand...
Click to collapse
I know you can use that firmware to install KitKat ROMs as shown here (http://forum.xda-developers.com/showthread.php?p=49028315).
Use the 10.6.1.27.5 firmware with this:
Tylorw1 said:
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700 and TF300: EP201_768_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Click to expand...
Click to collapse

Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?

DatacomGuy said:
Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?
Click to expand...
Click to collapse
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app

cmendonc2 said:
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Alright..
fastboot -i 0x0B05 flash recovery firmwarefile.zip
Click to expand...
Click to collapse
Is that the right syntax?

DatacomGuy said:
Alright..
Is that the right syntax?
Click to expand...
Click to collapse
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.

cmendonc2 said:
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.
Click to expand...
Click to collapse
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
fastboot -i 0x0b05 flash US_epad-user-10.6.1.27.5.zip"
Click to expand...
Click to collapse
and i get:
Unknown partition 'US_epad-user-10.6.1.27.5.zip'
error: cannot determine image filename for 'US_epad-user-10.6.1.27.5.zip'
Click to expand...
Click to collapse
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.

DatacomGuy said:
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
and i get:
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.
Click to expand...
Click to collapse
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob

cmendonc2 said:
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
EDIT2: Is this the right one?
openrecovery-twrp-2.6.3.0-tf300t-JB.blob

DatacomGuy said:
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
Click to expand...
Click to collapse
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.

cmendonc2 said:
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.
Click to expand...
Click to collapse
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?

DatacomGuy said:
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?
Click to expand...
Click to collapse
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.

cmendonc2 said:
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.
Click to expand...
Click to collapse
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?

DatacomGuy said:
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?
Click to expand...
Click to collapse
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1

cmendonc2 said:
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1
Click to expand...
Click to collapse
i dont want to flash any rom right now, i just want to stick with stock 4.2.1...
Last time i flashed TWRP.. albeit incorrectly.. it didnt ask anything when i rebooted into recovery. I'm assuming thats when it asks....