Database Users

Anyone know how to downgrade roms?

I have the updates installed but the unlock and selection sounds don't work. They were for a bit but then stopped. I tried to rename the rom update.zip but the phone stated it was an older version and could not flash it. It then forced me to reboot, end of story.
I want to reboot back to OG rom and then apply the updates over it.
Can anyone help me out.

Do it with paulobrian's method.

~~Tito~~ said:
Do it with paulobrian's method.
Click to expand...
Click to collapse
Assuming he knows what that is. OP, were you doing the fastboot flash method using the command prompt on Windows?

~~Tito~~ said:
Do it with paulobrian's method.
Click to expand...
Click to collapse
Now if i only knew what this really meant.
* Download the 1.19 stock ROM from here
* Download fastboot from here
* Extract the fastboot zip to the same directory as the ROM
* Turn your G2 on with the action button held (fastboot mode) I've never heard of an action button
* Type 'fastboot-windows oem rebootRUU' (case sensitive, replace windows with mac or linux as required) No where does it give me the option to type anything in.
* Type 'fastboot-windows flash zip PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459
signed.zip'
* Let this finish, then type 'fastboot reboot' and apply the OTA
P

EfemaN said:
Assuming he knows what that is. OP, were you doing the fastboot flash method using the command prompt on Windows?
Click to expand...
Click to collapse
I used this method to revert back to stock cuz i deleted the goggles. But, the click sounds only worked for an hours then stopped.
-------------------------------------------------------
Download PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b _26.02.01.15_M2_release_149459_signed
(the link is somewere in this thread)
*then read name it to PC10IMG.zip
*Put it on the root of your sd card.
*Power down phone
*Power up phone holding Vol Down and Power button.
*Phone will boot into fastboot i believe and then it will look for PC10IMG
*It will ask to flash it you use the vol key and power buttons to do that.
*Once it done it will reboot the phone and all your data will be gone and your be back at factory setting.
Then just rename the ota to update.zip and flash via recovery.
*remover the PC10IMG.zip from root of sd card
* Get back into the fastboot on the phone (setups up there^)
*this time use the vol button to go down to recovery.
*Once at recovery hold vol up and hit the power button.
*then vol down to flash update.zip

ddgarcia05 said:
I have the updates installed but the unlock and selection sounds don't work. They were for a bit but then stopped. I tried to rename the rom update.zip but the phone stated it was an older version and could not flash it. It then forced me to reboot, end of story.
I want to reboot back to OG rom and then apply the updates over it.
Can anyone help me out.
Click to expand...
Click to collapse
First make sure you media vol is on and up. If its not then u wont be able to hear it. And second you can downgrade the phone. All andiords are downgrade block unless we have custom bootloader. And the steps poste above are mines I orignaly posted them so I know it wont work after u applyed the ota
Sent from my T-Mobile G2 using XDA App

You cannot downgrade using either of the fastboot methods (fastboot-windows or fastboot on your phone) listed above after you have applied the OTA. It checks the version and then tells you that the downgrade version is old.
So far, I have not seen a solution to downgrade.

cparekh said:
You cannot downgrade using either of the fastboot methods (fastboot-windows or fastboot on your phone) listed above after you have applied the OTA. It checks the version and then tells you that the downgrade version is old.
So far, I have not seen a solution to downgrade.
Click to expand...
Click to collapse
This is correct, verified live in IRC by people in #g2root

Just call tmob and tell them your hinge is loose! Exchange phone, don't apply OTA.

All the sounds stopped working on my phone a day ago, had to do a hard reboot to get them working again.
OTA was applied.

Well, I called tmobile and told them my issue. I also told them I had already tried to reset my phone in attempts to fix the sound issue to no avail. I've got a new or like new G2 on it's way.
I'm going to be kinda bummed if it's a like new (refurbished) model, but then again it can't be older than the one I got now.

How to flash a radio Nexus S

Call me a n00b, whatever. I am interested in testing a different radio on my Nexus S i9020a. I have recently noticed terrible download and upload speeds over 3G on my device since upgrading to Android 2.3.4.
My device is not rooted, and if this is a requirement to flash the new radio, then I will not do it. But my question is, can somebody guide me through the process step by step?

get fastboot (and adb while you're at it) working, then power of an boot into fastboot (or "adb reboot bootloader"), then:
"fastboot flash radio radio.img"
either "fastboot reboot" or just scroll down to reboot in the fastboot menu.

irishrally said:
get fastboot (and adb while you're at it) working, then power of an boot into fastboot (or "adb reboot bootloader"), then:
"fastboot flash radio radio.img"
either "fastboot reboot" or just scroll down to reboot in the fastboot menu.
Click to expand...
Click to collapse
This doesn't exactly help me because I don't know what any of that is...

http://forum.xda-developers.com/showthread.php?t=619153

irishrally said:
http://forum.xda-developers.com/showthread.php?t=619153
Click to expand...
Click to collapse
Hey, good to have you back here. Do you still have the ns or have you shifted?
Sent from my Nexus S using Tapatalk

You need to set up adb, you will also need to have Java jdk in order to set up adb. You will also need to have to have the correct drivers installed on your computer in order for it to communicate with your phone. IMO you might as well root your phone if your going to set up adb lol its the hardest part. Good luck. Btw Google is your friend, read read and read so you wont end up bricking your device.
Sent from my Sexy Nexy 4 GIZZLE!

deeren said:
Hey, good to have you back here. Do you still have the ns or have you shifted?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Hey, thanks man. My NS took a turn for the worst. I think I corrupted the memory as I could no longer write to the internal memory and the phone wouldn't get past the google splash screen. I spent a while thinking I could fix it (ODIN etc.) but finally gave up and sent it back to Samsung. They replaced the PBA (Printed Board Assembly), free of charge. I should be getting it back in the mail any day now. Can't wait, I've been stuck with my g1 for weeks now.

My 3g/mobile data is also guffed since the 2.3.4 upgrade and I'm going to revert the radio back.
I dunno if I'm being stupid but I can't seem to find any radio images anywhere...can someone point me to them please?
Thanks,

irishrally said:
http://forum.xda-developers.com/showthread.php?t=619153
Click to expand...
Click to collapse
Thank for the helpful link. And to reference "Google is my friend", I have searchec high and low for some kind of step by step guide on how to do this. Somebody want to point me in the direction of a guide or write up quickly here in this thread?

I just re-read your first post and I don't think you can flash a different radio if you are not rooted (could be wrong though). Honestly, flashing a radio has much higher risk than rooting your phone (but still low risk as long as you check the md5 on the radio image you download and you don't pull the battery during a radio flash).
If you choose to root, this is a good guide: http://forum.xda-developers.com/showthread.php?t=895545

irishrally said:
I just re-read your first post and I don't think you can flash a different radio if you are not rooted (could be wrong though). Honestly, flashing a radio has much higher risk than rooting your phone (but still low risk as long as you check the md5 on the radio image you download and you don't pull the battery during a radio flash).
If you choose to root, this is a good guide: http://forum.xda-developers.com/showthread.php?t=895545
Click to expand...
Click to collapse
I found a thread on Modaco where Paul posted radios.
http://android.modaco.com/content/google-nexus-s-nexuss-modaco-com/333482/01-mar-xxkb3-gri54-basedband-radio-only-updates/
Not tried it yet...

Deeko1 said:
I found a thread on Modaco where Paul posted radios.
http://android.modaco.com/content/google-nexus-s-nexuss-modaco-com/333482/01-mar-xxkb3-gri54-basedband-radio-only-updates/
Not tried it yet...
Click to expand...
Click to collapse
I have the radio image I want to apply I just need to have some sort of guide on howvto apply. All this talk of fastboot and adb is in reference it seems to the Android SDK. I have the SDK installed and what not. But where do I go from there. Is there a way to root with stock recovery? Or just applyt the radio image without rooting in recovery mode with unlocking bootloader?

EvilSpants said:
I have the radio image I want to apply I just need to have some sort of guide on howvto apply. All this talk of fastboot and adb is in reference it seems to the Android SDK. I have the SDK installed and what not. But where do I go from there. Is there a way to root with stock recovery? Or just applyt the radio image without rooting in recovery mode with unlocking bootloader?
Click to expand...
Click to collapse
Fastboot or Clockwork Recovery is mandatory.
If you want to use stock + a radio. You can try renaming the .zip to update.zip and applying update.zip from stock Recovery but I'm not 100% sure if that would work.
best bet is to use fastboot or clockwork recovery.

Btw if you flash clockwork only once than it will not stick, than you can flash a new radio while still having stock recovery if that's you're jive.
Sent from my Sexy Nexy 4 GIZZLE!

Deeko1 said:
My 3g/mobile data is also guffed since the 2.3.4 upgrade and I'm going to revert the radio back.
I dunno if I'm being stupid but I can't seem to find any radio images anywhere...can someone point me to them please?
Thanks,
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/showthread.php?p=14564429#post14564429

[Q] another noob with a rooting issue

sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
ok so i used this: themikmik dot com/showthread.php?11114-GUIDE-WIP-How-to-achieve-S-OFF-after-unlocking-2-18-HBOOT-with-HTCDev-com-No-More-Watermark
after using the HTCDEV to unlock.
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
i am stuck in between step 10 and 11.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
i downloaded su, root checker,and busy box. root checker says the phone is rooted. i know i need to get the h boot to a lower level inorder to do the unrevoked3 program.
tried flashing the recovery and says "cant open /sdcard/pc36img.zip (bad)"
made sure it wasn't zip.zip and it was so i fixed that and still wouldn't work.
the only thing i am not sure of is step 10 and wether i did it right :Once the misc partition has been updated, you can downgrade your Bootloader and HBOOT to a non-watermarked version rootable with unrevoked.
does the partition auto update or do i need to do something to make it update? i didn't see any option for this. eveything up to this point went exacty liek it should have so now i am lost. i have searched numerous forums and found similar problems but none that were exactly the same. and none of the solutions worked for me. i tried all the basics rebooting, etc and nothing. any info would be greatly appriciated.
the only other thing that i may have done wrong that i can tell is what file i am trying to make the pc36img. at the bottom of post # 1 it has 2 attachments listed as pc36img files those are the ones i am trying to use. when i try to click the hyperlinks thru the rest of the post i get an error message from that site thats says " This account's public links are generating too much traffic and have been temporarily disabled! " so i dont know if that site has the same zip files or i am completely using the wrong zip file.
sorry for the long winded post i know the noob video says make it brief but i figured the more info the better.
thank you.

sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
Click to expand...
Click to collapse
Oh brother was it!
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
Click to expand...
Click to collapse
Your S-On,so your not rooted.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
Click to expand...
Click to collapse
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.

Diablo67 said:
Oh brother was it!
Your S-On,so your not rooted.
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.
Click to expand...
Click to collapse
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App

when i check with root checker it says i am rooted and have su. maybe it just means unlocked? busy box also says rooted?
pc36img is in all caps.
thanks for the quick response!

evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible

evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible
Click to expand...
Click to collapse
Ok,thanks for clearing that up,serious dudes i hate giving the wrong info when trying to help someone and i don't mind admitting when i'm wrong,lol.Your never to smart or old to learn something new.
Sent from my Dell computer.

I can probably help here.
If all you want is to be rooted, then you are. There's no reason to do the rest, especially if you're out of warranty. Since you already have a custom recovery installed, you can feel free to flash a custom ROM, and not even worry about the rest of the process.
The Dropbox links thing should be fixed now. I had to move them all to 4shared.
As far as the misc partition flashing, as long as you didn't get any errors when in the command prompt/adb shell, then I'm sure it flashed successfully. The only way to tell is if the Froyo PC36IMG.zip flashes successfully without a "main version fail."
I can assure you the PC36IMG works, as I've used it many times myself. Did you confirm the md5? Is it possible your SD card got corrupted somehow? Those are the only reasons it wouldn't pick it up.

thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?

98tib said:
thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?
Click to expand...
Click to collapse
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .

Captain_Throwback said:
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .
Click to expand...
Click to collapse
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.

98tib said:
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.
Click to expand...
Click to collapse
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.

This is what's cool about this forum a noob asking a question and you get 4 big time contributors helping out!
Sent from my PC36100 using xda premium

Captain_Throwback said:
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.
Click to expand...
Click to collapse
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem

98tib said:
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem
Click to expand...
Click to collapse
What kind of sd card are you using? You might want to try a different card, or reformat the stock card, if that's what you're using. That's the only other reason it wouldn't pick up the file, provided it's named correctly. And I assume you verified the md5 and it's good? And you're certain the file is on the root of the sd card as well? I cant think of anything else that could be causing the problem. Let me make sure my bootloader reads the file just to make sure.
EDIT: Scratch everything I said above. If your phone still says "unlocked" at the top of the bootloader, the misc partition wasn't updated successfully. Did you already complete that part, with no errors? You need to reconnect the device while booted up, with USB Debugging enabled, and run those commands from the command prompt from the folder with adb in it. Make sure you have the files "flash_image" (extracted from zip file) and "mtd-eng.img" (extracted from zip file) on the root of your sd card. If you're using Windows 7, run Command Prompt as an administrator. Let me know the output of those commands before continuing. If you got any errors on that part, that would be why you can't flash the Froyo ROM.
I saw you mentioned that in your OP, but I guess I didn't realize you skipped that part. That'a really the most important part of the process. It's the part right before the sentence you mention about the misc partition being downgraded. That last command flashes the mtd-eng.img file to the misc partition.

both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.

98tib said:
both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.
Click to expand...
Click to collapse
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".

Captain_Throwback said:
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".
Click to expand...
Click to collapse
thank you, you are my savior! its always the dumb things that you think you did right that you did wrong! lol. thank you again!

now i'm off to screw something else up!

[GUIDE] Everything Explained.

Before you go ahead and start unlocking, flashing and rooting, there are things you should know. This thread is a general guide that will serve to explain most of those things.​
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.​
Table of Contents
A. The layers (Hardware, Firmware, Software)
B. Definitions
C. Troubleshooting Common Issues
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.​
The Layers. How does everything come together?
Just like any other computing device there are 3 Layers to your phone. It helps to realize this prior to modifying your phone, so you are able to troubleshoot issues more effectively.
Layer 1 Hardware: The hardware layer is the physical components of your phone. That which you can touch, hold and see. This layer is the least likely to be modified unless you are a crazy super master level modder. Very few bother to mess with this layer so this layer tends to be the most stable with very little issues arising. The best way to make sure a problem is not related to the hardware layer, that is to say, a physical hardware problem where a physical component needs replacing, is to return all software and firmware to stock. This is typically done by running an RUU or manually reflashing stock firmware and software. There are instances where software or firmware modifications can affect the hardware. For example, if you overclock your CPU, the added heat could permanently damage the CPU and even other hardware components so be sure to take that into consideration.
Layer 2 Firmware: This layer is what allows the software to control the hardware in your phone, like a bridge between the two. There is firmware for just about every component of your phone, the camera, screen, radio, processor etc etc. This is the second least likely layer to be modified. S-Off is required to modify most, but not all, firmware files and rightfully so. Modifying firmware components can easily damage your phone if you do not understand what you're doing. In some cases a JTAGG repair can fix your phone from firmware modification damage, other times, only replacing physical components can repair the damage done. (Recovery and the kernel are technically part of the firmware layer but do not require S-Off to flash)
Layer 3 Software: The software layer consists of the "ROM" and applications on your phone. This is where most of the modification takes place and while modifying the software layer is the least likely to cause serious issues, it can still be dangerous. Flashing a ROM not intended for your device could easily put your phone into a bricked state. With SuperUser or Root access, software is capable of modifying the firmware layer of your device. It is up to you to decide what is safe and what's not safe. This is why rooting is not for everyone. How can you properly decide what is safe for your device without the proper knowledge?
Definitions
What is root?
Root, super user or su for short is a level of access giving you permission to read or write to folders, or partitions you could not have access to as a regular user. Think administrative access.
Consider a folder path “/sdcard/downloads/” If we break it down, “downloads” is a folder in “sdcard” and “sdcard” is one of the folders in “/” which is the “root” of the folder structure. As a regular user, one might not consider that folders other than sdcard exist in “/” as they are kind of hidden from us but rest assure they are there and this is typically where the android OS and firmware files are kept. Modifying these files can be extremely dangerous for your phone if you do not understand the modifications to the file you're making, and what steps you can take to recover from any issues you encounter.
What is an RUU?
RUU stands for ROM Update Utility. An RUU is used to reflash an existing firmware/software set or updated firmware/software set. An RUU will wipe everything and basically get your phone back to stock. Unless your phone is S-Off, you cannot run an RUU with an older firmware or software than those currently on your device. You can only run an RUU that matches your MID/CID unless you are S-Off and have SuperCID or have changed the MID/CID to match the carrier you are flashing. There may be differences in hardware/firmware between MIDs and CIDs so be mindful as this can lead to a brick. To properly run an RUU with S-On, you must also have stock recovery installed, the bootloader must be locked/relocked. BE VERY CAREFUL DOING THIS. It is not recommended to RUU or OTA after unlocking your bootloader unless you have to. If you are S-OFF you can RUU whether the bootloader is locked or not and if you are superCID, CID checks will be ignored so be sure to be mindful of the RUU you are running and that it will play nice with your phone.
What is an OTA?
OTA stands for Over The Air and implies an Over the air update distributed by your phone manufacturer, carrier or ROM developer. Unlike an RUU, an OTA will not typically wipe/factory reset your phone but can update your firmware and/or software set. To a apply a manufacturer/carrier released OTA you will need stock recovery and stock system apps installed. Your CID/MID must match that of the carrier/manufacturer your phone came from.
What is a ROM?
When the term ROM was first introduced it stood for Read Only Memory, however, most memory that claims to be Read Only nowadays is not like it was back then. Now a days it is not as complicated to write ROM as only permissions are in your way as opposed to the days when you were required to modify the hardware layer in some way to update the ROM chip. In this particular case, we are referring to the android software on your phone. Stock ROM would imply the manufacturer released ROM that came on your device when you purchased it. Custom ROMs are ROMs the are modified stock ROMs or ROMs built from android source code to. I think you get the idea. It's the device software or Operating System if you will. You should never flash a ROM that is not intended for the device you are flashing it to, this is very dangerous. Like, brick dangerous.
What is a nandroid backup?
A nandroid backup is a backup of your phone's current state. Like a snapshot or image of your phone's software. It includes the ROM currently flashed to your phone, the kernel, apps and settings. It does not include any firmware files other than the kernel and possibly the recovery. A nandroid is done with custom recovery and cannot be done with stock recovery. Taking a nandroid before you start messing with your phone is good practice. In fact, It's good practice to make nandroids before flashing a new ROM, or making any changes that may impact stability. This will ensure you always have a quick way to get back to having a usable phone. Obviously, a nandroid will not help in cases where you mess up firmware files like the radio firmware or hboot.
What is a kernel?
The kernel is the central point of an operating system. It contains the modules and settings necessary for the ROM or OS to work properly. Every Operating System has a kernel, including android. Just like ROMs there are custom kernels, with tweaks and the like that may improve or decrease performance/stability. Also, like ROMs, you should never flash a kernel not intended for your device. Very Dangerous!
What is a bootloader?
The bootloader is as the name implies, a device software/interface for handling boot operations it is contained within the hboot file. The bootloader screen has a few nifty features:
Gives you device information such as:
The bootloader state (locked, relocked or unlocked)
The Secureflag state (S-On or S-Off)
Your hboot and radio versions
Your Cid (only if you changed it)
Allows you to power down, reboot or boot your phone to android.
Allows you to factory reset your phone (Though should never really be used unless you are completely stock as you can properly factory reset in custom recovery)
Allows you access to the recovery
It gives you access to fastboot command operations you can send from your PC to your phone.
To boot to bootloader: Press and hold Power and volume up until the phone shuts off, then let go of power and volume up. Press and hold Volume down until your screen comes up in bootloader mode.
What is recovery?
Recovery is a software/User Interface that allows you to handle and make changes to your device, without having to boot the android OS. The stock M8 comes with a recovery that is quite limited but allows you to factory reset your phone and flash OTA updates which really is more than enough for the average user.
Those of us who want more from our phones, and modify them tend to flash custom recoveries with many extra features. I won't go into all the features they provide as the devs have websites, and you can visit them for more information. The two custom recoveries for the m8 include TWRP and Philz Touch. Both are very functional and choosing one is a matter of preference over anything else.
To flash a recovery image. Put the recovery image in your fastboot/adb folder and in the command prompt:
Code:
fastboot flash recovery recoveryfilename.img
You can find The latest:
TWRP for the M8 HERE
Philz Touch for the M8 HERE
To manually boot to recovery, boot to bootloader (Press and hold Power and volume up until the phone shuts off, then let go of power and volume up. Press and hold Volume down until your screen comes up in bootloader mode). Then select recovery in the bootloader menu.
What is S-Off/S-On?
This stands for Securewrite-on or Securewrite-Off. The name kind of gives some hints as to what it means. Having your bootloader unlocked, affords you the ability to to flash a custom recovery and custom roms as well as a custom kernel however, some people may need more. They may want to alter other system partitions. That is where S-Off comes in. It gives you full write access to all system partitons. It also forces a bypass for all security checks, such as those made by OTAs and RUUs, for CID and MID. S-Off is persistent. No matter if you RUU, OTA, Flash a ROM, Firmware, Factory Reset, S-Off will remain so until you use fastboot to reset the flag. I should say, if you don't know what you're doing, that is to say, if you are the type to follow instructions blindly on a thread, without much idea what is ACTUALLY Happening, what files you're modifying, you should not have S-Off. It should not concern you and that is that. S-Off can be dangerous. You have been warned.
What does a Factory Reset do?
A Factory Reset Clears the Cache, Dalvik Cache and Data Partitions. All settings will reset to default. User Apps (Apps you installed that did not com preinstalled with the ROM) will be removed. This will not restore your phone to when you purchased it. This will not relock your bootloader, Reset the S-Off flag, remove root, or downgrade your hboot. It merely affects the system and user settings and user apps.
What is fastboot?
Fastboot is a command line tool that allows you to manipulate certain parts of your phone from the bootloader. Your phone must be in fastboot mode and you must have the fastboot application and HTC drivers installed if you are on Windows. If you are on linux, the HTC driver is preinstalled.
Popular fastboot commands include:
Fatsboot devices (Lists devices connected for use with fastboot)
Fastboot flash recovery recovery.img (Flashes a recovery image)
Fastboot flash boot boot.img (Flashes a boot image)
Fastboot oem readcid (Shows the CID of the phone installed)
Fastboot oem writecid (Writes a new CID to your phone. Must be 8 Characters. Requires S-Off)
Fastboot oem rebootRUU (Puts the phone in RUU mode which is used for flashing firmwares and/or entire RUUs)
Fastboot reboot (Reboots your phone)
Fastboot reboot-bootloader (Reboots to bootloader)
Fastboot erase cache (Wipes the cache partition using fastboot. Good idea after flashing things via fastboot)
Fastboot help (Will list fastboot commands)
Fastboot boot imagefilename.img (Allows you to boot a recovery image or kernel image without actually flashing to your phone
allowing you one time access to the features without the headache of reflashing stock afterwards) Thanks to @garyd9 for suggesting I include this. Very convenient command.
What is ADB?
ADB is another command line tool used to manipulate your phone. The commands for ADB are way more extensive. ADB can only communicate with your phone while in a custom recovery or while the ROM is booted up with USB debugging turned on. The reason ADB is so much more extensive is because it allows you to remotely access your phone's terminal just like a linux terminal. You can use ADB to push or pull files to and from any partition (Some partitions will require S-Off), list devices, get a logcat, troubleshoot issues etc etc. For an extensive list of commands and how to use ADB I strongly suggest visiting http://developer.android.com/tools/help/adb.html
What is the CID?
CID stands for carrier ID. It's a string of letters and numbers, eight characters long that identify what carrier your phone is from. When you flash an OTA or RUU, The OTA or RUU checks for a few things, one of those things is the CID, to ensure you are flashing software intended for your device. Realistically, There's no hardware difference between the M8s (with the exception of CDMA vs GSM) so all firmwares/softwares should be compatible. With regards to radio firmware, your radio may function better with one firmware over another. There have been occasions with HTC where flashing an RUU or OTA with the wrong CID or SuperCID, while S-On would brick your phone. So try to be mindful of this and be careful.
Thanks to @garyd9 for suggesting I include this in my guide!
Some common CIDs include but are not limited to:
SuperCID: 11111111
HTC International: HTC__001
AT&T: CWS__001
ROGERS: ROGER001
VODAPHONE: VODAP001
T MOBILE: T-MOB010
TELESTRA: TELST001
Bell Canada: BM___001
What is a brick?
The term brick is sometimes thrown around a bit too casually. A brick is when your phone is no longer operable. It does not boot, there is no way to save it without resorting to Jtagg or replacing the nand chip or motherboard. If your phone powers on and something appears on your screen, your phone can almost always be saved. Be sure you know how to save your device before messing with your device.
Troubleshooting Common Issues
I flashed a ROM or Kernel and it's not booting! WHAT DO I DO!?
When this happens. There are actually a number of things to consider but first off, Hopefully you made a nandroid to restore from just in case the reason it doesn't boot is something not quickly or easily fixed.
1. Is the ROM you're flashing indeed intended for your device? ROMs you're flashing should be for the HTC One m8 International. You should not be flashing ROMs designed for the m8 Sprint or Verizon and should not be flashing ROMs designed for other models of phone. If the ROM you flashed is not for your device, best case scenario, it's not flashing properly. Worst case scenario, you have a brick. You will need to factory reset and wipe system then either flash a new ROM or restore a nandroid to get your phone up and running again.
2. Did you wipe Cache, Dalvik Cache, Data and System? (Don't wipe System for Kernel Install)
A factory reset will wipe all but system. You should wipe System manually in case the script for the ROM install does not do it or does it improperly. A factory reset is enough for a Kernel install. If you wiped system and just flashed a kernel, it's no doubt your phone is not booting.
* If you did not factory reset and wipe system, do so and then reflash your rom. It should then boot.
* If you wiped system to flash a kernel, you will need to reflash the rom, and then reflash your kernel again if you are flashing a custom kernel. (Note a GPE Kernel will not work on Sense and a Sense kernel will not work on GPE.
3. Did you matchup the Checksum? MD5 or SHA1 are usually posted on the ROM Download site/post. This allows you to check and make sure the integrity of the file you downloaded has been maintained. If The SHA1 or MD5 of the file you downloaded does not match what is posted, you have a corrupted file and should redownload. If you don't have a MD5 or SHA1 Checker, I suggest downloading one. Google MD5 or SHA1 Checker and you should find one. MD5 is most commonly used but it's up to the Dev as to which they post. Sometimes both. You only need to match one. (Linux comes with utilities for checking MD5/SHA1 called md5sum and/or sha1sum)
4. If you tried all these steps and it's still not booting, try another ROM. If no ROMs appear to be booting, you may be having an issue with your custom recovery. Redownload your recovery (Make sure it's the right one for your phone and check the checksum) Then reflash recovery, then use fastboot erase cache, boot to recovery and try flashing again.
5. If you tried all these and you're having issues, ask in the M8 Q&A!
I wiped everything and I don't have a ROM on my phone to flash! What do I do?
This is quite simple really.
Boot to recovery
Connect your phone to your PC
Make sure your ROM is on your PC and in your adb folder
Then use:
Code:
adb push romfilename.zip /sdcard/
Be patient, this could take a while, when it finishes you will get a confirmation with bytes in/bytes out.
Then flash.
Where can I go to find links to do all this cool stuff I want to do to my Phone!?!?!?!?
HERE!
Thank Yous!
Thanks to @garyd9
Thanks to @keithross39
This is a work in progress. I will be updating this as often as I can, trying to explain as much as I can for newer M8 owners who are not used to HTC or Android devices. If you have any suggestions for what I can put here, post here and let me know! Also, I'm not perfect, I make mistakes if I have/do make any, do not be shy! Let me know.
[08/18/2014] Partially updated and fixed spelling mistakes. More coming soon!

Hey fella, this is a good idea.
Thanks for taking the time to do this.
I am going to be getting the M8 in the near future, so reading up about the HTC specific stuff is really useful for me as I'm currently familiar with Samsung procedures and not a lot else. Most folks reading this should be familiar with the 'cross platform basics', so what you've covered so far should be enough........
But.....
Those (like me) who are getting an HTC device for the first time would probably benefit from more of a detailed description of the HTC side of things......maybe you could concentrate on expanding that information.......
Maybe you could include links to threads for s-off, rooting and/or anything else relevant?
Just my 2 cents worth....for what it's worth.....
Sent from my rooted debloated thingy

keithross39 said:
Hey fella, this is a good idea.
Thanks for taking the time to do this.
I am going to be getting the M8 in the near future, so reading up about the HTC specific stuff is really useful for me as I'm currently familiar with Samsung procedures and not a lot else. Most folks reading this should be familiar with the 'cross platform basics', so what you've covered so far should be enough........
But.....
Those (like me) who are getting an HTC device for the first time would probably benefit from more of a detailed description of the HTC side of things......maybe you could concentrate on expanding that information.......
Maybe you could include links to threads for s-off, rooting and/or anything else relevant?
Just my 2 cents worth....for what it's worth.....
Sent from my rooted debloated thingy
Click to expand...
Click to collapse
Thanks man! I welcome all suggestions! I will do my best to incorporate your suggestions
Sent from my HTC One_M8 using XDA Free mobile app

Great idea, thanks. I've been wondering what S-Off is for weeks but didn't want the flaming for asking a noob question!
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Some possible additions:
What is "RUU"?
What is MID (model ID) along with a list of some common MID's
What is CID (carrier ID?) along with a list of some common CID's
How do the MID and CID relate to each other and how does the combination relate and/or interact with RUU. Related, of course, is the third part of the version number.

I was thinking of writing a guide myself, because I was so confused myself after coming from samsung, really nice.

Shebee said:
I was thinking of writing a guide myself, because I was so confused myself after coming from samsung, really nice.
Click to expand...
Click to collapse
Lol...ain't that the truth....
Sent from my rooted debloated thingy

Nice one

Very well done!
Sent from my HTC One_M8 using Tapatalk

I'm one of those who also came from Samsung (S4).
This is really great and easy to understand. This should be sticky :victory:

While I think the OP uses the term "ROM" incorrectly (Read Only Memory), I'll admit that's just me being picky. Otherwise, a very useful post... I've requested it be made sticky.
Take care
Gary

garyd9 said:
While I think the OP uses the term "ROM" incorrectly (Read Only Memory), I'll admit that's just me being picky. Otherwise, a very useful post... I've requested it be made sticky.
Take care
Gary
Click to expand...
Click to collapse
That's not being picky at all! Feel free to suggest any corrections. I welcome criticism and corrections.
Thanks for the recommendation!
Sent from my HTC One_M8 using XDA Free mobile app

exad said:
That's not being picky at all! Feel free to suggest any corrections. I welcome criticism and corrections.
Click to expand...
Click to collapse
LOL. I'm one of those people who goes nuts when people want to install "ROM's" on their phone. I keep reminding them that if it was really "Read Only Memory", that they wouldn't be able to overwrite it. Ever.
I do understand, however, that it's one of the misused terms these days. I guess it's kind of like saying you are "dialing a phone number." (There aren't any dials on our phones anymore. I haven't even seen a working rotary dial phone in years...)
Anyway - I'll stop with my OT bantering. Once I get more familiar with HTC devices I'll probably have some good suggestions for your posts.
Take care
Gary

garyd9 said:
LOL. I'm one of those people who goes nuts when people want to install "ROM's" on their phone. I keep reminding them that if it was really "Read Only Memory", that they wouldn't be able to overwrite it. Ever.
I do understand, however, that it's one of the misused terms these days. I guess it's kind of like saying you are "dialing a phone number." (There aren't any dials on our phones anymore. I haven't even seen a working rotary dial phone in years...)
Anyway - I'll stop with my OT bantering. Once I get more familiar with HTC devices I'll probably have some good suggestions for your posts.
Take care
Gary
Click to expand...
Click to collapse
Read only memory isn't a great name for it. If you've ever updated the bios on a pc, flashed a firmware update to a router, etc... you've written to read only memory. There are types that are truly read only but I can't think of a single practical example. And welcome to htc phones!
Sent from my HTC One_M8 using Tapatalk

lampel said:
Read only memory isn't a great name for it. If you've ever updated the bios on a pc, flashed a firmware update to a router, etc... you've written to read only memory. There are types that are truly read only but I can't think of a single practical example. And welcome to htc phones!
Click to expand...
Click to collapse
I'm old enough to remember (clearly) when you couldn't update the BIOS on a PC - you had to physically replace the BIOS chip. (Usually, they were socketed to make replacement a bit easier.) That was ROM. Also, early game consoles used true ROM in cartridges.
As for current practical example: a simple CDROM (not CD/RW) is, of course, read only.

I agree that it's not the best name lol but that is what it stands for....
Sent from my HTC One_M8 using XDA Free mobile app

Added this to my index thread

Hi guys! I am planning to buy an htc one m8 but can someone please tell me the different models out there? I don't want to end up buying the wrong one. Also is the dev one worth spending the extra money over the international? And is it the same model as the international one? Thanks in advance. I didn't know where else to post this. I didn't wanted to start a new thread.

Karan and all other users, please post questions in Q&A. Only things that should be posted here are suggested additions to this thread.
Also thread has been updated and more to come!

Part on RUUs is wrong...
An RUU can be run at any point and in any state (so long as you can get to the bootloader) as it completely replaces the entire system so doesn't matter if you don't have the stock recovery as it replaces it during the update process. Also, if you're S-OFF it means you can flash any RUU for any phone, handy to go between branded and unbranded software. OK, there's a risk of trying to flash an RUU from another device but if you do that you're a bit dumb!!

FIX HTC-U11☆corrupt☆relocked☆s-on☆

______________________________________________
REPAIR HTC U11 - CORRUPT - RELOCKED - S_ON
______________________________________________
I run a phone repair shop,
Customer brought a HTC U11 in to repair,
was soft bricked with an attempted custom rom installation then relocked the bootloader without flashing a working OS to it,
The os version was there but when the device booted a message appeared the device is corrupt cannot be trusted and will not boot,
this tutorial is how I managed to revive the dead device please read below.
Device specs on this model were :
______________________________________________
Fastboot oem readmid
2PZC10000
Fastboot oem readcid
htc_039
______________________________________________
hTc download mode
***relocked***
***production***
htc_ocnuhl PVT S-ON
LK-1.0.0.0000
Radio-8998-002772TOV-1712061121
OpenDSP-V11.6.00347.CB8998_0711
OS-2.33.710.9
Dec 8 2017,21:29:54 (1002308)
_____________________________________________
Bootloader displayed killswitch enabled please disable,
Killswitch/frp
Killswitch/oem unlock
Killswitch/bootloader
when trying to unlock with provided original unlock_code.bin that was provided with the phone & returns not allowed on production build in bootloader, could not flash any stock recoveries or TWRP back to the device, also couldn't receive the unlock code
_____________________________________________
I used tried the following programs to flash :
•htc_fastboot.exe
•minimal adb and fastboot 1.7msi
•power shell on windows 8.1
•minimal adb & fastboot
•fastboot binaries from htc_dev.com
couldn't get anything to flash to the customers phone with any of these so dont bother.
____________________________________________
NOTE
I downloaded the OTA's & firmware from the google spreadsheet it had no file for the 2.33.710.9 section there the page it went to was 404 so I just downloaded all of the files with the same CID htc_039 in this case, so just download all relevant files with your matching CID main version shouldn't be an issue as it wasnt for me.
_____________________________________________
REPAIRING THE HTC U11
NOTE
☆Links are at the bottom of tutorial☆
#1 Go through the files in spreadsheet then download all with the same CID as you have even though the main versions might be different,
#2 try to flash them all with normal fastboot to see what is a signed or close to signed zip and what isnt, (you will know by the RUU errors you face anything but RUU security fail zip from USB command or RUU main version fail ) means it probably won't work but try anyway,
NOTE
I narrowed it down to a few but the one that did end up working was main version 1.11.710.5, but this main Verision was 2.33.710.9 ??? Dont ask me how it worked twice as it needed to be flushed first time it said but it did,
#4 Now the only flash tool that works for downloading to the device in RUU mode is the HTC 10 batch tool.
#5 Place the .zip into the "com" folder which is located where ever the batch tool is installed, in my case was C://Android/com
#6 Open the batch tool with administrator privledges,
select option 3 to open fastboot terminal with the purple screen
NOTE
when entered location of the terminal should be "example" C://android/com on the screen this is where you placed your RUU.zip file.
#7 boot U11 to download mode, with device off hold,
•Power
•Volume down
NOTE
plug the device into the computer & make sure drivers are installed properly and working.
#8 Type into the terminal "fastboot oem rebootRUU",
phone will reboot to RUU mode.
#9 type into terminal "fastboot flash zip <file_name.zip>
NOTE
do not add " " or < > into the command syntax simply drag and drop the file if you do not wish to type the entire filename out.
it flashed all 28 zips twice in my case as it needed to be flushed the first time, these same files would not work on any other fastboot terminal I would only ever receive RUU error zip from USB command or RUU error main version fail,
so there you go this helped me and now I hope it can help you all out with your broken U11 fix please enjoy and if this tutorial has helped you please dont forget to hit the thanks button
_____________________________________________
NOTES
when using the HTC 10 batch tool fastboot terminal you can use either standard "fastboot" syntax or the "htc_fastboot" syntax both work.
WINDOWS 10 USERS :
you MUST disable driver signature verification or you will not be able to install any drivers for your U11.
_____________________________________________
FASTBOOT COMMAND SYNTAX
_____________________________________________
STANDARD SYNTAX
fastboot oem rebootRUU
fastboot flash zip "<example.zip>"
HTC SYNTAX
htc_fastboot oem rebootRUU
htc_fastboot flash zip "<example.zip>"
_____________________________________________
LINKS
_____________________________________________
HTC 10 batch tool (credits to sneakyghost ),
http://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
_____________________________________________
Google spreadsheet for your RUU (credits to 5m4r7ph0n36uru),
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
_____________________________________________
HTC drivers for your U11 (fastboot adb & mtp)
http://gsmusbdriverzone.xyz/download-htc-u11-usb-drivers-official.html
____________________________________________

☆☆☆EDIT☆☆☆
I have noticed in download mode OS VERSION is 2.33.710.9 still,
But in the OS system settings in about phone & also HTC sync manager the OS VERSION is 1.03.710.7,
BUT it can also receive and install OTA updates up until 1.29.710.9 version before it will not install any higher updates,
So may be best to unlock the bootloader & flash a newer RUU version to your device to OTA update.
Very strange indeed but just thought I'd better add it.
Thanks

Mahalo OP for your posts. I'll give it a try. I got my phone back from HTC and it is still not operating correctly. I mistakenly relocked the phone, bricked it, sent it back to HTC and got it back the other day. When I turned it on and got the OTA update and the phone is rebooted, I got a corrupt OS error message and would not boot. Had to use Fastboot reboot to get the phone to boot up.
Sent from my coconut frond hut using Tapatalk

mauiblue said:
Mahalo OP for your posts. I'll give it a try. I got my phone back from HTC and it is still not operating correctly. I mistakenly relocked the phone, bricked it, sent it back to HTC and got it back the other day. When I turned it on and got the OTA update and the phone is rebooted, I got a corrupt OS error message and would not boot. Had to use Fastboot reboot to get the phone to boot up.
Click to expand...
Click to collapse
Hey mate,
No problem at all
Firstly though I would strongly suggest to flash the Unlock_code.bin you got from HTC dev to unlock your bootloader while you have a functional OS,
enable OEM unlock in developer settings then flash unlock code via bootloader or download mode, will save you the big headache of what I was going through when the bootloader is re locked only signed firmware can be flashed but if unlocked can flash unsigned firmware to the device,
I'd say HTC has not repaired the device correctly at all, I'd be pursuing reimbursement for any money you have paid to them,
not even I have had re corruption or anything works like brand new just my OS version in download mode is 2.33.710.9 but zip I flashed in RUU mode was 1.03.710.7 but let me OTA all the way up to 1.29.710.9 before it stopped installing them it downloads it just wont install it,
I'd switch OEM unlock on, flash unlock_code.bin to get unlocked bootloader will stop you from getting the corruption error, I'd also change the OS also just to see if HTC havent flushed something out of the device properly.
Just please whatever you do do not lock the bootloader without a functional OS
Hope this helps mate, if you need any more help dont hesitate
Thanks

Thank you for sharing you experience, I just want to clarify something here because I don't understand why someone want to relock their bootloader
- For warranty ? it will show up as re-locked so they know you did something anyway
- For OTA ? You can still get OTA on unlocked bootloader. Just restore your untouched system image backup and original reovery or flash RUU then apply the OTAs
If for some reason someone still wants to relock the bootloader you must flash the exact correct RUU first to restore your original system and recovery!

I ended up using the SD card method to reflash the stock OS to my bricked phone. I tried using ADB but I was not getting anywhere. Finally I noticed that when I attempted to flash the latest RUU zip file using the SD card method the process got to a point where it almost completed but there was a couple error messages. So I decided to flash a earlier OS and that worked! The phone booted right up. I still was a bit cynical that the phone wasn't completely out of the woods so I did the process of updating the OS via the software update menu. The phone did take the two earlier OS updates and finally was updated to the latest OS and booted up without any issues. Awesome.

korom42 said:
Thank you for sharing you experience, I just want to clarify something here because I don't understand why someone want to relock their bootloader
- For warranty ? it will show up as re-locked so they know you did something anyway
- For OTA ? You can still get OTA on unlocked bootloader. Just restore your untouched system image backup and original reovery or flash RUU then apply the OTAs
If for some reason someone still wants to relock the bootloader you must flash the exact correct RUU first to restore your original system and recovery!
Click to expand...
Click to collapse
No problem mate ,
I'm not sure why,
but the customer locked his bootloader before having a workable OS, he had a viper rom with TWRP on it & from what he told me he wanted the oreo bootloader and modem so tried to flash a firmware package that did not flash, but did not take a nandroid backup prior with TWRP then locked the bootloader allowing only signed firmware to be flashed, dont asky me why lol, as even re locking the bootloader it stills shows as modified in bootloader mode, possibly he thought that it would go away if he re locked it I cant be certain he wasnt to sure what he did,
I also had to re lock the bootloader after unlocking it to receive the OTA Updates from 1.03 - 1.29 as they wouldnt install they would download but not install as soon as I re locked it again I could OTA all the way up to 1.29.710.9 before the same would download but not install,
But in my personal reference to everyone you would be better of keeping the BL unlocked your device wont corrupt
As for the re lock of the bootloader snd the exact ruu version as mentioned in the post OS this was corrupted and would not boot, had no recovery only fastboot, download & RUU , could not flash token or receive unlock code, main version on device was showing version 2.33.710.9 as oreo firmware but ruu that I got to successfully flash with the HTC 10 batch tool was nougat 1.03.710.5, which was also giving me RUU error main version in normal and HTC fastboot but same file worked in the batch tool fastboot with or without htc-fastboot syntax I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would , main versions and SDK were both diff and it definitely works I recreated and flashed the device over and over again just to be sure before originally posting

mauiblue said:
I ended up using the SD card method to reflash the stock OS to my bricked phone. I tried using ADB but I was not getting anywhere. Finally I noticed that when I attempted to flash the latest RUU zip file using the SD card method the process got to a point where it almost completed but there was a couple error messages. So I decided to flash a earlier OS and that worked! The phone booted right up. I still was a bit cynical that the phone wasn't completely out of the woods so I did the process of updating the OS via the software update menu. The phone did take the two earlier OS updates and finally was updated to the latest OS and booted up without any issues. Awesome.
Click to expand...
Click to collapse
Have to use fastboot to flash device, or sd card,
Fastboot is diff from adb, but glad everything is working well now for you mate and you shouldn't hopefully have anymore problems with it

Matty1993;77934110<snip>
I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would said:
You have more patience than me. Ha! I was so frustrated after I relocked the bootloader and I wasn't able to boot up the phone after a few days. My first mistake was that I DIDN'T RESEARCH AND READ BEFORE I DID ANYTHING. I was a bit perturbed when the OTA update nag screen was coming up so often that I wanted it to go away. Well now I know better that relocking the phone was not the route to go in receiving the OTA update. I should have just calmed down and read and researched more before I shipped off the phone to HTC for 5 weeks for nothing cause they didn't do anything to the phone.
Click to expand...
Click to collapse

mauiblue said:
Matty1993;77934110<snip>
I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would said:
You have more patience than me. Ha! I was so frustrated after I relocked the bootloader and I wasn't able to boot up the phone after a few days. My first mistake was that I DIDN'T RESEARCH AND READ BEFORE I DID ANYTHING. I was a bit perturbed when the OTA update nag screen was coming up so often that I wanted it to go away. Well now I know better that relocking the phone was not the route to go in receiving the OTA update. I should have just calmed down and read and researched more before I shipped off the phone to HTC for 5 weeks for nothing cause they didn't do anything to the phone.
Click to expand...
Click to collapse
Haha patience probably not lol I'm surprised the phone ever started working again after some of the things it got called , no I'm just persistent in everything I do if I cant repair it I make it my goal to repair it ,
That's what I explained to the customer also never lock a bootloader when they system doesn't function as it should only bad things can happen,
I kept getting the OTA notification pop up to but you cant turn it off on HTC like you can with Samsung
I just flashed oreo and kept BL unlocked and no problems again so far
But it does pay off to read that is very true, I learnt the hard way when I first started out with mobiles I had a brand new S3 when they just came out and ended up flashing an S2 kernel to it and literally burnt the touch controller out on the board and made the touch non functional, I've always read up on everything ever since before attempting repair modification or customisation and havent gone wrong since pretty much,
Speaking of HTC did they charge you a fee to supposedly "repair" your device, as I could tell just from what you mentioned something wasnt flushed right in it, which makes you entitled to a refund, I'd file a dispute with them for the work order and reimbursement on the postage and what not as to be honest I've even been all over HTC websites in aus and America and spoken to they're tech support also (usless might i add) even they state that sometimes they cannot even fix this exact issue, and they charge more for the fact the bootloader is modified to repair them,
Click to expand...
Click to collapse

Aloha M. Fortunately HTC has didn't charge me anything. The frustrating thing is that they didn't include with my phone documentation on what they supposedly had done to the phone. Obviously they were able to get the phone to boot up at least once. But it seems like they didn't even test the phone so that it would consistently boot up. Flashing the latest OS update wouldn't have taken much time. I really like HTC phones and their GUI but their customer service SUCKS donkey balls.
Aloha!
Sent from my HTC U11 using Tapatalk

Aloha Matty. No, HTC didn't charge me for "no services rendered". They were able to get the phone to boot but they didn't make sure that all issues was completely resolved. They just placed the phone in a shipping box and sent it back to me with no documentation to what they did to the phone. BTW today makes a whole day since I was able to get my phone working and rooted. I've got all the main apps I normally use installed and signed on. So far so good. I'm now working on my U12+ and tweaking that phone as I notice the battery life is not as good as the U11.

mauiblue said:
Aloha Matty. No, HTC didn't charge me for "no services rendered". They were able to get the phone to boot but they didn't make sure that all issues was completely resolved. They just placed the phone in a shipping box and sent it back to me with no documentation to what they did to the phone. BTW today makes a whole day since I was able to get my phone working and rooted. I've got all the main apps I normally use installed and signed on. So far so good. I'm now working on my U12+ and tweaking that phone as I notice the battery life is not as good as the U11.
Click to expand...
Click to collapse
That's great mate, glad it didnt cost you anything then, apart from the 5 week wait though that must have been terrible,
I would have thought they would package it up a bit better but then again they have never been good for service,
Anyhow everything must still be working well then and all issues seem to be gone, , I'm yet to receive a U12 into my work for repair but I do agree battery is pretty good on the U11 I can charge it and it last me 2 days almost before I have to charge it again, but then again I've had it open aswell and the battery takes up 3/4 of the phone under the hood it's a very big battery even in actual size,
Anymore problems with U11 or any other makes and models feel free to contact me through pm or post if you need help and I'll get back as soon as I can

Thanks Matty. All the best!
Sent from my HTC U11 using Tapatalk

So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas or advice would be appreciated.

RWSDH said:
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
Any ideas or advice would be appreciated.
Click to expand...
Click to collapse
Hey mate,
Yeah somethings going wrong with your OS
What version of android is it using ? 7.0 or 8.0,
As the bootloader is unlocked please KEEP it unlocked dont relock it under any circumstances if relocked only a very specific version of firmware can be reflashed and if flash fail the device will be bricked completely until the correct RUU is flashed
S-ON shouldnt be a problem when BL is unlocked and you can flash most firmwares that match your HTC u11 MID & CID
Recovery should boot without an SD card so if say recovery is corrupted aswell as part of the system is also,
What you need to do is plug it into the PC and using fastboot type the command,
fastboot getvar mid
fastboot getvar cid
with the device in download mode if you can,
If it wont boot to download mode with the button combination
Turn USB debugging on & connect to pc now your going to be using adb
Type this command to try and reboot to download mode to use the fastboot command to obtain your device info
adb oem reboot-download
Or adb reboot-download
It should reboot you to download mode now where you can obtain the necessary info with the fastboot getvar command,
Once you have that info head over to the google spread sheet and download the firmwares that match your MID & CID and then use the tutorial one page 1 to flash the phone,
Remember do not lock BL under any circumstances bad things will happen if the flash goes wrong.

RWSDH said:
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
Any ideas or advice would be appreciated.
Click to expand...
Click to collapse
I had an nearly similar problem with my SD Card it always was seen corrupt from the system even after formating the SD Card. Then I did a factory reset, that did the trick for me.
It may take some time to set up the phone again, but for me it was the only way to make it reusable again.
Try to use different hardkey combinations, there are more then one to get into bootloader or downloadmode and even with the ADB commands you can treat your device to do what you want!
I hope this will help you.

So the links that I posted don't work because I don't have enough posts. I have factory reset the phone a few times in an attempt to get things working properly again. Here's the info since I can't put up the screenshots:
Android version:
8.0.0
Security level:
June 1, 2018
Software:
Bad Boyz US unlocked U11 v3.8 (I have a feeling I may have used the wrong one here)
Kernel:
3.3.78-perf-gbd700a6
[email protected] #1
SMP PREEMPT
Baseband:
8998-002772-1712182056
Build:
2.42.617.7 9.0_g CL1011554

Why when I run the command "fastboot flash zip ruu.zip" a message pops up that can not open a zip file?
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka

kajfux said:
Why when I run the command "fastboot flash zip ruu.zip" a message pops up that can not open a zip file?
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka
Click to expand...
Click to collapse
Have you tried the htc_fastboot command syntax mentioned in the tutorial also with the batch tool ? If so and its still not working Its 100% to do with the zip your trying to flash id say it contains header errors,
Has it given you an error somewhere along the lines of "
a terrible mishap happened with the original ret lens 0" thats another common error to receive to indicate that your .zip is no good,
Try another .zip that matches your PID & CID dont worry about the main version the htc batch tool fastboot command promt for bypasses bootloader security to allow rollback of the bootloader,
I successfully took mine back to nougat from oreo with a locked bootloader which couldnt be re unlocked due to all killswitches being on & S-ON, no recovery or working OS, only download, bootloader & RUU mode,
Deffo the .zip trust me sorry for the late reply aswell didnt get notification but i hope this helps you out a bit.