Database Users

MOTO CLIQ has been rooted! (confirmed) read more>>

we have now had a few users out there who have rooted their Cliq, and apparently there are a few ways of going about the process. the link below will take you to theDudes post, and im sure you will find other individuals with other methods if you search through the thread.
good luck to all who wish to root, and happy holidays to all!
_________________________________________________________________
As i do not have a moto cliq in my possession i would not be able to tell you if this is true or not. but to any users out there that DO have access to a Cliq, and are willing to test this. (just in case someone out there hadnt seen it)
Motorola CLIQ Rooted for Full Android Access http://bit.ly/4Y9uLs
(dont hate me, i caught this on a livesearch of android, the info was RT'd by
{@TaimurAsad} if you would like to RT it yourself, please do.)
i would like to hear if this works out. seeing as how the last moto cliq forum was closed.

For italian people I've translated the guide ;-)
http://www.tuttoandroid.net/guide/guida-root-per-il-motorola-cliq-3192/

Its true. I have a Cliq and I rooted it last night. There are two methods to root. One is by Demoshadow and one is by TheDudesAndroid. Both seem to be based on the same idea. They came out about the same time. TheDudesAndroid is actually a little easier to do and the files can be downloaded faster. You posted TheDudes version here. Here is Demoshadows verison just to be fair. Demoshadow's Root

Wonderful news for CLIQ users, I hope milestone will get rooted soon

Yah, its true, and apparently it will work with the Dext as well. Its STILL very raw though. And could possibly brick your phone. May be best to wait a a few days for it to be cleaned up and tested more. Still some risk with it. No flashable update.zip as of yet. Also, they are working on porting Cyanogen's Rom to the cliq and a Nexus One rom. And someone got the NexusOne boot screen running on it.

awesome, so its official. now we just wait for the genius' in the android community to "fancify" it, as they always do. props to all who tried this, and thanks for giving us a 100% positive answer.

does this also mean someone can port motoblur to the g1/mytouch easier?

malaeus said:
awesome, so its official. now we just wait for the genius' in the android community to "fancify" it, as they always do. props to all who tried this, and thanks for giving us a 100% positive answer.
Click to expand...
Click to collapse
This root proccess is different from what we are used to. I actualy rooted mine last night. Spent some time following the M3 forum for awhile and it was no easy task. If we were all "genius'" here why weren't we able to do it? I'm not trying to bash but we need to work together on this and not make anyone feel inferior.

djdeviance said:
This root proccess is different from what we are used to. I actually rooted mine last night.
Click to expand...
Click to collapse
The root process is quite different - and I think that there is a lot to learn from the original thread http://modmymoto.com/forums/showthread.php?t=525915&page=35 starting ~page 35.
The method to flash a custom image was put together by Skrilax_CZ and was the crucial breakthrough for the device. TheDude got 'su' working.
xnappo

tep065 said:
And someone got the NexusOne boot screen running on it.
Click to expand...
Click to collapse
You talking about me? I got it to show for....2 seconds,then bootlooped.
Well,once their is some roms ported/made for the CLIQ ,I think,with the right people,may pass the G1 in terms of roms/hacks.

Got root on my cliq
I followed The Dudes version and had no issues at all getting root. It only took me about 20 mins. I can't wait to see where this goes next. Love the cliq been waiting for root!!
So far everything works for me the same as before no FCs no apps not installing or running.
LK

landykos said:
I followed The Dudes version and had no issues at all getting root. It only took me about 20 mins. I can't wait to see where this goes next. Love the cliq been waiting for root!!
So far everything works for me the same as before no FCs no apps not installing or running.
LK
Click to expand...
Click to collapse
hey after you root the cliq does it still have motoblur?

Where is Cyan or Haykuro? Time to create some ROMs. I need 2.0 pls!

to my knowledge the ROM provided after rooting, is the same ROM. with SU enabled. am i correct in saying this?

malaeus said:
to my knowledge the ROM provided after rooting, is the same ROM. with SU enabled. am i correct in saying this?
Click to expand...
Click to collapse
Yes.
xnappo

Woot. I posted all necessary files and tutorial up on my site. Enjoy! Now all we need is APPS2SD and some speed mods and we'll be all set. This is the official TMO Rom so everything is the same, except you have root.

lolsmiley said:
hey after you root the cliq does it still have motoblur?
Click to expand...
Click to collapse
yes you still have motoblur.. but with root.. all i need now is app to sd and wifitether... i dont really care for hero rom ... or any other slow rom.

cant open rsd lite for some reason
I am running 32-bit windows xp and i downloaded rsd lite v4.5.7 .msi but when i try to run it on my pc it just opens a title bar that says "rsd lite" nothing else shows up. No option to install at all. A little help would be appreciated. Im kinda a noob at this. I work for tmobile and im so tired of the original os on my cliq, too many bugs. Thanks for the help.

kinda got an issue here, i rooted the cliq and everything worked fine following the dude's method, but the deal is that i did user metamorph ad basically screwed the phone, not sure if the theme fails or something, i'm currently unable to flash the phone with rdslite, i was trying to update or flash via update.zip or reseting to factory from the default recovery.img but no look :S..... and ye i know, no nandroid backup installed that's my bad

update firmware, OS to froyo for moto cliq
Hi good afternoon, i would like to know something about the upgrade of the moto cliq whit 1.5 to 1.6 or froyo 2.2, please somebody. Help me with that. Thanks in advance.

2.1 official release for rooted users?

This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?

I don't think they can actually push a OTW update.....
barnacles10 said:
This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?
Click to expand...
Click to collapse

It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other potential nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found. This fully depends on whether old method is patched.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.

danknee said:
It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.
Click to expand...
Click to collapse
Couldn't have said it better myself! I would just suggest waiting until the cook of your preference updates his to include items from the official release.

And the single most important reason: No nandroid. Having a point in time backup is insanely important to me. If I ever have to return my phone and get a refurb, it's nice to know I've got a nandroid that will get me right back to where I was before I turned in my phone.

It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.

jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.
Click to expand...
Click to collapse
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL

Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?

cicada said:
Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?
Click to expand...
Click to collapse
Not possible if the Hboot updates, which it probably will. Those here who tried the test leak 2.1 ruu.exe were unable to run the 1.56 ruu after.
There is an alternative to restore everything except the hboot from the 1.56 ruu here, but you cannot simply run the .exe. This method won't work if the official build has patched the ability to gain root (you won't be able to nandroid). In that case you will be stuck with official 2.1 only.
BTW, speaking from experience with the test build, ruu, hboot, etc.

Kcarpenter said:
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL
Click to expand...
Click to collapse
Open source is never a disadvantage. Ever.

Good to know, would've been awful to have to wait for new root hack just because I tried the new and shiny!
Guess I will sit back and wait for dev magic before I jump the gun.

Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
Mater of semantics, politics, and Ideaologies.
Google has a half belief here, they like open, but they protect that damn search algorithim like its a sacred scripture - Last count I think 8 people on earth knew exactly how it worked.
So the disadvantage to google would be ungodly competition if it was released. Proprietary stuff is a win if you look for profits. Again...depends on which side of the spectrum you are on. Points can be argued either way.

jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
Click to expand...
Click to collapse
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.

ramiss said:
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.
Click to expand...
Click to collapse
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!

Kcarpenter said:
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!
Click to expand...
Click to collapse
ROFL. . . you don't have unlimited text?

lol I would hope having a hero you would have unlimited data and texts
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.

yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.
Click to expand...
Click to collapse
lol! that's great.. ever since sprint gave us that free mobile to mobile in any network I do not bother checking minutes or texts. unless my bill changes.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one.
Click to expand...
Click to collapse
Why is it that people still think open source means insecure? I don't claim to know how previous rooting techniques exploit Android, but I do know that 2 Linux distros have a higher government security rating than any other operating system. I assume most weaknesses in android have to do with the recovery and/or update code, which has nothing to do with Linux.

Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
It IS when HTC bogards it from us and hordes it like cookie monster does cookies. I thought open source meant OPEN SOURCE. Ahh, who knows i probably misunderstood the whole concept

[WIP]Temp-root Gingerbread EVOs

my evo is rooted already and i havent paid much atention since i got my 3d but was there an HBOOT update in the GB OTA as compared to the last Froyo 3.70?
If there wasnt, anyone should be able to a simple downgrade with a previous RUU and then use any of the working root methods for froyo.
just a thought i had while being bored.

Nope, new bootloader is locked. Cant downgrade.

EVOlvedAndroid said:
Nope, new bootloader is locked. Cant downgrade.
Click to expand...
Click to collapse
so there was a bootloader update?

I really don't even know what to say anymore. I give up. Someone else can do it.

github said:
I really don't even know what to say anymore. I give up. Someone else can do it.
Click to expand...
Click to collapse
+1 thats all i have to say about that

what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
The short version is there is no way around or tricking the bootloader. Pretty much every way imaginable to do this has been tried a bunch of times. We need to find a new exploit to get in. Several devs are working on it and itay happen soon. Seems to be more problematic than any one expected.

firket2000 said:
The short version is there is no way around or tricking the bootloader. Pretty much every way imaginable to do this has been tried a bunch of times. We need to find a new exploit to get in. Several devs are working on it and itay happen soon. Seems to be more problematic than any one expected.
Click to expand...
Click to collapse
yes, but you're not tricking the bootloader. the bootloader remains the same. the sys image is all you are changing and the signatures should remain intact if it is pulled out of a froyo ruu. for that matter even try placing a rooted OTA sys image in it. this would not gain s-off but you could run a shell root and su if it would work.

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
As far as I understand, the new bootloader won't allow for downgrading or flashing anything that doesn't match HTCs signature....so modifying files is out of the question....
Sent from my PC36100 using XDA App

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
Can't do that, it would break HTC's signature and the bootloader would not accept it

I need to save this response in a text file so I can just copy and paste it every day.
You can't modify the contents of a RUU provided by HTC on an S-ON HBOOT. The zip is signed by HTC with their private key. The HBOOT has the public key. Changing just 1 bit on the zip will invalidate the private key and HBOOT won't allow it to flash. This is the reason for wanting S-OFF, so you can flash anything via HBOOT (Recovery, for example) without any signature checks.
You also can't downgrade the HBOOT, as it will give you an error about an earlier version.
All the obvious ideas have been tried, over and over again over the past few months since the new update hit.
If you are still confused, please see this article on Wikipedia about Public Key Cryptography.

Don't forget to add that goldcards and battery pull microsd swaps do not work either.

Well, eff. I switched back to Sprint and back to the EVO today after a (very unpleasant) experience with T-MO and the G2X, only to find out my brand new EVO is already on Gingerbread and can't be rooted, ruling out the best part about owning an EVO... all the awesome custom ROMs. Lovely.

There's been all types of shenanigans occurring trying to root this thing. Including physically planting in the ground. No root from that either. Appreciate where you're coming from and trying to help and all though

jjones1983 said:
Well, eff. I switched back to Sprint and back to the EVO today after a (very unpleasant) experience with T-MO and the G2X, only to find out my brand new EVO is already on Gingerbread and can't be rooted, ruling out the best part about owning an EVO... all the awesome custom ROMs. Lovely.
Click to expand...
Click to collapse
Its being worked on right now so no worries
Sent from my PC36100 using XDA App

I'm rooted but jw is there any news on when that source will be out?
My stupid friends at work wouldn't let me root their froyo and now want to pay me to root their gb I don't even want $ .
Sent from my PC36100 using XDA App

[Q] Is the Droid X rootable

I am thinking about getting a Droid X this afternoon. With the OTA update is it rootable and if so with what? Thank!

floridatank said:
I am thinking about getting a Droid X this afternoon. With the OTA update is it rootable and if so with what? Thank!
Click to expand...
Click to collapse
Not the OTA. You will need to sbf back to froyo and then upgrade to the pre rooted GB
Sent from my DROIDX using XDA App

bigshotrob22 said:
Not the OTA. You will need to sbf back to froyo and then upgrade to the pre rooted GB
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I went ahead and got it. It has 2.3.3 on it, Will Gingerbreak work on that? Thanks!

floridatank said:
I went ahead and got it. It has 2.3.3 on it, Will Gingerbreak work on that? Thanks!
Click to expand...
Click to collapse
Nope! Like I said its unrootable
Sent from my DROIDX using XDA App

Unrootable...
But that doesn't mean you can't root.
SBF to froyo.
Flash the 2-part gingerbread .zips.
Flash a custom rom (Liberty?)
Or stay on the froyo kernel...
and try MIUI or Cyanogen.

Be careful and read as much as you possibly can before starting. Myself and at least one other on here with the latest iteration of the X have ended up with boot looping or totally non-responsive devices.
I have started a thread with my findings. I am by no means an expert but I do have much experience with rooting devices going all the way back to the PPC6700.
Good luck.

getting stuck in a bootloop is part of the exploration process IMHO.
At least once per new ROM I'll flash something 'just to see what happens' and end up SBF'ing back. Just make backups between steps if you aren't sure about what will happen next.

it would be nice if one of the devs or people who work on rooting or someone in the know would at least comment if we are going to get a real root with the OTA
i mean im running froyo with CM7 but i sure would like the new firmwares for all the radios flashed and then be running CM7
so if someone could give us some kind of update at least saying no one is even remotely working on trying to gain root on 4.5.596 Official OTA or that yea we are working on it but it is a ***** and taken longer then we expected
that lil bit of info goes a long ways
thanks

I am not aware of any dev working on this ATM.

I don't think rooting 596 ota is critical 2nd unit has opened up alot of new doors and the attention has shifted. However I have flashed all of drew gardens latest and ran cm4dx until nightly 47. Now I'm daily MIUI and loving it, despite locked bootloader the cdma_shadow still has alot of options.
Sent from my DROIDX using XDA Premium App

to my understanding .596 has better battery life and signals are better for wifi and cellular (at least more stable and less drops)
i do not know if this is true but i have read/heard alot of ppl saying the battery life is better on .596
after all there is a .596 for some reason and its not a lil bump from 2.2.340 its pretty big
anyhow someone really needs to figure this out as the baseband has changed....i mean there is the pre-rooted rom .596 that works great so we know it can be done.
whats the big deal...let us have it

m16-maniac said:
anyhow someone really needs to figure this out as the baseband has changed....i mean there is the pre-rooted rom .596 that works great so we know it can be done.
whats the big deal...let us have it
Click to expand...
Click to collapse
the big deal is that there isn't a readily found exploit for the ota, the pre-rooted was done with a diff. method (brute force? recompiled?) but the versions are the same regardless
no ones holding back a secret root method, there just isn't a dev interested in spending huge amounts of time to recreate what already exists
i think it would be interesting to create a batch script that sbf's a phone and installs the pre-rooted .596 but all hidden behind a random animation so the user doesn't see what's happening. if i call it a 'one click' root method lots of people who don't seem to want to take the readily available pre-rooted gb for whatever reason would likely be happy. yeah i understand that if it includes a sbf then data may get lost, but if i said in the instructions of my 'app' that it would happen and they should have backups, people would still likely use it
sorry, but i just don't understand why so many people who want root are seemingly against using the pre-rooted option, as most of them don't have the knowledge to find an exploit or a root method from scratch themselves, so they are still using the work of someone else...

<Disclaimer>I'm going out on a limb here with limited knowledge of the X. <End disclaimer>
From what I read and I don't remember where, the rooting of an X involves a 2nd init method by which it takes control of the initial init. I believe I read the original init isn't able to be exploited and this is the basis of some of the more complicated methods of rooting the X.
If someone knows more about this please correct me or chime in.
I had an Incredible prior. The rooting was more comprehensive and simple. I believe that is because the bootstrap and recovery were not as difficult to get into. That being said, personally, I may be going back to another HTC device if the folks light years smarter than me aren't interested in developing a root method like the other devices out there.

[Q] Root for US OTA 2.0

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