Related
I'm just wondering, I purchased a phone on ebay (not knowing it was flashed/rooted). The boot animation says "clean rom" so after researching this site and the forums for this device, I see that it's probably a rom you guys are familiar with and it seems to be ICS based (from what I can see). With that being said, does this mean when they actually RELEASE the stock ICS that I probably won't get the update to my phone? Because I really would like to see what their stock version will be like. Can anyone answer that question or has it even been asked before?
you can't take the OTA rooted or while unlocked but you can flash the RUU once it gets posted after relocking your phone. hopefully by then we will have s-off.
mighty_markus12 said:
you can't take the OTA rooted or while unlocked but you can flash the RUU once it gets posted after relocking your phone. hopefully by then we will have s-off.
Click to expand...
Click to collapse
So does this mean I will no longer be able to receive updates to my phone with this "s-off" or what ever? That sucks, and I can't seem to follow the steps that have been given to get it back to a stock rom or "ruu" what ever THAT means. lol ****that moment when you realize you might look dumb or "newbish" for posting what you just posted****
Your phone has been hacked a little bit, and it's always going to have tell-tale signs.
The worst case scenario is that you have to manually install the next official update and manually relock the phone, which will always say "Relocked" in the boot menu. But if you do everything by the book you should be able to get it back to stock in every other way, including taking subsequent updates over the air normally.
If they get s-off working and you're willing to experiment, it may be possible to completely revert the phone to stock. But that's quite a bit more hackage in order to get your phone "unhacked."
cpurick said:
Your phone has been hacked a little bit, and it's always going to have tell-tale signs.
The worst case scenario is that you have to manually install the next official update and manually relock the phone, which will always say "Relocked" in the boot menu. But if you do everything by the book you should be able to get it back to stock in every other way, including taking subsequent updates over the air normally.
If they get s-off working and you're willing to experiment, it may be possible to completely revert the phone to stock. But that's quite a bit more hackage in order to get your phone "unhacked."
Click to expand...
Click to collapse
To be honest, the only thing I really want is to be able to get it stock on the basis of the apps, getting system updates etc. I'm not concerned with it having evidence of being "tampered with" "hacked" or "rooted". lol It already says "re-locked" The problem is the instructions I've gotten on here seem to go over my head. I might have to be walked through it like a little 3 or 4 year old being taught to sound out little words for the first time. lol Hey, I'm just saying..... No seriously though, I have a MAC and all of the instructions here seem to be based on having a PC
This can be done. But you're going to need to have somebody who knows what they're doing relock and reset your phone from the official ICS RUU after it's released, probably from a PC. There's nothing can be done before then.
cpurick said:
This can be done. But you're going to need to have somebody who knows what they're doing relock and reset your phone from the official ICS RUU after it's released, probably from a PC. There's nothing can be done before then.
Click to expand...
Click to collapse
So this means I'll need to basically need to take or send it to someone to get this done? I don't know why all of these instructions seem like their in spanish to me now, about 3 years ago I used to flash and unlock WM devices almost every other day. I guess I should've never stopped, but once the g1 came out and switched to android devices I stopped flashing and now I'm lost because I need to "tamper with" my phone again, but can't seem to get going at all. I mean SERIOUSLY, I used to flash WM devices so often that if a certain period of time went by without me finding a rom worth "flashing" I'd start having withdrawals. Now i'm feeling like an absolute IDIOT when it comes to getting into these android devices. I think part of that has to do with the fact that I only had PC's and now not only am I trying to tamper with android for my first time, but I only have mac computers as well.
Go to settings, about phone, software information, more, and write what your baseband version is.
http://forum.xda-developers.com/showthread.php?t=1417839
This thread may help you getting osx and fastboot going so you can relock and run an ruu. As was stated above, what is your baseband? If the previous owner flashed the leaked ics you will not be able to go all the way back to stock until either an official ics is released or the s-off tool is released. Good luck!
Sent from my ADR6425LVW using XDA
Unless you have issues, I would leave it as is for the time being. Take time to learn how to do all the stuff you need to do.
The custom ROMs really do make the phone better, you may find you want to keep it in the end. Battery life is much better on a good ROM.
When the official update comes out, we will have a new ROM based on the update within a day or two at most of the release anyway.
The baseband (the radio firmware) is also important. And unfortunately we can not downgrade to older basebands due to not having S=off. So if you are on the newest leaked version then you can run the old stock software.
BTW S=off (or S=on) is a security flag located in the firmware. S=on limits what parts of the phone you can flash and change. S=off gives you full access, it will allow you to downgrade as well. S=off also makes it easier to brick your phone because it does let you change software that is bootstrap essential, the baseband and hboot (sort of like BIOS) for example.
I separate the idea of bootstrap from boot. Most people associate booting with the OS, but bricking effects the firmware initializing the hardware that allows the OS to load and boot. So you get to see the old school term used.
Kennnny1 said:
http://forum.xda-developers.com/showthread.php?t=1417839
This thread may help you getting osx and fastboot going so you can relock and run an ruu. As was stated above, what is your baseband? If the previous owner flashed the leaked ics you will not be able to go all the way back to stock until either an official ics is released or the s-off tool is released. Good luck!
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
The baseband is 1.22.10.0310r, 1.22.10.0308r It also says clean rom 4.1. I don't mind waiting until an offcial ics is released, but I will I be able to receive THAT instead having to have a "dev equivalent" version is what I'm wondering....
It's like I said. Those radios are new, and part of a firmware upgrade that can't be completely backed out. Your simplest bet is to wait for the official ICS release, and then you (or someone more technical) can apply it manually. After doing that and relocking your phone, it should start to take updates automatically again. You'll also have the full factory-installed "bloatware" suite of software.
It's possible to downgrade all the other parts of your software manually back to the latest stock release, but it's expected that your current upgraded firmware version will continue to prevent you from taking OTA releases. It would be good training, actually, though you'll get better results and more support from a PC than on a Mac. If you figured out how to do all this, then you could get your phone back on the HTC software track yourself.
Depending on your flexibility, maybe you can find someone here you could send your phone to who can put it back on the official release track. But even they won't be able to put a permanent fix on it until the official ICS release comes out and somebody uploads it as a manually-installable package.
---------- Post added at 10:08 AM ---------- Previous post was at 09:29 AM ----------
EDIT:
So did the seller not mention on eBay that the phone had been customized?
Some of the responses lean toward telling you how to flash your phone for yourself. Is that something you'd have any interest in? Do you really want to go back to stock, or do you just want to see the difference?
Are you having any problems with the phone?
The custom ROMs are better, overall, but they usually have one or two bugs that you have to learn to live with. (Which is not to say that stock ROMS are bug-free, though the final versions of stock ROMs tend to be very, very stable.) But if you are on custom ROMs, then you're completely off the automatic update path, and everything will have to be done manually.
So unless you want to learn how to flash your own phone, the only way to get updates is to set it back to stock so HTC and Verizon can handle the updates for you. And therein lies the dilemma, because that in itself is something which must be flashed manually from where you're currently at.
(Oh, and you're probably going to end up losing any of your own customizations in the process, though the data on your SD card should be safe.)
cpurick said:
It's like I said. Those radios are new, and part of a firmware upgrade that can't be completely backed out. Your simplest bet is to wait for the official ICS release, and then you (or someone more technical) can apply it manually. After doing that and relocking your phone, it should start to take updates automatically again. You'll also have the full factory-installed "bloatware" suite of software.
It's possible to downgrade all the other parts of your software manually back to the latest stock release, but it's expected that your current upgraded firmware version will continue to prevent you from taking OTA releases. It would be good training, actually, though you'll get better results and more support from a PC than on a Mac. If you figured out how to do all this, then you could get your phone back on the HTC software track yourself.
Depending on your flexibility, maybe you can find someone here you could send your phone to who can put it back on the official release track. But even they won't be able to put a permanent fix on it until the official ICS release comes out and somebody uploads it as a manually-installable package.
---------- Post added at 10:08 AM ---------- Previous post was at 09:29 AM ----------
EDIT:
So did the seller not mention on eBay that the phone had been customized?
Some of the responses lean toward telling you how to flash your phone for yourself. Is that something you'd have any interest in? Do you really want to go back to stock, or do you just want to see the difference?
Are you having any problems with the phone?
The custom ROMs are better, overall, but they usually have one or two bugs that you have to learn to live with. (Which is not to say that stock ROMS are bug-free, though the final versions of stock ROMs tend to be very, very stable.) But if you are on custom ROMs, then you're completely off the automatic update path, and everything will have to be done manually.
So unless you want to learn how to flash your own phone, the only way to get updates is to set it back to stock so HTC and Verizon can handle the updates for you. And therein lies the dilemma, because that in itself is something which must be flashed manually from where you're currently at.
(Oh, and you're probably going to end up losing any of your own customizations in the process, though the data on your SD card should be safe.)
Click to expand...
Click to collapse
Well, I've kind of decided to just keep what I have. I don't have any issues other and it seems to run smoothly. What I REALLY want to see is what the official update will be like as being "stock released" when it comes out and was concerned that I might not be able to get the update because of the "clean rom" I have now being ICS based (as far as I can see). Other than that, I'm fine until then.
You really should consider leaving negative feedback if they ebay seller did not state in the auction that the phone was rooted and running a custom rom. If I sell a phone and im too lazy to revert it to stock ill ALWAYS state its rooted and what its running in the auction etc
mdunn1066 said:
You really should consider leaving negative feedback if they ebay seller did not state in the auction that the phone was rooted and running a custom rom. If I sell a phone and im too lazy to revert it to stock ill ALWAYS state its rooted and what its running in the auction etc
Click to expand...
Click to collapse
Good point, I mentioned it in the feeback portion and rated him low on the "item described accurately" portion
I would just wait til offiical ics is released. I am sure there will be instructions here on xda on how to relock and flash the new official ics ruu. It will involve downloading some files and entering items into command prompt from PC.
sent from my Rezound
stelv said:
I would just wait til offiical ics is released. I am sure there will be instructions here on xda on how to relock and flash the new official ics ruu. It will involve downloading some files and entering items into command prompt from PC.
sent from my Rezound
Click to expand...
Click to collapse
The problem is I don't HAVE a PC. It's already "re-locked" though. I just want to be able to receive the update without having to deal with any other flashing etc. But from what I was told, I should be able to since the current flashed rom is nearly stock (clean rom) and I'm already re-locked. But I guess we'll just see....
refuse2bstopped said:
The problem is I don't HAVE a PC. It's already "re-locked" though. I just want to be able to receive the update without having to deal with any other flashing etc. But from what I was told, I should be able to since the current flashed rom is nearly stock (clean rom) and I'm already re-locked. But I guess we'll just see....
Click to expand...
Click to collapse
seems like people are giving you information that is kinda all over the place.
Lemme try and help clear this up, since you are in a odd scenario.
You are running cleanrom 4.1 on a re-locked phone. For starters, cleanrom 4.1 is based off the current ics LEAK and is not an official OTA update. Chances are high you won't be able to get the OTA if the rom is not a stock rom, and also because chances are you don't have a stock recovery even though it is relocked. Since you are currently on the latest leaked firmware, not an official firmware, you can run the RUU for the phone and go back to stock. In your case, your kinda lucky with this, as you don't technically need a computer to run it. You would need someone to extract the PH98IMG.zip file from the RUU.EXE file for you to run when the OTA comes out through Hboot.
Be for warned, doing it like this, will wipe all data.
I would say you should run the leaked RUU on the phone, as since it is a beta testing Leak, you should still get the OTA, and that way the phone will think it is completely stock and get the latest update.
If you wanna do this, ask and we can help you.
nosympathy said:
seems like people are giving you information that is kinda all over the place.
Lemme try and help clear this up, since you are in a odd scenario.
You are running cleanrom 4.1 on a re-locked phone. For starters, cleanrom 4.1 is based off the current ics LEAK and is not an official OTA update. Chances are high you won't be able to get the OTA if the rom is not a stock rom, and also because chances are you don't have a stock recovery even though it is relocked. Since you are currently on the latest leaked firmware, not an official firmware, you can run the RUU for the phone and go back to stock. In your case, your kinda lucky with this, as you don't technically need a computer to run it. You would need someone to extract the PH98IMG.zip file from the RUU.EXE file for you to run when the OTA comes out through Hboot.
Be for warned, doing it like this, will wipe all data.
I would say you should run the leaked RUU on the phone, as since it is a beta testing Leak, you should still get the OTA, and that way the phone will think it is completely stock and get the latest update.
If you wanna do this, ask and we can help you.
Click to expand...
Click to collapse
Yes, I'm VERY interested, I'm not worried much about the data wipe, between what's backed up to my google account and my SD card, I'll be fine with a data wipe. My battery life is also HORRIBLE for some reason with this rom, but since I've not had it stock yet, I guess I can't REALLY say it's good or bad. But my Droid Bionic's battery life was at least twice as good as this phone's seem to be and I don't use it any more than I did the Bionic.
I will tell you right now the battery life will most likely get worse if you go to stock.
Now if the person who sold it installed a custom kernel rather than the one Scott includes in his ROM (scott makes clean ROM) then battery life could be worse than it should be.
Second, this is a 4.3 inch HD screen... it eats battery like a starving animal.
Third, try cleanROM developers edition (a very striped out cleaned up stock based ROM) or cleanROM senseless. I am running cleanROM developers edition and I get double to triple the battery life over stock.
Unless I actually use the phone... When I use it a lot, I do not get that big of a jump. When using the phone the battery life will be similar due to the screen and CPU use remains similar to what stock would be. (which you would expect, the screen will always use the same power, same for CPU) Its when the phone is in standby mode that you see the real gains. Because all the extra junk that is in the stock software is pulled out and isn't constantly running in the background, waking the phone, starting the cell radio to phone home, etc.
Senseless and the Developers edition have their quirks caused by removing so much of the stock sense based apps and functions and replacing with AOSP versions. Thinks like the caller ID not showing up on the screen until you unlock the phone because the sense phone/dialer can not talk to the AOSP lockscreen. Nothing major just different.
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!
UPDATE: The latest update still is safe. I just installed it and I am still s-off.
UPDATE: The update to Jellybean does not write the secure flag and this method is safe to apply the OTA update with this method and still maintain root access afterwards.
First and foremost, a couple disclaimers.
FIRST, YOU MUST BE S-OFF FOR THIS TO WORK. PLEASE DO NOT TRY THIS IF YOU ARE NOT ALREADY S-OFF.
SECOND, FOR THE OTA UPDATE 1.22.651.3 YOU WILL FOR SURE RETAIN S-OFF. ALTHOUGH HIGHLY UNLIKELY, HTC COULD POTENTIALLY MAKE YOU S-ON IN FUTURE OTA UPDATES. SEE HERE FOR MORE INFORMATION.
To obtain s-off please see this thread: http://unlimited.io/jewel.htm
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out. I don't really theme, mod, or do crazy things with my phone but still want root access. So, I decided since I was s-off, I would give this method a whirl. I am happy to report that I am s-off, with TWRP, fully rooted, and with installing the OTA update. I had a little hiccup but was able to solve that.
So, here is the process. This is kind of a hodge podge of different threads, ideas, devices, and versions of android so if I didn't give you credit, please let me know and I will put you in this thread.
Process for installing a stock recovery. I have already created some stock recovery files so see at the bottom of this post for the zip file that includes the stock recovery. If you wish to use these files, just start with step #10.
IF YOU CHOOSE TO JUST DOWNLOAD THE STOCK RECOVERY AT THE BOTTOM OF THIS POST, SKIP TO STEP #10.
Creating Stock Recovery File Manually
1. Install a stock recovery if you don't already have one.
2. To do so, get the RUU for the version you are running.
3. Run the RUU (don't connect to your phone at all)
4. Navigate to your temp directory on your computer (on windows 7 it is C:\Users\your_user_name\AppData\Local\Temp)
5. Find a folder that looks like it is in the following format "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX}" It might help to sort by date modified. The folder should have the current date
6. Inside the folder might be a couple other folders. Navigate through the folder to find a zip that says "firmware" or "rom" (mine said rom)
7. Extract the content to a folder in the same directory called rom
8. Navigate into the rom folder and find two files android-info.txt and recovery_signed.img. Copy those to a directory of your choice.
9. Send those files to a zip folder and name the file "PJ75IMG.zip" without the quotes. Make sure zip is only listed once. If you have file extensions hidden in windows yours will only say "PJ75IMG".
Installing the stock recovery, OTA, and regaining root
10. Place the stock recovery file on the root of your sd card
11. On your phone, head into settings and power and make sure the fastboot option is unchecked
12. Power down phone
13. Once phone is completely shut down, hold the volume down button and press the power on button while keeping the volume down button pressed.
14. It will boot into your hboot (verify it says s-off at the top or don't proceed) and find the file you placed on your sd card and ask you if you want to update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
15. Go to settings>check for updates and check to see if there is an update. Download the update. Once it verifies, click install now. It should install just fine.
16. Once you are up and running, download one of the dirty racun hboots. I used hboot 2.09 img found here. Follow the instructions on the unlimited.io website how to flash the hboot by using fastboot (flashing the zip doesn't seem to be working.
update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
17. Make sure usb debugging is checked under settings>developer options
18. Go download a su zip file. I used this one here and place it on the root of your sd card.
19. Go grab a custom recovery flashable zip (could not find the latest twrp zip) or img (I used TWRP found here. Take the image and place it in your platform tools folder for ADB.
20. Plug in phone while powered on and type in adb devices to make sure you are connected.
21. If you see a device type in
Code:
adb reboot bootloader
22. Your device will boot into your bootloader and you will see fastboot usb (make sure usb debugging was checked if you don't see that).
23. Then type fastboot flash recovery [filename] of the recovery img you downloaded. Once flashed, toggle with the volume up buttons to bootloader and then select recovery. This should boot you into TWRP
24. Once in recovery, install the su zip you downloaded in step 18.
25. Reboot and Enjoy!!!!
You are now rooted with the most current OTA update and all the goodies (radios, PRI, etc.)
This process should hopefully hold true for any future OTA updates if you are S-OFF. The only thing you will have to find is the current RUU to create the stock recovery. If this helped, feel free to thank! Go XDA!
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I don't know. So you don't have to wait at all? Or for the people that aren't accustomed to flashing ROMs or don't care to. I prefer this method for whatever reason and it seems just easier. Personal preference though. The beauty of android and their strong developer network is that it gives the users choices. I can take the OTA update as soon as it comes out and don't have to worry about waiting for anything. Just another method I guess.
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
msimindlessmsi2 said:
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
Click to expand...
Click to collapse
The update firmware is the part that hangs me up. I believe when it was back in the original EVO days that some people were having problems updating their PRI version and it screwed up some things with wimax. That is when I decided I would just accept the OTA to get everything they included in the update and then gain root access through this method.
Again, to each their own. Please try not to clutter up the thread with off topic items. Thanks.
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
im coming from the rezound, i just want the updated firmware! on my rez being s-off i could run ANY firmware ICS, or GB and then go back to whatever rom i was running. im wondering if im s-off, i should b able to do the same thing right.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
The devs state that so that they don't have to spend their valuable time troubleshooting because you didn't flash right. Its always best to do a full wipe, but not always required when flashing an updated version of the same ROM.
1) Nandroid.
2)Wipe Dalvik cache & cache
3) Flash
You retain all data.
If you have issues, then you nand restore and do a full wipe before bugging the devs
bpdamas said:
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out.
Click to expand...
Click to collapse
Lmao! You find that whole process "easier" than waiting for a day? I think it might take the better part of a day to do all that.
Sent from my EVO using xda premium
Thanks for taking the time to do a write-up OP!
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
Agreed.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Definitely agreed.
greyopaque said:
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
Click to expand...
Click to collapse
I know. This is exactly why I root and I can't believe there are so many people against this method. It seems very simple to me and I can have a stock recovery waiting to flash as soon as an OTA update comes out. Oh well.
Thanks for this info. I think I'm like you and not only like the stock experience and its benefits but also prefer diy when possible.
Of course I never seem to stay stock like you but I like doing the steps my self. To each their own is the beauty of android.
Go android!
Sent from my EVO
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
zounduser said:
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Click to expand...
Click to collapse
Very curious on this. Nothing in this method should affect this.
Robbie_G said:
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
Click to expand...
Click to collapse
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Rxpert said:
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Click to expand...
Click to collapse
That's fair, rooting and s-off could also inject malicious code. But so can ROM makers.
I think there's a difference between trying to be safe and being paranoid. If there is a way for someone to make money off of you/steal your identity, eventually they will try. I'm not suspicious of any of the current devs, but it's something we should maybe be more aware of. Look at all the warez Windows out there with malware built in to steal your information.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Totally agree. Its a good thing to learn in my opinion. I broke my Evo 4G, fixed it then rerooted it. Now on the 4G LTE got it rooted with custom rom. Love learning new things plus some of the good things that come with rooting and custom roms are worth it for me.
Ok I see that there are a couple of similar threads to this and I apologize in advance but I'm not sure exactly how to correctly interpret some of the answers on those threads...so I'm gonna start my own and see who can help lol. Once again I'm sorry if this new thread is considered obsolete by some or all.
I have a Motorola droid razr. Not the maxx just the standard razr. When I got my phone I started looking into rooting it after seeing one of my friends with a rooted thunderbolt. I successfully rooted my razr after doing a lot of research. I installed Titanium (not pro) and undelete. I'm fairly certain that I made a backup of everything on my phone shortly after installing Titanium Backup. Well through the course of tinkering around with my phone a bit I deleted certain files here and there that I considered useless or annoying to me that they were on my phone in the first place. Well when the upgrade to jellybean came out I tried to do a software update. It finishes, reboots my phone, then says the update was unsuccessful.
After some research I have realized that I probably deleted something that was important (lol yeah I'm an idiot) and so it wont let me update the software because of that. I realize that I could use titanium to restore those files but I have NO idea what files I deleted that were important. And I'm not all that comfortable with TB to just mess with it freely. TB has been something that I have used very little because I know I could probably cause some serious damage to my phone with it haha. I haven't done a factory reset because I know already that it wouldn't bring those files back.
If anyone can help me I would really appreciate it. I'm not a very technical person so I probably shouldn't have rooted in the first place but I tried my hardest to do the research first. Thanks in advance for the help everyone
vetchemh3 said:
Ok I see that there are a couple of similar threads to this and I apologize in advance but I'm not sure exactly how to correctly interpret some of the answers on those threads...so I'm gonna start my own and see who can help lol. Once again I'm sorry if this new thread is considered obsolete by some or all.
I have a Motorola droid razr. Not the maxx just the standard razr. When I got my phone I started looking into rooting it after seeing one of my friends with a rooted thunderbolt. I successfully rooted my razr after doing a lot of research. I installed Titanium (not pro) and undelete. I'm fairly certain that I made a backup of everything on my phone shortly after installing Titanium Backup. Well through the course of tinkering around with my phone a bit I deleted certain files here and there that I considered useless or annoying to me that they were on my phone in the first place. Well when the upgrade to jellybean came out I tried to do a software update. It finishes, reboots my phone, then says the update was unsuccessful.
After some research I have realized that I probably deleted something that was important (lol yeah I'm an idiot) and so it wont let me update the software because of that. I realize that I could use titanium to restore those files but I have NO idea what files I deleted that were important. And I'm not all that comfortable with TB to just mess with it freely. TB has been something that I have used very little because I know I could probably cause some serious damage to my phone with it haha. I haven't done a factory reset because I know already that it wouldn't bring those files back.
If anyone can help me I would really appreciate it. I'm not a very technical person so I probably shouldn't have rooted in the first place but I tried my hardest to do the research first. Thanks in advance for the help everyone
Click to expand...
Click to collapse
So does anyone have any suggestions??
im not sure about this particular phone but search for the SBF file for your phone model and how to use RSDLite. this is how to restore Motorola phones.
Sent from my HTC Glacier using xda premium
It's never a good idea to do an OTA update over a rooted phone.
You should just download a rooted stock ROM from the dev forum (a 4.1 ROM) and flash it via your recovery (flash the zip file) or another custom ROM, they have some good ones!
OR I would just flash stock THEN do the OTA update, because whatever rooting method you used (I don't have that phone so I'm not sure) probably replaced your kernel with an insecure one or your system.img so you're failing the OTA update.
orangekid said:
It's never a good idea to do an OTA update over a rooted phone.
You should just download a rooted stock ROM from the dev forum (a 4.1 ROM) and flash it via your recovery (flash the zip file) or another custom ROM, they have some good ones!
OR I would just flash stock THEN do the OTA update, because whatever rooting method you used (I don't have that phone so I'm not sure) probably replaced your kernel with an insecure one or your system.img so you're failing the OTA update.
Click to expand...
Click to collapse
this is a good point. i would only do the SBF if you can't get into custom recovery.
Sent from my HTC Glacier using xda premium
OP I moved you, here into your device forum Q&A for more visibility from actual users for your device. Thank you.
just try to flash a stock ROM using RSD, and then take the OTA update.
Sent from Motorola Razr XT910 With beatsaudio™ on ICS 4.0.4
gregeorgeraldo said:
just try to flash a stock ROM using RSD, and then take the OTA update.
Sent from Motorola Razr XT910 With beatsaudio™ on ICS 4.0.4
Click to expand...
Click to collapse
Ok I'm not gonna lie that sounds like a different language to me haha. I know I probably shouldn't have done all this without really knowing exactly what i was doing but I'm sure im not the first lol. What exactly is RSD and when I flash the razr stock ROM will it erase anything I already have save on my phone? Sorry I'm not the most intelligent when it comes to stuff like this haha
gregeorgeraldo said:
just try to flash a stock ROM using RSD, and then take the OTA update.
Sent from Motorola Razr XT910 With beatsaudio™ on ICS 4.0.4
Click to expand...
Click to collapse
Is this a good source and video that might explain this to me a little better? I havent posted 10 times so i cant use the link but its a video on youtube called How to use fastboot files to return Droid Razr back to Android 2.3.5! It's the first vid that comes up. has about 9,300 views and was posted 7 months ago. I think my RAZR was on ice cream sandwich (not gingerbread) but it should be the same i guess? Thanks in advance everyone
The reason I suggest just flashing a custom ROM thru your recovery is once you RSD stock then do the OTA you're just going to want to root again and maybe flash a better custom ROM.
Just flash a CM10 ROM from the dev forum and see how you like it, it's jellybean with tons more options that the stock ROM.
orangekid said:
The reason I suggest just flashing a custom ROM thru your recovery is once you RSD stock then do the OTA you're just going to want to root again and maybe flash a better custom ROM.
Just flash a CM10 ROM from the dev forum and see how you like it, it's jellybean with tons more options that the stock ROM.
Click to expand...
Click to collapse
The main issue i'm having is that after i rooted my phone flashing custom roms was pretty much the only aspect i didnt get into, so i'm not comfortable in the least with doing it. So just flashing a new rom might be a little strange for me. If i flash the stock rom will i lose everything i have? Like all my apps and pictures and info? And will it unroot my phone?? And if that video i posted above will work should i just try it that way?
I'm sorry to keep posting but I'm just trying to get some specific answers and I feel like if my thread falls too far down it will be forgotten lol. But that video title that I posted...does anyone know if that could be a viable solution? And if it isn't could someone explain. To me how to flash the stock rom so i can upgrade to ics. I don't think the razr has jellybean yet if I'm not mistaken
It sounds like you might be missing some of the stock apps. I had a similar problem while following the same upgrade path as you. I have a Verizon XT912 (standard RAZR) I'm lookin for a link to send you that helped with the issue...but basically there are several apps that would seem non-essential like Slacker radio or NFL Mobile that seem to have caused people trouble. If your update is failing at 30% or somewhere in the middle, this might be the problem. If this sounds like it could be it, Ill try and find the post that helped me find what I was missing.
watch your phone during the update, make sure its not actually cancelling and booting normally because of this error.
Do you know what version you were on before things happened? GB or ICS? You always use this utility just to start over and get back to stock. You could do like people are saying and get the files but this is easier. There is a version for either GB or ICS. Just need to get into AP Fast Boot mode and follow the directions. Also assume this is the Cdma phone? Here is something similar.
I would just start all over and flash.Make sure if you can that your phone is charged before starting.
blueis300 said:
Do you know what version you were on before things happened? GB or ICS? You always use this utility just to start over and get back to stock. You could do like people are saying and get the files but this is easier. There is a version for either GB or ICS. Just need to get into AP Fast Boot mode and follow the directions. Also assume this is the Cdma phone? Here is something similar.
I would just start all over and flash.Make sure if you can that your phone is charged before starting.
Click to expand...
Click to collapse
I'm on gingerbread 2.3.6. So i can just go to the bootloader menu and use AP fast boot to do what? I'm a little confused lol sorry
So does anyone have any explanation? The only reason i'm so desperate is because i'm planning on potentially selling my razr for the note 2 and i cant do that if its unable to perform this update/missing apps/etc.. lol. please help
Ok, you know, today I got my phone, I had been waiting forever, I got it and within 2 hours I screwed it up. I have followed and followed many forums and posts on how to fix this, and I am just.. lost. So please i need your help, I am seriously stressing out, and I know I shouldnt, but this is my first android phone. I am shot right now.
I had unlocked the bootloader, and then I tried to root it, then it rebooted and went into bootloop mode or whatever it is.
I still cannot figure out how to use this Hasoons2000's OX+ AIO kit. So I am just leaving it alone.
Ok the PC doesn't recognize it as a storage device, but the fastboot does recognize it, as I have executed a few commands, like reboot or something, just to test that it works.
My phone is ATT but I am in Russia so there is no sending this anywheres. All I want to do is reboot the OS and have it work again, I dont care what mod or stock rom it is, I just really need some direction here.
I know something about RUU, ATT RUU, Fastboot, some other stuff, I have like 5 pages on XDA pulled up and I cant figure this out.
What is the CMW or TWRP or whatever it is called? How do I flash a zip or an img to the phone? I really just want my phone on again.
Yes Ive done stupid noob stuff, but you learn. So please I am kindly asking for any assistance,
No need to stress. Its fairly hard to brick your phone, good way to learn quick also is to screw with it.
Just need the right guide and I think this will help you since u have fastboot access hopefully. Its a pain rebuiling so read everything so u only have to do it once.
Remember these guides are for different phones so don't use the ruu or recovery links, user my links below.
Your phone is:
AT&T(Evitare)
This guide:
http://forum.xda-developers.com/showthread.php?p=30863908
Or this guide:
http://forum.xda-developers.com/showthread.php?p=27301573
This is for another phone so you need to choose an ATT ruu from here for step 1:
Your phone is a HTC One X+ for AT&T(Evitare)*
http://www.androidfiles.org/ruu/?developer=EvitaRE
More info here for custom recoveries etc which is cwm and twrp for deploying roms, backing up your current installed Rom and general tools for fixing or enhancing your phone, displayed prior to your phone booting into android:
http://forum.xda-developers.com/showthread.php?p=37778531
Sent from my HTC One X+ using xda premium
somemadcaaant said:
No need to stress. Its fairly hard to brick your phone, good way to learn quick also is to screw with it.
Just need the right guide and I think this will help you since u have fastboot access hopefully. Its a pain rebuiling so read everything so u only have to do it once.
Remember these guides are for different phones so don't use the ruu or recovery links, user my links below.
Your phone is:
AT&T(Evitare)
This guide:
http://forum.xda-developers.com/showthread.php?p=30863908
Or this guide:
http://forum.xda-developers.com/showthread.php?p=27301573
This is for another phone so you need to choose an ATT ruu from here for step 1:
Your phone is a HTC One X+ for AT&T(Evitare)*
http://www.androidfiles.org/ruu/?developer=EvitaRE
More info here for custom recoveries etc which is cwm and twrp for deploying roms, backing up your current installed Rom and general tools for fixing or enhancing your phone, displayed prior to your phone booting into android:
http://forum.xda-developers.com/showthread.php?p=37778531
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
thank you very much I really appreciate your help. I finally figured out the ruu.exe thing, I didnt know they had to be the same numbers, ex 1.15.xxx.xx or whatever.
You see what happened originally was that I unlocked the bootloader, easy pie, but I tried to root it and that is when it started looping. Maybe I didnt understand something, but I seemed to have messed up right there.
Is there really any reason to root? I mean yeah there is super user, but doesnt bootloader help with that a bit? I know BL is for flashing custom roms and all.
May I ask how to flash a custom rom? I really want all of this ATT stuff off of my phone, I really dislike it.
Yes I know I can search, here, google etc. And maybe I should, but I end up getting so many different results, and here and there, and this and that. It really is just easier to talk to one single person who knows what they are doing. So if you could help me, I would again extend my appreciation.
Also I have the android revolution for ox+, and I dont know if it is.. you know.. THE BEST or not. Dont know what to do.
And yes, you live and learn, took me forever with iphones, then I realized hacking and roms and stuff were completely different from iphone. So new game new story.