Related
Hi there everyone,
I want to root my Desire HD, but I don't want to install any custom roms, radios, etc. I only want to root my HD so I can install apps that require root. I see no advantage in installing any custom ROMs, so I want to leave that alone.
What's the best way to go about this? I've found this guide: http://forum.xda-developers.com/showthread.php?t=834427. Do I need to do anything else, except what is in this guide? I'm terrified of bricking my phone!
Could I brick my device if I made a mistake with the above guide, or S-OFF?
Thanks in advance,
Alex
Sorry for the question (no doubt it's been asked before), I've rooted my old HTC Hero before, found that easy, but this I'm confused!
Hi there. I'm actually quite a noob at all this since rooting is all new to me but seems you and I went after similar threads because I also read that guide to rooting the DHD at first. But after some further reading I discovered this is actually a much more difficult method of rooting (maybe because it's older?).
It will really, really help to look in this thread: http://forum.xda-developers.com/showthread.php?t=846248 as it explains so much and has many useful links.
But in answer to your question read this guide - http://forum.xda-developers.com/showthread.php?t=841076 A much easier method of rooting =)
Good luck.
nikmesh said:
Hi there. I'm actually quite a noob at all this since rooting is all new to me but seems you and I went after similar threads because I also read that guide to rooting the DHD at first. But after some further reading I discovered this is actually a much more difficult method of rooting (maybe because it's older?).
It will really, really help to look in this thread: http://forum.xda-developers.com/showthread.php?t=846248 as it explains so much and has many useful links.
But in answer to your question read this guide - http://forum.xda-developers.com/showthread.php?t=841076 A much easier method of rooting =)
Good luck.
Click to expand...
Click to collapse
Thanks for that link! Looks a lot easier haha!
Detailed description:
1) Download Paul's Visionary+ tool
1.1) Click here to download http://android.modaco.com/content/ht...ne-click-root/ or download it from here http://forum.xda-developers.com/atta...3&d=1290501865
1.2) Install Visionary+ on Your DHD
1.3) Run it, enable "Set system r/w after root
1.4) Click "Temproot Now!" - Wait until it's finished
1.5) Click Attempt Permroot Now!
1.6) DHD automatically reboot's
To test that everything went fine download from market application "terminal emulator"
run it, type su
If You get after that sign # it mean's that everything went fine.
Click to expand...
Click to collapse
After I've ran that step - do I have permroot and I don't need to do anything else? I only want root, not custom ROM's.
I'm scared of doing the permroot, sounds like I'll break my phone if I even attempt it! Is there any way to ensure it will work?
Yeh you will be perma rooted if you follow the steps. About ensuring it will work, this is something I am now looking into myself. I'm getting the impression that it's possible to create a copy of the stock rom even without the perma root and using that to do a recovery in the event of a root failure. Though I would have thought perma root would have been needed to do a recovery in the first place....
I've got a thread below yours where I'm still trying to get a clear answer as to how to do all that. If I find out I'll let u know =P
nikmesh said:
Yeh you will be perma rooted if you follow the steps. About ensuring it will work, this is something I am now looking into myself. I'm getting the impression that it's possible to create a copy of the stock rom even without the perma root and using that to do a recovery in the event of a root failure. Though I would have thought perma root would have been needed to do a recovery in the first place....
I've got a thread below yours where I'm still trying to get a clear answer as to how to do all that. If I find out I'll let u know =P
Click to expand...
Click to collapse
By "if you follow the steps" - do you mean I only have to follow step 1 for perm root? Or more than that?
Sorry for all the questions, I really do appreciate your help, thanks!
And also - if it fails, the stock WWE RUU can be flashed to restore the phone, can't it?
EDIT: Followed step one, restarted device and everything - perm root stays. Thanks for all your help mate!
Detailed description:
1) Download Paul's Visionary+ tool
1.1) Click here to download http://android.modaco.com/content/ht...ne-click-root/ or download it from here http://forum.xda-developers.com/atta...3&d=1290501865
1.2) Install Visionary+ on Your DHD
1.3) Run it, enable "Set system r/w after root
1.4) Click "Temproot Now!" - Wait until it's finished
1.5) Click Attempt Permroot Now!
1.6) DHD automatically reboot's
To test that everything went fine download from market application "terminal emulator"
run it, type su
If You get after that sign # it mean's that everything went fine.
Click to expand...
Click to collapse
Go all way through these steps from 1.1 to 1.6. Once you've done 1.6 your phone should be rooted. Just download the terminal emulator from the market and do that last thing that is mentioned to test the perma rooting. If that works then your good.
Oh just so you know the temp root option in Visionary is apparently completely safe and won't harm nothing because it makes no changes to the system partition.
Not sure about the WWE RUU. I'm not sure it will be compatible with your current ROM (Only thing I do know is that if it's older then your current it won't work). Don't know how to flash it either tbh, that's something I ain't found out yet =P
Hello there fellow Glacier owners.
Let me start off by saying I have rooted 2 Glaciers very recently, and I am very familiar with the process. One of them was swapped at the store because I had one of the Taiwanese screens, and it was driving me nuts. I have been trying to root the new one.
I've gone through the gfree, adb, and Visionary+ methods already, and now an issue has cropped up.
Now, when I run Visionary, pop open the terminal, and type 'su' I get an 'unknown user root' error.
When I try to use the adb/gfree method and run 'rage', I now get a 'rage: applet not found' error.
During my previous attempt, I did not get this error. I have tried a reset to factory through stock hboot, I have tried loading the 2.2.1 PD15IMG.zip, through stock hboot (didn't help, wasn't expecting it to). I've even tried switching out and formatting mSD cards on the off chance it might help.
If anyone has any advice or help they can offer me, I would greatly appreciate it.
Thanks
Any way you can post a video of your step by step? I've always used grankin's guide and I've never had an issue, not once, on 6 HTC Glaciers.
Thus far, I've only seen a few reasons why people can't root their phone:
- They aren't on 2.2.1
- They didn't put files in the correct location/follow directions to the T
I don't think I've ever seen a legit, "your device is defective" post, but it's been suggested.
I use visionaryplus.r14.apk each time and my employee has rooted a handful of HTC Glaciers using the same.
I think a video would really help expose any possible oversights. It's either your steps or the device is just "bad" and I'm thinking video footage would help reveal which it is.
Here is a link to my video using the Visionary+ method. I can upload a video for the adb if you want as well.
www.youtube.com/watch?v=qb3HIvXiF74
Replace DOT with .
I should also note that I was able to run the 'su' command at one point successfully, but this is no longer the case.
Awesome, great vid and thanks for that. Can you get a screen shot (or pic) of your About Phone > Software Information?
Thanks! Here is the requested pic...
I should note that this phone came with 2.2.1, where the other two I have rooted did not.
Awesome, thanks for the quick pic. I've had six Glaciers, two of which came with 2.2.1 pre-installed, the rest came with 2.2 and then 2.2.1 came down once I checked-in. So that alone (2.2.1 pre-installed) shouldn't be an issue.
The difficult part is, there have been multiple "processes" attempted on this device, so I can't attest to the state of the device/ROM. Is this attempt with Visionary coming from a clean install/factory reset? I'd sort of like to "take it back to basics" and have a factory reset device THEN try ONLY the Visionary method.
I saw someone mention that a dev though there could be a hardware issue causing this (I can't remember which thread or which dev mentioned it), but it was only speculative.
It seems pretty clear you know what you're doing and you're quick AND we're not even to the .sh portion (where a lot of people end up with /root/root directories).
Keep me posted...
If you could, please supply me with some detailed factory reset instructions.
I want to make sure we are troubleshooting this appropriately, and I may not be wiping it correctly.
Please let me know.
Thanks.
It should just be Menu > Settings > SD & phone storage > Factory data reset...
Ok, it's running through now.
What would my next step be?
EDIT: Wipe finished. I installed Visionary, ran Temproot, still get the 'su: unknown user root' error.
May be heading to my local T-Mobile to replace the device.
K, so once it's finished you'll get to the TMO setup wizard where you enter your Google account info, etc. Once you get through that and get to the home screen, stop and don't do anything else. That's our home base.
Let me know once you get to the home screen for the first time after factory reset and we'll go from there...
I appreciate your patience and willingness to go through everything in baby steps.
Youch, k, there we go. That's exactly what the next step would've been and it sounds like you're truly not missing anything.
Does anyone else out there have anything to offer? I think you're probably best at cutting your losses and just getting another device. It really should be a very simple process, as you've seen before.
Keep us posted on the new device!
Woops, went a little too far then. I'll re-wipe.
What's the next step?
EDIT: Didn't do this, nevermind.
Ok, I got the new phone. Attempted to root through Visionary, everything looked good, but then I did not have root. Here is what I did...
From factory, out of the box (confirmed 2.2.1), ran Visionary - Temproot.
In terminal, 'su' works properly.
Ran root.sh
Appeared to work, rebooted the phone manually, S was still on.
Ran Visionary Temproot.
Ran Visionary Permroot.
S is still on.
Are there other steps I should take? Or did I perhaps do something wrong.
Please let me know.
Ok, unless there's some silly oversight, I think we might have a different issue here. Anything 'special' about these newer HTC Glaciers? All the specs you posted look identical the devices I've had from November, December, etc.
I hope there's no issue with me posting a link to Visionary.
Visionary R14:
http://deancasey.net/android/apps/visionaryplus.r14.apk
Just for giggles, can you try that APK? I know you said you have the same version, but there's obviously some difference between what you have (hardware, software, etc.) Other than that, it's either process or device. You seem pretty knowledgeable and it's not some silly mistake like not finding the .sh script.
Has anyone else tried to root using Visionary R14 on a newly-acquired MT4G? I'm just wondering if ANYTHING is different about the newer devices.
Still not working.
Should I try the gfree method? I will also note, that the last 2 I did gave me a real hard time rooting them. I bounced around a bunch of threads/methods before I got it to work, and I really don't recall what I had to do.
Yeah, it's just something that's really weird to me. I've been a "tech," professionally, for nearly 15 years. I worked as a Project Manager for a software company for 7 years, so I was solely responsible for testing our new releases. I also did all the 'lite' work like the database patches, installer scripts, etc.
Working closely with a smart developer, you start to get really good at testing and removing your own opinions from the loop. So there's pretty much always a finite reason why something isn't working as expected.
So that side of me wants to know what the variable is. Six of these devices and I've rooted them all without issue, using that .apk and Grankin's .sh script. So it's like, ok, I know this works. I've seen it not work for people who weren't on 2.2.1, who didn't follow the directions, etc. It looks like we can rule out the user with you so now it's a matter of what is unique about your device(s)?
Try the gfree method and report back, but I'd definitely like to see if anyone smarter than you and I has any input on what could be different about the newer devices you have.
Ok, I got the new phone. Attempted to root through Visionary, everything looked good, but then I did not have root. Here is what I did...
From factory, out of the box (confirmed 2.2.1), ran Visionary - Temproot.
In terminal, 'su' works properly.
Ran root.sh
Appeared to work, rebooted the phone manually, S was still on.
Ran Visionary Temproot.
Ran Visionary Permroot.
S is still on.
Are there other steps I should take? Or did I perhaps do something wrong.
Please let me know.
Click to expand...
Click to collapse
I was under the impression that you had to turn S off before you can perm-root this device. The way I did it is here: http://forum.xda-developers.com/showthread.php?t=858996
I used only Gfree and Visionary (both can be obtained in the link). No separate rage exploit. If I follow you correctly, I don't see where you used gfree after temp-rooting, which is what actually turns S on or off from my understanding. Visionary is what puts the binaries in place and executes the exploit to do so. I only used these two tools and I have S off with perm-root verified. Try it this way:
1. Fresh MT4G, stock bootloader, recovery, etc.
2. Ensure USB debugging is on
3. Install a terminal emulator
4. Install Visionary
5. Temp-root with Visionary
6. Push gfree to your phone as described in the link above using adb
7. Open your terminal and run gfree as described in the link above
8. Reboot
9. Run Visionary again, but this time ensure you check the box to have it mount system R/W after temp-root
10. Temp-root through Visionary
11. With Visionary still open, attempt to perm-root the device; it should reboot
These are the steps that I remember following and it worked perfectly. The key was using gfree to turn S off in order to get it to stick, then going back to Visionary and rooting. I think it is possible to get perm-root with the engineering bootloader and not really turning S off, but I am not %100 sure about the new stock bootloaders and having to turn S off or not. But, this method worked on more than one MT4G on which I tried it. Hope it helps.
The method outlined in Grankin's post gets you S-Off.
totalentropy is getting stuck before we can even get to the next steps. He's just trying to get Temp Root and then get su. You won't have S-Off at this point in the process and you don't need to have it off at this point. You won't get S-Off until you run the root.sh script...
*Crappy iPod Touch camera
total, have you tried the 'Alternative Root Process' outlined in Grankin's post? He wants you to remove the Visionary and Super User apps before proceeding with that method.
kmdub, that didn't work for me.
schlongwoodian, I did try that, and it seemed to be working. After the last rage, it soft reboots to the MyTouch logo, 5 seconds later flashes back to the MyTouch logo, then boots normally. I checked S after that, and it is still on. This is the same behavior that my other two exhibited when I was trying to root them.
Here is some additional info that may be helpful.
For all 3 Glaciers, I could not push su or Superuser.apk to the phone normally. I could only push them right when the phone booted with the USB plugged in, right after the USB debugging mode message appears. Any other time and I get access denied.
When I run gfree, with the -f switch, I get an error with input file, sometime a different error that I cannot remember off the top of my head. On one Glacier, I could run gfree with the -s off switch, which did work. I tried that on this current one, and it did not help.
For all 3 Glaciers, I could not push su or Superuser.apk to the phone normally.
Click to expand...
Click to collapse
Push via? ADB? Why is Superuser.apk being pushed to the phone? That's part of another root process I'm guessing? That's not part of Grankin's root process. Now, the Superuser.apk does get installed (Visionary), but never does Superuser.apk have to be manually copied over.
Those are good points that you mentioned. Can you clarify if you pushed Superuser.apk to your phone earlier? The process should be:
- Factory reset or start with clean device
- Copy visionaryplus.r14.apk to your microSD card (I put mine in a folder named _appz)
- Copy Grankin's 'root' folder to the root of your microSD card
- Run Visionary to gain temp root
- Run Terminal and type su
It's interesting that you're getting the 'unknown user' error right when you type 'su' and you also have manually copied over a Superuser.apk. Can you start the process over again - factory reset - and do nothing once you boot the phone for the first time? Wait and don't copy a thing over, nada. Just wait and post back here. And make sure there truly is nothing on your microSD card - nothing that you've put there that is, not until we can start this over again.
I hope we're onto something...
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.
Hi!
So I was looking for a way to use AdFree and backup my device and came across This how to on how to root the desire Z. But once I pushed the first set of files to my device and ran the Terminal Emulator and closed it, it won't open again. So I'm kinda stuck there... . When I re-open the emulator, just as the how-to says, it will force close. But then when I try to open it for the second time, it wont open nad my system gets sllooowwww.... All I can do from there is restart the DZ and open the Emulator again from where I would start the procedure all over again...
Any suggestions?
Is there a recent step by step guide on how to root the DZ?
I dont need s-off, do I?
Thanks
AO
Device specs:
HTC Desire Z
Android 2.2.1
Kernel Version 2.6.32.21
Build Number 1.82.405.1
Same here.
You need to downgrade from 1.82 before you can root. I think there is a sticky that explains this.
Sent from my HTC Vision using XDA App
Indeed, for now you require the much older 1.32 firmware revision in order to root the phone... Or leave it on 1.82 and wait and see if people manage to root the new firmware as well...
that happened to me, but i was able to get around it by downloading a different Terminal Emulator from the android market.
xT4Z1N4TRx said:
that happened to me, but i was able to get around it by downloading a different Terminal Emulator from the android market.
Click to expand...
Click to collapse
And then you rooted your phone with or without downgrading?
What happens, if I dont downgrade? Does it "just" not work or is there a brick risk?
I just rooted a G2 earlier today, essentially a Desire Z, but with one file different to download. This is done entirely in adb and took me 10-15 minutes max. Known as the G-free method: Steps are located here. All links aside from the drivers for your phone to pc are alive. For the drivers for your PC to read through adb (if you don't already have them), you can download them through the Android SDK manager. For a brief guide on setting up ADB, go here.
This will root your phone, unlock sim, give you s-off, super-CID, and ClockworkMod Recovery 3.0.
As mentioned earlier, you will probably have to downgrade your phone's firmware. Check it in your phone's settings with the one required by the wiki before progressing. There are instructions on how to downgrade in there, but I didn't have to go through that step.
Once you're rooted, the first two apps you're gonna want to get are Rom Manager and Titanium backup. Good luck on not getting addicted to custom roms.
takram said:
I just rooted a G2 earlier today, essentially a Desire Z, but with one file different to download. This is done entirely in adb and took me 10-15 minutes max. Known as the G-free method: Steps are located here. .............
Click to expand...
Click to collapse
I've followed the same link as above on two different DesireZ's now and its worked perfectly, just read it a couple of times first, get all the files, check md5's and follow it step by step making sure you don't miss anything.
/Update: Rooting went fine. Updated this thread - maybe it helps if somebody wants to root his/her 2.3.3 DZ and is being overwhelmed by guides etc.
Hi there!
I finally decided to root my Stock 2.3.3 Desire Z - I've read a lot, but I'm still confused when it comes to certain steps of rooting. I just wanted to get "green light" by someone who certainly has more experience in rooting etc.
First I read this ADB guide to get familiar with it. I certainly didn't understand everything about it, but the basic stuff should be clear.
Next step is downgrading my phone. I want to use this guide as mentioned in the HTC Vision wiki.
Which raises the first question: What's with that post, which Desire Z users should read. I don't really see the connection to the guide I want to use - it's stated that one should replace psneuter with fre3vo in step 4. But which step 4? Little confused.
So which step is different to execute for me?
No step is different, the guide is up to date and can be used with every device stated in its headline.
Next steps should be clear.
So after downgrading I planned on sticking with the Vision wiki - seems that every step is described clearly, even for an ADB dummy.
If everything went well, I planned to flash the Virtuous Sense v2.0.0 which requires a "full wipe".
So it's nonsense to save application settings via titanium backup in the first place, because I want to set Virous 2.0.0 as backup-rom anyway? Are there files I should backup - besides contact info etc.?
Application settings can be restored if you stick to the downgrade guide, only system settings/stuff should not be restored.
And am I missing anything important? Are there other (better) ways of rooting my device?
No
Tiny, rather unimportant last question - is there a way to save my savegames to just load them later if needed? Since the "full wipe" wipes everything (?), I don't see how I could save them.
See above.
Looking forward to be enlightened!
Greetings!
Kueber said:
Hi there!
I finally decided to root my Stock 2.3.3 Desire Z - I've read a lot, but I'm still confused when it comes to certain steps of rooting. I just wanted to get "green light" by someone who certainly has more experience in rooting etc.
First I read this ADB guide to get familiar with it. I certainly didn't understand everything about it, but the basic stuff should be clear.
Next step is downgrading my phone. I want to use this guide as mentioned in the HTC Vision wiki.
Which raises the first question: What's with that post, which Desire Z users should read. I don't really see the connection to the guide I wan't to use - it's stated that one should replace psneuter with fre3vo in step 4. But which step 4? Little confused.
So which step is different to execute for me?
Next steps should be clear.
So after downgrading I planned on sticking with the Vision wiki - seems that every step is described clearly, even for an ADB dummy.
If everything went well, I planned to flash the Virtuous Sense v2.0.0 which requires a "full wipe".
So it's nonsense to save application settings via titanium backup in the first place, because I want to set Virous 2.0.0 as backup-rom anyway? Are there files I should backup - besides contact info etc.?
And am I missing anything important? Are there other (better) ways of rooting my device?
Tiny, rather unimportant last question - is there a way to save my savegames to just load them later if needed? Since the "full wipe" wipes everything (?), I don't see how I could save them.
Looking forward to be enlightened!
Greetings!
Click to expand...
Click to collapse
I followed the downgrading guide you linked to in order to downgrade from 2.3.3 and it worked perfectly for me (and many others, it seems). The guide uses fre3vo so I think you are safe to just follow the steps described in it.
I used SMS Backup & Restore and Angry Birds Backup free, both worked a treat. Other than that I restored everything from scratch.
It's probably a good idea to do a nandroid backup after rooting the stock froyo ROM but before flashing something else. Just in case.
Good luck
Yeah, and you probably should have posted this in Q&A
Eventually it would have been better, yup, but then I considered this thread more like a list of steps you want to go through to root your Desire Z 2.3.3 successfully - maybe it helps someone.
Anyway, thanks for your answer. I'll try that SMS Backup app.
Now I have to gather some informations about that "nandroid" backup - I've read it several times, but still I don't know what exactly it does / its benefits are.
If anyone would like to give a brief explanation, feel free!
Greetings
/edit: Well, a nandroid backup can be done with clockwork recovery, which installation is kinda part of the rooting process. There's one thing I don't understand yet - how to load that backup if it's needed?
Kueber said:
Now I have to gather some informations about that "nandroid" backup - I've read it several times, but still I don't know what exactly it does / its benefits are.
If anyone would like to give a brief explanation, feel free!
Greetings
/edit: Well, a nandroid backup can be done with clockwork recovery, which installation is kinda part of the rooting process. There's one thing I don't understand yet - how to load that backup if it's needed?
Click to expand...
Click to collapse
Part of the rooting process gives you a better recovery partition that you can boot into, where you can flash roms, backup/restore ROMs and has some other tools,this is independent of the ROM you flash and is a safety net when messing with your phone.
bombadier said:
Part of the rooting process gives you a better recovery partition that you can boot into, where you can flash roms, backup/restore ROMs and has some other tools,this is independent of the ROM you flash and is a safety net when messing with your phone.
Click to expand...
Click to collapse
So, essentially, as you already mentioned, that means I got safety tools that work independent. For example - if everything goes wrong and I have a copy of that nandroid backup somewhere, I could easily adb push that onto my sd card and flash it? Or has this backup to be on my sd card all the time, because in certain cases the sd-card is not mountable?
Just want to make sure that I understand what I'm doing..
Kueber said:
So, essentially, as you already mentioned, that means I got safety tools that work independent. For example - if everything goes wrong and I have a copy of that nandroid backup somewhere, I could easily adb push that onto my sd card and flash it? Or has this backup to be on my sd card all the time, because in certain cases the sd-card is not mountable?
Just want to make sure that I understand what I'm doing..
Click to expand...
Click to collapse
You don't have to have the nandroid backup on your SD card at all times. You can do a backup, copy it to your computer and keep it there if you need the space on your SD card for daily use. There is also the possibility to keep multiple backups of different ROMs if you wish to change UI more often.
Whatever your needs, you should at least keep one backup from a stable setup. If anything goes wrong you can copy it back to your SD card (if it is not already there), boot into recovery (volume down + power) and choose backup/restore and restore your backup. Everything will be exactly as it was when backing up - very convenient
Everything went fine, updated thread - maybe it helps someone.
Thanks again!
Good to hear it went well
Got full root access and all the way to step 5 on the Wiki and go to verify that it worked and I get the...
secu_flag = 1
CID = T-MOB010
SIMLOCK = 01
Please disregard.
For my DZ:
secu_flag = 0
CID = 11111111
SIMLOCK = 00
Sent from my HTC Vision using XDA App
which method do i follow to just root my Desire z.
I dont want to update h-boot, or install clockwork recovery.
My device has S-off with stock htc sense rom...i just want root
sandipbarik said:
which method do i follow to just root my Desire z.
I dont want to update h-boot, or install clockwork recovery.
My device has S-off with stock htc sense rom...i just want root
Click to expand...
Click to collapse
Just follow the xda Vision wiki.. read it attentively.
You'll see that you can just skip these steps.
Im using that method & rooted my DZ.
Sent from my HTC Vision using XDA App
look, I don't want to downgrade my system.
I want to root 2.3.3. is this possible ?
artur-x said:
look, I don't want to downgrade my system.
I want to root 2.3.3. is this possible ?
Click to expand...
Click to collapse
You can't root 2.3.3 directly. In order to root you need to first downgrade to 2.2 and then root. Afterwards you can choose to install a rooted 2.3.3 stock ROM, a custom ROM with 2.3.5 or 2.3.7 depending on what you choose. Or you can try out one of the ICS alphas.
Sendt fra min HTC Vision med Tapatalk
I have factory 2.3.3 in my desire z , is it possible to root it (downgrade and change to something new ) and not to lose my data and installed applications?
Zocca: You have to downgrade, but the downgrade guide contains a section to get Titanium Backup running, so you can backup your apps and data.
-Nipqer