anyone running the 2.1 rom noticed there is an update out from 2.0.26?

[miharkula]

I found out the update shows up if you create a new account on the default "cloud" server.

[alb3rt018]

Did the update cause you to lose root ?

dont know im testin right now with my custom rom

[miharkula]

Did the update cause you to lose root ?

Yes but after reapplying the su fix I got it back.

[alb3rt018]

Yes

well yes it does but i got the rom working with root access on lasted version im still working on the kernal

[Durkbeef]

I found out the update shows up if you create a new account on the default "cloud" server.

I created a new account on the default server and I have yet to recieve an OTA

[alb3rt018]

I created a new account on the default server and I have yet to recieve an OTA

i will release my updated rom when i get approved from opencliq until da just wait a little longer n also click ignore

[miharkula]

I created a new account on the default server and I have yet to recieve an OTA

I didn't get an OTA notice but when I told it to check for an update there was one there. I downloaded it, re-signed it with test keys and then flashed it.

[EnderWiggin]

I created a new account on the default server and I have yet to recieve an OTA

Any clue as to whats different from the 2.0.25 I flashed earlier via RSDLite?

[carrrnuttt]

Yes but after reapplying the su fix I got it back.

I've read all over these boards, and I still am not sure what the "SU fix" exactly is. Sorry if I am being slow on the uptake here.

[Sandial]

i will release my updated rom when i get approved from opencliq until da just wait a little longer n also click ignore

Perhaps I'm being a bit slow on the uptake as well, but I think I am failing to understand the politics at play here. Why is approval necessary in order to release a rom? I mean, nobody has permission from Motorola to distribute it in the first place, so why would opencliq have say in what gets released and what doesn't? Don't get me wrong, I was quite happy to grab and install the "official" 2.1, but threads here are vanishing and I'm not sure why. Anyone care to explain this whole deal to a newb?

I've read all over these boards, and I still am not sure what the "SU fix" exactly is. Sorry if I am being slow on the uptake here.

I was unsure, too. It is here: http://forum.xda-developers.com/showthread.php?t=682828

Following the instructions got su working for me as expected.

[alb3rt018]

Any clue as to whats different from the 2.0.25 I flashed earlier via RSDLite?

dont know really but i already put the new update on the rom.

I've read all over these boards, and I still am not sure what the "SU fix" exactly is. Sorry if I am being slow on the uptake here.

i already fix SU issue is already fix on 1.1

Perhaps I'm being a bit slow on the uptake as well, but I think I am failing to understand the politics at play here. Why is approval necessary in order to release a rom? I mean, nobody has permission from Motorola to distribute it in the first place, so why would opencliq have say in what gets released and what doesn't? Don't get me wrong, I was quite happy to grab and install the "official" 2.1, but threads here are vanishing and I'm not sure why. Anyone care to explain this whole deal to a newb?.

is long story n i wont explan it.dont worry this is good cuz when it come out it work twice as better plus opencliq is working on his rom 2 so your guys will pick which one is better

I was unsure, too. It is here: [APP] Superuser 2.2.2 - Install fixed (really this time) [2010-07-07] - xda-developers

Following the instructions got su working for me as expected.

u still dont got root access?

[mazdroid]

yea i tried it kept trying to update but it would fail and reboot had to wipe and reinstall the original one

[FLSTCraig]

yea i tried it kept trying to update but it would fail and reboot had to wipe and reinstall the original one

Same thing happened to me after trying to apply the update. But I just did a wipe/reset from recovery mode. No need to reflash the ROM. The reset alone should be enough to stop the phone from trying to install the update over and over again.