Hello,
I was trying to convert my T-Mobile HTC One to a Developer Edition so I could receive OTA updates by following the instructions here. I made it to step 11 where I changed the CID to BS_US001 (from T-MOB010), but encountered an error trying to change the MID to PN0712000 (from PN0713000). I also tried to change the CID to 11111111 which also worked, but I was still unable to change the MID. At this point I searched around for alternate ways to change the MID and found this post which I was able to follow until step 5. When I rebooted to bootloader at step 5, the phone never turned back on and I got a message in Windows saying "USB device not recognized".
The phone doesn't turn on at all, I have tried to hold power and power + vol down for around 30 seconds and nothing happens aside from a few vibrations every 20-30 seconds. I've tried holding power + both volume buttons for over 2 minutes to no avail. The PC I'm using is Win 8.1 using the USB 2.0 ports. I left it connected to the wall charger overnight and it only gave me a flashing red light.
Am I permanently bricked? No matter what I've tried, the phone just will not turn on at all. I tried running the RUU but of course it didn't work because the phone wasn't recognized as being plugged into the PC. Any help would be greatly appreciated. I've also attached a screenshot of the command window up until the point where I tried to reboot and it never turned back on.
When you get the "unrecognized device" the phone is on. Chances are, it's running a badly modified HBOOT that is trying and failing to get into RUU. LAst tiome that happened to me, holding the power button for *exactly* 16 seconds brought it into RUU mode (did not display the HTC RUU logo). From there I was able to run the RUU.
If you can get to that point, the RUU should install so long as you are SuperCID. If it does not;
Make sure you have the latest adb/fastboot - (or search google for "Minimal ADB and Fastboot" which has always worked for me)
fastboot reboot-bootloader
Install the modified tmous hboot following the instructions here:
http://rumrunner.us/hboots/
This will enable the use of the fastboot oem writemid command allowing you to change your MID.
I use this HBOOT when doing any conversions on my device. It allows all of the commands and has yet to fail me getting RUU's to run.
I have converted from T-Mobile to Dev, GPe and Int'l (and back to T-Mobile) several times and haven't bricked.
Keep working at it. These things are hard to brick!
Thank you for the reply! I'll try what you mentioned and report back on the results. I probably should have waited until I had a windows 7 PC to work on, but mine is currently in shipment. Hopefully with those tools you mentioned I can resurrect it.
Sent from my Galaxy Nexus using xda app-developers app
Well, I was able to get it working again. I actually tried plugging it into the usb 3.0 port on win 8.1 and it didn't give the unrecognized device message so I went from there. I did have to install some 8.1 fastboot drivers for usb 3.0 which was easy. I tried to run the t mobile ruu which didn't work because I had changed the CID but after that the device just booted normally.
Sent from my HTC One using xda app-developers app
dg32 said:
Well, I was able to get it working again. I actually tried plugging it into the usb 3.0 port on win 8.1 and it didn't give the unrecognized device message so I went from there. I did have to install some 8.1 fastboot drivers for usb 3.0 which was easy. I tried to run the t mobile ruu which didn't work because I had changed the CID but after that the device just booted normally.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Try flashing a bright light into the proximity sensor while holding the power button + vol down buttons together.
:good:
Related
//Header information
***UNLOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.50.0000
eMMC-boot
Hey guys, I recently acquired an EVO 3D in a trade deal and even though I don't want it (I plan on selling it but the cash deal + EVO 3D was worthy), I ended up being hellbent on rooting it last night. Success. Great, I threw Cyanogenmod7 on there and realized I'll have to undo the root/ROM to sell it later. I used what I believe is referred to as the REVOLUTIONARY method (using HTCDev.com, some terminal commands on my Mac, etc.)
Anyhow, didn't think it would be hard to undo what I did and I guess I was wrong. Let me tell you what I've tried so far.
I've tried using the PG86IMG.zip flash and nothing. No option (VOL UP or VOL DOWN) to even TRY installing it. Just quickly flashes the green text "No Image!" under each category (it goes too fast for me to read it) and I'm back at the boot menu. I've tried using different copies of the PG86IMG.zip with the same results (latest site acquired from: Goo-inside me, or something like that).
I've also tried using the RUU*.exe method on a Windows 7 machine. I've installed the drivers, everything checks out just fine until it actually tried to update the ROM. What happens here is that the phone reboots (as expected) and though the splash screen is different (black background with silver/gray hTc logo, semi-reflected) from the usual splash screen (white background with hTc in green), nothing happens. The software on the Windows 7 machine says "Waiting for bootloader" - which never shows up. Then it quickly gives me an error stating that the USB cable between the PC and the phone needs to be checked. Of course, there's no disconnect anywhere in the cables.
Please help! I planned on selling this device but if it's stuck in Cyanogenmod7, especially with no Google apps (couldn't get Gapps*.zip to work but whatever, not really concerned about that right now), there's no way I could sell this thing. I'm fairly knowledgeable in the basics of these matters as I have a rooted EVO 4G as well.
Anyone wanna buy an EVO 3D? HAHA
you could always flash a stock rooted rom .
You've gotta relock through adb before running the RUU.exe; then it'll work.
Hit the thanks if I helped
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
zer0xity said:
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
Click to expand...
Click to collapse
It's because of the pg86img.zip you can delete/move it away from the root of your sd card and get back into recovery... but you shouldn't need to, follow these steps:
1) Turn off phone
2) Hold power+vol down
3) Choose fastboot
4) Plug into your PC if you're not already
5) When you see FASTBOOT USB on the phone screen go back to your command prompt where you have your adb.exe, fastboot.exe, etc.
6) Type: " fastboot oem lock "
7) Aaaand you're done w/ the relocking go crazy and run your RUU.exe, don't reboot the phone or anything just run your RUU while your phone's still in HBOOT.
Edit: Oh, the adb I was talking about would kind of make everything easier; in command prompt: adb reboot bootloader AND THEN fastboot oem lock
Two steps, mhm.
I'm on it! Standby...
Okay, the adb stuff - can I do that from terminal in Mac? I tried doing it while in the appropriate folder where all that adb stuff is and I typed: adb reboot bootloader (ERROR: command not found), then I tried just: reboot bootloader (not permitted). I did try: ./fastboot-mac oem lock (successful. header now says *** RELOCKED ***).
Tried the RUU*.exe stuff on the Windows machine while in that state and again an alleged problem with the USB connection...
Sounds like we're close?
BAM! Got it. You put me on the right track with that last post. RUU still wouldn't do the reversion even though I had some drivers installed on Windows so I had to find some other drivers (some HTC3*.exe file, 13MB) and ended up running those for it to recognize the phone.
+1 to you, sir. Thank you so much!
Glad it all turned out well.
I need some help.
I'm trying to recover a friend's Evo 3d. He tried to flash a different ROM on it, and messed it up.
I'm on Windows 7 32bit. The phone is the Sprint EVO 3D (CDMA). HBOOT is 1.50.0000 S-ON
The device is not bootlooping. I get a blank screen after the HTC logo. I don't have access to USB debugging. I can get into recovery to try to flash a different image but to no avail - I get the same screen every time. I decided to get it back to stock but I can't relock it. ADB doesn't recognize the device and the device is very much in the device manager (proper drivers and all). I would love any advice.
Thank you.
my fix method
pixel4e said:
I need some help.
I'm trying to recover a friend's Evo 3d. He tried to flash a different ROM on it, and messed it up.
I'm on Windows 7 32bit. The phone is the Sprint EVO 3D (CDMA). HBOOT is 1.50.0000 S-ON
The device is not bootlooping. I get a blank screen after the HTC logo. I don't have access to USB debugging. I can get into recovery to try to flash a different image but to no avail - I get the same screen every time. I decided to get it back to stock but I can't relock it. ADB doesn't recognize the device and the device is very much in the device manager (proper drivers and all). I would love any advice.
Thank you.
Click to expand...
Click to collapse
You can boot into fastboot by holding vol-down and power from off. Then plug in USB and run fastboot(in the same folder as adb i think) with these args
Code:
boot PATH_TO_RECOVERY.IMG
and then flash a ROM. LightsOut is a good ROM. Hope I help.
Download the RUU and get into fastboot USB. and run it. That'll reset your firmware and radios and everything.
IF it has 1.50 s-on than it's still on Gingerbread, You need to update your radios and firmware, With the 2.89 RUU
Then it'll be on ICS, and you can unlock the bootloader
Then get s-off, You shouldn't be flashing anything with s-on lol.
(You can, but get s-off it's 1 more hour of work once you get it booting)
I must have been using a faulty cable or USB port, I tried it the next day with my girlfriend's Samsung cable and "fastboot oem lock" worked immediately. Ran RUU like a champ and it is alive and working now.
pixel4e said:
I must have been using a faulty cable or USB port, I tried it the next day with my girlfriend's Samsung cable and "fastboot oem lock" worked immediately. Ran RUU like a champ and it is alive and working now.
Click to expand...
Click to collapse
good deal
Hi,
the last days, I read a lot about flashing custom ROMs and wanted to do so with my HTC Legend. I'm not really new to flashing ROMs in general.I already flashed several other devices, but I'm stuck with unlocking the bootloader. My problem is, that the CMD is either reacting with "CommandError" or "waiting for device". I'm not able to get the token for unlocking the bootloader. Another problem is, that the SDK Manager won't start for me. So I just grabbed the 3 files out of the filesystem and tried it with them. Using HTCs recommended fastboot.exe doesn't change anything. I hope you can help me with a few details:
1. Do I have to install something else than HTC Sync? (I think, it already installed the driver, too)
2. Which connection mode should i choose, when connecting the legend? (recharging/hdd/htc sync/tethering)
3. Which version of the SDK should I use? Is it possible, that someone just gives me a zip with those 3 files?
I'm looking forward to your answers!
Regards
OdlG
SOLUTION:
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
Click to expand...
Click to collapse
(pardon my english, it's not my mothertongue)
AW: Difficulties with unlocking the Bootloader
You should use charging mode and you have to activate usb debugging in settings
Sent from my HTC One using xda app-developers app
Thanks for the reply!
I already enbled USB Debugging, and now tried it in charging mode. I created a BAT-File with the following command:
cd C:\Android\
fastboot oem get_identifier_token
But it still says "waiting for device" Any suggestions?
Did you follow these instructions? especcially selecting "fastboot"?
http://www.htcdev.com/bootloader/unlock-instructions
if yes and it still didn't work i've no idea at the moment
I tried it once more:
I connected the phone, "fastboot usb" is written there. the cmd still writes "waiting for device". after a few seconds, the pc reports, that the usb device could not be recognised. then there is written "fastboot" instead of "fastboot usb", though the cable is still connected.
a few hours ago i also got a guide at htc dev, that i should install da RUU (what does it mean btw?). i downloaded the german vodafone version and tried to install it. I will try that once more, hopefully the unlock will be successful afterwards!
thanks for your advice!
EDIT:I'm using the following software btw.
Android SDK (adt-bundle-windows-x86_64-20130219)
Java RE 7 Update 17
HTC Sync (3.3.X or something like that)
The RUU installer is starting the setup without problems. It's rebooting the phone o install version 3.30 (hboot1.02). But when the Phone starts in the bootloader mode and displays "RUU", the PC is unable to detect the USB device and the setup fails caused by missing usb connection
Can I somehow influence the detection of the phone in fastboot/bootloader mode?
Normally it should be enough to install the HTC USB Drivers...
You can grab the newest for example from this thread: http://forum.xda-developers.com/showthread.php?t=2191279
The second what you need is an actual adb.exe, fastboot.exe, AdbWinApi.dll & AdbWinUsbApi.dll... grab it for example from here: http://d-h.st/RvD (Thanx to torxx (http://forum.xda-developers.com/member.php?u=3828647))
After u've installed the drivers and extracted the adb file do the folowing
Turn off your phone completly
Push Vol down & Power ...device will start
Navigate with vol+- to fastboot press power
connect with usb-cable (possible that windows will install drivers...wait till its complete)
now "fastboot usb" should be read in the display of your phone
open a shell (cmd)
navigate to your fastboot.exe
type: "fastboot oem get_identifier_token"
it seems, that my htc firmware is far too old (3.15.405.3). i installed all the stuff on my win7 laptop instead of win8 desktop pc and could install the RUU... at least untill the notification, that i needed to update the firmware first, and update hboot1.02 (3.30.0.0) afterwards. the big update is also 150MB, the small one only 5MB. i'll give it a try and report back here, if i am able to manage all the stuff^^
btw autoupdating via options doesn't work ("phone is up to date"). do i have to sign in via google to get a better result?
I managed to unlock the bootloader!
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
now i will try the rest Thanks for the helpful hints!
AW: [solved] Difficulties with unlocking the Bootloader
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
esco27 said:
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Already flashed CM10.1 It's not as smooth as on my Ainol Aurora 2 Tablet, but the Legend hasn't got the power by far. But if you have a look at the specs, it is amazing, how good it runs on the legend
Thanks for all the help! That was definately worth it^^ I only have minor problems with my SIM-card up to now.
I have been following all the posts about rooting and I managed to soft-brick my phone. I was able to temp root the phone, but I could never get superCID because the modified CID would never take. I didn't get errors, it just didn't stick. Anyway, I flashed the recovery for 2.17, but my phone took an OTA update to 2.19 a few days ago, and now I am stuck on the main screen but without the sense unlock ring. The screen works, and I can access the phone's drive and sd card, and I can adb. The bootloader shows ****TAMPERED***** (been that way for a while), and Bootloader is LOCKED. FIREBALL PVT SHIP S-ON RL, HBOOT is 1.15.0000.
Any ideas to recover to a fully booted phone?
yes had the same thing happen to me. download the ruu exe. from here http://www.androidruu.com/?developer=Fireball i used 217.605.2 ruu. put phone in fastboot connect it to computer and run ruu exe. on ur computer
I followed your reply but am not having any success . . . yet.
I go through the RUU.exe screens where I verify that I want to "upgrade" from image version 2.19.605.2 to image version 2.17.605.2.
Then RUU.exe runs to the point where it tells me the process will take 10 minutes. It then gets to "waiting for bootloader........" and the phone looks like it is rebooting and a black "HTC" screen appears. Bootloader never appears. A Windows 8 Systray error message then appears saying "USB Device Not Recognized - The last USB device connected has lost communication with the computer [or something like that]" The RUU.exe program then states: "ERROR [171] USB Connection Error. Check the following: (1) phone is connected to USB cable; (2) PC is connected to USB cable" There is no further option than to EXIT the RUU.exe. (Yes, my cable is connected to a USB 2 port).
I tried to do this twice with the same error message and the same disappointing results. The phone stays locked on the black HTC screen and I need to pull the battery to change this locked state.
I have no trouble communicating with the phone with ADB and I have root (#) at ADB Shell. I JUST loose USB communications with the phone as soon as it goes tries to load bootloader. I originally tried to run RUU.exe the way you stated by putting the phone into fastboot and then running RUU.exe, but then the program would not find the phone. What am I missing here? I have HTC drivers loaded, but I keep getting the comm error. Any more ideas?
Maybe I need to flash a recovery for 2.19.605.2? Any idea where I might find that?
OK, not sure why I didn't do this sooner, but I did a factory reset from Bootloader and it seems I am back again running the 2.19.605.2. Not sure if I can root this new OTA version using the 2.17.605.2 procedures or not, but I may give this a break for a bit.
Yeah u can't downgrade to 2.17 if ur on 2.19
Sent from my XT1060 using xda app-developers app
So I've scoured the internet/Google for HOURS trying to find a solution to my issue. I left my office with my phone charging on a charger plugged into the wall, then came back about 40 minutes later to find my phone black-screened. No charging light on my charger, so I tried a different outlet, a different charger, and still no power. Then I plugged it into my desktop computer and it booted up!! Great!...except, all it DID was boot up to the white HTC screen...and repeated it over and over and over...
After a lot of research and learning a bit about bootloop, I discovered the HBOOT menu, pressing the POWER and VOL DOWN keys at the same time. Luckily, this worked. I managed to find the HBOOT menu, and this is what I was greeted with:
*** LOCKED ***
MONARUDO PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.02.01.0818
OpenDSP-v12.120.274.0909
OS-4.09.605.5
eMMC-boot 2048MB
Aug 27 2014, 13:22:15.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Well, the last two options work, and FASTBOOT brings me to another menu screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
And of those, the 2nd and 3rd bring me into bootloop again, and the 4th actually powers it down and sometimes shows me a battery-icon (as my phone would NORMALLY show when powered down and charging, but no charging animation is shown) and a lit charging light, but only briefly before going into bootloop.
Trying RECOVERY brings me into bootloop, and as a last-ditch effort, I tried FACTORY RESET, but that also brought me into bootloop (would trying that have already erased my memory? I haven't backed up my photos and other files in awhile...).
Anyways, if ANYONE can give me ANY help with this, it would be greatly appreciated! THANKS!
-Marc.
You can get into fastboot, good. See if the below can get your phone up and running. If it doesn't work, I don't know if the special commands @dottat knows would work on a locked and s-on device to try and manually repartition. Hopefully he can verify in his free time.
http://forum.xda-developers.com/showthread.php?t=2935556
Sent from my HTC6500LVW using XDA Free mobile app
MarkyMarc413 said:
So I've scoured the internet/Google for HOURS trying to find a solution to my issue. I left my office with my phone charging on a charger plugged into the wall, then came back about 40 minutes later to find my phone black-screened. No charging light on my charger, so I tried a different outlet, a different charger, and still no power. Then I plugged it into my desktop computer and it booted up!! Great!...except, all it DID was boot up to the white HTC screen...and repeated it over and over and over...
After a lot of research and learning a bit about bootloop, I discovered the HBOOT menu, pressing the POWER and VOL DOWN keys at the same time. Luckily, this worked. I managed to find the HBOOT menu, and this is what I was greeted with:
*** LOCKED ***
MONARUDO PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.02.01.0818
OpenDSP-v12.120.274.0909
OS-4.09.605.5
eMMC-boot 2048MB
Aug 27 2014, 13:22:15.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Well, the last two options work, and FASTBOOT brings me to another menu screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
And of those, the 2nd and 3rd bring me into bootloop again, and the 4th actually powers it down and sometimes shows me a battery-icon (as my phone would NORMALLY show when powered down and charging, but no charging animation is shown) and a lit charging light, but only briefly before going into bootloop.
Trying RECOVERY brings me into bootloop, and as a last-ditch effort, I tried FACTORY RESET, but that also brought me into bootloop (would trying that have already erased my memory? I haven't backed up my photos and other files in awhile...).
Anyways, if ANYONE can give me ANY help with this, it would be greatly appreciated! THANKS!
-Marc.
Click to expand...
Click to collapse
Figure this out yet?
Uzephi said:
You can get into fastboot, good. See if the below can get your phone up and running. If it doesn't work, I don't know if the special commands @dottat knows would work on a locked and s-on device to try and manually repartition. Hopefully he can verify in his free time.
http://forum.xda-developers.com/showthread.php?t=2935556
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I downloaded the 4.09.605.5 wizard and everytime I try to run it while my phone is connected to my computer, it keeps giving me the ERROR [107]: USB CONNECTION ERROR, even though my FASTBOOT menu says FASTBOOT USB, which I guess means it is connected, but for some reason, the program isn't reading the phone as such.
I also tried downloading the third link in the thread you linked me to, but the folder isn't unzipping for some reason on my computer. Am I doing something wrong or am I missing something?
MarkyMarc413 said:
I downloaded the 4.09.605.5 wizard and everytime I try to run it while my phone is connected to my computer, it keeps giving me the ERROR [107]: USB CONNECTION ERROR, even though my FASTBOOT menu says FASTBOOT USB, which I guess means it is connected, but for some reason, the program isn't reading the phone as such.
I also tried downloading the third link in the thread you linked me to, but the folder isn't unzipping for some reason on my computer. Am I doing something wrong or am I missing something?
Click to expand...
Click to collapse
Connection error could be driver issues. What drivers and OS are on your PC?
That third zip is a flashable firmware for s-off.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
You can get into fastboot, good. See if the below can get your phone up and running. If it doesn't work, I don't know if the special commands @dottat knows would work on a locked and s-on device to try and manually repartition. Hopefully he can verify in his free time.
http://forum.xda-developers.com/showthread.php?t=2935556
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Uzephi said:
Connection error could be driver issues. What drivers and OS are on your PC?
That third zip is a flashable firmware for s-off.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I'm using my office computer at work since my HP Pavilion died on me early last month (Yeah, I've been having bad luck with my tech lately...). I'm running Windows 7 on this Dell desktop, but I'm not sure I have the proper drivers on it for my phone. Unfortunately, I don't have the required ADMIN credentials to run any .exe's to install the proper drivers for my phone (as I just tried that with this link - http://www.theandroidsoul.com/?files_box=d56b9fc4b0f1be8 )
MarkyMarc413 said:
I'm using my office computer at work since my HP Pavilion died on me early last month (Yeah, I've been having bad luck with my tech lately...). I'm running Windows 7 on this Dell desktop, but I'm not sure I have the proper drivers on it for my phone. Unfortunately, I don't have the required ADMIN credentials to run any .exe's to install the proper drivers for my phone (as I just tried that with this link - http://www.theandroidsoul.com/?files_box=d56b9fc4b0f1be8 )
Click to expand...
Click to collapse
Yeah, to have fastboot commands or ruu working, you would need to install drivers and a work PC would not have the correct ones.
Sent from my HTC6500LVW using XDA Free mobile app