So I'm helping this guy out to run an ruu...he has locked the bootloader and every time he tries to do it it says connection not there between the phone and the computer but its obviously connected...is there any way to go out of this situation....do we need s-off to type "fastboot oem unlock"?
Try re-installing HTC Sync, and try a different USB port. Try a different cable also, but its usually the drivers or USB port.
You don't need S-Off to unlock the bootloader. That would defeat the purpose of having a bootloader unlock. We don't currently have S-Off on this device, either.
Run the ruu while booted into fastboot
The ruu.exe should detect it and start
Or you could try fastboot oem rebootruu
Sent from my One X using Tapatalk 2
I think it is detecting the device. I was wondering cause it gets to the end and says check the connection. That maybe its the wrong ruu?
Sent from my One X using xda premium
---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------
Also thanks Omario for helping me out with this guy!
Sent from my One X using xda premium
No problem! And @ redpoint. I know we dont need s off to unlock bl I was referring to the command fastboot oem unlock... That wouldn't unlock the bl? Cuz Subaru now he wants to unlock again lol
Yea I spent all day yesterday explaining how to fastboot OEM lock. You need the token to unlock again, right?
Sent from my One X using xda premium
Have you ever tried this program. Its pretty cool and may resolve issue
http://forum.xda-developers.com/showthread.php?t=1952426
Sent from my HTC One XL using xda premium
subarudroid said:
I think it is detecting the device. I was wondering cause it gets to the end and says check the connection. That maybe its the wrong ruu?
Click to expand...
Click to collapse
How do you know its detecting (talking to) the device? If the person has adb, they can check easily with the command "adb devices". In any case, re-installing HTC Sync and trying a different USB port certainly won't hurt anything, might work, and it would at least eliminate those as the cause. The drivers (HTC Sync) is the most common cause for RUU not running (aside from not relocking the BL).
Wrong RUU doesn't give a connection error, it gives a version error.
---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------
subarudroid said:
You need the token to unlock again, right?
Click to expand...
Click to collapse
Yes, its not any different from the first time you unlock, except you already have the token.
---------- Post added at 04:22 PM ---------- Previous post was at 04:20 PM ----------
omario8484 said:
No problem! And @ redpoint. I know we dont need s off to unlock bl I was referring to the command fastboot oem unlock... That wouldn't unlock the bl? Cuz Subaru now he wants to unlock again lol
Click to expand...
Click to collapse
The correct command is:
fastboot flash unlocktoken Unlock_code.bin
Related
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
you are lucky to have white screen
You posted in the wrong section...
This is for devsonly
Sent from my HTC One X using xda premium
xpurpleblob said:
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
Click to expand...
Click to collapse
If you updated to 4.0.4 (2.20) before you killed your phone, then use the 2.20 RUU found on HTC's website. You can't be updated and use a downgraded RUU. If that doesn't work, and your bootloader is locked and everything, then idk what to say. Try taking it to ATT if you're stillin your 30 day period. If try even if you're not.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
And you are in the wrong section. This belongs in the Q&A.
vin255764 said:
you are lucky to have white screen
Click to expand...
Click to collapse
what does this mean...
xpurpleblob said:
what does this mean...
Click to expand...
Click to collapse
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
HTC_Phone said:
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
Click to expand...
Click to collapse
I believe so, maybe not I'm currently doing work right now so I will check later.
However, the computer seems to recognize my phone when I'm applying the RUU, it stops at about 7% then shows the ERRor message 171
Thanks for the help.
can anyone please help
Where can I get stock recovery, stock boot for the phone?
First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the RUU without any issues.
Now find your ruu here http://forum.xda-developers.com/show....php?t=1671237 under STOCK RUUs AND RELATED.
Once you've finished upgrading your ruu you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin'
Hope this helps ^____^
thanks for the reply, however ur link is broken.
And if possible can someone list all the programs I need for this task...
the Htc sync, android sdk,.. etc
and do i need the adt file??
Also i am getting a signature verify failure when im flashing a recovery.img....
also btw i have the nandroid backups. i cant access the recovery in the hot boot though
xpurpleblob said:
thanks for the reply, however ur link is broken.
Click to expand...
Click to collapse
He meant to link the Index thread for the RUUs: http://forum.xda-developers.com/showthread.php?t=1671237
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
subarudroid said:
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
Click to expand...
Click to collapse
I don't think I can use that because my bootloader is locked.
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
subarudroid said:
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
Click to expand...
Click to collapse
i relocked my bootloader to run the RUU, however when I run it the eroor code 170 comes up
I tried 3 diff. RUU's none of them worked. I'm on AT&T.
You should be able to Unlock bootloader again though.
HTC devs would have email you the unlock_code.bin file
Maybe you deleted from desktop? IT might still be in your email?
IF your windows you can hit (Shift+rightclick) in folder run CMD.
fastboot erase cache
fastboot flash unlocktoken Unlock_code.bin make sure your fastboot files are in there also.
THis thread might also help. I take no credit. But I hope we can help you get your phone up and running to some degree.
http://forum.xda-developers.com/showthread.php?t=1671396
---------- Post added at 08:03 PM ---------- Previous post was at 07:37 PM ----------
I should also know note that I cannot take any responsibility for your phone being destroyed
Sent from my One X using xda app-developers app
Alright I got it working. If anybody ever gets the same problem as me, disable your antivirus, take out your internet connection from the computer, run as administrator for the RUU, and close all programs except for the RUU.
I BELIEVE THE MOST IMPORTANT WAS TO OPEN A NEW ADMINISTRATOR ACCOUNT ON THE COMPUTER.
I don't know which of these factors are definite but follow these steps and hopefully you will solve your problem too.
I recently used the Exploit and All-in-One Toolkit with varied success. I was able to get my token, but this where things got weird.
1. The file from HTC comes in as a VLC file. I use Chrome and my local broadband service as my email. I'm not able to save it to a folder. I still was somehow able to unlock the bootloader as it says ***TAMPERED*** and ***UNLOCKED***
2. I try to use the tool to flash TWRP and my command seems to go through, but the phone never reboots itself it just stays at the fastboot. I found out later, while chosing recovery that it did somehow flash it, but i'm not able to backup anything.
3. I'm unable to send Superuser thru to perm root. It keeps telling me device not connected in ADB.
I guess my question is where is the error coming from on my side. Should I set back to stock and start over and if so how? My last phone was an HTC Inspire which I rooted and constantly swapped roms, radios, kernels, so this isn;t my first rodeo. I'm basically looking to root to future use as right now I'm not looking at roms, but would love to get the ATT crapware off the phone. The phone is operating fine since my attempt so any info would be great.
I posted in the all=in=one section, but haven't had any responses.
I came from a inspire as well. This is a different ballgame. can you get into recovery from bootloader screen?
Sent from my HOX w/CM10.1
subarudroid said:
I came from a inspire as well. This is a different ballgame. can you get into recovery from bootloader screen?
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
I can get into TWRP from the bootloader but I can't make a backup and i can't get the toolkit to push thru the superuser app to give root.
See if you can find a superuser zip and install in twrp?
Sent from my HOX w/CM10.1
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
Oops wrong one
Try this.
Sent from my HOX w/CM10.1
I went back in to recovery and was able to make a backup of my stock rom and settings. Where is a link to a superuser.zip and how to push it thru.
http://forum.xda-developers.com/attachment.php?attachmentid=1195050&d=1342168095
Sent from my HOX w/CM10.1
---------- Post added at 11:52 AM ---------- Previous post was at 11:50 AM ----------
After downloaded mount sd and copy, then install in twrp
Sent from my HOX w/CM10.1
---------- Post added at 11:54 AM ---------- Previous post was at 11:52 AM ----------
Crap. Im having a hard time shopping at wallmart and posting links.
http://forum.xda-developers.com/showthread.php?t=1742522
Sent from my HOX w/CM10.1
Thanks I finally got root and rid of the bloatware. It's weird because titanium backup won't show ATT Navigator for me to delete.
Good job. Sent you a pm if you need anymore help?
Sent from my HOX w/CM10.1
I'll try to make this fast and compact.
I soft-bricked my phone one year ago. To fix it I had to change my hboot value by pulling a file, changing it and pushing it back in. Turns out I did not have to do that.
Now my phone works, has a fake hboot value, it is bootloader unlocked BUT it is S-OFF.
I looked everywhere on the forums all day yesterday and today and yet I cannot find the solution. Maybe I'm too computer illiterate but who knows.
Here are my questions:
-do I need to revert back to stock to get the S-OFF/superCID
-if so how do I install the RUU. Every time I get a failed message with something concerning my HBOOT version error 44.
What ruu are you trying to run?
In the bootloader, does it show S-On or S-OFF?
what hboot version?
What is your Cid? Fastboot oem readcid
Sent from my One X using xda app-developers app
exad said:
What ruu are you trying to run?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
The rogers one. I figured since My phone is from rogers it should work.
Here is the link http://d-h.st/jPy
It is the PJ83IMG one.
Thank you for such a fast response.
You need stock recovery to flash that I believe and even then I'm not sure that would work? . You should get a windows executable RUU.
Sent from my One X using xda app-developers app
---------- Post added at 12:09 AM ---------- Previous post was at 12:02 AM ----------
exad said:
You need stock recovery to flash that I believe and even then I'm not sure that would work? . You should get a windows executable RUU.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
here: http://bugsylawson.com/index.php/fi...s320928l-101033224l-release-268972-signedexe/
Be sure you're soff before running. plug in the phone, and run the ruu
Hi, I am currently running one of the clean roms and am having random restarts and random data connection issues. I would like to go back to stock and am wondering if I just leave my phone plugged in and run the 4.1.1 ATT RUU? Is it that simple? I am also security unlocked so I can always reenable root and flash to other roms right? (Every time I power on there is a statement about something in red lettering)
Does anyone also have the power button pushed in to where pressing the power is really hard. It used to be fine but now it is really hard to press the power button. How difficult is it to replace the power button?
If you have s-off you can go ahead and run the RUU to take your phone back to stock.
What do you mean by security unlocked though? That red text you see on boot just means your bootloader is unlocked.
Sent from my Evita
---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------
PS. You're posting in the wrong section. Questions go in the Q&A section.
Sent from my Evita
timmaaa said:
If you have s-off you can go ahead and run the RUU to take your phone back to stock.
What do you mean by security unlocked though? That red text you see on boot just means your bootloader is unlocked.
Sent from my Evita
---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------
PS. You're posting in the wrong section. Questions go in the Q&A section.
Sent from my Evita
Click to expand...
Click to collapse
Oh I just checked and you are right I have S-ON and the bootloader is unlocked. Is it still okay to proceed and still be able to root in the future and flash custom roms? Or will the new RUU lock that?
I just want to flash to completely stock to see if it solves my battery and data connection as well as radio issues.
If you run the RUU while you're s-on and SuperCID you'll brick your phone. You need to get s-off first.
Then when you want to run a custom ROM again you just need to flash a new recovery, and flash a custom ROM.
Sent from my Evita
Hi All,
I have rooted (I think) my HTC Inspire and Unlocked it as well ( using EastAceRootTool_21112013). I was trying to put on the Blackout_ICS_Incredible_v4.0 but could not get it to work. So I tried the GizRoot_v_2. Once that was done i booted the phone but things were not working well.
So I want to go back to the original RUU and/or .zip for my phone. I have tried many things:
1) RUU faults saying there is no connection (error 171 or 170 have gotten both)
2) Have tried flashing from original file PD98IMG.zip and also the rom.zip pilled from the RUU (always get an error that states "E:Can't open sdcard/rom.zip (bad) or /PD98IMG.zip (bad).
I have read that if it is unlocked there with be issues with "signed" files. Also have tried wiping cache, dalvik, etc with no luck.
This is what I would like to do:
1) Get back to a stock ROM so my wife can use it
or
2) find a decent working ICS ROM for the HTC Inspire 4G (AT&T) that doesn't have many issues.
Thank you in advance for any support offered. I am a noob when it comes to some of this but do have some experience.
Regards,
Falcondown01
U fix it yet?
Sent from my One X using Tapatalk
---------- Post added at 10:01 PM ---------- Previous post was at 09:59 PM ----------
If u need help just ask me. This is QN ideal ROM for your device. This one is smooth and has no bugs or FCS
http://forum.xda-developers.com/showthread.php?p=21735599
Sent from my One X using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------
Error 170 means your PC isn't recognizing your phone. U might need to install the proper drivers and or minimal fastboot and adb drivers.
Sent from my One X using Tapatalk
---------- Post added at 10:05 PM ---------- Previous post was at 10:03 PM ----------
https://sites.google.com/site/communityhelpsareebro/how-to-fix-error-170-usb-connection-error
Sent from my One X using Tapatalk
---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------
http://forum.xda-developers.com/showthread.php?t=1809970
Sent from my One X using Tapatalk
Hi Chrisb906,
Thanks for replying. Short answer is nope haven't fixed it yet.
Just tried the ROM you pointed me too. Currently I have gotten the htc white screen and it is sitting there like that so it seems I have made things worse.
My htc sync is one of the newest from the download site at htc. I have also tried sync version DriverVer=11/06/2012,2.0.0007.00014.
So I am not sure where to go from here. At this point if I could get back to square one that would be something.
What other information can I provide you that might help?
Regards,
Falcondown01
Let me know when ur online and we can troubleshoot it
Sent from my One X using Tapatalk
Hi Chrisb,
I am on-line now.
Regards,
Falcondown01
Now?
Sent from my One X using Tapatalk
---------- Post added at 12:54 PM ---------- Previous post was at 12:52 PM ----------
What's your bootloader details? Are U s off,unlocked supercid?
Sent from my One X using Tapatalk
Hi Chrisb
I am unlocked, s-on. See the attached pic.
Thank you
U should run an ruu
Sent from my KFSOWI using Tapatalk
---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------
http://forum.xda-developers.com/showthread.php?t=2347208
Sent from my KFSOWI using Tapatalk
Hi Chrisb,
Sorry had some weather related issues.
Unfortunately the RUU always faults with connection issues. I was able to flash from zip back to the Gizroot_v_2 again and then tried the MR1 ICS but upon reboot only goes to the htc boot screen and then sits there.
I looked through the thread you had in the last post but I didn't see anything there for this issue.
Thanks again,
Falcondown01
I know this is a crazy question but bare with me as I diagnose here. You're s-on right? So when installing the zip in recovery are you going back to fastboot and flashing the boot.img from the zip?
Sent from my Htc Inspire 4G using xda app-developers app
Hi Muhff,
Yes, correct "s" is on. As far as fastboot and the bootimg I cannot say. I am new at some of this and am trying to get this to work.
Maybe I have misunderstood a step in the process or something like that but I am not sure.
If you have a thread I can look at or some steps to follow and try that would be great.
Thank you,
Falcondown01
Good catch muhff! Maybe he should just flash ROMs via fast boot huh? I've already suggested that. Lol
Sent from my Desire HD using Tapatalk
Remember the "adb" and "fastboot" you had to use on your computer to unlock bootloader? Boot your phone into recovery, wipe cache, delvik, data, and system partitions. Pick the zip you want to install and transfer the "boot.img" from inside the zip to the folder on your computer containing adb/fastboot. (Clockworkmod recovery has a "mount usb" function that allows you to trasnfer files in recovery.) Once you finish installing the zip of the rom in recovery go back into the bootloader (adb reboot bootloader) cmd then type "fastboot flash boot boot.img"(without quotes) then reboot and give it a few minutes, first boot is always the longest.
Sent from my Htc Inspire 4G using xda app-developers app
---------- Post added at 02:47 PM ---------- Previous post was at 02:43 PM ----------
The boot.img can always be found in either the root of the zip or in one of the folders like "boot" or 'kernel". If you need anything else feel free to ask, and happy pattys day mate :beer:
Sent from my Htc Inspire 4G using xda app-developers app
---------- Post added at 03:04 PM ---------- Previous post was at 02:47 PM ----------
Finally found the thread. Section 4 is where you want to be right now but it all has useful information, trust me :good:
It says most roms have a function of auto installing the boot.img, this is true in the case that the phone is "s-off (security off)" which in fact you are not. But dont worry, im also s-on and have installed atleast 15 roms from this forum just experimenting with things. Once you do it a few times it takes about 5 minutes. Its usually a good idea to create a backup in recovery, only thing you'll have to do is flash the boot.img from the rom in the backup. Say you made a backup of "moonraker" but just installed "aospx" rom. When you recover from the moonraker backup you'll need to reflash moonrakers boot.img.
Thread::http://forum.xda-developers.com/showthread.php?t=2182792
Hi Muhff and Chrisb,
So here is where I am at. I have tried the "fastboot" but it is always waiting for the device so not sure what is going on there.
1. Boot your phone into recovery, wipe cache, delvik, data, and system partitions. - Did this.
2. Pick the zip you want to install and transfer the "boot.img" from inside the zip to the folder on your computer containing adb/fastboot. - Did this.
Clockworkmod recovery has a "mount usb" function that allows you to transfer files in recovery.
3. Once you finish installing the zip of the rom in recovery. - Did this.
4. go back into the bootloader (adb reboot bootloader) cmd. - Did this and boot loader rebooted fastboot USB.
5. then type "fastboot flash boot boot.img"(without quotes) - Did this at bootloader screen (should I be in another state on the phone? Just stays at waiting for device.
6. then reboot and give it a few minutes, first boot is always the longest. - Did not achieve.
Thanks again,
Falcondown01
Sounds to me something is screwy..look up bannagranola and or gizmoe..they can help as well...I will continue to pass on the knowledge I know too
Sent from my Desire HD using Tapatalk
---------- Post added at 05:22 AM ---------- Previous post was at 04:29 AM ----------
Always type" fastboot devices" and or "adb devices" before continuing on another step. I learned the hard way..sometimes the PC won't recognize the phone.
Sent from my Desire HD using Tapatalk
---------- Post added at 05:24 AM ---------- Previous post was at 05:22 AM ----------
If the command window hangs and just says waiting for device. ..it sounds like the PC isn't recognizing the phone.
Sent from my Desire HD using Tapatalk
Hi Chrisb,
Yeah the adb devices works but fastboot devices never sees the phone. So it has to be either and issue with a driver and or phone issue. Cant tell which one yet but going to keep trying.
Thanks again,
Falcondown01
Hm, that's fishy. I'd call it something with the drivers. Or are you missing the actual "fastboot" file from the adb folder on your PC?
Sent from my Inspire 4G using xda app-developers app
Follow this link and install these.
http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=26370238
Sent from my One X using Tapatalk
---------- Post added at 06:17 PM ---------- Previous post was at 06:15 PM ----------
After installing this, add a short cut on your desktop of the .exe of minimal adb and fast boot. That way u can right click it again and select open file location. There u can copy and paste your zips u wanna flash via fastboot
Sent from my One X using Tapatalk
---------- Post added at 06:18 PM ---------- Previous post was at 06:17 PM ----------
Or..in search button..if ur using windows..type in search field "fastboot".. It should pull it up that way
Sent from my One X using Tapatalk
Hi Chrisb andMuhff,
Guys thanks for all your help. Finally found the issue. Although I had loaded drivers before whenever I would change it from HBOOT to FASTBOOT with usb cable connected I would get a "dun dun dun" noise instead of the normal connected or disconnected noise. Anyway I decided to take a second look and found under the hardware devices that indeed the drivers did were not loaded and I had an exclamation point on the android 1.0 device.
So long story short I loaded the drivers, went back and did the procedure again that hadn't worked before and then WOO HOO great joy. It worked and I am now running aospX-1.0.0-MR1-DHD.
Thanks again for all your help and time!!!!!!!!!
Regards,
Falcondown01
Did u s off?
Sent from my Desire HD using Tapatalk
---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
U still should do those suggests I gave ya.. It will surely help out
Sent from my Desire HD using Tapatalk