The difference between .595 and .596? - Droid X General

What is the difference between .595 and .596? In another forum, Lurch81 stated "believe activesync is fixed in .596 but other than that i've not heard anything different between the two other than it being "official". And El Jefe wrote ".001". So I'm guessing there's not much of a difference?

I believe el jefe was correct. And it is official. Thats about it

jideay said:
What is the difference between .595 and .596? In another forum, Lurch81 stated "believe activesync is fixed in .596 but other than that i've not heard anything different between the two other than it being "official". And El Jefe wrote ".001". So I'm guessing there's not much of a difference?
Click to expand...
Click to collapse
I also read on one of the forums that the .596 "official" has a different kernel version than the .595 and previous leaks.

wwwilly1986 said:
I also read on one of the forums that the .596 "official" has a different kernel version than the .595 and previous leaks.
Click to expand...
Click to collapse
Yes also this one changes the bootloader so you can't go back to froyo

Related

Need info regarding 2.1 Official

has anyone done a ROM based on the RELEASED 2.1 yet? I know that the MD5 is the same, but files sizes are different and the "Leaked" one we got has BT and Audio issues. Just wondering if anyone has compared the two yet?
None of the leak based 2.1 ROMS will let my phone sleep unless I go into running services and Kill OBEX.
gunnyman said:
has anyone done a ROM based on the RELEASED 2.1 yet? I know that the MD5 is the same, but files sizes are different and the "Leaked" one we got has BT and Audio issues. Just wondering if anyone has compared the two yet?
None of the leak based 2.1 ROMS will let my phone sleep unless I go into running services and Kill OBEX.
Click to expand...
Click to collapse
Not yet.
Go make one.
Im a bit confused here. The sprint release is the same as the leak you guys had a week ago correct? So why is the leak rooted but the new release is not as of yet? Whats the difference between the two roms?
Damage pulled the bits out of the RUU and made them into an Update Zip. I was asking if anyone had done that with the Official yet.
gunnyman said:
Damage pulled the bits out of the RUU and made them into an Update Zip. I was asking if anyone had done that with the Official yet.
Click to expand...
Click to collapse
I don't think anything has been done with the official yet, i wonder why?
markus_del_marko said:
Im a bit confused here. The sprint release is the same as the leak you guys had a week ago correct? So why is the leak rooted but the new release is not as of yet? Whats the difference between the two roms?
Click to expand...
Click to collapse
The leak that was signed with release keys did not have root...period.
A dev patched it with root. 2 different roms there. K?
markus_del_marko said:
I don't think anything has been done with the official yet, i wonder why?
Click to expand...
Click to collapse
Big things are cooking...Can't you smell it.
On the MD5:
How the hell are file sizes different but the return the same check sum? WTF?
I wasn't aware they were different sizes. Maybe I don't understand how MD5 works as well as I should.
Download the new RUU, do NOT run it as an RUU, but instead, extract the rom.zip and flash it. You'll keep root that way.
HeroMeng said:
Download the new RUU, do NOT run it as an RUU, but instead, extract the rom.zip and flash it. You'll keep root that way.
Click to expand...
Click to collapse
Doesn't he still have to patch SU in? and SH?

RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe

Download ROM HERE
It seems to be a Verizon Droid Eris 2.1 Official ROM.
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe
Anyone test this on their Eris yet?
Its an ruu, I suspect of the OTA maybe. Don't flash if you are root or 1.5
what about leaked v3 ok to flash?
I'm testing it right now. I was running leak v1. Will post results when it's complete.
tereg said:
I'm testing it right now. I was running leak v1. Will post results when it's complete.
Click to expand...
Click to collapse
Ok Thanks buddy
Tried it on leak v3. I still have hboot 1.49 so no change there. Other than that, the only thing that changed was the build number. It now has release-keys instead of test-keys after it. It is the OTA, just doesn't really do much for those running leak v3 and looking to root.
Flash successful HBOOT v 1.49.0000 S-ON
Radio 2.42.00.04.12
Conflipper, I cross-posted this on android forums .com and I gave you credit for posting it. Thank you! This will help all of the folks who are stuck on earlier non-root leaks and just want to get up to the current version (but are having trouble flashing the "leak v3" zip manually).
I've verified that the rom.zip within this RUU is identical (based on checksums) to the non-root PB00IMG.ZIP known as "leak v3" (the fourth leak).
thenestor said:
Conflipper, I cross-posted this on android forums .com and I gave you credit for posting it. Thank you! This will help all of the folks who are stuck on earlier non-root leaks and just want to get up to the current version (but are having trouble flashing the "leak v3" zip manually).
I've verified that the rom.zip within this RUU is identical (based on checksums) to the non-root PB00IMG.ZIP known as "leak v3" (the fourth leak).
Click to expand...
Click to collapse
but this may give us the ablitly to regain further updates, instead of verizon not giving us leakers no mo updates
feel free to spread the word, and get this out there. Spread the word, I am sure people will want the "Official" file.
i keep on getting error about connectiviy to the phone which i have it connected and idk,
also ever other time i try it gives me your battery is less than 30% which its at 68% so idk about that either.
i couldnt get it to work. im gonna give it another redownload and see
mattv3090 said:
Tried it on leak v3. I still have hboot 1.49 so no change there. Other than that, the only thing that changed was the build number. It now has release-keys instead of test-keys after it. It is the OTA, just doesn't really do much for those running leak v3 and looking to root.
Click to expand...
Click to collapse
Your rom had "test-keys" after it before you flashed this? That means you were rooted? If so you just lost root
jearl75 said:
Your rom had "test-keys" after it before you flashed this? That means you were rooted? If so you just lost root
Click to expand...
Click to collapse
i think he meant he was already running leak 3... and not rooted.
Does this bring all the 2.1 Sense UI features to the Eris like friendstream etc?
jearl75 said:
Your rom had "test-keys" after it before you flashed this? That means you were rooted? If so you just lost root
Click to expand...
Click to collapse
LOL
Perhaps folks should try re-reading what thenestor reported up above in this very thread:
[SIZE=+1]The ROM that is bundled inside this RUU IS IDENTICAL TO LEAK-V3[/SIZE].
Don't get your hopes up if you are a leaker; this is only useful for folks who mysteriously were able to manage Leak-V1 (the first leak) or Leak-V2 (the third leak), but are somehow now unable to repeat exactly the same procedure with the Leak-V3 (fourth leak) PB00IMG.ZIP.
bftb0
tenzomonk said:
i think he meant he was already running leak 3... and not rooted.
Click to expand...
Click to collapse
All the leaks (excepting the 2nd chronological leak, the "root-ROM") were shipped with release-keys.
The root-ROM was the only one that reported "test-keys".
bftb0
bftb0 said:
LOL
Perhaps folks should try re-reading what thenestor reported up above in this very thread:
[SIZE=+1]The ROM that is bundled inside this RUU IS IDENTICAL TO LEAK-V3[/SIZE].
Don't get your hopes up if you are a leaker; this is only useful for folks who mysteriously were able to manage Leak-V1 (the first leak) or Leak-V2 (the third leak), but are somehow now unable to repeat exactly the same procedure with the Leak-V3 (fourth leak) PB00IMG.ZIP.
bftb0
Click to expand...
Click to collapse
Right! If people are on the leak and are not holding out for the slim chance of root, they should flash this. Atleast they will have an "official" release
jearl75 said:
Right! If people are on the leak and are not holding out for the slim chance of root, they should flash this. Atleast they will have an "official" release
Click to expand...
Click to collapse
What?
If it is IDENTICAL to Leak-V3; as far as the phone is concerned, how would it be any more or any less official?
I'm wondering, what do people think "Identical" means?
Coinflipper needs to "get the word out" that there is a new copy of Leak-V3 floating around; his OP reads as if this is something new, when it is not.
Wow, great news! It will encourage folks like the poster up above to rush out and unroot their phone.
Oh well, more power to them... or less, as the case may be.
bftb0
bftb0 said:
What?
If it is IDENTICAL to Leak-V3; as far as the phone is concerned, how would it be any more or any less official?
I'm wondering, what do people think "Identical" means?
Coinflipper needs to "get the word out" that there is a new copy of Leak-V3 floating around; his OP reads as if this is something new, when it is not.
Wow, great news! It will encourage folks like the poster up above to rush out and unroot their phone.
Oh well, more power to them... or less, as the case may be.
bftb0
Click to expand...
Click to collapse
First of all I said "those on a leak", didn't say leak v3. Just to bring you up to speed there are 2 leak versions before v3, hence the v3. It would be more official because this one WAS released by Verizon, whereas the leaks were not, which is why they were leaks. It is identical yes, but the build number is different, which would differentiate between leak v3 and this OFFICIAL release should you need to return your phone. Just because the support people might not be able to tell, someone can believe me. I know people who have returned there leak and been charged for a new phone because they had unofficial software on there phone, never even mentioning it. This was a month or more later, just showed up right there on there bill.
So, people who feel better having an official release (whether your on leak v1, v2, or v3) can flash this, it's official. If someone who has root can't read where it says this is for people on the leaks, if you have or ever want root don't update. Then that's their problem, not much you can do about that....

[Q] OTA GB vs leaked GB

Hi guys,
I am currently running the OTA GB version, and am kinda tired of some of the bugs (delay in camera flash, sometimes slow, etc). My question is: does the leaked, rooted version (.596) have the same issues that the OTA seem to have? Is it worth it to sbf and flash the leaked version, or is it a non-issue. I have no fears of sbf-ing and rooting, I just don't want to change the settings back to the way I want them more than I have to.
Thanks!
dianaraven said:
My question is: does the leaked, rooted version (.596) have the same issues that the OTA seem to have? Is it worth it to sbf and flash the leaked version
Click to expand...
Click to collapse
Yes. And no, unless you want/need root.
You can get a custom rom on the leaked one. That could fix things
openbox9 said:
Yes. And no, unless you want/need root.
Click to expand...
Click to collapse
*sigh* That's what I was afraid of. I guess for the time being, I will just deal with it and hope that Motorola finally listens us. Thanks guys.

[RUU LEAKS] 1.69.605.0 & 1.68.605.3 Froyo

http://themikmik.com/forums/viewforum.php?f=296
thanks chingy!
thanks for bringing this here
Both have been s*canned for MR2. Just an FYI.
I assume we wont lose root. WHy two different files
trikotret said:
I assume we wont lose root. WHy two different files
Click to expand...
Click to collapse
trikotret wrote:
so if we are rooted we can flash this baby
chingy51o
No you shouldn't.
You welcome. thank chingy
Just installed Radio 1.69.605.0 on BAMF 3.0 RC4... No issues.
b33zy682 said:
http://themikmik.com/forums/viewforum.php?f=296
thanks chingy!
Click to expand...
Click to collapse
Sent from my ADR6400L using XDA App
trikotret said:
I assume we wont lose root. WHy two different files
Click to expand...
Click to collapse
Why would you assume that?
If you flash any official RUU, you will lose root.
So whats the story with these? Whats new about them?
stevessvt said:
So whats the story with these? Whats new about them?
Click to expand...
Click to collapse
They are newer than previous leaks I've seen posted here on XDA so far...
That being said... 1.68.605.3 was posted on Rootzwiki.com's forums around 6/24.
1.69.605.0 is slightly newer than that.
If these are "full" signed RRU's, and they include an hboot and recovery files, then flashing them will most likely remove root, S-Off, and clockwork/custom recovery.
Jcase mentioned being on a 1.70 build a few weeks ago too.
I'm running the 1.69.605.0 radio on bamf 3. everything seems to be fine.
KidJoe said:
They are newer than previous leaks I've seen posted here on XDA so far...
That being said... 1.68.605.3 was posted on Rootzwiki.com's forums around 6/24.
1.69.605.0 is slightly newer than that.
If these are "full" signed RRU's, and they include an hboot and recovery files, then flashing them will most likely remove root, S-Off, and clockwork/custom recovery.
Jcase mentioned being on a 1.70 build a few weeks ago too.
Click to expand...
Click to collapse
looks like the final release version is 1.70.605.0
http://support.vzw.com/pdf/system_update/thunderbolt.pdf
The will be old soon...
http://twitter.com/#!/teamandirc
TeamAndIRC ✔ jcase
Uploading thunderbolt ota now and full ruu
50 minutes ago
Click to expand...
Click to collapse
and I'm guessing that would be the 1.70.605.0 in the VZW PDF announcing the update.
http://www.androidpolice.com/2011/0...ed-1-70-605-0-update-for-the-htc-thunderbolt/
There ya go
1.70 ota's today and to correct earlier information MR2 was canned for these newer builds.
>> TeamAndIRC ✔ jcase Uploading thunderbolt ota now and full ruu 50 minutes ago
Excellent. New PlainJane right around the corner!
This released ruu has the release baseband, didnt check the older stuff, but here it is in a full PG05IMG flashable.
Compatible w/ the GB leak.
http://www.multiupload.com/IS8UTFDB3H

PLEASE IMPORTANT •••READ ABOUT BRICKING w/LEAKED ICS

AS Many of you know, there have been some People that have been experiencing hard bricking on their Note after Flashing leaked versions of ICS...... Thanks to Entropy512 & Chainfire we have some definitive answers on what is causing this.
THIS IS A MUST READ IF YOU ARE FLASHING CUSTOM ROMS........
DON'T BE LAZY, LAME or FOOLISH.... READ THIS NOW!!!!!
This will help you understand the risks and issues that have yet to be resolved ......
-Now Please Read the Article in the Link... (thx-EGZThunder1)
Thanks,................. Moderators
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
Good one but I think there are too many threads now giving information on bricking etc,. I think it would be better if they are all combined and summarized in a single thread. Just my thought!
Seems redundant to have two stickies for the same topic?
And you posted this saying "leaked" long after official releases have been confirmed affected.
plz i ve read this article but i ve noob question
i am now using lpf prefectly, is it one of leaked ics ?
what leaked ICS mean ?
sehooo said:
plz i ve read this article but i ve noob question
i am now using lpf prefectly, is it one of leaked ics ?
what leaked ICS mean ?
Click to expand...
Click to collapse
It's not leaked ICS. It is the official stock ICS for Taiwanese devices. And it's all safe as long as you don't use CWM, do a factory reset from even the settings menu and also try not to delete huge files right from your phone's explorer.
Sent from my GT-N7000 using XDA
sujal said:
It's not leaked ICS. It is the official stock ICS for Taiwanese devices. And it's all safe as long as you don't use CWM, do a factory reset from even the settings menu and also try not to delete huge files right from your phone's explorer.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
well I don't know I am on stock LPF rom and did a factory reset and no problems at all
I think this whole bricking thing is exaggerated
I upgraded from gb to lpy to lpf
and i used those way by dr ketan
http://forum.xda-developers.com/showthread.php?t=1659308
and rooted by cwm, is it safe or should I go back to gb?
Sent from my GT-N7000 using xda premium
hykhleif said:
well I don't know I am on stock LPF rom and did a factory reset and no problems at all
I think this whole bricking thing is exaggerated
Click to expand...
Click to collapse
It does not affect everyone but there a few 'unlucky' souls. Glad you aren't but avoid doing that. Even one brick is dangerous.
Sent from my GT-N7000 using XDA
If someone don't undestand yet...
read this:
http://forum.xda-developers.com/showthread.php?t=1633938
and pages 123, 124 e 125 of this:
http://forum.xda-developers.com/showthread.php?t=1490986&page=124
Now... stop giving bad advice based on what happens when you flash on your device!
The problem exists and it's not exaggerated.
It doesn't happen 100% of the times, but has high chances to happen !
wrong forum...sorry
yes it happen to me..
this is warning for official ICS too..
Yup... I'm still trying to figure out why we have TWO stickies on this subject now, one of which has had wrong information from the moment it was posted. (As stated before - even when THIS thread was first posted, it was already known that official releases were causing problems.)
Danger after going back to GB
Entropy512 said:
Yup... I'm still trying to figure out why we have TWO stickies on this subject now, one of which has had wrong information from the moment it was posted. (As stated before - even when THIS thread was first posted, it was already known that official releases were causing problems.)
Click to expand...
Click to collapse
I'm still a little unclear: is the danger to the eMMC simply from wiping/recovery with an ICS kernel or is it any wiping operations after having flashed the ICS kernel? That is to say, I had stock Android 4.0.3 LPY ROM and now I'm back on stock Android 2.3.5 KK1. Am I in danger after having used ICS, or am I safe flashing now that I'm back on GB?
vhanna said:
I'm still a little unclear: is the danger to the eMMC simply from wiping/recovery with an ICS kernel or is it any wiping operations after having flashed the ICS kernel? That is to say, I had stock Android 4.0.3 LPY ROM and now I'm back on stock Android 2.3.5 KK1. Am I in danger after having used ICS, or am I safe flashing now that I'm back on GB?
Click to expand...
Click to collapse
No man, you are clear !
Wipe as many as you want !
http://goo.gl/V8aQb
another victim of emmc bug on LP9...
vhanna said:
I'm still a little unclear: is the danger to the eMMC simply from wiping/recovery with an ICS kernel or is it any wiping operations after having flashed the ICS kernel? That is to say, I had stock Android 4.0.3 LPY ROM and now I'm back on stock Android 2.3.5 KK1. Am I in danger after having used ICS, or am I safe flashing now that I'm back on GB?
Click to expand...
Click to collapse
Once you're back on GB or a safe ICS kernel, you're safe. If you experience problems after returning to GB it's because the damage was already done before reverting and it's already too late.
I mean is there any safe ICS kernels out there to use with LPF or LP9?
daraj said:
I mean is there any safe ICS kernels out there to use with LPF or LP9?
Click to expand...
Click to collapse
Not yet. Hopefully, our kernel Devs will deliver us something to work with soon.
daraj said:
I mean is there any safe ICS kernels out there to use with LPF or LP9?
Click to expand...
Click to collapse
Not yet. Well - DAFUQ is safe but it has serious compatibility problems. I'll hopefully fix those this weekend.
Entropy512 said:
Not yet. Well - DAFUQ is safe but it has serious compatibility problems. I'll hopefully fix those this weekend.
Click to expand...
Click to collapse
Great That could be a temporary solution

Categories

Resources