What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Droid 2 Global ROOT, CUSTOM RECOVERY & SIM UNLOCK Tutorial

I'm not sure as I'm out of the country at the moment and not using VZW's network. If someone could report on this and let me know so I can update the first post that'd be great

z4root worked... but I had to do it like 3 times before I knew for sure I was re-rooted.

--IslesFan
I got the update pushed while in the UK (wasn't expecting it till I got back). "Fortunately" it started downloading at GPRS speed, which gave me time to unfreeze the bloatware and to unroot. The update then installed fine. I was then able to z4root, but, like the poster said, it took a few times, whereas with the original system version, it worked fine first time.


So if I am rooted and the update tries to install then what? Will I have the opportunity to push the update back, unroot and then install the update?
 
u dont need to unroot. install the update then reroot your phone

sent via wireless device

I also tried to use the Skype Mobile app but it says that it cannot connect to skype. I am on 3G and the traditional skype app for wifi works fine. Is this also caused by rooting?
 
quick question- about how long should z4root take to work? 5 mins? 10 mins? Longer?

Everything from the first post has worked fine right up into the blue background screen with the message "running exploit in order to obtain root access..." displayed. I've been on this screen for awhile now...

Verizon
gingerbread
android v2.2.1


thanks!

same here!!
 
quick question- about how long should z4root take to work? 5 mins? 10 mins? Longer?

Everything from the first post has worked fine right up into the blue background screen with the message "running exploit in order to obtain root access..." displayed. I've been on this screen for awhile now...

Verizon
gingerbread
android v2.2.1


thanks!

same here!!

**I just tried it, and finally it worked. It froze the first time and then I just reset my phone and retried it.
 
For the first time I did the Custom Recovery. Now I always get sent to the menu and have to click Reboot Now to get into normal mode. So, since I might need to send the phone back to VZ, is there a way to remove this. Uninstalling the app isn't enough!

Thanks

Ok, so do this:
1. Get root explorer from Market (I know, it costs money. If you really can't spare the cash, there is a way that doesn't cost a thing, but it is more complicated)
2. Open the app, and browse to /system/bin
3. Click Mount R/W
4. Delete the file called "hijack" (no quotes)
5. Now delete logwrapper (NOT LOGWRAPPER.BIN!!! This is very important. delete the file "logwrapper", the one with no .bin at the end!)
5. Rename the "logwrapper.bin file to just "logwrapper" (no quotes). Basically, just delete the .bin part
6. Reboot the phone immediately. Don't launcher any apps. Just exit Root Explorer and then turn the phone off.

You should be good, no more clockworkmod on the phone, all traces have been deleted. Just FYI, anything you do to your device is YOUR responsibility. What I have said will work, but always be aware of risks. But I'm sure you already knew that :)
 
For the first time I did the Custom Recovery. Now I always get sent to the menu and have to click Reboot Now to get into normal mode. So, since I might need to send the phone back to VZ, is there a way to remove this. Uninstalling the app isn't enough!

Thanks

Ok, so do this:
1. Get root explorer from Market (I know, it costs money. If you really can't spare the cash, there is a way that doesn't cost a thing, but it is more complicated)
2. Open the app, and browse to /system/bin
3. Click Mount R/W
4. Delete the file called "hijack" (no quotes)
5. Now delete logwrapper (NOT LOGWRAPPER.BIN!!! This is very important. delete the file "logwrapper", the one with no .bin at the end!)
5. Rename the "logwrapper.bin file to just "logwrapper" (no quotes). Basically, just delete the .bin part
6. Reboot the phone immediately. Don't launcher any apps. Just exit Root Explorer and then turn the phone off.

You should be good, no more clockworkmod on the phone, all traces have been deleted. Just FYI, anything you do to your device is YOUR responsibility. What I have said will work, but always be aware of risks. But I'm sure you already knew that :)

Thanks, I thought I had updated that post but now I see I updated:
http://www.droidforums.net/forum/dr...android-aosp-like-fission-rom-manager-10.html
Basically did exactly what you said, and it worked fine. Phone returned to VzW, replacement working fine.

Thanks
 
Possible dumb question here but I want to be sure I have everything covered. I am getting ready to root but want to be sure that this will not affect the corporate sync email (it is a work phone).

Thanks for the help.
 
Possible dumb question here but I want to be sure I have everything covered. I am getting ready to root but want to be sure that this will not affect the corporate sync email (it is a work phone).

Thanks for the help.

rooting will not alter the OS functionality except add superuser permission and unlock functionality for apps that take advantage of it.

you should be fine.
 
Possible dumb question here but I want to be sure I have everything covered. I am getting ready to root but want to be sure that this will not affect the corporate sync email (it is a work phone).

Thanks for the help.

rooting will not alter the OS functionality except add superuser permission and unlock functionality for apps that take advantage of it.

you should be fine.


I was hoping to hear that.

Thanks for the response.
 
Do I need to change some kind of root password after I use z4root? I seem to remember a story about malware on rooted iPhones that were spreading because people didn't change their root password.
 
Do I need to change some kind of root password after I use z4root? I seem to remember a story about malware on rooted iPhones that were spreading because people didn't change their root password.
No, there aren't any issues like that with the D2G
 
Back
Top