Related
Seems alot of this "everyone will unroot for 2.1" vs. "no one will unroot for 2.1" arguments is going on. Personally, I'd say you'd have to be a fool to unroot for 2.1. Toast has about everything but the camera working, Darch is getting an AOSP built. Even if Sprint DOES release it first, XDA will have custom ROMs up within 24 hours.
EDIT:
Yes, I made a typo on the poll.
Probably, assuming I can use one of the 1.5 RUUs to go back.
On another note, I anticipate that once the official 2.1 is released, all of the current 2.1 builds will basically dissolve and, eventually, all future development will be based on the official 2.1 release.
That's just a guess, but I think it's a good one.
Nandroid muthafucka, can you use it?
Using RA to go back to 1.5 and then doing the RUU is the only way I've gotten it to work.
Get an "Error 180" otherwise.
I'm assuming that the 2.1 update will overwrite RA the way the 1.5 RUU does.
If it doesn't, then of course restoring a Nandroid directly will be sufficient. If it does, then I'll need to go back to the 1.5 RUU, then root, then apply the backup.
abcdfv said:
Seems alot of this "everyone will unroot for 2.1" vs. "no one will unroot for 2.1" arguments is going on. Personally, I'd say you'd have to be a fool to unroot for 2.1. Toast has about everything but the camera working, Darch is getting an AOSP built. Even if Sprint DOES release it first, XDA will have custom ROMs up within 24 hours.
EDIT:
Yes, I made a typo on the poll.
Click to expand...
Click to collapse
First things first, I think the answer mostly depends on if someone tries it and reports whether they can root again afterwards or not.
If so, I believe many will unroot and upgrade.
If not, I doubt anyone here will do it.
Secondly, Toast's 2.1 build, while great(I use it daily) is not even close to the final 2.1
http://www.youtube.com/watch?v=elDD2mxE4ak
^^ Something a bit more like what we will have
Ah crap, I thought you meant you'd keep root.
jonnythan said:
I'm assuming that the 2.1 update will overwrite RA the way the 1.5 RUU does.
If it doesn't, then of course restoring a Nandroid directly will be sufficient. If it does, then I'll need to go back to the 1.5 RUU, then root, then apply the backup.
Click to expand...
Click to collapse
Potential problem being you may not be able to go back to the 1.5 RUU.
For example, if you flash Sprint's second RUU that was released, you are then unable to flash the original one.
So it may end up being you cannot go back to 1.5. Not sure how likely this is though due to the operating system version change, they may allow you to go back because some users may not like it(for some reason )
No, here at XDA some cool guy will probably make a better ROM based on 2.1
I agree that I will probably wait to see if someone can still root after the update if yes then I will probably go back and update then root again. if not then I will wait for one of the great devs here to release a rom built off the official 2.1 so I can keep root
You'd be a fool to unroot for 2.1. After you unroot, it might take weeks, months, or years to find a new exploit to root again. I say keep root and wait until our awesome devs have a rooted version up
I might unroot, but then again I don't want to wait for a root exploit ...
so I might stay rooted and wait for the devs to come out with a nice suitable ROM ...
I'm gonna wait for an root exploit before locking my phone down again with the 2.1 official. Then i'll probably try the official 2.1, not like it, and go back to an XDA 2.1
I give it about 72 hours before my curiosity gets the better of me, but only if there isn't already a viable 2.1 release here.
unroot
I would unroot for the update, simply because i have so much faith in the dev community. Im sure they will be able to root it again.
Powers16 said:
I would unroot for the update, simply because i have so much faith in the dev community. Im sure they will be able to root it again.
Click to expand...
Click to collapse
You love the dev community, yet you'll unroot in hopes they'll be able to root it?
Why not just wait for them to put up a custom ROM and keep root? I really doubt it'll take longer than a few hours, maybe a day to put out a fully working ROM
Well, i didnt say i wouldnt give them time either, ill wait about 2 or 3 days for them to make a custom rom, but i am so damn excited about the update i really am feeling like i am getting the short stick with the cdma hero on sprint. honestly the update needs to come asap.
why would anyone unroot to update? it would only take ten minutes to extract their build and just make an update.zip out of it. u flash it and its as good as sprints ruu. even better because u wont have to worry about root or upgrading to the next android version. lets not forget 2.1 isnt the end of the road for android. as soon as they start releasing updates for it. u can bet they are already working on the next build of android. but yeah i wouldnt unroot for the update. ill just get it, exstact it, make an update zip, and flash that sucker. then go back and tear it apart and start adding all the stuff sprint was to cheap or to dumb to add while removing all the bull they did add. i bet it wont take but an hour before an update.zip hits the forum after sprint releases it.
NOT going to unroot i love the custom roms
toastcfh said:
why would anyone unroot to update? it would only take ten minutes to extract their build and just make an update.zip out of it. u flash it and its as good as sprints ruu. even better because u wont have to worry about root or upgrading to the next android version. lets not forget 2.1 isnt the end of the road for android. as soon as they start releasing updates for it. u can bet they are already working on the next build of android. but yeah i wouldnt unroot for the update. ill just get it, exstact it, make an update zip, and flash that sucker. then go back and tear it apart and start adding all the stuff sprint was to cheap or to dumb to add while removing all the bull they did add. i bet it wont take but an hour before an update.zip hits the forum after sprint releases it.
Click to expand...
Click to collapse
QFMFT!
10chars
okay guys, I tried to figure this out without bothering yall, but my newb knowledge is limited and I'm confused as hell. I was planning on rooting my phone today after reading about all the information I've been collecting from you guys, but now that I have updated my phone, will Toast's method using those files still allow me to root? Or do I need new files in order to root my phone? I see some files on developer page on new root but I'm confused if those are for phones already rooted or not...ahhhh
so I guess I'm asking is..if you have stock phone with new update applied, how do I go about rooting my evo?
We don't know yet. You should not have updated.
Quick and straight to the point, thanks for your reply. I guess I'm a motherfreakin idiot with the worst timing in the world for things like this. FML
TheBiles said:
We don't know yet. You should not have updated.
Click to expand...
Click to collapse
quick question; if i root with Toast's method, then install the rooted updated rom that's in the dev section (by Calkulin), that should be fine, right?
jblazea50 said:
quick question; if i root with Toast's method, then install the rooted updated rom that's in the dev section (by Calkulin), that should be fine, right?
Click to expand...
Click to collapse
yes
-----------------------
So in order to fully root and nand unlock stock evo with new update, all I have to do is follow Toast's step 1&2 then apply the new rooted update on developer site? just wanna get things crystal clear so I don't risk bricking my evo..
I don't know or think it has been confirmed to work with the new update yet.
Toast step 1 will root the phone
Toast step 2 will unlock nand
Installing the new rooted update will flash the stock sprint rom without breaking your root.
mizerab1e said:
So in order to fully root and nand unlock stock evo with new update, all I have to do is follow Toast's step 1&2 then apply the new rooted update on developer site? just wanna get things crystal clear so I don't risk bricking my evo..
Click to expand...
Click to collapse
No. We don't even know if you can use Toast's method to root it. You can be the guinea pig and post results, though!
initial said:
yup.
Toast step 1 will root the phone
Toast step 2 will unlock nand
Installing the new rooted update will flash the stock sprint rom without breaking your root.
Click to expand...
Click to collapse
There is some info going around in dev forum saying Toast's method will not work if you have the new OTA update applied on stock EVO saying you will get error messages and stuff although it will not brick your phone which is adding to more confusion..
has anyone successfully rooted their stock evo with new OTA update applied? or do I need to wait until devs come up with new files needed to root the evo?
mizerab1e said:
There is some info going around in dev forum saying Toast's method will not work if you have the new OTA update applied on stock EVO saying you will get error messages and stuff although it will not brick your phone which is adding to more confusion..
has anyone successfully rooted their stock evo with new OTA update applied? or do I need to wait until devs come up with new files needed to root the evo?
Click to expand...
Click to collapse
All you have to do is place a file in the root of your SD card and reboot the phone. Try it out and post your results!
mizerab1e said:
Quick and straight to the point, thanks for your reply. I guess I'm a motherfreakin idiot with the worst timing in the world for things like this. FML
Click to expand...
Click to collapse
You and me both my friend, you and me both. Sat there as the update came up and thought, I bet this is going to prevent me from rooting today ...
Yeah, ALL root is broken if you install the OTA.
Okay so I've been digging around and asking questions in dev forum, seems like there is no way for Stock EVO with OTA update to root their EVO yet. What bothers me is that I haven't seen a single post from a dev announcing that they are working on new root methods for Stock EVO with new OTA update.. they seem to be more concerned about fixing the issue around previously rooted EVOs, and I'm afraid we are getting left out... I hope this isn't the case, and hopefully one of our brilliant devs will give the new stock evo with OTA update owners some attention to this matter.
mizerab1e said:
Okay so I've been digging around and asking questions in dev forum, seems like there is no way for Stock EVO with OTA update to root their EVO yet. What bothers me is that I haven't seen a single post from a dev announcing that they are working on new root methods for Stock EVO with new OTA update.. they seem to be more concerned about fixing the issue around previously rooted EVOs, and I'm afraid we are getting left out... I hope this isn't the case, and hopefully one of our brilliant devs will give the new stock evo with OTA update owners some attention to this matter.
Click to expand...
Click to collapse
They're busy working on the kernel. Everybody was warned not to accept the OTA and those of us that chose to do it have to lie in our beds until the developers get around to it.
EtherealRemnant said:
They're busy working on the kernel. Everybody was warned not to accept the OTA and those of us that chose to do it have to lie in our beds until the developers get around to it.
Click to expand...
Click to collapse
Seems like that is the case, someone from dev forum suggested that downgrading the OTA to previous one then rooting might wield some fruit, If I can figure out how to do that I'll be more than happy to be a guinea pig for you guys.
TheBiles said:
All you have to do is place a file in the root of your SD card and reboot the phone. Try it out and post your results!
Click to expand...
Click to collapse
I'm not quite sure which file you're talking about, could you elaborate some more?
mizerab1e said:
Okay so I've been digging around and asking questions in dev forum, seems like there is no way for Stock EVO with OTA update to root their EVO yet. What bothers me is that I haven't seen a single post from a dev announcing that they are working on new root methods for Stock EVO with new OTA update.. they seem to be more concerned about fixing the issue around previously rooted EVOs, and I'm afraid we are getting left out... I hope this isn't the case, and hopefully one of our brilliant devs will give the new stock evo with OTA update owners some attention to this matter.
Click to expand...
Click to collapse
They busted their asses to get root the first time, and, as of right now, every EVO that you buy is capable of being rooted. Only people who update without heeding the warnings are affected, so it is kind of hard to convince a dev to throw down all of their current work to go back and try to solve this AGAIN. It should be a general rule of thumb that you NEVER install manufacturer's updates on any piece of electronics that you are interested in hacking/modifying/changing in any way. 99% of the time they provide some kind of security fixes that are not announced.
mizerab1e said:
Seems like that is the case, someone from dev forum suggested that downgrading the OTA to previous one then rooting might wield some fruit, If I can figure out how to do that I'll be more than happy to be a guinea pig for you guys.
Click to expand...
Click to collapse
It doesn't work. I've already tried it. The bootloader is locked.
TheBiles said:
They busted their asses to get root the first time, and, as of right now, every EVO that you buy is capable of being rooted. Only people who update without heeding the warnings are affected, so it is kind of hard to convince a dev to throw down all of their current work to go back and try to solve this AGAIN. It should be a general rule of thumb that you NEVER install manufacturer's updates on any piece of electronics that you are interested in hacking/modifying/changing in any way. 99% of the time they provide some kind of security fixes that are not announced.
Click to expand...
Click to collapse
I have no doubt in my mind the devs are doing everything they can to provide us with their brilliant work, I have no one but myself to blame for updating the OTA without heeding their warnings. I'm sure once the devs iron out all the issues with previously rooted system, they will get around to us as they always have. I just wish there was any way I can contribute to putting some light onto this matter for those who made the mistake of updating their OTA..
Yeah, was kicking myself as I knew it was a mistake.
Am willing to try out some ish too, that is if an extra Guinea is needed.
OK, so i SBF'ed to 2.1, pulled the battery when it was done, then applied the OTA update to 2.2. Worked fine, then i rooted, but was having problems with the market. All apps showed up, but i had this huge list of items waiting to be downloaded and it didnt budge for hours. So i manually downloaded DX Bootstrapper from the market and tried to install the Tranquility rom. I didnt mount the system the first time i tried to install the Tranquility rom so i went back to do it, but this time i did a factory reset, and wiped the cache, then mounted the system and installed the zip. Then i was stuck on an Endless loop of the Tranquility logo. Attempted an SBF restore back to 2.1, and this time it just failed. Now the phone only turns on to the programming screen and i get this message:
Bootloader
30.03
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
Should i just go back to Verizon, not sure if they have this in stock, and not sure what questions they will raise when they see this screen.
Well according to a birdman twitter post:
_mrbirdman_
do not flash back to 2.1 sbf after 2.2 0ta, keys/signature check has changed, if you go to 2.2OTA say goodbye to 2.1 forever....
and then he proceeded to say...
_mrbirdman_
Please retweet, everyones about to wake up! DO NOT DOWNGRADE TO 2.1 SBF FROM THE 2.2 OTA, YOU WILL BE BRICKED! UNTILL WE GET A 2.2 SBF LEAK
So until they leak a 2.2 SBF I don't think anything you can do. =(
They've got a thread over at droidforums with a number of people w/ the same problems too.
I got the same problem Now waiting for leaked 2.2 SBF :|
wow, im screwed.
if i tell verizon that i performed an SBF, will they refuse to replace my phone since i took it upon myself to try to service my phone on my own?
GoldenCyn said:
if i tell verizon that i performed an SBF, will they refuse to replace my phone since i took it upon myself to try to service my phone on my own?
Click to expand...
Click to collapse
i would tell them you were doing the ota it failed then just play dumb. It almost always works.
now the problem is that there are none in stock so im either gonna have to wait for a 2.2 SBF, or a replacement from verizon (and only god knows how long that will take).
I can't believe Motorola. For a company that is just barely getting their feet back on the ground after years of crappy phones - they sure not how to stick it to the consumer. I know we are just small percentage, BUT THAT'S THE POINT. Leaving it unlocked (aka no eFuse, etc.) would not really effect them much.
went to the store today, and they ordered a phone for me and it will be at my house tomorrow before 3pm by fedex. yay!
Even worse...p3droid warned that tranquility was meant to be applied over deodexed systems and the ota is not deodexed...yet.
Sent from my DROIDX using XDA App
GoldenCyn said:
went to the store today, and they ordered a phone for me and it will be at my house tomorrow before 3pm by fedex. yay!
Click to expand...
Click to collapse
That's kind of crazy when you think about it....intentionally brick your phone = get a new (though probably refurbished) phone.
I suppose it would be just about impossible for verizon to determine if the phone was bricked from their update or someone that tried to sbf but gone wrong.
Sent from my DROIDX using XDA App
hello first sorry my english,now let me see if i understaood....i was affreasid about updarte to oficial froyo ota....i am using a leaked froyo with some theme...and deleted some stock apps with root explorer...now my question is if i flash my droid with sbf file and gop back to stock 2.1 and wipe data and everything start over you know....than i upgrade to ota froyo....in this step i will be good??? with no bricked phone???? now my second question can i root this ota...and my last question is it worth since i alrady am in froyo with root with theme??? thanks i hope u undertand my englis hahaha bye and thanks in advance...
denpad2010 said:
hello first sorry my english,now let me see if i understaood....i was affreasid about updarte to oficial froyo ota....i am using a leaked froyo with some theme...and deleted some stock apps with root explorer...now my question is if i flash my droid with sbf file and gop back to stock 2.1 and wipe data and everything start over you know....than i upgrade to ota froyo....in this step i will be good??? with no bricked phone???? now my second question can i root this ota...and my last question is it worth since i alrady am in froyo with root with theme??? thanks i hope u undertand my englis hahaha bye and thanks in advance...
Click to expand...
Click to collapse
Yeah, that's the way to do it. sbf to 2.1 > ota > root.
But the only thinig I see that makes it worth it is if you have bad reception on your phone. OTA has new baseband version, which might help. Other than that, I don't really see any advantages.
As always, modder beware
Personally, I think Motorola will drop the anal attitude of locking down hardware in due time. Probably getting significant downplay from it. The number of people bricking the phones might be higher than other types? I don't know. Of course, only time will tell.
As for the OTAU. It's nice and buttery for an official release imo.
meshdub said:
Yeah, that's the way to do it. sbf to 2.1 > ota > root.
But the only thinig I see that makes it worth it is if you have bad reception on your phone. OTA has new baseband version, which might help. Other than that, I don't really see any advantages.
Click to expand...
Click to collapse
Ok thanks I think I stay with my leaked froyo
You are the reason Motorola has chosen to lock these devices down. It's awful that you bricked your phone through impatience, carelessness, or imprudence, but you shouldn't expect a free replacement because you couldn't follow directions or misunderstood them. These are probably low on stock because of all the consumers like you who did this. When you think about it, you take the one you initially bought out of circulation and then the replacement which you feel that you are owed. Maybe Motorola made enough, but since you bricked yours, another customer has to wait a week longer to get their first one. Thanks for that. If you are going to attempt these modifications you need to make sure you can handle it or have deep pockets.
Motorola locks these phones down for one reason "Verizon" or whatever carrier the phone is on. Motorola doesn't care if we are root or not but if Verizon says "jump" they say "how high". the better they lock it down the more the carrier likes them.
if we have root and can do things like get free wifi tether Motorola doesn't care they have already sold the phone but Verizon does because it takes from their pockets.
not Moto's fault.
iDroidNow said:
Motorola locks these phones down for one reason "Verizon" or whatever carrier the phone is on. Motorola doesn't care if we are root or not but if Verizon says "jump" they say "how high". the better they lock it down the more the carrier likes them.
if we have root and can do things like get free wifi tether Motorola doesn't care they have already sold the phone but Verizon does because it takes from their pockets.
not Moto's fault.
Click to expand...
Click to collapse
This not true, all I'm hearing is fanboyism. What about the Backflip or the Cliq? If you root the Backflip or the Cliq you will lose your manufacturer's warranty not the carrier's warranty. It Motorola's fault not anyone else. Even on the Motorola website they call it illegal when talking about rooting the Cliq, and rooting Android in general. You will your manufacturer's warranty if you root a Motorola Android even if it's on, Verizon, At&t, and or T-Mobile. The carrier's have nothing to do with this.
OTA coming tonight, for real this time
http://androidapproved.com/item/motorola-rolling-out-droid-2-ota-update-tonight/
Not if you are running Fission. Lol
Sent from my DROID2 using XDA App
It does appear that rooted users need to beware.
I have removed all the bloat except for the 3G AP app, and I can not install the OTA.mainly because i am lazy I am going to SBF and then OTA and re-root.
Tell us if you can root after OTAing
Dumb question from me...
I just recently installed the 2.3.15 leak from Motorola (posted in the forums here). Will it still prompt me to update or do I have to sbf back to stock?
I'm rooted and deodexed, but otherwise stock. Have been checking for updates today and not received the update yet... I should at least see the update, yeS?
I got the update.
Sent from my rooted DROID2 using XDA App
Just following up here as well, do NOT attempt to SBF your device using the current available droid 2 sbf if you get the update. Angdroid/Motoboy was testing it out on his development D2 and it's now a paper weight.
My advice, exercise extreme caution with this OTA, from what I hear you will be stuck with stock D2 MotoBlur for hte time being if you update.
bladearronwey said:
Just following up here as well, do NOT attempt to SBF your device using the current available droid 2 sbf if you get the update. Angdroid/Motoboy was testing it out on his development D2 and it's now a paper weight.
My advice, exercise extreme caution with this OTA, from what I hear you will be stuck with stock D2 MotoBlur for hte time being if you update.
Click to expand...
Click to collapse
Thanks for the tip!
I still haven't seen the update and am considering doing a factory reset. Has anyone gotten any information about the performance increase / battery life in the update, is it worthwhile to seek it out?
Is this update for the R2D2 version also?
I have been hitting system update now for a few days. Just a few times a day. I still have not gotten the update. Is there any way to make it go? I figured it would have gotten to me by now.
tgrantjr said:
I have been hitting system update now for a few days. Just a few times a day. I still have not gotten the update. Is there any way to make it go? I figured it would have gotten to me by now.
Click to expand...
Click to collapse
Same here ...
at least im not the only one not getting it. Would doing a factory reset possibly kick it to start?
tgrantjr said:
at least im not the only one not getting it. Would doing a factory reset possibly kick it to start?
Click to expand...
Click to collapse
Factory reset didn't do it for me. If you really want it, just flash the 2.3.2 SBF
This thread at droidforums has a link to an update file. Probably shorter/easier than applying a new .sbf, but same result.
People are also saying that the 1-2-3 root method will give root back after applying the update.
That said I have not applied either and have still not received the update automatically.
Verizon doesn't push the update to everyone at the same time, different markets will get the update at different times. They do this to not overload the servers
How would I tell if i got the update?
I gave up waiting and applied the update from droidforums using the stock bootloader. Worked like a charm on my stock droid 2. Haven't yet re-rooted since I don't really see a need for root at the moment.
I was able to pull down the update today. It just finished, so no comments or thoughts on it yet.
edit:
I restored the bloatware and unrooted before applying the update. No issues upgrading. I have not tried to apply root again (yet).
So I'm going to go out on a limb and say that there is no solution to root a TP that's already applied the 2.0 update?
I've tried the root methods already obtainable on here and they don't work. I'm guessing (more hoping) that someone is working on finding a solution.
Makes me sad. A co-worker updated it for me because "it said it needed to update it so I did it for you"... *sigh*
OTA2 removed the exploit unless you were already rooted and used Voodoo Rootkeeper to maintain root during the update. I haven't heard the outcome with regards to 2.5. I don't want to risk root so won't be updating unless it's safe.
2.5 is out ? which your version of tablet ?
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Either people like us find a way to downgrade or wait until a new exploit is found. The former seems easier but my knowledge of these things isn't very high...
Yeah, I'm not sure how to either. I'm good at following directions but when a "friend" upgrades your device for you...
As for downgrading, I don't think that'll be an option until someone finds a Lenovo rom flash utility.
byersbw said:
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Click to expand...
Click to collapse
2. 5 was not available to US last week. How did you get it? Supposedly it's still going through certification. 0086_US is 2.0. What version are you?
Oh hell.... I've been reading too many posts on the Lenovo forums. My apologies, I am running OTA 2.0 NOT 2.5. I will correct my first post and title.
I'm running ThinkPadTablet_A310_02_0039_0086_US.
Okay. Thanks. No worries, but was scratching my head, looking puzzled.
Haha! I can understand. I have that look a lot sadly. I appreciate you telling me as I had no clue as to what exactly I was saying.
Now, if anyone knows someone on the inside at Lenovo that could get the flash utility...
LOL If only.
And now we wait. Did NOT expect CM9 to come out so fast and be working so didn't care much for root otherwise. Oh well, that was my fault and I knew I'd lose root for the time being. Now I wait patiently, since the primary work of the developers now is making CM9 to work properly so w/e.
Why isn't there a way to downgrade the rom to 075? The tab has a recovery boot. If it could be downgraded, it could then be rooted , then updated.
No way to downgrade, unless you know something the rest of us are unaware of. There's a bunch of folks that either can't root at all, or took OTA2 before getting root/without preserving root. We've been told that there's nothing to be done for the time being.
I don't know how to do it, but I know that's how other tabs got around the problem. I only say it in case someone does.
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Thanks. Noob enough that I couldn't explain it, just knew it doesn't work.
YassinTP said:
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Click to expand...
Click to collapse
I wonder what it takes to defeat the check? There must be an update script that performs that check. Editing elements of the update script has been the key to other "can't be done" situations.
http://forum.xda-developers.com/showthread.php?p=22918839[WIP][4.0.3]ICS CM9 ThinkPad Tablet PORT
I'm going to keep putting forth suggestions instead of claiming something can't be done. Afterall, the point of this entire forum is to work togther to overcome obstacles.
While I don't know a lot about these things, if it could be done, it would have been. This forum is overflowing with posts from owners of all kinds devices asking how to downgrade their respective device so they can take root. It's not an uncommon request, and one that I have researched for another device, only to find the same answer. Hey if you find out how to do it, you'll make a fortune.
Two other tablets, the Flyer and the View downgrade to gingerbread, then unlock bootloader, then root, then update to honeycomb, then custom roms are applied. They got the idea from another tab, the Iconia, who got it from the Transformer . . .
I'm just trying to push good and bad ideas to someone with the skills. It's about not taking 'no' as an answer.
Here's the thread for Flyer/View:
http://forum.xda-developers.com/showthread.php?p=21028879[Procedure]No HTC unlock downgrade HC-GB for official OTA