[Q] Sort of bricked phone.. What can I do?

[Q] Sort of bricked phone.. What can I do? - HTC One X+

I managed to accidentally flash the BLADE boot.img for CM10.1 to my phone before I transferred the ROM across to my SD card.
Didn't think this was a problem.. went into recovery to Mount USB Storage. Didn't work, so I flashed TWRP to see if it worked on there. No luck.
Tried performing a restore of the full working stock sense and wiped caches so I could try to transfer it over the OS. again no luck.
I've even tried pushing the .zip file to the sdcard using adb (run cmd as admin and use 'adb push ROM.zip /sdcard/ROM/') with no luck. It just tells me the device isn't connected. The drivers are definitely installed (fastboot is working).
I'm all out of ideas. If anyone could point me in the right direction, I'd be grateful. Thank you!

Mounting usb storage does not work with MTP devices.
Sent from my HTC One X+ using Tapatalk 2

AndroHero said:
Mounting usb storage does not work with MTP devices.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Is there another way of accessing the SD Card through recovery?

No except adb, but that only works with twrp. Why not flash a stock rom, and copy the rom to the SD Card while booted into android.
Sent from my HTC One X+ using Tapatalk 2

You might not be able to directly access your sd card, but you can most likely use adb sideload to load the CM10.1 ROM onto your device and regain functionality. Check this out for more information: http://teamw.in/ADBSideload

NasaGeek said:
You might not be able to directly access your sd card, but you can most likely use adb sideload to load the CM10.1 ROM onto your device and regain functionality. Check this out for more information: http://teamw.in/ADBSideload
Click to expand...
Click to collapse
Yeah while I was waiting for replies. I did a lot of research into adb sideloading and I pretty much get it now.. Only problem is that I'm running Windows 8 which has a whole bunch load of problems with adb... can't get it to recognise my device even with the correct drivers installed. Followed a few guides on the internet, but to no avail.
Does anyone know of anything that works? Or do I have to install it all on a W7 PC?

petedavison93 said:
Yeah while I was waiting for replies. I did a lot of research into adb sideloading and I pretty much get it now.. Only problem is that I'm running Windows 8 which has a whole bunch load of problems with adb... can't get it to recognise my device even with the correct drivers installed. Followed a few guides on the internet, but to no avail.
Does anyone know of anything that works? Or do I have to install it all on a W7 PC?
Click to expand...
Click to collapse
Do you have the latest SDK downloaded from google? I can confirm on windows 8 sideload through command prompt works fine in the platform tools folder. This is through CWM in my experience. i have not messed with TWRP

Kraizk said:
Do you have the latest SDK downloaded from google? I can confirm on windows 8 sideload through command prompt works fine in the platform tools folder. This is through CWM in my experience. i have not messed with TWRP
Click to expand...
Click to collapse
I downloaded and installed it today.
I'll go through exactly what I've done..
- Installed Java SDK
- Installed Android SDK
- Installed platform tools and usb driver
- Installed HTC Sync
- Opened hasoon's toolkit for the One X+
- Booted into TWRP and selected Advanced > Side Load
- Used the side load button on the toolkit.
I've also tried pushing files using the command line directly and cd-ing to the platform tools folder. This is what brings up the error connecting to device message. I've also started getting messages about starting daemon? No clue what that means.

petedavison93 said:
I downloaded and installed it today.
I'll go through exactly what I've done..
- Installed Java SDK
- Installed Android SDK
- Installed platform tools and usb driver
- Installed HTC Sync
- Opened hasoon's toolkit for the One X+
- Booted into TWRP and selected Advanced > Side Load
- Used the side load button on the toolkit.
I've also tried pushing files using the command line directly and cd-ing to the platform tools folder. This is what brings up the error connecting to device message. I've also started getting messages about starting daemon? No clue what that means.
Click to expand...
Click to collapse
Ignore the toolkit. That thing is less than stellar. Open the platform tools folder in the android SDK directory (default should be C: Android) Place the ZIP file of the rom you wish to flash in this directory. Hold shift and right click in blank space in the android sdk folder. Select "open command window here" (or something along those lines, not at my desk). type "adb kill-server" and then type the command "adb sideload romname.zip"
I recommend using CWM as I know this works on that. I do not use TWRP. You are welcome to try it with TWRP though.

Kraizk said:
Ignore the toolkit. That thing is less than stellar. Open the platform tools folder in the android SDK directory (default should be C: Android) Place the ZIP file of the rom you wish to flash in this directory. Hold shift and right click in blank space in the android sdk folder. Select "open command window here" (or something along those lines, not at my desk). type the command "adb sideload romname.zip"
I recommend using CWM as I know this works on that. I do not use TWRP. You are welcome to try it with TWRP though.
Click to expand...
Click to collapse
I have tried this method before too. It brought up the error message. I'll try it again in a minute and let you know. I'll also try it on CWM, but I read somewhere that CWM didn't support it? TWRP 100% does. It has an option for it in GUI.
EDIT: my android sdk in burried in Users/x/AppData/Local/Android/ .. Should I re-install in C:\Android ?

petedavison93 said:
I have tried this method before too. It brought up the error message. I'll try it again in a minute and let you know. I'll also try it on CWM, but I read somewhere that CWM didn't support it? TWRP 100% does. It has an option for it in GUI.
EDIT: my android sdk in burried in Users/x/AppData/Local/Android/ .. Should I re-install in C:\Android ?
Click to expand...
Click to collapse
That sounds like it is in the wrong place. That is usually a temporary folder. Check your c drive, it may also be labeled adt bundle and may be in program files. Sideload is an option in CWM by lloir by default which can be found in the original development section.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
Alternatively after rereading your OP. If you have not wiped anything you could just flash your old boot.img

Kraizk said:
That sounds like it is in the wrong place. That is usually a temporary folder. Check your c drive, it may also be labeled adt bundle and may be in program files. Sideload is an option in CWM by lloir by default which can be found in the original development section.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
Alternatively after rereading your OP. If you have not wiped anything you could just flash your old boot.img
Click to expand...
Click to collapse
About to reinstall the Android SDK (uninstalled and rebooted PC). I should install it to C:\Android ? (This folder doesn't exist currently)
I've also never set the environment variables as the Android SDK installed fine. Should I set these?
Also tried that.. it just hangs

petedavison93 said:
About to reinstall the Android SDK (uninstalled and rebooted PC). I should install it to C:\Android ? (This folder doesn't exist currently)
I've also never set the environment variables as the Android SDK installed fine. Should I set these?
Also tried that.. it just hangs
Click to expand...
Click to collapse
Download the android SDK bundle from google and install to C: Android, if it does not exist let it create it (i would still bet it is somewhere in your C drive but ok). I do not know what comes stock but i typically launch the SDK (NOT ECLIPSE) and allow it download all of the files associated with android (probably not needed). There should be an sdk folder inside the c android folder. in that is the platform tools folder. This is where you will open your command window and run the previously mentioned commands.

Kraizk said:
Download the android SDK bundle from google and install to C: Android, if it does not exist let it create it (i would still bet it is somewhere in your C drive but ok). I do not know what comes stock but i typically launch the SDK (NOT ECLIPSE) and allow it download all of the files associated with android (probably not needed). There should be an sdk folder inside the c android folder. in that is the platform tools folder. This is where you will open your command window and run the previously mentioned commands.
Click to expand...
Click to collapse
Trying the sideload now

petedavison93 said:
Trying the sideload now
Click to expand...
Click to collapse
If it is CWM give it a few minutes (literally like 5). Never used TWRP but it could take some time as well.

Kraizk said:
If it is CWM give it a few minutes (literally like 5). Never used TWRP but it could take some time as well.
Click to expand...
Click to collapse
Nothing came up for the kill-server command but it did pause.. so I'm guessing it did something.
The rest ran pretty quick but the phone hasn't received anything and is just sitting there (using CWM to keep my battery charged)

petedavison93 said:
Nothing came up for the kill-server command but it did pause.. so I'm guessing it did something.
The rest ran pretty quick but the phone hasn't received anything and is just sitting there (using CWM to keep my battery charged)
Click to expand...
Click to collapse
You could flash the stock recovery and run the RUU

Kraizk said:
You could flash the stock recovery and run the RUU
Click to expand...
Click to collapse
Very quick guide? I knew this was a possibility, but I've never had to do it until now. Thank you so much for the help btw
Although this still doesn't solve my problems with adb

petedavison93 said:
Very quick guide? I knew this was a possibility, but I've never had to do it until now. Thank you so much for the help btw
Click to expand...
Click to collapse
Flash the stock recovery (I do not have this as you appear to be on the international variant). Download your RUU (search the forums, I know it is here somehwere but the usual htcruu.com is now down....) boot into your boot loader and run the command "fastboot oem lock" Hit the power button to select hboot from the list and then just run the executable.

Kraizk said:
Flash the stock recovery (I do not have this as you appear to be on the international variant). Download your RUU (search the forums, I know it is here somehwere but the usual htcruu.com is now down....) boot into your boot loader and run the command "fastboot oem lock" Hit the power button to select hboot from the list and then just run the executable.
Click to expand...
Click to collapse
Can't relock the bootloader without working drivers.. this is beyond annoying now ¬.¬
EDIT: Relocked but not enough battery to flash RUU. Do I just run the RUU from the computer while the phone is at the home menu in the bootloader?
I'm using a batch file to charge the device over night. Will try again tomorrow.

Related

Update USB Drivers?

I recently rooted my Eris and I'm unable to flash a custom recovery because I can't get the USB drivers to update with those found in the SDK files. When I try to update the drivers Windows tells me that I have the most up to date drivers installed. It's because of this I cannot see my phone in the command prompt and can't get the custom recovery to work.
Has anyone tried putting the recovery files on their SD and using a terminal emulator?
Any ideas on updating the USB drivers?
If I flashed a custom Rom (as risky as that is without a recovery) could I then use nandroid or some other recovery? Or would I still need to use SDK?

joshw0000 said:
I recently rooted my Eris and I'm unable to flash a custom recovery because I can't get the USB drivers to update with those found in the SDK files. When I try to update the drivers Windows tells me that I have the most up to date drivers installed. It's because of this I cannot see my phone in the command prompt and can't get the custom recovery to work.
Has anyone tried putting the recovery files on their SD and using a terminal emulator?
Any ideas on updating the USB drivers?
If I flashed a custom Rom (as risky as that is without a recovery) could I then use nandroid or some other recovery? Or would I still need to use SDK?
Click to expand...
Click to collapse
download htc sync that should fix ur problem , it did for me

Yes HTC sync updated mine as soon as your phone is acknowledged by HTC sync it should update your usb drivers

FYI HTC sync did NOT work for me on Windows 7. I had to do some pretty annoying stuff to stop windows from installing the regular drivers automatically. If HTC sync doesn't work I can try to help.

If HTC Sync doesn't help, try the following steps.
1. Unplug your Eris from the PC
2. Open Device Manager and delete the Android device
3. Reboot your PC
4. Once in Windows, connect your Eris
5. The drivers should load automatically, if not point it to the SDK drivers folder
Good luck!

Any more ideas
First I tried downloading HTC Sync on my laptop (running Vista) and that didn't do it. Then I deleted the drivers and tried to manually download them back with the ones in the USB folder of SDK and still it wouldn't work.
So I started over and downloaded SDK and Java to my pc (Windows 7) and tried to update the drivers with the ones found in SDK and it wouldn't let me. So I deleted the drivers, unplugged my phone, and plugged it back up. Before I could attempt to direct it to download the intended USB drivers, Windows 7 had already updated with the drivers of it's choice. I can't win for losing.

If you don't mind using one of those "Live" Linux CDs, you could install the recovery using fastboot.
No need to install anything on the PC, and no drivers are needed for Linux, no SDK, no Java, no adb; just make sure to run fastboot as root.
The downloads of fastboot and the Amon_RA recovery are small, so they will easily fit in /tmp.
bftb0

I've never used Linux but I'm willing to try. Please tell me more. Are there "how tos" for this?

When you have your phone plugges in do you have it set to "charge" or "sync"? I know all the how to's say yo have it set to charge only but the inly way my computer ever finds my phone is if it us set to sync.
-------------------------------------
Sent via the XDA Tapatalk App

I set it to charge. I was finally able to install the correct driver. I selected a Google driver from the list it gave me (which my computer did not like) then went back and updated the drivers with those found in the tools usb folder of SDK. IT FINALLY LET ME!
Now I have a new problem. I'm using the command prompt and trying to create a custom recovery. I set it to the tools directory in SDK (where the flash and recovery images are) and I'm entering the commands exactly like the "how to" instructions have them. I keep getting "adb: not found" errors.
Can anyone tell me what I'm doing wrong?

joshw0000 said:
I've never used Linux but I'm willing to try. Please tell me more. Are there "how tos" for this?
Click to expand...
Click to collapse
Well, in the long run it is probably a good idea to resolve the driver install problems you are having on your PC, because it is very useful to have "adb" around, even if you are already rooted and have the ROM of your choice installed.
But, if you would like to do this, here's an outline below. Note that the point of the "Live" CDs is that you are not installing Linux on your machine, you are just booting it directly from the CD - the OS and hard drive on your PC are untouched.
1) Download an ".iso" file from your favorite Linux distro [ 3 ] for their "live" CD. (BIG download, usually 600+ MB)
2) Burn the .iso file to a CD as a bootable CD. (Most decent CD/DVD burner programs know what an .ISO file is, but might refer to them as a disk image).
3) Boot your PC off it! (You might need to hit a key on your PC right after you power it on to go into a boot menu, or the BIOS setup to change the boot order so your PC will try to boot from the CD/DVD before it tries the hard drive).
4) Copy the fastboot [ 1 ] executable for Linux and the Amon_RA recovery image [ 2 ] to /tmp "somehow" - you could just download it using the Linux browser if your network come up automatically (wired ethernet), or you could put them onto a USB key beforehand, and plug that in after Linux has booted; it should mount automatically.
5) Then, open up a terminal window and become root. (Type either "su" or "sudo /bin/bash" - depends on the Linux distro)
6) Attach your (well-charged) phone to the phone via USB, and power it up in fastboot mode (Send+End simultaneously)
cd /tmp
chmod 755 fastboot
md5sum recovery.img (check file sig)
./fastboot devices (check to see you are connected)
./fastboot flash recovery recovery.img
Obviously, if you need to look something up on the internet, it is useful to be networked, so you can use a web browser. The Linux boot will try to autoconfigure network interfaces automatically, but this is going to be most straightforward with a wired connection (Ethernet). Alternatively, if you have another PC or laptop nearby, you could use that.
Good luck.
Edits:
[ 1 ] Find Linux version of fastboot from HTC midway down this page - md5sum 9851bb6ad29cd4b60c9ba9d011ba9efd
[ 2 ] Amon_RA's recovery is located on this XDA page - md5sum e3932991f097993602af3c7a4b61a4f8
[ 3 ] Ubuntu's Current (x32) CD for v10.04 this page
NOTE: This CD is both a "Live" CD and an Install CD. You DO NOT WANT TO INSTALL ANYTHING; you are using the "Live" CD function - see the "show me how" link under Item #3 ("Try It!") on the above linked page
[ 4 ] Various OpenSuSe 11.2 Live CDs

Thanks for the info. I was able to get my drivers installed and run a nandroid recovery. Then I think I bricked my phone:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.

joshw0000 said:
Thanks for the info. I was able to get my drivers installed and run a nandroid recovery. Then I think I bricked my phone:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
Click to expand...
Click to collapse
First, relax and take a deep breath; everything's going to be fine.
In the recovery main menu, there is an Item called something like "MS-USB toggle" or something like that. It does not use the adb driver, it uses a standard "Mass Storage Device" USB driver already on the PC. The purpose of this function is to make the SD Card mount on the PC when the Amon_RA recovery is running.
Try that - it should work.
Then, download a conservative ROM such as Ivanmmj's Official 1.0 alpha, or Jcase's "Plain Jane", and copy it to your SD card.
After you have done that, make sure to check the MD5 sum of that .zip file on the SD card. (You should be doing this already).
Then, cleanly dismount the USB drive from the PC with the "Safely Remove Hardware" thingamabob, and toggle "off" the MS-USB toggle on the phone. Return to the main menu, wipe /data, and then flash the "conservative" ROM.
Then boot the conservative ROM just to verify everything is OK.
Next, Backup anything from the SD card that you don't already have (this step might be optional), and boot into recovery, and unpartition your SD card so that the only thing that is there is the VFAT partition.
For the moment, I'll give you some advice: f*ck A2SD. You need to gain some familarity with how the various versions of a2sd work before you start using it..
Very likely you were just stuck in a boot loop created by the re-partitioning you performed after initial configuration of a ROM that uses a2sd. Frankly, it is easy to create conditions for this, especially if you switch between ROMs that use different versions of a2sd, and/or don't understand that certain versions are not correctly backed up with Nandroid at the moment (e.g CLB).
bftb0

Go in to the start menu of your computer or laptop right click on computer and go down to properties and open it up look to the right and you will see something that says advanced system settings click that and it will open up another window for system properties.. Okay look at the bottom of that small window you will see something that says environmental variables, click that. Now you want to scroll through the system variables and find the one that says "path" you want to change that to you ";C:\android-sdk-windows\tools" and save it.. That is where your adb file or app is in your sdk tools folder, so when you open up a command prompt type in adb devices it may say something about killing daemon starting successful.. Don't worry just type it in again you should get your phones serial number thats when you know your good and you can start talking to your phone.. You can try a simple command like adb reboot and it will reboot your phone.. All else fails and you do this and your phone is responding but you can get anything to run in the command prompt type with 1 space cd then another space and then copy and paste "C:\android-sdk-windows\tools" that.. So it will look something like this
cd C:\android-sdk-windows\tools.. That should def do the trick.. Or absolute worst case scenario and you want to make it real easy and not have the fun of doing all the hard but fun work just use the "all in one root script" it will root your phone and it will also install "amon RA recoveryv1.6.2"... Hope this helps you out. LoL I know its long but yo dude I went through the same hell and I finally got everything where I want it!!!!!! Also make sure your HBOOT is under 1.49, if you have 1.49 you cant root... For example 1.46 your good...

Need rooting help

I have debugging on , disc drive, installed sdk manager, htc drivers , download the fr3vo file and try to run and get this ,,,, What am i missing

Arnezie said:
I have debugging on , disc drive, installed sdk manager, htc drivers , download the fr3vo file and try to run and get this ,,,, What am i missing
Click to expand...
Click to collapse
Instead of disk drive put it in USB charge only. Also if it still doesn't work, restart the phone and try again. Let me know if your still having problems

Oh also, I just looked at your picture, your adb service is not running. Open command prompt and change your directory to where adb is. Typically something like C:/android/android-sdk/platform-tools.
Then type adb devices or any other command and that should start up adb. Once again let me know if you have any questions

Isn't this right?

It very well could be. Mine is set up slightly different. But go into the sub folders and you should find one named tools or platform tools and one will contain adb. So you just need to find adb.

BDawgTrap said:
It very well could be. Mine is set up slightly different. But go into the sub folders and you should find one named tools or platform tools and one will contain adb. So you just need to find adb.
Click to expand...
Click to collapse
? I am not sure adb is installed right, how do I know

By going into the sub folders of your android sdk going into tools or platform tools and it will be there. It's named adb.ext. ext being extension , I don't remember what the extension is. If you can't find it I would uninstall android sdk, go to the site http://developer.android.com/sdk/index.html , download the recommended package, install it and when it asks where you want to install it use C:/Android/android-sdk.......
It could also be in your program files. I would just reinstall if you don't find it easily...

Re downloading now

Make sure you uninstall and delete everything so It's not sloppy...

Is it suposed to take forever once you get to the installing archives part?

Ya there are a few things that take a while. I don't know exactly what parts because I usually just leave it for a while and come back when It's done. Did you install it to the right location like I said earlier?

Yes i installed it where you said, it is still installing.........

ok re installed , tried 4 more times , somthing just isnt right and I don't know what it is?????

Dude just use the post thats Easy Frevo w/ overclock and bloat remover..u plug in phone to computer in charge mode with usb debugging on and make sure phone screen is not on(but phone is) and hit like 2 buttons to root and 2 buttons to overclock..so much easier
EDIT>> Heres the one. http://forum.xda-developers.com/showthread.php?t=1158400

irishgreen said:
Dude just use the post thats Easy Frevo w/ overclock and bloat remover..u plug in phone to computer in charge mode with usb debugging on and make sure phone screen is not on(but phone is) and hit like 2 buttons to root and 2 buttons to overclock..so much easier
EDIT>> Heres the one. http://forum.xda-developers.com/showthread.php?t=1158400
Click to expand...
Click to collapse
You still need adb for that method , that is where i think somthing isn't right.

What is it saying? Have you got adb started? You need to be able to get into the command prompt and run adb commands. Once you can do that if it doesn't work there are a few workarounds you can try but you have to have adb working.

this is what it is saying

Adb still isn't running. Have you found where adb is located yet?

C:\Program Files (x86)\Android\android-sdk

U shouldn't
i dont think you really need to root your phone if you can't even set up adb .... for one you are not even in the correct directory ... u have to cd C:/android/android-sdk/platform-tools then type adb devices

Im going CRAZY trying to root!

Heres the deal. I have a MAC with a newly installed hard drive. On my old hard drive I had everything setup with SDK and Adb but that was when I had an HTC Hero. My problem is this: When in terminal my damn computer keeps prompting me for a password but it doesnt allow me to type anything except control C which aborts the program. It never was like that with the old hard drive.
2. Ive dl SDK for MAC unzipped it and saved it to my desktop and my hard drive.
3. When I click on tools it says "adb_has_moved.txt"
4. It says the adb tool has moved to platform-tools/ and if you dont see this directory in your SDK, launch the SDK and AVD manager and install "android SDK Platform-tools and also update my path environment variable to include the platform-tools/ directory, so I can execute adb from any location. What the heck does this mean and how do I fix it. Also how do I know if SDK is installed correctly.
5. I DL some version of eclipse that was recommended from SDK but I dont know how to use that either.
6. I have tried all the root methods shown here in XDA except the on with the Dock since I dont have a dock.
7. Also ADB does not recognize my device and my debug is selected. I cannot get it to find my device.
8. One last question when some instructions say unzipped and move the root exploit to /data/tmp/ is that the file labeled under sdcard/data or is it the one inside the Android Folder listed as "data"
Please anyone help if possible.

let me try that

Stupid question but How do I launch SDK?

laraiza said:
Stupid question but How do I launch SDK?
Click to expand...
Click to collapse
Make sure your phone has USB Debugging Mode enabled. Otherwise, adb will not recognize your device.
Check this thread: http://forum.xda-developers.com/showthread.php?t=879701
However, you will have to modify for MAC.
In my opinion the easiest way to root the Photon is still using the dock method. Otherwise, try the One Click Root method (Torpedo) as mentioned above. Then you don't have to worry about issuing all the commands.

I got it done I got it done. What I did was borrow my daughters windows netbook and the one click method worked on the first try. Thanks to all who replied. I will definitely hit your thanks buttons.
Sent from my MB855 using XDA App

im sorry.. my tool was a one click i dint think i needed to give it instructions.. especially teh part of how to run it on your computer... just fyi.. when invoking sudo (to do things as admin/root) on your computer. you are asked to enter in your password.. as a privacy/security feature it will NOT display any characters.. ergo it looks blank...
as you arent teh first one to run into this issue ill add instructions for mac users ( i know anyone running linux can figure out how to run a bash script, and windows users have a bat file after installing 209387249087 drivers... but they still figure it out ;P)

Stuck In CWM Recovery Loop...

Installed latest version of CWM..made backup of original rom...Rebooted System...No problem...Flashed CM9 per instructions...Full Wipe...Played with it for awhile...Backed it up...tried to restore Stock Rom ...went into CWM loop...Read a lot of threads and I still have drivers and Asus is seen in Device Manager with ADB Interface...So I tried Command prompts for 1a...and what I get is 'adb' is not recognized as an internal or external command,operable program or batch file...
Am I typin the command right ???...I never used ADB before...Came over from Epic Touch 4g Forum here...and I only used Odin...Could someone give me a clue if on on the right path of Unbrickin this thing...
Thanx...
BTW its Unlocked and of course rooted...

Your salvation is at hand:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Follow this guide. To the letter, very important you set the path correctly in the environment variables or you'll be going around in circles. Once it's done, you'll have a working ADB and fastboot environment, you will also want the "Universal naked USB driver" which can be found on this site.
Once you've got that up and running, try getting your system into fastboot protocol and type fastboot -i 0x0b05 reboot, if that works, then you've access to ADB and fastboot protocols, follow the commands given in solution 1a then to complete your recovery.
Hope this helps.

Hobbesian said:
Your salvation is at hand:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Follow this guide. To the letter, very important you set the path correctly in the environment variables or you'll be going around in circles. Once it's done, you'll have a working ADB and fastboot environment, you will also want the "Universal naked USB driver" which can be found on this site.
Once you've got that up and running, try getting your system into fastboot protocol and type fastboot -i 0x0b05 reboot, if that works, then you've access to ADB and fastboot protocols, follow the commands given in solution 1a then to complete your recovery.
Hope this helps.
Click to expand...
Click to collapse
Yep it was a Nandroid Backup...Im not at all familiar with ADB ...Just Odin which I use Rooting Phones...Ill give it a try...This is drivin me nuts...Just cant get ADB to work for me thru commands...Ill definitely do what you suggest...Thanx a lot Ill let ya know what happens...

Still gettin this when I run a command prompt
adb is not recognized as an internal or external command,operable program or batch file..Says the same for fastboot...Am I typin the commands right...
Installed driver and extracted the files from the download to my c part of the drive...Do I have to open anything in the download folder inorder for it to work or just extract everything like I did...

Didnt have the path of the extracted files in the right spot...Just had to change it...Wurked fine...Up and Runnin...Thanx a lot...Really appreciate it...

Help
ronny71 said:
Didnt have the path of the extracted files in the right spot...Just had to change it...Wurked fine...Up and Runnin...Thanx a lot...Really appreciate it...
Click to expand...
Click to collapse
What did you do? What files? I did literally the EXACT same thing to my prime. Please help. (Idk what to do with this driver download)

chrsbrrss said:
What did you do? What files? I did literally the EXACT same thing to my prime. Please help. (Idk what to do with this driver download)
Click to expand...
Click to collapse
Extract it if you haven't already.... put your prime into recovery .... plug it into the pc... in device manager find the prime and update the driver manually... point windows to the driver and your there...
For adb... you need to download that too I use the one in the nvfashpack... so... you extract the file.. with the window open... press and hold shift then right click in the window (nvflashpack folder, where the adb.exe file is) and select open command prompt here. Now you can use the adb commands... if your trying to push a file...it is best to put it in the same folder (nvflashpack)

Bootloader for Droid DNA

Hello Everyone,
New to the rooting Droids, but have an understanding of them. I have jailbroken all Apple products which i got tired of. Now i finally got myself the New DNA phone with verizon. my dilemma is i dont know how to get the bootloader unlocked http://forum.xda-developers.com/showthread.php?t=2109862 i read through this link on how to do so. but it just gives u the link to download the apk file but no idea on what to do next with it? which also ive been reading off this site how to root my phone. http://forum.xda-developers.com/showthread.php?t=2000896
I need of a bit of help if anyone has a min to help me that would be great.
what i dont understand off the first link what to do with the apk file do i put the zip file right on my DNA drive? or run it off the pc?? if so what programs do i need on my computer to unlock my bootloader.
"
What you need:
1.) a Droid DNA
2.) this attached APK
Instructions:
1.) Download apk (attached, cid.apk)
2.) run it (in your app drawer titled HTC DNA SuperCID
3.) reboot to bootloader and confirm you have SuperCID:
a.) fastboot oem readcid
"
that is all the post contains on how to get the supercid?
thanks again!

1. Access XDA from your phone and download the app. (It will show up in your downloads)
2. Install the app by opening it
3. Here's where I believe your main issue/question is. You need Android SDK, if you don't have it installed you can get it Here
4. Follow the instructions and set that up
5. Hold your power button and down on the volume rocker till your phone goes into the bootloader.
6. Plug your phone into your computer
7. While in CMD Prompt type Fastboot oem readcid and hit enter.
8. if you get a response along the lines of 111111 you're good to go.
9. Head over to HTCDev.com and follow the steps they give you
10. After following those steps your bootloader will be Unlocked
11. Flash CWM or TWRP (recoveries) [There are instructions in those threads on how to do that]
12. You should then be good to go and flash ROM's, etc.

access the XDA from the first link? i posted?? on myphone?
ok downloaded to my phone and installed the Apk file

Yes. From your phone go to the link with the apk. Click on the download for that apk, and it will show up on your phone.

ok i now i have it installed and booted to the bootloader screen, which i selected fastboot, and now i have the CMD open but the command you told me to input doesnt work just error message saying "fastboot" is not recongnized. i also have the adt extracted on my desktop.

xd4v3x said:
ok i now i have it installed and booted to the bootloader screen, which i selected fastboot, and now i have the CMD open but the command you told me to input doesnt work just error message saying "fastboot" is not recongnized. i also have the adt extracted on my desktop.
Click to expand...
Click to collapse
Fastboot is an ADB command. Did you install the android SDK to your computer, and follow the guide on how to set it up?
Edit:
Here's a guide on how to setup the SDK Guide

yes it completly installed for the APK software, so i used the "abd" command instead of the word fastboot?

xd4v3x said:
yes it completly installed for the APK software, so i used the "abd" command instead of the word fastboot?
Click to expand...
Click to collapse
Did you set the platform-tools folder to the root of your C: Drive? ADB (my bad, not ABD) uses commands. Fastboot is one of the commands it uses to talk to the phone. If you don't set it up correctly the command: Fastboot will not be recognizable. Double check with the guide I posted, that you have everything correctly setup.

yes i have it in C:\android-sdk-windows
but all i see in the folder is .metadata....

xd4v3x said:
yes i have it in C:\android-sdk-windows
but all i see in the folder is .metadata....
Click to expand...
Click to collapse
Ok, a couple questions...
1. Did you install HTC Sync? That installs the HTC drivers to your computer.
2. What version of Windowns (if you're on windows) are you running?

Yes i install the htc sync and i am running windows 7 x64.

xd4v3x said:
Yes i install the htc sync and i am running windows 7 x64.
Click to expand...
Click to collapse
Ok, go into the sdk folders. There should be a little android icon that says Android SDK or something along those lines. Open that up and it should ask you if you want to install some drivers. You need to install those. Once you do that everything should work.

OverDroid5 said:
Ok, go into the sdk folders. There should be a little android icon that says Android SDK or something along those lines. Open that up and it should ask you if you want to install some drivers. You need to install those. Once you do that everything should work.
Click to expand...
Click to collapse
I have thanked a couple of your posts because the OP hasn't and you have gone out of your way

ok so far what I have setup:
installed phone drivers on the wndows 7 - htc sync.
installed the CID.apk file on my phone.
installed the sdk software on my windows 7 64bit.
I reboot the phone to the bootloader screen.
but cant get the command prompt to work by using the "fast oem readcid"
what am I missing? I keep getting an error when running that command.
thanks again for everyone help so far.

You have to be in a folder that has the fastboot.exe file. Or you need to update your windows path so it recognizes the android sdk folders.
Your best bet is to create a new folder in C:\. For example C:\HTCbootloader. Then copy fastboot.exe, adb.exe, and AdbWinApi.dll into it. Then when you run 'cmd', type 'cd HTCbootloader'. From that point you should be able to type 'fastboot oem readcid'.

thanks I try that when I get home.

betterthancrimzon said:
You have to be in a folder that has the fastboot.exe file. Or you need to update your windows path so it recognizes the android sdk folders.
Your best bet is to create a new folder in C:\. For example C:\HTCbootloader. Then copy fastboot.exe, adb.exe, and AdbWinApi.dll into it. Then when you run 'cmd', type 'cd HTCbootloader'. From that point you should be able to type 'fastboot oem readcid'.
Click to expand...
Click to collapse
This is correct. Also to setup a set path that you can access anywhere.
1. Right click on "Computer"
2. Go to properties
3. Click on Advanced System Settings
4. Click on Environmental Variables
5. In System Variables, Scroll to PATH
6. Select it and hit Edit
7. Do not change anything, in the current string, instead go to the very end
8. No spaces from where it ends. ;C:\(whatever you named the file with fastboot.exe, adb.exe, and AdbWinApi.dll)
9. Click ok, and you have a path setup, so no matter where you access cmd prompt from you can use adb commands.

I apologize by attempting to hijack this thread but the advice in here is superb... Alright gentleman I could use some help, I got my code from HTC and have followed the instructions with the utmost precision including the verification of my paths (using the same folder from the previous CMD during the unlock process) but no matter what I do I get the error...
"cannot load *** bin unknown error". Any ideas?

ok so i finally got the fastboot oem readcid, and it read 11111111 so im in a good spot so far.. but now i dont see any where, on whats the command to get the token. on this forum page. http://forum.xda-developers.com/showthread.php?t=2000896
thanks again!

xd4v3x said:
ok so i finally got the fastboot oem readcid, and it read 11111111 so im in a good spot so far.. but now i dont see any where, on whats the command to get the token. on this forum page. http://forum.xda-developers.com/showthread.php?t=2000896
thanks again!
Click to expand...
Click to collapse
Ok, Now that you have it reading 11111111 head over to HTCdev.com and follow the steps there. You're going to go to unlock bootloader and select other supported devices. It will guide you on how to get the token as well as how to unlock the bootloader.

Better Mobile App

welcome