Related
Heeellllooooooooooooooooo,
I'm totally new on here so please excuse me ...
I've a HTC Sensation 2710e but its NOT rooted for the time being...
So which guide should I use to get the phone rooted (theres so many out there!!)???
Thanks
macdadi112
Hi and welcome! First thing you need to do is find out your hboot version. Their are different proccedures for different hboots, thus the reasons for the many guides. Once you find your hboot then we can help finding a guide. Too find hboot you can power volume down at same time this will boot you into a menu, you will see the information you need written above menu. You can also access by pulling battery out, replace battery volume down power at the same time. You can read your hboot then also. Really hope this helps you out! Once you know hboot you can take it from their.
Or we can help find proper guide if you can not.
Sent from my HTC Sensation 4G using xda premium
Ancenis, ingsixu
Thanks realsis.
My hboot is 1.27.
Hope that helps...
macdadi112 said:
Thanks realsis.
My hboot is 1.27.
Hope that helps...
Click to expand...
Click to collapse
Then you can use the guide in my signature (SOFF and one click root). To first SOFF then root your device.. The guide is bit tricky
You can also go via htcdev unlock..
Search for "flashing rom's with SON" guide by asskicker2 to have the root too.. (this method may(very slim) void the warranty)
Sent from my pyramid.. Through blazing fast sonic waves
sensation xe official ICS wifi error
I was connected via Wi-fi to my home router and downloaded the new version of android 4.0.3, and after updating the phone and it turned on again i couldnt connect to the router.
I can tell that the Wi-fi device on the phone works just fine. Because i can find my router, and my neightbours. It aks me the password ofc. Then when i try to connect, at first it says connecting, then after about 2-4secs it says disconnected. When i look at the list of routers, it only says 'not in range', but that isn't the problem.
I would say its not a hardware problem, but somehow a software problem. Because it was running just fine before the update.
Any idea on how to fix the issue ?
Anyone experienced the same problem after updating the phone ?
Could it be a WiFi driver problem with the on the new version of android ?
Here is some info on the software on my phone :
Andriod Version 4.0.3
Htc Sense version 3.6
Software number 3.32.401.105
Hope to get some help
mugenblackx1 said:
I was connected via Wi-fi to my home router and downloaded the new version of android 4.0.3, and after updating the phone and it turned on again i couldnt connect to the router.
I can tell that the Wi-fi device on the phone works just fine. Because i can find my router, and my neightbours. It aks me the password ofc. Then when i try to connect, at first it says connecting, then after about 2-4secs it says disconnected. When i look at the list of routers, it only says 'not in range', but that isn't the problem.
I would say its not a hardware problem, but somehow a software problem. Because it was running just fine before the update.
Any idea on how to fix the issue ?
Anyone experienced the same problem after updating the phone ?
Could it be a WiFi driver problem with the on the new version of android ?
Here is some info on the software on my phone :
Andriod Version 4.0.3
Htc Sense version 3.6
Software number 3.32.401.105
Hope to get some help
Click to expand...
Click to collapse
apparently its a bug in HTC
you need to search for updates again from phone (they released another update to fix this--around 15mb)
but as you didnt have wifi..you need to either use mobile network or internet pass through
if updating didnt solved the problem..try factory reset
I've checked out asskicker [GUIDE] Flashing roms with S-ON and 1.27 HBOOT..
The problem is I get to the Stage 2. Flashing a recovery.
I continue getting the following error message:
C:\AndroidSDK>fastboot flash recovery recovery.img
sending 'recovery' (6116 KB)...
OKAY [ 1.494s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.285s
So any ideas guys???
Your help is really appreciated.
macdadi112 said:
I've checked out asskicker [GUIDE] Flashing roms with S-ON and 1.27 HBOOT..
The problem is I get to the Stage 2. Flashing a recovery.
I continue getting the following error message:
C:\AndroidSDK>fastboot flash recovery recovery.img
sending 'recovery' (6116 KB)...
OKAY [ 1.494s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.285s
So any ideas guys???
Your help is really appreciated.
Click to expand...
Click to collapse
wow signature check..that should not happen if you got htcdev unlocked bootloader
did your bootloader say *unlocked* ..if not get the bootloader unlocked (step 1) and then try flashing recovery again
Ive been trying since yesterday to try and unlock the bootloader using the htc website.. Nothing seems to happen
Is there any other way I can unlock the bootloader...???????
macdadi112 said:
Ive been trying since yesterday to try and unlock the bootloader using the htc website.. Nothing seems to happen
Is there any other way I can unlock the bootloader...???????
Click to expand...
Click to collapse
not happening means...unlock process is failing ?
did your phone..recently came from replacement ?
you can use my guide(link in signature) to SOFF then ROOT
Yo ganeshp...
when I mean nothing happens, I mean I click the Begin unlock Bootloader and nothing happens, I sit there waiting for the web page to do something... But nothing.
My phones a HTC Sensation 2710e...
Wow, I've checked out your version as you said... And it looks amazing...! Much simpler than what I was trying...
Now shall I go with your version???
macdadi112 said:
Yo ganeshp...
when I mean nothing happens, I mean I click the Begin unlock Bootloader and nothing happens, I sit there waiting for the web page to do something... But nothing.
My phones a HTC Sensation 2710e...
Wow, I've checked out your version as you said... And it looks amazing...! Much simpler than what I was trying...
Now shall I go with your version???
Click to expand...
Click to collapse
the actual JB SOFF process ..was kinda difficult..you need to wire trick...that's the tricky one but fun part (some people struggled for hours to get wire trick done and some ppl did it in first try)
anyways if you can do unlock of bootloader i advise you to try that
try to open the web page in different browsers
I've done it and thanks to you, I'm finally rooted
Thanks to ganeshp
Now I'm on the lookout for ROM's.. Just a couple of quick questions..
1) Will I lose data and software each time that I flash my phone?
2) How do I check if I'm s-off or s-on?
3) Is there a ROM that you'd recommend?
Thanks
macdadi112 said:
I've done it and thanks to you, I'm finally rooted
Thanks to ganeshp
Now I'm on the lookout for ROM's.. Just a couple of quick questions..
1) Will I lose data and software each time that I flash my phone?
2) How do I check if I'm s-off or s-on?
3) Is there a ROM that you'd recommend?
Thanks
Click to expand...
Click to collapse
1. when completely changing the rom..you need to wipe your phone completely..so that will cause data loss..
(but the apps and contacts will be linked to your gmail account...so they can/will be added, you can backup your messages and call logs using an app (there are lot out there) , the only thing you lose is system data (wifi pairings,bluetooth pairings, the phone data usage etc etc) and data of the apps... i use titanium backup for saving data of apps and restore them once i change a rom)
Also remember ..you no need to wipe unless mentioned..when upgrading the same custom rom ..like going from 1.2 to 1.3 etc etc
2.to check for SOFF..you need to go to bootloader..and see
to go to bootloader ...uncheck fastboot in settings -> power
then power of your phone
then hold volume down and power together...you'll go to a white screen ..it
has all the details...post it here ..so that i can confirm you are soff
3.im currently using sense 4 ROM ..check my signature..almost all sense 4 roms ..here are pretty stable..except two bugs...wifi theter and hdmi out..i dont need them so ..im on sense 4 ...for sense 3.6 you can go for any ROM..as they are completely stable..no bug at all imho
Hi press volume down and power OR pull battery, put back in press volume down and power, this will take you to your menu where you can see if your soff or on. When flashing roms ALWAYS do a full back up of
Current rom, then use a app. Of your choice to backup applications. This way if something goes wrong during flashing you can restore recent rom and apps remember to please flash apporiate firmware before flashing your rom. Ics firmweare is usually 3.32. Gb firmweare is différent. If you ignore this step you will be headed for trouble. Follow thé guides to flashing with either s-on or off. Depending on which you are . There are à lot of great stable roms out there depending on YOUR personal prefrence. You can find a senceless rom with victorious inquisition, you can find sence 4 with béats with ordroid, you can find sence 3.6 with béats in many, ive uséd béats by Grogg. Its just à matter of personal taste, look at thé change logs, and screen shots and you can choose from there in development section. Its so wonderful to havé options
And wé have great developers that give us mamy options! Thank God for thèm! So i suggest looking over thé Roms and décide which suites your needs best! This is thé fun part! Good Luck to you. Happy flashing . i hope this helped answer your questions.
Sent from my Sensation 4G using xda premium
What about my settings such as version numbers?
I know for a fact that I'm on hboot 1.27..
I dont wanna download the wrong one?
P.S. You guys are really good with sharing your thoughts
macdadi112 said:
What about my settings such as version numbers?
I know for a fact that I'm on hboot 1.27..
I dont wanna download the wrong one?
P.S. You guys are really good with sharing your thoughts
Click to expand...
Click to collapse
as you are having ICS ..you no need to flash firmware again ..aka version number ..wont change
just flash the rom and enjoy
Sorry but what is ics?
macdadi112 said:
Sorry but what is ics?
Click to expand...
Click to collapse
ICE CREAM SANDWICH android 4.0.3 the one HTC sensation has now
DOH...
HOW does one figure out what ver of isc ver there on?
Hello everyone,
I am in trouble but not sure if I bricked my HTC One X AT&T hboot 1.09 or not
Here is what happened:
I had Android 4.0.3 running and rooted with bootloader unlocked.
S-ON for sure.
Yesterday I tried to install custom rom or I thought if anything wrong goes bad I would upgrade it to the latest
4.2.2 from HTC.
with some commands from the fastboot I believe I distressed the entire system to the point where it cannot boot.
the only thing my device is doing now is just booting to the screen where HTC in green and the red text beneath it or I can go to the
bootloader menu.
I tried to fix this by flashing openrecovery-twrp-2.4.1.0-evita.img
it worked, and I was able to push several ROMs but non of them got installed, I kept getting error status 7.
I wiped everything from the recovery and then locked the bootleader and now I am really really stuck.
just the bootloader is showing.
One last experiment I tried to do, I put my device into fastboot and run the RUU for one of the ROM I downloaded for my device
but I only see a black screen with HTC logo and it kept me waiting more than half hour, I knew this will not work but I thought I would try.
Is my device done and I should through it away or there is a hope of fixing it?
I had this device for more than 2 years so no way AT&T would help, that's my guess.
Please guys, any suggestion? I am all for fixing it.
It was a stupid mistake ahhhh.
Thanks in advance.
Wrong forum mate, this is for the international hox quad-core version. You have to be in the at&t HTC one XL forum.
Mr Hofs said:
Wrong forum mate, this is for the international hox quad-core version. You have to be in the at&t HTC one XL forum.
Click to expand...
Click to collapse
Sorry, is there anyway someone can move this thread to the appropriate forum.
I apologize.
I will report this one to get it moved. Good luck in the correct section
Moved to: AT&T, Rogers HTC One X, Telstra One XL > One X Q&A, Help & Troubleshooting.
(mod team)
Looks like you've possibly made several mistakes there. First problem is you've been lurking in the wrong forum, which means you've probably been trying to flash ROMs that aren't for our device. Our device forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Bookmark that page and make sure you stay within our forum. Flashing ROMs/kernels/radios that aren't intended for our device can very easily result in a bricked phone.
I think your phone is fine as long as you can get it into the bootloader. Your problem when you were flashing ROMs is that TWRP 2.4.x and 2.5.x are buggy and are basically useless. This is probably a blessing in disguise if you were attempting to flash the wrong ROM, it probably saved your ass. Download at least TWRP 2.6 from here and you should be able to flash with no problems, just make sure they're actually our Evita ROMs that you're flashing.
Now, just to make sure this doesn't happen again, what were the commands you issued through fastboot that "distressed" your system? I need to know what you were doing that caused your device to falter. Also, don't ever run a jb RUU while you're s-on or you'll definitely brick your phone, doing that (SuperCID + s-on + jb RUU) has a 100% kill rate.
As a piece of advice, I'd suggest you stop "experiencing" with your device because the experiments you've been conducting could have easily bricked your phone on several occasions. You're extremely lucky. It seems to me that you need to do some research about our device and what you can and can't do with it. A good place to start would be my Evita FAQ and How-To Guide For Beginners threads in my signature, and build from there.
Sent from my Evita
You are not bricked. With this phone, as long as the screen comes on, you are almost certainly not bricked. You just don't know how to recover.
shakash3obd said:
with some commands from the fastboot I believe I distressed the entire system to the point where it cannot boot.
Click to expand...
Click to collapse
What the heck does "some commands" mean? You need to be specific about the exact steps you took. If you don't know the commands you tried, that is a problem, as it implies you are not being careful while modding the phone.
shakash3obd said:
I tried to fix this by flashing openrecovery-twrp-2.4.1.0-evita.img
it worked, and I was able to push several ROMs but non of them got installed, I kept getting error status 7.
Click to expand...
Click to collapse
That is a very outdated version of TWRP, and probably part of your problem. Use an up to date version.
shakash3obd said:
One last experiment I tried to do, I put my device into fastboot and run the RUU for one of the ROM I downloaded for my device
but I only see a black screen with HTC logo and it kept me waiting more than half hour, I knew this will not work but I thought I would try.
Click to expand...
Click to collapse
You can't (and shouldn't) just run any RUU. You should run the proper RUU for your carrier version (AT&T) and with s-on it has to be equal or later then the hboot version on the phone. Also do not run a Jellybean RUU on the phone, since SuperCID + S-on will brick the device on most Jellybean RUUs. You're okay if the screen is coming on, but don't run any RUUs unless somewhere here specifically instructs you to.
You have a couple options to proceed:
1) Re-unlock the bootloader, install an updated TWRP version, and try flashing a custom ROM.
2) If still on hboot 1.09, try running the 1.73 or 1.85 RUU (do you remember what build number you were on when you unlocked the bootloader?).
shakash3obd said:
I had this device for more than 2 years so no way AT&T would help, that's my guess.
Click to expand...
Click to collapse
AT&T warranties phones for 1 year. So you are out of the warranty period, if that is what you are wondering about. And warranty covers manufacturing defects, not damage done by the owner due to their negligence.
Besides, you don't need a repair or replacement. You just need to know how to recover properly from what you have done.
timmaaa said:
Download at least TWRP 2.6 from here and you should be able to flash with no problems, just make sure they're actually our Evita ROMs that you're flashing.
...
Now, just to make sure this doesn't happen again, what were the commands you issued through fastboot that "distressed" your system?
....
Click to expand...
Click to collapse
Thanks for stopping by,
I believe that I cannot flash any recovery mod such as clockwork or TWRP now, because as I explained. I locked the bootloader again.
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
I didn't mean 'distressed' I was trying to say I destroyed, spilling correction mistake.
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me :crying:
redpoint73 said:
That is a very outdated version of TWRP, and probably part of your problem. Use an up to date version.
You have a couple options to proceed:
1) Re-unlock the bootloader, install an updated TWRP version, and try flashing a custom ROM.
2) If still on hboot 1.09, try running the 1.73 or 1.85 RUU (do you remember what build number you were on when you unlocked the bootloader?).
Click to expand...
Click to collapse
Thanks for your comments.
I put the command I used in the previous reply.
As far as the version of TWRP, I originally tried the latest one, but it wont flash at at that's why I tried an older version.
Again in my previous reply i said that I am not able to Re-unlock the bootloader.
Yes I am still in hboot 1.09 but don't remember the build number unfortunately.
Because all what I am in is because of my lack of knowledge of custom roms, would you be able to
point me to where I can download 1.73 or 1.85 RUU?
Also, Do you think I will be able to run RUU even from the bootloader menu. I tried to run RUU from the bootloader and it got stock in the
black screen with HTC logo forever!!
shakash3obd said:
Thanks for stopping by,
I believe that I cannot flash any recovery mod such as clockwork or TWRP now, because as I explained. I locked the bootloader again.
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
I didn't mean 'distressed' I was trying to say I destroyed, spilling correction mistake.
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me :crying:
Click to expand...
Click to collapse
I won't judge you, I'm here to try and help you. Go to htcdev and try unlocking the bootloader again from scratch, hopefully that'll work. If not, I'm really not sure what you can do. In future, just be careful and make sure know exactly what you're doing before you do it. Fastboot commands have very specific functions and should only be used in specific situations, issuing random commands is a bad idea. I you're unsure about anything or if you have any question at all please feel free to ask here or in my q&a thread.
Sent from my Evita
timmaaa said:
Go to htcdev and try unlocking the bootloader again from scratch, hopefully that'll work.
Sent from my Evita
Click to expand...
Click to collapse
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
shakash3obd said:
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
Click to expand...
Click to collapse
That message suggests that you haven't copied the identifier token correctly. You need to make sure you copy the whole thing, including all of the arrows at the beginning and end.
Sent from my Evita
shakash3obd said:
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
Click to expand...
Click to collapse
That error message simply means you cut and pasted the token incorrectly (included an extra character or characters that you were not supposed to). Follow the instruction very carefully and exactly for what exactly needs to be cut and pasted.
---------- Post added at 03:43 PM ---------- Previous post was at 03:37 PM ----------
shakash3obd said:
would you be able to
point me to where I can download 1.73 or 1.85 RUU?
Click to expand...
Click to collapse
All you will mostly likely ever need for this device is in my Index thread:
http://forum.xda-developers.com/showthread.php?t=1671237
shakash3obd said:
Also, Do you think I will be able to run RUU even from the bootloader menu. I tried to run RUU from the bootloader and it got stock in the
black screen with HTC logo forever!!
Click to expand...
Click to collapse
RUU is meant as a recovery tool, and therefore is intended to work while the phone is in almost any condition (as long as the screen comes on), including bootloader.
The reason the RUU did not work, is likely because it was the wrong RUU.
---------- Post added at 03:54 PM ---------- Previous post was at 03:43 PM ----------
shakash3obd said:
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
Click to expand...
Click to collapse
The bootloader unlock is a bit finicky, and its known to fail for some folks for no good reason (even if you did it all correct), possibly even numerous times. I would suggest just making sure you do the steps correctly and keep trying.
shakash3obd said:
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me
Click to expand...
Click to collapse
The only judgement I have of you, is that you seem to be rushing forward a bit too much, and not researching properly.
Fastboot (and phone modding in general) is not a place to be experimenting. You should not be trying fastboot commands haphazardly. I've seen more than a few devices on this forum bricked with a couple careless fastboot commands. I would recommend you not running any fastboot commands, unless you have obtained them from one of the established guides on this forum, or from a reputable/knowledgeable contributor on this forum.
redpoint73 said:
All you will mostly likely ever need for this device is in my Index thread:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Hey guys, I got my device unlocked, i think I copied an extra character.
Now I have an unlocked bootloader + recovery mod 2.6.0.
What should I do next?
should I download RUU from your thread or should should I do something else?
I
I am waiting right here right now until my phone is fixed.
Thank you so much guys
EDIT:
I tried to download RUU 1.73 and the links were down
so i downloaded 1.85 for now.
Waiting for your other instructions. Sir.
shakash3obd said:
Hey guys, I got my device unlocked, i think I copied an extra character.
Now I have an unlocked bootloader + recovery mod 2.6.0.
What should I do next?
should I download RUU from your thread or should should I do something else?
Click to expand...
Click to collapse
Download a custom ROM, move it to your phone, and flash it.
If a custom ROM is what you wanted to begin with, no reason to go backward and RUU (since you were able to get the bootloader unlocked again, and custom recovery installed).
redpoint73 said:
Download a custom ROM, move it to your phone, and flash it.
If a custom ROM is what you wanted to begin with, no reason to go backward and RUU (since you were able to get the bootloader unlocked again, and custom recovery installed).
Click to expand...
Click to collapse
This is actually my original intention, I don't want to have all the junk that comes from HTC and the one from AT&T.
Any recommendation to get something like the kitkat rom that is stable and reliable.
I am asking for recommendation because after all trouble I went through last night, I just want to get my phone to something very nice and stable other than the RUU with HTC and AT&T stuff.
Really appreciate your help.
shakash3obd said:
Any recommendation to get something like the kitkat rom that is stable and reliable.
I am asking for recommendation because after all trouble I went through last night, I just want to get my phone to something very nice and stable other than the RUU with HTC and AT&T stuff.
Click to expand...
Click to collapse
Best/recommended/favorite ROM discussions are not allowed on XDA. They are each good in their own way, and everyone has different preferences. Part of the fun of flashing custom ROMs is trying them out, to see what you like the best.
Try any of the ROMs on my Index thread, and you won't need to worry about a brick. But read through the specific ROM thread as some ROMs have specific flashing procedures.
Bear in mind that KitKat means you will be on an AOSP ROM. Sense is limited to Jellybean, for now.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
shakash3obd said:
Thank you so much guys
Click to expand...
Click to collapse
Feel free to click the "Thanks" button for any posts that you found helpful.
redpoint73 said:
Best/recommended/favorite ROM discussions are not allowed on XDA.
Try any of the ROMs on my Index thread, and you won't need to worry about a brick. But read through the specific ROM thread as some ROMs have specific flashing procedures.
Bear in mind that KitKat means you will be on an AOSP ROM
.
Click to expand...
Click to collapse
I will check the index of yours when I find it since I am always lost in the xda forum.
Sorry to ask for something not allowed in XDA, I will start looking for AOSP ROM since I want something like KitKat.
If we can forget about "recommendation/best ROM" will anyone can point me to where to find KitKat like ROM for my device or
give a list of names or links to threads in XDA. Or even the whole forum starting point for which i can find these type of ROMs
just to avoid bricking my device since it's S-On
redpoint73 said:
RUU is meant as a recovery tool, and therefore is intended to work while the phone is in almost any condition (as long as the screen comes on), including bootloader.
The reason the RUU did not work, is likely because it was the wrong RUU.
Click to expand...
Click to collapse
What I was afraid of is happening, I run RUU 1.85 and I am right now passed 50 minute with the phone screen is black with HTC logo on it.
is this normal?
should I be doing anything? or just wait more or unplug the phone from the PC?
i got this pm and i thot it was worth everyone to see. while i do not recomend turning any device s on,a verizon device that is not unlockable via htcdev is of much more importance,as the only thing that can rescue it is a new enough,signed RUU.
it really is not worth the risk,i promise.
nicholi2789 said:
scotty1223 said:
nicholi2789 said:
Hey there, Sorry to bother you with a PM like a noob, but I just have a quick question for you. I have just received a Certified like new replacement M8 from Verizon because my original one had a manufacturer defect. My original one was S-OFF, rooted, with custom recovery and the latest firmware (1.55.605.2) from Verizon. I'm trying to get it back to as close to stock as possible so Verizon doesn't try and say I modified it and mak me pay for it. I already un-rooted it, flashed stock recovery, and took the latest OTA so my radios match my software version. Then I followed this thread: http://forum.xda-developers.com/showthread.php?t=2708571
to re-lock the bootloader and set the lock status flag. It says locked again in fastboot.
The only thing I have left is the S-OFF that displays in fastboot. I'm trying to find a way to reset that, or at least modify it so it shows S-ON. That way if by some weird chance a Verizon employee boots it to fastboot it will show completely stock and S-ON.
Now i've found this thread: http://forum.xda-developers.com/showthread.php?t=2475216 for resetting the S-OFF flag. I posted in it and asked if it would work on the M8 and nobody could give me an answer. XDA member brymaster5000 told me to ask you and that you could provide an answer.
So finally, my question is, will this fastboot command "fastboot oem writesecureflag 3" work to set my M8 back to S-ON? I know it works on the M7 but nobody can tell me for sure on the M8.
Thanks alot for your time.
Nick
Click to expand...
Click to collapse
I would very strongly recommend that you do not turn s on. Phones came s off ,so leaving out that way is not an issue.
Turning s on may open a can of worms that you cannot recover from,and then you're paying for a phone for sure.
As long as your stock rom, recovery and locked you're good to go
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
What do you mean phones came s-off? Verizon sent people m8s that already were s-off? It just seems like a super obvious indication that the device was modified. Your not the first person that has said that going back to s-on is a bad idea, so I will listen and not tempt fate. But iam curious, What can happen by doing that command that could cause such problems? And don't stock RUUs return you to s-on? Or do they just reset everything else but s-off?
Click to expand...
Click to collapse
before any phone is released,batches are sent off to testers and these devices are always s off. i have owned several factory s off devices,and there is no way of proving the phone you have did not come this way. further, large phone resellers are able to use factory htc diagnostic files to clear security data(sim lock,s off,cid/mid),wich again is a legitimate reason a phone is s off.finding s off in the bootloader is not by any means a "super obvious" indication of having been messed with.
turning the phone s on could cause the tampered flag to reset(we dont completely understand all the things that trip it) or you could end up locked into bootloader with a security warning if the boot,system or recovery are not stock enough. either of these things ARE super obvious indicators that you have messed with it,and tried to hide it.
in the case of the security warning,the only course of action is to:
1)run a signed ruu(wich must meet many criteria since youre now s on)
or
2)re-unlock the bootloader. as you know,using htcdev to unlock is not possible with vzw
an ruu does not change/update the partition where the secutity flag lives and thus will NOT turn you s on.
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
wtoj34 said:
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
thunderbls said:
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
Click to expand...
Click to collapse
You have missed the point... If you are locked into the bootloader with a security warning and s-on, you can not use weak sauce and firewater
Sent from my HTC One VX using Tapatalk
People need to realize that verizon reps and techs see hundreds of phones, they don't know the details of every device. The security and bootloader status is obvious to us because it's our device and we know everything about it. To a samsung person they won't know WTF your talking about.
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
scotty1223 said:
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
Yes, I misinterpreted the comment as general ease of use which makes me look like an idiot given the reason for the response.... my apologies and note to self read xda after nap lol.
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
scotty1223 said:
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
Click to expand...
Click to collapse
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
l7777 said:
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
Click to expand...
Click to collapse
I agree completely.
Sent from my HTC One using Tapatalk
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
dottat said:
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
How do you reset tampered?
scotty1223 said:
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
Paulb787 said:
How do you reset tampered?
Click to expand...
Click to collapse
Search this forum for a thread. I'm at work, I can't link it at the moment
Sent from my HTC One VX using Tapatalk
scotty1223 said:
So far, no m8 ruus yet. Hopefully some start popping up.
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
nicholi2789 said:
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
Click to expand...
Click to collapse
I didn't mean to embarrass you. They were good questions I thot everyone should read. I should have asked you,and can edit them if you wish.
Sent from my HTC PG09410 using Tapatalk 2
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Nah I wasn't really embarrassed. Haha. I just meant that it's slightly embarrassing that I knew so little about HTC devices, but not a big deal or anything. You were right to post it though, there is some good information there that will do lots of people good.
dottat said:
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Definately a great rescue resource. I just want to make sure that folks understand that since it is unsigned,it will do them no good if they are s on,and stuck in bootloader with a security warning.
As you said,they must stay s off to benefit.(further supporting the point of this thread- don't turn s on)
Sent from my HTC PG09410 using Tapatalk 2
I was going to relock/S-On my defective M8 before returning it. I didn't have time though, and ended up just sending back only wiped and un-rooted, although I don't think /system was 100% stock. VZW sent me a text:
VZW FREE MSG: Thank You! The defective device you recently returned has been received by Verizon Wireless.
Click to expand...
Click to collapse
That was several weeks ago, haven't heard a thing since. I'm assuming they didn't care it was unlocked, or they are very slow at processing the devices.
Okay so I haven't rooted or rommed for quite some time and i decided to finally come back to it after stopping over a year ago. I just recently got this m8 for verizon and i wanted to turn it into a developer edition. Well I used sunshine to s-off my device, and i changed my mid and cid to the developer ones. (yes i know they're the right ones. I've triple checked them. All was going well. I then used the jrummy rom installer to install my twrp. When I did that, it rebooted and then all of my stuff was gone except for my hboot, recovery, and fastboot. the recovery said it couldn't mount anything. not even the system! so i couldn't flash anything. i tried sideloading liquid smooth through adb in twrp and all it does is boot loop. so i thought that I should probably run the appropriate RUU. I tried. I keep getting error 155. even after i relocked the bootloader. But before i locked the bootloader i flashed a stock recovery img. i tried manually installing a RUU zip. wrong mid (tried using verizon one when i had already changed the mid to developer one. I can't find the right zip for the developer edition and none of the .exe ones work. i keep getting error 155. So now the only thing i can access is a bootlooping liquid smooth rom and hboot/fastboot/ruu mode. no recovery. and as far as i still know, a recovery cannot recognize the system partition and any .exe ruu gives me the 155 error. I am in desperaste need of help. at this point i don't even care about lollipop and anything. just help get me back to stock please!! :crying: :crying: :crying: :crying:
Edit: I was on Stock Verizon 4.4.4 when I started all of this, and I was following this thread http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
Ryuk666 said:
Okay so I haven't rooted or rommed for quite some time and i decided to finally come back to it after stopping over a year ago. I just recently got this m8 for verizon and i wanted to turn it into a developer edition. Well I used sunshine to s-off my device, and i changed my mid and cid to the developer ones. (yes i know they're the right ones. I've triple checked them. All was going well. I then used the jrummy rom installer to install my twrp. When I did that, it rebooted and then all of my stuff was gone except for my hboot, recovery, and fastboot. the recovery said it couldn't mount anything. not even the system! so i couldn't flash anything. i tried sideloading liquid smooth through adb in twrp and all it does is boot loop. so i thought that I should probably run the appropriate RUU. I tried. I keep getting error 155. even after i relocked the bootloader. But before i locked the bootloader i flashed a stock recovery img. i tried manually installing a RUU zip. wrong mid (tried using verizon one when i had already changed the mid to developer one. I can't find the right zip for the developer edition and none of the .exe ones work. i keep getting error 155. So now the only thing i can access is a bootlooping liquid smooth rom and hboot/fastboot/ruu mode. no recovery. and as far as i still know, a recovery cannot recognize the system partition and any .exe ruu gives me the 155 error. I am in desperaste need of help. at this point i don't even care about lollipop and anything. just help get me back to stock please!! :crying: :crying: :crying: :crying:
Edit: I was on Stock Verizon 4.4.4 when I started all of this, and I was following this thread http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
Click to expand...
Click to collapse
Can you go into bootloader an try to flash twrp via fast boot? Then if you can try going into recovery by picking recovery in boot loader..
Tigerstown said:
Can you go into bootloader an try to flash twrp via fast boot? Then if you can try going into recovery by picking recovery in boot loader..
Click to expand...
Click to collapse
I tried already. it gives me this error in my command prompt:
target reported max download size of 1826414592 bytes
sending 'recovery' (14814 KB)...
OKAY [ 1.373s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.388s
And then that's all I get. twrp was not flashed.
Ryuk666 said:
I tried already. it gives me this error in my command prompt:
target reported max download size of 1826414592 bytes
sending 'recovery' (14814 KB)...
OKAY [ 1.373s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.388s
And then that's all I get. twrp was not flashed.
Click to expand...
Click to collapse
So have you tried to change your Cid back to vzw an run the ruu?
I had the dev cid, but then i changed it to super cid. i'll try the vzw one right now and get back to you in a moment
Ryuk666 said:
I had the dev cid, but then i changed it to super cid. i'll try the vzw one right now and get back to you in a moment
Click to expand...
Click to collapse
An use the VZW ruu too
Tigerstown said:
An use the VZW ruu too
Click to expand...
Click to collapse
I'm using the VZW RUU zip through the external sd card and i changed the cid to the verizon one. It was loading the RUU zip and it gave me this:
Model ID incorrect!
Update Fail!
Press <POWER> to reboot.
When i press power it just throws me back into the bootlooping liquid smooth rom to i have to put it back into fastboot so I'm still at a standstill.
Ryuk666 said:
I'm using the VZW RUU zip through the external sd card and i changed the cid to the verizon one. It was loading the RUU zip and it gave me this:
Model ID incorrect!
Update Fail!
Press <POWER> to reboot.
When i press power it just throws me back into the bootlooping liquid smooth rom to i have to put it back into fastboot so I'm still at a standstill.
Click to expand...
Click to collapse
You change your mid as well? If so can you change it back to VZW one.
How do i go about doing that through fastboot? I did it through adb last time.
Ryuk666 said:
How do i go about doing that through fastboot? I did it through adb last time.
Click to expand...
Click to collapse
Hold tight for a few mins. Don't do anything else. I'm talking to someone now. He is going to join in an finish getting you booted...
Ryuk666 said:
How do i go about doing that through fastboot? I did it through adb last time.
Click to expand...
Click to collapse
any chance you can install teamviewer so i can get you fixed up and booted?
Okay thank you so much. I will sit here and leave it alone and wait patiently lol.
dottat said:
any chance you can install teamviewer so i can get you fixed up and booted?
Click to expand...
Click to collapse
One moment and i'll go do that now.
Ryuk666 said:
One moment and i'll go do that now.
Click to expand...
Click to collapse
PM me the login info...
Dottat you are seriously the man! You are so awesome! I would have never gotten that done myself. You are seriously amazing!
Glad your all set. That's why I hit him up
I am having the exact same issue except i found a couple problems in my recovery log that stumped me some how in the mix my serial number became =£Ðcçy™yüRv–²‹ and my mid shows
ro.boot.mid=
in my boot log what can i do to solve these problems????
---------- Post added at 07:02 AM ---------- Previous post was at 06:45 AM ----------
I am having the exact same issue except i found a couple problems in my recovery log that stumped me some how in the mix my serial number became =£Ðcçy™yüRv–²‹ and my mid shows
ro.boot.mid=smiley and an arrow (woulent paste)
in my boot log what can i do to solve these problems????
People I think it would be best to give up the dev conversion idea on a verizon m8. A bunch of us tried and tried and take this from experience you will be opening up a can of worms. Wouldnt it be nice to be able to oh heck yeah I would like to also but unless your really really really experienced with this stuff your going to be regretting trying it.
It would be nice but I think it wont work because of the cdma side of the verizon m8. It works great on at&t & tmobile verizons which are all gsm. Our verizon phones are world phones and both cdma and gsm so somewhere lies the incompatibility.
Believe me I tried and tried and tried and I spent a lot of time getting my phone back working right again. My recommendation is if your thinking about trying to convert your verizon m8 to a dev edition save yourself a big headache and dont waste your time. Either that or get an at&t or tmobile m8 and convert it, but then use it on either at&t or tmobile where it will work right and the LTE will work.
It was really nice of these guys to help get his phone fixed so anyone else thinking about it learn from his mistake and forget about it lol.
Ryuk666 said:
Dottat you are seriously the man! You are so awesome! I would have never gotten that done myself. You are seriously amazing!
Click to expand...
Click to collapse
Did you get your fixed? because i have similar problem. i got my verizon m8 messed up MiD To 0P6B10000 instead of 0P6B20000. And now i cant flash any official firmware. can you help me out?
Mine did indeed get fixed. But I'm not exactly sure how. Dottat was a huge help. He definitely knows what he's doing lol. He was going through command prompt fastboot commands so fast I couldn't follow him haha.
I have an HTC One M7 from sprint that I owned for not even 6 months before it started randomly bootlooping and losing signal. I gave up on it and used it as a paper weight, but now I would like to finally get it functional again as my old phone is no longer usable. I am new to Android devices. I have read thread after thread for the past 2 days and have yet to fix this phone.
I have cleared all caches and done factory resets to no avail.
The phone is stuck in bootloop if it is allowed to restart as normal. Once booted, it will immediately reboot if you swipe to unlock. If you wait, it will display "com.htc.htcdialer not responding" before rebooting again. It does not bootloop if you put it into bootloader/fastboot/recovery whatever you call it. I am trying to just load Android Revolution on to the phone instead of retrying the old OS.
I have already unlocked bootloader. I originally tried to push the androidrevolution.zip to the phone, but ADB gave an "error: device not recognized". I tried to install twrp recovery, but fastboot gets stuck at "waiting on device". I understand I'm having issues with the PC not recognizing the phone. The only android thing in device manager is "Android 1.0" and it has no driver installed. I have installed multiple drivers and tried different ports and cables. I cannot use PDANet to install drivers to recognize it because I cannot get access to the phone to enable debug mode. I cannot use sideloading because I can't get the device to be recognized. Everything I try seems like a constant circle.
I don't know if I'm giving enough information or not. I'll answer any question/give whatever info you need to solve this.
Can anyone please give me any insight as to how I can get my phone to work before I get angrier and break it?
BUMP
Has anyone else been in the same boat? Still struggling to figure this out.
DoostyD said:
BUMP
Has anyone else been in the same boat? Still struggling to figure this out.
Click to expand...
Click to collapse
If its a software related error you can get rid of it by flashing (installing) the stock firmware again. First you ned to check HBoot and CID. Connect your phone in "fastboot" bode, open commandline and type
fastboot getvar all
Post the output here (Delete your IMEI). Then i will get the right firmware for you and can guide you how to install it.
If the error is hardware related (signal loss?!) you probably can't do much on your own. What brings me no the next question: If you had the phone for just 6 month when the errors occured first, why didn't you let the vendor fix it? Phone still had guarantee.
It just says :
Waiting for device
My computer won't recognize the phone properly.
I took my phone to sprint and was told I would have to pay $65 for a used phone replacement, which I thought was ridiculous. I contacted HTC and was told I would have to pay shipping to send it in, and would be a week before I got an answer for it. (Fix it or refurbished one). So I said screw it, and reactivated my old phone. I'd fix it myself eventually.
DoostyD said:
It just says :
Waiting for device
My computer won't recognize the phone properly.
I took my phone to sprint and was told I would have to pay $65 for a used phone replacement, which I thought was ridiculous. I contacted HTC and was told I would have to pay shipping to send it in, and would be a week before I got an answer for it. (Fix it or refurbished one). So I said screw it, and reactivated my old phone. I'd fix it myself eventually.
Click to expand...
Click to collapse
Make sure you install the "fastboot" driver correctly. Are you running win 8.1?
LS.xD said:
Make sure you install the "fastboot" driver correctly. Are you running win 8.1?
Click to expand...
Click to collapse
I'm pretty positive it's installed correctly. I've deleted it and reinstalled it 3 times. The first two times I did it all manually. The one I'm currently running I got from here:
http://forum.xda-developers.com/showthread.php?t=2317790
I am running Windows 7 Home Premium 64bit.
DoostyD said:
I'm pretty positive it's installed correctly. I've deleted it and reinstalled it 3 times. The first two times I did it all manually. The one I'm currently running I got from here:
http://forum.xda-developers.com/showthread.php?t=2317790
I am running Windows 7 Home Premium 64bit.
Click to expand...
Click to collapse
I meant the HTC driver (for fastboot) -> Your devices must be listed as "My HTC" in the device manager. If it has a yellow exclamation mark, try to install the driver manually for "My HTC".
@DoostyD
LS.xD said:
I meant the HTC driver (for fastboot) -> Your devices must be listed as "My HTC" in the device manager. If it has a yellow exclamation mark, try to install the driver manually for "My HTC".
Click to expand...
Click to collapse
I also had once a problem with HTC drivers, I downloaded HTC Sync Manager and then i connected my device after my pc got all drivers i closed HTC sync and i was able to use fastboot.
Give it a try!
Newyork! said:
@DoostyD
I also had once a problem with HTC drivers, I downloaded HTC Sync Manager and then i connected my device after my pc got all drivers i closed HTC sync and i was able to use fastboot.
Give it a try!
Click to expand...
Click to collapse
I had done that before but it didn't work. I tried it again but this time noticed a windows protection blocking it. I disabled it and got it all to work now!
I put the new rom on the phone but it gets stuck at the HTC screen and never loads. I read that I have to change the CID and change to S-OFF for it to work.
However, now I've got another problem that I can't find a solution to ANYWHERE.
I cannot get the phone to S-OFF. Everytime I try to change my CID I get this:
C:\Android>fastboot oem readcid
...
(bootloader) cid: SPCS_001
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Android>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.006s]
finished. total time: 0.007s
C:\Android>
Click to expand...
Click to collapse
I've tried manually changing the CID and using a CID script and both keep giving me the "[JAVACARD_ERR] SD/USBDISK Init error".
Any ideas??
DoostyD said:
I had done that before but it didn't work. I tried it again but this time noticed a windows protection blocking it. I disabled it and got it all to work now!
I put the new rom on the phone but it gets stuck at the HTC screen and never loads. I read that I have to change the CID and change to S-OFF for it to work.
However, now I've got another problem that I can't find a solution to ANYWHERE.
I cannot get the phone to S-OFF. Everytime I try to change my CID I get this:
I've tried manually changing the CID and using a CID script and both keep giving me the "[JAVACARD_ERR] SD/USBDISK Init error".
Any ideas??
Click to expand...
Click to collapse
Is your phone already S-OFF ? Uninstall HTC sync before changing the CID. If you want to flash a unbranded firmware later, make sure that its compatible with your MID.
BTW
Why don't you flash the sprint firmware again to check if your error got fixed.
Here is the link to the current Sprint RUU:
http://www.htc.com/us/support/htc-one-sprint/news/
Sent from my HTC One_M8 using XDA Free mobile app
Newyork! said:
@DoostyD
I also had once a problem with HTC drivers, I downloaded HTC Sync Manager and then i connected my device after my pc got all drivers i closed HTC sync and i was able to use fastboot.
Give it a try!
Click to expand...
Click to collapse
LS.xD said:
Is your phone already S-OFF ? Uninstall HTC sync before changing the CID. If you want to flash a unbranded firmware later, make sure that its compatible with your MID.
BTW
Why don't you flash the sprint firmware again to check if your error got fixed.
Click to expand...
Click to collapse
No, the phone says it's S-ON. If I uninstall HTC Sync, won't that remove the drivers I needed to get my computer to recognize my phone?
I'm sorry I'm new to this, but what is MID?
I thought about retrying the original sprint firmware but I'd honestly rather just try out a new custom one.
c5satellite2 said:
Here is the link to the current Sprint RUU:
http://www.htc.com/us/support/htc-one-sprint/news/
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
My bootloader is unlocked and I have TWRP recovery. Would I have to remove those to use the Sprint RUU?
DoostyD said:
My bootloader is unlocked and I have TWRP recovery. Would I have to remove those to use the Sprint RUU?
Click to expand...
Click to collapse
Just relock your bootloader to use the ruu BUT if your phone is S-ON you can only RUUs that are newer or the same version number as actually installed on the phone. You can safely uninstall HTC sync, drivers persist.
The RUU link I posted is LP and was just released. Should be newer than what he was running.
Sent from my HTC One_M8 using XDA Free mobile app
c5satellite2 said:
The RUU link I posted is LP and was just released. Should be newer than what he was running.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I checked the RUU myself. Was just a general information and not a "stop, what are you doing?!''
LS.xD said:
I checked the RUU myself. Was just a general information and not a "stop, what are you doing?!''
Click to expand...
Click to collapse
Ok, cool. Just letting him and everyone else know.
Sent from my HTC One_M8 using XDA Free mobile app