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.
Related
I cannot find an answer to my problem as hard as i look. today, i decided to root my phone (HTC vivid). I rooted it successfully, i went to the Superuser and it said it needed to be updated and to flash a kernel or something like that. (i was using this program http://forum.xda-developers.com/showthread.php?t=1498003) I went to the program that i meantioned above and i clicked flash stock vivid kernel, thinking that this was the kernel i had to update or flash or whatever then my phone reboots and its all like Hurr duur im stuck on the HTC screen watcha gonna do about it. I tried many things:
One thing i tried was to do the .zip thingy, with the boot loader relocked, and it wont boot to anything else but the boot loader
i tried also to do the ruu thing, but it kept giving me errors about my phone model or something like that
Can someone please tell me what i did wrong and how to fix it?
i would really appreciate it big time!
Edit: i have an micro sd, if that info helps
I would try to restore it back to stock.
Relock to bootloader if it isn't still locked.
Then run the stock ruu for your phone from http://forum.xda-developers.com/showthread.php?t=1338919
I had my vivid stuck on the HTC screen and this worked for mine.
Also, If you rooted to ICS you are most likely stuck until the official RUU from HTC is out...
FernandoR211 said:
I would try to restore it back to stock.
Relock to bootloader if it isn't still locked.
Then run the stock ruu for your phone from http://forum.xda-developers.com/showthread.php?t=1338919
I had my vivid stuck on the HTC screen and this worked for mine.
Also, If you rooted to ICS you are most likely stuck until the official RUU from HTC is out...
Click to expand...
Click to collapse
You need to install HTC sync or the htcdrivers before running the ruu otherwise it won't see your phone and will just error out.
Sent from my HTC PH39100 using xda premium
pichi123 said:
I cannot find an answer to my problem as hard as i look. today, i decided to root my phone (HTC vivid). I rooted it successfully, i went to the Superuser and it said it needed to be updated and to flash a kernel or something like that. (i was using this program http://forum.xda-developers.com/showthread.php?t=1498003) I went to the program that i meantioned above and i clicked flash stock vivid kernel, thinking that this was the kernel i had to update or flash or whatever then my phone reboots and its all like Hurr duur im stuck on the HTC screen watcha gonna do about it. I tried many things:
One thing i tried was to do the .zip thingy, with the boot loader relocked, and it wont boot to anything else but the boot loader
i tried also to do the ruu thing, but it kept giving me errors about my phone model or something like that
Can someone please tell me what i did wrong and how to fix it?
i would really appreciate it big time!
Edit: i have an micro sd, if that info helps
Click to expand...
Click to collapse
1. You obviously didn't know what you were doing. Lessons for next time.
2. If the .zip thingy made the bootloader update and it seems like it managed to flash everything alright, then you need to make sure the zip isn't on any storage connected to the phone, then go from bootloader to fastboot, unlock the bootloader using the HTCDev bootloader unlock procedure (I hope you kept your unlock_code.bin!), then fastboot flash a recovery.img, then boot to recovery from the bootloader, and flash an ICS ROM, then go back to fastboot and flash the boot.img to get the kernel flashed.
I'm guessing that you may have flashed the ICS bootloaders, but you aren't specific enough. What ruu did you try to run, exactly what zip did you try to install?
You didn't do anything wrong, you just didn't complete the procedure.
kozmikkick said:
You need to install HTC sync or the htcdrivers before running the ruu otherwise it won't see your phone and will just error out.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Well I hope that was a given. BUt I guess I should have listed it. Good point!
If you have an AT&T Vivid, then you should be okay, run the latest ICS RUU and hope for the best. If not, you'll have to do it the old fashioned way through lots of fastboot commands.
thank you everyone!
/thread
Hi guys i decided i wanted to try the google play edition. So i got root, installed custom recovery and took a nandroid backup.
I then installed the latest play 4.3 rom. Didnt like it so went back into my cmw and restored the nandroid. Cool phone running fine again.
But i keep getting updates and when rebooting to install it would fire it into cmw and said couldnt mount. So i thought id reset the phone, and it rebooted to cmw again.
Read online it might be because the bootloader was unlocked. So i used the command fastboot oem lock in command prompt and relocked it. Now every time i try to reset the phone or update it im dropped to the bootloader
i thought an rru would fix it but i couldnt find one for my phone.
Its the htc one m7, was on o2 but i had it unlocked. It has hboot 1.54 so i couldnt get s-ff, baseband 41.17.3250.14. With the bootloader in tampered but relocked mode.
Any help would be appreciated. Just want my phone working again.
Ps i tried the guides to go back to stock. I dont have a 401 so i tried the rru, which i couldnt find for my phone and i cant seem to find the stock recovery for my device to reflash that see if its the problem, i tried a guide to extract from the nandroid, but altho i had root i couldnt see the folders. Tried the rom manager method as well and it says there is no backups altho there is one showing in cmw which i now cannot get into since relocking the bootloader
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
So... I'm embarrased to say, I am stuck. I usually figure this stuff out, but this one's got me stuck.
While trying to S-0ff (1.57) I somehow have erased something important . I've rooted probably 25 phones. Every HTC I've had I rooted, and S-Off. But I have NO idea how I did this.
It all started when I re-locked my bootloader so I could RUU in order to try one method for S-off (I've tried about 10 times to s-off with no luck - firewater, moonshine, rumrunner, etc.)
Every time I tried to flash RUU to fix it via fastboot I got a verification error. Not only that but after I tried, my phone would only boot to bootloader. I then tried unlocking the bootloader again, and suddenly it booted back to my origional (ViperRom) Rom. I thought everything was good, but I tried flashing CM11, and ran firewater again on a last ditch effort. It was then that I noticed I had no cell signal. When I booted into bootloader again is says "OS- " - nothing. I have no "OS" under the bootloader. It had been the 5.x
I've tried RUU the same firmware. - errors. I tried reflashing VenumRom - boots to lock screen, but when I swipe up, HTC logo with white screen appears and stays. It eventually reboots.
So the only thing I can boot is CM11, but I don't have cell signal.
The kicker is I was in such a hurry (wife's phone) that I didn't nandroid.... :crying:
SO does anyone have a nandroid (of m7wls) I can have a copy of? I can change to any recovery. I have no problem with that, but I have NO idea how I even got here and I've tried everything I can find on it. I've been trying for hours.
I can't find a stock rom that I can flash in recovery - I've looked all over - other versions galore, but no m7wls.
Or any other suggestions...
boytoreckonwith said:
So... I'm embarrased to say, I am stuck. I usually figure this stuff out, but this one's got me stuck.
While trying to S-0ff (1.57) I somehow have erased something important . I've rooted probably 25 phones. Every HTC I've had I rooted, and S-Off. But I have NO idea how I did this.
It all started when I re-locked my bootloader so I could RUU in order to try one method for S-off (I've tried about 10 times to s-off with no luck - firewater, moonshine, rumrunner, etc.)
Every time I tried to flash RUU to fix it via fastboot I got a verification error. Not only that but after I tried, my phone would only boot to bootloader. I then tried unlocking the bootloader again, and suddenly it booted back to my origional (ViperRom) Rom. I thought everything was good, but I tried flashing CM11, and ran firewater again on a last ditch effort. It was then that I noticed I had no cell signal. When I booted into bootloader again is says "OS- " - nothing. I have no "OS" under the bootloader. It had been the 5.x
I've tried RUU the same firmware. - errors. I tried reflashing VenumRom - boots to lock screen, but when I swipe up, HTC logo with white screen appears and stays. It eventually reboots.
So the only thing I can boot is CM11, but I don't have cell signal.
The kicker is I was in such a hurry (wife's phone) that I didn't nandroid.... :crying:
SO does anyone have a nandroid (of m7wls) I can have a copy of? I can change to any recovery. I have no problem with that, but I have NO idea how I even got here and I've tried everything I can find on it. I've been trying for hours.
I can't find a stock rom that I can flash in recovery - I've looked all over - other versions galore, but no m7wls.
Or any other suggestions...
Click to expand...
Click to collapse
I don't know which RUU you tried but this site has the latest RUU and firmware. Since you are S-ON you will need to relock your bootloader.
boytoreckonwith said:
So... I'm embarrased to say, I am stuck. I usually figure this stuff out, but this one's got me stuck.
While trying to S-0ff (1.57) I somehow have erased something important . I've rooted probably 25 phones. Every HTC I've had I rooted, and S-Off. But I have NO idea how I did this.
It all started when I re-locked my bootloader so I could RUU in order to try one method for S-off (I've tried about 10 times to s-off with no luck - firewater, moonshine, rumrunner, etc.)
Every time I tried to flash RUU to fix it via fastboot I got a verification error. Not only that but after I tried, my phone would only boot to bootloader. I then tried unlocking the bootloader again, and suddenly it booted back to my origional (ViperRom) Rom. I thought everything was good, but I tried flashing CM11, and ran firewater again on a last ditch effort. It was then that I noticed I had no cell signal. When I booted into bootloader again is says "OS- " - nothing. I have no "OS" under the bootloader. It had been the 5.x
I've tried RUU the same firmware. - errors. I tried reflashing VenumRom - boots to lock screen, but when I swipe up, HTC logo with white screen appears and stays. It eventually reboots.
So the only thing I can boot is CM11, but I don't have cell signal.
The kicker is I was in such a hurry (wife's phone) that I didn't nandroid.... :crying:
SO does anyone have a nandroid (of m7wls) I can have a copy of? I can change to any recovery. I have no problem with that, but I have NO idea how I even got here and I've tried everything I can find on it. I've been trying for hours.
I can't find a stock rom that I can flash in recovery - I've looked all over - other versions galore, but no m7wls.
Or any other suggestions...
Click to expand...
Click to collapse
Your os version is missing because you used a version of twrp recovery that has the misc partition bug. But it is only cosmetic. Your os (firmware) is still there it just doesn't show the version number. Flashing firmware or an ruu will fix it.
Now on to the more serious problem, which sounds like you have Unknown imei and Baseband. Check under settings to see if your Imei and baseband are correctly displayed.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Your os version is missing because you used a version of twrp recovery that has the misc partition bug. But it is only cosmetic. Your os (firmware) is still there it just doesn't show the version number. Flashing firmware or an ruu will fix it.
Now on to the more serious problem, which sounds like you have Unknown imei and Baseband. Check under settings to see if your Imei and baseband are correctly displayed.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Well, you are correct about baseband missing. I don't even see imei anywhere - didn't think sprint had that... anyways. I tried both locked AND unlocked bootloader to flash firmware versions 5.05.651.2 and 5.11.401.10.zip. When the bootloader is unlocked I get an error 99 and when it's locked I get signature verification fails.... any ideas?
boytoreckonwith said:
Well, you are correct about baseband missing. I don't even see imei anywhere - didn't think sprint had that... anyways. I tried both locked AND unlocked bootloader to flash firmware versions 5.05.651.2 and 5.11.401.10.zip. When the bootloader is unlocked I get an error 99 and when it's locked I get signature verification fails.... any ideas?
Click to expand...
Click to collapse
I've known many cases of Unknown Imei and Baseband, unfortunately it's not good news. Especially if your s-on. But I only know of one case where the problem was repaired and it was a hardware repair (antenna pin connector)
You can post your getvar all and maybe find some firmware to try but I doubt there's an ruu that you can use with s-on, Since your already on the latest hboot. And downgrading requires s-off.
See one such case here http://forum.xda-developers.com/showthread.php?t=2885235
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Hello,
I am new to xda forum and expecting a helping hand from fellow members, here's the scenario, I have a sprint htc one which was working fine a few days ago before i decided to act smart .
It was rooted when i purchased it so i thought of flashing a new custom rom into it.I tried flashing (HTC_One_-_MaximusHD_53.0.0) and this one (NuSenSeveN-LP-m7-Sprint_v4.02_050715) and ended up being stuck at green HTC logo, even though the physical buttons are performing their respective functions when pressed but the screen shows just the htc one logo and nothing else.
It is unlocked, tampered and s-on and i have twrp recovery on board, hboot 1.57.0000
WHAT I HAVE ALREADY TRIED AND FAILED:
1) tried rum runner to turn s-off because i though may b because of s-on the roms are not being flashed properly but it says adb device not found
2) tried flashing Bad_Boyz_Sprint_ONE_M7_Lollipop_v2.0 but stuck at handsfree activation, even though i deleted htcwizard.apk.
Now the bottom line is, I am unable to use my device and in desperate need of your help.
Please respond, awaiting to put my hand back on the device.
Thank You
Flashing MaximusHD_53.0.0 messed up your partitions (it's not Sprint compatible as far as I know) and NuSenSeveN you have to fastboot flash the kernel separately ( I had the same problem lol)
The easiest fix would be to run the latest RUU and start fresh, then only flash roms that are Sprint compatible.
Sloth said:
Flashing MaximusHD_53.0.0 messed up your partitions (it's not Sprint compatible as far as I know) and NuSenSeveN you have to fastboot flash the kernel separately ( I had the same problem lol)
The easiest fix would be to run the latest RUU and start fresh, then only flash roms that are Sprint compatible.
Click to expand...
Click to collapse
Hey thanks for the response, I am not tech geek so I have no idea how to flash the latest RUU can you please be more specific about how to perform the above mentioned process or can you have a chat on hangouts as I have altready added you on it.
Thanks alot
Try to flash ruu which could be found on other posts do u know how to boot into the bootloader?
problem solved
Update: thanks to @Sloth I have fixed the problem, if anyone out there who owns a sprint htc one and have messed up his phone by flashing an incompatible rom the way i did, first relock your bootloader if you are s-on and then simply download RUU file from htc official website, make sure its for sprint variant.
Once the bootloader is relocked simply run ruu.exe file that you have downloaded and you are done.
Note: if the ruu setup says that you phone is not connected or gets stuck, boot into recovery and perform factory, after that re-try running ruu.
Thanks Sloth, and thanks xda members