Database Info

[GUIDE] How to fix "Failed image LNX 0x0002 / RSD mode 2

I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!

mowassasin said:
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
Click to expand...
Click to collapse
So I went and bought the factory cable from the Black Hat guys, and luckily haven't had the need to use it. Any advice you'd like to give in case I need to at some point?

I guess the only advice I can give is: don't re-lock the boot loader when you have a custom rom loaded

You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It wouldn't recognise any fastboot commands nor the RSD Lite program for me.
But if it does, then thats good.
Merely a heads up for those who were in the same situation I was

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.

yaturner said:
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
Click to expand...
Click to collapse
Over the course of a few hours I was able to fix this, so I am going to write this little walkthrough for you using a rom from bwcorvus's page (CLICK HERE) and then used the guide from dirtymindedx -(CLICK HERE)
The reason it took me this long (as well as doing other things) was because I used the wrong set up to unroot my tablet. I was using the Unofficial images that are on bwcorvus's link. Because I didn't read thoroughly enough in his breakdown, I made myself look like a fool...
What you want is NOT
UNOFFICIAL STOCK IMAGES
Click to expand...
Click to collapse
because you will not be able to lock the bootloader (IF you want it to be that way, which I did, and so it gave me a 0x000004 Error, and yes i see that you are having a 0x000002 but somewhere i read this could help that.) I just wanted to get rid of Clockwork Recovery Manager cause it was not working on my 3.2 rooted tablet, and thought that because i messed up teh whole image with playing around and upgrading and seeing how i could break the image without overclocking, i thought i should actually try and make it back to stock too. With this... I needed to do these steps...
1. Upgrade the Motorola drivers while the XOOM was plugged in, so then I would be able to use the Fastboot Correctly.
2. Download the correct roms for my tablet, (Wi-Fi is mine, just grab the one that fits your version and just follow along.)
3. Upgrade my ADB from google because for soem odd reason my fastboot did not like the xoom till i did that...
4. Used the STOCK CABLE. I can Confirm that the STOCK CABLE that allows you to recharge the phones, WILL WORK for this...
5. Once the ADB was set up, I restarted it, aka Hit the red X and then loaded it back up and then closed it again, just to make sure the services were updated somewhat...
6. Opened Command prompt and navigated to the folder that help the zipfile for the fastboot flashing guide (aka dirtymindedx's guide at the top), be using CD (Drive Letter):/location/of/the/folder/that/is/unzipped
7. I then checked over the information in the folder by using dir /a and then proceeded to read through the guide
7-1. A note here... I did the fastboot erase userdata instead, because I wanted to see if it would brick it again... (sorry, I was in a fowl mood with the world last night so I was waiting for it to get bricked so i had a reason to use it as an ice scraper on my car... (not like i would really do it... just wanted a reason for justification haha)
8. ???
9. Profit
This is only to get rid of a "already slightly bricked" device... which I had done after relocking the Rom that was not official to Motorola and now, after a few updates, i now have Android 4.0.3 for the Xoom that was OTA'ed, looking to see how easy it will be to root to reload my rpg game saves that i got caught up in (hence my disappearance from the forums haha...) but I hopefully helped you out in a direction to heads towards... and as long as you don't lock the boot-loader (which someone posted about it before i did...) you should be fine with any changes to the rom after the updates... Also, you can skip steps on this too... you can just flash the image and not the recovery menu and so forth, allowing you to keep other settings that are not part associated to the rom image.
Also sorry for the insanity in my words... I have been up for a good 36 hours with a half hour nap somewhere in there...

Is my device bricked?

Hello, guys!
Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
So, the only approach for me to take seems to be installing CWM or ROM manager or anything else directly into my phone via my PC. Don't know how to do that, though. I can't access or do anything in my phone, so whatever needs to be done needs to be done via my PC, probably.
I'm using an Alcatel One Touch 985.
Thanks in advance!
Note: Installing a fresh copy of the setup wizard would be the easiest fix of all, or even the stock Android ROM. Once I get my phone working in its basic form, everything else becomes much easier to do.

If your phone still boots in either recovery or download mode, then its not bricked
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM
Hope this helps

Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
Click to expand...
Click to collapse
what that is its most likely the rom you downloaded is for a different phone, are you sure it was your phone specificly? check model no. if not theres a option in CWM to uncheck signature verification and it will sorta force flash what you wanted to flash.
If your phone still boots in either recovery or download mode, then its not bricked
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM
Hope this helps
Click to expand...
Click to collapse
Read the Question before posting stupid Answers, this shows that you didnt even read it...

I can still enter recovery mode, yes.
This all happened while using the ROM the phone came with.
I've tried with what seems to be the only compatible ROM for my phone, and also with other 2.3 ROMs. The problem regarding the ROM issue seems to be that the phone's boot loader isn't unlocked.
I know CWM can fix the signature problem, but how do I get it into the phone in the first place? That's the real issue.
Edit: I've tried unblocking the boot loader with the help of a tutorial online, but I believe I'm missing a step. Ideally this fix should be attempted after I know for sure there's no way to simply install an apk directly into the phone through my PC.

Klowdz said:
I can still enter recovery mode, yes.
This all happened while using the ROM the phone came with.
I've tried with what seems to be the only compatible ROM for my phone, and also with other 2.3 ROMs. The problem regarding the ROM issue seems to be that the phone's boot loader isn't unlocked.
I know CWM can fix the signature problem, but how do I get it into the phone in the first place? That's the real issue.
Edit: I've tried unblocking the boot loader with the help of a tutorial online, but I believe I'm missing a step. Ideally this fix should be attempted after I know for sure there's no way to simply install an apk directly into the phone through my PC.
Click to expand...
Click to collapse
have you tired factory reseting it again? the setup wizard crash is really werid at a stock rom.

I have. Same result.
Perhaps I deleted some file needed for the wizard to function properly.
I don't mind flashing a new ROM into the phone, or do whatever else in order for it to work properly.

Klowdz said:
Hello, guys!
Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
So, the only approach for me to take seems to be installing CWM or ROM manager or anything else directly into my phone via my PC. Don't know how to do that, though. I can't access or do anything in my phone, so whatever needs to be done needs to be done via my PC, probably.
I'm using an Alcatel One Touch 985.
Thanks in advance!
Note: Installing a fresh copy of the setup wizard would be the easiest fix of all, or even the stock Android ROM. Once I get my phone working in its basic form, everything else becomes much easier to do.
Click to expand...
Click to collapse
Try installing the ROM again, doing the correct wipe. After installing the ROM give the fix permission option.

In what novel way should I do that? I've tried the regular way, as mentioned above, and nothing.

Klowdz said:
In what novel way should I do that? I've tried the regular way, as mentioned above, and nothing.
Click to expand...
Click to collapse
If phone boots, is rooted and setup wizard stops just remove setup wizard app via adb.
Code:
adb shell rm /system/app/<name-of-setup-wizard-app>.apk
Cheers,
AJ

How do I do that? I have the SDK and everything installed, but that's it.

Klowdz said:
How do I do that? I have the SDK and everything installed, but that's it.
Click to expand...
Click to collapse
Following steps are for Windows PC
U need to find a file called adb in the folder of SDK
I use an older version of SDK and it's in folder named 'platform-tools'
Open the folder which contains this file
Then u need to open command prompt window there
( Do that by holding shift while right clicking in the folder then select 'open command window here' option)
Then u can type the following code
in the window.
Abhinav2 said:
adb shell rm /system/app/<name of setup wizard>.apk
Click to expand...
Click to collapse
Sent from my GT-I9000

It says it's a read-only file system.

Maybe It only works if your phone is rooted
If u r rooted U can try adding su command before it
su adb shell rm /system/app/<name of setup wizard>.apk
.
Sent from my GT-I9000

"Su" isn't recognized, but I clearly have it since whenever I try to access adb shell it asks me for permission (not for this task, but for another).
Wouldn't it be simpler to just install the setup wizard again? The problem is where to find that .apk.

[Q] one+1 un-brickable? I think not...

OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!

jpilch said:
OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!
Click to expand...
Click to collapse
This honestly is very confusing. I had to read what you wrote a couple of times to try and comprehend what the problem is.
Have you tried using fastboot without any toolkit? I ask because you haven't mentioned it anywhere. Persist can be fixed by fastbooting back to pure stock, and Mike's fix on the OnePlus forums, and/or updating to 44S.
Can you tell us what errors you get when you try to reflash the same rom? What recovery are you running? Which rom were you trying to reflash?

I have to agree with @nicholaschum, your post is very vague and confusing in its present form, and I'm a pretty seasoned troubleshooter on XDA.
What's needed? Less emotion, less comic type speech, less sarcasm, more specifics and facts.
Transmitted via Bacon

1328
If I try to sideload, it says either signature failed or whole signature failed.
Anything i push does not get pushed and I have tried multiple drivers from the galaxy ones that come in the reflash.zip from the one plus tech support to the Google ones I am using now.
If I try to fastboot through toolkit it says failed, not unlocked can't flash/erase. If I fastboot through cmd it says error: closed. I do all my checks, and it shows up in fastboot and adb but won't let me send anything.
The phone boots up for about 15 in is before restarting, the only way to get files on are to drop them in explorer within these 15secs, to internal storage, which used to be my sdcard.
I have tried flashing/side loading multiple ROMs from miui, 44s, 33r all signed to caulkins and mahdi. Nothing has worked (and the aosp OTA).
I cannot unlock bootloader, cannot reset tamper, cannot load GUI for more than 15 secs, and cannot root (although kermal already says it is, I suspect su needs to be in place).
I have also tried fastboot -c boot recovery.IMG (and recovery recovery.IMG) but no luck still. Is there a PC version of the Mac toolbox that can reset tamper? At least then I could unlock bootloader and install twrp and flash.
Thanks for the help
Josh

Still sounds like a driver issue imo.
First uninstall ALL previous drivers you have tried from device manager.
Installing one driver after another often causes conflicts.
Then download the official Android SDK and install Google USB driver. Google for instructions if needed but everything is pretty much straight forward.
This driver has the biggest chance of success.
After that you're off to start fixing your phone using fastboot and adb.

OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys

jpilch said:
OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys
Click to expand...
Click to collapse
For the fastboot bit, I've seen this happen a lot. Many people used this to solve their issue: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!

HTC One M8 Verizon Bricked - How I fixed it

I had bricked my HTC One M8 while trying to root it and had a very difficult time restoring the OS. After trying numerous things to fix the phone I had almost went out and bought a new phone. Lucky for me the deposit was more than what I could afford for which reason I decided to continue searching for a way to restore the phone online. I've created this thread in an effort to help someone who is in the same position as I had been.
I learned that RUU files were available at HTC's website for all carriers except for Verizon. HTC's website advises that your phone can be restored via Verizon Repair which is accessible within HTC Sync Manager. This didn't work for me. I'd hit the repair button and received a message that there are no downloads available.
The easiest solution is to follow this link: droidviews.com/restore-verizon-htc-one-m8-to-stock-with-android-5-0-1-lollipop-ruufuu
There are two methods 1) involves the use of a RUU file. This method is a little more difficult. The problem I had with this method is that I'd copy the file to my phone using windows and then reboot into TWRP and the file wouldn't be visible. This is also more difficult because you have to flash your phone with an image for TWRP. I eventually figured this method out. I had to learn how to use the sideload command within TWRP. You also have to learn the fasboot command. The easy way to restore your phone is to use the FUU file as this only requires that you reboot into fastboot mode by pushing the power button while holding the volume button down after which you then click on fastboot. You should see a notification that says fastboot USB at which time you can run double click the FUU file. If the FUU program doesn't recognize your phone you may have to download and install adb and fastboot drivers.
After I restored my phone using the FUU utility I later learned of a number of other methods that would have worked as well. All the methods however require that you have TWRP installed and that you know how to use the adb Sideload dos command. There are many tutorials explaining how to use this command. If your phone is bricked and you can't get into the OS then you'll have to use the DOS command to flash the TWRP image file. There are a number of sites that have ROMS for the HTC M8. When you sideload the file the ROMS automatically self install.

HTCM8Kaber said:
I had bricked my HTC One M8 while trying to root it and had a very difficult time restoring the OS. After trying numerous things to fix the phone I had almost went out and bought a new phone. Lucky for me the deposit was more than what I could afford for which reason I decided to continue searching for a way to restore the phone online. I've created this thread in an effort to help someone who is in the same position as I had been.
I learned that RUU files were available at HTC's website for all carriers except for Verizon. HTC's website advises that your phone can be restored via Verizon Repair which is accessible within HTC Sync Manager. This didn't work for me. I'd hit the repair button and received a message that there are no downloads available.
The easiest solution is to follow this link: droidviews.com/restore-verizon-htc-one-m8-to-stock-with-android-5-0-1-lollipop-ruufuu
There are two methods 1) involves the use of a RUU file. This method is a little more difficult. The problem I had with this method is that I'd copy the file to my phone using windows and then reboot into TWRP and the file wouldn't be visible. This is also more difficult because you have to flash your phone with an image for TWRP. I eventually figured this method out. I had to learn how to use the sideload command within TWRP. You also have to learn the fasboot command. The easy way to restore your phone is to use the FUU file as this only requires that you reboot into fastboot mode by pushing the power button while holding the volume button down after which you then click on fastboot. You should see a notification that says fastboot USB at which time you can run double click the FUU file. If the FUU program doesn't recognize your phone you may have to download and install adb and fastboot drivers.
After I restored my phone using the FUU utility I later learned of a number of other methods that would have worked as well. All the methods however require that you have TWRP installed and that you know how to use the adb Sideload dos command. There are many tutorials explaining how to use this command. If your phone is bricked and you can't get into the OS then you'll have to use the DOS command to flash the TWRP image file. There are a number of sites that have ROMS for the HTC M8. When you sideload the file the ROMS automatically self install.
Click to expand...
Click to collapse
No offense here, as I'm glad your device is up and running, however the title needs to be fixed.
You weren't "bricked". You were in a simple bootloop of the OS...
You simply flashed an RUU and put the phone back to stock, basically. Next step would have been to set to S-ON and then you're back to 100% stock.
You could have flashed TWRP, put a ROM on the device and flashed that.
If your device never got wiped, and you had a nandroid on it, you coulda installed TWRP and restored your nandroid.
Point is, a brick is when your device will not boot up. It won't turn on, it will not show a charging light when plugged in, the thing is well.. a brick.
You had a simple boot loop, and the differences are a working device and a paperweight.
The tutorial you gave is not even anything about a brick, but "Restore VZW M8 to Stock Android 5.0.1 Lollipop" I'm sure there are already other threads like this, but you were prob looking for a "brick fix" thread, so it's important to understand the differences so that this can help someone else in the future, because this doesn't fix a brick, and someone coming across this may think you just saved them from a paperweight, and that isn't what's going on.
But again, glad you are back up and running.

HTCM8Kaber said:
I had bricked my HTC One M8 while trying to root it and had a very difficult time restoring the OS. After trying numerous things to fix the phone I had almost went out and bought a new phone. Lucky for me the deposit was more than what I could afford for which reason I decided to continue searching for a way to restore the phone online. I've created this thread in an effort to help someone who is in the same position as I had been.
I learned that RUU files were available at HTC's website for all carriers except for Verizon. HTC's website advises that your phone can be restored via Verizon Repair which is accessible within HTC Sync Manager. This didn't work for me. I'd hit the repair button and received a message that there are no downloads available.
The easiest solution is to follow this link: droidviews.com/restore-verizon-htc-one-m8-to-stock-with-android-5-0-1-lollipop-ruufuu
There are two methods 1) involves the use of a RUU file. This method is a little more difficult. The problem I had with this method is that I'd copy the file to my phone using windows and then reboot into TWRP and the file wouldn't be visible. This is also more difficult because you have to flash your phone with an image for TWRP. I eventually figured this method out. I had to learn how to use the sideload command within TWRP. You also have to learn the fasboot command. The easy way to restore your phone is to use the FUU file as this only requires that you reboot into fastboot mode by pushing the power button while holding the volume button down after which you then click on fastboot. You should see a notification that says fastboot USB at which time you can run double click the FUU file. If the FUU program doesn't recognize your phone you may have to download and install adb and fastboot drivers.
After I restored my phone using the FUU utility I later learned of a number of other methods that would have worked as well. All the methods however require that you have TWRP installed and that you know how to use the adb Sideload dos command. There are many tutorials explaining how to use this command. If your phone is bricked and you can't get into the OS then you'll have to use the DOS command to flash the TWRP image file. There are a number of sites that have ROMS for the HTC M8. When you sideload the file the ROMS automatically self install.
Click to expand...
Click to collapse
Have you not read a single one of my threads?
Seriously?
You went to a third party click bait site to read a how to on work I have posted here many many times (and actively support) and you then come back here to post about this new novel approach? That guy only reposted my stuff to make money. His screen shot clearly shows he needed to re-run the RUU as his /data partition failed to update. Giving any credence to idiots like this is both dangerous and stupid.
This takes things to a whole new level.
Sent from my HTC6545LVW using Tapatalk