Hi there,
I know this might seem like a really dumb question, but I was wondering if someone can point me the way to updating my One XL to this firmware or whatever this is. I really wanna try the newer CM for the phone.
Thanks in advance!
You need s-off first, do you have s-off?
Sent from my Evita
Man I would love to know what that means, but my friend helped me root my phone last year. How can I check whether s-off is enabled or not? If not, can you direct me somewhere I can do this?
Sorry for the super noob questions.
Thanks man
Oh, I see. This is why I'm totally against people rooting phones for other people. Now you have an unlocked/rooted device but you have no idea what you're doing. You're gonna need to do a lot of learning. I need to see your bootloader details, to boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Sent from my Evita
Thanks for the help man! Really appreciate it man!
EVITA PVT SHIP S-ON RL
HBOOT-1.11.0000
RADIO-0.18as. 32. 09. 28L
OpenDSP-v28. 1. 0. 32. 0504
eMMC-boot
You need to get s-off so you can run the 3.18 RUU, do you have SuperCID? You can check your CID by issuing this fastboot command
Code:
fastboot oem readcid
Sent from my Evita
timmaaa said:
This is why I'm totally against people rooting phones for other people. Now you have an unlocked/rooted device but you have no idea what you're doing. You're gonna need to do a lot of learning.
Click to expand...
Click to collapse
Completely agree on these points. An owner with a modified device, that doesn't understand the basic concepts of what is modified is very dangerous for a variety of reasons.
This is one perfect example, if you had run the 3.18 RUU with S-on (which you have) and SuperCID (which you probably also have) would have instantly bricked the phone.
Its a very good thing you asked, before proceeding.
Related
Hi!
Tried this: "If you want to help, check if you have S-ON or S-OFF. Turn off the phone, reboot with the volume button held down, and check at the top of the white screen if it says "SHIP S-ON", "SHIP S-OFF" or "ENG S-OFF". S-ON is stock and not helpful, SHIP S-OFF could be useful, the really helpful ones are ENG S-OFF. Please don't post asking if you can help if you have S-ON."
The thing is that my device have a white screen with a red symbol so i can't see if i have S-OFF or nothing... i can't see this white screen the text talks about above... AND, my device does not have Swedish langauge... Isn't it available yet or where does my device come from?
Thanks in advanced!
ToddeSwe said:
Hi!
Tried this: "If you want to help, check if you have S-ON or S-OFF. Turn off the phone, reboot with the volume button held down, and check at the top of the white screen if it says "SHIP S-ON", "SHIP S-OFF" or "ENG S-OFF". S-ON is stock and not helpful, SHIP S-OFF could be useful, the really helpful ones are ENG S-OFF. Please don't post asking if you can help if you have S-ON."
The thing is that my device have a white screen with a red symbol so i can't see if i have S-OFF or nothing... i can't see this white screen the text talks about above... AND, my device does not have Swedish langauge... Isn't it available yet or where does my device come from?
Thanks in advanced!
Click to expand...
Click to collapse
Take a picture of it for us, although this should be posted in the Q&A section. I'm sure a mod willl move it
moved
I had to turn off "fastboot" in Settings>Power, then power off phone, then hold the volume button & the power button @ the same time
Pull your battery and put it back and then hold volume down & power. Basicly its a hard reset.
I have an HTC Desire S with a broken power button. I manage to power on the device by using quick battery in-out trick, and unlock screen with an unlock app. I want to root the device and install custom rom.
The problem is that i cant select items on the Bootloader menu since the power button doesnt work. Is there some way to select items without the power button?
z33m said:
I have an HTC Desire S with a broken power button. I manage to power on the device by using quick battery in-out trick, and unlock screen with an unlock app. I want to root the device and install custom rom.
The problem is that i cant select items on the Bootloader menu since the power button doesnt work. Is there some way to select items without the power button?
Click to expand...
Click to collapse
How is the power button broken? You might be able to fix it if you can take the device apart which is quite easy, I've done it. However, that would have to be a risk you're willing to take. I'm not sure if you can navigate the bootloader without a functioning power button. But I know you can access fastboot from the command line. Is your device S-OFF? Is the bootloader unlocked?
Sent from my Desire S using xda app-developers app
uarepeople said:
How is the power button broken? You might be able to fix it if you can take the device apart which is quite easy, I've done it. However, that would have to be a risk you're willing to take. I'm not sure if you can navigate the bootloader without a functioning power button. But I know you can access fastboot from the command line. Is your device S-OFF? Is the bootloader unlocked?
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
The power button became lesser and lesser responsive over time. i had to press multiple times before the screen would unlock. Eventually it just stopped working. I have taken the device apart once, with hopes of fixing the power button, but it seems that the power button is a tiny button surface mount directly to the main board. I cleaned eveything out, but no luck.
The device is S-ON. I havnt done anything other than installing the Official ICS upgrade. How did you fix your power button?
z33m said:
The power button became lesser and lesser responsive over time. i had to press multiple times before the screen would unlock. Eventually it just stopped working. I have taken the device apart once, with hopes of fixing the power button, but it seems that the power button is a tiny button surface mount directly to the main board. I cleaned eveything out, but no luck.
The device is S-ON. I havnt done anything other than installing the Official ICS upgrade. How did you fix your power button?
Click to expand...
Click to collapse
I should've explained why I took mine apart, I took mine apart in order to mod the unibody thing. I've seen websites that sell replacement parts so if you feel confident about repairing it yourself then you could always consider that.
Back to your initial question. You will be on the most recent HBOOT due to being on the ICS upgrade. Follow this guide by skanob in order to downgrade your HBOOT. Then use Revolutionary to S-OFF and install a custom recovery to your device. Then you should update your HBOOT to 7.00.1002 so that you have no difficulties with any custom ROMs.
Remember to read all the guides in full and make sure that you know what you are doing and that you are prepared before you start doing anything to your device. And make sure you are willing to risk damaging your device. Every device is different, personally my DS had no issues with any of these things I used as you can see in my sig.
Good luck.
uarepeople said:
I should've explained why I took mine apart, I took mine apart in order to mod the unibody thing. I've seen websites that sell replacement parts so if you feel confident about repairing it yourself then you could always consider that.
Back to your initial question. You will be on the most recent HBOOT due to being on the ICS upgrade. Follow this guide by skanob in order to downgrade your HBOOT. Then use Revolutionary to S-OFF and install a custom recovery to your device. Then you should update your HBOOT to 7.00.1002 so that you have no difficulties with any custom ROMs.
Remember to read all the guides in full and make sure that you know what you are doing and that you are prepared before you start doing anything to your device. And make sure you are willing to risk damaging your device. Every device is different, personally my DS had no issues with any of these things I used as you can see in my sig.
Good luck.
Click to expand...
Click to collapse
This is the procedure that i am following. Step 1 itself is to unlock bootloader using htcdev.com/bootloader . This procedure requires me to select HBoot from the bootloader menu, which i cannot, since the power button is broken.
z33m said:
This is the procedure that i am following. Step 1 itself is to unlock bootloader using htcdev.com/bootloader . This procedure requires me to select HBoot from the bootloader menu, which i cannot, since the power button is broken.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't require you to select anything. The guide tells you to type some code into a command line. Your PC will do everything for you. To get in to the bootloader all you do is connect your phone to the PC, open a cmd box and type:
fastboot reboot-bootloader
Click to expand...
Click to collapse
It will then turn off your phone and boot into fastboot.
uarepeople said:
Unlocking the bootloader doesn't require you to select anything. The guide tells you to type some code into a command line. Your PC will do everything for you. To get in to the bootloader all you do is connect your phone to the PC, open a cmd box and type:
It will then turn off your phone and boot into fastboot.
Click to expand...
Click to collapse
I have done this. But im now stuck at the final step, which is a yes/no confirmation prompt on the phone, where i have to press power button to confirm.
z33m said:
I have done this. But im now stuck at the final step, which is a yes/no confirmation prompt on the phone, where i have to press power button to confirm.
Click to expand...
Click to collapse
Usually the yes/no prompt is selected by the volume up/down buttons.
Sent from my Nexus 7 using xda app-developers app
Hi there, I'm new at this forum and new at android so please be patient with me!! This is my problem and I have a few questions too.
I wanted to perform my htc one x AT&T interface so I rooted it succesfully, then I installed recovery PWRP v2.6.0.0 but i dont know what went wrong and now i cannot start my phone, it is stuck on htc boot screen. I'm really afraid of what can happen now. I've read that if you install the wrong ROM i can brick it. I want to know how to fix this, and if i can flash any any any ROM at this forum. I know that htc is not upgrading this phone to android 4.2, just to 4.0.4, which is the one i have, but can i upgrade to 4.2 sense 5 using a custom ROM? please if you need any info ask for it and thank you!! Evermore, I wiped system, sdcard, cahce, etc...
We will need some further information from you. You said your phone hangs at the HTC screen when you try to boot it, does it stay on that screen constantly, or does it perform multiple boot loops? Here's a couple of options:
Scenario A (phone stays in htc screen constantly): hold volume down + power together, keep holding them and your button lights will start flashing then the screen will turn off. After a couple of seconds let go of the power button but continue holding volume down until you reach the bootloader (a white screen with text).
Scenario B (phone performs multiple boot loops): hold the volume button while it's booting, the next time it reboots it will enter bootloader as long as you keep holding volume down.
Now that you're in the bootloader, please post the first five lines of text you see. Also please tell us which root/unlocking method you used, and whether you've flashed any custom ROMs or anything at all before your phone stopped booting.
Sent from my Evita
timmaaa said:
We will need some further information from you. You said your phone hangs at the HTC screen when you try to boot it, does it stay on that screen constantly, or does it perform multiple boot loops? Here's a couple of options:
Scenario A (phone stays in htc screen constantly): hold volume down + power together, keep holding them and your button lights will start flashing then the screen will turn off. After a couple of seconds let go of the power button but continue holding volume down until you reach the bootloader (a white screen with text).
Scenario B (phone performs multiple boot loops): hold the volume button while it's booting, the next time it reboots it will enter bootloader as long as you keep holding volume down.
Now that you're in the bootloader, please post the first five lines of text you see. Also please tell us which root/unlocking method you used, and whether you've flashed any custom ROMs or anything at all before your phone stopped booting.
Sent from my Evita
Click to expand...
Click to collapse
Thank you for your reply. I fixed this problem installing DM9 ROM and now works great. Here are the first five lines you asked:
It is unlocked
EVITA PVT Ship S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
I used X-Factor root and at a first time it used to get stucked on htc white scrren logo, then i performed a cache restore through adb and at that time it started rebooting over and over again.
If you can help me now with the following will be great: I want to know if i can upgrade my OS to 4.2 JB with Sense 5 having superCID and s-on, or if there's a ROM out there that can simulate Sense 5 for 4.0.4. If it exist, could you tell me which will work fine? thank you very much
You can definitely run the Android 4.2.2 / Sense 5 ROMs with your current setup, no problems. You will need to flash the Beastmode kernel as well as the ROM to fix signal drop issues though. All of this can be found in our Android Development section.
Sent from my Evita
Hello, just to start I have read through probably 100 post regarding similar issues but none are working. I have the ATT Htc one x EVITA 3.18 version. I did the super CID unlocked my bootloader through htc dev, flashed twrp recovery, and got a custom rom, gapps etc.. in twrp I wiped all data,system,cache, factory reset. Then flashed my rom and gapps (being kinda new to HTC devices I didn't flash the boot.img from the rom) now my phone after restarting just continues a bootloop (HTC Quietly Brilliant) screen, then powers off repeating this over and over.. I tried holding the volume down with the power button it just loops again, the I tried some other suggestions like holding power and vol down until the flashes stop and releasing power while continuing to hold volume down, again loops, then tried using volume up as well...none of these are working I don't understand what happened and why I can't get into any of these? I did not run any RUU. I tried using adb but of course i cant get into fastboot or anything so the phone is not recognized. If anyone could please help I really do appreciate it. I know this has been all over the threads but I read for the past 3 hours and could not get anything to work.. Thanks in advanced for any help it is much appreciated. :crying:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
timmaaa said:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply timmaaa... I usually would not try the other button presses just someone else had said that worked for them, but thanks for the advice. I did try what you said and just holding the volume down button, let it bootloop, and keep holding and it just continues to bootloop :/ it stay off for about 20 seconds the same then bootloops, with the htc screen for about 5 seconds the rinse and repeats D**n this thing is annoying. Any other Ideas? Thanks again man appreciate it.
if you are SOFF u can go for RUU?
Sonone said:
if you are SOFF u can go for RUU?
Click to expand...
Click to collapse
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
sensei_777 said:
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
Click to expand...
Click to collapse
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Sonone said:
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Click to expand...
Click to collapse
I had to change the CID to unlock the bootloader on htc dev, its like 11111 so that is super CID right?
Yea I've tried everything to get to adb since I am familiar with adb but its a no go none of the tool kits or even manual cmd is recognizing the device.. I had a one x just like this before and never had the problem getting into bootloader so I don't really get what is blocking it. Only thing I had done was flash twrp recovery, wiped data/factory reset, system and cache, then flashed the rom as one usually would and gapps, just I had forgot about these phones needing you to flash the boot.img. that is all I did to it. Kinda sucks I just got this thing yesterday from a friend too.
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
timmaaa said:
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
Click to expand...
Click to collapse
Thanks bud, well I can't get it to catch even using super finger speed cmd'ing lol.. oh well.. I'm not gonna try anything else other than the usual ways to get into bootloader until someone else has some idea what might be blocking it from entering. Is there anyway to turn it off? its just restarting over and over with the bootloop. Or does one just let it go dead? I suppose worse case senario sending it for Jtag would fix it right? thanks again to the both of you.
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
timmaaa said:
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
Click to expand...
Click to collapse
Yes well on my laptop its the up key that's what I was doing was spamming, you can hear the connected device sound on then off, but it just doesn't see it. I will let you all know once its working again and what I did or had to do to get it back so that it may possibly help others that run into the same issue. If not I suppose I'll try to get it Jtagged, too nice of a phone to use as a paperweight really
Yeah sorry, I knew it was one of the arrow keys, kinda took a stab in the dark at that one :sly:
Sent from my Evita
Hold down the power button until the phone turns off. You'll see the buttons flash. This simulates a battery pull. Then wait a few secs then hold vol down and press power button for 2 secs while still holding vol down. Wait for bootloader
Sent from my VENOMized HoxL
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
timmaaa said:
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
Click to expand...
Click to collapse
Nothing is working guys :/ full Battery drain and everything it just keeps looping no matter what I do it will not go in bootloader :crying: thanks for trying to help
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developers app
exad said:
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developer app
Click to expand...
Click to collapse
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
sensei_777 said:
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
Click to expand...
Click to collapse
Just flashed the boot.img good to go now thanks for the advice everyone
Hello,
I would like to start off with saying I am new here and so far I love this site it has helped me a lot with rooting my phone. However, I have a problem:
Okay so I rooted the phone successfully and installed SuperSU and all that. After I did this the phone was rooted and running on jellybean just fine. Well the whole reason I wanted to root the phone in the first place was so I could install a custom ROM. So i followed this tutorial for the whole rooting process: http://forum.xda-developers.com/showthread.php?t=2069904
So after I rooted I downloaded the .zip file for the rom i wanted, which in this case was one of the Beanstalk roms for evita HTC One X.
After I moved the .zip file to the phone, I booted the phone into TWRP recovery. (I am using TWRP v2.7) and flashed the ROM. After I did this I extracted the boot.img file to my desktop. After I did this I opened up the toolkit and pressed Flash a Kernel, it said it did so successfully. I rebooted the phone and got stuck at the Beanstalk boot screen, and couldnt get it to fully boot up at all.
So I booted the phone back into recovery mode, made a backup, and wiped the phone clean so i could try to start over. Well when i wiped the phone i tried to back up the phone in TWRP, only to find that my backup file has disappeared.
Now my phone is ROMless and i can only boot the phone into recovery and bootloader mode.
This wouldn't be that much of a problem, if it weren't for my PC acting up. (I'm using Windows 7 Professional) My PC recognizes the device but the drivers never successfully install, the only place where i can find the device on my computer is in the Device Manager and it says Needs troubleshooting, when i try to troubleshoot it never troubleshoots correctly and i cant find the driver. So I can't access the files on the phone to put a different ROM on the phone, and i also tried running the RUU exe file for it and that did nothing. Is there any possible way to at least get this phone back to normal?? At this point I could care less about the root or custom ROM.
If anyone can help it would be greatly appreciated. I'm currently stuck without a phone until I can find a way to fix this
Thanks in advance for anyone able to help me.
First off, do you have the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)? I ask this because you linked to a guide for the Endeavoru but you have mentioned an Evita ROM, which means you're lurking in both device forums which is dangerous. What are your bootloader details?
Sent from my Evita
I have the AT&T HTC One X (Evita, US verison) and what do you mean by bootloader details? Sorry if i sound like a noob, i'm new to rooting and such.
Your bootloader details are the lines of text that your see in your bootloader screen. To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Sent from my Evita
timmaaa said:
Your bootloader details are the lines of text that your see in your bootloader screen. To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Yes i'm aware of what bootloader is (not trying to sound sarcastic or anything) but the first five lines are these:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PUT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
its a little more than 5 lines but yeah. I heard theres a way to flash the device with a third party software called ODIN if the pc wont recognize the device normally? Do you know anything about that?
ViolentPoptart said:
Yes i'm aware of what bootloader is (not trying to sound sarcastic or anything) but the first five lines are these:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PUT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
its a little more than 5 lines but yeah. I heard theres a way to flash the device with a third party software called ODIN if the pc wont recognize the device normally? Do you know anything about that?
Click to expand...
Click to collapse
Well, you did ask what I meant by bootloader details, so I answered. You absolutely can't use ODIN, that's Samsung software.
My advice is to get rid of whatever toolkit you're using and learn to do things manually, it's very easy, plus clearly toolkits are unreliable. You're gonna need to resolve your driver issue, probably by installing HTC Sync Manager, which will install drivers. Once you've gotten your drivers sorted out you can head to my How-To Guide For Beginners thread for detailed instructions on how to flash the boot.img manually.
Sent from my Evita
timmaaa said:
Well, you did ask what I meant by bootloader details, so I answered. You absolutely can't use ODIN, that's Samsung software.
My advice is to get rid of whatever toolkit you're using and learn to do things manually, it's very easy, plus clearly toolkits are unreliable. You're gonna need to resolve your driver issue, probably by installing HTC Sync Manager, which will install drivers. Once you've gotten your drivers sorted out you can head to my How-To Guide For Beginners thread for detailed instructions on how to flash the boot.img manually.
Sent from my Evita
Click to expand...
Click to collapse
yeah you just cleared up what you meant by details with the text lines
and ive tried uninstalling and reinstalling sync manager a few times now, it recognizes the device, but i cant access the files, the phone only shows up in Devices and Printers, and it shows up as Evita with an exclamation mark and says needs troubleshooting. when i try to troubleshoot it it doesn't work. however there are also other problems with my PC, the monitor is listed as a generic pnp monitor and the graphics card is listed as standard vga graphics adapter. i think thats my main problem, im going to try to wipe my pc and reinstall windows and see if that works.
ViolentPoptart said:
yeah you just cleared up what you meant by details with the text lines
and ive tried uninstalling and reinstalling sync manager a few times now, it recognizes the device, but i cant access the files, the phone only shows up in Devices and Printers, and it shows up as Evita with an exclamation mark and says needs troubleshooting. when i try to troubleshoot it it doesn't work. however there are also other problems with my PC, the monitor is listed as a generic pnp monitor and the graphics card is listed as standard vga graphics adapter. i think thats my main problem, im going to try to wipe my pc and reinstall windows and see if that works. Where can i find your how to guide for beginners?
Click to expand...
Click to collapse
Ok, yeah you probably need to sort out your PC first. My guide thread is in my signature.
Sent from my Evita
timmaaa said:
Ok, yeah you probably need to sort out your PC first. My guide thread is in my signature.
Sent from my Evita
Click to expand...
Click to collapse
my problem is now solved. thanks for your help