Database Develop

[Q] Bricked phone?

I think I may have bricked my phone. It's a rooted htc hero cdma. I'm running cyogenmod on it and it was working fine, until using metamorph to apply some changes to the theme.
I went to reboot, and it now it won't load past the htc screen. Even when i try the key combination to put it into recover mode. I didn't install a nandroid backup, and i'd be fine with just completely wiping my phone. can someone please help me?

Have you tried flashing the ROM back over itself without wiping? Try that first, and if that won't work, do a full format and reflash the ROM and you should be good to go.
And just an FYI, you really can't fully brick your phone by flashing a ROM or theme. You can always get it back.

Do what ranger suggested.
To elaborate, I *think* as long as your phone turns on, it is not bricked. Specifically, as long as you can boot to recovery you can do whatever you need to do, be it make fixes or start from scratch again. (I think even if you can't boot to recovery, but it turns on, you can run the RUU ). The only way to brick is to flash a wrong/corrupt radio or anything below the radio level.

Wipe then reboot and wait. When you change the framework, initial boot takes longer.
Sent from my HERO200 using XDA Premium App

I can't even get to the recovery mode screen. it'll only take me to where i can select hboot, fastboot, or wipe. nothing else will load up past that.

What key combination are you using? Hold home then depress end key/power key until phone vibrates.
Sent from my HERO200 using XDA Premium App

Load the fast boot ruu flash
Done
zbach said:
I can't even get to the recovery mode screen. it'll only take me to where i can select hboot, fastboot, or wipe. nothing else will load up past that.
Click to expand...
Click to collapse
Sent from my HTC Hero CDMA using XDA App

mahalocat said:
Load the fast boot ruu flash
Done
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
I can't select that option. Sorry for being kind of new at this, it just loads a bunch of green letters down really quick, telling me it can't find HERCIMG.zip/HERCDIAG.zip files. under that, it says no image or wrong image?

zbach said:
I can't select that option. Sorry for being kind of new at this, it just loads a bunch of green letters down really quick, telling me it can't find HERCIMG.zip/HERCDIAG.zip files. under that, it says no image or wrong image?
Click to expand...
Click to collapse
I am guessing you're not s-off, try this:
http://forum.xda-developers.com/showthread.php?t=958968

il Duce said:
I am guessing you're not s-off, try this:
http://forum.xda-developers.com/showthread.php?t=958968
Click to expand...
Click to collapse
I don't see the command to run "fastboot oem rebootRUU"

zbach said:
I don't see the command to run "fastboot oem rebootRUU"
Click to expand...
Click to collapse
It's a cmd prompt for windows. Open your command prompt from windows, with the phone plugged in usb, and then follow the steps in the OP of that thread.

il Duce said:
It's a cmd prompt for windows. Open your command prompt from windows, with the phone plugged in usb, and then follow the steps in the OP of that thread.
Click to expand...
Click to collapse
it keeps telling me fastboot is an unrecognized command. i have to be doing something wrong here.

zbach said:
it keeps telling me fastboot is an unrecognized command. i have to be doing something wrong here.
Click to expand...
Click to collapse
did you do the adb command first, like it says?

il Duce said:
did you do the adb command first, like it says?
Click to expand...
Click to collapse
yeah, it won't recognize that either. i'm selecting the right path to my C drive too. the driver just isnt recognized :/

You have to go further than just the C drive you have to specify the path all the way to the android-sdk-windows directory. If your on Vista, find the folder, hold the shift key and right click. Then select open a command line here.
EDIT: Yeah you need the drivers installed as well.
I had this happen to me a week ago. Luckily the phone rebooted and I was able to re-flash another recovery using the terminal emulator.

wild1z said:
You have to go further than just the C drive you have to specify the path all the way to the android-sdk-windows directory. If your on Vista, find the folder, hold the shift key and right click. Then select open a command line here.
EDIT: Yeah you need the drivers installed as well.
I had this happen to me a week ago. Luckily the phone rebooted and I was able to re-flash another recovery using the terminal emulator.
Click to expand...
Click to collapse
okay, i'm in now. i'm on the rebootRUU black and silver screen on my phone, but when i go to flash another .zip file, it says can't upload. do i need to download one from somewhere, or place it in a different folder?
I'm on my computer working through my command prompt by the way.

zbach said:
okay, i'm in now. i'm on the rebootRUU black and silver screen on my phone, but when i go to flash another .zip file, it says can't upload. do i need to download one from somewhere, or place it in a different folder?
I'm on my computer working through my command prompt by the way.
Click to expand...
Click to collapse
I've never actually done this fyi, but I think you need the RUU from htc.com, it would probably be under support, then hero cdma? DL that, and input the command "fastboot flash zip correctnameofhtcRUU.zip" in your cmd.

okay, i found and am currently downloading the file. so i should just have to root it to my SD, then flash it, right?
I'm really hoping this works.

il Duce said:
I've never actually done this fyi, but I think you need the RUU from htc.com, it would probably be under support, then hero cdma? DL that, and input the command "fastboot flash zip correctnameofhtcRUU.zip" in your cmd.
Click to expand...
Click to collapse
still nothing. it only tells me its and error, and cannot load the .zip file.

zbach said:
still nothing. it only tells me its and error, and cannot load the .zip file.
Click to expand...
Click to collapse
I don't know where the file should be located, but your posts in the other thread will yield better answers, jason knows the way better than me, given he started the thread. Wait for his response. I assume the error has something to do with where you have the ruu and what path you need to specify in the cmd. Wish I could be of more help. Once you fix it and get back to rooted and such, I HIGHLY recommend you get s-off, its basically like idiot-proofing your phone (no offense) so you can fix anything.
sent from a series of tubes.

[Q] Cyanogenmod installation.

Hey all.
I understand that this thread is probably painful to read for you Desire C 'Guru's' but I am really interested in installing Cyanogenmod on my device, and I find it a little daunting, and can't find a good tutorial...
Do any of you know of a in-depth tutorial that I can use? If you could, that'd be greatly appreciated.
Thanks.

Storaxis said:
Hey all.
I understand that this thread is probably painful to read for you Desire C 'Guru's' but I am really interested in installing Cyanogenmod on my device, and I find it a little daunting, and can't find a good tutorial...
Do any of you know of a in-depth tutorial that I can use? If you could, that'd be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
First download cm 10 and gapps from here
http://forum.xda-developers.com/showthread.php?t=2265060
Here you go with the entire tutorial...read it and if any doubts ask without hesitating
http://forum.xda-developers.com/showthread.php?t=2132686
Hope it helps you!

Unlock boot loader. Then install custom recovery. Then flash either NOPE or Prometheus kernel via fastboot. The flash Cyanogenmod 10 via custom recovery. Then flash gapps via custom recovery. Then reboot and enjoy
Sent from my HTC Desire C using xda app-developers app

Thanks for the assistance so far.
I've spent the past little while attempting to unlock the bootloader, I'm following the instructions on HTC's website. It was working up until I have to type in: fastboot oem get_identifier_token.
When I type this in to the command prompt, it perpetually says "waiting for device..."
I've installed all the recent drivers, have all the software that HTC asks you to get, and have tried several different USB ports and still nothing.
So yeah.. I have no idea what the issue is here.

Storaxis said:
Thanks for the assistance so far.
I've spent the past little while attempting to unlock the bootloader, I'm following the instructions on HTC's website. It was working up until I have to type in: fastboot oem get_identifier_token.
When I type this in to the command prompt, it perpetually says "waiting for device..."
I've installed all the recent drivers, have all the software that HTC asks you to get, and have tried several different USB ports and still nothing.
So yeah.. I have no idea what the issue is here.
Click to expand...
Click to collapse
Where did you type the "fastboot oem....." Command???
Tell the accurate thing you did so that we can help u

warrior1208 said:
Where did you type the "fastboot oem....." Command???
Tell the accurate thing you did so that we can help u
Click to expand...
Click to collapse
Well, I created a folder called "Android" on the C Drive. Then, I headed into the command prompt and typed cd \Android. Once the command prompt was running from that folder I typed the "fastboot oem get_identifier_token" And it said "waiting for device". This was all while my device was powered on in the White bootloader screen (mental block, can't think of the official name) and developer mode was on. I'm at a loss and I really want to do this. xD

Storaxis said:
Well, I created a folder called "Android" on the C Drive. Then, I headed into the command prompt and typed cd \Android. Once the command prompt was running from that folder I typed the "fastboot oem get_identifier_token" And it said "waiting for device". This was all while my device was powered on in the White bootloader screen (mental block, can't think of the official name) and developer mode was on. I'm at a loss and I really want to do this. xD
Click to expand...
Click to collapse
Maybe the path you typed was wrong...try out this method it works!
Go to the folder named android on c drive and press 'shift+right mouse button'...when you see the options click on 'open command window here'
Then you will be brought to cmd and then just type the command fastboot oem...
With this you wont get the error!
If you still encounter any problem dont hesitate to ask

warrior1208 said:
Maybe the path you typed was wrong...try out this method it works!
Go to the folder named android on c drive and press 'shift+right mouse button'...when you see the options click on 'open command window here'
Then you will be brought to cmd and then just type the command fastboot oem...
With this you wont get the error!
If you still encounter any problem dont hesitate to ask
Click to expand...
Click to collapse
Thanks for the continued assistance.
I tried that method too, still no luck. Do I need to delete everything off the phone prior to attempting to unlock the bootloader? If so; do I do a "Factory Reset" or a "Full wipe"?

Storaxis said:
Thanks for the continued assistance.
I tried that method too, still no luck. Do I need to delete everything off the phone prior to attempting to unlock the bootloader? If so; do I do a "Factory Reset" or a "Full wipe"?
Click to expand...
Click to collapse
Did you enable USB Debugging on your phone?

Storaxis said:
Thanks for the continued assistance.
I tried that method too, still no luck. Do I need to delete everything off the phone prior to attempting to unlock the bootloader? If so; do I do a "Factory Reset" or a "Full wipe"?
Click to expand...
Click to collapse
No a wipe is not needed...did you try aashay's response???
Make sure your usb debugging is on in settings under development options and fastboot is unticked...

Try uninstalling htc sync on your PC.
Sent from my HTC Desire C using xda app-developers app

warrior1208 said:
No a wipe is not needed...did you try aashay's response???
Make sure your usb debugging is on in settings under development options and fastboot is unticked...
Click to expand...
Click to collapse
Yes, USB debugging was definitely enabled. =I I removed HTC Sync, and also gave the "Easy unlock Bootloader tool" a go, and I continue to get < waiting for device > http://i.imgur.com/inIM34a.png

Storaxis said:
Yes, USB debugging was definitely enabled. =I I removed HTC Sync, and also gave the "Easy unlock Bootloader tool" a go, and I continue to get < waiting for device > http://i.imgur.com/inIM34a.png
Click to expand...
Click to collapse
Make sure it says fastboot USB on phone and not fastboot or hboot
Sent from my HTC Desire C using xda app-developers app

uchihasparky said:
Make sure it says fastboot USB on phone and not fastboot or hboot
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
It does, and still no luck.. I have no idea why this isn't working.

Ohh I get what the problem is.. You didn't copy the executables in your android folder..
Run the fastboot command in the 'platform tools' folder in C:\Program Files\Android.

Ummm wouldn't it just say: "fastboot not recognized as a command"?
Sent from my HTC Desire C using xda app-developers app

Any other ideas what the issue could be here? I've been constantly trying and checking for errors for 2 days now.. I'm either missing something obvious (I've tried multiple guides to doing it) or there's some other issue...

Storaxis said:
Any other ideas what the issue could be here? I've been constantly trying and checking for errors for 2 days now.. I'm either missing something obvious (I've tried multiple guides to doing it) or there's some other issue...
Click to expand...
Click to collapse
Alright, then download this fastboot files and adb...extract in a folder in c drive...
https://skydrive.live.com/?cid=e45252246171a8f9&id=E45252246171A8F9!113&authkey=!ANYwFTBtKm58Zcc
Next open up the folder, press shift+right mouse button and select open command window here
Refer To this guide ahead
http://forum.xda-developers.com/showthread.php?t=2250122

warrior1208 said:
Alright, then download this fastboot files and adb...extract in a folder in c drive...
https://skydrive.live.com/?cid=e45252246171a8f9&id=E45252246171A8F9!113&authkey=!ANYwFTBtKm58Zcc
Next open up the folder, press shift+right mouse button and select open command window here
Refer To this guide ahead
http://forum.xda-developers.com/showthread.php?t=2250122
Click to expand...
Click to collapse
Followed the tutorial exactly, still get < waiting for device >
I think this is the stage where I give up. xD

Never give up!!! Cenation
Sent from my HTC Desire C using XDA Premium 4 mobile app

[SOLVED] Please help me save my device

Hello Guys,
I am in a huge problem. So my microphone isnt working and i need to send my device to HTC for repairs. I am S-off using rum runner and unlocked. I use TWRP recovery and restored my device to stock nandroid backup. I did fastboot oem lock after that and tried to flash the original rom ruu but i kept getting error 155 although it said relocked on the bootloader. My Hboot was 1.44 and now suddenly it is upgraded to 1.56 maybe coz i flashed ARHD 41?
All of a sudden my touchscreen stopped working too. I am pretty sure it is something to do with touchscreen drivers. I want to reflash a rom so i can come out of all this. Can someone please help me flash a rom using fastboot since i cant use my touch screen?
I used the command fastboot flash rom rom.zip but below is the error it gave me:-
c:\fastboothtc>fastboot flash zip rom.zip
sending 'zip' (1145618 KB)...
OKAY [ 51.894s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 51.931s
Someone please please help me.
Thank you

arzin said:
Hello Guys,
I am in a huge problem. So my microphone isnt working and i need to send my device to HTC for repairs. I am S-off using rum runner and unlocked. I use TWRP recovery and restored my device to stock nandroid backup. I did fastboot oem lock after that and tried to flash the original rom ruu but i kept getting error 155 although it said relocked on the bootloader. My Hboot was 1.44 and now suddenly it is upgraded to 1.56 maybe coz i flashed ARHD 41?
All of a sudden my touchscreen stopped working too. I am pretty sure it is something to do with touchscreen drivers. I want to reflash a rom so i can come out of all this. Can someone please help me flash a rom using fastboot since i cant use my touch screen?
I used the command fastboot flash rom rom.zip but below is the error it gave me:-
c:\fastboothtc>fastboot flash zip rom.zip
sending 'zip' (1145618 KB)...
OKAY [ 51.894s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 51.931s
Someone please please help me.
Thank you
Click to expand...
Click to collapse
You can move through the recovery and Rom installation with the volume and power buttons. Hope that helps.
Sent from my HTC One using XDA Premium 4 mobile app

BanBoo said:
You can move through the recovery and Rom installation with the volume and power buttons. Hope that helps.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flashed CWM recovery and was trying to mount storage via USB and that is not happening either. I tried adb sideload but it says no device found

arzin said:
I just flashed CWM recovery and was trying to mount storage via USB and that is not happening either. I tried adb sideload but it says no device found
Click to expand...
Click to collapse
try adb push <path of the file in system > /sdcard

[email protected] said:
try adb push /sdcard/rom.zip <path of the file in system >
Click to expand...
Click to collapse
Can you please explain this command a bit more?
I typed adb push/sdcard/rom.zip C:/fastboothtc and it did not work
rom.zip is what i renamed the ARHD rom and C:/fastboothtc is the location where the rom is kept

arzin said:
Can you please explain this command a bit more?
I typed adb push/sdcard/rom.zip C:/fastboothtc and it did not work
rom.zip is what i renamed the ARHD rom and C:/fastboothtc is the location where the rom is kept
Click to expand...
Click to collapse
I really messed it up sorry first of all
Code:
adb push C:\fastboothtc\rom.zip /sdcard
will do...

arzin said:
Can you please explain this command a bit more?
I typed adb push/sdcard/rom.zip C:/fastboothtc and it did not work
rom.zip is what i renamed the ARHD rom and C:/fastboothtc is the location where the rom is kept
Click to expand...
Click to collapse
I tried this command C:\miniadb_v1031>adb push rom.zip /sdcard/
it gives me an error as follows.
error: device not found
I am connected via USB and i have selected install Rom via Sideload in CWM. I just need a way to push the rom on my sd card

[email protected] said:
I really messed it up sorry first of all
adb push C:/fastboothtc/rom.zip /sdcard will do...
Click to expand...
Click to collapse
This did not work too

arzin said:
This did not work too
Click to expand...
Click to collapse
is ur device recognized...
If yes it has to work...
Code:
adb push C:\fastboothtc\rom.zip /sdcard

[email protected] said:
is ur device recognized...
If yes it has to work...
Code:
adb push C:\fastboothtc\rom.zip /sdcard
Click to expand...
Click to collapse
My device is not recognized. I went to device manager and saw an exclamation mark in other devices named one. I tried updating the drivers but i cant find any online. How do i get the drivers?

arzin said:
My device is not recognized. I went to device manager and saw an exclamation mark in other devices named one. I tried updating the drivers but i cant find any online. How do i get the drivers?
Click to expand...
Click to collapse
Try this drivers
and check whether it s recognized....
if not recognized then try
Code:
adb kill-server
Code:
adb devices
See whether this works......:fingers-crossed:

[email protected] said:
Try this drivers
and check whether it s recognized....
if not recognized then try
Code:
adb kill-server
Code:
adb devices
See whether this works......:fingers-crossed:
Click to expand...
Click to collapse
Both did not work. The problem is my computer is not recognizing my device. The drivers you provided dont open on my computer.. I will check this on my office computer tomorrow.

arzin said:
Both did not work. The problem is my computer is not recognizing my device. The drivers you provided dont open on my computer.. I will check this on my office computer tomorrow.
Click to expand...
Click to collapse
Found this by googling.....
this is the latest and the installation too went smooth

arzin said:
Both did not work. The problem is my computer is not recognizing my device. The drivers you provided dont open on my computer.. I will check this on my office computer tomorrow.
Click to expand...
Click to collapse
You mus have usb debugging enabled. Go to settings - info - Software information - more and push several times on build number. then go to settings and you can enabel usb debugging.
---------- Post added at 08:48 AM ---------- Previous post was at 08:43 AM ----------
Justin2003 said:
You mus have usb debugging enabled. Go to settings - info - Software information - more and push several times on build number. then go to settings and you can enabel usb debugging.
Click to expand...
Click to collapse
And than look on http://www.htc1guru.com/ for more info and stock ruu

Justin2003 said:
You mus have usb debugging enabled. Go to settings - info - Software information - more and push several times on build number. then go to settings and you can enabel usb debugging.
---------- Post added at 08:48 AM ---------- Previous post was at 08:43 AM ----------
And than look on http://www.htc1guru.com/ for more info and stock ruu
Click to expand...
Click to collapse
Can't do this since my touch screen is not workng and I wiped the device so I have no rom on it as of now

[email protected] said:
Found this by googling.....
this is the latest and the installation too went smooth
Click to expand...
Click to collapse
Thank you buddy but it still doesnt see the driver even after installing these. I guess i will try once on another computer. Any other solutions till then?

arzin said:
Thank you buddy but it still doesnt see the driver even after installing these. I guess i will try once on another computer. Any other solutions till then?
Click to expand...
Click to collapse
The only solution is to get ur phone recognized......
or else there is no way to communicate with ur device....
u tried
adb devices
Click to expand...
Click to collapse
from recovery right...????

[email protected] said:
The only solution is to get ur phone recognized......
or else there is no way to communicate with ur device....
u tried from recovery right...????
Click to expand...
Click to collapse
I guess so. Here is in detail what ive been doing:-
1. Connect phone via USB and i have no ROM nor any data on it right now since ive wiped the device.
2. Boot into recovery and then select adb sideload
3. Use all adb commands but it says no device found coz device is not being recognized right?
4. I am at work now and im trying on my office computer but i have one exclamation mark under other devices in device manager. It was the same on my Home computer. It just does not want to install drives for this "one" under other devices.

arzin said:
I guess so. Here is in detail what ive been doing:-
1. Connect phone via USB and i have no ROM nor any data on it right now since ive wiped the device.
2. Boot into recovery and then select adb sideload
3. Use all adb commands but it says no device found coz device is not being recognized right?
4. I am at work now and im trying on my office computer but i have one exclamation mark under other devices in device manager. It was the same on my Home computer. It just does not want to install drives for this "one" under other devices.
Click to expand...
Click to collapse
Yeah.....U did that right.....
Try to install it Manually following these steps ....choose from the attachment according to whether it 32-bit or 64-bit
Click StartStart button, right-click Computer, and then click Properties.
In the Tasks pane, click Device Manager.
User Account Control permission If you are prompted for an administrator password or confirmation, type your password or click Continue.
In Device Manager, locate the device for which you want to install the driver.
Note To display hidden devices, click Show hidden devices on the View menu.
Right-click the device, and then click Update Driver Software.
Click Browse my computer for driver software, click Let me pick from a list of device drivers on my computer, and then click Have Disk.
In the Install From Disk dialog box, click Browse, locate an .inf file for the device driver that you want to install, and then click Open.
Follow the steps in the Update Driver Software DeviceName dialog box to update the driver.

Thanks a ton [email protected] (bohot bohot shukriya). My phone finally came to life. I used some other driver but you really helped me and kept me going. I am attaching the drivers for someone in need sometime. Can you also help me downgrade my Hboot to 1.44 if that is possible? When i did Soff using rumrunner it just upgraded my Hboot to 1.56.
http://adbdriver.com/

[Q] HTC One, tampered, unlocked, S-ON, no OS, device not foun on laptop. Cluster****.

Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!

PrimalMK said:
Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!
Click to expand...
Click to collapse
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs

clsA said:
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs
Click to expand...
Click to collapse
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version of TWRP does not work. I have no preferences when it comes to OS's. A stock OS (is OS and ROM the same thing?) would be fine.

Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.

PrimalMK said:
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version does not work. I have no preferences. A stock OS (is OS and ROM the same thing?) would be fine.
Click to expand...
Click to collapse
Well your going to need adb / fastboot on your PC
use mine here >> https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip
and install the HTC Drivers here >> http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
unzip that to c:\ so you have c:\fastboot in windows explorer
now inside the folder you shift + right click / command prompt here
now you have a command prompt window type
fastboot getvar all
and post the result here / minus your serial number and IMEI
then i can find you the correct recovery and rom for your phone
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
PrimalMK said:
Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.
Click to expand...
Click to collapse
yes window 8 will be a problem till you get another hboot above 1.44/1.54
hboot 1.55 has no problem on windows 8 ( I use windows 8.1)

clsA said:
instructions
Click to expand...
Click to collapse
Downloaded fastboot, unzipped in c:
Drivers from that link are classed as malware. Trying to find earlier drivers/other mirror.

Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.

PrimalMK said:
Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.
Click to expand...
Click to collapse
this will work fine
just put TWRP and the Rom in the fastboot folder
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse

clsA said:
this will work fine
just put TWRP and the Rom in the fastboot folder
Click to expand...
Click to collapse
error: cannot open 'openrecovery.......img'
What to do?

PrimalMK said:
error: cannot open 'openrecovery.......img'
What to do?
Click to expand...
Click to collapse
is it in the fastboot folder ?

clsA said:
is it in the fastboot folder ?
Click to expand...
Click to collapse
Yes, see screenshot.

PrimalMK said:
Yes, see screenshot.
Click to expand...
Click to collapse
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?

clsA said:
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?
Click to expand...
Click to collapse
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?

PrimalMK said:
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?
Click to expand...
Click to collapse
fastboot crashes ?
no if fastboot getvar worked it will all work
it's only 4 commands and your phone will be working
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
adb sideload rom.zip
sideload takes about 8 min

calculation icatkg
clsA said:
fastboot crashes ?
no if fastboot getvar worked it will all work
Click to expand...
Click to collapse
Restarted a couple of times etc. It worked. Will do the ROM thing now.

PrimalMK said:
Restarted a couple of times etc. It worked. Will do the ROM thing now.
Click to expand...
Click to collapse
great your about done ...your phone will be android 4.3 when it finishes
don't take any updates to the OS

cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:

PrimalMK said:
cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:
Click to expand...
Click to collapse
no problem, hit the thanks button

[Q] Flash back to Stock

Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.

samwathegreat said:
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
Click to expand...
Click to collapse
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.

samwathegreat said:
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
Click to expand...
Click to collapse
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.

samwathegreat said:
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
Click to expand...
Click to collapse
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.

samwathegreat said:
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
Click to expand...
Click to collapse
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app

boss. said:
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.

Awesome!

samwathegreat said:
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Click to expand...
Click to collapse
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!

boss. said:
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
Click to expand...
Click to collapse
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:

samwathegreat said:
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
Click to expand...
Click to collapse
Re-did the whole thing from scratch again and now all problems are solved. Really appreciate the help my friend!
Sent from my SM-N9005 using XDA Free mobile app