Originally Posted by cspiby

I meant to return to stock from AHD, I guess I need to find a full ROM from somewhere first?

Yes, you should be able to find the stock rom on Asus' site.

Originally Posted by farsight73

So this is for the TF101 stock ICS 9.2.1.17 upgrade package via CWM..

Mine was rooted with CWM installed.. Of course with rootkeeper too.
But I'd since flash Guver's custom kernel. Would this work with your flashable zip?
All other system files/apps were untouched..

And will all my installed games and apps remain intake after this update?


Sent from my Transformer TF101 using XDA Premium HD app

This will work fine, but you will lose the custom kernel. You will need to reflash the kernel after flashing this upgrade. Installed games/apps will also remain.

Originally Posted by superdioz

does this asus update finally fix the bosd and reboot problems?

Asus hopes it will fix most problems, but there are already reports this update doesn't fix all cases.

I have just installed this, and it has removed my root. The zip file says rooted.... What can I do now to get root back? There is no SU Icon and If I run Lucky patcher it says I cant do things as don't have root

You didn't really read the startpost then...

If you have root and want to keep it, use OTA Rootkeeper.

But since I assume you still have CWM installed, you can flash the su-bin-3.0.3.2-efghi-signed.zip package from the superuser site.

Originally Posted by wilx

I have just installed this, and it has removed my root. The zip file says rooted.... What can I do now to get root back? There is no SU Icon and If I run Lucky patcher it says I cant do things as don't have root

Did you use OTA RootKeeper as suggested in the OP?
You will need to go back to a rootable firmware, root, use OTA RK, update to .21 and restore root with OTA RK

Originally Posted by Lizard

If you have root and want to keep it, use OTA Rootkeeper.

Did you install OTA rootkeeper before flashing?

Originally Posted by Lizard

You didn't really read the startpost then...



But since I assume you still have CWM installed, you can flash the su-bin-3.0.3.2-efghi-signed.zip package from the superuser site.

Came up with error when I tried to install Error in zip file.
Like a fool I didn't notice the use root keeper, and as the zip file had"rooted" in the title, assume it was allready present

---------- Post added at 02:17 PM ---------- Previous post was at 02:14 PM ----------

Originally Posted by baseballfanz

Did you use OTA RootKeeper as suggested in the OP?
You will need to go back to a rootable firmware, root, use OTA RK, update to .21 and restore root with OTA RK

Thanks, what is the best rootable firmware to go back to with CWM installed does anyone know?

TIA

Originally Posted by wilx

Came up with error when I tried to install Error in zip file.
Like a fool I didn't notice the use root keeper, and as the zip file had"rooted" in the title, assume it was allready present

Ok, let's try to fix this for you:

can you do this in a terminal:

ls -l /system/bin/su

And paste the output? Because I assume you still have su installed just with the incorrect permissions.
The I'll make a small script to correct the permissions from recovery.

Originally Posted by Lizard

This will work fine, but you will lose the custom kernel. You will need to reflash the kernel after flashing this upgrade. Installed games/apps will also remain.

Does not work on guevor's kernels.
Updater script fails on checking pre-install requirements:

assert(apply_patch_check("/system/lib/modules/battery_rvsd.ko", "66c516b01d95c36310cc3e7ee7771b32ed5cb823", "cc8d636a0573c41623c066c4fb5e238f611$
set_progress(0.994619);

That's the first line in the updater-script that fails.
I believe the bcm4329.ko, bcmdhd.ko, scsi_wait_scan.ko, and maybe the /system/vendor/firmware/bcm4329/fw_bcmdhd_p2p.bin will also fail.

Originally Posted by Lizard

Ok, let's try to fix this for you:

can you do this in a terminal:

ls -l /system/bin/su

And paste the output? Because I assume you still have su installed just with the incorrect permissions.
The I'll make a small script to correct the permissions from recovery.

Thanks for your help, I have got home from work realised I still had my root from the .17 update in Root Keeper, so I put that back. thanks very much for your offer of help though. I think it may be an idea to remove the "rooted" from the image name though, because it is misleading and will no doubt fool some other person, if not now, 6 months down the line when they finf the file on their microsd card

Originally Posted by wilx

Thanks for your help, I have got home from work realised I still had my root from the .17 update in Root Keeper, so I put that back. thanks very much for your offer of help though. I think it may be an idea to remove the "rooted" from the image name though, because it is misleading and will no doubt fool some other person, if not now, 6 months down the line when they finf the file on their microsd card

Good to hear it worked out in the end. I've updated the filename, to prevent confusion.