- 10-16-2011, 02:34 PM
Thread Author #1
Been researching root for 2.3.4 for hours now
So I got my DInc 2 early September. I recently heard about rooting and Ive been looking into it for a couple hours now I found something on a temporary root but I got lost at the third step. I jailbroke my iphone before no hassle; this is soo much different. I guess I would just like a confirmation if its possible to do it on my phone yet, or if someone can share a thread that would help me out. Im new and dont understand some of the terms. Thank you
- 10-16-2011, 04:14 PM #2
It is possible once you downgrade your hboot .98 per the instructions in the development thread at xda. Then just follow the instructions to root 2.3.3. I will post a link later when I get to my laptop.
- 10-16-2011, 04:25 PM #3
- 10-16-2011, 04:50 PM #4
Re: Been researching root for 2.3.4 for hours now
Sorry for being a total noob, but ive been trying for hours to figure out how to do the XDA downgrade that is on their forum...but i have no idea what im doing...when it comes to it i am lost....is there anyone out here who can help a total noob and put the instructions into total vanilla noob language? or even post a youtube video on how to do this? THANK YOU!!!!!
Peeing on iPhone Since 2009 - 10-16-2011, 07:00 PM #5
Re: Been researching root for 2.3.4 for hours now
I am going to try. I might break this into multiple replies and might not get them all up tonight. I will assume you are in Windows 7 for all of this! I did use an Ubuntu Live CD to do the s-off procedure, but I think there is revolutionary instructions for Windows.
(1) First enable USB debugging on your phone by going to Settings->Applications->Development. Then turn off fastboot by going to Settings->Power (this is different than the fastboot mode choice once in recovery, which is used with the fastboot.exe that is part of the Android SDK.)
(2) Next install the HTC USB Driver for the Droid Incredible 2. You can find the download link in the XDA downgrade thread at
(3) Install the Android SDK, which will include ADB and Fastboot. You can find the instructions and the download link here:
You can skip the USB driver install because you have what you need from Step (2). Fastboot is in the platform tools folder. I just moved adb.exe and adbwinapi.dll from the tools folder to the platform tools folder so they are in the same location as fastboot. I also place any files I am flashing to the phone, etc in that same folder. It just makes is easier to change to that folder at the command prompt and execute commands from there. (The easy way to open the folder at the command prompt in Windows 7 is to hold down shift and right click the folder. You will get a command window option.)
At this point you should have a C:\android-sdk-windows folder and the necessary files under it. If you have trouble to here, I don't think you should go any further.
As an alternative to step (3), and easier, is to download attn1's kit from . It contains the files necessary to run adb and fastboot without installing the Android SDK. The key is to put all of the files from his kit under .\tools\win in the same folder as the files in the root folder of his kit (namely misc_version, zergRush, etc). Put them in c:\adb would be my suggestion.
Assuming you did the paragraph above, which I recommend. Do the following:
(4) Open the command prompt and change to c:\adb. Connect your phone via USB as charge only. You should have USB debugging enabled per the above. Manually execute the commands from attn1's downgrade thread. Namely:
adb shell rm -r /data/local/tmp/*
adb push zergRush /data/local/tmp/zergRush
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/zergRush
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
fastboot reboot
At this point, you should have downgraded your hboot and can gain s-off.
(5) Attn1's thread also contains the link to gaining s-off and installing cwm (clockworkmod recovery) using Revolutionary:
You should be able to run this per the instructions there. This will set security off and install the clockwordmod recovery. You can follow this thread for more thorough instructions:
At this point you are downgraded with s-off and clockworkdmod installed. You now have everything you need to flash ROMs, etc.
(6) You should read about flashing ROMs, etc here:
There are other resources if you search.
(7) You get into recovery by turning off your phone. Then hold volume down and power on. Then you use the volume keys to move the cursor up and down one in the bootloader. Use the power button to choose options. The same goes for once you are in recovery. You should see an option called "recovery" once booted into the bootloader. This will run CWM. The first thing you should do is do a nandroid backup in the backup and recovery menu. Make sure you have a least 1 GB free on your SD-card (I keep 4 GB for experimenting with ROMs). This will backup your stock ROM setup.
(8) Now you can reboot, download ROMs to your SD card and flash them as instructed. Good luck.Last edited by tack; 10-16-2011 at 07:19 PM.
Thanked by 5: - 10-16-2011, 09:04 PM #6
Re: Been researching root for 2.3.4 for hours now
umm I downloaded something from xda that had a whole command prompt thing in and I clicked it and it just rooted my phone by itself I think will see what happened
edit: it literally downgraded my whole op system to 2.3.3!!!! ima see if I can remember link to poist my phones rooted!
rdit 2 this is link I used and I clicked on the link that included scripts and tools theres a command prompt it literally does everything for you.
Last edited by gir007; 10-16-2011 at 09:32 PM.
- 10-16-2011, 09:42 PM #7
- 10-17-2011, 05:47 AM #8
Same link I put above, but I wanted to add more color because he asked for a more in depth explanation. Attn1 did everyone a favor for sure with that tool.
Sometimes you can get flamed at XDA for asking basic questions. Everyone has to learn, and I wish some people were not so offensive when new users ask for help. Overall I think XDA is a great site with many great members. - 10-17-2011, 08:34 AM #9
Re: Been researching root for 2.3.4 for hours now
I was wondering why it was similar but by far yours was the best description I have seen even I was able to understand yours. but I ended up accidently clicking that commnd link I thought wasw just command line shortcut or something lol. but watever extra file was on there it went back to 2.3.3 so my question for you tack does that happen regardless or was it that file? cuz I thought it was just a boot loader.
- 10-17-2011, 09:42 AM #10
- 10-17-2011, 10:27 AM #11
- 10-17-2011, 11:43 AM #12
Re: Been researching root for 2.3.4 for hours now
In terms of vanilla ROMs, if you like Sense I had good luck with RMK's Gingersense and it is patched to the newest release. I use Skyraider Zeus, which is a Sense 2.1/3.0 hybrid that works great. They are both good if you want good, stock international GSM access.
I really like CM7 for non-international use. Virtuous Unity is a nice Sense 3.0 ROM, and a lot of people like Miui. - 10-17-2011, 04:05 PM #13
- 10-19-2011, 07:38 AM #14
Re: Been researching root for 2.3.4 for hours now
Heys guys, this thread has been a huge help so far, but I am having a problem. I downloaded the kit from the XDA site, extracted the zip, and opened up the abd command file, and the command opens and then closes immediately.....I dont know what the issue would be. I even rebooted my PC, deleted the zip. and extracted folders, redownloaded and it still is doing it. Any suggestions would be hugely appriciated!!
- 10-19-2011, 05:37 PM #15
Re: Been researching root for 2.3.4 for hours now
@ mr. fresh.
i've been reading three threads about this and while i have not done it yet, i thought i might mention a possibility.
Put all downloaded files in one folder.
run .cmd as administrator.
another thread beside this and xda
MAYBE?
you were great in concert when i saw you in rochester NY back in the late 80's. - 10-19-2011, 06:05 PM #16
- 10-20-2011, 02:15 AM #17
- 10-20-2011, 02:20 AM #18
- 10-20-2011, 06:42 AM #19
Re: Been researching root for 2.3.4 for hours now
You need to run the Windows cmd prompt as admin, not just the script files attached. Then manually from the terminal execute the scripts. Or you could execute the adb commands manually as I indicated in the thread.
- 10-20-2011, 06:58 AM #20
- 10-20-2011, 07:42 AM #21
Re: Been researching root for 2.3.4 for hours now
I have run the command prompt as Admin....but it just opens and closes out immediately....actually running the script hasnt even been an option for me yet since the command prompt will not stay open.
Thanked by: - 10-20-2011, 07:43 AM #22
- 10-20-2011, 09:10 AM #23
Re: Been researching root for 2.3.4 for hours now
Alright, I have now also tried the alternate approach and downloaded the SDK file. I have followed all of the instructions to the best of my ability and I have having the same results that I had previously with the downgrade kit approach. When I run the adb as admin, it opens, scrolls very quickly, and closes immediately. I am completely confused why I can have all the neccessary steps complete, and be so close, and the command prompt will not stay open. I am really out of options for any assistance with this other than this thread. XDA wont even let me ask any questions because of it being a development thread and I am a "noob" because I just registered with them. Could someone please give me some help, or as asked previously by victoryore, a youtube walk-through would be amazing. Thank you in advance for all of your help!
- 10-20-2011, 11:30 AM #24
Re: Been researching root for 2.3.4 for hours now
Run the command prompt, not adb.exe. Go to run in the start menu and input "cmd". You will get a persistent terminal/command prompt window. Change to the folder where you have adb and the files from the kit. Then execute the commands. I believe what you are doing is trying to execute adb from Windows directly. That will cause it to open the command window and close after execution rather than taking you back to the prompt.
Thanked by: - 10-20-2011, 11:55 AM #25



Reply



































