Database Info

[Q] Stock Sensation stuck on white HTC screen and bootloop

Thanks

spturner said:
I have also tried the HTC bootloader unlock on the HTC website, but after following the instructions exactly, it failed. I tried twice.
Click to expand...
Click to collapse
when you are saying it failed what do you mean exactly?
i would suggest you to use ganeshp's guide from general section to S-OFF your device but unfortunately your device is not in working condition

I would say its time to retire your sensation... If you cannot unlock the bootloader and a factory reset does not help then I dont think there is much more that can be done.

I would say... Find the cid then based on it... Find the proper ruu and run it...
Sent from my HTC Sensation using xda premium

The failure I get when trying the HTC unlocking tool is the same as a lot of people have reported

spturner said:
The failure I get when trying the HTC unlocking tool is the same as a lot of people have reported -
c:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.160s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.170s
I've triple checked the process and am sure I'm doing it right.
I bought the phone on ebay a few months ago and it's been working fine up until now.
A few things about the phone however -
1. It was sent to me with a box, but the IMEI number on the phone didn't match the number on the box. I've since found that maybe this could be due to an HTC motherboard repair when it was under warranty (I understand there was a high dust under the screen failure rate on these models ?) This could also explain why the HTC unlock doesn't work ?
2. When I got the phone, I did a factory reset and the only language packs available as part of the factory reset were Asian ones, (Thai etc), but after a full reset, it operated fine in English.
3. The phone is sim-free
Unless anyone can come up with any solutions it sounds like it's time to take a sledgehammer to the thing, and also a mental note to NEVER buy HTC again. Time for the Nexus 4 I think.
Thanks
Click to expand...
Click to collapse
i think that causes the failure because of different imei after motherboard's replacement
if i remember well there is somewhere a thread of what to do when htcdev fails after motherboard is being replacing
and it comes with different imei
but i don't remember where
give it a try and search it

I have none of these, as the phone is completely stock and of course I can't get into the phone to install things or change settings.

spturner said:
Thanks, yes I had already searched and found various ways to do this, but it seems most do not work, or you at least need to have other things installed and working, or USB debugging enabled.
I have none of these, as the phone is completely stock and of course I can't get into the phone to install things or change settings.
Here comes that sledgehammer ! Actually, maybe I'll just fry it in a microwave and post the video on youtube.
Goodbye HTC...you pile of junk phone manufacturer.
Click to expand...
Click to collapse
Nooooooooooo... :silly:
as i said find the proper RUU ...from here and flash it
TIP: RUU can be flashed from bootloader and no adb is required ..thus usb debugging enabling is not required

For the moment, the sledgehammer is put away as it seems you guys might just get me sorted...maybe ?
Thanks

Any further assistance will be much appreciated
Thanks

ask FootBall for the non xe RUU ...

[Q] [Solved] Frequent Signal Drops / RUU Help

So I've read a few things on the forum about signal drops and have tried a few solutions but I wanted to get some additional feedback before I go the ATT:
Just in the past few days, I have had increasingly frequent signal drops. This has become really annoying for me, as it always seems to happen when I am using mobile data or sending a text message. The signal drop is transient and only lasts about 30 seconds before it re-connects to my network. I haven't noticed much correlation with when it actually happens but I have attached a picture just so you all can see how frequent these signal drops are. Happens when phone is asleep or in use. These are the things I have tried:
1) Originally was running KingCobra 1.5 and thought it may have been the ROM so I flashed CM10
2) Flashed radio 2.09 for ATT - this showed no improvement / did not make it worse
3) Wiped cache / Dalvik - no improvement
My next course of action was to go to ATT and get a new SIM card. Is it possible that a faulty SIM over time could cause this? And would replacing the SIM likely help in the experience of this community?
Thanks a lot for the input, and if there is something else I can do that I haven't already tried please let me know!

Faulty SIM is a possibility. Replacing the SIM is a quick, free fix. So its at least good to eliminate as the cause.

redpoint73 said:
Faulty SIM is a possibility. Replacing the SIM is a quick, free fix. So its at least good to eliminate as the cause.
Click to expand...
Click to collapse
Can this sort of thing spontaneously happen? One day the SIM just starts getting derpy?

I've heard of people taking the card tray out and putting a piece of card stock behind their sim to improve contact
Sent from my HTC One XL using xda app-developers app

area51avenger said:
I've heard of people taking the card tray out and putting a piece of card stock behind their sim to improve contact
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Well I got a new SIM from AT&T and I'm still dropping signal. They did say that they just put up LTE towers here where I'm at 2 days ago, which, coincidentally is when I started getting signal drops. I suppose all that is left is for me to RUU? I don't know how to so it should be fun reading up lol

Actually: I made a backup via TWRP before I ever flashed a ROM -- Is there a boot.img of the stock ROM floating around out there that anyone knows about and would this work? That would be a hell of a lot better than having to go through the process of RUU..Or is there any way I could pull it somehow out of the recovery files?
Edit: Could someone enlighten me a little bit on the process of the RUU -- The only thing that is cloudy here is that I am currently running CM10, would I be able to run the executable RUU if I was running a stock odexed/deodexed ROM after re-locking the bootloader? I have looked at this (http://forum.xda-developers.com/showthread.php?t=1814217&highlight=ruu) and the associated guide but this all assumes that I'm already on a stock image right? I've tried doing some reading but I am drawing a blank on the RUU process

TheEmpyre said:
Actually: I made a backup via TWRP before I ever flashed a ROM -- Is there a boot.img of the stock ROM floating around out there that anyone knows about and would this work? That would be a hell of a lot better than having to go through the process of RUU..Or is there any way I could pull it somehow out of the recovery files?
Click to expand...
Click to collapse
This would not be the equivalent of a ruu
Flash a ruu replaces every single file/partition to stock.
Running a backup would just replace system, data, and cache
My opinion would be to ruu, on my previous phone this was the only way to fix data drops of
Sent from my One X using Tapatalk 2

superchilpil said:
This would not be the equivalent of a ruu
Flash a ruu replaces every single file/partition to stock.
Running a backup would just replace system, data, and cache
My opinion would be to ruu, on my previous phone this was the only way to fix data drops of
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I edited my previous post after you posted this but am I able to run an RUU executable if I'm on CM10? Or is this process more complex?

TheEmpyre said:
I edited my previous post after you posted this but am I able to run an RUU executable if I'm on CM10? Or is this process more complex?
Click to expand...
Click to collapse
I had issues with running an ruu actually. Its different with this phone
But you can try backing everything up obviously and running fastboot OEM lock to lock your boot loader
Then put it in hboot not fastboor and hooking it to your computer then running the ruu
It took a few tried to get the program to recognize the phone but it doesn't matter what ROM you are on as long as you are locked
Sent from my One X using Tapatalk 2

superchilpil said:
I had issues with running an ruu actually. Its different with this phone
But you can try backing everything up obviously and running fastboot OEM lock to lock your boot loader
Then put it in hboot not fastboor and hooking it to your computer then running the ruu
It took a few tried to get the program to recognize the phone but it doesn't matter what ROM you are on as long as you are locked
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Ok so to summarize:
1) in bootloader: fastboot oem lock
2) fastboot reboot-bootloader
3) attempt to run the RUU via fastboot USB? I know my computer recognizes my HTC Device if I run "fastboot devices" command
In the case that it totally derps and doesn't recognize what is my recourse? I still have my unlock token bin file which is good, but I wouldn't have an OS to boot into and probably wouldn't be able to flash anything via recovery with a locked bootloader no?
Edit: Forgot that when you unlock bootloader you do it through fastboot with "fastboot flash unlocktoken Unlock_code.bin so ultimately I would be able to re-flash my recovery etc

TheEmpyre said:
Ok so to summarize:
1) in bootloader: fastboot oem lock
2) fastboot reboot-bootloader
3) attempt to run the RUU via fastboot USB? I know my computer recognizes my HTC Device if I run "fastboot devices" command
In the case that it totally derps and doesn't recognize what is my recourse? I still have my unlock token bin file which is good, but I wouldn't have an OS to boot into and probably wouldn't be able to flash anything via recovery with a locked bootloader no?
Click to expand...
Click to collapse
Edit 2, and 3
2) just select boot loader in fast boot
3) attempt to run the RUU via hboot USB
Your recourse would be to unlock again with your unlock token, flash twrp, and either restore a backup or download a stock/rooted ROM and lock and try again
Sent from my One X using Tapatalk 2

superchilpil said:
Edit 2, and 3
2) just select boot loader in fast boot
3) attempt to run the RUU via hboot USB
Your recourse would be to unlock again with your unlock token and either restore a backup or download a stock/rooted ROM and lock and try again
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Sweet I'm gonna give it a try right now -- thanks a lot for the help! And yes I saved my .bin file

TheEmpyre said:
Sweet I'm gonna give it a try right now -- thanks a lot for the help! And yes I saved my .bin file
Click to expand...
Click to collapse
I missed that part in your post and no problem.
Keep us updated, like I said running a ruu was a pain in the butt with this phone.
Sent from my One X using Tapatalk 2

superchilpil said:
I missed that part in your post and no problem.
Keep us updated, like I said running a ruu was a pain in the butt with this phone.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Ok I caught this before doing anything, but hboot USB requires a specific driver? I have no hboot USB mode showing on my bootloader once I select bootloader in the bootloader main screen

TheEmpyre said:
Ok I caught this before doing anything, but hboot USB requires a specific driver? I have no hboot USB mode showing on my bootloader once I select bootloader in the bootloader main screen
Click to expand...
Click to collapse
This is my hopeful assumption, but I would hope the ruu.exe would contain the drivers for hboot USB
I personally haven't had to install any drivers
Nothing pops up stating your computer is installing any drivers or searching?
Sent from my One X using Tapatalk 2

superchilpil said:
This is my hopeful assumption, but I would hope the ruu.exe would contain the drivers for hboot USB
I personally haven't had to install any drivers
Nothing pops up stating your computer is installing any drivers or searching?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I haven't executed any files because I noticed that I only have Fastboot USB...once I exit that and select "Bootloader" then nothing happens and I hear the sound from my PC of a disconnecting device -- So basically I'm confused because you said make sure to execute the RUU when I am in "hboot usb" but I only have "fastboot usb" after I click fastboot in the bootloader....hopefully this makes sense
hboot usb == fastboot usb?

What my screen looks like here before and after selecting bootloader with the power button
Sent from my Nexus 10 using Tapatalk 2

TheEmpyre said:
I haven't executed any files because I noticed that I only have Fastboot USB...once I exit that and select "Bootloader" then nothing happens and I hear the sound from my PC of a disconnecting device -- So basically I'm confused because you said make sure to execute the RUU when I am in "hboot usb" but I only have "fastboot usb" after I click fastboot in the bootloader....hopefully this makes sense
hboot usb == fastboot usb?
Click to expand...
Click to collapse
this is where i had issues, but hboot usb =/= fastboot usb
im trying this myself to see how to get it to recognize it
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
alright, in fastboot run fastboot oem rebootRUU
then run the ruu.exe

superchilpil said:
this is where i had issues, but hboot usb =/= fastboot usb
im trying this myself to see how to get it to recognize it
Click to expand...
Click to collapse
Have you ever tried running the RUU in fastboot usb? Because my computer certainly recognizes my device when its in fastboot usb but as soon as i click it off, it no longer registers my device as connected

TheEmpyre said:
Have you ever tried running the RUU in fastboot usb? Because my computer certainly recognizes my device when its in fastboot usb but as soon as i click it off, it no longer registers my device as connected
Click to expand...
Click to collapse
try my method above, ive tried it with fastboot... the ruu just ignores it
That method should work, the ruu should pick it up and wipe it clean

[Q] Stuck in Clockwork

hello to all, i was given this phone by a friend cuz its stuck in CWM. im not new to android but i am to this phone( i have a G2x wich was easier by far to figure out). anyways after much searching in these forums i couldnt find anything to do with this problem so here it is.
I am stuck in CWM. i try to flash a rom( i have tried multiple times with different roms) and i get an error 7. does anyone one know what that means, and if so how do i fix it?
ive been trying to re root or revert to stock but adb must have been disabled and or debugging. any help would be awesome. for now ill keep searching and trying to get adb up and going...
i wonder if having lg drivers for my g2x on my comp would mess with adb....
any comments and or suggestions would be greatly appreciated

lmao your lucky your friend never heard of google, but I guess you haven't either haha. Anyway, you need to download a new rom and flash because the one on your sdcard is corrupt

Yup more than likely a bad download or possibly a corrupt partition of sdcard, reformat card, redownload rom, check md5sums
Nope having lg drivers won't effect this phone, but not having the right drivers for this phone is probably why adb doesn't work
Also the g2x is kinda fake rooting funky business, as you found this phone is much different. I would suggest booting into hboot and checking what bootloader you have and if the security flags are still on or not, can make a difference when flashing a rom.
Probably worth your while to read through the stickies and search the forum a bit too
Sent from my MyTouch 4G Slide using xda premium

Lol. Seriously dude. I'm not a noob at flashing Roms. I have tried to flash at least 6 different Roms all ending up with error 7. I'm brand new to this phone so treat me like I need a step by step, but don't be condescending plz.
Sent from my LG-P999 using xda app-developers app

demkantor said:
Yup more than likely a bad download or possibly a corrupt partition of sdcard, reformat card, redownload rom, check md5sums
Nope having lg drivers won't effect this phone, but not having the right drivers for this phone is probably why adb doesn't work
Also the g2x is kinda fake rooting funky business, as you found this phone is much different. I would suggest booting into hboot and checking what bootloader you have and if the security flags are still on or not, can make a difference when flashing a rom.
Probably worth your while to read through the stickies and search the forum a bit too
Im gonna have to read the stickies. im gonna have to read the whole forum....dont let the g2xers hear you say its fake flashing lol. first order of buisness is figuring out how to get into this hboot you speak of. everytime i trun the phone on it hits lg splash and then goes straight to cwm
Click to expand...
Click to collapse

In my signature you'll see a "Mirrors" link. Go there and at the bottom of Post #1 you'll see HTCdrivers.exe. Grab them & load 'em up. ADB should work for you then. Then issue "adb reboot recovery" from a cmd line and when there go to "mounts & storage" & activate. Copy the ROM you want to your SD card while retaining your boot.img in your ADB folder. Wipe Dalvik twice. format cache & then factory reset. Format system then under "mounts & storage". After ROM has flashed from .zip in CWM leave it there and issue "fastboot flash boot boot.img" fom ADB. Reboot & let it settle. Should work.
Don't turn your phone on.....go to HBoot by holding volume down & power at the same time & bypass boot sequence..

I should also mention the reason why this phone is messed up like it is. It was rooted running a custom Roman and then the previous owner did and total. Is that gonna matter much?
Sent from my LG-P999 using xda app-developers app

grantusmantus said:
I should also mention the reason why this phone is messed up like it is. It was rooted running a custom Roman and then the previous owner did and total. Is that gonna matter much?
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
I don't think I understand.
---------- Post added at 11:12 PM ---------- Previous post was at 11:07 PM ----------
Sounds like maybe he was flashing while unlocked with the kernel going in seperately. Your HBoot will tell you that if it says "S-On".
All that aside, XMC is right though. Somehow your ROM is corrupt.

Sorry my typing sucks. The previous owner did an OTA update. i try to get to hboot but it goes straight to cwm. downloaded the drivers from the link provided even...still no adb devices listed in the device manager or when i type in "adb devices" command. if i can get adb working i can get this all fixed, but ill be a raped ape if i knew what the hell happened to this phone.
Sent from my LG-P999 using xda app-developers app

grantusmantus said:
Sorry my typing sucks. The previous owner did an OTA
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Thats where your issues are coming from then. You probably have the ....1313 bootloader with S-On. Reread all your responses here & it should get you there.

Well I wouldn't be the first to say that about the g2x, a friend of mine has one and I needed to root it for him, kinda laughed as I read through the forum on how everything is done there, not saying devs aren't talented just saying the phone is well... I don't know how to say it politely so I just won't
Boot into your bootloader and write down everything on that screen here so we can help, if you get adb running just type
adb reboot bootloader
If not power on while holding volume down and you'll get there
My guess is the phone is s-on and the bootloader was at one point unlocked, glad you still have a recovery though, I warned people about this type of stuff before... not to say that I warned you or your friend, just feels as if people believe me some times
Read last post on page 4 some info about your situation, hell skim the whole thread to understand a bit more about htc phones
http://forum.xda-developers.com/showthread.php?p=35743946
Sent from my MyTouch 4G Slide using xda premium

WeekendsR2Short said:
In my signature you'll see a "Mirrors" link. Go there and at the bottom of Post #1 you'll see HTCdrivers.exe. Grab them & load 'em up. ADB should work for you then. Then issue "adb reboot recovery" from a cmd line and when there go to "mounts & storage" & activate. Copy the ROM you want to your SD card while retaining your boot.img in your ADB folder. Wipe Dalvik twice. format cache & then factory reset. Format system then under "mounts & storage". After ROM has flashed from .zip in CWM leave it there and issue "fastboot flash boot boot.img" fom ADB. Reboot & let it settle. Should work.
Don't turn your phone on.....go to HBoot by holding volume down & power at the same time & bypass boot sequence..
Click to expand...
Click to collapse
got adb working...well, adb recognizes a device.....it give me no name just a string of numbers and letters
i followed your instructions to the T. got as far as flashing the rom...error 7 again(big suprise lol)after said error, flashing boot.img doesnt work terminal hangs at waiting for device.
In case your wondering what comes before the error 7....here is:
assert failed: getprop("ro.product.device)=="doubleshot"
E:Error in /sdcard/mikTouch.zip
(Status 7)

String of numbers is your phone, that's normal
Flashing boot.img is done through fastboot not adb, did you ever make it into your bootloader? It may help if you do and write down everything here.
Sent from my Nexus 7 using xda premium

Your gonna laugh at me. Idk what happened, but cwm is gone now. Device isn't recognized by the computer.
Sent from my LG-P999 using xda app-developers app

Pull your battery for 15 seconds then pop it back in. Then hold volume down + power & make sure your usb cord isn't plugged in or it will just start booting. That will take you to your bootloader. Write all that down the use volume down to navigate to the "recovey" option. Use power button to select it. From recovey's initial screen use trackpad to to get to the "install from .zip". Next screen select ".zip location" (or something like that). Trackpad down to the ROM.zip file & select. Install. After done...."fastboot flash boot boot.img" then reboot. Let it settle for 5 minutes.

grantusmantus said:
everytime i trun the phone on it hits lg splash and then goes straight to cwm
Click to expand...
Click to collapse
You get an LG splash??? The MyTouch 4G Slide is made by HTC, not LG. If you get an LG splash, either you have a different MyTouch phone, or something is seriously wrong.

Fuzi0719 said:
You get an LG splash??? The MyTouch 4G Slide is made by HTC, not LG. If you get an LG splash, either you have a different MyTouch phone, or something is seriously wrong.
Click to expand...
Click to collapse
Nice catch Fuzi! That passed right on over my head. Unless the guy before changed the splash screen this is a big UH-OH!!

Fuzi0719 said:
You get an LG splash??? The MyTouch 4G Slide is made by HTC, not LG. If you get an LG splash, either you have a different MyTouch phone, or something is seriously wrong.
Click to expand...
Click to collapse
Wow didn't even see that!
Yeah if the phone you have in your hands is made by lg then that's your issue, you have a my touch q or something, this forum is for the HTC made mytouch 4 g slide. If this is the case it makes a whole lot of sense your errors when flashing, not being able to get into bootloader, etc.
The old good news would be you probably didn't brake anything, just find the right forum, put it into download mode and restore with some kinda lg stock thing.
Sent from my Nexus 7 using xda premium

Lmao. Sorry guys,i wish this was my phone, you guys have a really great community and I was happy to be part of it for the night.
Sent from my LG-P999 using xda app-developers app

grantusmantus said:
Lmao. Sorry guys,i wish this was my phone, you guys have a really great community and I was happy to be part of it for the night.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
come back anytime

[Q] S-Off not working

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

Sprint version bricked?

Recently tried to unroot due to issues with the vibrate motor not working for any notifications or anything. Also, apps started to fail more frequently it was all just becoming a big headache. I had thought for sure I enabled OEM unlocking but at this point its obvious I did not. Currently I can not get phone to boot besides to the encryption page and no idea what pin code would be. I have tried everything imaginable under the sun. In adb I ran the oem unlock string which caused all these issues. If I try to boot into recovery I get the message "Your device is corrupt. It cant be trusted and will not boot". If I try to boot normally i get the message "Your device has loaded a different operating system" then boots to the encryption lock page. I have placed the RUU and other files and attempted the SD card way of running the files to no avail. Does anyone have any other advice to getting this thing back on?
Edit: this can be closed. I flashed nearly every file I could find but nothing would take. Doing it both the adb and SD card method. Finally, I found the zip that the phone finally liked and it finally flashed. OH man cant be any happier to finally have my baby back on. Anyone else become stuck in this issue, just do as others have said, find the correct zip, flash it, and all will be ok.

mbaseball3 said:
Recently tried to unroot due to issues with the vibrate motor not working for any notifications or anything. Also, apps started to fail more frequently it was all just becoming a big headache. I had thought for sure I enabled OEM unlocking but at this point its obvious I did not. Currently I can not get phone to boot besides to the encryption page and no idea what pin code would be. I have tried everything imaginable under the sun. In adb I ran the oem unlock string which caused all these issues. If I try to boot into recovery I get the message "Your device is corrupt. It cant be trusted and will not boot". If I try to boot normally i get the message "Your device has loaded a different operating system" then boots to the encryption lock page. I have placed the RUU and other files and attempted the SD card way of running the files to no avail. Does anyone have any other advice to getting this thing back on?
Edit: this can be closed. I flashed nearly every file I could find but nothing would take. Doing it both the adb and SD card method. Finally, I found the zip that the phone finally liked and it finally flashed. OH man cant be any happier to finally have my baby back on. Anyone else become stuck in this issue, just do as others have said, find the correct zip, flash it, and all will be ok.
Click to expand...
Click to collapse
I'm in this predicament at the moment. I am not able to find the zip file with the same OS as my phone (2.42.617.6)
I am looking at this spreadsheet to locate the correct zip file. Could anyone help me, please? Thanks.
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0

mauiblue said:
I'm in this predicament at the moment. I am not able to find the zip file with the same OS as my phone (2.42.617.6)
I am looking at this spreadsheet to locate the correct zip file. Could anyone help me, please? Thanks.
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
38 or 39 should work. The last octet doesn't matter as that is just sub version. So long as the first 3 octets match ie 2.42.617, your good to go.

shivadow said:
38 or 39 should work. The last octet doesn't matter as that is just sub version. So long as the first 3 octets match ie 2.42.617, your good to go.
Click to expand...
Click to collapse
Thanks shivadow for responding to my post. So I downloaded one of the one of the latest versions (from the zip variant link) and renamed it "firmware.zip" I am using ADB to do the process (https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048) and I get this error:
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 2399200000 bytes
error: cannot load 'firmware.zip'
I renamed it a couple other times and I still get that error above. My phone (U11) is in the download mode. Just for giggles when I type in on the command prompt "fastboot oem rebootRUU" I get to a screen that has HTC on it and says and the warning "Security Warning. If you flash this phone with any ROM that was not officially released by HTC you take the risk of releasing...." When I give the command to flash the zip file I get the same error as above.
I am hopeful that I can get this phone back to normal running status. I just need to get the right commands and files to do this.
I appreciate any and all help to get my phone back to normal again. Aloha.

Sorry just saw all the updates. Notifications turned off apparently. Since I was able to get phone back on I can say it's not like it used to. I've tried to run the RUU which fails every time. And my signal has turned to absolute crap; constant dropped signal and barely any LTE. So, I'm no help since all I've done is get the phone on but not working properly lol.
mauiblue said:
I'm in this predicament at the moment. I am not able to find the zip file with the same OS as my phone (2.42.617.6)
I am looking at this spreadsheet to locate the correct zip file. Could anyone help me, please? Thanks.
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
Sent from my 2PZC5 using Tapatalk

mbaseball3 said:
Sorry just saw all the updates. Notifications turned off apparently. Since I was able to get phone back on I can say it's not like it used to. I've tried to run the RUU which fails every time. And my signal has turned to absolute crap; constant dropped signal and barely any LTE. So, I'm no help since all I've done is get the phone on but not working properly lol.
Sent from my 2PZC5 using Tapatalk
Click to expand...
Click to collapse
Aloha and thanks for taking the time to respond. Well you got farther than me as I was not able to get my phone out of trouble. Tomorrow will make two weeks since I sent my phone out to HTC. I just got the new HTC U12+ yesterday as I can't go without a reliable set because I need one for my jobs.
Next time if I do unlock the bootloader on any phone I will figure out how to do the process of rooting, updating, and not bricking the phone.
I hope you sort things out with your phone.
Sent from my HTC U12+ using Tapatalk

I'm not sure about getting further when it feels messed up still, ha. Yeah I get ya though, had the same experience freaking out that I wouldn't have a phone for work. Fortunately I had my cracked screen m10 that served as a backup until I was able to get the u11 to boot. I swear the last phones I rooted were less hassle than these more complex devices. Hope HTC can get it figured out for you.
mauiblue said:
Aloha and thanks for taking the time to respond. Well you got farther than me as I was not able to get my phone out of trouble. Tomorrow will make two weeks since I sent my phone out to HTC. I just got the new HTC U12+ yesterday as I can't go without a reliable set because I need one for my jobs.
Next time if I do unlock the bootloader on any phone I will figure out how to do the process of rooting, updating, and not bricking the phone.
I hope you sort things out with your phone.
Sent from my HTC U12+ using Tapatalk
Click to expand...
Click to collapse
Sent from my 2PZC5 using Tapatalk

I agree that the past phones were not so hard to unlock, root, update, and tweak. Now with the U12+ dual A/B slot partition and multiple files that are needed to root the phone it can be overwhelming.
I'm sure HTC will be able fix the phone but at what cost? I'm just waiting it out and hoping for the best.
Aloha!
Sent from my HTC U12+ using Tapatalk