[How-to] Root Droid Charge**5/19/11**[Windows & Mac] Now with GingerSnap!

roc did you use the odin downgrade package originally?

Was never ED2 just followed the steps yesterday and glad everything worked out, even if it was not picture perfect. Now just have to figure how to hide those annoying system update available messages and what to freeze in titanium to hide mobile hotspot now that I have Wireless Tether. Everything else was so easy to figure out, but I do not see anything that says mobile hotspot/hotspot/etc in titanium. Probably one of those com.verizon files that give no clue to what it does. Don't want to freeze something vital so probably just gonna toss it at the end of the apps if nobody else knows.
 
Can someone tell me how the ED2 update is "unrooting" ED1 rooted devices? It is just removing the setuid root permissions on su or it something more involved?
 
Can someone tell me how the ED2 update is "unrooting" ED1 rooted devices? It is just removing the setuid root permissions on su or it something more involved?

If we knew then we could possibly figure it out ..... Why do you think you have an idea to fix it , we are open to ideas

Sent from my SCH-I510 using Tapatalk
 
If we knew then we could possibly figure it out ..... Why do you think you have an idea to fix it , we are open to ideas

Sent from my SCH-I510 using Tapatalk

Looking at the ED2 update file META-INF/com/google/android/updater-script these lines will kill the suid for both su and the superuser.apk:

ui_print("Symlinks and permissions...");
set_perm_recursive(0, 0, 0755, 0644, "/system");
. . .
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");

If that's what's killing it there are a few possibilities for allowing ED1 rooted devices to migrate to ED2:

If the package is downloaded to the phone and requires user action before the update is applied, we could just patch out those lines. Or can we put a patched version on the phone and trigger it manually?

EDIT: It looks like we might be able to patch out those lines in the update file in /cache and then allow the update.
EDIT 2: Since those lines might be needed to actually set some other permissions correctly, we could add:

set_perm(0, 0, 6755, "/system/xbin/su");
set_perm(0, 0, 6755, "/system/xbin/Superuser.apk");


Failing that can we get a version of su that does not reside in /system to work? I've played around with it for a few minutes and cannot get a copy elsewhere to work. I'm not very familiar with the Android security model, but I'm assuming that's what I'm running into problems with here.
 
Last edited:
downgraded to ED1 from ED2, rooted and everything works...

thanks for great tutorial and your work!!!
 
Looking at the ED2 update file META-INF/com/google/android/updater-script these lines will kill the suid for both su and the superuser.apk:

ui_print("Symlinks and permissions...");
set_perm_recursive(0, 0, 0755, 0644, "/system");
. . .
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");

If that's what's killing it there are a few possibilities for allowing ED1 rooted devices to migrate to ED2:

If the package is downloaded to the phone and requires user action before the update is applied, we could just patch out those lines. Or can we put a patched version on the phone and trigger it manually?

Failing that can we get a version of su that does not reside in /system to work? I've played around with it for a few minutes and cannot get a copy elsewhere to work. I'm not very familiar with the Android security model, but I'm assuming that's what I'm running into problems with here.

Can't do it because the update zip is signed and can not be modified

Sent from my SCH-I510 using Tapatalk
 
Just purchased DC .... employee did E2 update for me. :-\

So from what I have read.... I cannot root.

How to roll back to E1 or should I wait?
 
This is exactly what happened to me when I got a DC the other day. Had to use ODIN to flash back to ED1. The best part? The ED1 package was already rooted.
 
Can't do it because the update zip is signed and can not be modified

Sent from my SCH-I510 using Tapatalk

I'm at a disadvantage because I'm not sure what has failed before so forgive me if these ideas have been tried and/or I'm missing something obvious.

Next idea:

It doesn't look like the update replaces init.rc so we can modify it and have it still run after the update. Can we just have init.rc restore the suid bit on su and superuser.apk on boot?
 
I'm at a disadvantage because I'm not sure what has failed before so forgive me if these ideas have been tried and/or I'm missing something obvious.

Next idea:

It doesn't look like the update replaces init.rc so we can modify it and have it still run after the update. Can we just have init.rc restore the suid bit on su and superuser.apk on boot?

have you updated yet?
 
About to downgrade to ED1 and run rooting process on my first android phone, must say its an exciting venture
 
after you downgrade you shouldnt need to run this , just download the superuser app from the market.

Yea, as I'm reading, I see people say the possibility of being "stuck" with ED1 when future updates come along, this confuses me, and I'm not sure what the actual long term effects could be. Does anyone really know for sure if the downgrade route is a "safe" option, or if I should just wait for ED2 to be rooted?
 
Yea, as I'm reading, I see people say the possibility of being "stuck" with ED1 when future updates come along, this confuses me, and I'm not sure what the actual long term effects could be. Does anyone really know for sure if the downgrade route is a "safe" option, or if I should just wait for ED2 to be rooted?

well some claim they have been able to update back up to ED2, its up to you i cant make that decision for you . But one way or another we will be able to root ED2 and be able to make an odin package to ED2 again
 

Latest posts

Trending Posts

Members online

Forum statistics

Threads
956,867
Messages
6,970,411
Members
3,163,644
Latest member
RichardDixon