Related
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users
Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.
I am 1.54.
Sent from my Nexus 5 using Tapatalk
Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app
Hi guys,
I'm wondering if someone can help me please. I attempted to root my phone a few months back, not knowing it can't be done on HBOOT 1.54 so ended up flashing Clockwork Mod recovery to the phone (now says TAMPERED)
I got the alert come through to my phone when 4.3 became available, but when downloading it fine, it won't install. It boots into CW recovery and an error saying 'operation aborted' appears very quickly and the phone reboots back into how it was originally before downloading the update.
Does anyone know why this is? Ideally, i'd like to scrap the CWmod and get back to how it was before (like factory etc)
I also can't seem to get my desktop to recognise my phone, I think it's a driver issue, does anyone have drivers for Windows 8?
I have a UK Vodafone contract HTC One.
Please can someone help!
Thanks
You need stock recovery to flash OTA.
You can probably S-Off with rumrunner.
Hello all,
I'll start with saying how awesome you all are!
Now that the pleasantries are done I have a damned frustrating problem.
I converted my Bell mobility m7 to a gpe m7, it was great until I got the ota 4.4.3 update and like many others got the screen glitch.
So I searched for a way to get it back to stock.
Here us what I've done, flashed twrp and restored the nandroid backup for my device ( all good here) I then changed the cid back to bm___001, also all good. Now it asks me to update the ota, it downloads and verifies, but when I select install now, it boots into twrp recovery and does nothing.
My bootloader is also Black and not the normal white.
My hboot is at 1.54, I have no idea how to get the stock hth recovery on this thing... I have s-off, it's unlocked.
I can get the var dump and post it when I get to my pc.
I've been looking for a week now and I'm stuck. Any help would be awesome..
Just a side, why is there no RUU for bell mobility ?
OTAs only install with stock recoveries. You need to find the correct stock version for the Rom you are on. There is a post on here with all the recoveries
Sent from my HTC One using XDA Premium 4 mobile app
Iz3man said:
Hello all,
I'll start with saying how awesome you all are!
Now that the pleasantries are done I have a damned frustrating problem.
I converted my Bell mobility m7 to a gpe m7, it was great until I got the ota 4.4.3 update and like many others got the screen glitch.
So I searched for a way to get it back to stock.
Here us what I've done, flashed twrp and restored the nandroid backup for my device ( all good here) I then changed the cid back to bm___001, also all good. Now it asks me to update the ota, it downloads and verifies, but when I select install now, it boots into twrp recovery and does nothing.
My bootloader is also Black and not the normal white.
My hboot is at 1.54, I have no idea how to get the stock hth recovery on this thing... I have s-off, it's unlocked.
I can get the var dump and post it when I get to my pc.
I've been looking for a week now and I'm stuck. Any help would be awesome..
Just a side, why is there no RUU for bell mobility ?
Click to expand...
Click to collapse
You need stock recovery installed to install OTA updates..
http://forum.xda-developers.com/showthread.php?t=2545227
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Iz3man said:
Hello all,
I'll start with saying how awesome you all are!
Now that the pleasantries are done I have a damned frustrating problem.
I converted my Bell mobility m7 to a gpe m7, it was great until I got the ota 4.4.3 update and like many others got the screen glitch.
So I searched for a way to get it back to stock.
Here us what I've done, flashed twrp and restored the nandroid backup for my device ( all good here) I then changed the cid back to bm___001, also all good. Now it asks me to update the ota, it downloads and verifies, but when I select install now, it boots into twrp recovery and does nothing.
My bootloader is also Black and not the normal white.
My hboot is at 1.54, I have no idea how to get the stock hth recovery on this thing... I have s-off, it's unlocked.
I can get the var dump and post it when I get to my pc.
I've been looking for a week now and I'm stuck. Any help would be awesome..
Just a side, why is there no RUU for bell mobility ?
Click to expand...
Click to collapse
Why would you try and OTA update a phone with TWRP recovery on it ?
the OTA updates check everything on your phone and can only be used on a totally stock phone with Stock Recovery.
have you tried this >> http://forum.xda-developers.com/showthread.php?t=2529225
The odd thing is the HTC sense Rom checks the update and veryfies it , it starts to install then boots into twrp.
I have hboot 1.54, is that going to be an issue, how do I get to 1.55?
Go Here
Read xda carefully to understand these stuff
from HTC One
Alright I installed the Bell recovery and it works fine. Rebooted phone and it asked again to install ota this time I said install now and watched. Seemed to install fine, but at the very end of the install I got the red triangle. I forced a reboot and I get a blue, then pink screen with boot up sounds, then the HTC logo with blue beats logo and it hangs.
I'll flash twrp back on and restore the nandroid backup I have and restart.
Anyone know why I still have the black bootloader and the Google screen at start up.?
Where Can I get the HTC bootloader?
yatindroid said:
Go Here
Read xda carefully to understand these stuff
from HTC One
Click to expand...
Click to collapse
Thanks for the link.. No idea how I didn't find it earlier...
in short, I have a playstore M7_UL that just won't switch to LTE after flashing a couple of lolipop based roms, I already tried messing around with the APN settings. stock roms such as this one (http://forum.xda-developers.com/showthread.php?t=2499452) will work properly with every single feature the phone should have if it was originally from T-Mobile, however I would Ideally like to update my phone to 12.
do you have any suggestions for this problem? or am I stuck with this 4.3 rom? I would like to thank you in advance for your time and consideration, and I wait eagerly for your response.
BNMotive said:
I've tried updating to several Lolipop roms, flashed 2 different radios as well as double checked APN settings and confirmed that my Sim card does support LTE however no luck, I've been having the issue of not being able to retain LTE support. only rom that worked completely was this one http://forum.xda-developers.com/showthread.php?t=2499452 the help would be greatly appreciated to resolve this nightmare.
my carrier is T-Mobile.
Click to expand...
Click to collapse
That is a very old ROM, have you updated your system to the latest Sense 6 firmware? If not, then you might want to run the latest TMOUS RUU. When completed, check to see if you have LTE. My guess you will, then if you want you can try one of the Lollipop ROM.
majmoz said:
That is a very old ROM, have you updated your system to the latest Sense 6 firmware? If not, then you might want to run the latest TMOUS RUU. When completed, check to see if you have LTE. My guess you will, then if you want you can try one of the Lollipop ROM.
Click to expand...
Click to collapse
this makes a ton of sense to me, so I decided to downloaded this RUU http://forum.xda-developers.com/htc-one-tmobile/general/ruu-t-mobile-htc-one-android-4-4-3-t2995420
I tried flashing it through my PC but I get this "Error [170] USB connection error" I read briefly over the code and there are some mentions of re-locking my phone, before I get deeper into this, do you have any suggestions for flashing the right RUU?
I really appreciate the help
BNMotive said:
this makes a ton of sense to me, so I decided to downloaded this RUU http://forum.xda-developers.com/htc-one-tmobile/general/ruu-t-mobile-htc-one-android-4-4-3-t2995420
I tried flashing it through my PC but I get this "Error [170] USB connection error" I read briefly over the code and there are some mentions of re-locking my phone, before I get deeper into this, do you have any suggestions for flashing the right RUU?
I really appreciate the help
Click to expand...
Click to collapse
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Utterly Clueless
majmoz said:
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Click to expand...
Click to collapse
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
BNMotive said:
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
Click to expand...
Click to collapse
I think you have a gross firmware - ROM mismatch. You are running version 1.XX firmware with a version 6.XX or 7.XX rom. You need to update your phone to at least version 6.XX and then see if CM12 will give you 4G. If you still have troubles with it in CM12 but not in the stock then it is CM12 that is the issue! These need to be done in order so that you don't brick your phone!!!
RUU 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.1
RUU 6.10.531.10
BNMotive said:
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
Click to expand...
Click to collapse
if you have a read through the CM12 thread or use the search feature within the thread itself, you will find that 4G / LTE is currently a problem for most users and in all not working, seem's to be a problem with 11 and 12 at the moment.
tried installing the first one, I get Error [155] "The ROM update utility cannot update your android phone. please get the correct ROM update utility and try again."
is there a way to give detailed information of my phone's firmware status? would that help? I thank you for the help.
BNMotive said:
tried installing the first one, I get Error [155] "The ROM update utility cannot update your android phone. please get the correct ROM update utility and try again."
is there a way to give detailed information of my phone's firmware status? would that help? I thank you for the help.
Click to expand...
Click to collapse
as you are s-on you will need to do the updates in order, therefore your next one you'll need will either be a 1.28.531.xx or 1.29.531.xx or even 2.24.531.xx, you need to do them in the correct order otherwise you'll just keep erroring out, easier to just s-off on your current firmware.
you cant jump from 1xxxxxx to 3xxxxxxx
Windows 8.1 proved to be a very bad choice to begin flashing old RUUs. USB drivers went rogue on me, so I decided to switch to an old beat up windows 7 system. worked like a charm, I was able to flash 1.2 and 3.2 things were looking up till tried 4.2, both windows 8.1 and 7 killed the installer, 7 says it is a USB error [171] while 8.1 says it is the wrong RUU. apparently I am not the only one with this issue, I'll see what I can find. I feel that thanks to your help guys I am getting real close, I can almost smell the sweet scent of fresh 4G lolipop brewing.
BNMotive said:
Windows 8.1 proved to be a very bad choice to begin flashing old RUUs. USB drivers went rogue on me, so I decided to switch to an old beat up windows 7 system. worked like a charm, I was able to flash 1.2 and 3.2 things were looking up till tried 4.2, both windows 8.1 and 7 killed the installer, 7 says it is a USB error [171] while 8.1 says it is the wrong RUU. apparently I am not the only one with this issue, I'll see what I can find. I feel that thanks to your help guys I am getting real close, I can almost smell the sweet scent of fresh 4G lolipop brewing.
Click to expand...
Click to collapse
Error 171 is a connection error, meaning the RUU can't connect to/find your phone, recheck your drivers with the phone booted and plugged into the computer and also recheck your drivers with the phone in the bootloader and plugged into your PC, I think you might find when its in the bootloader you have "One" with a yellow exclamation mark in device manager, you will have to manually force the driver, right click and select update driver, you the manual installation instructions, don't let windows search anything itself, it will fail.
have you also tried to just run the updates from your phone, ie settings - about - software updates ?
majmoz said:
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Click to expand...
Click to collapse
majmoz said:
I think you have a gross firmware - ROM mismatch. You are running version 1.XX firmware with a version 6.XX or 7.XX rom. You need to update your phone to at least version 6.XX and then see if CM12 will give you 4G. If you still have troubles with it in CM12 but not in the stock then it is CM12 that is the issue! These need to be done in order so that you don't brick your phone!!!
RUU 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.1
RUU 6.10.531.10
Click to expand...
Click to collapse
Seanie280672 said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone, recheck your drivers with the phone booted and plugged into the computer and also recheck your drivers with the phone in the bootloader and plugged into your PC, I think you might find when its in the bootloader you have "One" with a yellow exclamation mark in device manager, you will have to manually force the driver, right click and select update driver, you the manual installation instructions, don't let windows search anything itself, it will fail.
have you also tried to just run the updates from your phone, ie settings - about - software updates ?
Click to expand...
Click to collapse
after the first comment in this post yeah, I had installed a very early TMOUS RUU, from there it asked to be updated to Sense 6.0, I let it update and from there I flashed CM12 and I had no 4G. would something different happen if i try this again now that I flashed 1.2 and 3.2?
more info though, both computers do "update" the phone but get interrupted. regarding the "wrong" RUU error message from windows 8.1, it says "ERROR[158]: Image Error"
BNMotive said:
after the first comment in this post yeah, I had installed a very early TMOUS RUU, from there it asked to be updated to Sense 6.0, I let it update and from there I flashed CM12 and I had no 4G. would something different happen if i try this again now that I flashed 1.2 and 3.2?
more info though, both computers do "update" the phone but get interrupted. regarding the "wrong" RUU error message from windows 8.1, it says "ERROR[158]: Image Error"
Click to expand...
Click to collapse
Im sure I read through here somewhere ages ago about users having problems with the 4xxxxx update, have a search through this forum for T-Mobile RUU, it was in the main RUU thread, and im sure someone fixed it too.
http://forum.xda-developers.com/htc-one-tmobile
ok so I'm not even gonna explain what brought me here to this point with this phone lol, here is the deal right now...first off the phone works, I just relocked the bootloader, TWRP is installed and I have a stable running rom, the phone boots up normally...the rom I'm using is the one created by a member for VM/Sprint that is debloated, now I guess I could just ask the simple question, wich is why the hell no matter what I do why cant I sign into the HTC theme thing (this is btw why I am reverting back to factory everything) idk if its a problem with the rom, but me and my non patient self decided to just say F it and go back to factory (after that I will Unlock BL again, flash TWRP and flash SU) now I did see on this page for the debloated rom, that there is a full stock rooted img, but every time I tried that one, it returned a error saying something about not finding the meta inf something, so again this brings me back to scratch...so I DL the RUU and ran it, well first time it failed with a 155 error, ok I get it, BL was unlocked, ok I fixed that, BL is now relocked, confirmed in BL
Software Status Official
Relocked
S-On
now re running the RUU from normal bootup, it does its thing, restarts goes into RUU mode, and then when its tying to push, it fails again with a 155 error, I'm at a loss, please help me
or if possible, help me fix the original problems I stated first, either way is fine
Thanks
Michael
UPDATE!!!!
ok after doing some reading...I just kept re running the RUU over and over again, about the 5th time it took, now phone is fully back to stock...however
how do I unlock my BL since I relocked it?
WOW I'm on a roll today!!!!
I just unlocked it like normal, I still had the Unlock_code.bin and I just simply reflashed it, VOILA!!
Deimos_Phobos said:
ok so I'm not even gonna explain what brought me here to this point with this phone lol, here is the deal right now...first off the phone works, I just relocked the bootloader, TWRP is installed and I have a stable running rom, the phone boots up normally...the rom I'm using is the one created by a member for VM/Sprint that is debloated, now I guess I could just ask the simple question, wich is why the hell no matter what I do why cant I sign into the HTC theme thing (this is btw why I am reverting back to factory everything) idk if its a problem with the rom, but me and my non patient self decided to just say F it and go back to factory (after that I will Unlock BL again, flash TWRP and flash SU) now I did see on this page for the debloated rom, that there is a full stock rooted img, but every time I tried that one, it returned a error saying something about not finding the meta inf something, so again this brings me back to scratch...so I DL the RUU and ran it, well first time it failed with a 155 error, ok I get it, BL was unlocked, ok I fixed that, BL is now relocked, confirmed in BL
Software Status Official
Relocked
S-On
now re running the RUU from normal bootup, it does its thing, restarts goes into RUU mode, and then when its tying to push, it fails again with a 155 error, I'm at a loss, please help me
or if possible, help me fix the original problems I stated first, either way is fine
Thanks
Michael
Click to expand...
Click to collapse
If sounds to me like your original problem was uninstalling the stock Sense home launcher. The Sense 7 theme stuff won't work without it
Sent from my HTC Desire 626s using Tapatalk
RUU troubles?
I had a problem with the RUU running and found that (I'm running vista) I needed to download and install from Microsoft the Microsoft Visual C++ 2008 Redistributable Package (X86) onto my laptop and presto...it worked.
Maybe the same problem? Hope I helped you.