Please do not PM me with questions about this guide! I don't have time to help everyone through it, create a thread in Q&A if you don't have 10 posts or post here, there are other people who have done this and can help you, and I will get to it if I can. PMs asking questions about this guide will be ignored. Thank you.
Fully stable root methods for all firmware versions (no bootloops on 6.01.605.05 firmware!)
Table of Contents
To quickly find a section, hit CTRL+F and type the letters in parentheses, then click "Next"
(IRO) Intro: Read first!
(HDV) HTCDEV Unlock
(TCR) Tacoroot
(DWG) Downgrade tool
(RVL) Revolutionary
(HSO) S-OFF with HTCDev unlock (second post)
(ASO) After S-OFF (second post)
INTRO(IRO)DISCLAIMER: I am not responsible for anything that happens to your device while following these instructions. I will try to help you through problems as much as I can, but I can't guarantee success, especially if you do not carefully read the instructions.
This is a comprehensive guide of all known and fully stable root/s-off methods, at this time, it covers just about all firmware versions out there. Most of these methods will require the Android SDK, so download that (Google it. A link for this really isn't necessary, and I'm sure many people could use practice googling things. ) and set it up (again, just google "android sdk," the download page even has tutorials). The downgrade methods no longer require the sdk, but it is still reccomended that you download it as it is a very useful tool. Don't forget to download the device drivers here (only neccessary on Windows) and set the PATH variable.
So, which downgrade method should you use? Most likely you will either have firmware version 5.x or 6.x, you can find out under Settings>About phone. If you are using 5.x, go to the Downgrade Tool section; if you have 6.x, go to the Tacoroot section. Both methods eventually lead to the Revolutionary section, HTCDev unlock is not reccomended and, honestly, completely pointless (read more below).
HTCDEV UNLOCK(HDV)Versions: All
HTCDev is HTC's "official" unlock, it will unlock the bootloader but leave S-ON. Don't do it. Seriously. It's a guaranteed voided warranty and pretty much a huge PITA (you can't flash radios and need to extract and separately flash ROM kernels), and s-off methods are completely stable and even relockable. That said, if for whatever reason you do wish to do this, just go to http://htcdev.com/bootloader/. If you want to obtain S-OFF at any time after using HTCDev unlock, see the second post.
Note: to flash ROMs when HTCDev unlocked, flash the ROM normally, then extract the boot.img from the rom.zip and boot into fastboot, then use the command "fastboot flash boot boot.img."
TACOROOT(TCR)Versions: 6.01.605.05 firmware
Tacoroot is a temp root method discovered by Justin Case that will allow those on the newer firmware to flash an older version and root with Revolutionary. Before you begin, download this zip containing all the files you'll need:
EDIT: Looking for the files? See this post.
Extract this zip to C:/Android. You can extract it somewhere else, just replace C:/Android with the path to the wherever you extracted it wherever it comes up. Now, connect your device to your computer with a USB cable, turn on USB Debugging under Settings>Apps>Development, and disable fastboot under Settings>Power. Make sure your phone is fully charged. Open a command prompt by opening the start menu, typing "cmd" and hitting enter. Type in everything that is in black text. Notes and extra instructions will be written in blue. It is reccomended that you copy/paste the code to avoid typos, to do this, copy by highlighting the line and hitting Ctrl+C as usual; to paste, go to your command prompt and click the small black icon in the upper left corner. A menu will pop up, go to Edit>Paste. Make sure you have not highlighted any spaces before or after the line or any of the blue text. Now, begin copying the code:
cd C:/Android
md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip Remove the space in the middle of the word radio before hitting enter, I don't know why it won't let me remove it. Result should be cea499f51b40055ffd118960e1e73255, if it isn't, redownload the miniadb zip.
md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip Result should be ea6b98be48210d7797e62362f49ff751
md5sums tacoroot.sh Result should be 6ec06d776feb212d8b2a55817eddf76d
md5sums misc_version Result should be 050f55d34ddbcc860efa5982491437de
adb devices Result should be your phone's serial number. If it isn't make sure drivers are properly installed and USB Debugging is enabled.
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
adb shell /data/local/tacoroot.sh --setup This will reboot your phone. When you get to a screen with a red exclamation mark, press VolUp+Power until you get to a menu, then press VolUp+VolDown+Power until the phone turns off. Once it is rebooted, continue.
adb shell /data/local/tacoroot.sh --root
adb wait-for-device Running the step before this will reboot your phone again, this time it will be bootlooping, meaning it will not boot fully and get stuck on the boot animation. Once your prompt comes back after this step, you're good to continue even though the phone isn't fully booted.
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 2.18.605.3
adb shell /data/local/tacoroot.sh --undo This will reboot your phone one more time, this time fully stable and will boot completely. Continue once fully booted.
adb reboot bootloader This will reboot your phone to a white screen with a few options. Once you are at this screen, continue with the instructions.
fastboot devices Result should be your phone's serial number, again.
fastboot getvar mainver The result should be 2.18.605.3. If it is not, something was not done correctly, you'll need to restart from the beginning.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip This will take a bit of time without giving any indication as to when it will be done, be patient and do not interrupt it.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip Same as the above, do not interrupt under any circumstances (unless you really wanted a phone-shaped paperweight )
fastboot reboot
That's the end of the codes, you should be fully booted into the now downgraded version. Re-enable USB debugging, then continue to the Revolutionary section and follow instructions there.
DOWNGRADE TOOL
Versions: HBOOT .98, firmware below 6.01.605.05
This will not work with firmware version 6.01.605.05! Use the tacoroot method!
This tool will downgrade you to 2.3.3, which will allow you to use Revolutionary to gain S-OFF.
Download the tool here, and extract it to a folder where you can easily get to it in a command prompt/terminal.
Now, connect your device to your computer with a USB cable, and turn on USB Debugging in settings. To ensure you are connected, open a command prompt/terminal and type "adb devices". If you see a bunch of letters and numbers followed by "device," you're good to go.
Navigate to the files you extracted in a command prompt/terminal ("cd /path/to/folder," replacing /path/to/folder with the actual filepath), type "hack-vivow.cmd" and let it run. It may take a while and seem to get stuck on some commands, just leave it alone. After it's done, continue to the Revolutionary section. Yep, it really is that easy.
REVOLUTIONARY
Versions: GB 2.3.3, any others after downgrade methods
This is the final step that will actually get you S-OFF.
Go to the revolutionary website, click on the download link for your OS, you'll get a download right away. While it's downloading, fill out the form that pops up (if you don't know your serial number and have the sdk installed, open up a command prompt/terminal and type "adb devices," the letters/numbers before "device" is your serial. Extract the files and run either revolutionary or revolutionary.exe depending on your OS, enter your beta key and say yes when it asks to install CWM recovery. Let it run, and you'll be S-OFF and ready to go!
If you have any questions/comments or found something that isn't right, go ahead and post, I would greatly appreciate any positive or negative feedback, as long as it's constructive.
Credits:
attn1 for Downgrade tool
Revolutionary team
Guhl for misc_version
jcase for Tacoroot
PalmerCurling for Tacoroot downgrade guide
MIVLives for bootloop fix
scotty85 for better Tacoroot downgrade and HTCDev S-OFF method
If you find anything I didn't give credits for and should have, let me know and I'll add it.
Get S-OFF after using HTCDev Unlock
(HSO)If you used HTCDev unlock and want to get S-OFF, follow this guide. What you get from going from HTCDev unlocked to full S-OFF is a full unlock instead of HTC's restricted unlock. This way, you can flash custom radios and flash ROMs without needing to extract and separately flash the boot.img. (Note: If you already installed a custom recovery and a custom ROM, flash this ROM and start at "adb push misc_version /data/local/tmp/misc_version" in the code.) To do this, first download this zip and extract it to C:/Android. You can extract it somewhere else, just replace C:/Android with the path to where you extracted it wherever it comes up. Next, download this zip and extract it to C:/Android. Download this zip as well and put it in your C:/Android folder, but do not extract it. Now, connect your device to your computer with a USB cable, turn on USB Debugging under Settings>Apps>Development, and disable fastboot under Settings>Power. Make sure your phone is fully charged. Open a command prompt by opening the start menu, typing "cmd" and hitting enter. Type in everything that is in black text. Notes and extra instructions will be written in blue. It is recommended that you copy/paste the code to avoid typos, to do this, copy by highlighting the line and hitting Ctrl+C as usual; to paste, go to your command prompt and click the small black icon in the upper left corner. A menu will pop up, go to Edit>Paste. Make sure you have not highlighted any spaces before or after the line or any of the blue text. Now, begin copying the code:
cd C:/Android
md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip Result should be cea499f51b40055ffd118960e1e73255, if it isn't, redownload the miniadb zip.
md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip Result should be ea6b98be48210d7797e62362f49ff751
md5sums misc_version Result should be 050f55d34ddbcc860efa5982491437de
adb devicesResult should be your phone's serial number.
adb push CWM-SuperSU-v0.94.zip /sdcard This might take a minute or so. If it gives an error, try "adb push CWM-SuperSU-v0.94.zip /mnt/sdcard"
adb reboot bootloader This should reboot your phone to a white menu, once it is there, continue.
fastboot devices This should return your phone's serial number.
fastboot flash recovery recovery.img This might take a while, be patient and do not interrupt it. Once it is done, use the volume buttons on your phone to navigate through the menu until RECOVERY is highlighted, then press Power to select it. Your phone will reboot into another menu, once it shows up, select "install from sdcard" then "choose zip from sdcard," then scroll down and select CWM-SuperSU-v0.94.zip, and accept it. Once it is finished, press power then select reboot. Once you are fully booted, continue with the instructions.
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 2.18.605.3
adb reboot bootloader This will reboot you to the white menu again.
fastboot devices Result should be your phone's serial number.
fastboot getvar mainver Result should be 2.18.605.3. If it isn't, make sure you didn't get any errors in the above code and everything was copied correctly.
fastboot oem lock
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip This will take a while, be patient and do not under any circumstances interrupt it.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip This will also take a bit, again, do not interrupt it.
fastboot reboot
That's the end of the code, you should be downgraded and can now get S-OFF by following the Revolutionary guide in the first post.
After S-OFF(ASO)So, now you have S-OFF. Congratulations! The next step would be to flash a custom recovery, then either an su zip or a custom, rooted ROM. For recoveries, the choices are ClockworkMod, 4EXT or TWRP. I personally prefer 4EXT, but TWRP is also great and has many great features. ClockworkMod is a little slower, but still stable. All ROMs and recoveries for the Dinc2 can be found in the development forums (where you found this guide), and there are many different ROMs to choose from, so check them out! If you want something rock solid and completely stable, try out CondemnedSoul's CM7 or one of the Gingerbread Sense ROMs, or if you want something newer, a bit faster, but maybe has a few minor bugs, check out one of the many ICS ROMs. If you want the latest and greatest, with a few slight bugs, go Jelly Bean with aeroevan's CM10. If you were looking to just root, download and flash the zip found here: http://forum.xda-developers.com/showthread.php?t=1538053, however, I would recommend that you try one of the Gingerbread Sense ROMs such as Skyraider Zeus if you wanted something a bit different with extra features, or andybonestock for a faster, debloated ROM that looks and feels exactly like what you're used to, but rooted.
Nice guide. I have to use the tacoroot method for a buddy of mine.
Awesome post!
This should be stickied...
sk842018 said:
This should be stickied...
Click to expand...
Click to collapse
+1 ^^
Sent from my Kang Banged Dinc2
Consider it done, excellent resource :good:
Also added to roll-up.
Bad links for Tacoroot.sh and .0312 radio. Great wright up though and cant wait to get my replacement unlocked.
Edit: Ok so I am almost there but have run into some issues. I cant get the 2.3.3 RUU to flash. It will get so far and stop saying bad signature verification. The one thing I noticed is that at the end of the file name it has si and not signed. I tried to change it but kinda knew that would not work and it didn't. Hope this can be fixed soon.
Edit of the edit. Ok so I followed dets34's wright up as I could not get the commands posted here to work. I put the files in the proper SDK folders and went through the commands and when I got to the RUU I hit tab after starting the name to make sure the end was si.zip. Flashed went into boot loop, boot recovery, flash newest radio, and bam no more loop with S off. Thanks to everyone who keeps us sorted out and flashing strong.
zackspeed said:
Bad links for Tacoroot.sh and .0312 radio. Great wright up though and cant wait to get my replacement unlocked.
Edit: Ok so I am almost there but have run into some issues. I cant get the 2.3.3 RUU to flash. It will get so far and stop saying bad signature verification. The one thing I noticed is that at the end of the file name it has si and not signed. I tried to change it but kinda knew that would not work and it didn't. Hope this can be fixed soon.
Edit of the edit. Ok so I followed dets34's wright up as I could not get the commands posted here to work. I put the files in the proper SDK folders and went through the commands and when I got to the RUU I hit tab after starting the name to make sure the end was si.zip. Flashed went into boot loop, boot recovery, flash newest radio, and bam no more loop with S off. Thanks to everyone who keeps us sorted out and flashing strong.
Click to expand...
Click to collapse
Links work fine for me. What did you do differently with dets34's tutorial?
The only thing that was different was I put misc and taco files in AndroidSDK\platforms. Then I put the RUU in the tools folder. Ran the commands and it went through first try. For the first part I cd c:\ to my platforms folder and ran the first part then cd c:\ to my tools folder and installed the RUU. Once it booted as soon as I messed with it boot loop. So flashed the radio and all seems to be fine.
zackspeed said:
The only thing that was different was I put misc and taco files in AndroidSDK\platforms. Then I put the RUU in the tools folder. Ran the commands and it went through first try. For the first part I cd c:\ to my platforms folder and ran the first part then cd c:\ to my tools folder and installed the RUU. Once it booted as soon as I messed with it boot loop. So flashed the radio and all seems to be fine.
Click to expand...
Click to collapse
Shouldn't make a difference if you added those folders to your PATH variable, that way you can use adb/fastboot commands without having to cd in.
Yea that's kinda what I thought but some how I messed it up or something because it never would flash the RUU. I am no expert at this by any means. Either way you helped out and its nice to see we don't have to worry about loops any more. :good:
Great guide, thanks! My couple of things I had to add in to make everything work:
Code:
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
I had to add the path to this file for it to work and then afterward do a
Code:
adb reboot
to get ready for the Revolutionary process. At first Revolutionary wouldn't recognize the device when it booted. I quickly realized I needed to re-enable USB Debug.
Then I used adb to do the rebooting necessary to flash the .0312 radio.
Thanks again! Great stuff.
techspecs said:
Great guide, thanks! My couple of things I had to add in to make everything work:
Code:
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
I had to add the path to this file for it to work and then afterward do a
Code:
adb reboot
to get ready for the Revolutionary process. At first Revolutionary wouldn't recognize the device when it booted. I quickly realized I needed to re-enable USB Debug.
Then I used adb to do the rebooting necessary to flash the .0312 radio.
Thanks again! Great stuff.
Click to expand...
Click to collapse
Updated, thanks.
Thanks for your guide. Will this guide work with the newest firmware 5.10.605.9? Just use TACOROOT?
leshan said:
Thanks for your guide. Will this guide work with the newest firmware 5.10.605.9? Just use TACOROOT?
Click to expand...
Click to collapse
Use the downgrade tool.
Sent from my vivow using Tapatalk 2 Beta-5
leshan said:
Thanks for your guide. Will this guide work with the newest firmware 5.10.605.9? Just use TACOROOT?
Click to expand...
Click to collapse
The latest firmware is 6.01.605.05. You don't have to use tacoroot.
Thanks. worked perfectly.
prototype7 said:
Use the downgrade tool.
Sent from my vivow using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
unroot to re-root correctly
Does anyone know a method to go back to stock on one of refurbed phones in order to re root correctly and not get the Sense bootloop? I found a few methods but they are all four hboot .97 and I have a feeling won't fix the problem.
mccarrel said:
Does anyone know a method to go back to stock on one of refurbed phones in order to re root correctly and not get the Sense bootloop? I found a few methods but they are all four hboot .97 and I have a feeling won't fix the problem.
Click to expand...
Click to collapse
Flash the latest firmware, or just flash whatever RUU then the .0312 radio, then follow the guide to go back to s-on.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Related
YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
*Also note that not all sections will apply to you. I have tried to seperate different senerios using * at each one. Also more then one section here may be needed by you.
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, s-on, and post OTA, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Thank you, really, for taking the time to write this guide. I shared that dreadful feeling of a brick a little while ago, but made it out alive. I know this will help a lot of people.
I'm not bricked, semi bricked or none of that. Rootrd and running BB 0.3
This is the best guide to everything you would need. Too bad you can't post this at the beginning of every thread or some kind of link on every page. This would answer a lot of question if some people would look hard enough. I'm not some smart phone guy by no means. I just read a lot before I ask. In my further reading I can direct people.with further problems here.
Thanks for all your work and giving me another fun hobby
Peace
Sent from my T-Mobile G2 using XDA App
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Good point . Not sure on that one
Sent from my T-Mobile G2 using XDA App
renn9420 said:
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
if you look where im saying /mmcblk0p21 we are replacing RECOVERY with CWM. i do that because i just dont like the idea of trying to replace hboot from a looping system. worst case something goes wrong, you still have hboot and you can try again. screw up hboot, game over! then once android is back up and running we worry about hboot on mmcblk0p18.
you should not state that steps can be changed if people are brave, someone is going to sip parts and cry that their hboot is boned and now they have a BRICK, this is the best post i have seen in the G2 section thus far and i have been through almost every thread(with any kind of importance) in the dev section and 90% of them in general and Q&A. thank you for this post and let's hope people READ at least 5 times before even starting on this.
Gotcha
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Amazing guide, thanks a lot.
fastludeh22 said:
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
Click to expand...
Click to collapse
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
reycat said:
Amazing guide, thanks a lot.
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
Click to expand...
Click to collapse
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
{golf clap} on the post.
you sir, have incredible patience... and it's truly appreciated.
fastludeh22 said:
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
Click to expand...
Click to collapse
Mmm... It seems all of it is quite a bit over my head.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
Click to expand...
Click to collapse
Don't ask me how I did it, but I actually downloaded a web page instead of the actual hboot file I should have used . I did it from the phone and didn't notice. Since I was supposed to rename it to make the typing easier, I didn't notice it was the wrong file.
Anyway, right now the phone is a complete brick. It doesn't respond to any button presses, the LED doesn't do anything when you plug in the charger... A complete brick.
Device offline?
fastludeh22 said:
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Click to expand...
Click to collapse
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
-FuRBz- said:
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
Click to expand...
Click to collapse
Download and instal PDANet, that gave me the drivers i needed for adb, now if only i could figure out how to get my device to register online through the ADB command interface.....
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
marley097 said:
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
Click to expand...
Click to collapse
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
-FuRBz- said:
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
Click to expand...
Click to collapse
Glad you got it! After drivers installed, did you fix it per a section of the op?
it all happened because i had tried flashing cm 6.1- it got stuck on the splash screen but i had done a recovery prior to trying to flash... once i got the drivers installed i was able to get in to adb and do a reboot-bootloader and was able to get into the recovery file
fastludeh22 said:
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
Click to expand...
Click to collapse
Lame....so how often do they release official pic10img's....? are we talkin a month....or a year?
ok so what is fast boot i see it when i hold down volume and power button it doesnt do much for me am i suppose to enable it some how i only ask becuase i see people talking about it flashing things via fastboot but im not sure what that is. also i want to flash gingervillain 1.4 and i want to have an idea what i need to do incase i want to get back to froyo
cudahy_boy said:
ok so what is fast boot i see it when i hold down volume and power button it doesnt do much for me am i suppose to enable it some how i only ask becuase i see people talking about it flashing things via fastboot but im not sure what that is. also i want to flash gingervillain 1.4 and i want to have an idea what i need to do incase i want to get back to froyo
Click to expand...
Click to collapse
You need to have the ENG. Hboot installed on your phone in order to use "Fastboot". If your not sure if you have it or not, boot into Hboot(volume down+ power) and the first line will say " VISION PVT ENG S-OFF" if it says this you have the ENG. HBOOT, but if it says "VISION PVT SHIP S-OFF" you dont and cant use fastboot. Check the WIKI for info on flashing the ENG. Hboot.
As far as flashing GingerVillian you dont need the ENG. Hboot to flash CWM 3.0.0.x you can do it from your Phone . HERE is a link on how to do it, as far as getting back to FROYO just follow the flash_image instructions for flashing CWM 3.0.0.x in the link I provided except replace the CWM 3.0.0.x with a CWM 2.5.1.3 recovery.img and rerun the commands.
ok im kind of confused do i use adb in command to write this
This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)
(this part below)
I'd recommend using an adb shell from your computer (with root privileges: just unlock your phone, run 'su' in adb shell, a window will pop up in your phone asking you to allow it to run, check for it to remember, then allow, the prompt in adb shell will change to '#') for the following command, as it will permit you to copy/paste it:
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
cudahy_boy said:
ok im kind of confused do i use adb in command to write this
This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)
(this part below)
I'd recommend using an adb shell from your computer (with root privileges: just unlock your phone, run 'su' in adb shell, a window will pop up in your phone asking you to allow it to run, check for it to remember, then allow, the prompt in adb shell will change to '#') for the following command, as it will permit you to copy/paste it:
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
You can do this from your phone/w terminal emulator or computer/w ADB, what it is saying is it recommends using your computer/w ADB in an ADB Shell to run this command because you can simply just copy and paste the command into the command promt so there will be no mistakes typing it out by hand, make sure you follow the instructions perfectly or you will end up with a brick. Good luck.
This guide is now obsolete. Please use this guide instead.
For Gingerbread Phones, Please use this guide.
Hey guys, this is probably the easiest guide to follow for rooting a branded desire Z. The reason why this can sometimes be hard is cause it uses a unique identifier (INFOCID) and the companies that brand the phones ONLY want roms from their company on them. This stops us from using a WWE rom like every else to downgrade and then root.
But ultimately, the reason I'm making this is because every other guide I've read constantly links you to other guides or other pages and it sorta annoyed me. So after I figured it all out I posted one concise guide that doesn't redirect you 50 times.
Now I’m gonna run you through EVERYTHING so you won’t get stuck anywhere.
This guide will work with:
Device: Desire Z or G2
Firmware Version: Any Firmware version will be fine (All you need to do is downgrade using step 1)
Android Version: Froyo or any previous variation of Android (Absolutely no gingerbread device will root with this method)
Btw, I take no responsibility for any damage taken by using these procedures. Sorry =P
Also if you don't have ADB and Fastboot set up then go ahead and follow the guides on the first two posts here. -Thanks nephron
g4b4g3 said:
If your INFOCID is NOT one of these you need to make a goldcard to downgrade!
HTC__001
HTC__032
HTC__E11
HTC__203
HTC__Y13
HTC__102
HTC__405
HTC__304
HTC__A07
HTC__N34
HTC__J15
Which can be checked by typing the following two commands:
adb reboot bootloader
fastboot oem boot
Click to expand...
Click to collapse
If your CID matches one of the CID's above then you can skip Step 1.
1. Creating a Goldcard:
Prerequisites:
ADB Set up and running fine (to check if it is working just connect your phone and have USB debugging enabled. Then type adb devices in your CMD Prompt)
HxD Hex Editor (see attachments of post 1)
USB Debugging enabled on your phone
1.Firstly we need to mount the memory card on a windows PC.
2. Format the memory card as FAT32 using all the default options.
3. Mount the memory card on your Phone. Then give it a couple of seconds.
4. Remount the memory card on your PC.
5. Find your CID by using the follow command in your cmd prompt (YOU NEED ADB)
Code:
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid
6. Use the excel sheet provided to reverse the CID (see Attachments)
7. Goto this website and send yourself a goldcard.img
http://psas.revskills.de/?q=goldcard
8. Run HxD hex editor AS AN ADMINISTRATOR! (I can’t stress how important having admin rights is)
9. Go to Extras > Open Disk Image. Then select your goldcard.img
10. Go to Extras > Open Disk. IMPORTANT: Select your memory card UNDER the Physical Drives category. DO NOT open the logical drive.
11. Switch to your goldcard.img tab. Go to Edit > Select All. Then Edit > Copy.
12. Go to the physical drive tab and select the lines 00000000 until you get to the one with 00000170.
13. Go To Edit > Paste Write.
14. You should have a huge block of red characters now. This is good btw.
15. Mount your SD card on your Phone and let it detect it. If it comes up with a corrupt SD card error you have done it wrong and you may have to start over.
16. You are done with the goldcard.
2. Downgrading and Debranding
Before you start this please do the following:
1a. Download the RUU I’ve linked (it should be a ~300mb exe file) -Thanks g4rb4g3
ii. If you are a BELL User. Please download this RUU instead.
1b. Run the setup until you get to the screen with the tick boxes (Some Users may have to run this as an Administrator)
1c. Leave the setup running and go to C:\Users\<your account name>\AppData\local\temp ( Or Try %AppData%\Local\Temp\ ). Then right click and Sort By Date Modified. Look for the most recently created folder which should look like {xxxxxxx-xxxxxx-xxxxxxxx}. Then navigate into it and its then into its one folder. Look for rom.zip and copy that to your goldcard/memory card.
1d. Rename the rom.zip on your memory card to PC10IMG.zip (Make sure it is exactly the same as the way I've typed it there)
1e. Mount your sd card back onto your phone.
2. Download the attachments (misc_version & psneuters) and extract them in a folder like C:\RootVision\
Now you are ready to begin:
1. Open a CMD prompt window
2. Navigate your way to the folder with psneuter & misc_version IN CMD PROMPT. (So the cmd prompt window should be something like this C:\RootVision> )
3. Now we will use the following 5 commands one after the other
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
4. After the last command you should have a # and a flashing line for you to enter text. This is good. (If you get a $ you have done it wrong and should try typing the commands out again)
5. Now you have the # type the following command in: (This will spoof the radio version)
Code:
/data/local/tmp/misc_version –s 1.33.405.5
Then go ahead and type:
Code:
exit
6. Type this command into your cmd prompt (btw you should be back with the normal C:\RootVision>)
Code:
adb reboot bootloader
7. Once on your white screen with colourful text you can go ahead and press the power button ONCE
8. Now just wait for the rom to install and verify. If you get INCORRECT CID your gold card doesn’t work or your CID doesn't match and you'll need a goldcard. (Go to Step 1. and make a goldcard for your phone)
9. Go ahead and install the rom when it asks you.
10. You are done downgrading and can now begin the Rooting process.
See Post 2 For Rooting
Assuming all as gone well and you now have a rom without superuser but you have a baseband version that is 1.34xxxx.
Alright, let’s begin.
Prerequisites:
Download psneuter
Download gfree 0.5
Download root_psn
Download flash_image
Download the Desire Z hboot
Download Clockwork Recovery
ALL of these are in the attachments section
They all should be extracted into the same folder. Use something simple like C:\RootVision\Root
3. Root your Desire Z!
Before you start:
Enable USB Debugging and Allow Unknown Market Installations again.
Also delete the PC10IMG.zip on your phone if you downgraded.
Okay lets go:
1. Now Assuming you succeeded at the last part you should have a stock-ish rom without superuser. What we want to do is start by pushing all the files across with the following adb commands (use in cmd prompt the same way you pushed files in 2.)
Code:
adb push psneuter /data/local/tmp/
adb push gfree /data/local/tmp/
adb push busybox /data/local/tmp/
adb push root_psn /data/local/tmp/
adb push flash_image /data/local/tmp/
adb push su /sdcard/
adb push hboot-eng.img /data/local/tmp/
adb push Superuser.apk /sdcard/
adb shell chmod 755 /data/local/tmp/*
2. Alright now we have all the files we need to root the phone. Input the following command. This is just putting our clockwork recovery in a convenient place with an easy name.
Code:
adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
3. Now we’re gonna temp root again by typing in the following:
Code:
adb shell /data/local/tmp/psneuter
adb shell
4. This should leave us with another #. Now enter the following commands:
Code:
cd /data/local/tmp
./gfree -f -b hboot-eng.img
./flash_image recovery recovery.img
./root_psn
sync
5. Type in: (thanks for the correction john_d1974)
Code:
reboot
6. You should have a rooted phone with superuser after the reboot. Also it will have clockworkmod, SuperCID, secu-flag off & an Unlocked HBOOT-ENG.
If gfree 0.5 doesnt work for you then this section is for you:
Prerequisites:
Download psneuter
Download gfree 0.2
Download root_psn
Download flash_image
Download the Desire Z hboot
Download Clockwork Recovery
ALL of these are in the attachments section
They all should be extracted into the same folder. Use something simple like C:\RootVision\Root
1. Now Assuming you succeeded at the last part you should have a stock-ish rom without superuser. What we want to do is start by pushing all the files across with the following adb commands (use in cmd prompt the same way you pushed files in 2.)
Code:
adb push psneuter /data/local/tmp/
adb push gfree /data/local/tmp/
adb push busybox /data/local/tmp/
adb push root_psn /data/local/tmp/
adb push flash_image /data/local/tmp/
adb push su /sdcard/
adb push hboot-eng.img /data/local/tmp/
adb push Superuser.apk /sdcard/
adb shell chmod 755 /data/local/tmp/*
2. Alright now we have all the files we need to root the phone. Input the following command. This is just putting our clockwork recovery in a convenient place with an easy name.
Code:
adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
3. Now we’re gonna temp root again by typing in the following:
Code:
adb shell /data/local/tmp/psneuter
adb shell
4. This should leave us with another #. Now enter the following commands:
Code:
cd /data/local/tmp
./gfree -f
./flash_image recovery recovery.img
./root_psn
sync
5. Type in: (thanks for the correction john_d1974)
Code:
reboot
6. You should have a rooted phone with superuser after the reboot. Also it will have clockworkmod, SuperCID and secu-flag off.
4. Installing your own custom ROM
This section is just in case you don't know how to install a custom ROM.
Note: Always make sure the ROM you are installing is FOR YOUR PHONE! If you install a ROM meant for another phone you could potentially damage it or brick the phone itself.
1. Download the ROM you want and copy it to your SD Card. (Try to keep it in a folder that is easy to get to)
2. Turn off your phone.
3. Hold down the volume down button and then press the Power Button. This should take you to a white screen with lots of colourful text. One of which says FASTBOOT or FASTBOOT_USB.
4. Press the power button ONCE when BOOTLOADER is selected(BLUE)
5. Navigate using the volume buttons until you get to RECOVERY and then press the Power Button again.
6. The HTC Logo will come up then you will get a black screen with text.
7. From here you should Always do a NANDROID Backup so you can restore a working ROM if something fails.
NANDROID Backup
7a. Navigate to 'backup and restore' and then select it by pressing the trackpad button.
7b. Select 'Backup' and then let it finish. Once done you have a backup of your android.
8. Now you want to do these before you start installing:
a. 'wipe data/factory reset
b. 'wipe cache partition'
c. Go into 'advanced' and select 'Wipe Dalvik Cache'
9. Now you can install the ROM itself. This is done by selecting 'install zip from sdcard' in the main menu. Now you can select 'choose zip from sdcard' and just go ahead and select the ROM you copid to your sd card earlier.
9a. If the phone says verification failed then just toggle the signature verification option.
FAQ - For Anyone with any issues.
1. My version is 1.7xxxx or higher. Can I use this method?
Yes you can. This method will downgrade your phone to 1.34 so your radio is no longer locked thereby allowing you remove the secu-flag, add superCID and allow you to install a custom recovery (like ClockWorkMod)
2. My CID is XXXXXXXX and isn't on that list, will this method still work?
Yes it will. The reason why it will work is because a goldcard is essentially a manufacturers way of bypassing the CID checks used by ROMs. Therefore, by creating our own unique goldcards we can also bypass the CID check.
3. My CID is on the list that you mentioned. Do I need this goldcard?
No, you can skip the 1st step because when the ROM checks your phones CID it will match up perfectly and the phone will install the older radio without issue.
4. What Benefits does rooting a phone grant you?
Simply, it allows you to install any ROM of your choosing onto the phone as well as use custom kernels and certain applications that access locked functions on the phone. This can ultimately lead to; a longer battery life; more stable roms and more frequently updated roms; and finally an overall faster Android experience.
5. What is root access?
Root access essentially gives you access anything locked by the manufacturer on the phone. This most importantly means that you can read and write to any system partitions on the phone that would normally be locked.
6. Whats psneuter?
psneuter is an application used to grant temporary root access. This is done through an exploit in the android system and will give us a window to further exploit the system and ultimately grant us Permanent Root Access.
7. How do I find my CID?
To find your CID you run two commands. Firstly, in your CMD prompt you type 'adb reboot bootloader' when your phone is connected and USB debugging is active. This will restart your phone into its bootloader. Then once you see the words FASTBOOT_USB you type 'fastboot oem boot'. Then look for the words CID and then just read the 8 character CID.
Also there is a post with a screenshot here.
8. My phone will not find PC10IMG.zip
You will need to double check that the PC10IMG.zip is the correct ZIP file from the RUU that has been linked. It should be roughly 250mb in size and should be placed in the root folder of your SD Card. Also your SD Card must be compatible with your device (able to be read/written to). If you cannot access your SD Card from your Desire Z or G2 then there is probably something wrong with your SD Card. It should probably be reformatted.
9. Can I use this on the Desire Z/G2 running Gingerbread?
So far no one has been able to root the gingerbread version of android on the Desire Z/G2. Unfortunately, this guide still cannot root gingerbread desire Zs or G2s.
If there are any more, feel free to post them and I'll add them
10.I'm Missing my AdbWinApi.dll? What now?
espentan[U said:
][/U]
I don't know if you've figured this one out yet, but here's the solution to a potential cause.
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Now the windows command shell knows where to find the necessary DLL's and whatnot.
Click to expand...
Click to collapse
will this work if i have 1.84.666.2?
anyone? thought?
Should work fine as long as you've got a Desire Z or G2 lol.
hi, manageage to root the DZ sucessfully, however on step 5 you say
"5. Type in:
Code:
Reboot"
i got an Reboot: error not found
i retried with with "reboot" and was sucessful
Hi, im sure this has been covered before in other posts, but, could someone tell me, if i were to use the above method to downgrade and root etc, would this prevent me from doing an official upgrade, to, say gingerbread in the near future? Also is there any real benefits to going to gingerbread? I ask as im sure ive read somewhere its only possible to flash to cooked roms, not official ones (once downgraded and rooted etc).. this would concern me as ive moved over from win mo to android, and in my experiance, EVERY cooked unoficial rom i ever flashed (xperia x1) was simply rubbish, and i tried alot of them. (Even though people would say the roms would be fine, bugs smoothed out etc), i went back to stock in the end after constant dissapointment.
Sorry for the rant, just need to know where i stand.. thanks people..
jmpcrx said:
Hi, im sure this has been covered before in other posts, but, could someone tell me, if i were to use the above method to downgrade and root etc, would this prevent me from doing an official upgrade, to, say gingerbread in the near future? Also is there any real benefits to going to gingerbread? I ask as im sure ive read somewhere its only possible to flash to cooked roms, not official ones (once downgraded and rooted etc).. this would concern me as ive moved over from win mo to android, and in my experiance, EVERY cooked unoficial rom i ever flashed (xperia x1) was simply rubbish, and i tried alot of them. (Even though people would say the roms would be fine, bugs smoothed out etc), i went back to stock in the end after constant dissapointment.
Sorry for the rant, just need to know where i stand.. thanks people..
Click to expand...
Click to collapse
It is pretty difficult to go back to stock updates from your carrier for example Vodafone. This is because of the unique CIDs used and the fact that it is extremely hard to find a stock ROM since no one can give you a NANDROID backup.
Anyways, there are numerous benefits to rooting your phone included with most ROMs. These benefits include longer battery life, faster ROMs & various other things depending on each chef.
Ok, thanks, but are the roms buggy at all, will some of the hardware not work properly, or will i have freezing probs etc, as i found this always to be the case with win mo roms?.. have you personally found a rom that works perfectly that includes htc sense? As i do like the UI..
My goal is to have all security off, full perm root, with a perfecly working sense rom that i can then overclock to a speed that works well with my particular phone, and to underclock when idle etc..
Thanks..
I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?
Newbie question,
how to unroot if i rooting the phone using this metode?
and how to go back to original rom?
Vader™ said:
Newbie question,
how to unroot if i rooting the phone using this metode?
and how to go back to original rom?
Click to expand...
Click to collapse
Firstly, to root the phone just follow the steps and once you've finished them all you will be done.
Second, it should technically be possible once you've rooted the phone to simply do a NANDROID backup via ClockWorkMod Recovery before you start flashing new ROMs. If you have backed it up and later decide you want to unroot then all you would need to do from there is restore your nandroid backup and unroot the phone through this method.
forceOnature said:
I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?
Click to expand...
Click to collapse
Using this method you don't have to worry about your CID. If you make a goldcard it will completely bypass the need for one of the CID's listed in the first post. So to put it simply, you don't need to worry about your unique CID if you create and use a goldcard to downgrade.
Aegishua said:
It should technically be possible once you've rooted the phone to simply do a NANDROID backup via ClockWorkMod Recovery before you start flashing new ROMs. If you have backed it up and later decide you want to unroot then all you would need to do from there is restore your nandroid backup and unroot the phone through this method.
Click to expand...
Click to collapse
okay, but we need to root the device first right? before ClockWorkMod Recovery can run, the problem is, if I root the device first, the device must be downgrade to build 1.34.405.5, and now my Desire Z using build 1.82.xxx.x
is it if we backup via ClockWorkMod, the ROM that we backup is 1.34.405.5? not my current build?
please help bro, really confused here
Hi forceonature, im no expert, but when i was having a look myself, i found out it was simply my enviroment variables wernt set up for the directory fastboot was located.. an easy way round this was just to enter the directory fastboot was in (program files, 'some directory'.. do a quick search) within your command prompt, and type the second command from there.. hope that helps..
Everything goes fine until
mmap() failed. Operation not permitted
when I put in
adb shell /data/local/tmp/psneuter
Any help?
Also I can only put su and Superuser.apk on my sdcard if I manually transfer them.
Hi forceonature, im no expert, but when i was having a look myself, i found out it was simply my enviroment variables wernt set up for the directory fastboot was located.. an easy way round this was just to enter the directory fastboot was in (program files, 'some directory'.. do a quick search) within your command prompt, and type the second command from there.. hope that helps..
Click to expand...
Click to collapse
I need to verify that my Tmobile G2's INFOCID is compatible.
I typed in the two commands:
adb reboot bootloader
fastboot oem boot
The first one worked. The second command is not recognized once I'm in the bootloader. Can someone suggest a solution?
Click to expand...
Click to collapse
I tried the same thing to get my DZ phones CID and the first one worked and the second didn't. If I don't have to make a gold card all the better. How can I find out for sure if my CID is on the list or not? Also if I have to make a gold card do I need to have a micro SD card to make the gold card?
Thanks,
Chevy
chevy2410 said:
I tried the same thing to get my DZ phones CID and the first one worked and the second didn't. If I don't have to make a gold card all the better. How can I find out for sure if my CID is on the list or not? Also if I have to make a gold card do I need to have a micro SD card to make the gold card?
Thanks,
Chevy
Click to expand...
Click to collapse
You should get a line that says INFOt.cid=XXXXXXXX or any of the lines that say your 8 Digit CID. However, as you can see there are multiple lines that say it and they should all be the same.
If your CID does match one on that list then you will not need a goldcard.
I've attached a screenshot to make things easier.
forceOnature said:
okay, but we need to root the device first right? before ClockWorkMod Recovery can run, the problem is, if I root the device first, the device must be downgrade to build 1.34.405.5, and now my Desire Z using build 1.82.xxx.x
is it if we backup via ClockWorkMod, the ROM that we backup is 1.34.405.5? not my current build?
please help bro, really confused here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Yeah, you can only have a NANDroid backup of 1.34.xxx because there is no way to get clockwork onto a 1.72+ rom.
Hi, I'm new to rooting the G2. Iv'e been trying to follow this tutorial, but I'm having some trouble. After renaming Rom.zip to PC10IMG.zip I booted into the bootloader and it says 'no image found' or something like that. What am I doing wrong? Am I not supposed to put the zip file on the root of the SD card? Is it possible to just use the RUU to downgrade?
And regarding the downgrade, the build number on my G2 shows 1.22 . Isn't that lower than 1.34?
Any help is appreciated!
I followed the instructions twice and both times I get to
"/data/local/tmp/misc_version –s 1.33.405.5"
I get
/
Patching and backing up partition 17
Error opening backup file.
#
The first time around I iqnored it and went through hboot, the rom PC10IMG.zip was checked and verified and finally failed prompting "the main version is older"
what am I missing?
EDIT: checked SD card, unmount and remounted phone/sdcard no avail.
Will try 1.33 Bell rom next.
EDIT2: Patching and backing up sucessful, problem was I couldn't get my phone to stay in debugged mode without being in DISK DRIVE, had to start HTC Sync to mount the phone in that way to relieve the sd card, allowing adb to patch the file. Now running through PC10IMG.zip with fingers crossed.
EDIT3: Everything went smooth after that! Thanks. Now I will attempt to update to 2.3 and Sense 3.0
EDIT4: Now running on 2.3.3 and Sense 3.0 Virtuous port. Testing...probably going back to more stable gingerbread and sense 2.1
It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
*--*--* I am not responsible for any damage that may occur to your phone by following this guide or any other guide. If you are at this step, your warranty is already void, and if you lie to Verizon to get a replacement, an angry bear will break into your house and molest you quite thoroughly. Those people are the reason why Verizon is forcing locked bootloaders, and why I had to wait two months to root my Inc2. Don't be one of those people. You might be a noob, but that doesn't excuse you from doing research. In short, anything that happens is your own damn fault, and you can't blame anyone else. /rant *--*--*
Now that that is out of the way, the steps:
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe and adbwinapi.dll, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Boot into fastboot by powering the device off, then powering back on while holding the volume down button on the side. It should boot to a white screen, similar to what you saw when you first rooted it. Plug your phone into usb if you haven't already.
6. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot".
7. Rooting the phone is only the beginning. You still need a rooted kernal, and su and busybox. Without these, rooting does you little practical good. To that end, follow RMK's guide here: http://forum.xda-developers.com/showthread.php?t=1160745. That will get you all set up to start enjoying root fully. I would recommend installing ROM Manager from the market and using it to flash the latest CWM (4.0.0.8). ****NOTE that you need to already have CWM to flash the su and then flasht he new CWM. I know, it seems silly, but that's the way things are. Also, a disclaimer: a few people have had problems with the newest CWM not working properly for them. It worked for me, though, and there is a fix on page four of this thread.
Credit goes to attn1 for the modified CWM, xgunther for posting it/original instructions, and crazythunder of Android Community for the original instructions for using fastboot with a G1. Hope this helps
Some information from supersonic that those trying this on linux will find useful. Thanks!
supersonic2.5 said:
Download this recovery: http://forum.xda-developers.com/showthread.php?t=1134520
BTW, if you havn't installed fastboot, download it here.
http://developer.htc.com/adp.html
1.First rename your android sdk folder to "sdk" just like that. Dont use quotation marks on anything fyi.
2.Next step is to move the sdk folder to your home folder.
3.Move adb, fastboot, and the recovery image from the link above into the tools folder of the sdk.
4.Open up terminal and type or copy this in there.
"cd sdk/tools" hit enter.
5. "./adb kill-server" hit enter.
6. "./adb start-server" hit enter. should look something this. (below)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
7. "./fastboot" hit enter.
8. "./fastboot flash recovery cwm-recovery-vivow.img" hit enter
give it some time to flash.
9. "./fastboot reboot" hit enter
10."./fastboot adb reboot recovery" hit enter
And there you go, wait for your phone to reboot and what not and you should have CWM installed. I would immediately do a nandroid of the stock rom. after that i didnt bother messing with superuser on stock froyo because who the hell wants to be on froyo!? lol, so i installed the GB ota rooted version with superuser already because its very stable....found here http://forum.xda-developers.com/showthread.php?t=1161411 as i wait for a stable version of rewind,you can then install and update CWM through rom manager to the current version once you've done this.
there you go buddy sorry so long. if you encounter any problems let me know so i can boot into ubuntu and help out. i'd give you a little more details but im on my mac right now. hit the thanks button if i was any help
Click to expand...
Click to collapse
devator22 said:
It took me some searching to find this information, so I thought I would post it here in an easy format. This will get the modded CWM flashed on your Inc2 so you can start enjoying root.
1. Download the android SDK here http://dl.google.com/android/installer_r12-windows.exe I don't really want to go into details on this, as it is explained on the site and in the sdk itself. Basically, install and then follow the directions here http://developer.android.com/sdk/installing.html specifically the part about the sdk tools.
2. Open the sdk tools folder, select adb.exe, adbwinapi.dll, and ddms.bat, then copy them to somewhere easy to find. I just dumped them in the C:\ folder.
3. Download http://android-roms.googlecode.com/files/fastboot-win32.zip and extract to the same folder with the other files (C:\ in my case).
4. If you haven't already, download the CWM file from here http://forum.xda-developers.com/showthread.php?t=1134520. Extract the main image (not the osx image) to the same folder with the other files (not necessary, but makes things easier).
5. Open the Command Prompt. Type (without the quotes): "cd (the folder where adb is)" so, "cd C:\" in my case. Next: "fastboot flash recovery cwm-recovery-vivow.img" and when it is done, "fastboot reboot". And you should be done.
Credit goes to attn1 for the modified CWM, and xgunther for posting it/original instructions. Hope this helps
Click to expand...
Click to collapse
Just a heads up, if you are S-Off, you can enjoy these instructions on Mac, Linux, or Windows. ADB and fastboot give you options for all! <3
Here is another link i found to help out!
http://forum.xda-developers.com/showthread.php?t=1122694
In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.
I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit
b0gman said:
I know this is pretty new but does anyone know how to flash fastboot through the linux side I have just about given up on getting the ADB to work in Win 7 64bit
Click to expand...
Click to collapse
Dumbest solution ever... I was having the same problem. As long as you've installed the jdk file from the link it shows on the initial error on sdk install...
Just click 'back' then 'next' again on the SDK installer... It worked for me.
Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?
Grouper said:
In case you didn't know, AlphaRev X will install CWM for you. Then you can just load a different ROM, install ROM Manager, and update it from there.
Click to expand...
Click to collapse
Guess I forgot to mention that this is for the people with problems with the automatic installer, including myself.
Sent from my Incredible 2 with Xda app
Clutch McWinner said:
Now I'm getting stuck on 'Waiting for device' when I run the fastboot command on the command prompt. Thoughts?
Click to expand...
Click to collapse
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app
devator22 said:
Are you in fastboot on your phone?
Sent from my Incredible 2 with Xda app
Click to expand...
Click to collapse
I was, but it turns out I didn't have the HTC sync drivers. S-Off, Rooted, and running overclocked CM7 now!!!!!!!
This must be in Fastboot USB mode while doing?
Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?
SHAKEJONES said:
Im also stuck on < waiting for device >
I've tried in charge only mode and HTC Sync mode and neither seem to be recognized by cmd. The HTC Sync software opens when I connect the phone in HTC Sync mode so I would assume the drivers are installed correctly. Any ideas?
Click to expand...
Click to collapse
Should HTC Sync be opening? I think you're supposed to uninstall HTC Sync, but leave the drivers. AlphaRevX provided a link to the drivers only, so it might be easier to just completely uninstall everything and then reinstall the provided driver instead.
Just tried that and its still stuck... I'll mess with it more tomorrow
Yeah i've been having the exact same problems with the drivers. I have a completely fresh install of windows 7, and it still wont work. I installed the HTC Sync, and it still doesnt recognize my device. I tried using Ubuntu, however it makes absolutly zero sense in my mind, so unless i have a detailed instuctional text, windows is my only choice really. Its funny, this thread is for noobs, yet i can't get even do this, but other phones i've rooted without any problems, and they we're much harder for me. Blah.
I've tried all variations of connection modes, triple checked I had all the files in the right spot, and tried different usb ports and it still wont work... does someone have a more detailed guide for this?
Seriously frustrated about this. S-Off was no problem. I'm triple booted with OSX, Win XP Pro and Linux. Used linux to get s-off but didn't get a CWM install. Window won't allow the driver to install and Linux is a mystery. Anybody have luck with OSX or Linux and want to write it up?
OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.
devator22 said:
OH, all you people having trouble...you need to be in fastboot in order for this to work. Power off your phone, then power it back on while holding volume down. Then run the commands.
Click to expand...
Click to collapse
Thank you kind sir hahaha I JUST got done doing that and it worked like a charm! this thread will be a great help to anyone else ---> http://forum.xda-developers.com/showthread.php?t=1122694
The directions for fastboot are in the OP
Haha, yea. I guess I am a noob when it comes to writing guides. I updated the OP with an extra step for booting into fastboot.
Disclaimer:
I (or anyone other than yourself) am not responsible for anything that goes wrong with your phone. This process is very safe, and the likelihood of bricking your phone is so small that you have a better chance of flying to the sun without a rocket. If you read the guide here closely and do not alter from it in any way, your phone will be S-Off and fully ready to have fun with.
#2
I did not write any code or have any involvement with the development of rumrunner. If you want to donate to someone, donate to them at [email protected] via PayPal. Really guys, I didn't do anything more than test.
For Linux:
For Linux, you do not have to install anything to your hard disk. In fact, you only need a USB port or CD-ROM drive. Ubuntu (32bit) is the recommended distro, however others will work. This guide will only use the Ubuntu given below, for universality purposes.
Downloads:
Firstly, we need to get some important files. Please download all the files given below
Ubuntu 13.10 (32bit)
rumrunner (Go to One V Linux at the bottom of the page)
hboot mod (For your corresponding device, for more info see Device Identification section)
NOTE: Some variants do not have Hboot mod yet. Please be patient.
ADB and Fastboot
Unsecured boot.img
If primoc or if primou (DONT have a stock boot.img yet... can someone send that in a PM please)
Now that you have all the files, boot into Ubuntu. I will not go into detail in how to do this, as it is well documented elsewhere.
Once in Ubuntu, open a terminal for usage.
Now minimize this and place the downloaded files onto your desktop.
unzip the adb_fastboot_linux.zip file to the Desktop
Un-tar and Un-gzip your rumrunner file to the desktop. This can be done by double clicking the file, then clicking extract.
unzip the adb_fastboot_linux.zip
move Primoc_Unsecureboot.img into adb_fastboot_linux/
go to your terminal, type "cd ~/Desktop/adb_fastboot_linux/ && chmod a+x *"
now type the command "sudo ./adb reboot bootloader" (if you get waiting for device, enable USB debugging in developer settings)
If you're not unlocked, unlock at htcdev now... Else, continue
Run the command "sudo fastboot flash boot Primoc_Unsecureboot.img" then "sudo fastboot reboot"
Now....Type in "cd ~/Desktop/rumrunner_primo_0.5.6" and press enter.
Now, type in sudo soju. Respond to the prompts within the program and follow all the directions.
You should now be S-Off... want more power, well lets get it.
If your device has a hboot mod follow the following commands.
move the hboot_rumrunner_primoc.zip into adb_fastboot_linux/
"sudo adb reboot bootloader"
"sudo fastboot erase cache"
"sudo fastboot oem rebootRUU"
"sudo fastboot flash zip hboot_rumrunner_primoc.zip"
OR if it primou
"sudo fastboot flash zip hboot_rumrunner_primou.zip"
Congradulations, you are now S-OFF and can flash kernels in recovery. You also have flat out ultimate control over your phone; however, tread carefully. With great power comes great responsibility.
NOTE: Windows coming soon.
Device Identification:
It is important to know which device you have with the S-Off process. If you do not know what device you have, you can severely damage your device, possibly bricking it. To prevent this, follow the steps for identification below.
Unplug phone if plugged in
Go to settings>power>fastboot(disable)
power off phone completely
once phone is off, press volume down+power until bootloader appears
look in the top left corner, you will see either Primou or Primoc
If primou appears, you are GSM if primoc appears you are CDMA
Reserved
Im leaving this thread closed until I get a chance to write up windows as well