Database Info

[Q] Can the B90 Transformer be downgraded from ICS to honeycomb???

Header says it all... and if the answer is YES, then a link to HOW to accomplish that would be greatly appreciated...
Many thanks...

You would need to root, install cwm recovery, flash a rooted HC ROM.

@basballfanz: how to root the 9.2.2.3 Firmware?

From my experience, once you are on ICS, re-flashing Honeycomb via CWM does NOT solve the reboot issues (you'll have them in Honeycomb too). The ONLY way that I was able to return to a stable version of Honeycom was to NVFLash a stock honeycomb image and go from there. But, since you have a B90, you can't NVFlash, so basically, I think you're screwed at this point....
There is a whole thread about returning to honeycomb via CWM and still having the reboots, etc.. Search it out...
Sent from my Transformer TF101 using Tapatalk 2

meinmichi said:
@basballfanz: how to root the 9.2.2.3 Firmware?
Click to expand...
Click to collapse
Don't think there's a way right now.

Can't you modify/use an ASUS Ota update package and use the stock recovery to 'Update' to HC. Reboot issues will still be there though.
Edit: as in when downgrading for razorclaw root etc

Thing O Doom said:
Can't you modify/use an ASUS Ota update package and use the stock recovery to 'Update' to HC. Reboot issues will still be there though.
Edit: as in when downgrading for razorclaw root etc
Click to expand...
Click to collapse
You can't downgrade on a stock tf.
The trick going from 8.6.5.21 to 8.6.6.19 to use razorclaw is technically an upgrade not downgrade. It was going from 8.6..5.21 to 8.6.6.19

Sorry I wasn't clear, I mean modifying a downgrade ASUS package to trick the Tf into Thinking that it's being updated.
Thanks for the version # clearup though X.x"

a simple rename do not work. Have taste it....
The tf see the update, reboot and start Update. But stoppt...
So what to do? Edit buildprob? Or what read the tf in Thema Update file ?

Get a hc package, unzip the ics package, delete and replace as needed. Probably need to edit build.prop too, and make sure the kernel flashes.

Or is a replace of the blob file the onky we need?
How is the chance of bricked?

Considering the kernel/os differences, higher than you'd want it to be, so I'd only do it as a last resort. Make a nandroid backup before doing any tinkering.

Cant do Backup without root. Thats why i want to downgrade...

Seems like a new method to downgrade from ICS to HC even for the non rooted users.
http://forum.xda-developers.com/showthread.php?t=1622628

THX thats works!

Can someone lead me or explain to me exactly what the s/n number means in terms of rooting and nvflashing. I have C30.
Sent from my Transformer TF101 using XDA

I think the real question here is why would you want to downgrade to HC from ICS? It's pretty well known that a full system restore fixes most issues.

miketoasty said:
I think the real question here is why would you want to downgrade to HC from ICS? It's pretty well known that a full system restore fixes most issues.
Click to expand...
Click to collapse
Why? Because ICS is completely un-stable on ALOT of TF101's (if not all). Honeycomb was rock solid.
Sent from my Transformer TF101 using Tapatalk 2

McSurge45 said:
Can someone lead me or explain to me exactly what the s/n number means in terms of rooting and nvflashing. I have C30.
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
First letter:
B=2011 & C=2012 manufacture year.
Second letter/number:
1=Jan 2=Feb ect till Oct which is A(hex)
So your C3O was manufacture in March 2012.
Only different is the SBK
ASUS changed the sbk mid July 2011.

miketoasty said:
I think the real question here is why would you want to downgrade to HC from ICS? It's pretty well known that a full system restore fixes most issues.
Click to expand...
Click to collapse
Except, it doesn't.

[Q] Update available but nothing happens

Decided to return to stock and try 9.2.2.4 update (currently on 9.2.2.3 WW), in settings-info-firmware update it says that the update is available "check notification area" but nothing really happens. I can notice that some other message is "flashing" from behind, "server busy, try again later" or something like that.
Ive read about the update rolling out in Italy and some other countries in Transformer General so the Asus servers shouldnt be down.
Is anyone else experiencing this? Or something has gone wrong when I was flashing the stock ROM?

Stock rooted? Or did you nvflashed it stock unrooted. Cause i had some sort of problem when i sented it for repairs. When it came back i wanted to update it to android 4.0 . And as everyone i know had there updates i still had none.

batjuh said:
Stock rooted? Or did you nvflashed it stock unrooted. Cause i had some sort of problem when i sented it for repairs. When it came back i wanted to update it to android 4.0 . And as everyone i know had there updates i still had none.
Click to expand...
Click to collapse
Iam not rooted got C10 transformer so nvflash is not an option. I deleted su binary and superuser app via root explorer under Megatron ROM and used this
http://forum.xda-developers.com/showthread.php?t=1622628
guide to push in the 9.2.2.3 WW blob using method 1.
So now Ive got everything completely stock, at least I think I do

VITUSH said:
Iam not rooted got C10 transformer so nvflash is not an option. I deleted su binary and superuser app via root explorer under Megatron ROM and used this
http://forum.xda-developers.com/showthread.php?t=1622628
guide to push in the 9.2.2.3 WW blob using method 1.
So now Ive got everything completely stock, at least I think I do
Click to expand...
Click to collapse
What about your recovery? Stock or cwm?

baseballfanz said:
What about your recovery? Stock or cwm?
Click to expand...
Click to collapse
Stock

I have one that refuses to detect any updates as well. Everything is stock on it.

I had this problem on my stock TF101 quite a long time ago on HC. This thread might help:
http://forum.xda-developers.com/showthread.php?t=1106054

[Q] How can I get root for .24?

Purchased a used TF101 last night, and the update was waiting when I powered it on. Needless to say, I regret doing it now.
However, I believe I have it figured out how to get root. I'd just like someone that's had more experience with the TF101 to verify for me.
Opt. 1
- Download recoveryblob from Wolfman's thread.
- Downgrade to .11 or .17
- Root
- OTA Rootkeeper
- Update to newest firmware
Opt. 2
- Download recoveryblob from Wolfman's thread.
- Downgrade .11 or .17
- Root
- CWM
- Flash custom rom with OTA already included.
Am I looking at a bricked pad here? Not actually sure if .24 can be downgraded, but I figured since it worked for .21. I'd give it a shot and see what happens.

Not bricked in the slightest, bricked means can't turn on at all. Downgrade should work with .24 as well, or just wait for an official root for .24 to come out. I also recommend option 2, if you're going to go through the trouble of downgrading may as well put a ROM on there.

Thing O Doom said:
Not bricked in the slightest, bricked means can't turn on at all. Downgrade should work with .21 as well, or just wait for an official root for .24 to come out. I also recommend option 2, if you're going to go through the trouble of downgrading may as well put a ROM on there.
Click to expand...
Click to collapse
Thanks,
I've found the resident expert. I'll give it a shot tonight when I get home.

meant to type .24 not .21 Sorry, just give it a shot. If the exploit is still there it should work. Good luck.

Thing O Doom said:
meant to type .24 not .21 Sorry, just give it a shot. If the exploit is still there it should work. Good luck.
Click to expand...
Click to collapse
Thanks alot..
Worked perfectly! Downgraded to .17, rooted, installed CWM and Android Revolution.

What's the best way to get just root with .24
Sent from my Transformer TF101 using Tapatalk 2

Ellingsoc said:
What's the best way to get just root with .24
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
If you're currently on .17, you can root using Vipermod, install CWM, and flash just the .24 zip using CWM.

05GT said:
If you're currently on .17, you can root using Vipermod, install CWM, and flash just the .24 zip using CWM.
Click to expand...
Click to collapse
I think you would need to follow the sequence flashing from .17 to .21 update zip and lastly the .21 update zip using CWM. Use Voodoo OTA RootKeeper to retain your root previllage..

I am on .24
Sent from my Transformer TF101 using Tapatalk 2

I have the same problem.
I want to keep my .24 but i can't root this.
Is there a good guide to do this ?
I only want to root - nothing more.
Thanks in advance.

klopikxda said:
I have the same problem.
I want to keep my .24 but i can't root this.
Is there a good guide to do this ?
I only want to root - nothing more.
Thanks in advance.
Click to expand...
Click to collapse
Right now,
There's no way to root .24 without downgrading first. I'm pretty sure that you're going to need CWM as well. Only way I know to do it.

Downgrade without Unlock on .24 i have done 5 TF101's ussing this method all with serials b80 to c20 Go here: http //freek.ws/2012/05/07/howto-root-you-asus-transformer-tf101-or-asus-transformer-prime-tf201-running-ice-cream-sandwich-ics-9-4-2-21-without-unlocking-your-bootloader/

Hi!, i've just followed these instructions to downgrade my TF101 b70 and it was just perfect, easy and fast...
Now i'm with .24 rooted.
Thank you!

Yep, this method worked perfect with my .24 TF101 B50. Thanks!

If you don't aren't proficient with adb, or just don't feel like using it, this is a link that should be easy enough for anybody. It has illustrations and step by step directions. It works for. 24 also.
Good luck
http://freek.ws/2012/05/07/howto-ro...s-9-4-2-21-without-unlocking-your-bootloader/
Sent from my Team-B CM7 Nook Tablet using Tapatalk

No more downgrading crap required anymore! link in my signature for NvFlash for SBKv2!!!

Thing O Doom said:
No more downgrading crap required anymore! link in my signature for NvFlash for SBKv2!!!
Click to expand...
Click to collapse
While I'm not a dev by any stretch, I'm also not tech retarded lol... I have tried downgrading .24 using every method posted and can't seem to make it happen. Close as I get is the firmware update droid with the progress bar then he falls flat with a red triangle. Doom the whole APX mode and everything in your link throws me off and after doing all that I'd still have to root? or would I just have an easier time with the custom ROM stuff (which I don't really need).
Thanks in advance for any help that comes my way.

No, just vol-up+power to get into APX, then NvFlash a custom Recovery (rouge has a version specifically for NvFlash.) Then once you have recovery, either flash a ROM (which will be pre-rooted) or superuser.apk (if you want to stay stock) Easy as pie process.

Your need to downgrade to an ota that is able to be rooted first, then after rooting use ota rootkeeper to maintain your root. You can then update back to. 24 and keep your root. The link that i posted explains this or you could also try wolfs downgrade method, but it requires adb, which some people might not feel comfortable using.
Sent from my Team-B CM7 Nook Tablet using Tapatalk

balrog558 said:
Your need to downgrade to an ota that is able to be rooted first, then after rooting use ota rootkeeper to maintain your root. You can then update back to. 24 and keep your root. The link that i posted explains this or you could also try wolfs downgrade method, but it requires adb, which some people might not feel comfortable using.
Sent from my Team-B CM7 Nook Tablet using Tapatalk
Click to expand...
Click to collapse
It is no longer required with the release of nvflash for b70+ devices.
We are working on a windows binary, but no ETA quite yet.
The recommended way is to install a custom recovery then flash an update.zip to install Superuser.apk and the su binary.
Note that this should also enable "one-click" roots using nvflash for ANY rom version - eventually at least

Does Current Root Method Work On Recent OTA

Since I will be getting this tablet tomorrow. I would like to know if anyone knows if the current debugs root method works on the recently released firmware? I probably will root before connecting to the network; however was just wondering.

crystalstylez said:
Since I will be getting this tablet tomorrow. I would like to know if anyone knows if the current debugs root method works on the recently released firmware? I probably will root before connecting to the network; however was just wondering.
Click to expand...
Click to collapse
Yes, it works just fine with 9.4.5.26. I've done it several times now!

It does. So does RootKeeper if you've already rooted it on an earlier firmware, so you can do this either way.

d14b0ll0s said:
It does. So does RootKeeper if you've already rooted it on an earlier firmware, so you can do this either way.
Click to expand...
Click to collapse
yeah i'm fairly familiar with RootKeeper. Just wanted to know just in case something F's up. Thanks

d14b0ll0s said:
It does. So does RootKeeper if you've already rooted it on an earlier firmware, so you can do this either way.
Click to expand...
Click to collapse
crystalstylez said:
yeah i'm fairly familiar with RootKeeper. Just wanted to know just in case something F's up. Thanks
Click to expand...
Click to collapse
Meh. OTA Rootkeeper has lost both root and the backup on my device on upgrading both .21 to .22 and .22 to 0.26. I do not put my trust in it any longer.

MartyHulskemper said:
Meh. OTA Rootkeeper has lost both root and the backup on my device on upgrading both .21 to .22 and .22 to 0.26. I do not put my trust in it any longer.
Click to expand...
Click to collapse
Have you done OTA or flashed it manually?

MartyHulskemper said:
Meh. OTA Rootkeeper has lost both root and the backup on my device on upgrading both .21 to .22 and .22 to 0.26. I do not put my trust in it any longer.
Click to expand...
Click to collapse
Just make sure it's backed up before an update and you should have no problems. I usually delete the back up copy and create it again just to be safe. I have never had an issue with it. Also if you applied an update like the above poster mentioned manually it will wipe that back up everytime. FOTA should be fine though.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

crystalstylez said:
Since I will be getting this tablet tomorrow. I would like to know if anyone knows if the current debugs root method works on the recently released firmware? I probably will root before connecting to the network; however was just wondering.
Click to expand...
Click to collapse
I actually installed the OTA update and then re-rooted my TF700 without any issues.

d14b0ll0s said:
Have you done OTA or flashed it manually?
Click to expand...
Click to collapse
Both, as the first one was a manual flash, and the second one was OTA. Root lost both times. :S
Sent from my ASUS Transformer Pad TF700T

crystalstylez said:
Just make sure it's backed up before an update and you should have no problems. I usually delete the back up copy and create it again just to be safe. I have never had an issue with it. Also if you applied an update like the above poster mentioned manually it will wipe that back up everytime. FOTA should be fine though.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh well, it worked out in the end, so I'm happy.
Sent from my ASUS Transformer Pad TF700T

Drivers seem to matter a bit for this as I think it's been mentioned in other threads. I did the OTA yesterday and when I went to restore root today from the same laptop I used originally it failed every time. Using a different laptop solved the problem.
The other laptop had the vipermod supplied drivers while this one had whatever windows pulled down from WindowsUpdate.
Now, back to installing BT5

[Q] How to root device on jelly bean?

Hi folks.
I've just bought an Infinity. When booting it for the time, I updated it to Jelly bean. Now I'd like to know how can I root it? Unfortunately the debugfs method does not work anymore. So am I stuck ?
Thanks.

I have the same issue!
Gesendet von meinem GT-I9100 mit Tapatalk 2

You will have to wait for a new method to come out which may be a while. At this time if you lose root or have not rooted prior to JB you cannot get it back.

slainer68 said:
Hi folks.
I've just bought an Infinity. When booting it for the time, I updated it to Jelly bean. Now I'd like to know how can I root it? Unfortunately the debugfs method does not work anymore. So am I stuck ?
Thanks.
Click to expand...
Click to collapse
Yes, you are stuck. You will either have to develop a root method yourself or wait for someone else to do it for you unless you are willing to unlock. If you unlock, you should be able to flash alternate ROMs, etc, the sky's the limit. Be aware though, if you unlock, you will void your warranty and will not be able get OTAs. Flashing ROMs also comes with a certain amount of risk (especially w/out nvflash which you can't get since you upgraded).

Return it if you can. With the new one, Root and save with Voodoo OTA First, then run the JB update. It may be a long time before someone develops a root method for JB. The TF300 has been on JB for a while now and still no Root solution.

micaman said:
Return it if you can. With the new one, Root and save with Voodoo OTA First, then run the JB update. It may be a long time before someone develops a root method for JB. The TF300 has been on JB for a while now and still no Root solution.
Click to expand...
Click to collapse
I think that's the best recommendation to the OP. Cause there's no telling when a native JB root solution will come. Especially since all the Devs are already rooted.
For anyone who has not applied JB yet, this is one thread you'd want to read before applying that update: Last chance to root.

micaman said:
Return it if you can. With the new one, Root and save with Voodoo OTA First, then run the JB update. It may be a long time before someone develops a root method for JB. The TF300 has been on JB for a while now and still no Root solution.
Click to expand...
Click to collapse
Its sad but it is the Best option imo. Its a damn shame that asus ( and others ) have to go so far out of there damn way to stop root.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

i did the voodoo ota rootkeeper. it says I have root but when I try and open titanium backup, it doesn't work. any solutions?

I had an issue with the device at first with es File explorer. Had to install newer beta version of superUser and that fixed it. I have SU 3.1 installed now and all is working fine.

I found a jellybean root exploit in another thread I'll see if I can adapt it to work on the infinity. No guarantees though. I'm sure we'll be able to get this wild beast to submit once more!... eventually.

http://forum.xda-developers.com/showthread.php?t=1915598
might as well try downgrading if your just going to return it anyway.

dopapifreak34 said:
i did the voodoo ota rootkeeper. it says I have root but when I try and open titanium backup, it doesn't work. any solutions?
Click to expand...
Click to collapse
Are you using Superuser or Supersu? SuperSu is better in JB in my experience. Anyway open it and have it forget Titanium. Then open TB again and grant access.

you dont have to wait. you can downgrade to .30 update root it. and upgrade and use vooodoo OTA root keeper to root JB

Downgrade, root, then upgrade to JB again.
[TIP] Downgrade from JB to 0.30 works!