Database Info

[Q] HTC Desire Bricked?

I recently tried (foolishly) to do an OTA update from Eclair to Froyo on my rooted Desire and suddenly my device is stuck in a reboot cycle. I do have access to the stock recovery mode and fastboot seems to be working properly. I rooted using unrevoked3 and I don't know if it give me access to any custom recovery tools. I also do not have a goldcard, and as I understand it, I can't make one since I can't get adb up and running.
I have tried pretty much everything I can find that applies to my device, which isn't much since I seem to have some odd bootloader/radio specs which make all the ROMs and RUUs I can find not work. When I boot into fastboot or hboot, my device lists these specs:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-WYNW0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18
I can get to the recovery tool and try running update.zip, but I have only found one which gets past signature verification and then errors with a Status 2. I have also tried running the WWE RUUs from: http://forum.xda-developers.com/showthread.php?t=695667 which will run once I give the device the "fastboot oem rebootRUU" command, but they all fail with a code 130 which means the device doesn't match. Also, the RUUs are all for a 1.1x or 1.2x revision and the loader says I have the 2.25.661.2 when it goes though the "are you sure" messages.
Is there anything else I can do to get this back up and running?
edit: An additional note, I have the SLCD screen which I know causes a bunch of issues since it uses a different driver than the AMOLED one and many of the ROMS, RUUs, etc. don't support it.

Hi tahosa,
I am suffering from the same issue but wondring if the Volume -/+ is working in your case or not, another observation that on the "SHIP S-ON" is this mean anything in locking or security issue?
my device gives :
BRAVO PVT3 S-ON
HBOOT-0.83.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.00.08
Jan 10 2010, 12:12:05
thanks, and I am also doing some research till find solution.... :s

Volume +/-
My volume buttons are working fine. I can navigate through all of the HBOOT and fastboot menus and get to the stock recovery menus. Any information you have would be awesome. I have been bashing my head against this problem for a couple weeks now and gotten nowhere.

Please try to check this link :
http://forum.xda-developers.com/showthread.php?p=7618995
In my case the volume is not worked :s

No change
Nope, the only image I could find linked from there fails with the same error as the RUU. I think it is mainly to do with the fact that my HBOOT version is higher than what everyone else seems to have.
When the image gets loaded during the HBOOT, it verifies just fine, but when it tries to run the device check, it errors with "Model ID incorrect!"

Fixed: Process
EDIT: I don't know how I overlooked this for so long, but since I did my root using unrevok3d I got clockworkmod recovery and a backup of my old image, which is probably why this method worked for me. These instructions may still hold if you are stock, but no guarantees.
I was able to fix my Desire using the following method:
You first need to identify which version of the software you device has using the HTC reflash tools. To do this, boot your device into FASTBOOT and connect it to USB. Start the fastboot tool and reboot it into the OEM RUU mode using "./fastboot oem rebootRUU". This brings you to the OEM reflash mode and you can run any of the available RUU tools from this page: http://forum.xda-developers.com/showthread.php?t=695667. When you run them, they give you the version of the software on the device as well as what they are trying to overwrite with. Write down your software version if the first two groups don't match since you will most likely need a different version. From here, you can try running the update but it may fail. If it doesn't you should be all set.
If you can, find another one of the RUUs on the xda-developer page which matches your software version. Most of those link back to the shipped-roms page, but if you don't see yours on that list, look at http://www.shipped-roms.com/shipped/Bravo/ for the full list of Desire ROMs and RUUs. Mine happened to be the TELUS_WWE_2.25.661, which is a zip file. If the matching file is an exe, you have the HTC install tool, and can use the instructions above to flash it. If not, rename the .zip to update.zip and put it on your SD card and boot into HBOOT.
From HBOOT, choose recovery, and when you get to the black screen with the red error message press VOL-UP and POWER to get to the options and choose "Apply update.zip from SD Card." If everything matches, it will apply the update, and you should be able to boot up into a stock (or somewhat stock, mine was rooted) ROM for the Desire.
Let me know if this is confusing and I will rewrite it to be easier to follow.

[Q] [HTC LEGEND] (bootloader) [ERR] Command error !!!

Hello,
I try to unlock my bootloader with htcdev but i get this error :
C:\Users\Administrator>cd C:\Android
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.009s
How to fix this ? :$

I'm looking too, but for the [Doubleshot].
Trying the same thing myself on the HTC Doubleshot (MyTouch 4G Slide) and no joy, same exact error.
ericosman, did you by chance follow all the advice on HTC's site -- including specifically installing HTC Sync? I didn't install Sync because it looks like stuff I won't use and don't need, except that Sync has some dependencies (like a USB BMP Driver, whatever that is) that might make the difference. I haven't tried yet but I plan to.
I've tried two different versions of Fastboot, one I downloaded from masterjason.com and another I downloaded from Google's Android SDK manager. Both behave identically, despite one being nearly a megabyte where the other was 70 kilobytes.
I've tried reinstalling USB drivers, no joy.
I can get fastboot devices to work, as well as adb anything when the phone is booted, so I don't think drivers are really the issue.
I think it's HTC making a blanket promise that all the phones in that list can do this and indeed not all can.
[EDIT 2012-01-07: Add more info I found]
Gotta love it. Edited the post, and when saving, was told to refresh and log in. Then I wasn't given a chance to copy-paste what I typed. Annoying.
Anyway, see if I can remember what all I typed...
uhm...
I found through Google, and directed to Yet Another Android Forum somewhere on the 'net, that fastboot oem h will provide you a list of commands that are supported, and get_identifier_token was not among them. I suspect it's the phone's bootloader which contains supported commands, not Fastboot executable itself, so it may require downgrading/upgrading to a different HBOOT that has the necessary command support.
I did find readsecureflag which returns the integer "3" on my S-ON device. I assume then that the command I found called writesecureflag similarly takes an integer value, but what value to feed it, I don't know, and I don't want to risk my phone. Seems benign enough, but I know from computer programming that anything looking benign is not always.
Anyway, if you run fastboot oem h and get_identifier_token isn't there, I'd recommend giving up on this particular method of rooting.
Hope this helps.
[Edit 2012-04-15: Strikeout above no longer applicable info]
Turns out, see Aisho's post below, which sums up what eventually worked for me.
I actually had to wait for an OTA to be available long enough for a dev to package it up to a bootloader-flashable package, which included the get_identifier_token. Once I had that version on my phone, I was able to get the token to HTCDEV and get my bootloader unlocked. Not full access, but not bad: The only downside is if I need to flash a kernel I have to do it separately from the ROM through fastboot, and I don't think I can update my radio (not that I should need to). But hey, I can flash a custom ROM and get rid of this nasty crap T-Mobile thinks everyone should have (I will never play bejeweled, so I don't even want that adware/nagware on my phone).
[/edit]

I actually had this same problem with my HTC Wildfire S, and found this thread in searching for answers -- since I figured it out, I figured I'd put the solution out there.
My HBOOT was precisely the version HTC was advertising on their site as necessary for the unlock, which made it all the more perplexing when I repeatedly got this error. But then it occurred to me that while my version might be the same, HTC had stuck a neat little asterisk* next to the Wildfire S initially, saying that it required a new HBOOT anyway. I'd thought I was smarter than they were, but really what's different in the new download is the incorporation of just the command you're missing here. Since the ability to unlock is fairly new (through HTC officially, I mean) they're providing new HBOOTs with that command line included. I flashed the new HBOOT (even though it was exactly the same version) and lo and behold when I tried it again, it accepted the fastboot oem get_indentifier_token command.
I'd check to make sure that the HTC Legend doesn't have an asterisk as well, and maybe redownload the HBOOT anyway just in case. It can't hurt.

Aisho said:
I flashed the new HBOOT (even though it was exactly the same version)
Click to expand...
Click to collapse
I'm having the same problem on htc salsa, I have the version it says i should have, but have no get_indentifier_token, how is HBOOT updated?
My phone is S-ON and Hboot is 1.07.0000

HBOOT is updated via bootloader mode (on my phone, assumably the same for most HTC phones). You will need the correct HBOOT for your phone, and it will probably have to be contained within a full update package (for my phone, it's PG59IMG.ZIP, for the Dream it was DREAIMG.ZIP, your phone model will have its own filename). That file goes on the SD card, you boot into bootloader (usually, remove battery to ensure phone is full off, replace battery, and power up while holding the "VOLUME DOWN" button in). It then checks the file and asks you if you want to update.
However, if your phone is the same or newer version as the file you are trying to use, there's a good chance it will not work (the phone will not downgrade (usually (I think (I could be wrong) ) ) ).
You might also be amongst the lucky few who have a phone with what's called an RUU available. That's an .EXE file you run in Windows, connect your phone, and it writes what's in the file directly to the phone regardless of version.
HIH.

I have the upgraded HBOOT version as Im following a thread for how to do it, which incidentally isnt working, when I go to the bootloader menu it finds the file but does not up date it. It has been updated to the current version stated on htcdev with a FOTA update which may be why the HBOOT upgrade doesnt work.
I have the HTC salsa and it does reference RUU a few times. I dont use windows but HTC sync doesnt seem to find the phone, I have tried many things to get it working
Am I meant to run the EXE provided by htcdev and dont run HTC SYNC? Should I be in the bootloader menu/recovery first before running it?

@ericosman
did you follow every single steps ?
I just did it on my Legend (24 hours ago), in the end I followed the post of BlaY0 (http://forum.xda-developers.com/showpost.php?p=22613990&postcount=62) and it worked great.
And yes, the RUU file is the one of a few MiB that you find at the very beginning at HTCdev.
The only trick is that I had to restore my data backup but also my boot backup, otherwise I was stuck in the hboot.
I did it by flashing the recovery image, as I deleted my old update.zip of ClockWorkMod, following the steps of http://forum.xda-developers.com/showthread.php?t=1290841 (see the end of the post: 'New recovery'). Then I went to 'Advanced restore' and restored both my boot image and my data back.
Always backup your system before playing around !

i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below

chris... said:
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
Click to expand...
Click to collapse
Alright, let's try again.
Before the step 1 of HTCdev, it asks you to upgrade your phone to the latest RUU. You don't have to. (see BlaY0's post [1])
Just download the RUU file, thus you will be able to retrieve the very hboot's zip (just run the EXE, don't go through the installer but instead locate its temporary extraction folder with the task manager and get that rom.zip).
They only want you to install HTC Sync so that your phone is recognized by Windows and the RUU can located it.
[1] BlaY0 explains that you don't have to upgrade to the latest HTC ROM or even RUU.

got it, and dump that zip file with the correct file name onto the root of the sdcard and start the bootloader
YAY it works, time to proceed to unlock
The version I got from a different post must not have been the correct one

im sure im bumping an old thread, but im trying to unlock an old espresso, but its having the same issue as the OP, i cant find the RUU with the new hboot, it currently has the 1.02 hboot, any clues?

Have you tried following the steps I referred to ?
Look at my two posts.
In fastboot, What is displayed besides the hboot version ? Something like "unlocked" ?
If note you have to re-flash your hboot with HTC dev method, once again read the post I linked to.
Sent from my Legend using XDA

just to add that on my MyTouch 4G slide I had hboot-1.44.0007 and gave me the same error as the first post when trying to unlock through htcdev.com. I did an OTA update to HBOOT-1.45.0013 (Software version 1.63.531.2 710RD) then went back to htcdev.com and it worked without problems

Getting this while trying to re-unlock evo 3d ics. hboot 1.58.

It's an old thread but maybe it's helping someone...
If you receive the error described in the topic title/first post you need to simply register to htcdev dot com and follow each step(including the 1st step because that's actually what you need to do )

i got same problem w my Z3 plus hbot will work on my z3 plus????????

Help needed please.... got into a dead end with my One X

Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster

sunster00 said:
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
Click to expand...
Click to collapse
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout

jags_the1 said:
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
Click to expand...
Click to collapse
Hi mate thanks for offering advice and help. I have not had to use your method as I decided to give the HTC bootloader unlock code one final try before proceeding to your rescue plan and all of a sudden it was successful again. I got into recovery and did a nandroid restore so am back online again, but have nevertheless made note of your method in case I become stuck again in the future. Thanks anyway for your reply! :good:

completely stock (never tampered) Mini won't boot past hboot into OS

Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.

iceterminal said:
Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.
Click to expand...
Click to collapse
I gotchu my friend ;D http://www.htc.com/us/support/htc-one-mini-att/news/ That is the ruu for the htc one mini

abzboi said:
I gotchu my friend ;D That is the ruu for the htc one mini
Click to expand...
Click to collapse
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!

iceterminal said:
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!
Click to expand...
Click to collapse
Ah I read that it will work too if it is fastboot which is why you were suggesting it. I'm wrestling with fastboot drivers and windows 8.1 so it is recognized so I dualbooted into ubuntu which can communicate via fastboot so I'm hoping WINE will run and flash the RUU .exe

So I ended up rebuilding an older laptop to Windows 7 and ran the RUU executable and it looked promising at first with the updater recognizing the device and displaying what software version and stuff.... but then when it rebooted into hboot with it's process, the update failed.. not sure if it matters but it was "updating" from the same version as the current version. I was hoping this would be a fresh install. So now I'm looking into maybe doing a fastboot oem unlock and flashing a rom myself. Not sure if this will help me get the phone back from the dead, but going to do some more reading and exploring. If anyone has some shots-in-the-dark they would like to offer, I'm up for trying them.

I hope you would be able to fix it.

Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.

iceterminal said:
Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.
Click to expand...
Click to collapse
Have sent you a PM re your issue.....
Re flashing recovery without fastboot (locked bootloader), it can be done, but only, as far as I know, via the phone os using CWM manager or Flashify (which is a cool app!)

wanted to close the loop on this thread that nelvinchi and I literally tried everything we could think of to bring the phone back to life with no avail. Much respect out to nelvinchi for taking his time to help me out! We've determined that the device has a faulty memory chip and cannot be recovered...

Mine just did the same thing and I can't get through to anything I need help also if you have found a solution

Help my
provided you solve a problem with one htv mini.my I have the same problem, please help me

Sunshine s-off, but can't get Superuser SU Binaries installed.....

I just got S-Off with Sun Shine, but can't seem to get SuperuserSU working (I was going to install TWRP from TWRP Manager after getting SuperuserSU.) Anyone know what I need to do? I looked for a thread that explained the process, but have not found anything. Many thanks!

Flash twrp from fastboot. Flash SuperSU from twrp.
Sent from my XT1254 using Tapatalk

I am trying to flash TWRP with Minimal ADB and Fastboot from here..... http://androidmtk.com/download-minimal-adb-and-fastboot-tool
I keep getting this for messages when I type the command flash twrp.img "cannot load 'twrp.img'
I know that the device is connected since it goes into fastboot when I type "adb reboot bootloader".
Any ideas?

Solved......I am a complete fool. I renamed the recovery image "twrp.img" so the actual file was "twrp.img.img". How embarrassing.....LOL! Time to just go and hit the bar and have a beer! I must have cabin fever after this winter and my mind is not functioning properly. ARGH!

therreid said:
Solved......I am a complete fool. I renamed the recovery image "twrp.img" so the actual file was "twrp.img.img". How embarrassing.....LOL! Time to just go and hit the bar and have a beer! I must have cabin fever after this winter and my mind is not functioning properly. ARGH!
Click to expand...
Click to collapse
It happens a lot[emoji14]
Sent from my XT1254 using Tapatalk

I posted this in the general questions thread, but I wanted to post here as well...
beaups said:
It happens a lot[emoji14]
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I apologize in advance as I'm sure this has been asked toomany times to count, but I have searched and searched thread after thread to see if I can find a solution for about 23 hrs straight, I'm pretty much out of time & panicking now that I messed up beyond fixing. Any advice, help, or a point in the right direction to the right post would be very much appreciated!!!
So, the problem is, I'm not 100% sure but I think I have "soft bricked" my phone... I gained s-off through Sunshine about a week ago, I have been reading & researching how to root my phone for updating to a custom ROM running 6.0 MM for months now trying to prevent any issues & be as well educated as possible...
Last night I finally gained root access using Kingroot, then switching over superSU BUT of course, I had the problem with the binaries. I installed TWRP app to perform the recovery flash to ext SD because I do have a PC, but it's a work computer so I don't have administrator rights to install any programs/apps on the PC such as ADB, Flashify, etc.
Before I decided to restart my phone I had SuperSU running the # sign in the notifications center (re: the binaries), I also had the TWRP manager I chose my device model, but I did not install any files (at least I don't think I did). I was most concerned on my current backup & flashing that to my extSD. Which is what I thought I had done, or maybe I didn't do anything at all? BTW- I have removed the SD card & inserted into my PC to see what files were on it, and nothing!! Nothing at all to do with SuperSU nor TWRP (I have since installed the latest update SuperSU zip file on that card). All I know is I cannot get my phone on past the Verizon screen, I can perform a hard boot & get back into hboot /fastboot, I have all options on the menu, and have tried every one of them minus the 'factory data reset', 'apply from phone storage' or 'ramdump'. I would have typed in the information that the screen says in HBOOT but my phone literally just died from the screen being on so long :-/ I will add that info if needed once I can boot it back up without use of the charging cable.
Any help on what to do would be so greatly appreciated as apparently I'm freaking out & I'm thinking I'm way in over my head not knowing what exactly happened to cause this!!! Please Help:crying:

M-FayeHTC said:
I apologize in advance as I'm sure this has been asked toomany times to count, but I have searched and searched thread after thread to see if I can find a solution for about 23 hrs straight, I'm pretty much out of time & panicking now that I messed up beyond fixing. Any advice, help, or a point in the right direction to the right post would be very much appreciated!!!
So, the problem is, I'm not 100% sure but I think I have "soft bricked" my phone... I gained s-off through Sunshine about a week ago, I have been reading & researching how to root my phone for updating to a custom ROM running 6.0 MM for months now trying to prevent any issues & be as well educated as possible...
Last night I finally gained root access using Kingroot, then switching over superSU BUT of course, I had the problem with the binaries. I installed TWRP app to perform the recovery flash to ext SD because I do have a PC, but it's a work computer so I don't have administrator rights to install any programs/apps on the PC such as ADB, Flashify, etc.
Before I decided to restart my phone I had SuperSU running the # sign in the notifications center (re: the binaries), I also had the TWRP manager I chose my device model, but I did not install any files (at least I don't think I did). I was most concerned on my current backup & flashing that to my extSD. Which is what I thought I had done, or maybe I didn't do anything at all? BTW- I have removed the SD card & inserted into my PC to see what files were on it, and nothing!! Nothing at all to do with SuperSU nor TWRP (I have since installed the latest update SuperSU zip file on that card). All I know is I cannot get my phone on past the Verizon screen, I can perform a hard boot & get back into hboot /fastboot, I have all options on the menu, and have tried every one of them minus the 'factory data reset', 'apply from phone storage' or 'ramdump'. I would have typed in the information that the screen says in HBOOT but my phone literally just died from the screen being on so long :-/ I will add that info if needed once I can boot it back up without use of the charging cable.
Any help on what to do would be so greatly appreciated as apparently I'm freaking out & I'm thinking I'm way in over my head not knowing what exactly happened to cause this!!! Please Help:crying:
Click to expand...
Click to collapse
You are fine. Start fixing it by flashing the latest s-on ruu I have posted. This will NOT affect your s-off or unlocked boot loader status. Then when done flash twrp via fastboot. (Never use that stinking app). Then flash supersu zip in twrp to root your stock rom. If you have fast internet I can always you using team viewer (free app)

I'm still having trouble...
dottat said:
You are fine. Start fixing it by flashing the latest s-on ruu I have posted. This will NOT affect your s-off or unlocked boot loader status. Then when done flash twrp via fastboot. (Never use that stinking app). Then flash supersu zip in twrp to root your stock rom. If you have fast internet I can always you using team viewer (free app)
Click to expand...
Click to collapse
First,I appreciate you getting back tome so soon. I downloaded the latest RUU onto my SD card, then reloaded it into my phone in bootloader, nothing happened
Right now, I still cannot get past the red Verizon screen, my phone won't turn on fully... The options I have are my "Administrator PW protected work PC" that I cannot run fastboot on, or my Nextbook tablet. Would Team View work on either of these since my phone is out of the question?
Rightnow this is what my HBOOT screen is saying....
**UNLOCKED**
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT- 3.19.0.0000
RADIO- 1.12.20.1211
OpenDSP- v47.2.2-00564-M8975-FO.1024
OS-4.17.605.9
eMMC-boot 2048MB
Aug 11 2015, 22:31:04.0
Thanks in Advance!!!

M-FayeHTC said:
First,I appreciate you getting back tome so soon. I downloaded the latest RUU onto my SD card, then reloaded it into my phone in bootloader, nothing happened
Right now, I still cannot get past the red Verizon screen, my phone won't turn on fully... The options I have are my "Administrator PW protected work PC" that I cannot run fastboot on, or my Nextbook tablet. Would Team View work on either of these since my phone is out of the question?
Rightnow this is what my HBOOT screen is saying....
**UNLOCKED**
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT- 3.19.0.0000
RADIO- 1.12.20.1211
OpenDSP- v47.2.2-00564-M8975-FO.1024
OS-4.17.605.9
eMMC-boot 2048MB
Aug 11 2015, 22:31:04.0
Thanks in Advance!!!
Click to expand...
Click to collapse
If nothing ran you have the file either named wrong or have an extra .zip on the end of the name. Make sure you view file extensions to be sure. It's case sensitive and 0P6BIMG.zip
Leading character is a zero.

First part COMPLETE!
dottat said:
If nothing ran you have the file either named wrong or have an extra .zip on the end of the name. Make sure you view file extensions to be sure. It's case sensitive and 0P6BIMG.zip
Leading character is a zero.
Click to expand...
Click to collapse
Okay, I have hope. Thank You SO MUCH!!! Phone is on (upgrading currently), but IT'S ON:highfive: I think I accidentally used the s-off file instead of the s-on, and I did add the .zip onto that file (since it wasn't showing it w/ it, DUHHH). I will follow the rest of your instruction's very carefully later on, this will take a while, on app 80 out of 279 (bloatware, ugh!!) Hopefully, it goes more smoothly & I won't have to bother you again :fingers-crossed:
Thanks Again!
P.S. Will be contributing ASAP once I get this mess cleaned up. I really do appreciate all of your hard work & the magic that you make happen!!

M-FayeHTC said:
Okay, I have hope. Thank You SO MUCH!!! Phone is on (upgrading currently), but IT'S ON:highfive: I think I accidentally used the s-off file instead of the s-on, and I did add the .zip onto that file (since it wasn't showing it w/ it, DUHHH). I will follow the rest of your instruction's very carefully later on, this will take a while, on app 80 out of 279 (bloatware, ugh!!) Hopefully, it goes more smoothly & I won't have to bother you again :fingers-crossed:
Thanks Again!
P.S. Will be contributing ASAP once I get this mess cleaned up. I really do appreciate all of your hard work & the magic that you make happen!!
Click to expand...
Click to collapse
Well if you used the s-off one that's fine too. You will be rooted already. Just need to flash the latest twrp image and you will be fine.