I've been rooted on my AT&T One X for some time (it's the most reliable way to get tethering). I've been doing this to my Android phones for some time, and while I've dabbled with ROMs on my old Galaxy I've been comfortable with rooting on all of them to get some perks like tethering.
So now I have a phone with Android 4.0.4, BL-Unlock, SuperCID, and root. It works great, I love it except that now I'm getting constant reminders that an OTA is available; it's annoying and I can't stand it. My plan at this point was to gain S-Off and open up all my options (either going back to straight stock or flashing a ROM).
Unfortunately, the facepalm S-Off isn't working for me. All the steps complete as they are supposed to as far as I can tell but every time I get back to the bootloader, "S-ON" is staring back at me. I've made sure to grant SU permissions for the last command but I've gone through it several times now and nothing. I have no idea what isn't working; anyone have any ideas?
AT&T One X
Android 4.0.4
Software 2.20
Unlocked
SuperCID
HBOOT 1.14
Rooted
Reboot your phone and try again. If you could pastebin your cmd and link here so I could see what's happening I should be able to help but typically, if you're doing everything properly, it doesn't always work the first time. Sometimes you need to reboot the phone and try again
Sent from my HTC One X using xda app-developers app
I've tried about a half-dozen times now and no dice. Here's what my command window showed for the last attempt; as far as I can tell they've all been the same.
I can't post links but the pastebin is YLw1DRgf
This part:
c:\ADB>fastboot flash zip PJ8312000-OneX.zip
sending 'zip' (36064 KB)...
OKAY [ *3.957s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 4.467s
Sent from my HTC One X using xda app-developers app
Needs to give error 92 and not 99.
What rom are you on? Stock rooted works best.
I am stock rooted as far as I'm aware; that's why I'm getting the OTA notifications (I think). The only things that should be changed should be CID and root plus the addition of TWRP Recovery.
tinwhisker said:
I am stock rooted as far as I'm aware; that's why I'm getting the OTA notifications (I think). The only things that should be changed should be CID and root plus the addition of TWRP Recovery.
Click to expand...
Click to collapse
Then reboot and keep trying. Until you get error 92. I've seen it take some people quite a few tries. You can also try changing you're cid to 22222222, sometimes the change in cid gets it working.
Fastboot oem writecid 22222222
Pressing and holding the power button until the screen shuts off simulates a battery pull. If you're not rebooting that way, reboot that way.
Sent from my HTC One X using xda app-developers app
:good: Thanks a lot, after a dozen tries, the hard reset of the phone did the trick. It worked the first time after that.
Edit to say that I did not have to change the CID.
Well i figured i would put this here for anybody having device offline problems while trying to get s-off. If you get "device offline" in the middle of the process like i did you may have to unplug your phone and plug it back in. This seems to be an issue with aosp 4.2.2 roms
sent from my jellybammed one x
I was having the same issue until i tried the hard reset but now when i enter the last three commands they all say "ADB server didn't ACK" and when I reboot it still says s-on. am i doing something wrong?
Pastebin your command prompt. I'll see if I can help.
Sent from my HTC One X using xda app-developers app
exad said:
Pastebin your command prompt. I'll see if I can help.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks, but I looked a little harder in the forum and figured out my problem. I didnt unlock the phone before putting the last three commands in haha but now I have a fully unlocked device
Related
I recently bought a new Desire S which works great with me. I installed an update that upgraded my hboot from 0.98 to 0.98.0002. Now I need to s-off it using AlpharevX but it only supports 0.98. My question is: is there a way to downgrade it into 0.98? I followed another guide on the site that didn't help at all & didn't even provide the right rom. Any help
not sure but i think that u need to flash stock rom with 0.98.0000 then s-off ....maybe someone can provide hboot 0.98.0000 image
that's exactly what i've been hoping for. hope someone could do that
Extract it from a RUU or wait until I get home and upload it.
Sent from my HTC Desire S using XDA Premium App
badeaioan said:
Extract it from a RUU or wait until I get home and upload it.
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
Please, I beg you upload it when you can. This would be a great favor for me. Just when excatly do will you return (so I would when to check as there is a big time difference here in Egypt ) Thanks in advance .
Here you go: http://www.mediafire.com/?tiuuiuoc70k3q0j
Remember ! I will not be responsible if you brick your phone. It worked for me though.
Good luck !
ok, thanks so much but I have a very silly question. How do I flash the .img? I know its a very silly one but I'm still a bit of a noob in Android
Reboot your phone into Bootloader and then choose Fastboot.
Open a cmd window, cd into your android sdk folder and then type:
fastboot flash hboot example.img
fastboot reboot-bootloader
*replace example with the name of the img.
I did what you said but when I write "fastboot flash hboot saga_hboot_0.98.img" it displays:
{sending 'hboot' (1024 kb)...
OKAY [ 0.189s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.339s}
any idea what might be causing the signature check error?
I suggest you to flash a RUU and then S-OFF it.
Better and safer.
Sent from my HTC Desire S using XDA Premium App
ok, steps?
http://www.filefactory.com/file/ca1...0805U_38.03.02.11_M_release_177977_signed.exe
download this one and install. put ur phone on usb
u sure? i have a slow (but unlimited) net & what should i do after that, just run the installer & it will downgrade the hboot?
Exactly. It will replace everything: ROM, radio, hboot, etc.
L.E: Have you checked this post: http://forum.xda-developers.com/showthread.php?t=1078497 ?
actually, yes. I've tried the following but it didn't work. Every time I reach step 10 it finishes but doesn't change anything. And I have another question but its out of the topic, if I flash Virtuous Unity ROM, will games & apps recognize the device as HTC Desire S & be compatible or what?
Yes, your device will be recognized as Desire S.
Ohh, that's a great relief. Thank you so much for your help up till now. Hope it works out in the end. Sadly, I won't be able to continue the process today & I'll have to continue tomorrow. Don't worry, I'll immediately post the result when I wake up & finish the process (probably I'll wake up here at about 8:30 - 9:00) & the download takes 30 min. so I'll post the result at about 11:00 - 11:30 in Romania .
Ohh thank you so MUCH. It worked!! Luckily I backed up all my things first. The most important thing is, my hboot is now 0.98.0000! Thanks a million again .
Really glad it all worked out nicely. Have a nice time testing ROMs !
Yeah, got Cyanogenmod & Virtuous Unity but liked Virtuous more. Anyway, thanks so much for all your help . As for anyone that needs to downgrade his hboot, I suggest that he downloads this program & it will do all the work: http://www.filefactory.com/file/ca1f...977_signed.exe. Not my fault if it bricked your phone or if it didn't work but it worked for me. & note that it will erase every thing on the device so back up first.
I'm going to try and cover every detail
I bought a used htc inspre 4g online, i dont know the history of the phone, don't know if it was rooted before and a cant contact the guy who solud it to me
in the hboot the phone displays
ACE PVT SHIP A-ON RL
HBOOT-0.85.0024
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011,00:55:45
the phone´s original carrier is at&t so I bought the unlock code online, I turn the phone on and enter the 8 pin code and a messege apears saying that the phone whas seccesfully unlock from network and that the phone need´s to restart, but when the phone restarts it freezes in the htc white screen, I have to do a battery pull to restart the phone and when it boots its locked again
if I ignore the message and dont reboot the phone it does unlocked an I can reseive calls but the screen to enter the 8 pin number wont go away so a can't acces the phone, just to answer the incoming calls
if i turn the phone on with no sim card it wont letme acces the phone because it will ask me to enter the unlock patron
here is what i've done so far to try to fix it
factory reset for the hboot
it will freeze in the htc white screen, i have to do a baterry pull to reboot the phone and it boots up in the same conditions
installng the sock roms from att by ruu.exe way and sd car PD98IMG.zip file way
both ways it says seccesfully update roms but wen the phone boots in freezes in the htc white screen, I do the baterry pull and wen the phone boots its the same way it was
wipe data/factory reset from the android system recovery <3>
and the phone desplays this message
E:can't open /cache/recovery/command
--wiping data...
formatting /data...
E:can't open /data/cwpkg.zip
E:can't open /data/cw.prop
E:can't open /cache/cwpkg
E:can't open /cache/cw.prop
formatting /cache...
data wipe complite.
I reeboot the phone and it's the same
root with ahhk
I can't acces the phone to put it in usb debugging mode so I have to run the ruu.exe and then exit when it asks me to agree to the update, then a message aperas on the phone that it's on usb debugging mode, the I run the ahhk, but whe it gets to the part of INFOsignature it gives me an error
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 15.460s
rebooting...
finished. total time: 0.172s
Radio downgrade complete - starting next process - please be patient...
the phone reboots and it freezes on the htc white scree
i reed in the effen manual that this error was because the sd card was bad an it could no be used as a gold card, so I went and bought a new one and it keeps giving me the same error
manually downgrade and root (scotty85's guide)
I have to cheeat my phne into usb debbuging mode from the ruu.exe
I can get to step 5 with no errors but wen a paste the "fastboot getvar mainver" it doesnt show 1.31.405.3 it shows 2.47.502.7
and I cant continue the guide
c:\mini-adb_inspire>fastboot devices
HT18GT207390 fastboot
c:\mini-adb_inspire>fastboot getvar mainver
mainver: 2.47.502.7
finished. total time: 0.001s
c:\mini-adb_inspire>
if anyone can help me out or has some other idea to fix my phone I would apreteate it
thanks in advance!!
Not being mean but you should have stopped when the phone unlock code didn't work and then asked for help. Whoever is selling those codes needs to be stopped because they don't work and just screws things up. Factory reset from hboot disables USB debugging. Also what ruu did you run? And what version of hboot do you have now? If you used the ruu for the new 3.20.502.52 it will make things even more difficult. The hack kit failed because your ROM version isn't correct so I am assuming its the newer version just released mentioned above, which doesn't work with the hack kit. Please repost what your hboot screen says now. If your hboot is still .0024 then we may be able to run the old 2.47.502.7 ruu which I have a copy of. It would need to be run from fast boot within hboot though.
Sent from my Inspire 4G using xda premium
Gizmoe said:
Not being mean but you should have stopped when the phone unlock code didn't work and then asked for help. Whoever is selling those codes needs to be stopped because they don't work and just screws things up. Factory reset from hboot disables USB debugging. Also what ruu did you run? And what version of hboot do you have now? If you used the ruu for the new 3.20.502.52 it will make things even more difficult. The hack kit failed because your ROM version isn't correct so I am assuming its the newer version just released mentioned above, which doesn't work with the hack kit. Please repost what your hboot screen says now. If your hboot is still .0024 then we may be able to run the old 2.47.502.7 ruu which I have a copy of. It would need to be run from fast boot within hboot though.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
thanks for you repry!!
the ruu that I used is: RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed
here is whats on my hboot screen
ACE PVT SHIP A-ON RL
HBOOT-0.85.0024
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011,00:55:45
thanks for your help!!
Alright. Format your sd card and leave empty, then put back in phone. Put phone into hboot, select fast boot. Plug phone into PC and then run ruu from PC. If it doesn't get rid of your issue then its possible your emmc chip is going bad.
Sent from my Inspire 4G using xda premium
Gizmoe said:
Alright. Format your sd card and leave empty, then put back in phone. Put phone into hboot, select fast boot. Plug phone into PC and then run ruu from PC. If it doesn't get rid of your issue then its possible your emmc chip is going bad.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
all ready try that, when I run th ruu from the hboot boots the phone boots in to the htc white screen and stays there
if its the emmc chip cant it be fixed?
Have u tried removing the battery for a while and then trying it?
Sent from my Inspire 4G using xda premium
Gizmoe said:
Have u tried removing the battery for a while and then trying it?
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
yes!! I´ve tried that and get the same results!
keops22 said:
yes!! I´ve tried that and get the same results!
Click to expand...
Click to collapse
My guess is one of two things. Bad emmc which can be repaired but requires a new main board. Or a corrupted boot IMG which without s off can't be flashed. Maybe the person who sold it knew the emmc was bad.
Sent from my Inspire 4G using xda premium
Gizmoe said:
My guess is one of two things. Bad emmc which can be repaired but requires a new main board. Or a corrupted boot IMG which without s off can't be flashed. Maybe the person who sold it knew the emmc was bad.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
seens you told me about the emmc I looked arrund and find people with the exact same problem as mine,
thanks for your help, I´m going to try and find someone how can fix it!
Out of the blue, my htc sensation 4g started restarting again & again.
I've tried to flash stock rom again using correct RUU but nothing is working. Yesterday formatted my SD card through other phone & after phone started working nice but when I switched off phone to insert SIM card, it started giving same problem.
Please advise what kind of solutions I have to restore my phone back on stock rom? I don't want to loose my investment.
S-ON
HBOOT: 1.27.0000
cid: T-MOB010
RADIO: 11.23.3504.07_M2
PROVIDER/LOCATION: TMUS T-MOB010
version-main: 3.32.531.14
Try a new battery buddy, this happened to me and I bought an anker battery and its fine now, batteries show wear after time and do need replacing , good luck
Sent from my HTC Sensation Z710e using Tapatalk 4 Beta
I read a lot about people with batteries not making contact with the pins. Maybe stick in a tiny piece of paper to tighten it up?
Sent from my SGH-I727 using Tapatalk 4 Beta
Thanks for the quick reply folks but don't think its battery issue as I'm able to start phone in bootloader everytime.
In bootloader, getting message "No image or wrong image"
Could it be a problem with your SIM maybe ? If your phone can stay powered in bootloader , the radio won't be powered up in bootloader, try a different SIM and see if that helps ? And the no image stuff is just where the bootloader is scanning for update and diagnostic images , nothing to worry about .
Sent from my HTC Sensation Z710e using Tapatalk 4 Beta
I tried it already, this happens with/out SIM card. Started without SIM, with same SIM & with different SIM.
Ummm not too sure I can help then buddy sorry , all I can say is I had the exact same problem as you and I replaced the battery and never had any issues again , good luck in finding a solution , I hope someone can find a solution to your problem
Sent from my HTC Sensation Z710e using Tapatalk 4 Beta
No worries, all kinds of help is appreciated as it's 3rd day with this problem.
What do you think about SD card? Yesterday phone started working when I've formatted my card but after next restart, it started giving same problem.
not too sure, Have you got another sdcard laying around to try ? may not help but worth a try i think, At least you can rule out faulty sdcard if it doesnt help
Flash Boot.img
Sometimes I have the same thing.
What works is to flash de boot.img of the rom again. I see u also have S-ON so I think you allready know how it works.
fastboot flash boot boot.img
Good luck!
>> I see u also have S-ON so I think you allready know how it works.
No not sure what you mean? can you please elaborate.
Tried to flash boot image but got
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
Any suggestion?
hurreyy said:
>> I see u also have S-ON so I think you allready know how it works.
No not sure what you mean? can you please elaborate.
Tried to flash boot image but got
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
Any suggestion?
Click to expand...
Click to collapse
did you unlock the bootloader in order to use the fastboot command?
No I did not & not sure how to do it. Can you please help me to go through the entire process? Any past thread on this topic or link would help.
hurreyy said:
No I did not & not sure how to do it. Can you please help me to go through the entire process? Any past thread on this topic or link would help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1631861
step 1 is for unlocking the bootloader
i suggest you to install a custom rom and see how it goes
after unlocking bootloader follow step 2 for recovery
then from recovery
format all partitions except sdcard
enable smartflash
flash the rom
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