i have a sprint htc one.
i unlocked the bootloader via htcdev site.
then flashed latest twrp (v2.6.3.0, clockwork wouldn't flash)
flashed latest supersu.
then obtained s-off through xda (hboot 1.55 before then 1.44 after. maybe did something wrong?)
having issues with "no sim card - 4g lte will not work as sim/uicc is removed. please insert sprint sim/uicc into the device"
tried to relock it so i cant take it in to get that fixed.
did the adb oem lock thing to obtain 'tampered' 'relocked'
tried to flash RUU 1.something.7 and 1.something.10
the RUU 1.something.10 wouldn't even try to go
then the RUU 1.something.7 (also it said current image was 3.something but i couldn't find a RUU for 3.something) tried and failed in the middle
since that failure my phone isn't recognized while in fastboot, but works to access all the files on it
so i'm stuck on s-off hboot 1.44 'tampered' 'relocked' but my supersu seems to still function ok (titanium backup works) and i can still boot into recovery twrp.
my short term goal is to get back to 100% stock to get my simcard issue resolved through sprint or htc or whatever, i don't know what that's about.
my long term goal is to have my 4g working/simcard thing fixed running a custom rom. ie cyanogenmod or something 4.4 kitkat.
any help would be awesome, thank you guys!
Just an FYI, 100% stock is not needed to have Sprint look at it. You can have an unlocked/tampered bootloader and custom recovery and still be within Sprint's S&R policy for warranty issues. However, your ROM must be stock (can still be rooted) so that the technicians are not faced with issues potentially related to poor/incompatible ROM development and code. Essentially, the Sprint tech will want to do a hard reset on the device, and it will need to appear to be stock after the reset so that they can rule out the software causing the issue. If they give you any hassle about the root, tell them to check their M&Ps.
Grab a Stock Rooted ROM and try to flash in recovery, see if that works.
sorry, guess i left out that i been to sprint once for this already, and they said they fixed it yet it came back only 2 days later. but in between those 2 days is when i did all the rooting supersu and s-off cause i thought i was done with them for now. i thought that since the problem was persisting that they might have to check with or send to htc and then they would see it unlocked and rooted etc.
anyway, i haven't actually flashed any roms yet so i should still be stock + rooted. but i'll do as you suggested.
thank you!
Are you on Windows 8 or 8.1?
I'm running windows 8.1. i've been able to work on the phone with windows 8.1 until just recently with the problem i described. also i just flashed a stock rooted rom for 3.04.651.2 (first link in second post http://forum.xda-developers.com/showthread.php?t=2467607 )
my phone is near dead so i'm charging now before i try testing fastboot again.
also, was there a known issue using windows 8.1? when my phone stopped responding in fastboot i noticed that i couldn't get the htc sync thing to open anymore either. but ican still access data on phone from pc normally.
edit: still getting devices not recognized when i plug my phone in while in fastboot =\
When running and RUU from 3.04 to an older version you will have issues right now with fastboot after the RUU reboots the device into RUU mode. If you go from 3.04 to 3.04 then you will have no issues whatsoever, trust me. I have had the same issues but fixed them by thanking the people who hooked us up with the 3.04 RUU link.
---------- Post added at 08:55 PM ---------- Previous post was at 08:50 PM ----------
fragler said:
I'm running windows 8.1. i've been able to work on the phone with windows 8.1 until just recently with the problem i described. also i just flashed a stock rooted rom for 3.04.651.2 (first link in second post http://forum.xda-developers.com/showthread.php?t=2467607 )
my phone is near dead so i'm charging now before i try testing fastboot again.
also, was there a known issue using windows 8.1? when my phone stopped responding in fastboot i noticed that i couldn't get the htc sync thing to open anymore either. but ican still access data on phone from pc normally.
Click to expand...
Click to collapse
Also, one more thing. In order for you to get fastboot working again you just need to uninstall forms of anything HTC as far as drivers and sync. No need to reinstall fastboot and adb add-ons from SDK though. Once you do this you will be golden but dont forget to unplug your device. . . at the same time people dont think to also go into Device Manager and select "View" and enable "Show hidden devices" and this will show you all of the drivers that have been installed even if they are unplugged so look at all of the categories that any HTC One drivers can be installed in to ensure you havent forgotten any of them and then start over by reinstalling the HTC Drivers all over again.
EPayne123 said:
When running and RUU from 3.04 to an older version you will have issues right now with fastboot after the RUU reboots the device into RUU mode. If you go from 3.04 to 3.04 then you will have no issues whatsoever, trust me. I have had the same issues but fixed them by thanking the people who hooked us up with the 3.04 RUU link.
---------- Post added at 08:55 PM ---------- Previous post was at 08:50 PM ----------
Also, one more thing. In order for you to get fastboot working again you just need to uninstall forms of anything HTC as far as drivers and sync. No need to reinstall fastboot and adb add-ons from SDK though. Once you do this you will be golden but dont forget to unplug your device. . . at the same time people dont think to also go into Device Manager and select "View" and enable "Show hidden devices" and this will show you all of the drivers that have been installed even if they are unplugged so look at all of the categories that any HTC One drivers can be installed in to ensure you havent forgotten any of them and then start over by reinstalling the HTC Drivers all over again.
Click to expand...
Click to collapse
that's all i'll need to do? that'd be great! i'll try that now. also, thank you for telling me how to find the drivers, i have done that for something before, but completing forgot how i got to that. Thank you! i'm deleting away right now!
edit: well i went ahead and deleted all the htc stuff off my pc and then went to the htc site to download the latest htc sync. but i got an error when trying to install it.. "1152: error extracting to the temporary location" i ran it as admin and i have like 700bg of free space.. wth? =\
edit: went and plugged the phone in and let the drivers auto detect/install that way. tried fastboot and still isn't being recognized...
There are compatibility issues between HTC Sync and Windows 8.1 from what I have read, though I am not sure that the issue you are having falls into this category. Do you have another PC available to try this on?
no other pc available that doesn't have windows 8.1
i followed some instructions to use adb with ubuntu (partitioned and install ubuntu along side win8.1 specifically for my phone) followed instructions and either i don't know what i'm doing because i don't know a thing about linux anything or it isn't being recognized that way either. =\
Related
So xda, here's the situation.
I'm on stock 2.1 update 1, build number 2.27.651.6. I know you can't root that, which is why I downloaded the RUU that installs 2.27.651.5 back on my phone. Right now, I have a MacBook Pro running Windows 7 under BootCamp. Whenever I run the RUU, plug my phone in, and start it up, it just hangs on that "Verifying information on your Android phone, please wait..." gray box screen the entire time, I see no progress. I just wiped my phone completely hoping it will show up as a new device now, and I also removed all the device drivers installed. I'm about to try the RUU and plugging in the phone fresh one last time, but I need your take on what the problem is. The phone is showing up fine under devices.
Basically, when running this RUU, I have the phone on charge only, on, screen timeout off, and just sitting there plugged in. Once I get this RUU to run and install the new firmware, I'm golden. I just need someone to identify the problem of why it's not getting past the verifying info on my android phone.
Help would be EXTREMELY appreciated, to the point where I'd be willing to pay something like $5 via PayPal for your time if you solve the issue.
Thanks XDA, I'm fully confident if somebody here wants to do this they could solve it in a matter of minutes, and hopefully someone will be as kind to help me out here.
You might try booting into fastboot and trying to run the RUU.
Fastboot: while holding the volume up button press the power button.
Okay, I did that, it says FASTBOOT USB in a red box, do I just leave it now and run the RUU? Or do I need to select any options?
Can you 'adb devices' on the Win7 machine?
if you can, just let it set there - mine took at least 15 minutes to verify or error.
If it errors don'u unplug or mess with the phone, let it sit there. Then restart the RUU and it should work the second time.
I can in fact abd on here, the process works up to the point where I need superuser and it doesn't appear as it's .6 build. I'm going to try running it in FASTBOOT and see what goes on, I just wish something on the phone changed so I knew it was working.
Trashing the RUU, redownloading, and fastboot all solved the problem. Now, it's currently running the RUU. In a second when the RUU finishes I will post the results and retry the adb process, and let you all know. For now, what's the best official 2.1 ROM? I know Regaw has one, and I'm also wondering how his toolbox works.
Alright here's the deal, it's been stuck in the RUU on "Rebooting Android Phone" for more than 10 minutes now, however the bar is still animated and its still working. It just won't reboot for whatever reason. On the phone is htc with a full green bar underneath.
Same problem on my Hero with 2.1-update1 , build number 3.32.405.1CL191507 relase-keys.
Is any way to get this rooted ?
daweed3003 said:
Same problem on my Hero with 2.1-update1 , build number 3.32.405.1CL191507 relase-keys.
Is any way to get this rooted ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=747598
Worked on my new Hero just fine. You can root it,then unroot it if you need to have any warrenty work done on it.You do have to do all the back ups you normally do if you switch to another rom though.
I'm not running any custom roms yet cause I haven't decided on which one to use,but my Sprint CDMA hero rooted easily with this method. Now if the developers will just come out with a 1 click method of installing one of their customs roms.....One can only wish
Mac
Yup, one click root works perfect on .6 builds.... done 2 myself
Thanks "Mac11700" It works
Ok I hope I am in the right section. I have literally tried everything on this forum to return my wife's vivid to stock. The ruu doesn't work it says it's the wrong one, except it's not !!! her phone says vivid in the settings menu but is being reported as holiday in hboot unlocked s-on. I am on windows 8 and none of the fastboot or adb drivers will recognize the device, I even disable driver signing and fastboot will still not recognize it.
The phone has been acting wonky and I want to warranty it. I don't have access to recovery even though I've flashed them multiple times with cwm and goomanager. All I can do is boot into bootloader or boot into android, recovery hangs on htc white screen. phone will not charge when it's off?!?!?! WTF I'm stuck.
all the recovery PH39IMG.zip i can find point to the same file that was on this forum and has been deleted, so i can't try that.
please read my details before you snark me to death.
Thanks
Thread moved to Q&A
Please post in the correct section next time
Moderating from my One Xl
http://forum.xda-developers.com/showthread.php?t=2013122
I uploaded the PH39IMG.ZIP files here.
Sent from my HTC Raider on the Rogers Wireless Network
colonel187 said:
Ok I hope I am in the right section. I have literally tried everything on this forum to return my wife's vivid to stock. The ruu doesn't work it says it's the wrong one, except it's not !!! her phone says vivid in the settings menu but is being reported as holiday in hboot unlocked s-on. I am on windows 8 and none of the fastboot or adb drivers will recognize the device, I even disable driver signing and fastboot will still not recognize it.
The phone has been acting wonky and I want to warranty it. I don't have access to recovery even though I've flashed them multiple times with cwm and goomanager. All I can do is boot into bootloader or boot into android, recovery hangs on htc white screen. phone will not charge when it's off?!?!?! WTF I'm stuck.
all the recovery PH39IMG.zip i can find point to the same file that was on this forum and has been deleted, so i can't try that.
please read my details before you snark me to death.
Thanks
Click to expand...
Click to collapse
i'm kind of a newb so i probably shouldnt be giving advice but how else am i supposed to get 10 posts :B firstly the issue i see is that you are using Windows 8 which to my knowledge isnt supported by HTC.. so there are no drivers for it.. if that has changed and for some reason you are just having issues with the newly released drivers then ignore me haha.. when i was having issues rebooting into recovery i just reflashed the ones that come with the AIO tool.. because i know for sure those work.. i've used both of them and the only recovery that didnt work was the ONE that i tried that didnt come with the AIO..
camo_flage said:
http://forum.xda-developers.com/showthread.php?t=2013122
I uploaded the PH39IMG.ZIP files here.
Sent from my HTC Raider on the Rogers Wireless Network
Click to expand...
Click to collapse
Yeah I tried that and hboot says it's an older version and then makes me reboot. does anybody have a ph39img.zip of the stock ICS recovery for at&t ????
I was able to install VMware on ubuntu and install windows xp inside of it. I got one of the all in one tools to recognize the phone and reboot it into fastboot however now when I try to flash a recover it hangs at writing recovery. Does anybody know how to either fix this or brick the phone worse so I can warranty it?
ubuntu usb?
Maybe try making a bootable ubuntu usb stick and install the android sdk on it, then acsess the phone from there?
I tried fastboot and adb in Linux and the recovery won't write, it copies over but it won't write.
Is there a way to modify the ics ph39img.zip to trick hboot into thinking is a newer version so it won't halt the update?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Hi,
I have unlocked my HTC one using HTC dev tool. Rooted with Hboot. However, i had a problem while doing s-off. I followed the procedure from one youtube channel and it was very thorough and understandable for an amateur user like me. However, my one big mistake is that I assume the procedure works perfectly and hence, i continued with flashing a Google Edition Rom. What makes it worse is that , i didn't back up the storage. Then, this 'BootLoop' problem happens.I have tried some tools that push the Rom from PC to the phone. It doesn't work.
Now, I'm using HTC one tool kit by Squabbi to solve the problem.
But, my the adb devices is missing from PC device manager.
Somebody please be kind to save me and my HTC One.
Thanks a million times
First of all, don't use a toolkit. Go into the bootloader then select fastboot. Then on your computer, open up cmd and type "fastboot devices". If that works, just post here again and I'll try to help.
If that doesn't work, you either don't have the proper drivers, or something else is wrong. The last resort would be to flash the RUU for your model. That almost always works, but will wipe everything.
EDIT: The reason why it says adb device not found is that the phone needs to boot in order to use usb debugging. If it doesn't boot, then it will never work. So do what I said above and let me know the result.
I've been looking for a while for a forum with someone who has my problem hoping to solve it on my own but i haven't found one so if this is a duplicate please post a link so i can do it! thank you!
As far as i know, this m7 has never had s-off because as long as i've had it i haven't been able to access fastboot. i bought it from swappa and it already had root and a custom rom. However a few months later i thought i was going to sell it so i flashed an RUU onto it and declined root. the sale fell through and i'm trying to put a custom rom on it again but i don't have a recovery anymore. it must have gotten wiped when i flashed the RUU? i declined root when i flashed it (because of the sale) and not having root OR a recovery OR access to fastboot i'm not sure what to do from here.
ADB works just fine, as far as i know. i DO have the fast boot option turned off within the os (which is the only thing that boots) i have Hboot 1.44 which should apparently be a BREEZE to get s-off and root with except neither I, or any of the apps, programs, one click root's i've tried have been able to access fastboot.
i HAVE tried multiple machines with multiple OS. (windows 8.1 and Ubuntu 14) i've tried multiple cables. i've tried usb 3.0 and usb 2.0. i've installed htc sync drivers on the windows machine. i've tried the 'naked' unsigned drivers that a few people have said made fastboot work for them but they never worked. although what confuses me most is i've never had a problem with ADB. adb reboot bootloader works for me no issue but as soon as i get into fastboot this device has never been recognized.
at this point i'm rrreeeaaalllyyy tempted to just trash it but i was hoping this phone would last me until the rest of the year so i could save up for the m9.
Thank you so much for your help!! I was as thorough as I could be with the details.. I hope it's enough.
I believe hboot 1.44 had issues with recognition on Windows 8+. Did you try a computer with an older version of windows? I think there is also a thread that might help you out on that.
shinji257 said:
I believe hboot 1.44 had issues with recognition on Windows 8+. Did you try a computer with an older version of windows? I think there is also a thread that might help you out on that.
Click to expand...
Click to collapse
i haven't had the option yet to try with windows 7 but i had hoped that Ubuntu would recognize it because all the problems i've heard from windows 8+ were with the usb drivers.. i will see if i can get my hands on a win 7 machine though.
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Youngtusk said:
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Click to expand...
Click to collapse
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
eyeyousee said:
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
Click to expand...
Click to collapse
Thanks for the tip. Does flashing a boot.img and stock recovery require adb? Currently, that is where my main setback is.
If it doesn't require adb, can you point me into the direction of the right keywords to Google to find out how to do that?