Database Info

[Q] Rooting, unlocking & updating madness

Having been a member on this forum for years I must admit it has been incredible the wealth of information I've gained from it. I've had all sorts of phones/pdas and I'ved used this site to help me get the most out of it and to help m "tame" the device and stop rubbish from the vendors being installed on there when I don't want it.
A couple of years ago I got an HTC Desire. Great phone although limited memory. I was happy with it. Didn't bother to root it or anything. I then got a Motorola Xoom. Didn't bother rooting that either. I got myself an HTC Sensation now. I decided one day that I was going to unlock/root the thing to see if I could do it.
Somehow, I think I managed it. I haven't really noticed a difference but then I haven't put a custom rom on it. On all my old Windows mobiles I always had a custom rom.
Now, going back to the Xoom. It's an original Xoom. I bought it in May 2011. It is running Android 3.2 after Motorola sent out an update. All is good.
However, I would like to have ICS on it. This is where my problems begin. I've tried following so many different how-to's on how to do this unyet none so far have worked. So, either I'm completely stupid or, the guides are not easy to follow or the process (that is always touted as easy) is not very easy.
So I am asking for help. Here is what I understand are the steps that I need to acheive.
1. I need to unlock the device
2. I need to install a recovery image
3. I need to install ICS
Questions: I *think* I have done 1. How do I check? After what I believe is a convoluted process, I have installed the Android SDK. I have the drivers for the device on the [Windows 7 64bit] PC and I can see it listed when I type adb devices.
Why do I need to unlock the device? What does the act of unlocking it do? When I followed this:
http://forum.xda-developers.com/showthread.php?t=1242241
I got to step 3. I typed in the first command:
adb reboot bootloader
After much faffing around I found out from another site I needed USB Debugging enabled. Nobody told me this. No, it isn't obvious that I need this.
The boot screen appeared and gave a message at the top and then I typed in:
fastboot oem unlock
I followed the instructions on the screen. I unlocked the device. It took a while. When it rebooted I found I had to set the device back up again as if it was the first time I'd used it. "Great!" I am thinking, I've lost everything. Thankfully I backed up what I wanted so I am not bothered. Slowly the apps appeared to come back after it synched with Google. I'm assuming stuff gets backed up somewhere.
I typed:
fastboot reboot
It rebooted.I typed:
adb reboot bootloader
It rebooted into the bootloader. Now here is where things started to go off track. I typed the next command:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
I get this:
unknown partition 'recovery-Tiamat-R4c-100611-1150-cwm.img'
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img'
So what now?
I cannot believe the process to unlock and flash a rom is so unbelievably convoluted. I've read dozens of walkthroughs, how-to's and forums and each one seems to be very similar unyet there is always something different on there to what I get on my screen or something doesn't happen quite the same way.
Here is what I am trying to acheive:
I have Android 3.2 on my Xoom and I would like it to be ICS.
We'll assume that I am completely stupid and need serious handholding to get to ICS. Is there anyone that can help with these seemingly simple steps?
One thing I keep reading is about the recovery image file. Is this related to Cyanogenmod? I am assuming as it is called a recovery image file it helps you get back when things go wrong.
Thanks and much love to the person that takes up the reigns and helps me out here.

Hi!
If you are rooted already that's pretty easy. But if not, try using LordAIOTool to root (yea it's mine and I think it's worth a try). After you are rooted flash a new recovery - download from development section - after, rename the recovery to recovery.img and then use the following commands on adb, fastboot and this recovery folder (simultaneously)
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Then after keep clicking the vol- after 2s of your tablet appears on Motorola logo. Then keep cycling until appears Android Recovery then press vol+
You are on recovery now, just select install zip from sdcard...
Good luck
Sent from my MZ601 using XDA Premium HD app

If you wanted your xoom rom'd, then you could try wesamothman's guide: http://forum.xda-developers.com/showthread.php?t=1717402 It is great for beginners and the experienced alike.
This is for the wifi only xoom MZ604. There is another guide by him i believe for the MZ602

Do I need to flash a new rom to get root on my MZ604? What is the easiest way to just root the stock 4.0.4 firmware? I have no desire for a different rom. I just want to root it.

Hey there.
If you don't want to flash a custom ROM and only want to root it, try this:
1) unlock your bootloader.
2) thru ADB, flash a recovery image.
3) thru Recovery, flash superuser flashable zip: http://www.4shared.com/zip/g3yzbrIa/...?cau2=403tNull

I ran the first couple of steps to unlocking. That is as far as I have got. As I said, I have tried so many of these walkthroughs and not one of them has all the steps. They all make an assumption somewhere along the line.
For example: xxlordxx replied with:
"If you are rooted already that's pretty easy".
I'm not, that is the problem.
Again:
1. adb reboot bootloader
2. fastboot flash recovery recovery.img <---- This didn't work and gave me the error I pointed out earlier and that is where it all stopped. Noone explains what to do when it goes wrong.
Anything passed this stage is irrelevant until I can sort out the problem above.
yosterwp, you mentioned wesamothmans guide. I will try that one as it looks a bit more "dummies guide-like" and it is for my exact device which is the MZ604 wifi only. I hadn't seen this one as it was only posted a couple of days ago
Just so I know, can someone anser these questions? I'm sure they're very simple but I don't know.
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
2. Is unlocking the same as setting s-off?
3. If not, what is the difference?
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
5. What is Cyanogenmod and do I need it or is this another custom rom?
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Thanks for everything so far. I will let you know how I get on with wesamothmans guide.

Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions

wesamothman said:
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
Click to expand...
Click to collapse
You did
Much love!

HTC One X AT&T complete step by step root unlock s-off and flash ROM

Make sure phone is on 4.1.1 or 4.1.2, if not, put phone in usb debugging mode and open the RUU file and run it.
RUU downloads
make sure it matches your baseband though
download Hasoon2000 all in one/AIO for HTC One X
put phone in usb debugging and plugged in to android home screen
use chopper, step 2 on the list of options to the left, and make sure you get cid 1111111
use AIO to get into bootloader
select unlock bootloader in AIO
phone will reboot to factory android, skip ahead to android home page
hit finish or ok on AIO message
after success, get into usb debug and android homescreen and use AIO to flash TWRP, then boot into recovery and flash install to wipe TWRP
after CMD screens finish, reboot to phone, then use AIO to reboot into recovery
in TWRP select reboot into phone and itll prompt to flash SU and finish install to root
one booted to android file supersu app in app section, finish download thru playstore
open supersu app again and finish updates thru twrp, it will reboot into recovery, install zip, and reboot again to android
device is still cid111111
put soffbin file in adb location of of sdk, the platform tools folder usually
use AIO to flash one x zip file and follow prompts
after closing final cmd screen after failed 92, use AIO to boot up device in step 5
complete s-off with phone screen unlocked, close the cmd's as prompted
boot into bootloader, check for s-off
if s-off, boot into recovery
while in recovery;
enable usb mode
transfer CM and gapps files to device (or whatever rom and gapps)
wipe cache and dalvik and system
factory wipe
installCM and gapps
reboot
I'm hoping someone has links to the soffbin and one x zip files because they didnt work in AIO if I remember, a friend sent them to me.
enjoy

While you meant well, there might be a couple of problems with this.
1) This method will only work on certain firmware versions. You didn't properly note those firmware versions, you only noted Android versions which is irrelevant. A phone can be on 4.1.x without having the correct firmware version to use this method.
2) Using an RUU is a great way to update your device to the latest firmware, but there are instances where this will brick phones. For example, SuperCID + s-on + RUU = brick. That hasn't been noted in your post at all.
3) There are already explicit guides to unlocking/rooting for each firmware version here in our device forum. Creating another "guide" without all of the correct information is dangerous. It can also cause confusion due to the fact that there are different methods for different firmware versions.
My advice to anyone reading this who wants to root their device is this: work out which firmware/hboot you have and find the method already listed on this forum. There is a link in my signature to a resource thread, you'll find everything you'll ever need there.
To the OP: I'm not trying to cut you down, I hope you understand my reasons for this post after reading the information above.
Sent from my Evita

timmaaa said:
To the OP: I'm not trying to cut you down, I hope you understand my reasons for this post after reading the information above.
Click to expand...
Click to collapse
It all looks like constructive criticism to me, so hopefully it will be taken as such the the OP.
I agree, this isn't any more helpful than what is already out there, and not nearly comprehensive enough. It also needs a lot of cleanup, such as numbered steps and proper capitalization and punctuation. Some people might think this is nitpicky. But if you care enought to write it up, than do it in a way that is easy to read.

In his defense, this forum is crazy-messy.
I was a longtime ThunderBolt user, and on that forum there were clear paths to do what you needed to do. I will note that the ThunderBolt had only one version, and was only on Verizon.
My wife has an AT&T HOX. Not XL. She's on JB and her phone is slow and the battery lasts about 6 hours with moderate use. Nothing has been done to her phone to unlock, root, or S-off. But her phone is in such bad shape I'm thinking about stepping in.
Not trying to sound like a jerk, but all I care about is how I would go about taking a stock AT&T HOX through the rooting and romming process. I don't have Linux. I don't have a HTC OneXL. I'm not Canadian (Not that there's anything wrong with that, eh?).
Is there a CONSOLIDATED guide that will take me from stock to flashaholic? This thread attempts to answer this, and I applaud the OP. Hopefully we can work on perfecting this gem...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

I don't think our forum is messy at all. There are different guides for a reason. Different firmware versions have different methods and therefore have separate threads. All you need to do is find out the firmware version the phone is on, and find the appropriate method. The concerns I raised are all valid and I stated them for a reason.
Sent from my Evita

Model ID incorrect! Update failed! Failed flashing rom.

By the title, you can assume the situation is not very pretty and this poor individual needs some help. You would be correct in your assessment. This was me yesterday, freaking out after the new OTA update crippled my device and made me fear the worst (bricking). As a new Rom developer/flasher, I certainly worry about bricking my device, but have luckily not…yet. I certainly won’t deny the amount of tinkering that I do with my phone and flashing custom Roms, which might have assisted in my near meltdown, however, I thought it may be a good idea to share this experience (issue + solution) with the rest of the community, to hopefully save someone long periods of stress and research.
Note: I am only assuming the OTA is what caused the problem, but this could be incorrect, feel free to correct me.
Key Factors:
Custom Recovery: TWRP
Custom Rom (at the time of meltdown): Google Play Edition
Device: Verizon HTC One m8
OTA update ran.
Decided I wanted to go back to something closer to Sense and noticed that the ViperOne rom was getting some awesome reviews.
Downloaded Rom
Attempted to go into Recovery, but was greeted by the following error message:
HBoot
Model ID incorrect
Update failed
Press power to reboot
Downloaded Flashify and was able to get into recovery.
I knew I would need to deal with this error eventually, but thought maybe flashing the new Rom would assist in that area.
Flashed ViperOne rom, flash failed.
I swiped to unlock and the phone rebooted…
Then the real fun began.
My phone would boot to HTC logo with the read development disclaimer at the bottom:
“This build is for development purposes only. Do not distribute outside of HTC without HTC’s written permission. Failure to comply may lead to legal action.”
I freaked out for a bit, researched a ton and finally began to put the bits and pieces together:
At this screen it is possible to reboot, but then you will just boot into Hboot error, so pretty pointless (from what I know, feel free to chime in If you know of a way to get into recovery/fastboot from here).
I downloaded the latest version of TWRP
While on the HTC One screen, I plugged my phone into the computer and entered: adb devices.
At first, the command yielded no results, but after about 3 minutes, the device was recognized, but offline.
After 4 minutes, the device was recognize and looked to be available.
I then issued the following command:
Adb reboot bootloader
Success! This booted me into the fastboot usb method, which gave me a huge glimpse of hope.
Next, I ran the command to reflash the custom recovery:
Fastboot flash recovery [insert recovery file name here].
I received a successful message flash, however, after a reboot, I experienced the same problem as before.
I attempted to boot into recovery from the menu UI, but the option was not available. The journey continues:
I attempted the steps outlined above and then flashed the TWRP recovery image to boot instead of as recovery:
Fastboot flash boot [insert recovery file name here].
reboot-bootloader
This time, I was able to select “Recovery”, and booted into TWRP.
I then installed the GPE Rom again.
After the GPE rom installed, I rebooted into TWRP and checked to see if my restores were available, and luckily enough they were still in the same place (phew!).
This little article will hopefully help someone, as all the information I found for this issue was scattered throughout the web and I was luckily able to piece it together for my specific issue.
Ultimately, typing the ADB and Fastboot by themselves and reading through the commands in the CMD prompt, helped me figure out the commands needed to be successful in my endevours.

This would have been deeply helpful for me a week and a half ago. I actually bricked my device during the process of S-Off and unlocking the bootloader, after which, my device wouldn't be recognized on my computer (I missed a step in the process). Luckily for me, Verizon gave me an exchange, even though the phone was rooted and the only screen that'd boot up was TWRP. Apparently since I was in the 14-day return window, rooting or unlocking your device doesn't disqualify you from doing an exchange.
The first ROM I flashed after getting the new device and unlocking it was the same Google Play Edition. I had some issues getting in to recovery. I reflashed TWRP and have been fine ever since. I'm thinking it may be a bug in that ROM that causes devices to lose discoverability or for recovery to fail.

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