Related
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
simple29 said:
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
Click to expand...
Click to collapse
what guide are you using? the recovery img has to be in the same folder as fastboot unless you point it towards a different folder
In the same boat as the OP, I've done everything right and I get this error message in cmd with the black screen and white HTC text.
BTW OP - You can go back to using your phone. Take out the battery (with the usb plug out of the phone or computer) and put it back in and turn the phone on normally. You'll just have to go through the process again of fastboot oem rebootRUU to get back to the black screen with white HTC text.
I'm using the CyanogenMod Wiki HTC Incredible 2 Full Update Guide (since I cannot link it in my post), I dunno what the OP is using. Also, the recovery file is in the appropriate location(s) in the android-sdk-windows folder.
im using the cyanogenmod wiki and i tried putting the recovery image for clockwork into the same folder as fastboot and adb and it still gives me that error and i dont have the technical savvy to figure this out
edit: that would be the platform-tools folder in the android sdk folder, thats what i found people did by googling this
and to finalassault, i took out my battery and tried turning it back on normally i just get stuck at the white screen with the green htc lettering so i clearly messed something up unless i just have to wait a few minutes
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
nothing is working and im completely lost, thanks for the help though
also i still cant turn my phone on normally
drcrawfo said:
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Same error, except it's just coming up as not able to load this file instead of the other one. Maybe I possibly screwed up whilst doing AlphaRev?
Edit - I just did it a different way and I didn't get an error message:
sending 'recovery' (5022 KB)...
OKAY [ 25.776s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 28.030s
I guess that worked.
Edit 2 - It "worked" but didn't really do anything else. Might have done something wrong on the AlphaRev step. Actually I'll shut up now, something else showed up.
Edit 3 and final edit - Done and done. That was fun.
how did you get it too work???
simple29 said:
how did you get it too work???
Click to expand...
Click to collapse
It sounds like you may have borked your stock rom....if you can boot to hboot and select fastboot then you should be able to flash the CWM from this link http://forum.xda-developers.com/show...php?p=14947083
Follow the instructions on the link not the one from CM Wiki. Make sure you have fastboot.exe and CWM image from the link in the same folder as your adb. If you're using windows 7 64bit then you'll need to run adb in compatability mode (at least that's what I had to do to get it working in 64bit).
You should then be able to flash a rooted, deodexed stock froyo sense rom from this link by Jcase http://forum.xda-developers.com/showthread.php?t=1138274 or use XGunthers Incredibly Debloated Rom here http://forum.xda-developers.com/showthread.php?t=1138202
That should get you up and runnning. Or you could just jump straight into the GB ASOP roms CM7, MIUI, etc.
Let me know if this works for you....
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
edit: got it in compatibility mode, i suppose i didnt install it right because it looks like it does something for a few seconds then seems to stop
simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
Use the link in my post above.
Sent from my Incredible 2 using Tapatalk
simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
It's okay don't worry...I'm pretty new to this stuff too since I just got into rooting about 2 weeks ago.
Compatability mode is an option in windows 7. Right click on the adb.exe file and select Properties. Once that comes up, you'll need to select the compatability tab on top and choose run in 'Windows XP Service Pack 2' mode (sorry I'm at work and don't have access to my win7 machine). Then click ok and it should run in compatability mode.
Then just follow the flash instructions from the link drcrawfo posted up and you should be good to go!
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
ok so idk why but i decided to try taking out the sd card and then when i did the flash recovery cwm thing a whole list of commands came up in the command prompt and i have no clue if thats good or bad or what command i should pick
ill list a few just to see if that helps you guys in helping me out
update <filename>
flashhall
flash <partition> [ <filename> ]
and a few more then there were options that followed
edit: and now for somereason it doesnt flash again but if i do fastboot recovery i still get all those options so is there a way to get the cwm to flash through that way
simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
Hmmm..so you have all your files setup in the same folder and when running the commands from cmd they don't do anything? Does it saying anything is being sent?
This may be beyond my expertise. Have you tried posting in the clockwork mod thread in the development section?
Sent from my Incredible 2
I just want to mention that I didn't end up using the exact commands that are given from the wiki, that didn't seem to work for me. I had to mess around with it (including manually pointing cmd to where it was) to get it to work for me. Had all of the drivers, SDK stuff, the path and everything where they should have been. I hope you get this resolved.
nothing is working out for me this is not fun
same boat as you simple but I can still use my phone. I just gave up as none of the methods seemed to work.
simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
You need to open a command window, change the working directory to where adb/fastboot are located and then type adb.exe at the command prompt.
It sounds like you are trying to double-click the adb.exe from Windows Explorer.
yea i was double clicking, im not too savvy with this stuff, how do you change the directory and all that
Marvelc Problem SolvingWe all have problems with our Marvelc, so why isn't there a guide for it? There is.
If you're having issues, check out my guide at http://teamblueridge.com/marvelc-problem-solving/ for how to fix the most common issues.
You don't have to live with a hard-to-manage Marvelc anymore.
Changelog:
May 24, 2012 10:12 PM EDT
Added a link to vbhtt's tutorial for solving different brick types.
July 19, 2012 8:04 AM EDT
Revised guide to say that all Marvelc HBOOTs can be S-OFF'd.
August 7, 2012 3:48 PM EDT
Revised to say how to fix <remote: not allowed>
Explain issues with Three-Vibe Brick
August 7, 2012 4:59 PM EDT
Link to guide on Team BlueRidge site.
Three Vibe Brick
So far, no 100% guaranteed method has been found to cure the infamous three-vibe brick. Your phone is presently in Qualcomm Diagnostics Mode
Click to expand...
Click to collapse
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.
vbhtt said:
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.
Click to expand...
Click to collapse
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)
kalaker said:
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)
Click to expand...
Click to collapse
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!
vbhtt said:
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!
Click to expand...
Click to collapse
Oh! I understand that! I was just trying to provide a common method that I had read. I understand you weren't saying I was wrong. I was actually about to add something about your tutorial, but I had another project I was working on.
Yes, my goal is that this can be a place to help most Marvelc users solve most of their problems with as many alternatives as possible while still being fairly noob-friendly.
Thank you for reminding me of your tutorial as it slipped my mind while I was writing this in the beginning!
Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks
CoLlisiionZz said:
Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks
Click to expand...
Click to collapse
What you need to do is download ClockWork Mod 5.0.2.8 from http://download.clockorkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvelc.img and then rename it to recovery.img. If you're on Windows, put it into the same directory as your ADB and fastboot commands. Next, you'll need to put your phone in fast boot mode. Go into HBOOT and choose "Fastboot" by scrolling with the volume keys and selecting with the power key.
Connect your phone to your computer.
Next, depending on the OS of your computer, launch Command Prompt (Windows) or Terminal (Linux/Mac). Navigate to the directory with recovery.img. Now type: fastboot flash recovery recovery.img and then power off your phone when it's done.
Now boot into recovery. Go to HBOOT and choose recovery. Now, get on your computer and find a ROM that you like (something fairly stable). Download it. Find Simon's super wipe. Download it.
Connect your phone to your computer (if you removed it earlier).
In recovery, scroll to Mounts and Storage. Go to USB Connect or something similar (it will be near the bottom). Then on your computer, place your desired rom and the super wipe. Remove the phone from your computer and choose "Go back" on your phone. Go back to the main menu.
Backup.
Flash the super wipe. Then flash your ROM.
Go back to the main menu and reboot.
Sent from my NookColor using XDA
Great!! thanks this seems legit I will try this as soon as I get to my PC uhm I have windows btw and have no clue how to put the cwm into my adb / fastboot directory but I will search more about it when possible thanks for your help
Well, if you're on Windows, you should have a directory like C:\Android\ or something like that.
If you're on a Mac just do:
Code:
fastboot flash recovery /path/to/recovery.img
If you want to have the file anywhere on Windows, you still need to have fastboot somewhere and then do the same command I just typed above.
For more instructions, follow the instructions in the guide under "I can't flash a custom recovery"
Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?
CoLlisiionZz said:
Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?
Click to expand...
Click to collapse
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.
kalaker said:
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.
Click to expand...
Click to collapse
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.
CoLlisiionZz said:
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.
Click to expand...
Click to collapse
That's what you want. Move them into a folder at the root of your hard drive (C:\) called "Android". (C:\Android\)
Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?
CoLlisiionZz said:
Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?
Click to expand...
Click to collapse
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.
kalaker said:
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.
Click to expand...
Click to collapse
Okay that's what I kind of thought so I tried typing fastboot flash recovery recovery.img
and it says
error: cannot load 'recovery.img'
it is placed in the same directory as the tools are too.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
Okay nvm I tried something and it worked!!!
I went and re downloaded your CWM on your tutorial and deleted the one I renamed and didn't rename it this time just kept it the way it was I then tried flashing it and success I'm now going to reboot my hboot and see if it worked but also I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on
CoLlisiionZz said:
Okay that's what I kind of thought so I tried typing I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1598143
I'm glad to hear you got it working!
A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2
insink71 said:
A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2
Click to expand...
Click to collapse
Right, a Goldcard (unless one is S-OFF or ENG) will be required. However, achieving a goldcard requires ADB access to your phone. (The Simple GoldCard tool reads a file in /proc/*/*/ I believe to get the CID required for goldcard.) Now, ADB access is quite difficult with a bricked phone as you cannot boot into Android (or recovery) and to get S-OFF you would need to borrow the HTC Wildfire S (it MUST be a Wildfire S) to get the goldcard required.
Even with what I just said, depending on how bad your phone is bricked (Flashing a GSM RUU, for example), you may have a 100% bricked radio, thus resulting in an entirely bricked HBOOT not allowing you flash a PG76IMG.zip.
Another idea I have is that the Marvel is a PG761**** for the model number, and an incorrect RUU is the most common brick for Marvelc. What may be an issue is that the Marvelc is a PG762**** model number. The current files we have for un-bricking are Marvelc, but the android-info.txt for modelid says PG762000, therefore a GSM HBOOT (especially a locked, RUU HBOOT) would not take that file as it is for Marvelc.
What I think would be necessary is: a goldcard + a PG76IMG.zip with a GSM android-info.txt, but Marvelc radio, ROM, HBOOT, etc.
This is my idea on how we may need to do this. However, as the GSM HBOOT cannot get S-OFF without XTC-Clip which we can't use due to a lack of SIM card slot.
To get a 100% working-in-all-methods 3-Vibe Brick Recovery Method, we are waiting for the people in the S-OFF thread to get a full software S-OFF. However, even with that, we may still have issues...
I have spent a lot of time thinking about this, actually. (I'm a planner; not a dev :crying: so I can't be of much help with the dev part.) However, if it ever becomes a Team BlueRidge project to fix this type of brick (or a project by any group) I will be happy to plan (but not test just yet).
Since now we're moving into a very difficult and not-so-noob-friendly as I am intending for this thread to be, it may be a good idea to either start a new brainstorming thread or to PM or IRC or something.
Anyway, those are my thoughts.
My other thread got screwed up. So, I just thought it would be easier to re-write it all over.
Some warnings:
-This is not a FULL unlock (S-OFF or to unlock your SIM card slot.)
-This WILL VOID your warranty.
-This will work with ANY version of HBOOT. Unless something has changed and I never update.........
-This is a how to for WINDOWS ONLY. Sorry Mac, Linux, and Unix. If someone knows how to do it VIA those ways, I'll add it in here.
-If you are logged out of HTC Dev at any time during the identifier period (1 - 5), just sign back in and don't click anything. It will automatically redirect you to the last page you were on.
-I am not responsible if you didn't follow a step correctly and your phone lights on fire, cracks into two, wants to destroy you, etc...
If you like to learn visually (like me) and would rather not go through my jumble of steps, check out this YouTube video. [link]
What you are going to need:
-A computer
-Fastboot and ADB [API] - [link] <-- These are applications I use to flash ROM's. They are in a .zip from me.
-HTC Drivers - [link] <-- Drivers HTC gives, couldn't find them on HTC's site.
-Android SDK - [link]
-microUSB cable, phone, and some time
STEPS TO ROOT: finally...
1.) You are going to want to head over to the HTC Dev[eloper] site ([link]) and make an account or sign in. Once you have done one of the two, you are going to want to click 'Unlock Bootloader,' then 'Get Started.' It will next ask you what device you are trying to unlock, click 'Droid Incredible 2 (Verizon)' then 'Begin Unlock Bootloader.' Then a pop up window will ask you if you are sure, just click 'Yes.' Then, another pop up window will appear, just tick the two boxes and press 'Proceed to Unlock Instructions.'
2.) Go to your phone. Take off the [back] battery door and remove the battery (don't hold the power button and make it a proper shut off, just rip the battery out. Then, put the battery back in. Once you have replaced the battery, hold the volume down button and the power button at the same time until a white screen shows up. You can use the volume rocker to highlight your selection, and the power button to select the highlighted selection. Right now, we want to highlight 'BOOTLOADER' and use the power button to select it. Next, grab your miniUSB cable and plug it into your computer to your phone.
3.) Next, make a folder on your computer in the C:\ Drive. In Windows Vista & 7, you can just go to Computer from the Start Menu and it will be labeled Local Disk (C:\). You can name the folder whatever you want, I am just going to name it Android. Next, you are going to want to download my ADB, Fastboot, and ADBAPI .zip file and place all three files into the Android folder. After you unzip the ADB/Fastboot folder, you are going to want to (if you have not already) download and install the Android SDK manager. You will need to install SDK tools [and I believe a version of Android?] After you have installed everything, you can go to the Start Menu again and type in 'cmd' in the search bar and press enter. Then type in the following: (Or you could take the easy way of going to your C:\ drive and shift-clicking the folder and press 'Open Command Window Here...)
Code:
cd C:\Android
4.) After you have got into Command Prompt and are in the \Android folder, type in the following:
Code:
fastboot oem get_identifier_token
You will then see a great big brick of random characters. Right click in the bottom right-hand corner of '<<<<< Identifier Token End >>>>>' and click 'Mark...' Hold down the left-mouse-button and select the great brick of text up until '<<<< Identifier Token Start >>>>' (don't highlight any of the 'INFO' things.) Then, right-click again and you will have the identifier token copied to your clipboard. Back on the HTC Dev site, it will ask you for your identifier; just paste the identifier in the box and it will send you an email with a .bin file (Unlock_code.bin) and just throw that into the folder with ADB and Fastboot.
5.) You are going to want to click the continue link that HTC Dev sent you as well to downloading the file. After you have finished downloading and put it in the folder, type in the following:
Code:
fastboot flash unlocktoken Unlock_code.bin
Once you have done that and pressed Enter, your phone will change screens. It will ask you if you are SURE you want to do this. Just press the volume rocker up and press the power button. Your phone will reboot and take you back to Android. It's normal and it doesn't mean it failed... Your phone is fine and it should have went OK if you followed the steps. We are done with HTC Dev now, so you can close it.
6.) Next thing we are going to want to do is flash ClockWorkMod (CWM) Recovery onto your phone. You are going to want to download the .iso for CWMR and flash it to your phone (download link [link].) After you are done downloading the .iso, place it into your ADB and Fastboot folder. Once your phone has finished starting up, take the battery out again and put it back into HBOOT mode (step 2.) You are going to want to go back into FASTBOOT (step 2, again) and flash the recovery by doing the following:
Code:
fastboot flash recovery recovery(press TAB)
Once you press enter and fastboot says it has completed, it will just have the Fastboot screen. Just highlight 'Bootloader' and press the power button. Next, to make sure it worked... Scroll down to 'Recovery' (which is right under Fastboot) and select it. The HTC screen should show and then CWMR should come to life.
7.) This is where the real magic happens. We are going to install SuperUser on to your phone now. Reboot your phone into regular Android. Now, you can plug it into the computer and make it a disk drive or pop out the miniSD card and put it into a converter. Now, you are going to want to download SuperUser ([link] - make sure your scroll down to the .zip dowload) and put it onto the miniSD (I recommend not putting it in any folders so it is easy to find.) Now, put your phone back into CWMR (step 6.) Now, use the volume rocker to scroll down to 'install .zip from sd card' and press the power button. Now, find the SuperUser.zip (or whatever it is named) and press the power button. The 'yes' to install it is in the middle of all the 'no' options, use the volume rocker to select 'yes' and press the power button. Wait for CWMR to finish, and in the meantime... Just stare at your phone. After you have finished installing SuperUser, restart your handset into Android. Once it has finished restarting, go into the app drawer and find the SuperUser app. Press the 'menu' button and tap 'Settings.' Scroll down to 'Su Binary x.x.xx' and tap it. On the bottom it will say 'Update Binary,' just tap that and it will do its 'magic.' Once SU has finished updating Binary, you have a rooted DINC2.
If you need any help, please let me know here, or on Twatter (@Rumor0922)
Updated post. Finished the guide. Hope you guys enjoy.
thanks for your guide - I'm needing to get something fresh on my wife's DI2...and I'm not as savvy with the HTCs as I am with my GNex.
The problem I have initially run into is the JDK - I have it installed....but whenever I try to install the Android SDK, the installer tells me that it does not recognize an installed JDK...
Also, I did notice that your Fastbook & ADB link is not active - is it obsolete now?
Thanks again, hopefully I can get this puppy running smoothly soon
jegawhat said:
thanks for your guide - I'm needing to get something fresh on my wife's DI2...and I'm not as savvy with the HTCs as I am with my GNex.
The problem I have initially run into is the JDK - I have it installed....but whenever I try to install the Android SDK, the installer tells me that it does not recognize an installed JDK...
Also, I did notice that your Fastbook & ADB link is not active - is it obsolete now?
Thanks again, hopefully I can get this puppy running smoothly soon
Click to expand...
Click to collapse
Android SDK includes fastboot and adb, so it isn't necessary. Are you sure you have the JDK installed? What version? I know OpenJDK was giving me trouble so I had to switch to the official JDK.
Sent from my Transformer Pad TF300T using Tapatalk 2
prototype7 said:
Android SDK includes fastboot and adb, so it isn't necessary. Are you sure you have the JDK installed? What version? I know OpenJDK was giving me trouble so I had to switch to the official JDK.
Sent from my Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Yep, just tried to reinstall 7u7 from the oracle site....no dice with SDK. Weird. I'll try with another PC to see if my laptop just licks
I added the ADB and Fastboot link, I thought it was already added... So, that is my fault. And like prototype said, Android SDK also includes ADB and Fastboot. Hope the best to your wife and the phone.
getting error!
EVoorhees said:
I added the ADB and Fastboot link, I thought it was already added... So, that is my fault. And like prototype said, Android SDK also includes ADB and Fastb7Aoot. Hope the best to your wife and the phone.
Click to expand...
Click to collapse
Hey guys im trying to root this phone with your instructions so I can use it for straight talk. Any who this error is popping up in cmd
<bootloader> [err] comand error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
any help would be great and much appreciated!
how to de odex a rom
is there an easy way
thanks.
casseer15 said:
how to de odex a rom
is there an easy way
thanks.
Click to expand...
Click to collapse
www.google.com
Sent from my Incredible 2 using Tapatalk 2
Take it to the house said:
Hey guys im trying to root this phone with your instructions so I can use it for straight talk. Any who this error is popping up in cmd
<bootloader> [err] comand error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
any help would be great and much appreciated!
Click to expand...
Click to collapse
This isn't for a SIM CARD tray unlock. It's just to root you phone and get ROMS and SU apps on it. Look around for a SIM unlock.
Sent from my HTC Incredible 2 using xda premium
6.) Next thing we are going to want to do is flash ClockWorkMod (CWM) Recovery onto yoour phone. You are going to want to download the .iso for CWMR and flash it to your phone (download link [link].) After you are done downloading the .iso place it into your ADB and Fastboot folder. Once your phone has finished starting up, take the battery out again and put it back into HBOOT mode (step 2.) You are going to want to go back into FASTBOOT (step 2, again) and flash the recovery by doing
Click to expand...
Click to collapse
the following:
In my download folder this shows up as an image file, is this right?
Does this mean that C: Android folder I created in the beginning of the guide? If not, where am I supposed to place it?
Does flashing it to my phone mean simply copy/pasting this cwm image file into the adb and fastboot folder?
Sorry guys I've been lurking for weeks. Successfully rooted my galaxy nexus and that was a breeze compared to this!
JimHTP said:
the following:
1.) In my download folder this shows up as an image file, is this right?
2.) Does this mean that C: Android folder I created in the beginning of the guide? If not, where am I supposed to place it?
3.) Does flashing it to my phone mean simply copy/pasting this cwm image file into the adb and fastboot folder?
Sorry guys I've been lurking for weeks. Successfully rooted my galaxy nexus and that was a breeze compared to this!
Click to expand...
Click to collapse
1.) Yes, an .iso file is a disk image.
2.) I personally like to place it in the C:\ Drive, but people put it where ever they want to.
3.) Yes, just put that in the folder with Fastboot and ADB[API.]
Please fadtboot install as administrator in pc?
Sent from my E15a using xda premium
It shouldn't have to install. You have to use Fastboot VIA Command Prompt.
Sent from my Incredible 2 using xda premium
Ok i try thanks
Sent from my E15a using xda premium
Here this message its in spanish sorry
Sent from my E15a using xda premium
kdrumwork said:
Here this message its in spanish sorry
Click to expand...
Click to collapse
English equivalent: "fastboot" is not recognized as an internal or external command, operable program or batch file.
That's happening since you're still in the Administrator's directory - C:\Documents and Settings\Administrador\.
You need to use the "cd" command to change to the directory where you downloaded fastboot. Then you'll be able to use that command.
Ok thanks i try this bro :thumbup:
Sent from my E15a using xda premium
anyone have any trouble with the new twrp 2.3.1.0 on here?
The Dropbox link for the drivers is empty. Can you put a new one up?
Phone Was working fine on latest PA rom until battery died. Upon charging and rebooting up, the Rom some how got corrupted i guess, because it now just boots logo forever. I don't have any roms on the device itself so can't reinstall anything through recovery to try to fix whatever may have got corrupted. I know there is a way to Side Load with TWRP, but am running into difficulties. I do have the drivers for the nexus installed. I can't directly drop files through windows because it doesn't read in recovery and read up upon researching the Side load function. So I downloaded the ABT bundle zip folder and placed it in C folder, but that's where i'm stuck. I've tried looking a few things up but every time i try to run Adb command in the platforms folder it just opens and closes within a second. not sure what i'm missing. i've tried looking at other ways but most other phones have the capability of just throwing it on to the SD card which helps other people. thanks in advance.
Tl:dr Need to get a rom file onto the Nexus, to install and repair my corrupted rom.
you run adb from COMMANDLINE, it sounds like you are trying to double click the adb.exe....that will never work. adb is a commandline tool
ok, i'm pretty much a noob, don't know how to do that but i'll google it first before i bug any more. thanks again.
Since you are using windows, while looking at the explorer window that contains the adb/fastboot exes, hold down shift and right click somewhere in the blank space within the folder...OPEN COMMAND WINDOW HERE
once you have a DOS prompt open in that location, type 'adb devices' without any quotes to see if your device is being recognized.
there is an entire thread dedicated to walking you through this whole process.
start reading here:
http://forum.xda-developers.com/showthread.php?t=1812959
this site contains all the info you need.
I googled it and got it set up and working. it does recognize my device. now i'm reading up on the command to send the zip file. seriously, thanks for the feedback. been sitting here for like 2 hours trying to figure this out without pulling out my hair and tossing the phone lol.
You could have just read the stickies... Why people don't get curious about things like "RETURN TO STOCK ON ANY GALAXY NEXUS VARIANT" or "ANDROID 101", I'll never understand.
a manta wrote this.
first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks
CrankyPants said:
first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks
Click to expand...
Click to collapse
Restore you stock ROM nandroid. Look for it in here COLLECTION of Stock backup's seeing as you really didn't bother to provide us with the relevant and more important information such as the CID and Main software version you were on before you decided to mess your phone up and I doubt you made a backup of your device before doing it.
Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.
I guess I will be the "bad guy" but why are you messing with your phone when you have no clue what you are doing?
Everyone starts somewhere. Im sure we all learned a lot of what we know now by making lots of stupid mistakes. This logic rings true for life... not just phones.
lucas.scott said:
Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.
Click to expand...
Click to collapse
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?
CrankyPants said:
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?
Click to expand...
Click to collapse
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.
Jyotirdeb said:
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.
Click to expand...
Click to collapse
How to install a custom recovery via adb and what is adb?
sorry I don't know anything
CrankyPants said:
How to install a custom recovery via adb and what is adb?
sorry I don't know anything
Click to expand...
Click to collapse
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.
I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.
leongwengheng said:
I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.
Click to expand...
Click to collapse
Good choice on the videos, these days reading is a bit to tedious for most people. Heck, they don't even read "STOP" on the STOP signs anymore, just drive straight past
I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app
leongwengheng said:
I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Good luck at school then and later on in your job
Lucky boy having such a commited community here. You could've quite easily ended up with a £600 paper weight. Might want to show some appreciation to everyone holding your hand through a process that you should've read about before doing anything. Must admit, I did like the 'I just kept hitting next without knowing what I was doing', that's probably the best thing I've read lol lol.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
BerndM14 said:
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.
Click to expand...
Click to collapse
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?
CrankyPants said:
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?
Click to expand...
Click to collapse
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.
BerndM14 said:
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.
Click to expand...
Click to collapse
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.
CrankyPants said:
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.
Click to expand...
Click to collapse
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?
BerndM14 said:
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?
Click to expand...
Click to collapse
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.
Jyotirdeb said:
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.
Click to expand...
Click to collapse
To get getvar all you'll need fastboot commands, will fastboot commands even work if he MIGHT not have enabled USB Debugging or for that matter haven't accepted the RSA key?
That's why I asked about the recovery as well though. I saw that on hasoon's toolkit the flashing of a custom recovery was like the next step on the process which means that this guy should at least have a custom recovery already installed.