[Q] What's the difference between SPL Hboot and Recovery? - Android Q&A, Help & Troubleshooting

What's the exact difference between SPL Hboot and Recovery?
Please explain it precisely.

There's a link in my sig to a glossary of Android terms, you'll find both of those listed there with a good description. But seriously though, you could've just Googled it...

Why so many of you assume that people don't make a search before they make a question?
I did Google it and I haven't found a good answer. And I haven't found a good answer in your glossary either. Pleased?
The glossary says that Hboot is a piece of firmware - great.
I've been asking for precise explanation.
If you would google it you would probably find the information that Hboot is the same as SPL not as Bootloader:
http://forum.android.com.pl/f92/hboot-co-to-takiego-11383/
That is why I'm making the quiestion:
1. What is what.
2. What does what.
3. And what is more primary.

HBOOT is 2nd stage bootloader. (GRUB, NTLDR)
Recovery is a boot image that used to fix and manage the system. (Recovery boot, Safe mode)

Thank you omongo.
I feel the difference between NTLDR and Safe Mode.
And what is the difference between Hboot and SPL?

Maxymo123 said:
If you would google it you would probably find the information that Hboot is the same as SPL not as Bootloader:
http://forum.android.com.pl/f92/hboot-co-to-takiego-11383/
Click to expand...
Click to collapse
I'm not sure if it's Google Translate's fault or not, but the description Arturrro gave in that thread is horrible, using terms such as SPL (secondary program loader) dates back to the WM days. Android doesn't use the same system as WM, so things are pretty different.
Maxymo123 said:
That is why I'm making the quiestion:
1. What is what.
2. What does what.
3. And what is more primary.
Click to expand...
Click to collapse
If anyone spots something I've made a mistake with, let me know.. But otherwise, this is the conclusion I've come to after about 5 months' worth of research. And all of it retrieved by nothing more than reading XDA, searching Google and trial-and-error on my Desire.
HBoot
What it is: This is the hardware initiation or boot stage, much like the BIOS on a PC. Other than a placeholder for specific settings, all the HBoot does is handle the initial hardware initialization for your device.
What it does: With S-off (or 'Full Root' as it's also referred to) controls specific settings related to your device: these include the system partition size, cache partition size, data partition size, and more. They are not stored in an editable way, hense the reason for flashing a modified HBoot to get custom system partition sizes.
FastBoot
What it is: This is a more software orientated system, you'll notice when loading into FastBoot, support for the navigation controls on your phone are enabled? That's because it's already started loading your device drivers into memory at this point. Think of it as a GUI to the terminal style interface to the system settings on your device.
What it does: Because certain navigation and communication drivers are loaded at this point, USB connections are available in this state, which allows the use of both the ADB (used to push/pull files from phone) and FastBoot (used only as an initiator for FastBoot on the phone itself) processes to be run from a computer to update areas of your device.
For the record, the 'Recovery' menu as Omongo says, is not really a 'safe mode'. The recovery menu only shows up after rooting the device, it's a true root-level management tool that allows you to make system changes in a less technical manor.
For example:
Flashing a custom ROM via FastBoot involves terminal commands to push the update to the phone's memory card ('adb push update.img') then to flash it and update the correct areas ('fastboot flash system update.img').
Flashing a custom ROM via Recovery involves selecting the menu options update by a selected zip file, this would then use the same methods as FastBoot to flash, but you don't need to manually type any commands.

Thank you ZaLiTH very much.
That clears many things up.
Would you mind answering my other question?
I can't get a good explanation of what exactly Gfree and Rage are:
Here.

Maxymo123 said:
Would you mind answering my other question?
I can't get a good explanation of what exactly Gfree and Rage are:
Click to expand...
Click to collapse
Honestly, I'm not sure.. I've never used either of those apps. Best bet is probably to see if they have dedicated threads on XDA, or wherever it is you originally found out them.

Tahnks.
Obviously I was asking after searching in google.

Related

[Q] One Click Bootloop + Trackball Issue

Okay, so I've seen these issues dealt with separately, but never in conjunction. Unfortunately, I am having both in conjunction.
Starting with a fresh Droid Eris, I used a one-click root to allow superuser permissions.
From there, I flashed CM7. Along with many other users, I ran into the issue where I had no data or voice signal.
I'll let you know here, that I've wiped EVERY time I did anything. This is NOT a wipe issue.
I flashed the newest radio... No luck. So, I went through clockwork's recovery and reverted back to the original 2.1 ROM. Still no luck on the signal issue. At this point, I decided to reflash CM7 and try to deal with the issue through ADB.
This is where things went wrong. The load for CM7 corrupted (I'm assuming) and gave me a nice case of Bootloop. Thinking everything was fine, (Assuming I'd do a battery pull and just go back to 2.1) I booted into the original Android recovery and NOW the damn track ball will no longer make selections. It will scroll, but not select.
Here's my question: Seeing as I can not boot fully to allow usb debugging, and I can not recover through Android (Thank you, trackball), is there ANY way to reflash the original RUU through ADB?
Thus far, I can't get passed the obvious "This device is not ready," prompt.
Any help is greatly appreciated.
FYI, adb is available when the custom recovery is booted.
what that means is that with the recovery booted you can:
1) drop a smallish (say, less than 100 MB) ROM file into /cache (e.g. "adb push")
2) create an Android command file (/cache/recovery/command) with a single line that points at the ROM file as an update
3) do a "adb shell reboot recovery"
This will cause the subsequent boot to the recovery to automatically install the ROM file you dropped in cache.
Voila. No trackball needed.
The syntax for the command file (/cache/recovery/command) will be a single line:
--update_package=CACHE:your_ROM_file_name_goes_here.zip
See this post for an expanded explanation.
cheers
[ Edit ]
Note that the above is a thumbnail sketch which requires you to fill in the blanks. For instance, wiping /data and /cache and flashing packages after the main ROM. Cumbersome, but you only need to do it once. Once you have a rooted ROM installed, you should flash a trackball-free version of the recovery so you don't need this method for every ROM you install. Instructions for that (using "flash_image" via adb) can be found elsewhere.
Scott,
Whoa! You got a lot going on there...
Okay, I don't have all of the answers here for you, but I know enough to ask a few questions that we'll need a clarification on.
1. Can you tell us your HBOOT version and whether its S-ON or S-OFF?
2. You mentioned that you've used ClockworkMod (not good , but maybe not terrible)...you also have mentioned using/having Amon_RA custom recovery. Which custom recovery do you have currently installed and can you boot into said recovery?
3. By the way, I think the voice/data signal thing is fixable--it sounds familiar to me, but I don't know the answer right off-hand and this is not your primary issue at the moment.
4. You should be able to run the RUU to restore 2.1 back to your phone. It doesn't require a working custom recovery running and/or adb. Although you might simply be asking if you can flash a ROM through adb, then the answer is yes, you can. Although you will need custom recovery running to make sure its adb server is running and that, of course, require USB connectivity (alluding to your "This device is not ready." message).
5. Usually, installing HTC Sync will install the USB drivers necessary for you to use adb. If that doesn't work for you, PM me with your email address and I'll send you about 10MBs worth of USB drivers I've collected over the last year that might help you with this issue.
6. Lastly, there is a version of Amon_RA's custom recovery available that does not require the use of the trackball. You're not really in a position to flash/install that at this point unless you have the S-OFF engineering bootloader.
I'll hold-off with additional info pending your responses to the above.
Cheers!
edit: trumped by the Master himself, LOL! [I knew you'd be along sometime soon, bftb0 ]
scary alien said:
Scott,
Whoa! You got a lot going on there...
Okay, I don't have all of the answers here for you, but I know enough to ask a few questions that we'll need a clarification on.
1. Can you tell us your HBOOT version and whether its S-ON or S-OFF?
2. You mentioned that you've used ClockworkMod (not good , but maybe not terrible)...you also have mentioned using/having Amon_RA custom recovery. Which custom recovery do you have currently installed and can you boot into said recovery?
3. By the way, I think the voice/data signal thing is fixable--it sounds familiar to me, but I don't know the answer right off-hand and this is not your primary issue at the moment.
4. You should be able to run the RUU to restore 2.1 back to your phone. It doesn't require a working custom recovery running and/or adb. Although you might simply be asking if you can flash a ROM through adb, then the answer is yes, you can. Although you will need custom recovery running to make sure its adb server is running and that, of course, require USB connectivity (alluding to your "This device is not ready." message).
5. Usually, installing HTC Sync will install the USB drivers necessary for you to use adb. If that doesn't work for you, PM me with your email address and I'll send you about 10MBs worth of USB drivers I've collected over the last year that might help you with this issue.
6. Lastly, there is a version of Amon_RA's custom recovery available that does not require the use of the trackball. You're not really in a position to flash/install that at this point unless you have the S-OFF engineering bootloader.
I'll hold-off with additional info pending your responses to the above.
Cheers!
edit: trumped by the Master himself, LOL! [I knew you'd be along sometime soon, bftb0 ]
Click to expand...
Click to collapse
Yup bftb0 is a beast at these things, lol

A crash course on the Rezound and modding

There seems to be a lot of confusion about what things are or how they work together so I'm gonna try and build a post to explain some things. If i get any of this wrong, feel free to call me out and I'll correct it. I can generally be relied upon to make mistakes.
First let's start with the various things that you're gonna be hearing about or messing with on your phone.
Hboot or bootloader
This is pretty much the lowest level thing you're gonna mess with. This is what makes the phone boot up, and where you can flash all sorts of things like new hboots, kernels, and whole roms depending on how they are packaged. You can get here by either powering off your phone then powering on with volume down + power, or by selecting "reboot to bootloader" in most custom roms. If you've entered your hboot from a powered off state, you'll start in hboot, also known as the bootloader. The bootloader is where you will load ph98img.zip files, factory reset, boot to recovery, or enter fastboot. Fastboot is the section of the bootloader that will allow you to run fastboot commands from your PC/mac/whatever to load things like boot images, recovery images, return your phone to an s-on state, etc. It's a very powerful interface. From here you have menu options which will allow you to reboot, power off, or return to the bootloader.
If you've entered hboot from the adb reboot bootloader command or your custom rom, you will start in fastboot, and can enter the bootloader from here.
When entering the bootloader using either method, the first thing the phone will do is look for a PH98IMG.zip file. If it finds one, it will want to install it. You'll have the option of installing it, or rebooting. That's it. This is why you want to get rid of the ph98img.zip files from the root of your sd card once you've used them - if you pooch your rom, you're not getting into recovery or fastboot until you remove that file. If you can't boot your phone, you better hope you have another SD card or a micro sd card reader kicking around somewhere. You can boot into fastboot by powering off the phone, then powering it on by holding power and volume down keys at the same time.
A word of warning - this is one of the few places you can actually "brick" your phone. Don't mess around with installing hboots unless you are absolutely certain that you a) have a need and b) have an md5 checksum of the file and have verified that checksum on your own gear. Generally speaking, the only time you need to flash the hboot is when you are upgrading in some way, for example when going from GB to ICS.
Quick note - when people refer to the "SD card patch" they are referring to a patch that allows you to use the GB firmware with ICS roms. This is largely unneeded at this time, since the main purpose was for folks who wanted to run ICS roms without upgrading their hboot - there's no going backward with hboot unless you have s-off.
Radio files
this is how your phone works with the radio. you can brick your phone here, too, so always check md5 before installing, and ask yourself if you really need to be installing it. new radio versions are generally given the credit for things like increased signal strength, faster 3g/4g, better power consumption, etc. these are often paired with a kernel, as well.
Recovery
This is a software layer that you can flash to your phone that allows you to boot the phone into a utility state where you can install roms, flash things like patches or modifications, backup your rom/kernel, etc. When people refer to a nandroid backup, they are referring to a backup made here. It's a snapshot of your phone that lets you mess with things and restore back to that point in time should you screw something up. You pretty much can't brick your phone at this level - it's all just files and filesystems. You can also mount your SD card to reader mode for connection to a computer, do a factory reset of data, and a few other fun things like root your rom here. You should only root your rom if it is a stock rom that has not been rooted yet. Rooting a rooted rom will usually unroot your root so you don't have root.
There are a couple of different recoveries. The rezound community seems to use primarily amon-ra, which is what i use, but there is also clockwork recovery as well. Recovery is usually installed by booting your phone into fastboot and running the "fastboot flash recovery <recovery file>" command. Recovery can also be installed via the flash_image binary found in the RomManager package (ex: flash_image recovery amonra.img). This eliminates the need for fastboot altogether. Just need a terminal, root, and the flash_image binary.
Kernel
This is basically the primary component of an OS. The kernel is where a lot of the functionality of the phone are made or broken. the setting that prevents use of setcpu to change the way the CPU is governed is here. The thing that prevents bluetooth from working right on sense 4 roms? Kernel. Everyone is waiting eagerly for the ICS kernel source to be released so custom kernels can be made that resolve these issues and more. You can flash a kernel via recovery if you've done s-off to your phone, or via a ph98img.zip file in the bootloader. With s-off, kernels can also be backed up in recovery. The kernel is often given much of the credit or blame for the performance of your phone, overheating, etc.
Roms
Your phone's OS, sometimes incorrectly referred to as firmware. It's not - the firmware is the stuff we've already covered that can brick your phone. Think of your phone more as a tiny computer, with the rom being the distribution that you're using. This is pretty apt since it's basically linux, and just like linux, the actual OS is just files and partitions. Because the radio interface layer requires sense, the bulk of our roms are all based on sense roms, and all the functional ones are. Developers modify them to add features, remove bloat or sense components, or take sense roms from other phones and adapt them for our own. You install a rom through recovery.
Never claim to have "bricked" your phone when installing a rom. You can't, and doing so only points out that you don't really know how your phone works. This is embarrassing and best avoided when possible so jerks like me do not tell you what a n00b you are, and to go read threads like this one. Since you're here, we can assume that you've bothered to research things before asking stupid questions, so bravo! In all seriousness, you can no more brick your phone by messing up the rom than you'd brick your PC by screwing up your windows install. You can always start again from the beginning and reinstall. You might lose apps and settings, but this is the nature of the beast. Always nandroid before messing about, and you'll be fine. Nandroid is covered further later on.
RUUs
Strictly speaking, the things that we refer to as RUUs aren't. Everyone calls them that anyway, and I don't see it going away anytime soon. Technically, however, an RUU is HTC's Rom Updater Utility, and it's an executable that gets run on your PC, not something you load to SD card and flash in your bootloader. That said, RUU has come to mean factory signed software/firmware packages that are released by the manufacturer or leaked. They come in the form of a ph98img.zip file that can install pretty much anything - hboot, radio, kernel, rom, etc. What is installed varies from package to package.
Installing an ruu can only be accomplished on a phone that is currently not in an htc dev unlocked state, or a phone that has s-off. when installing one of these that includes an hboot, you'll need to reinstall recovery as well - installing a new hboot via RUU will always require this as the custom recovery is overwritten with the stock recovery.
If your phone has not yet had the s-off procedure done and you intend to do so, make sure the RUU you are about to install does not break the s-off exploit. Doing so will lock you into that RUU until the dev updates the exploit to work with the new hboot (if included in the RUU) or another RUU is released.
HTCdev
This is the method HTC gives us to unlock our phones. it allows us to install recoveries and roms, but not a lot else. you cannot downgrade your hboot or radio files with this, for example. you can install kernels via ph98img.zip file, but not through recovery. basically, it's HTC's way of letting us mess with our phones but without (hopefully) giving us enough control to brick them. this is considered better than nothing, but much less than ideal since you still don't have total control over what your phone does and how. doing this does essentially void your warranty, though to date there have been no confirmed reports of this affecting a return via either warranty or insurance.
With your phone in a stock state, you can apply only factory signed RUUs. Roms and kernels are closed to you, and you can move only forward with your radio and hboot, never backward.
With your phone in an HTCdev unlocked state, you can apply unsigned RUUs that contain a boot, system, and recovery image - all components must be present.
To get your phone into this state, visit HTCdev.com.
S-Off
This sets your security flag on the phone to off.Stock, your phone comes with this flag set to on. Our s-off method does it at the radio layer, and at this time is thought to be irreversible by update. It isn't, though - it's just unlikely because there are legitimate s-off phones out there. Still, it's always a good idea to wait to see if that shiny new RUU is gonna make your phone boring again before you install it. To be safe, wait for an RUU that has the hboot removed and just applies kernel, radio, and system files. You can turn it back on with fastboot should you wish, however. Htcdev unlocking, a bit of wire or a paperclip, and a decent set of timing is required for this. In my opinion it is best to do this once you are sure your phone does not have problems that require a warranty return, but it should be done before upgrading to new, untested OTAs/RUUs. There's always the chance that HTC will block the exploit that gives us this, at which point you're stuck until the devs figure out another way or someone comes up with some crazy method like the evo 3d guys. Many are nervous about this process, and for good reason. While the devs have done everything they can to make this bulletproof, it is best to enter into this mod with as much knowledge as possible, just like any other mod. It's also best to be relaxed, have an internet connection other than your phone, and not have anywhere you have to be right away in case things go like you don't expect. Should things go wrong, don't freak out. Ask questions. Many "bricked" phones have been restored with simple application of knowledge.
Things s-off does: Allows you to flash kernels from recovery, allows you to flash any hboot and radio you want. Lets you install any "ruu" you want with any combination of boot image, system, and recovery, rather than the entire package. Makes rom installation easier on devs due to kernel installation in recovery.
Many have scoffed at s-off, claiming it does nothing that unlocking doesn't do already. This isn't really the case, as we've all seen how important the ability to downgrade firmware and radios can be. Personally, I think of a phone with s-on in much the same way I think of eating steak through a trash bag. If you have the option not to, what the hell are you doing?
Things s-off does not do: magically turn your phone into an open platform to which devs will instantly flock to give you the aosp roms you believe yourself entitled to. What will do that? Glad you asked.
RIL - radio interface layer
Basically, the RIL is a driver for the radio - it lets the radio interface with the software running on the phone. This is a new problem that effects 4g phones. It sucks. Basically, your manufacturers (also verizon, but you can assume they don't want you to do anything other than pay them.) don't want you touching their precious radio chipset with your grubby little paws. We don't have source code, and they're not talking. Of course we already have software on our phone that has the RIL stuff we need, right? Yes... sort of. For any sense roms we want to use. This is why we don't have aosp. For aosp, one of three things needs to happen:
1) Manufacturers grow a soul and give us source in the form of a leak or they go mad and just release it. This is pretty much as likely as Verizon deciding that they are doing away with early termination fees.
2) Someone reverse engineers our RIL and makes their own RIL software. This is as likely as my wife developing new roms for her Incredible 2. The one she blames for her school's ****ty email server and wants to trade in for an iphone.
3) Someone develops an interim layer that translates aosp to sense and back again. This was done on the thunderbolt, but it was wonky. Certain individuals are confident that this will be easier done on ICS and are working on it. Some AOSP action would be pretty damn awesome, but don't expect it, demand it, or hold your breath for it. It's hard, and is going to require a very intense combination of skill, knowledge, and tenacity.
Now i know what you're thinking - the Nexus is a CDMA 4g phone and they can do whatever the hell they want. Do they have an open RIL? The answer is no. They have an aosp (Android Open Source Project) RIL though, which amounts to basically the same thing. If it is any consolation they can't have sense roms as a result. Those poor bastards, right? This is why many are torn between the Nexus and the Rezound. The Nexus is open and a dev's paradise - CM9, AOKP, MIUI, ****ty roms that some kid slapped a godawful theme on - it's all there. The Rezound has better radios, better screen, and better build quality (subjective) but no aosp. If you're reading this you've already chosen or had the choice made for you by verizon's $50 sale.
Fast Boot
But Derek, you say, you already talked about fastboot in the bootloader section. We get it. Nay nay. This is fast boot. Note the space. Basically, HTC roms include a tech that puts the phone into a hibernation state rather than powering off. You'll find it in the power menu. When this box is checked, your phone will go from powered off to your home screen in a very short period of time - 15 seconds on my phone, vs the normal 45 second boot time. If you pull the battery, you will have a normal boot time. Personally, I could take or leave this feature. I almost never shut my phone off, and when I do, I want it to actually shut off because i'm shutting it down because I need a cold boot. It's up to you how useful this feature is to you.
Perflock, CPU Frequency, and Governers
Many people have had poor experiences running the ICS leaks due to the CPU maxing out. The stock HTC kernel uses perflock, which constantly resets the frequency and scaling of your CPU. This means that the use of programs like setcpu or system tuner to change the min/max frequencies or governer of your CPU will cause it to essentially run in a state where it is either using the max frequency, or the minimum, without scaling up and down according to need. Some CPU monitoring apps will cause a similar reaction. The best way to avoid all this unpleasantness and get the best battery life out of your phone is to simply leave it be and let it do it's thing, because quite frankly you can't stop it anyway. If you absolutely must see what your CPU is doing, I have had good results with CPU Monitor by Coconuts. I still don't recommend keeping this active full time as I suspect it still impacts performance and battery life, but many do without any obvious adverse results. As a side note, the HTC kernel uses the On Demand governer, which steps up the CPU frequency quickly when needed and scales it back down slowly. Clearly, HTC's focus was on performance rather than battery life, here. Once kernel source for ICS is released, devs can build custom kernels which do not include perflock, and add other nice features as well like full power usb charging. Once this occurs, we will be free to use setcpu to scale our CPUs up or down to our hearts content and use whatever governer we like. Until then the best advice is simply to leave it alone.
I will be updating this and adding to it constantly. I'm not an expert, just an average user who is trying to put some useful info in the same place. Please shoot me a PM with suggestions/things I got wrong and I will update this post and credit you.
Contributors who have helped make this more accurate
scotty1223, esheesle
Section for General Education Type Things
Titanium Backup
Quite possibly the most useful software you will use on your rooted android device. Well worth buying. This software will allow you to backup pretty much everything on your phone to your sd-card, dropbox, box account, etc. It even lets you pull data from nandroid backups. This is the best way I know of to backup your apps and restore them when switching to a new rom. Not only do you not need to go digging through the my apps section of the play store to reinstall every damn app, you can restore with the data from the time of the backup. That means config for a lot of apps, game saves, etc. Note that most SMS apps and launchers will require you to use the backup included in their software, as Ti Backup doesn't grab these things. Forgot to backup your apps and data but made a nandroid backup? No problem. It can read your nandroid backup and pull those things right out of it.
It can also screw up your rom install to the point where you might as well factory reset, if you use it wrong. Basically, you never ever want to use it for anything other than apps you've installed from the app store and their data. Restoring system apps, unless you know what you're doing, is a bad idea. Restoring system data, no matter how tempting, is an even worse idea. It's very likely to screw you up. There are circumstances in which it may not do so, but if you are reading this and this is new info, you don't know them. Stay away. Most devs will outright tell you not to use it with their rom since people will inevitably ignore the warnings and do it anyway. It makes switching roms an absolute breeze though - I can switch roms and have my software setup exactly how it was before in less time than it takes to download a rom from Android Police. Granted, that's a good hour, but you get what I'm saying. It's a huge time saver. Backup your user apps and data, but touch system apps or data at your own peril.
What to do if you think you're bricked
Step 1: Chill out and slow down. Seriously. Unless your phone isn't doing anything at all when powered up, it's probably recoverable. Double check your MD5 sums before pushing things like hboots and radios, and you should be OK. If you've screwed up the s-off process, make a post describing exactly what you've done and how, then wait for responses. Do not demand them. You can also join #juopunutbear on freenode, where the devs hang out. They're not always right there, but I've seen them help dozens of people out of some sticky places, and they'll help you if they can. They really know their stuff.
For general Rezound problems, you can join #rezound on andirc.net. There's usually some knowledgable guys hanging out there, willing to help. Remember, the very best thing you can do is take the time to gather enough knowledge to be confident that the steps you are going to take to fix the phone are the right ones, and why. Flipping out about your "bricked" phone and throwing anything you can at it is much more likely to make things worse, and annoy the people trying to help you. For example, if you are s-on and in a state where you need to reinstall a stock RUU package, you only have as many chances to get it right as there are newer RUUs than what is on your phone already. If you don't know enough about things to know what is wrong and why, you're not terribly likely to know the best way to fix it. Keep calm and carry on.
What will installing this ______ do to my phone? What do I need to do to install them?
Now that we have s-off and all these new ICS leaks, we've all gotten a bit flash happy. This has led many to ask what they can install, how, and what needs to be done. I'll try and address as much of this as I can by talking about the different states your phone might be in.
Totally stock - You have only one choice. You can install the full RUU, or not. That means you're getting whatever radio, hboot, kernel, and rom come with that RUU. Once you've installed that RUU, you can't install anything but a newer RUU after that. Remember that with RUUs, you need to reboot twice - there are two installation steps in hboot that require a reboot in between. Note that some RUUs will wipe your SD card. Nice of them, isn't it?
HTCDev unlocked - You can install kernels via hboot, a custom recovery via fastboot or hboot if packaged, and custom roms. If you want to install new radio files or an hboot, then you'll want to make a nandroid backup in recovery, relock your phone, and install the RUU via hboot. You cannot install the RUU without relocking first. You can then unlock your phone via HTCdev again, flash recovery, and restore from your nandroid backup. Like a totally stock phone, you can only go forward with hboot and radios, never backward. You have more options than the stock guys, but are still limited. But you also can't brick your phone. Again, some RUUs will wipe your SD card.
S-off - You can do anything you want. Flash any radio or hboot you want. Flash any kernel you like. If a new RUU comes out and you want to try it, just install it. You'll need to reinstall recovery, but that's it. Want to use the new leak's radio and kernel but not the rom itself? Flash 'em. But for the love of god, check the MD5 checksum before you flash. Apps like root explorer will let you see the MD5 of a file right from your phone's SD card. Flashing a bad radio or hboot can brick your phone. With great power comes great responsibility. Flashing hboot, kernels, and radio files do not require you to factory reset your device, nor will they do so. It is advisable to clear your cache and dalvik cache in recovery after installing a new kernel, but that will not affect the data on your device.
So let's say you've got s-off, and you're running a rom you like, but you want that new radio, hboot, and kernel. First, don't touch the hboot unless you have a reason to. That's a risk that you don't need to take most of the time. To flash the radio, find someone who has extracted the radio and repackaged it into a PH98IMG.zip that contains just the radio. Copy it to your SD card, check the MD5, and flash via hboot. To install the kernel, either grab it from someone who has packaged it, or pull the boot.img from the RUU zip. Check your md5, boot your phone to fastboot, and run:
fastboot flash boot <path to boot.img file>
You need fastboot on your PC, of course. Also, bear in mind that with a new kernel on an older rom, you may need to apply patches to make everything work properly, like wifi. Devs will generally release these patches and post them. Simply copy them to your SD card and install in recovery.
Where are all these files?
The Dev section. Go in there, and poke around. It doesn't take long after a leak is released to see that leak taken apart, rooted, deodexed, stripped of its kernel and radio files, etc. Read what people are saying, and asking. Generally, the first post will be updated to have everything you need, but the thread may have what you're looking for as well. What you don't want to do is ask where things are when the same question has been asked several times over already, often three pages back. Sometimes things can be hard to find, but it's good to make the effort. The community will be better for it.
What's a rooted rom? Deodexed? Busybox? Zipalign?
Rooted is fairly self explanatory. It's the process of packaging a superuser app with a rom that will allow you to operate your phone with root access. You'll need this for the good stuff like removing bloat, installing most wireless tethering apps, ad blockers, titanium backup, etc. Verizon wishes you wouldn't do this, so you know it's awesome.
Deodexing basically removes an optimization, called odexing, that basically takes bits of an apk and puts them elsewhere for optimization purposes. Deodexing packages everything back into the apk so you can use different apks without fear of conflicting code, etc. This is what makes a lot of mods possible.
Busybox provides several stripped down versions of unix tools in a single package. A lot of things like titanium backup depend on this. Generally when someone roots a rom they also busybox it.
A zipaligned rom is a rom that has had its application packages optimized for quick access by aligning them on 4 byte boundaries. This allows android to access resources without having to explicitly read them. You don't necessarily need to understand this one - just think of it as being optimized.
Contributions are appreciated and will be credited in the main post. In the interest of keeping this thread clean without a million different versions of the OP, please edit your post down to a basic "suggestions added" or something similar once I've noted your additions. That way things stay readable and don't confuse the readers. Ideally, a PM would be best, leaving the comments free for questions and the like. My goal is to jam as much knowledge in this thread as I can, and I'll continue working on it as I see new questions that commonly pop up.
tspderek said:
I literally meant the phrase "suggestions sent." i would prefer PMs or cleaned up posts after suggestions are included in the original post for cleanliness' sake and to keep down redundant info.
Click to expand...
Click to collapse
so,in other words,youd like your posts,followed by no posts,or "thanks" posts,with no real discussion.
my only issue with that,is simply any of us are capable of sending suggestions that are not correct,or that are correct but an opinion. are you filtering somehow what you add? or just adding everything everyone sends?
its your thread,ill accept your request,but i personally would like to see everyones personal contributions and how you incorporate them.
readers should be smart enuff to seperate the first 3 information posts from the rest of the discussions. my 2 cents
I literally meant the phrase "suggestions sent." i would prefer PMs or cleaned up posts after suggestions are included in the original post for cleanliness' sake and to keep down redundant info.
..
Khayos said:
Suggestion: Sticky! (then delete me)
Click to expand...
Click to collapse
it's been sticky since about an hour after it was written last night...
Thank you for writing this. It should be a requirement to read this before someone can post again.
Thanks for this! I was just thinking that this is getting REALLY confusing...I appreciate the Primer!
tspderek said:
There seems to be a lot of confusion about what things are or how they work together so I'm gonna try and build a post to explain some things. ...
<snip>
Click to expand...
Click to collapse
I had been contemplating a post to ask questions that this addresses; for myself, it is very timely as well as very helpful.
I've seen terms in the forum used interchangeably that really are not, and this helps clarify that. Consistent use of terminology could go a long way to help with the abundance of questions and misunderstandings that exist.
Again, many thanks.
Nice post. Thanks!
I was waiting for the OTA to go official before even thinking about s-off but now you got me thinkin' about it.
If the OTA is good but I just want it de-oxed and de-bloated should I bother with S-Off?
My Dinc was so easy with UnRevoked, wish this one was as easy as that!
my personal feeling is that i like my phone to have s-off, so i can use the radio that works best for me and have full control of my phone. if i've already voided the warranty with htcdev, then why not? it's not a difficult process if you research and prepare everything ahead of time. know the steps, have your tools ready, and you'll be fine. took me one try on my phone.
it's really up to you, though. it's your phone. there is a risk of bricking that isn't there with htcdev. it's low unless you make poor decisions or skip steps, but it does exist - that's what s-off does. it opens the door for you to help or hurt yourself.
Very Useful
This is very well written. I wish I had this when I started my journey with Android. This is my first post btw. Iv been doing this for about 6 months now and hate that i cant post in Developement section. But i appreciate the time it took to make this. Very nice!
Edit.. Second post. Fogot about the first one
Sweet, will be following this closely! Thanks for posting!
Thanks for posting this it helped clear a lot of things up for me. This is my first smartphone and so I'm still learning about this stuff. I think some people forget that not everyone understands all of the jargon. I'm learning more and more about what I can do everyday and this has certainly helped.
Installing RUU
tspderek said:
Installing an ruu can only be accomplished on a phone that is currently not in an htc dev unlocked state, or a phone that has s-off. when installing one of these that includes an hboot, you'll need to reinstall recovery as well - installing a new hboot via RUU will always require this as the custom recovery is overwritten with the stock recovery.
Click to expand...
Click to collapse
tspderek said:
With your phone in a stock state, you can apply only factory signed RUUs. Roms and kernels are closed to you, and you can move only forward with your radio and hboot, never backward.
With your phone in an HTCdev unlocked state, you can apply unsigned RUUs that contain a boot, system, and recovery image - all components must be present.
Click to expand...
Click to collapse
I'm confused. I am S-ON (scared of brick), bootloader unlocked, and running CleanROM Pro 4.3. I want to update to the newest firmware and then the newest version of CleanROM. Do I have to re-lock my bootloader in order to install ICS firmware? I'm looking at the 3.14.605.5 Ice Cream Sandwich ZIP RUU (http://forum.xda-developers.com/showthread.php?t=1365654). How do I go about installing that?
Any help would be appreciated, thanks!
pumpkinsoftruth said:
I'm confused. I am S-ON (scared of brick), bootloader unlocked, and running CleanROM Pro 4.3. I want to update to the newest firmware and then the newest version of CleanROM. Do I have to re-lock my bootloader in order to install ICS firmware? I'm looking at the 3.14.605.5 Ice Cream Sandwich ZIP RUU (http://forum.xda-developers.com/showthread.php?t=1365654). How do I go about installing that?
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
yes, you need to lock it back up then apply the ruu.
or, take the path of awesome, and s-off that bad boy. what i'd actually do is install the latest leak RUU, s-off from that platform, then install amon-ra and whatever rom you want. that way your bootloader will already be upgraded, and your radio files. as new leaks come out you'll be able to apply radio files and kernels independently.
tspderek said:
yes, you need to lock it back up then apply the ruu.
or, take the path of awesome, and s-off that bad boy. what i'd actually do is install the latest leak RUU, s-off from that platform, then install amon-ra and whatever rom you want. that way your bootloader will already be upgraded, and your radio files. as new leaks come out you'll be able to apply radio files and kernels independently.
Click to expand...
Click to collapse
Ok, so...
1. Re-lock Bootloader
2. Install latest RUU
3. Unlock Bootloader and Root
4. S-OFF
5. Install Amon-RA
6. Install ROM
Sounds simple enough. Thanks.
Ok so I've taken your advice and removed setcpu and installed the one recommended in the post however is there any way to also monitor battery temp that won't interfere with things the same way setcpu does?
Sent from my ADR6425LVW using XDA
pumpkinsoftruth said:
Ok, so...
1. Re-lock Bootloader
2. Install latest RUU
3. Unlock Bootloader and Root
4. S-OFF
5. Install Amon-RA
6. Install ROM
Sounds simple enough. Thanks.
Click to expand...
Click to collapse
Step 4.5, install the patched hboot they offer you!

Don't Panic -- Please Read First, includes troubleshooting guide

This Guide has been written to aid users both old and new as a generalization of how the entire process of phone customization works. It is useful and relevant knowledge that will aid in the process of unlock, root, flash, and recovery. This is not a tutorial on unlocking your HBOOT, nor is it a tutorial of how to root your phone. It is a list of things you should know before, during, and after you complete the process. Below is everything I could think of to help guide you as you attempt to obliterate unlock your phone. There are risks involved and you may end up with an unusable device, this is not to be taken lightly. However I have included a basic troubleshooting guide as well. Should you run into trouble, it lists some of the most common issues. If all goes well then congratulations on unlocking your device.
ROOT This is a term used for everything here. Basically there are areas of your phone that are locked out. Root gives you admin or superuser privledges that can be used to modify things like build.prop or app data that you could not normally access. Typically during to root process an app is installed on your phone that governs which apps are given exclusive superuser privileges to modify your system. Superuser by CHAINSDD and SuperSu by CHAINFIRE are the only two apps I'm aware of.
S-OFF Security off, Basically the Holy Grail of Android customization. This disables the security allowing you to directly modify the NAND memory of your device. This in turn allows you to apply patches, device drivers and other niceties not normally available. This is why developers work tirelessly to enable S-OFF (Be sure to thank them for their amazing work).
HBOOT - This is your boot loader and is very similar to the BIOS on a PC, it basically performs POST (power on self test). It is responsible for flashing official software releases, enabling FASTBOOT and is basically the bouncer outside a club. This is what initially stops you from flashing unsigned code to your phone. OEMs have begun offering tools to unlock your boot loader and enabling the use of fast boot. Examples include HTC DEV Unlock, Samsung Odin, and Motorola's Unlock My Device.
Note: Depending on the security of your HBOOT you may or may not have access to the boot partition. Best example would HTC's HBOOT software. Unlocked it only offers access to FASTBOOT which in turn allows for recovery and flashing of ROMs. It does block flashing radios and other firmware
What does upgrading your HBOOT do? It adds support for new hardware (future phones) or fix bugs (break any chance you have of S-OFF, it may also bed your significant other but I have yet to confirm)
Should I upgrade my HBOOT? If a new firmware is released they may contain bug fixes, new radios, or newer versions of Android. If you want S-OFF and have yet to obtain it, no. Developers may find an exploit that can be used to obtain S-OFF. If you are stuck with S-ON and are waiting for S-OFF, again the answer is no. Developers may find an exploit to obtain S-OFF. If you don't care about obtaining S-OFF and you want to update your firmware, flash new radios, or simply want the bug fixes then this is the only option you have while S-ON if you are running stock. The only real benefit comes from what you can not flash with S-ON, basically radios or update for various drivers.
What does downgrading my HBOOT do? It falls back to the previous version of HBOOT, in some cases developers have released tools to downgrade to a previous HBOOT allowing users to then exploit the older boot loader and achieve S-OFF. Some people with S-OFF will upgrade but there is no real benefit, it often causes more problems with ROMs. They then attempt to return to previous HBOOT (very real potential for bricking your phone)
How do I upgrade my HBOOT? By installing an OTA or by using official ROM Upgrade Utility (RUU) To my knowledge there is no other method for upgrading HBOOT
Why do I need to downgrade HBOOT? As of right now, you don't. Do not trifle in what you do not understand.
Does rooting my phone require a certain HBOOT? Root is not dependent on HBOOT
Help, I upgraded my HBOOT and lost root! HBOOT has nothing to do with removing root, the RUU replaced your ROM with one that doesn't have superuser privileges.
RUU ROM Upgrade Utility, this is used to update your phone or revert it to a OEM factory state. The most common use of RUU in the community is to restore the original recovery and or re-enable S-ON
RECOVERY A very small type of operating system that resides on a part of your phone that is separate from Android. It is used by OEMs to install official OTA updates. Developers have created custom recoveries such as CWM, Amon Ra, and TWRP that allow a user to flash unsigned ROMs to the phone allowing for a greater degree of customization not offered by the stock operating system.
Nandroid Also referred to as a system back up. This is a copy if your phone's current system state. It creates duplicate images of your kernel and system including system settings, apps and app data, userdata, and or any mods. First and foremost, this is the most important thing to do after you flash recovery and before you flash a ROM. Should anything go wrong during the course of flashing a new ROM package (ROM/Kernel) and or should you wish to return to a stock state, restoring a Nandroid is the easiest and most effective way. Always be sure to back up your current system state prior to flashing a new ROM and or Kernel.
Note: Using Flash Image GUI will replace kernel from within OS. Be sure to create Nandroid before using this app to flash a new kernel.
ROM A package consisting of a boot image (kernel) and a system image (AOS or Android Operating System, I will now refrain from calling it AOS in fear that Apple may ruthlessly try to sue me for infringing on such a broad generalization to an operating system). ROM broadly refers to all of the phone's software. A custom ROM is any ROM that is modified from stock OEM or AOSP (for good measure, Android Open Source Project)
AOSP vs STOCK
AOSP Pure untainted Android OS maintained by users who want a clean open source mobile OS that is available for everyone. This is the base for ROMs like CM10 or Kanged. This is also the starting point for all OEMs
STOCK A build of Android that has been customized by an OEM. At first manufacturers used the opportunity to build custom skinned versions of Android. They supplied custom apps which they packaged into the ROM separate from the apps available in the market as a means to include exclusive features. This started a fierce competition between manufacturers who began making radical changes to the lowest levels of Android, including the kernel and framework. This led to slow, unreliable devices (frustrating for many developers who only have one real world device) that may have great hardware but poor software. In order to satisfy carriers OEMs may remove features or add many unwanted features. The most prominent issue stemming from this practice has been the Carrier IQ debacle. Roms like Venom and Mean use stock as their base.
Note: The most recent changes done by HTC and other OEMs are so extensive that they now offer their own SDK (Software Development Kit) for app developers to be able to write applications that are compatible with their framework
Kernel It is the layer between software and hardware. It allows the hardware and software to communicate with each other. The kernels must match the ROM Base and Version. Sense with Sense, AOSP with AOSP, ICS with ICS, Jelly Bean with Jelly Bean
CPU Governors A CPU Governor controls the frequency of the processor in response to the workload placed on it. If your phone supports multiple forms of governing, You will have the option to choose how it affects the performance and battery power consumed.
On Demand Pretty much the standard governor. The way it work is by ramping up the frequency to max in order to ensure responsiveness and then sampling the work load and scaling down the frequency to match. This is done by setting maximum frequency when the CPU is busy and gradually scales down as CPU reaches idle.
Interactive Governor Similar to On Demand, Interactive will dynamically scale the clock frequency as the workload demands. This is where the similarities end however. Rather then ramping clock speed to max when CPU is busy, interactive determines how to scale the CPU as it comes out of the idle state. When the CPU leaves idle, the governor sets a timer (pre-set by the developer). If the CPU use is intensive between leaving idle and timer expiring, governor will assume the system is under clocked and ramp to max frequency. It is better suited to handling intermediate clock speeds. Think of this as a faster, smarter On Demand
Performance I got a fever, and the only prescription is more cowbell! This sets the min frequency to the max. Your phone will burn, your battery will spring a leak, and you will see insane benchmark scores. This is obviously not a day to day solution.
Power Save Is anyone home? This will set you max frequency to your min. What a bore.
User Space This allows the user to set the frequencies. Better suited to the more advanced users
Input/Output Schedulers Determines "who goes first" by assigning which operations go to the storage volumes.
NOOP Scheduler This scheduler works on a sort of "first come, first serve" basis and will implement request merging. Its best for solid state drives and good on DB systems. It uses the least amount of CPU cycles per request. The one flaw I can see straight away is "less cycles = less performance"
Deadline Scheduler Used to minimize latency, it reserves five queues and schedules all I/O operations accordingly. This is an aggressive scheduler that runs at near real time speed. It is great for reducing latency and like NOOP, works best on solid state drives, db systems, and reduces latency in any I/O request. When system becomes taxed, this scheduler becomes very unpredictable.
Completely Fair Queue Scheduler This scheduler is scalable per I/O Queue, it distributes I/O bandwidth to all I/O requests fairly and equally. It helps maintain balanced performance through out and is great for multiple processors. The problem is when too many requests are competing for bandwidth, performance degrades.
Simple Input Output Scheduler This is as plain as it gets. No priority queues, no reordering or sorting requests, and the most basic merging. Minimum latency and low overhead, this is a simple and reliable scheduler.
BFQ Scheduler I would rather not risk getting into trouble with this acronym, lets just say the B is for brain and the F is a no-no word. I have not really used this scheduler but it's supposed to be good for USB data transfer, high definition video recording, video streaming, and is a fairly reliable scheduler. In my personal use I didn't get very good results.
MD5 It is basically a finger print for files, the developers use this to help regular users verify the integrity of the file. Most recoveries already support MD5SUM to prevent users from flashing corrupt files. Always verify the MD5 of any Kernel or ROM before flashing it to your phone
How to verify MD5 Hash
In Windows Like most useful utilities in Windows this is not supported, you can download a small utility that will load the file and display the Checksum Hash needed to verify.
In OSX Open a terminal and navigate to the folder your ROM is in and type md5 filename.ext
In Linux Again open terminal, navigate to folder and type md5sum filename.ext
In Android Open a terminal emulator, navigate to folder and use the same command used in Linux. Not surprising as Android is Linux but really neat! There are also apps for checking MD5 Hash Sum
Crossplatform Download managers and manager extensions for browsers like Firefox and Chrome may come with Checksum built in
Recovery As stated, most if not all recoveries will verify checksum hash. It is still good practice to verify by other means to avoid a bad flash
ROM Downloaders I don't really trust these or any large download on Android, sue me. Downloader apps should have a means to verify hash
NAND or N(OT) + AND Named after its basic operating principle, it is a form of non-volatile flash memory. Devices such as USB drives, cameras, mp3 players, and cellphones use NAND to store necessary firmware/software needed to operate. On Android phones the NAND memory is what holds all the information that powers your device. It is divided into separate partitions that are used to store firmware, the kernel and the system along with any other information such as contacts and cached data.
The Partitions are as follows
BOOT This Partition holds the HBOOT and Kernel and as the name suggests, is responsible for the allowing the phone to start. This is the most important Partition in your NAND memory.
SYSTEM This Partition is what holds our beloved Operating System. It contains the entire Android Operating System and the apps that come preinstalled on our phones.
RECOVERY Recovery can be thought of as our alternative boot partition. It holds the advanced recovery console that we need for flashing our phones.
DATA Also refered to as user data. This partition holds our contacts, messages, apps, and settings.
CACHE This is for the temporary storage of frequently used app components and frequently used data.
MISC This contains various bits of information like CID (Carrier or region identification), hardware configurations and various hardware/system settings.
SD_EXT Not to be confused with the Ext-SD shortcut on some phones (a way to access the external SD) This is not a standard Partition, it is an additional partition stored or your SD card that acts as another data partition. This allows you to install apps on your SD card and store data relative to the apps installed.
ADB Android Debug Bridge, it is used for development purposes but it has its usefulness
adb push This allows you to copy a file or directory to a phone
adb pull This allows the opposite, copy a file or directory from the phone
adb sync Copy host - phone if there are any changes present
adb logcat View phone log
adb install [ -l ] [ -r ] < file name > Push package file to phone and install it (-l means forward lock the app, -r means reinstall the app keeping its data)
adb uninstall [ -k ] Removes app package from phone (-k means keep data and cache directories)
adb reboot [bootloader] Reboots phone into the bootloader
adb reboot [recovery] Reboots the phone into the recovery
FASTBOOT A command line interface that can be used to directly flash the file system in Android, it is quite possibly the most reliable method to use if you know what you are doing. HBOOT must be unlocked (OEM or S-OFF) to have access to FASTBOOT
fastboot devices List all connected devices/phones
fastboot update Flash/re-flash a phone from update.zip
fastboot flashall Flash boot, recovery, and system
fastboot flash Flash a specific partition (partitions are boot, recovery, system, cache, and userdata)
fastboot erase Erase specified partition
fastboot reboot Reboot phone normally
fastboot reboot-bootloader Reboot into bootloader
fastboot -w Erase cache and userdata
fastboot oem lock Relock the boot loader
Flash Image GUI Created by member joeykrim, it is an Android app used for flashing recoveries and kernels from with in Android ROM. This is an easy to use tool for OEM Unlocked (S-ON) users to replace/update the kernel and or recovery before rebooting into recovery to switch ROMs. I have not used this myself so I can not determine how safe it is. Always verify MD5SUM
HTC Dumlock Created by TeamWin as a means to flash phones with OEM Unlock (S-ON) on HTC devices with HBOOT that do not allow for boot partition to be flashed. It is built in to TWRP, TeamWin also offer a Universal Dumlock solution compatible with other recoveries. It is probably the safest method for new users despite its seemingly complex nature. It is installed from recovery and run from within Android similar to Flash Image GUI but does not flash kernels. It makes a back up of your boot and recovery and then it takes the back up recovery and writes it to boot from within OS, your phone will then reboot (some phones must reboot manually, do not boot to recovery). From here on the recovery is running from within boot, you must then restore boot and then you will be allowed to flash a ROM like you would if the phone was S-OFF. Be aware that this is not the most ideal method as it writes to your boot partition 3 times (recovery, then restore boot, then kernel). Still this is the most flexible method for new users.
Uniflash Created by member MihailPro, this utility is a veritable swiss army knife of Android customization. It is basically several tools rolled into one. It supports and automates adb, fastboot, image editing/creation, manipulation of file system, back up and restoration of NAND partitions.
Features:
Flash
flash core (My guess is this is the flashall command; boot, system, recovery)
flash recovery
flash splash
flash radio
flash official and custom firmware (updates, patches and zip files)
Modify
edit Build.Prop
remove bloat
install or remove custom applications
copy to and from the device (internal, external memory) with the option to delete files
wipe user data, cache and perform factory reset
Image Creation
Basically back up and recovery
Note: This application is not compatible with HTC Sync, in order to use it please uninstall sync. Those of us with HBOOT 1.15+ still can not modify certain aspects of the memory but this application should at least make it easier to fastboot flash kernels, recovery and or ROM
PRI Product Release Instruction, the protocol used for the transmission of voice and data across Sprint's cellular networks. It may be updated from time to time to improve battery life and/or performance. It will also be updated when any drastic changes are made to the network. This directly affects the performance of your phone's voice and data
PRL Priority/Preferred Roaming List, It is a database used primarily by CDMA networks. It provides a list of network identifiers(service providers), wireless bands, and sub bands used to select the best service for roaming (example of bands/sub bands: PCS wireless band is 1850mhz to 1990mhz, divided into 6 blocks I believe. Sprint uses 1900, Block G if I'm not mistaken). Rather then giving you the best and most reliable option, the carriers choose which service providers to use (they have roaming agreements which help keep company costs down).
NV Non volatile memory, it contains info for MEID/ESN/EVDO and other credentials.
Radios These are basically drivers for the radios on your phone (basically firmware) They pertain to CDMA/EVDO, WIMAX, LTE, BLUETOOTH, WIFI and even NFC. They may be updated with patches or bug fixes to improve battery life and or performance.
Note: The only means of flashing new firmware on S-On unlocked devices is by using official HTC software
Basic Troubleshooting
**Please take the time to read all the relevant info I have posted prior to reading the troubleshooting section. I promise it will help you to better understand your phone and that is the entire purpose of this guide**​
Note: To those of you with CWM Recovery, it is recommended that you use TeamWin Recovery as it is better suited for our phones.
Brick This is a very serious problem, your device is catatonic and will not respond to the usual methods of power on/off or sim-pull. In some cases the phone comes back when the battery dies and is recharged, this isn't very often. There are un-bricking tools written by OEMs when they screw up (Samsung / Motorola) and there are tools written by developers working on S-OFF. They notice a very real danger and will supply the tool just in case (this is not possible in all cases). Bricking can and will be permanent in many situations
Boot loop There a different kinds of boot loop situations (also referred to as soft brick, please do not cry brick in the forums if it is a boot loop) the most common are a mismatch of kernel and ROM.
Help, my phone is stuck in a boot loop or my phone is stuck on HTC! Not a problem at all. Hold down the power button and continue to hold it, the capacitive buttons will begin flashing and phone will reboot. After the screen turns off let go of power for one second and the press and hold power and volume down to boot into the boot loader. This is known as a simulated battery pull. HTC built this in as a fail safe to reboot your phone, and it gives us a chance to jump into the boot loader should anything go wrong. Once you have successfully made it to the boot loader read through these forms of boot loop to understand what went wrong.
Known forms of boot loop
Generic Boot loop You have a working recovery and now you have installed your first ROM. There's just one problem every ROM you try boot loops but if you restore your back up and it runs fine. This is common when you haven't taken the time to wipe your phone before you flash. You can use a wipe script to clean your phone or you can systematically wipe Dalvik, Cache, Factory Restore, and then wipe System. Now you can flash your custom ROM (HBOOT 1.15+ requires you to flash the kernel separately)
Help my phone won't boot past the splash screen similar to a generic boot loop, the most common fix is to wipe the phone before flashing your ROM. Wipe your dalvik and cache, the factory reset and wipe system. You can now flash your new ROM
Kernel Issue You have flashed a kernel that may be corrupt, originate from a different base, or is just not supported by the ROM (not really the case these days, most developers are willing to share tweaks and custom code) The result is a phone that boots to a black screen and will hang or reboot.
Note: HBOOT 1.15+ requires you to flash the kernel separately, all relevant info to do so is in this guide.
ROM Issue The kernel boots and luckily the ROM takes to the kernel but something in the kernel does not agree with your ROM. The result is a phone that will boot to android and promptly reboot.
Missing ROM Due to a misunderstanding, you have already wiped all ROM data from phone (cache, dalvik, and system) and fastboot flashed the kernel. Now phone hangs on HTC boot screen and will not load Android. Only the kernel has been flashed, the screen hangs because there is no OS to load. Fear not, return to recovery and flash the ROM package that your boot.image originated from. Now select reboot to system and wait for your phone to restart. The kernel will boot, your OS will load, and all will be right with the world.
Update.zip or update pmg.zip This is a doozy, the rewrite didn't take and you no longer have a working kernel or system image, phone will keep booting to boot loader. If you updated using fastboot this will be less frustrating then if it was placed on the root of your phone/SD card. If fastboot method was used just jump into recovery and flash a working ROM package or restore a back up. If updating from boot loader, remove the SD card and delete update. The boot loader will continue to automatically read update and flash it until you do so.
Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you.
MISC
Help I just flashed the latest *insert ROM here* and my apps wont open (force close) This isn't the end all solution, but in many cases you just boot into recovery and select fix permissions. If you still have apps force closing and you know its not from the market, you may have to boot recovery and wipe the system and data, you will then need to re-flash the ROM
Help I flashed a new ROM/update/script and now I can't access my internal/external SD card Its OK, the SD card has been corrupted but you can reformat it with recovery itself or by using recovery to mount the card and formatting it by PC
Help the internal card isn't recognized by recovery or PC! (This is rare so make sure before attempting this fix) You're card is beyond a simple reformat, the physical address linking the card and or entire card is corrupt. Don't panic, you have to start clean. Back up the info on you external or remove it, make sure you have a ROM available on your PC. Go into recovery and repartition your phone, this will wipe all memory. You then load up a working ROM (a bad back up may be responsible or just reintroduce the problem), after you have flashed the ROM (HBOOT 1.15+ must fastboot kernel, unless S-OFF) go ahead and boot into android and restore your apps.
Help I repartitioned my phone and now I'm having trouble with my apps Not a problem, go into recovery and fix permissions.
My power button is broken! While I really don't recommend continued flashing of your phone without a power button, you can use built in menu options to reboot to recovery or adb reboot to recovery and or adb boot to fastboot.
Note: In the event that recovery is somehow damaged, phone may boot to boot loader depending on the state of your system. To the best of my knowledge, there is no way out if power button is damaged
Help my power button is broken and I'm stuck in the bootloader without Rom or Recovery Without the power button you can not choose recovery from the menu, so even if you flash TWRP you are stuck in bootloader. Flash recovery normally so that you have it after the problem is fixed. (Type fastboot flash recovery twrp.img) Now flash recovery again, only this time you will flash to boot. (fastboot flash boot twrp.img) This is a workaround to get into TWRP. Now we reboot the phone and flash the rom. (Type fastboot reboot) Wipe the phone as you normally would. (Dalvik, Cache, Factory reset, System) Install a Rom that has a kernel installer and reboot.
I can't seem to get my GPS to lock onto my location You can try using an app called GPS Tools, it will clear any data and reset GPS
How do I check to make sure my ROM/Kernel isn't damaged? Open zip file prior to flash or verify MD5 Checksum Hash
How do I check MD5? Read my section on MD5 verification
How do I flash ROMs? You can use Regawmod but I recommend you use HTC DEV Unlock. The basic process for this is simple. Register to HTC Developer website, go to unlock device and select other. Follow the simple instructions to enable adb and request token(Its a unique identifier for each phone). The website will then ask for token and send an email with further instructions. Once you have unlocked the boot loader you will now have access to fastboot. You have 2 methods of flashing recovery, you may fastboot flash the recovery image or use the update zip provided by TeamWin (Make sure the zip or image is compatible with your phone and verify MD5 sum to ensure no corrupt files are flashed). Once recovery has been flashed, its best to boot into recovery and make a back up of your phone's current state. Now before attempting to flash any ROMs, boot back into stock Android and download Goo manager from the market. Once installed, open app and from the menu select install open recovery script. This will ensure you have the latest recovery incase the one you just flashed is out of date. It will also enable you to use yet another alternative method to reliably flash your phone. As always, please read all relevant information before you attempt to unlock or flash your device. There are guides to help you posted on the forums. Good Luck!
Note: HTC Device Drivers must be installed prior to using HTC Dev Unlock, it should be covered in the HTC's unlock instructions.
Help the RUU failed and my phone is stuck in boot loader Try running it again or failing that, flash twrp in fastboot, then flash a kernel from which ever rom package you wish to flash and flash rom in twrp. If you really want to update it would probably be better for you to flash a stock rom with a stock recovery and perform an OTA update. If you relocked your boot loader, just flash the unlock_code.bin which you can get by unlocking through HTC DEV
Help my Android has super ceded Isaac Asimov's Three Laws of Robotics You gave it root, what did you expect to happen. It's the ghost in the machine man, Sky Net has to happen eventually.
So a brooding teenager with a hatred for machines really is our only hope for survival? God no, an emo teenager is never the solution
I think this is it for the most part, everything here should help most users troubleshoot their phones by themselves.
Thank you thank you thank you
Oh yea FIRST lol
Sent from the depths of hell
---------- Post added at 01:13 AM ---------- Previous post was at 01:07 AM ----------
Btw nice write up suggestion if i may would be add link to my flashung thread that also has rx's link to his thread about everything just a suggestion
Sent from the depths of hell
didnt I shoot you, damn those incredible recoveries they save just about anything if you know how to use them. Also, I believe that post has inevitably given me some form of carpal-tunnel. That or I'm just tired of typing typing typing. ALSO, I thought about linking the guides but that would make it more of a tutorial style and I clearly state it is not a tutorial, all the relevant information is on XDA or linked by other members
om4 said:
didnt I shoot you, damn those incredible recoveries they save just about anything if you know how to use them. Also, I believe that post has inevitably given me some form of carpal-tunnel. That or I'm just tired of typing typing typing. ALSO, I thought about linking the guides but that would make it more of a tutorial style and I clearly state it is not a tutorial, all the relevant information is on XDA or linked by other members
Click to expand...
Click to collapse
Very true well sorry bout carpel tunnel and all that lol very informative tho if used that is
Sent from the depths of hell
These people better use it lol, I some what ignored the gf to write this and I suspect she will be forgoing all extra-curricular activities in retaliation
I've been a bit confused on this: If I have S-OFF already, flashing a new RUU isn't going to be a problem; right? All I would have to do is re-install a rooted ROM to be back to where I am now (using CMX)?
if you want the new radios you can flash a zip that has the new radios without changing your hboot
om4 said:
And for the love of God clear your Wallet settings before you do anything. Menu > Settings > Reset Google Wallet. This can not be done anywhere else, you have been warned
Click to expand...
Click to collapse
Actually, I think it has been proven that you don't have to clear Wallet settings. I can't remember where I read it, but the problems when the phone first came out were problems with the app itself. I have flashed around 5-6 times with a full wipe without clearing the settings and Wallet works fine. I use it every day.
sofla2 said:
Actually, I think it has been proven that you don't have to clear Wallet settings. I can't remember where I read it, but the problems when the phone first came out were problems with the app itself. I have flashed around 5-6 times with a full wipe without clearing the settings and Wallet works fine. I use it every day.
Click to expand...
Click to collapse
well 1.22.651.3 did reset some of the phones that had bricked the secure element but not all of them, there are users who havent taken the new updates either so better safe then sorry. I added it as an after thought just to be safe but if its no longer a concern I can remove it
om4 said:
well 1.22.651.3 did reset some of the phones that had bricked the secure element but not all of them, there are users who havent taken the new updates either so better safe then sorry. I added it as an after thought just to be safe but if its no longer a concern I can remove it
Click to expand...
Click to collapse
No, probably best to leave it to let people know there was a problem, especially if for some reason they are still on the original software.
sofla2 said:
No, probably best to leave it to let people know there was a problem, especially if for some reason they are still on the original software.
Click to expand...
Click to collapse
Out of curiosity I looked at the change log for Wallet, all data is stored in the cloud now. So if I'm understanding this correctly, the secure element problem appears to have been bypassed
om4 said:
Out of curiosity I looked at the change log for Wallet, all data is stored in the cloud now. So if I'm understanding this correctly, the secure element problem appears to have been bypassed
Click to expand...
Click to collapse
That is a possibility
Arrghh!!?!?!! A developer called MihailPro just released a tool aptly named Uniflash that now makes a good chunk of this irrelevant. Oh well, it makes things easier for everyone here. I guess I could always add troubleshooting scenarios, unless a dev thinks of a way to automate that as well lol
om4 said:
Arrghh!!?!?!! A developer called MihailPro just released a tool aptly named Uniflash that now makes a good chunk of this irrelevant. Oh well, it makes things easier for everyone here. I guess I could always add troubleshooting scenarios, unless a dev thinks of a way to automate that as well lol
Click to expand...
Click to collapse
I will have to search for that. Also, Joeykrim's Flash Image GUI works great! I have used it on a few of my compatible devices. It takes 5-10 seconds to flash an img
Sent from my EVO using Xparent SkyBlue Tapatalk 2
om4 said:
Arrghh!!?!?!! A developer called MihailPro just released a tool aptly named Uniflash that now makes a good chunk of this irrelevant.
Click to expand...
Click to collapse
This still deserves a sticky.
Here is the link for more info on Uniflash, for those interested: http://forum.xda-developers.com/showthread.php?t=1859261
Added basic information on Uniflash, i was trying to add it earlier but my internet hates me
side note: those who took the time to read and learn about the info I posted will most likely be able to name the adb/fastboot commands this program automates...not very useful but it shows how easy these tools become when you understand the underlying process
Pretty good write up, but the key is whether people actually read it
Rxpert said:
Pretty good write up, but the key is whether people actually read it
Click to expand...
Click to collapse
thats always the case and a major problem with american education lol
Wileout suggested I post links to the tools and guides on how to root. I sincerely thought about it but theres a major issue with that, if I post links for tutorials or links for the tools I listed the reader is more likely to skip reading and go straight to the tool. Then we end up with more people asking for help
Posting links to other threads also puts the burdon on you for keeping the information up to date. I'd suggest leaving out anything that changes rapidly
Rxpert said:
Posting links to other threads also puts the burdon on you for keeping the information up to date. I'd suggest leaving out anything that changes rapidly
Click to expand...
Click to collapse
pfft...thats half the guide now and I wrote that thing at 2am this morning

[Q] Fastbooter won't run. No response. What do I do?

I need to get my phone back to the original stock Android since Cyanogenmod wrecked it by disabling the phone dialing keys, but I can't because fastboot isn't working. What do I do? Apart from the number keys not working, everything else on the phone is fine.
I've spent 15 hours on this so far and if it doesn't get solved I have to throw my phone in the trash. I've read every word and gone through every step of the how-tos linked below, over and over and over and over.
In the command prompt my commands and responses are:
fastboot devices -> 'fastboot' is not recognized as an internal or external command, operable program or batch file
fastboot-windows devices -> nothing happens
fastboot-windows oem unlock -> <waiting for device>
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
http://forum.xda-developers.com/nexus-4/general/tutorial-nexus-4-update-to-4-4-kitkat-t2534160
http://forums.androidcentral.com/ne...s-4-factory-image-restore-13.html#post3938684
Nexus 4
CyanogenMod 11.0 installer xnpq32p
Android 4.4.4
Do you HAVE fastboot on your computer and are in the correct directory to run the commands? Are you in the right mode on the phone? Check the Device Manager for driver errors?
But why not just update CM? There's obviously something that went wrong there because certainly CM doesn't usually have issues with the Dialer. Or just flash a stock rom in recovery.
es0tericcha0s said:
Do you HAVE fastboot on your computer and are in the correct directory to run the commands? Are you in the right mode on the phone? Check the Device Manager for driver errors?
But why not just update CM? There's obviously something that went wrong there because certainly CM doesn't usually have issues with the Dialer. Or just flash a stock rom in recovery.
Click to expand...
Click to collapse
Yes I had the tool.
Took half a day but I finally found Minimal ADB and Fastboot tool. Fortunately I sensed that everything must to be saved and extracted into one single folder, and the tool installed there - which the step-by-step guides either omit to mention or are vague about.
The dialer problem happened immediately upon installing CM, for the first time, the other day. So that was the latest version. Others have reported the same problem in the past and no one at CM replied. I'm leaving the country on a long trip and can't play with this any longer. I need a completely 100% working phone immediately.
If I had known that a so-called 'factory reset' does nothing of the kind, and getting back to stock is a such massive undertaking, I never would have considered messing with this.
fbtsrg said:
Yes I had the tool.
Took half a day but I finally found Minimal ADB and Fastboot tool. Fortunately I sensed that everything must to be saved and extracted into one single folder, and the tool installed there - which the step-by-step guides either omit to mention or are vague about.
The dialer problem happened immediately upon installing CM, for the first time, the other day. So that was the latest version. Others have reported the same problem in the past and no one at CM replied. I'm leaving the country on a long trip and can't play with this any longer. I need a completely 100% working phone immediately.
If I had known that a so-called 'factory reset' does nothing of the kind, and getting back to stock is a such massive undertaking, I never would have considered messing with this.
Click to expand...
Click to collapse
It's a factory DATA reset, not a restore your operating system option. It works exactly as it should, by removing user data and settings.
But for future reference, this is why you do a backup in recovery - so you can switch back in time of want or need.
times usbeae
es0tericcha0s said:
But for future reference, this is why you do a backup in recovery - so you can switch back in time of want or need.
Click to expand...
Click to collapse
- What do you mean by "backup in recovery"? What is that, and where is it?
- What do you mean by "switch back"? Switch back to what? The original state precisely as it was when I opened the box? Because ideally - if I ever root again - that is what I would like to be able to do in a simpler way than removing a bunch of drivers then installing new ones then enabling and disabling and re-enabling USB debugging then running ADB and fastboot and typing commands.
I guess I'm not clear on how it's possible to install Cynanogenmod by downloading an installer, click on two or three things, bam you're done - whereas removing it is an order of magnitude more complicated.
fbtsrg said:
- What do you mean by "backup in recovery"? What is that, and where is it?
- What do you mean by "switch back"? Switch back to what? The original state precisely as it was when I opened the box? Because ideally - if I ever root again - that is what I would like to be able to do in a simpler way than removing a bunch of drivers then installing new ones then enabling and disabling and re-enabling USB debugging then running ADB and fastboot and typing commands.
I guess I'm not clear on how it's possible to install Cynanogenmod by downloading an installer, click on two or three things, bam you're done - whereas removing it is an order of magnitude more complicated.
Click to expand...
Click to collapse
Well I would never have reason to use an installer (I prefer the "old school" manual methods) but CM couldn't install without a custom recovery, so not really sure how you don't know about that...? You can get to recovery from the bootloader screen accessed while off from Power + Vol Down for a few seconds. In recovery you can flash another rom or a stock based one. If you are S-On, you still need to fastboot flash the boot.img though. Have you checked your Device Manager for driver errors? I never have luck with this vintage of HTCs in fastboot on my Win 8.1 PC. I never have issues in Win 7 though. I actually keep a POS WIn 7 PC around just to work on HTCs.
So yea, the installer is helpful in making it simple to install, however, since you went the "easy" route, it seems like you missed out on a lot of reason to read through some threads and get some idea on what exactly you're doing and what's been done to the phone. It's best to walk before you run.
This thread may help you with your fastboot issues
http://forum.xda-developers.com/showthread.php?t=2277112

Problems understanding how to Root

Maybe the problem is that I don't know how to properly ask for what I want/need. First off, I am new, so let's pretend I know nothing about modding phones. Second, what I am trying to achieve is the following:
Marshmallow OS or newer (I have lollipop and I highly dislike it)
Complete removal of all AT&T software/bloatware from my M8
Ability to try out different ROMs (are those the same thing as operating systems?) like cyanogenmod.
Those are the highlights to my endgame.
I have found there are several steps to this, and it seems like each step has at least one prerequisite or sub-step and I get overwhelmed when reading up on how to achieve the above goals. Feels like I'm doing taxes for a poorly run business. Apparently I need TWRP on my phone. No clue why or what it does. In order to install it, I need to have root access or a previous version of TWRP already installed, or I need to install the SDK tools package, and from that, only install fastboot and adb. Then after that I need to already have some type of drivers on my PC for that to be useful. Like I said, it is overwhelming to someone who does not know all of the lingo. Especially when I know that if I mess up at certain intervals, I could very well turn my phone into a shiny paperweight or small cocaine tray. Anywhere I have read up on this, when it says download/install _______, I cannot determine whether that means download/install on my PC, or on my phone, bc it doesn't specifically say what goes where in every instance. To make matters more difficult, I do not have an internet connection other than on my phone. Anything that needs to go on my PC, I have to download it to my phone first, then transfer it over, then install it. I asked once for a step by step tutorial or a link to one, and I was given something that was just as confusing as what I have already found. These tutorials seem to be written for ppl who know a lot by ppl who know a lot. I am not one of those ppl. I am a green noob, still wet behind the ears. I apologize in advance for not knowing, but I am just not at the level where I can guess which things go where and If I temporarily render my phone unusable, I won't be able to easily go online to find the fix, nor will I be able to download anything else, if needed. Would greatly help me if I had a list of ingredients needed before I begin, and a sequence, much like a recipe for a cake. Again, I apologize for not knowing, and I'm sure all of you reading this were, at one point, uneducated on the matter. Thank you for any advice and/or reading my TL/DR post.
See my responses below, in red font:
Damagj said:
Apparently I need TWRP on my phone. No clue why or what it does. In order to install it,
TWRP is a custom recovery, and what that is, is explained in "that" thread I linked you to: https://forum.xda-developers.com/showthread.php?t=2744194
Think of TWRP as a kind of small installer program and backup/recovery tool. You need it to flash custom ROMs, and you can also use it to backup the current ROM. It's not used within the Android OS, but rather you can boot into it separately. Which is obviously handy, if for whatever reason you can't boot to Android OS, and need to "recover" (restore the OS).
I need to have root access or a previous version of TWRP already installed, or I need to install the SDK tools package, and from that, only install fastboot and adb. Then after that I need to already have some type of drivers on my PC for that to be useful.
Don't go by the install instructions on the TWRP website, they are not device specific (to the M8) and may misguide you (every Android device has it's own nuances).
To install TWRP, you need to unlock the bootloader. The bootloader is "locked" by default, which by definition means you cannot install a custom recovery. The following is a good step-by-step guide to unlock the bootloader and install custom recovery. Note, that you do not need to root, in order to install TWRP, or flash a custom ROM. So stop before you get to the step of root (flash SuperSU). Also, the version of TWRP you install should be current (3.1) or alternately 2.8.7 (which is a known "old reliable) version).
https://forum.xda-developers.com/showthread.php?t=2799796
Like I said, it is overwhelming to someone who does not know all of the lingo. Especially when I know that if I mess up at certain intervals, I could very well turn my phone into a shiny paperweight or small cocaine tray.
No, you actually can't. Your fear of bricking the phone (permanent damage) is unfounded. As with s-on, this phone is nearly impossible to brick. The phone is fully recoverable even if you screw up; since for what you describe, you are only touching a limited number of partitions (system which is the OS, and recovery). As long as you don't mess with "critical" partitions like hboot and radio, you can't actually brick this phone. And those partitions are actually protected, and you can't modify them even if you wanted, unless you s-off. So all the more reason to stay s-on, as I described in the other thread you posted in here: https://forum.xda-developers.com/showpost.php?p=74107487&postcount=100
To make matters more difficult, I do not have an internet connection other than on my phone. Anything that needs to go on my PC, I have to download it to my phone first, then transfer it over, then install it.
but I am just not at the level where I can guess which things go where and If I temporarily render my phone unusable, I won't be able to easily go online to find the fix, nor will I be able to download anything else, if needed.
That part is difficult. While possible, doing what you describe is somewhat risky with no other device for internet. At some point, it's almost inevitable for anyone tinkering these phones, that something will go wrong. Either you forget a step, or you can't boot for no mistake of your own, at all. Even having done this stuff for years, it still happens to be, once in a while. It just happens. So without a way to ask for help, or download files, you can get stuck in a bad jam. You'll need to have some backup plan, even if it's a friend or family, letting you use their computer as a last resort.
Click to expand...
Click to collapse
Stick with it. Keep reading up, and trying to learn the basic terms, concepts, tools, and methods. I know it seems overwhelming, but it will all start to make sense. You really can't (and shouldn't) try doing these things, until you have some basic understanding. You wouldn't ask someone to tell you how to tear the engine out of a car, without knowing how any tools work, or what any of the parts of the car are called.
I would also suggest you refer to my (AT&T M8) index thread. It has a lot of links and basic info, you may find useful: https://forum.xda-developers.com/showthread.php?t=2751432

Categories

Resources