Just yesterday, I was trying to get CM10.1 on my HTC One XL, and all of a sudden, my touchscreen at my dock area just stopped working, i didnt take much notice at that time as I didnt have an OS to boot into yet and i thought it was just a tiny problem. Today when I successfully flashed CM10.1 i then started to realize that my touchscreen there wasn't working. I don't exactly know what the last thing i did was before it happened, as I said i didn't really take notice when it started happening. I tried factory resetting but it didn't work either. Could it be that my touchscreen on that area is spoilt? should i replace the screen???
All help is greatly appreciated
Thanks
The best way to find out whether it's a hardware problem or not is to run an RUU. Boot the stock ROM up directly after running the RUU, if the problem persists it's almost definitely a hardware issue, if your touchscreen works again it was a software problem. Please note: if you have SuperCID (which you probably do) and s-on, running an RUU will brick your phone, so make sure you get s-off first.
Sent from my Evita
timmaaa said:
The best way to find out whether it's a hardware problem or not is to run an RUU. Boot the stock ROM up directly after running the RUU, if the problem persists it's almost definitely a hardware issue, if your touchscreen works again it was a software problem. Please note: if you have SuperCID (which you probably do) and s-on, running an RUU will brick your phone, so make sure you get s-off first.
Sent from my Evita
Click to expand...
Click to collapse
so im s-on, but when i try to change my cid to 11111111, using
>adb shell
>su
>dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
when i type in su it says
/sbin/sh: su: not found
Have you enabled usb debugging and granted it root access in developer settings? Or you could try the hex edit method, but you'll still need su access.
Sent from my Evita
timmaaa said:
Try the hex edit method.
Sent from my Evita
Click to expand...
Click to collapse
thanks for the speedy response. That was the method that i tried, when i type in su, it says
/sbin/sh: su: not found
but im in recovery mode
because i cant turn on usb debugging because i can't click the about phone portion of my screen
timmaaa said:
Have you enabled usb debugging and granted it root access in developer settings? Or you could try the hex edit method, but you'll still need su access.
Sent from my Evita
Click to expand...
Click to collapse
i have now enabled usb debugging and allowed root access for apps and adb. But when i type in adb shell now, it cant detect my device. I have all the necessary drivers installed
So adb has been working previously? Does your screen work fully in TWRP recovery?
Sent from my Evita
timmaaa said:
So adb has been working previously? Does your screen work fully in TWRP recovery?
Sent from my Evita
Click to expand...
Click to collapse
Adb has been working previously in recovery, and yes, my screen works fully in TWRP, exceptthe three buttons below (not the stock htc buttons but the ones in twrp on the screen itself )
Ok, the fact that the problem exists in recovery as well tells me that this is likely a hardware issue.
Sent from my Evita
timmaaa said:
Ok, the fact that the problem exists in recovery as well tells me that this is likely a hardware issue.
Sent from my Evita
Click to expand...
Click to collapse
so i should get my screen replaced???
or can i still just try to run the RUU?
At this point I'm fairly confident that you're looking at a hardware problem. If you want to, you can still try the RUU (as long as you can get s-off first) but I have a feeling it won't really help. It is worth a try though.
Sent from my Evita
timmaaa said:
Have you enabled usb debugging and granted it root access in developer settings? Or you could try the hex edit method, but you'll still need su access.
Sent from my Evita
Click to expand...
Click to collapse
hi again, where do you find the file to hex edit on your computer??? i cant seem to find it.
Thanks again for your help
Related
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
schnidex said:
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
Click to expand...
Click to collapse
Go to shippedroms and download the RUU for your phone. Although why you'd want to return to stock is beyond me?
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
schnidex said:
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
Click to expand...
Click to collapse
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
olyloh6696 said:
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
Click to expand...
Click to collapse
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
kartkk said:
do a nandroid backup & also set up your adb beforehand
setting up adb saved me from possibly bricking my device a few times
try this guide
Click to expand...
Click to collapse
ben_pyett said:
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
Click to expand...
Click to collapse
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Sent from my HTC Desire S using XDA Premium App
olyloh6696 said:
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Click to expand...
Click to collapse
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
ben_pyett said:
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
Click to expand...
Click to collapse
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
olyloh6696 said:
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
Click to expand...
Click to collapse
If the ruu runs successfully to competition I believe that it will return the device do that it's identical to stock
Swyped from HTC Desire S using XDA Premium
After many, many hours of trying to figure out what the hell half the terminology about Android actually means and wondering whether or not I would brick my phone..
..I'm now back to S-ON. It's been a pretty horrible experience all in all. Yes, it's easy when you know how but knowing how has been through trial and fortunately not much error.
From being on 6.98.1002, I used the Jorgen method in Ben's link above to get to 0.98.0000. I should note that when my phone was first supplied, I was on 0.98.0002 and very worried that the earlier software wouldn't work - but I tried it anyway, and it did. However, I was still S-OFF.
I then re-installed my stock network ROM using the RUU. This kept me on 0.98.0000 but put the phone to S-ON. I flashed the branded ROM that the phone was shipped with thinking that this would take me to 0.98.0002 but to my surprise it didn't. Otherwise though, the phone is now stock condition again.
So I then tried to update OTA to the problematic software which caused me all this grief in the first place - and it appears my network have withdrawn it. And rightly so, pending a fix.
schnidex said:
Ben, I've seen elsewhere you've said:
"If you load the latest RUU you may end up updating the HBOOT so that it can't be downgraded."
..in which case, Houston, we may have a problem. The latest HTC non-branded ROM (1.47...) gives you HBOOT 6.98.1002.
Click to expand...
Click to collapse
You're right, I'm afriad that this is an area where I'm no expert, But HBOOT = 6.98.1002. = Alpharevx = so you've not upgraded it simply failed to downgrade (which is slightly better- I think )
I notice that there are a couple of guides, allow I've obviously not tried either of them both are in the [GUIDE] A Complete Tutorial for the Beginners and Others sticky
The second guide looks quite complex and not for beginners...
Although I've just spotted a note within the second guide which says says
Note 2: RUU 1.46 or greater can not be downgraded as yet, since gingerbreak does not work on these RUUs.
So Opps....a full nights sleep may shed some more light on this.....and hopefully so sound advice from someone who has already performed this task.
Good luck. (I'll back online in the morning) - but, only really able to answer easier questions and not unfortunately not provide you with a solution.....but I'll do what I can!
Alternate way to restore your phone to S-ON and stock
If your attempts are unsuccessful, there's another potential way to go S-ON.
http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2
Maarten
Okay so if you are like me and have installed the OTA Update or ran the 3.18 ruu with an S-On Device chances are You are currently hard bricked which in most cases leaves 4 options, Option 1. Try to get a replacement through the carrier or Manufacturer Option 2. Send it off for a repair or Option 3 try and fix it yourself. Option 4 Toss the device and look elsewhere.
I Personally am going with Option 3 and am attempting to figure out a working Unbrick Method that does not require a RIFF box so with that said i will be working in this thread in an effort to get an unbrick project working. Feel free to add your knowledge, input, and advice in the proceeding posts below.
Please Note if you are using Windows 8 you will need to disable driver signature enforcement, while there are many ways to do this by far the easiest way is to open an Elevated Command Prompt and enter
Code:
bcdedit /set {globalsettings} advancedoptions true
when you restart your Computer choose option 7. To Disable Advanced Boot Options Enter
Code:
bcdedit /set {globalsettings} advancedoptions false
I suggest that you try reading here. I hard bricked my device before while trying to downgrade my HBOOT version from 1.14 to 1.09.
http://forum.xda-developers.com/showthread.php?t=2156231
To sum it up, he could still access his bootloader, but couldn't flash anything. By accessing rebootRUU, he managed to place his phone into a brick mode which allowed Linux to recognize and write to the boot partition. To enter that sort of brick mode, he flashed an UNSIGNED HBOOT file, which would have been fine since he was S-ON. BUT, once he sent in the command for S-ON, the device saw the UNSIGNED HBOOT and rebricked. He was then able to re-write the P4 file, which contains all your device information (IMEI, CID etc.). Then flash in the recovery, access the recovery, and flash your ROM.
I don't know how different that hard brick is from yours, but it worked for me. Can you access your bootloader btw?
d3thstalker said:
I suggest that you try reading here. I hard bricked my device before while trying to downgrade my HBOOT version from 1.14 to 1.09.
http://forum.xda-developers.com/showthread.php?t=2156231
To sum it up, he could still access his bootloader, but couldn't flash anything. By accessing rebootRUU, he managed to place his phone into a brick mode which allowed Linux to recognize and write to the boot partition. To enter that sort of brick mode, he flashed an UNSIGNED HBOOT file, which would have been fine since he was S-ON. BUT, once he sent in the command for S-ON, the device saw the UNSIGNED HBOOT and rebricked. He was then able to re-write the P4 file, which contains all your device information (IMEI, CID etc.). Then flash in the recovery, access the recovery, and flash your ROM.
I don't know how different that hard brick is from yours, but it worked for me. Can you access your bootloader btw?
Click to expand...
Click to collapse
no my device is literally hard bricked, no bootloader/hboot no os no recognition on pc other than qhsusb_dload i remember working on the same issue with the htc shooter on sprint so im trying the method we used to recover our device after intentionally bricking it which requires linux but in any case im almost there im currently trying to track down the ENG hboot for the evita atm
FragmentedLogik said:
im currently trying to track down the ENG hboot for the evita atm
Click to expand...
Click to collapse
If you find one, let Leamstears know. He has a thread posted somewhere asking for it.
Also, you might search for unbrick evita in general section. There was a thread started awhile back by my buddy.
Sent from my HTC One X using xda premium
i have you made any progress ??? my htc one s is hard briked too
https://www.dropbox.com/sh/a1n5s4r61wfh7qr/gkgxmKXwka/Evita soff partitions
Maybe this will help.
Sent from my One X using xda premium
I am not sure if this is helpful at all, but I was looking into methods used to unbrick other HTC devices and found this thread: http://forum.xda-developers.com/showthread.php?t=1522351 I am not sure what all I would need to change to get it to work for our phone. if you have any thoughts I would be more than willing to look at it.
PUfelix85 said:
I am not sure if this is helpful at all, but I was looking into methods used to unbrick other HTC devices and found this thread: http://forum.xda-developers.com/showthread.php?t=1522351 I am not sure what all I would need to change to get it to work for our phone. if you have any thoughts I would be more than willing to look at it.
Click to expand...
Click to collapse
I'm not sure it will really help. The first part is to run brickdetect.sh. That script appears to try to enumerate the partitions. I tried to enumerate my partitions using the manual steps in mirgantrophy's unbrick evita thread to no success before I sent my device off for JTAG. You could always try to run the brickdetect.sh script and see though. It doesn't do anything to your phone. It just searches dmesg (a Linux log) for the partitions being detected when you attach the bricked phone via USB. Don't run the rest of it though. ;-P
I'd like see a method to fix emmc of an htc inspire 4g(htc ace). Can any of our methods be transposed for other htc devices?
do you think this would work on a samsung device? i flashed a skyrocket rom for my S2 and it was sposed to be fine but it decided not to be. or at least work on a project for samsung devices.... dont leave us hanging
Trozzul said:
do you think this would work on a samsung device? i flashed a skyrocket rom for my S2 and it was sposed to be fine but it decided not to be. or at least work on a project for samsung devices.... dont leave us hanging
Click to expand...
Click to collapse
I definitely would not try this on any device other than the device it's intended for. Completely different chipsets.
Sent from my Evita
my htc one x does not start and charge the battery
try installing an edited rom
then restart the phone now will not start
gato06 said:
my htc one x does not start and charge the battery
try installing an edited rom
then restart the phone now will not start
Click to expand...
Click to collapse
Do you have One X (Endeavor) or One XL (Evita)?
Sent from my Evita
timmaaa said:
Do you have One X (Endeavor) or One XL (Evita)?
Sent from my Evita
Click to expand...
Click to collapse
One X at&t
gato06 said:
One X at&t
Click to expand...
Click to collapse
What ROM did you flash?
Sent from my Evita
timmaaa said:
What ROM did you flash?
Sent from my Evita
Click to expand...
Click to collapse
I try with this rom
http://forum.xda-developers.com/showthread.php?t=2174855
gato06 said:
I try with this rom
http://forum.xda-developers.com/showthread.php?t=2174855
Click to expand...
Click to collapse
Well you've bricked your phone. That ROM is not for our phone.
Sent from my Evita
How unbrick :'( You have idea?
You can either get a jtag repair or send it to HTC to have the motherboard replaced. Jtag is the cheaper option. When you get it back, make sure you stay within our forum and only flash software intended for our device.
Sent from my Evita
ran the 3.18 ruu with an S-On Device
Click to expand...
Click to collapse
i never thought run RUU with s-on device will brick it. Will it be more correct to say "run RUU on device with s-on & supper cid will brick you device"
i've unlocked my att one x got supercid.. and then i decided to change it to htc_405... so... it was the wrong choice! and now i can't get back to supercid, i've tryied all guides on forum but no one works..
from adb shell.. command writes.. device not found.
also installed newest htc drivers but nothing changes.. the hasoon allin1 tool doesnt work and i dont know what to do..hellppp :crying:
Are you s-on or s-off?
Sent from my Evita
timmaaa said:
Are you s-on or s-off?
Sent from my Evita
Click to expand...
Click to collapse
i'm s-on
Wait why did you do that? The cid for at&t one x is cws_001...
Sent from my HTC One X using Tapatalk 4
panda_mode said:
Wait why did you do that? The cid for at&t one x is cws_001...
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
i know but i changed it to recieve eu update.. didn't know that he has other cpu.. so now i cant change it to supercid or the original one..
You're kinda stuck then. To change CID more than once you need s-off, but to get s-off you need SuperCID. You probably should have done some research before you did that.
Sent from my Evita
timmaaa said:
You're kinda stuck then. To change CID more than once you need s-off, but to get s-off you need SuperCID. You probably should have done some research before you did that.
Sent from my Evita
Click to expand...
Click to collapse
so any suggestions? i know that i shloud search more.. i have other one s and i thought it was similar.. but that one is not branded
denny094 said:
so any suggestions? i know that i shloud search more.. i have other one s and i thought it was similar.. but that one is not branded
Click to expand...
Click to collapse
Maybe you can hex edit your mmcblk0p4 and change the cid back to super cid or the AT&T cid. DO MORE RESEARCH ABOUT THIS. I cannot help you step by step because I have not attempted this myself. THIS IS JUST AN IDEA AND MAY BRICK YOUR PHONE. I am not responsible for what will happen of you attempt this.
In the sticky-roll up, there is a thread called "AT&T: Unlocking the bootloader through HTCdev." The title looks irrelevant to your issue, but it has information about hex editing the mmcblk0p4 file
Sent from my HTC One X using Tapatalk 4
panda_mode said:
Maybe you can hex edit your mmcblk0p4 and change the cid back to super cid or the AT&T cid. DO MORE RESEARCH ABOUT THIS. I cannot help you step by step because I have not attempted this myself. THIS IS JUST AN IDEA AND MAY BRICK YOUR PHONE. I am not responsible for what will happen of you attempt this.
In the sticky-roll up, there is a thread called "AT&T: Unlocking the bootloader through HTCdev." The title looks irrelevant to your issue, but it has information about hex editing the mmcblk0p4 file
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
yeah i've seen that one.. but if i try to take that file.. adb says "device not found" so i cant do this one too..
C:\fastboot\adb shell (>enter)
daemon started succesfully*
device not found!
with lastest htc drivers and htc sync... if i could get the mmcblk0p4 file i wont open this thread
Ah I see. Well I can't be much of help then. Sorry
Sent from my HTC One X using Tapatalk 4
denny094 said:
yeah i've seen that one.. but if i try to take that file.. adb says "device not found" so i cant do this one too..
C:\fastboot\adb shell (>enter)
daemon started succesfully*
device not found!
with lastest htc drivers and htc sync... if i could get the mmcblk0p4 file i wont open this thread
Click to expand...
Click to collapse
Ensure that USB debugging is turned on.
Verify that HTC Sync is not running.
Try other cables, USB ports and even other computers.
s79336951 said:
Ensure that USB debugging is turned on.
Verify that HTC Sync is not running.
Try other cables, USB ports and even other computers.
Click to expand...
Click to collapse
i've tried all thoose , 3 pc's (1 with win7 the other win8) always debug mode..(actually the phone is runnin viperx4) ,..on, 2 different calbles and all pc 's usb ports i'm desperate
denny094 said:
i've tried all thoose , 3 pc's (1 with win7 the other win8) always debug mode..(actually the phone is runnin viperx4) ,..on, 2 different calbles and all pc 's usb ports i'm desperate
Click to expand...
Click to collapse
Are you on a Jellybean Sense ROM currently? Does fastboot detect the device? I had a heck of a time getting adb to see the device (but fastboot was working fine), back when the s-off method first came out, while on a Jellybean Sense ROM. I tried any number of the usual fixes, such as different drivers, different USB cords, and a different PC. The only thing that worked is using an old nandroid to go back to ICS, and adb picked up the phone right away. All I can think is that the change to MTP storage somehow messed with the adb connectivity for me (but not for others, I don't know).
BTW, reported to mods to move this thread, as it should be in Q&A.
redpoint73 said:
Are you on a Jellybean Sense ROM currently? Does fastboot detect the device? I had a heck of a time getting adb to see the device (but fastboot was working fine), back when the s-off method first came out, while on a Jellybean Sense ROM. I tried any number of the usual fixes, such as different drivers, different USB cords, and a different PC. The only thing that worked is using an old nandroid to go back to ICS, and adb picked up the phone right away. All I can think is that the change to MTP storage somehow messed with the adb connectivity for me (but not for others, I don't know).
BTW, reported to mods to move this thread, as it should be in Q&A.
Click to expand...
Click to collapse
the device is running viperxl and fastboot its working well..
commands like..dunno...
fastboot oem readcid:
your cid is : HTC_405
so he has no problems..adb yes..
i dont have any ics backup and dont know how to install it..tryied to install ruu (with sense+ and not working)
denny094 said:
the device is running viperxl and fastboot its working well..
commands like..dunno...
fastboot oem readcid:
your cid is : HTC_405
so he has no problems..adb yes..
i dont have any ics backup and dont know how to install it..tryied to install ruu (with sense+ and not working)
Click to expand...
Click to collapse
If you want to get back to ICS to see if adb works: Make a nandroid of your current setup. Then just flash any stock rooted of custom ICS ROM. This is assuming you are still bootloader unlocked.
Of course, I'm not necessarily saying this will work (get adb to work). But it worked for me, and if you are out of options, then its certainly worth a try. If it doesn't work, just restore your nandroid, and you are no worse off.
What is your hboot version?
Also, RUU will not run if the CID is incorrect. So you' ve screwed yourself from running any correct RUU.
redpoint73 said:
If you want to get back to ICS to see if adb works: Make a nandroid of your current setup. Then just flash any stock rooted of custom ICS ROM. This is assuming you are still bootloader unlocked.
Of course, I'm not necessarily saying this will work (get adb to work). But it worked for me, and if you are out of options, then its certainly worth a try. If it doesn't work, just restore your nandroid, and you are no worse off.
What is your hboot version?
Also, RUU will not run if the CID is incorrect. So you' ve screwed yourself from running any correct RUU.
Click to expand...
Click to collapse
uhmm i think the cid problem i solved i've tryied again and adb worked now must be scid.. i'll do s-off.., with all in 1 toolkit or hexeditor?
denny094 said:
uhmm i think the cid problem i solved i've tryied again and adb worked now must be scid.. i'll do s-off.., with all in 1 toolkit or hexeditor?
Click to expand...
Click to collapse
That post is really confusing, your sentence structure and punctuation is all over the place. Can you clear it up a bit and ask again?
Sent from my Evita
Yeah, not sure what was being said there. Did going back to ICS fix the adb issue, or did you find another way? So you have SuperCID now? If so, do the facepalm method to get s-off.
If you are still trying to get SuperCID, I don't think hasoon's all-in-one tool will work. Believe its looking for the AT&T CID (cws__001), so any other CID, it will fail. You'll have to use the hex edit method.
Problem is solved thanks I did s-off but I would like to ask you another question.. I installed clear rom sense 5 but the device has very low signal the radio firmware is 0.24p are there new updates to increase the quality?
Inviato dal mio HTC One S usando Tapatalk 4
I'm not sure which which radio you're referring to there. Have you updated the firmware as suggested in the CR thread?
Sent from my Evita
Hey all,
I'm trying to fix my friend's totally FUBAR'd evita, and I now can get the bootloader and boot to a really screwy CM10, but I can't do adb commands on his evita. But ADB works just fine for my M7. Not sure why this would be the case.
Any idea what's going on?
What exactly are you attempting to do? And what's wrong with the phone?
Sent from my Evita
His SD card was corrupted, so first I used the old Team Nocturnal trick to fix it. The Evita was also getting inexplicably bad reception and running an out of date twrp and CM. I updated his twrp, but his hboot is too old for recent CM builds, so I was trying to get him to s-off (he's hboot 1.14.0001, and from what I read you need to get s-off to update the hboot). I was able to run some commands from fastboot USB, in spite of the fact that adb devices didn't return anything for his phone (did for mine).
But the s-off tool I found requires that I can run commands from within booted android, hence the problem.
My end goal is to get the Evita to a fresh install of CM11, in hopes the the updated software will fix some of the issues he's had with the thing.
Do you have usb debugging turned on on the Evita?
Sent from my Evita
timmaaa said:
Do you have usb debugging turned on on the Evita?
Sent from my Evita
Click to expand...
Click to collapse
Yes I do. I found some threads where people talked about toggling that multiple times before they got it to take, but that didn't work on this device.
You could try uninstalling all drivers from your PC, reinstalling HTC Sync Manager, and connecting only the Evita.
Sent from my Evita
Hi guys!
First of all thank you for reading.
I'm probably in my 3rd day lurking around every possible forum and thread looking for an answer to my similar problem but have yet to find one.
I used to have a sensation xe but I kinda smashed the digitizer to bits. before that the was battery swollen and the back case pretty damaged (it survived a 120 kph gps reading of an rc car before going end over end across a parking lot). Meanwhile I got an Htc One, which is superb and I kinda forgot about the old gal.
A few days back I found a guy selling a sensation for spares (the mobo was fried on his) so I just bought that (for 20 euros) and figured all I needed to to was a mobo transplant and then have a nice almost new sensation.
But obviously the digitizer is not calibrated. I found the forum with the tutorial on that but it requires super CID and Soff. Cannot do either of them.
Since the mobo has been replaced the devunlock didn't work. Cannot, for the love of me succeed with the junopunutbear soff with the wire trick. Tried it on a ubuntu live cd, all goes well up until the wire trick. On a side note, I design and build 3d printers for a living, I might be a noob in the android department but that's about it. Even tried an automatic timed relay to do the two wire taps and still nothing. Obviously, it's not working on windows, I found the kgs1992 tool which requires a version of controlbear for windows which I cannot find (found one but it doesn't recognise it when I put it in the tools folder).
tl;dr
Cannot devunlock, cannot soff, nothing. Could I possibly try changing the IMEI so that i can maybe just maybe devunlock it first? I tried putting the mobo back in the old phone, still powered up but didn't recognize the token. I'm pretty much stuck right now.
Any help would be highly appreciated and if you read the whole thing, kudos to you for standing my chatter !
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
rzr86 said:
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
Click to expand...
Click to collapse
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
elktw said:
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
Click to expand...
Click to collapse
did it tell you to be rooted first?
rzr86 said:
did it tell you to be rooted first?
Click to expand...
Click to collapse
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
elktw said:
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
Click to expand...
Click to collapse
just use the temproot.bat file from juopunutbear thread
then run rumrunner again
it is mentioning also in rumrunner thread
Stuck on confirm Unlock bootloader
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
culler said:
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
Click to expand...
Click to collapse
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
elktw said:
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
Click to expand...
Click to collapse
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
culler said:
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
Click to expand...
Click to collapse
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
rzr86 said:
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
Click to expand...
Click to collapse
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
culler said:
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
Click to expand...
Click to collapse
S-OFF requires a working rom so you can't use S-OFF method
with windows 8.1 you will face connectivity issues
type in search box how to set up adb/fastboot in windows 8 but the point is that you don't have enabled usb debugging mode
so i am not sure if you will have any success
by the way what version of TWRP did you flash?
the latest? (2.7.0)
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
culler said:
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
Click to expand...
Click to collapse
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
rzr86 said:
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
Click to expand...
Click to collapse
I tried unbricking project but it hangs on start with connecting to device or waiting for device.
As I understood, it needs to access ADB which i cant succeed.
I dont have JTAG equipment so it goes to some service to see if they could repair it.
It's such a great device, i don't want to lose it so soon