Database Users

Does 1-click root still work w/mt3g???

I know for a fact that 1-click root does not work for G1, I was just wondering if the fix was also done for the mt3g. My educated guess, would be yes, but I just want to hear confirmation. If I can't use the 1-click method, does anyone have an alternative besides the really long method. Basically, I'm trying to root my co-workers mt3g, from work. I don't have access to adb, fastboot, etc. I root a lot of my co-workers G1's, never did mt3g.

...anyone?

If your phone came with stock android 1.5 then you can use the unroot method to get back to 1.5 then one click will work.
if you unroot and its 1.6 stock then I'm unsure.

It works. I was always skeptical of rooting my phone but I did it two days ago. I got my phone originally with cupcake and I receive the OTA update to donut. This is what I did to get root..
First follow this to get back to cupcake:
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Follow this to get root:
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
Loading a custom rom:
http://theunlockr.com/2009/08/22/ho...ps2sd-onto-your-g1-or-mytouch-3g-best-method/
It was really simple and I had no problems. I skipped the App2SD because I only have the original MicroSD card so I can't vouch for that. But everything else worked perfect. I'm currently running Cyanogen 4.2.1 with Enoch Theme which can be found at:
http://forum.xda-developers.com/showthread.php?t=548918

Downgraded from rooted 2.2 to 2.1 and cannot root anymore.

I've read over the forums quite a few times and am stumped. For some reason i cannot get rooted again after SBF flashing to 2.1. I've used the one click root program and while it says the root was successful, i go into adfree, titanium backup, and wifi tether and all tell me that i am not rooted. Super permissions doesn't seem to work either.
I've flashed my phone six times and have had the same results, so i was wondering if anyone else had this problem or could help me out. I just want to root and get back to 2.2 again, but i don't see why I'm having such difficulties when I've had success before in the past. I'm trying to give all the information i can, but there isn't really much to it. I followed all the steps in the HOW TO downgrade 2.2 to 2.1 link in this very forum.
If anyone can help me or tell me whats going on, I'd be in their debt forever.

snorelax said:
I've read over the forums quite a few times and am stumped. For some reason i cannot get rooted again after SBF flashing to 2.1. I've used the one click root program and while it says the root was successful, i go into adfree, titanium backup, and wifi tether and all tell me that i am not rooted. Super permissions doesn't seem to work either.
I've flashed my phone six times and have had the same results, so i was wondering if anyone else had this problem or could help me out. I just want to root and get back to 2.2 again, but i don't see why I'm having such difficulties when I've had success before in the past. I'm trying to give all the information i can, but there isn't really much to it. I followed all the steps in the HOW TO downgrade 2.2 to 2.1 link in this very forum.
If anyone can help me or tell me whats going on, I'd be in their debt forever.
Click to expand...
Click to collapse
Six times? Did you try the 7th????
http://alldroid.org/Default.aspx?tabid=40&g=posts&m=5164#5164
But anyways...did you try to root in manually instead of doing it with one click?

Ok the seventh time was in fact the charm. I just upgraded to 2.2 without root and then SBF flashed to 2.1 again and now when i root, it actually takes and adfree tells me im rooted and super permissions kicks in. I could just not figure out what was going on because it didn't make any sense. It still doesn't, but hey problem solved so i'm not gonna speculate. Anyways thanks for the time.

Droid incredible update

Alright here we go. I've been sent the new new update and I want to install it. I have s-off so I can always reroot which I know how to do. Buuuut I need to find the stock recovery for froyo. Or if it doesnt change I just need stock recovery. Any help locating it will be loved. Thank you all very much!
sent from IOslvr

I got the update this morning and my phone is still rooted. Please clarify what you mean and I will see what I can do .
Sent from my ADR6300 using XDA App

Like install stock recovery so I can install the update then go back to being rooted.
sent from my sexy housemaid

I need the stock recovery image link so I can install it through boot loader.
sent from Ioslver

not sure. the RUU?

Here you go:
Applying November 2010 OTA to STOCK 2.2/FroYo rooted Incredible

Undereducated noob with rooted stock rom
I rooted my Incredible using Unrevoked so I could use free wifi tether and kept the stock rom. Unfortunately, because I am a noob and didn't know the ramifications or have all the info I needed (it's hard to filter and process all the info from searching the subject on Google), I deleted a couple of apks (before finding info saying to move them) in my attempt to eliminate some bloatware. I got nervous about it and stopped before deleting much, but don't remember which apks I did delete (I did a manual update at 4am while very tired). Now Verizon has pushed the Nov OTA to my phone and I have been pushing "Install Later" since. Think I still have s-off.
Can I allow the phone to do the update? I really don't care about retaining root or not, and can uninstall the wifi tether, superuser, etc, do the update and wait for Unrevoked to catch up so I can reroot (if necessary?) and reinstall wifi tether later. I have also seen that the RUU is out there, but as I understand, it wipes the phone and I'd really like to avoid that. I have seen the instructions posted earlier in the thread about "Installing OTA to rooted Android" but am lost when reading them. Plus the instructions and info I gathered when researching rooting my phone are being held hostage by my Chrome bookmarks (had to quit using Chrome, but that's another story).

WARNING - Do not use Visionary to permanent root your G2/DZ - high brick risk!

Hi !
I would like to warn everybody that the use of the permanent root option of visionary can lead to an unrecoverable brick!
Lately we are facing an increasing number of bricked phones that have been created by an attempt to permanent root the G2 (or Desire Z) using visionary.
While there is still cure for Desire Z phones (even if it is a complicated procedure) there are certain conditions for the G2 where nothing can be done to rescue the phone.
These are the conditions:
- the phone is S-ON and not SuperCID
- the hboot and the recovery are still stock
- the main software version is 1.22
When visionary corrupts the system partition (which it does some times) the phone can not boot anymore. And as there is no original stock rom (PC10IMG.zip) for the G2 that has software version 1.22 or higher the stock rom can not be installed from hboot.
And with the stock recovery there is also no chance to cure the system partition or change the main version in the misc partition.
But even if the brick can be cured for other phones (Desire Z, Desire HD) this is totally unnecessary because the phones can be rooted and freed by methods that do not have any risk at all (even if you do some steps wrong).
The method that I highly recommend to use is the one described on the XDA-wiki at http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD.
This method is constantly maintained and is the most up to date method.
If you really are not able or willing to use adb I would recommend the method described by ianmcquinn in the thread "[GUIDE] Permanent Root with Visionary/gfree (No ADB Required)" at http://forum.xda-developers.com/showthread.php?t=928160
It is less up to date but it uses visionary only to gain temporary root and it uses scripts for the necessary commands so that the risk of bricking the phone by typos in important commands is minimized.
Scotty2 and I (and a lot of other people) tried our best to make the rooting process as easy and risk less as possible and therefore it is very frustrating to see people who bricked their phones by using an unnecessary, outdated and risky method.
Thanks and have fun - Guhl
Update 05/15/2011:
Since football dropped the new gingerbread T-Mobile ROM (see http://forum.xda-developers.com/showthread.php?t=1074391) a G2 bricked by visionary can be cured. (which is a complicated procedure of course)

I think this is/should already stickied however no one seems to read stickies... Thanks for posting the warning again though.
Sent from my HTC Vision using XDA App

On my first G2 I used the visionary method and it messed up after about 2 weeks.
It wouldn't connect to the wireless network.
On my second G2 I used the gfree/rage method and, it has worked just fine.
I'm sure with all the visionary problems people are having, it probably had something to do with mine going bad.

I am waiting on an insurance replacement G2, glad I found this. I rooted mine the very first method that was posted. So does Visionary have a checkbox in the app or something to permanent root? I was using the first release of it.
:edit Just got my G2 from UPS at 1:20, and now at 1:50 I am already flashing CM7 Visionary is great, glad I saw not to do Perm Root attempt though haha

dumb? question
i rooted my g2 a few weeks back, installed the cyanogenmod 7(which seems solid btw) & honestly dont remember the method i used (it took multiple tries over multiple posts/guides/websites) but i recall visionary was involved at some point.
anyhow should i be worried about this thing becoming useless? should i be reinstalling/uninstalling something? are there any precautions i should be taking? is there a way to tell what method i used?
sorry if im cluttering this thread up, i really try not to post if possible(searching usually answers my dumb questions) THANKS! tho

If you're already rooted you should be good. The method that uses VISIONary/Gfree was posted in January, the latest thing that said it could cause any problems was an update on December 23rd, and from what I understand is that you'd have to downgrade a Desire Z... Didn't say anything about a G2. I'm sitting here waiting for UPS then I'll be doing this.

hmm ok, thanks, ill continue to slowly set it up for use than & keep an eye out for additional posts/info on the subject. i sure would hate to doorstop the thing before even using it.
thanks again for the reply

The only issue I've encountered with the way I did was that it says phone number unknown. Quick xda search found you go into Call settings, additional settings, and you can set the phone number in there

Well, I used the Visionary + gfree way to permanent root today, and it went smoothly, on the 1st try, no problems, as of yet. I ran root check and noticed that busybox isn't installed. Is it supposed to be? It was when I was using temp root. Is it ok, to install busybox from the app from the Market?

I got busy box through titanium backup "problems" button

Hi Guhl, I decided to be safe and follow your more highly recommended method to rooting my tmobile g2. This is my first time rooting a phone, the problem is I have a mac... I'm not sure it will work the same way since I don't have a pc... Do you know someway around this? Or some other way I can root my phone on my mac...
Thank you!

one2345shutup said:
Hi Guhl, I decided to be safe and follow your more highly recommended method to rooting my tmobile g2. This is my first time rooting a phone, the problem is I have a mac... I'm not sure it will work the same way since I don't have a pc... Do you know someway around this? Or some other way I can root my phone on my mac...
Click to expand...
Click to collapse
It should be no problem to root your phone on a Mac. The guide to setting up adb in my signature has a section on how to do so on a Mac.

I perm rooted with visionary method the day it came out (I think this was November or October?). Was on cm 6 and now been on cm 7 for a while. No issues at all. Guess I was lucky or people are doing it without being careful.

My friend's G2 seems to be bricked under these conditions. Failed Visionary root. He's counting on me to fix it.
The recovery is stock and it has S-ON. How can I check the version?

Electrodeath0 said:
How can I check the version?
Click to expand...
Click to collapse
You can't.
Just try to install the 1.19 PC10IMG.zip using hboot and you will see. If it installs you'r good if it tells you that you version is to high you are 1.22
Sent from my HTC Vision using XDA App

Whats up everyone?
OK real quick because this has had a little more insight to my situation than what i have been able to find. a guy called me up yesterday and wanted to know if i could root his g2. well apparently.... he attempted to do this on his own and used visionary and messed up his phone. bootscreen heaven. stuck on htc.
Hboot. 0.82.0
radio 26.03.02.26
SHIP S- ON
I have no control over adb.... says device is offline but at least recognized. and shows devid. is this phone a lost cause or can someone toss me a bone without telling me to read this and go here or there?
i have been searching since 5pm yesterday and it is now 1030am.
I have been able to load an update through the stock recovery and it shows that it went well. when it reboots to the screen with the grean circle arrows over the phone, it doesnt seem to take enought time to be loading image or other software. and when its done and reboots, its still stuck on htc screen.
any help would be greatly appreciated and sorry if i cluttered up this thread.
RELEVANCE::::: Visionary
SErooted,
Xperia X10
2.2 Xperia BLISS
2gig data2sd
998mhz
sysctl
2780 Quad

Wish i would have read this 3 hours ago.Tried to perm-root with vision bout 4 months ago and didnt brick, But 3 hours ago tried it again and i semi bricked/bricked it?
This blows i already miss my android .This is definitley a FML post
FMLLLLL!
well new g2x or just a New G2 here i come

I agree with this thread but back then there was only one root tool for the HTC Desire Z or G2 persay. If there is another tool I am unwilling to unroot and reroot again if possible. But I agree that Visionary++ increases the chances of a bricked phone with a percent of about 55%

Rooting a new G2
wrong post, mods please delete

I AM VS4 said:
I agree with this thread but back then there was only one root tool for the HTC Desire Z or G2 persay. If there is another tool I am unwilling to unroot and reroot again if possible. But I agree that Visionary++ increases the chances of a bricked phone with a percent of about 55%
Click to expand...
Click to collapse
If you used Visionary, and it worked, then you don't need to worry about unrooting and rooting again. If there were going to be any problems, it would have happened as you were rooting. If you didn't run gfree, and are not Super-CID, S-Off, then you might want to do that (you still can). But otherwise, you are good to go.

[Q] Updating while in in-between rooted state

Allow me to explain my vague topic.
My son and I both have a droid pro, and are both running update 3.8.7
However, both of our phones were rooted before the update came and simply let it update.
After it got updated I noticed I was not rooted anymore. And z4root would not unroot my phone, or root it anymore.
Basically it was in sort of an in-between state, between rooted and unrooted.
The way I had to fix mine was by running the 2.2.6 (or whatever it was )sbf I had found on TBH, and from there going through the update progress.
Problem with that was that I had to set it back to factory settings.
So, my son's phone is still in that in-between state. Does anyone here know if it will pose a problem when this new gingerbread update hits his phone?
Will I be forced to do a factory reset with a previous sbf in order to be able to do it without it bricking?

I can't speak from personal experience, but others here have strongly suggested unrooting before update to prevent problems like what you described. As for the latest update, there are not really any reports yet on how it has gone for rooted users yet.

Before the last 3.8.7 updated, my phone was rooted with z4root and I had some unimportant apps frozen, nothing that is really crucial. I went ahead with the update (using the update.zip) which worked just fine. Yes, z4root is a bit confused of what is going on but I would not worry about it - I guess it is just logging events and thinks that because u havent unrooted it thru the program, it must still be rooted. The update removes the root anyways .. but I went ahead to unroot it with aroot again which worked like a charm on 3.8.7. At the moment, I am going to updating to Gingerbread also using an update.zip and I can give you a detailed report on how things went in a little bit ...

tnt118 said:
I can't speak from personal experience, but others here have strongly suggested unrooting before update to prevent problems like what you described. As for the latest update, there are not really any reports yet on how it has gone for rooted users yet.
Click to expand...
Click to collapse
This.
You might be able to go through just fine without flashing the SBF, but it's always a good idea to unroot/unfreeze apps and be stock for an update. Always.

Not always.
After the update from 2.26 to 2.63 (cant remember?) I had rooted my phone with z4root and froze some unimportant bloat ware, I didnt touch any programs that I deemed important for the system. I then proceeded to update to 3.8.7 without unrooting or unfreezing apps! It worked fine. After this, the system was unrooted again, I rooted again with aRoot without any problems.Now, I upgraded to Gingerbread, also coming from being rooted. The individual updates remove the rooting and you are back at point zero and, as long as you dont have any important system utilities frozen, it will work absolutely fine.

vivid22 said:
Before the last 3.8.7 updated, my phone was rooted with z4root and I had some unimportant apps frozen, nothing that is really crucial. I went ahead with the update (using the update.zip) which worked just fine. Yes, z4root is a bit confused of what is going on but I would not worry about it - I guess it is just logging events and thinks that because u havent unrooted it thru the program, it must still be rooted. The update removes the root anyways .. but I went ahead to unroot it with aroot again which worked like a charm on 3.8.7. At the moment, I am going to updating to Gingerbread also using an update.zip and I can give you a detailed report on how things went in a little bit ...
Click to expand...
Click to collapse
Interesting. Well if the root has been removed then there is no problem.
My son has a lot less problems then I do so I never had to freeze any apps. Meaning I basically never had to root his phone to begin with. So I may just get away with doing nothing then.
I mean I had rooted his phone on the previous system, on 3.8.7 it never worked with z4root so I'm guessing it's not rooted at this point.
I'll try to double check
As for my own phone, I will need to keep an eye on how to after the new update. I have serious battery problems that I blame on useless background processes.
I'll just tell him to go ahead and run it, if it ever comes to us that is.
Thanks guys

That is true, but z4root is just mistaken in a sense that it is confused and thinks its still rooted while its actually not ... Unless you click unroot in z4root, it will always assume its still rooted. z4root will not work in the 3.8.7 version as its not compatible. You need to use aRoot for that. And I can confirm that all updates work, even when the phone is left rooted before the update! Every update automatically unroots (locks) the phone again anyways.

Ok.
I just found the update on droidforums and went ahead and installed on my phone because I couldn't wait for Verizon
Later on ill do my sons phone as well. Im sure it will go well so ill report back to help ease the mind of others.

yeah so it wasnt a problem. I ran the same update.zip file i found and my sons phone is running nicely.

vivid22 said:
Not always.
After the update from 2.26 to 2.63 (cant remember?) I had rooted my phone with z4root and froze some unimportant bloat ware, I didnt touch any programs that I deemed important for the system. I then proceeded to update to 3.8.7 without unrooting or unfreezing apps! It worked fine. After this, the system was unrooted again, I rooted again with aRoot without any problems.Now, I upgraded to Gingerbread, also coming from being rooted. The individual updates remove the rooting and you are back at point zero and, as long as you dont have any important system utilities frozen, it will work absolutely fine.
Click to expand...
Click to collapse
It may work just fine, and it may even work fine most of the time, but it's still a good idea to unroot before installing a stock update. A lot of issues can potentially come up. Unrooting doesn't hurt anything since the updates break root anyway. It's just a good precaution. A lot of people had major issues with the last 2.2 update when they installed it without unrooting first.
It looks like all is well on updating with the Gingerbread release. But better than safe than sorry I say.