I see a lot of people repeatedly asking the same questions regarding 2.1/root/etc, so I made an FAQ for them to be referred to. It is located here:
lostsync.net/erisfaq.html
It's perfectly ok with me if it is reproduced in any way. I'm also happy to make changes and corrections.
Following jcase's advice, the full text is also posted below:
__________________________________________________
What is root and why do I want it?
On UNIX-like systems, root is generally the only account that can do anything it wants without restriction. The root account is often disabled or access is not given to the end user for security reasons. Rooting a phone (or anything else, really) refers to obtaining root access through whatever means available. A person would want to root their phone because it allows for capabilities beyond those provided in the original software and gives third-party apps new possibilities (like wireless tethering, for example). It also allows the user to flash custom ROMs, boot images, and otherwise tinker with their phone in ways that it was not designed to let you do. If you are familiar with iPhone/iPod Touch jailbreaking or softmodding a game console, you can consider rooting analogous for all intents and purposes.
Can I root my phone?
Yes, Whether your phone is running 2.1 or 1.5 you can root it using this method
If I have 2.1 leak on my phone, can I root it?
Yes
What versions of 2.1 exist?
There are three 'official' versions of 2.1. These are generally referred to as 2.1 root, 2.1 leak, and 2.1 ota (or new 2.1 leak).
What version of 2.1 do I have?
The easiest way to determine this is to go back to where you got 2.1 and re-read. Barring that, use the following steps:
From the home screen, press the menu key
Select "Settings"
Select "About Phone"
Select "Software Information"
If you see "release-keys" under the "Build Number" heading, you have some version of 2.1leak. If you see "test-keys," you have 2.1root or some derivative of it (i.e. a custom ROM)
Is it possible to downgrade from 2.1 to 1.5?
Only if your phone is already rooted.
Is it possible to upgrade from 1.5 (rooted) to 2.1 and keep root?
Yes.
If I install 2.1leak (or any version of 2.1 currently available), will I be able to receive the OTA update from Verizon when it comes?
Nope
I have installed some version of 2.1. Some apps don't appear in the Market. What gives?
Use this tool made by Jcase
Can I install a custom ROM without root?
No.
I have root. How do I install a custom ROM?
Read Here and Here
Does <some custom ROM> contain <some feature I want>?
Check with the person or people responsible for the custom ROM in question.
Can you explain all this talk about signed ROMs?
It goes something like this: When HTC is ready to release a firmware version, they sign it. They do this by first creating something like an MD5 checksum based on the original contents of the file. That checksum is then encrypted with a key pair belonging to HTC. When the phone tries to flash firmware, it first decrypts the checksum using keys installed on the device. That checksum is compared against the firmware package you are trying to flash. If it matches, firmware installation can proceed. If not, the firmware is assumed to be broken, corrupt, or hacked and is rejected. Nobody outside of HTC knows exactly how they sign their ROMs and the above is really just an educated guess. This makes it difficult, if not impossible, to reverse engineer the signing process as a way of obtaining root. Even if we did know the exact procedure, it would be very difficult to pull off.
I installed 2.1 leak. When will I be able to root my phone?
Yes, Use this method
How did they get root in 2.1 root?
2.1 root was leaked from HTC and was already rooted. Since no procedure was developed by the devs to root it, it's impossible to apply that procedure to other versions of 2.1 that have been leaked from HTC.
What is a 'gold card'?
A gold card is a memory card that has been converted to unlock your device's CID while it is in bootloader mode. It allows you to essentially turn your production phone (meaning one sold in stores) into a development phone (meaning one used internally at HTC for the development of ROMs), which will let you flash any ROM you like. No one has succeeded in creating a gold card for the Droid Eris.
It would be great if you included the whole FAQ in the post. Good write up.
jcase said:
It would be great if you included the whole FAQ in the post.
Click to expand...
Click to collapse
Good point.
Nice job lostsync. Will definitely be pointing to this thread to help guide the
lost sheep and/or the"too damn lazy".
+1
this is defiantly a very good write-up FAQ. It answers almost all of the common questions new members are asking. i will be pointing to this often!
Sticky!
Great info
Stickying this, and unstickying the other thread. You should add a link to the rooting process, though.
And, of course, thanks for the write up .
I tried searching for a how-to on this but apparently I'm searching inclined.
From what I can gather is it as simple as just dumping the zip onto the root of your SD card and doing:
3. Make sure phone is off then hold Power button and Call Button.
4. The menu opens quickly press the power key over the hboot option.
5. Follow onscreen instructions to install the update. the phone will reboot a few times.
you dont even need to search. go to the development section and then look at the top few, it will have very detailed instructions.
I guess I should have elaborated more and said I don't have my phone rooted and really don't want to go that route. I was just getting confused because everything i was finding on here was people running root but I came across a few things where people said the 2.1OTA Leak was just a straight upgrade, so that is my confusion.
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
rheally said:
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
Click to expand...
Click to collapse
but if you have root you can do the downgrade back to 1.5
Android22 said:
but if you have root you can do the downgrade back to 1.5
Click to expand...
Click to collapse
Oh right, I forgot about that, duh It just seems like root would be a better choice.
But to each his own.
rheally said:
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
Click to expand...
Click to collapse
yeah that is my question, can 2.1OTA just be flashed or does your phone need to be rooted?
I just feel like with root I'll be more likely to kill the phone but I'm going to check into it more again.
If you flash the 2.1 OTA leak onto your phone you CANNOT root your phone. It hasn't been figured out yet.
Root really isn't that hard to do. There are several threads over in the development forum.
rheally said:
If you flash the 2.1 OTA leak onto your phone you CANNOT root your phone. It hasn't been figured out yet.
Root really isn't that hard to do. There are several threads over in the development forum.
Click to expand...
Click to collapse
yeah I was just reading the thread on going from stock 1.5 to rooted 2.1. Can you give me some of the major benefits of rooting? I'm trying to find really practical stuff, not just the "Well it's cool cause it's like being root in Linux".
And just to clarify you can just flash to 2.1OTA? I'm skeptical of doing that now because I was reading some people think 2.1OTA has a time sensitive date on it.
Future developments will likely be easier to impliment if you root. The ability to run different (and potentially more stable) ROMs. Support for future software not designed for the Eris. Post rooting you can also make Nandroid backups and as long as you don't somehow screw your bootloader you can actually fix your phone.
Also, and this is pure speculation, should Verison decide to discontinue support for the Eris entirely, non-rooters may have issue getting new Android versions since they're limited to signed code.
EDIT: there is also little reason NOT to root. It does everything that you can do unrooted and more. All this plus the fact that you may never be able to root again but could always unroot at your leisure.
Marisa said:
Future developments will likely be easier to impliment if you root. The ability to run different (and potentially more stable) ROMs. Support for future software not designed for the Eris. Post rooting you can also make Nandroid backups and as long as you don't somehow screw your bootloader you can actually fix your phone.
Also, and this is pure speculation, should Verison decide to discontinue support for the Eris entirely, non-rooters may have issue getting new Android versions since they're limited to signed code.
EDIT: there is also little reason NOT to root. It does everything that you can do unrooted and more. All this plus the fact that you may never be able to root again but could always unroot at your leisure.
Click to expand...
Click to collapse
Can you point me to a good nandroid tutorial? tried searching for one but if you know of a good one I'd appreciate it.
I was trying to find a nandroid guide when I did it the first time, but once I discovered that Amon_RA's recovery has it built-in, I decided to wing it and see what happened. It was a lot easier than I expected to be honest.
Reboot your phone into recovery (VOL UP + Power), you should have a short list of options, one of which should be Backup/Restore. Trackball into it and select to make a backup. Let it do it's thing, should take a few minutes. Congratulations, you've made a backup of your phone. You can make as many as you like, they're given names based on the date and time they're created, but you can rename without harm (barring a few characters keep it A-Z a-z 0-9 and you should be good)
Restoring to that backup is as easy as entering the same menu but picking restore instead. You need to have made a backup first in order to restore something.
NOTE: I've written all this by memory, and while it should be fairly accurate, I can't turn my phone off currently to double check that the wording is all correct.
I'm a bit confused on the Amon thing. I found the the link here http://forum.xda-developers.com/showthread.php?t=648025
Do I just dump that IMG file onto the root of my SD card and that's it? Will it know to always use his recovery or do I need to do more?
I have an application that I write to make going from 1.5 to root a lot easier with a gui application. It will be released very soon for everyone to use. Take a look at my thread for more info. Link is at the top of my signature.
Sent from my Eris using the XDA mobile application powered by Tapatalk
frankspin said:
I'm a bit confused on the Amon thing. I found the the link here http://forum.xda-developers.com/showthread.php?t=648025
Do I just dump that IMG file onto the root of my SD card and that's it? Will it know to always use his recovery or do I need to do more?
Click to expand...
Click to collapse
If you followed Ivan's guide to the very end, you already flashed Amon_RA's recovery to your phone. To enter it, shutdown your phone and then hold volume up and the call end button (power), you should boot into the recovery.
Marisa said:
If you followed Ivan's guide to the very end, you already flashed Amon_RA's recovery to your phone. To enter it, shutdown your phone and then hold volume up and the call end button (power), you should boot into the recovery.
Click to expand...
Click to collapse
AWESOME! Thank you I am doing it right now.
NM: got it
Well I got 2.1 on but I did something wrong and can't load rooted 2.1. I get "signature verification failed" message when I load the zip file.
I tried to flash a custom rom on my eris last night with unsuccessful results.
To begin, my phone had the newest 2.1 OTA update on it and is running HBOOT 1.47. I downloaded and ran the 1-click universal root app. I noticed that a few new apps showed up (Latitute), but the Superuser app did not. I re-ran it several times but it still wouldn't show up.
Getting ahead of myself, I decided that I probably *DID* root the phone and I flashed Kaosfroyo V29 through the recovery menu. As I rebooted, the phone hung at the loading screen. I then tried to flash the Cyanogen mod with the same results.
After looking around, it appeared that the HBOOT 1.47 was exploitable with the 1.5 PB00IMG.zip update. I loaded it to my sd card and booted the phone in quickboot. It recognized the image but did not give me the option to update.
So now I am left with a phone that won't boot and without a backup (I know, I know).
What are my options? Is it still rootable from the recovery menu? Should I take it back to verizon and see if they can reflash/replace it (Doubtful as I probably voided the warranty).
wolfpack10 said:
I tried to flash a custom rom on my eris last night with unsuccessful results.
To begin, my phone had the newest 2.1 OTA update on it and is running HBOOT 1.47. I downloaded and ran the 1-click universal root app. I noticed that a few new apps showed up (Latitute), but the Superuser app did not. I re-ran it several times but it still wouldn't show up.
Getting ahead of myself, I decided that I probably *DID* root the phone and I flashed Kaosfroyo V29 through the recovery menu. As I rebooted, the phone hung at the loading screen. I then tried to flash the Cyanogen mod with the same results.
After looking around, it appeared that the HBOOT 1.47 was exploitable with the 1.5 PB00IMG.zip update. I loaded it to my sd card and booted the phone in quickboot. It recognized the image but did not give me the option to update.
So now I am left with a phone that won't boot and without a backup (I know, I know).
What are my options? Is it still rootable from the recovery menu? Should I take it back to verizon and see if they can reflash/replace it (Doubtful as I probably voided the warranty).
Click to expand...
Click to collapse
Try installing the engineering Bootloader. Instructions can be found in a sticky called Eris roll-up in the Eris developement section. Even if you can't flash a custom Rom after this you can still flash the official 2.1 ruu which will put your phone back to 100% stock and you can try again.
If your rooted and can still boot to fastboot your not bricked.
Sent from my Eris using XDA App
If the bootloader still appears (power phone on with vol-down+end), your phone is not bricked.
If the recovery boot still appears (power phone on with vol-up+end), your phone is not bricked.
If you don't have a SD card reader on your PC, you can transfer a different ROM to your SD card by booting to recovery and using the USB-MS toggle.
Smart money says that all you failed to do when you installed the ROM was perform a wipe before you flashed the ROM.
Prove this to yourself by installing a conservative ROM such as PlainJane, and when you get it running, for Dog's sake, make an effing Nand backup.
bftb0
I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Can I actually install alternative bootloaders on an unrooted phone?
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.
wolfpack10 said:
I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Can I actually install alternative bootloaders on an unrooted phone?
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.
Click to expand...
Click to collapse
Do you still have ra recovery? If so simply boot to recovery, wipe data and cache and reflash the rom.
All the 1 click root does is flash the custom recovery, so it did work.
Fyi
The Eris can now be rooted no matter what Bootloader version you have so doing the ruu will not prevent you from rooting. I myself was a leaker and had no problem rooting with the 1.49 s-on Bootloader.
As stated by btfb0, ALWAYS wipe data and cache before flashing a new Rom. ALWAYS do or have a nand backup ready just in case.
Sent from my Eris using XDA App
wolfpack10 said:
I know for a fact it isn't rooted though (It says S-UP on the Recovery Menu).
Click to expand...
Click to collapse
If you see the text "S-OFF" at the top of the screen, that is the bootloader, not the recovery boot. The one-click rooting method does not touch the bootloader, so, after successfully using "one-click", you will still have the same bootloader (initially).
wolfpack10 said:
Can I actually install alternative bootloaders on an unrooted phone?
Click to expand...
Click to collapse
You can install the Root PB00IMG.ZIP file onto a 1.46.xxxx or 1.47.xxxx bootloader phone - but you don't need to, because your phone already has a custom recovery installed on it (Amon_RA). As I mentioned previously, you get to that recovery facility by one of two ways:
1) Power phone off. Press and hold Vol-Up and then End/Power; continue to hold both keys down until you see the three skating droids appear (Don't release the keys until you see that screen). A menu system should appear 10 seconds after that happens. It will say "Amon_RA" on the bottom of the screen.
2) Make sure there are no files named PB00IMG.ZIP in the root folder of the SD card; either that or eject the SD card. Power the phone off. Press and hold Vol-Down and then End/Power; continue to hold both keys down until you see the three skating droids appear (Don't release the keys until you see that screen). A menu will appear immediately. One of the items will indicate that if you press "Vol-Up", you will boot into recovery. Press Vol-Up, and wait 10 seconds. You should be at the Amon_RA menu. (At this point, you can re-insert the SD card if you previously ejected it).
If you can't get either of these things to work, report back with exactly what you observe - saying "it didn't work" might be correct, but it isn't very informative.
wolfpack10 said:
Also, I want to avoid flashing the official RUU because it updates the HBOOT to 1.49 which, to my knowledge, has not be exploited yet.
Click to expand...
Click to collapse
Not correct. Both the "one-click" and "Dummies" methods (see All Things Root forum over at AF) work for 1.47, 1.49.0000, and 1.49.2000 bootloaders.
wolfpack10 said:
Do either of you know why the PB00img.zip didn't work? I read multiple places that it should work with my HBOOT version.
Click to expand...
Click to collapse
The PB00IMG.ZIP files are not compatible with the Amon_RA "update"-style installs; they are signed using an entirely different method. Not compatible. That's why it didn't work when you tried it (using Amon_RA). They are installed by starting up the bootloader with the PB00IMG.ZIP file in the root folder of the SD card. I am recommending that until you understand things a little better, you avoid this method - it only works with certain combinations of bootloaders and PB00IMG.ZIP file versions.
wolfpack10 said:
Also, why didn't the 1-click root work? I haven't done anything like this previously and I bought the phone new at version 1.5.
Click to expand...
Click to collapse
It did work. You indicated in your first post that you used the Amon_RA recovery, which was installed by that method.
bftb0
Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.
wolfpack10 said:
Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.
Click to expand...
Click to collapse
Contacts should have been backed up through google. Although I have leaked and rooted some friends phone and their contacts never sync'd to their phones.
Sent from my Eris using XDA App
wolfpack10 said:
Thanks for the detailed responses. I know I should have researched this stuff more before I started toying with it but I'll just have to pay the price.
I wiped and flashed KaosFroyo V29 from the recovery menu and it finally booted. Many thanks for that suggestion.
Hopefully this thread will be helpful for other people in the future.
In the mean time, I lost all my contacts so lesson learned.
Click to expand...
Click to collapse
Glad you got it working.
If you were using Gmail instead of the HTC mail app for managing your contacts, all your contacts are still "in the cloud" (so long as you did not define them to be "phone only" when you added them).
If they were phone-only contacts, it would have been a simple matter to get your contacts back if you had made an initial Nandroid backup. I'm not saying that to add insult to injury, but rather (as you said) "Hopefully this thread will be helpful for other people in the future."
Backups are a really good thing.
BTW - You will find that Android Forums is a useful adjunct to this forum. The reason is that the ROM devs over here on XDA have their hands full trying to do both development work and interact with the users/testers reporting issues with their ROMs, so they don't spend much time in here (Q&A or General sub-forums). When they do announce a new hack, or patch, or rooting method, the descriptions are many times written tersely (for subject-matter experts, not newbs). There are a number of very helpful folks over on AF, and some good "sticky" posts that are quite a bit more detailed than what you will find here. I'm not ragging on XDA at all; just saying that by nature of the focus required for development work, the experts can't give much personal attention to individual users, even if they want to.
bftb0
I have a stock rom evo 4g LTE, rooted, with Android 4.0.3 on it.
I forget the root app I used, some one click thingy, I guess my bootloader is unlocked
because I get a boot menu every time I reboot, on that screen that says **TAMPERED**.
Anyway, I ignored the notification icon in my taskbar for OTA updates, for a very long time.
Since the day I bought it over a year ago.
Finally I decided "eh, screw it, why not." ...I'm sure I'll regret that.
I told it to do the OTA update, and it downloaded (I think??) and rebooted.
The icon went away. Seemed to be a done deal.
But once per day since then, my phone rings, and I see a prompt saying
there's an OTA update, and would I like to install it now?
I think it's the same OTA update being prompted repeatdly,
because the filesize is always the same (~42 megs).
What should I do? I can choose install, reboot, and be fine for the rest of the day,
or choose cancel, reboot, and be fine for the rest of the day.
Doesn't seem to matter. But would be nice to fix it for good.
Well, considering that you are about 4-5 OTAs behind the rest of the community, I would say that the notification is probably correct. HOWEVER, of you are not using the stock recovery, then the OTA did not flash. Yes, the phone rebooted, but that's because it is installed entirely through recovery, and the phone has to reboot to get into recovery mode in the first place.
Now, for the more important question at hand....why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted? As far as I'm concerned, the OTAs are actually necessary updates for the phone. I'm sure that you will love Jelly Bean if you have never used it before.
And please, for the sake of us all who are cringing at the sight of the first sentence....PLEASE UPDATE your phone! If you have a good reason not to, please share.
Hi, thanks for the reply... Maybe they were all different updates after all.
I haven't been prompted to update again since my post.
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
HOWEVER, of you are not using the stock recovery, then the OTA did not flash.
Yes, the phone rebooted, but that's because it is installed entirely through recovery,
and the phone has to reboot to get into recovery mode in the first place.
Click to expand...
Click to collapse
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted?
Click to expand...
Click to collapse
Well, I had no compelling reason to upgrade. I still don't really, the phone does what I want,
I just saw some of the features in the next version and thought "huh, that sounds pretty cool".
I'm rooted for all the usual reasons... I want to be able to browse, copy, move, rename files (including system files)
without incident... use nandroid for backups... wifi tether (still can't get that to work actually)... install unapproved apps...
tweak the OS, and so on.
Ok, my friend...let me educate you. Instead of giving you the simplest, fastest solution, I will actually try to answer all of your questions, since you did ask.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
Click to expand...
Click to collapse
To give a very superficial explanation of Jelly Bean, it is everything that ICS does, and more. It just does it smoother. It also brings Google Now, which was – and still is – the selling point of Jelly Bean. The Sense launcher got a few changes, too, but you will have to explore those changes on your own (mainly because I don’t remember them off hand, and this post is beginning to become lengthy).
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
Click to expand...
Click to collapse
If the first update didn’t update properly, then the phone is simply downloading and trying to install the same update over and over. When you boot back into Android after a successful update, you will be greeted by a welcome message congratulating you for installing the new version.
If you are rooted, odds are, you are using a custom recovery, such as TWRP or CWM. OTAs are only installed through the stock recovery & a locked bootloader. The stock recovery doesn’t make nandroids, or do anything of the sort. To install the stock recovery, go here:
http://downloadandroidrom.com/file/HTCEvo4GLTE/rooting/Evo4GLTERoot2.zip
Click to expand...
Click to collapse
The stock recovery is located somewhere within the zip file.
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
Click to expand...
Click to collapse
You can flash install the stock recovery by using fastboot commands from the bootloader (which is the screen that shows the TAMPERED status on the top), or you can use Flash Image GUI. It is a paid app on the Play Store, or you can get it from XDA (the dev let XDA users download it for free…Google it).
Lastly, there are a few things that I suggest that you do. First, obtain S-Off (Google, Google, Google...very simple), so you can install the new firmwares directly, instead of using OTAs. Otherwise, if you accept the OTA, you will lose root, and you will have to root your phone again and again. Installing the firmware, then the new rom is the same as accepting the OTA, then rooting.
Another alternative is to get S-Off, then accept the OTA (after installing the stock recovery). Your bootloader does not need to be locked, and there are recovery zips floating around here that can be installed through the bootloader (therefore, you will not be stuck rooting the phone the hard way, just boot into recovery and flash SuperSU). I highly suggest achieving S-Off.
If you want to jump straight to the latest version (Android 4.3, Sense 5.0) by installing the RUU located somewhere in this forum. I actually suggest that you try Sense 4 with Jelly Bean first, but that is completely up to you. Keep in mind that using the RUU will wipe your internal memory, so back up what needs to be backed up. This doesn’t require you to be rooted, and the state of the bootloader does not matter. It will lock the bootloader, load the stock recovery, and you will lose root. You won’t be able to downgrade without S-Off.
Other Notes:
When using the 4.3 RUU, make sure that Android USB Debugging is enabled.
Bookmarking for later but I wanted to say thanks for the thorough reply!
I can confirm the update never worked, because I never got the confirmation message
and I got prompted again a few hours after I posted.
Are you willing to answer just a few more things?
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
- Get my phone into S-OFF status.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
Are you willing to answer just a few more things?
Click to expand...
Click to collapse
As always, I'm open for questions. Not to sound egotistic, but I enjoy sharing my opinion.
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Updating to the 4.3 firmware wipes your internal memory, not your sd card (although, that may be a very unfortunate circumstance, so it should be backed up as well). The other firmware updates do not affect your memory.
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Technically, yes they are "on the cloud." The fact that you paid is saved somewhere within your main Google account that you downloaded the app with. It is possible to pay for apps with your secondary gmail account, which can be switched within the Play Store app.
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Use Titanium Backup if you can't find the apks. I do save my apks that I download, and I also upload them to Google Drive, since I have multiple Android devices, and I also have a faulty micro sd card that I am yet to replace. I can lose my data at any given moment, but everything is backed up, so I'm not worried.
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
Everything within the /system folder is wiped when you flash new roms. That data is NOT backed up while flashing between roms. Also, since it is from an older Android version, it's best to leave them alone. You may back up the data if you like, but I would refrain from restoring the apks along with the data.
The /data directory may be wiped, depending on the dev who built the rom zip. If they added the superwipe script, then /data will be wiped as well. Most devs do not include this, since many people "dirty flash," which is flashing new roms or updates of the current rom without wiping /data first.
- Get my phone into S-OFF status.
You will save yourself a LOT of headaches in the future. It was my S-Off status that allowed me to reflash my firmware when I lost the function of my data/voice antennas while carelessly flashing a port of a phone on a different carrier. Also, if you feel curious to try AOSP roms, then you do not need to do any extra steps to flash them.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
Yes, the firmware handles manages how the hardware of the phone operates. Updating the rom changes how the software looks and behaves. The kernel is sort of a bridge between the firmware and the software, since it manages the firmware (like battery life, processor speed, antennas, etc.), but the kernel is dependent on the software version. The firmware is not dependent on the software version, just as the software version is not dependent on the firmware version.
The only exception of the firmware/software independence is the 4.3 update, which requires a complete update of the firmware, and the older software cannot run on the new firmware without being modded by a dev.
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
Your bootloader is the white screen that shows the TAMPERED status on the top, and little Androids on skateboards on the bottom. With the exception of the firmware information in the top left corner, this screen does not change...ever.
TWRP is your recovery image, which is accessible through the RECOVERY option in your bootloader, or you can boot directly into it through different apps in Android - Titanium Backup is one of them (yes, that's one of the options, even for the free version).
The only reason to return your recovery to stock is to accept OTAs, and also to bring your phone back to the complete factory settings, just as the day when it was first purchased (for the sake of selling the phone, or returning back to Sprint for service}. Otherwise, don't bother with it. You may want to update your version of TWRP, though. If you update to 4.3, you will have to update it. I'm not going to take the time to get into that right now. I've given you enough homework.
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
I am a very patient person. To me, exploring Android takes time. I enjoy reading before I test, and testing before I settle (which I'm yet to "settle"). All of that being said, I suggested Sense 4 before Sense 5 because I wanted you to experience the both of them. They are truly two different versions of Sense, which one might not realize, as their version numbers are differentiated by one integer (in other words, 4 to 5). Sense 3 was a small step above Sense 2, and Sense 4 was a bigger step from Sense 3. Sense 5 is a complete overhaul of the Sense UI, save the flip clock.
I just feel that skipping from 4.0 to 4.3 is missing out on a great experience, but that is mainly if you actually want to try out different roms. Until the Sense 5 RUU, I still visiting ICS on occassion, but I usually didn't last more than 3 hours before I jumped back to JB.
Click to expand...
Click to collapse
Whew...you're making me work. But I like it. Anymore questions? Feel free to ask.
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
CreeDo said:
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
Click to expand...
Click to collapse
Did you unlock your boot loader first? You don't need to be S-off to install a custom recovery. Unlock your bootloader at htcdev.com then install twrp.
Read here for more info:
http://forum.xda-developers.com/showthread.php?t=2420916
Also, I suggest learning how to use fastboot commands. Install twrp using fastboot.
Sent from my EVO using XDA Premium 4 mobile app
OK, so I'm semi-bricked but not panicking yet.
Here's where I'm at.
• Unlocked boot loader successfully
• Installed TWRP using fastboot.
• Followed instructions as closely as I could on moonshine.io to get S-OFF working.
Several times during the process I got "installing device driver software" in my win7 system tray.
Not sure if that's normal. But the drivers seemed to install fine. At first.
But then, during this part of the process:
Moonshining .................(1)
Windows prompted me that it was installing some drivers again, But it failed to install the MTP driver.
After ten tries with the "Moonshining" step, I got "ERROR: don't drink and moonshine!" or something like that.
So, it seems like I need to get this MTP driver going. First I tried solutions on the computer:
• Uninstalled all HTC software, unplugged phone, rebooted,
installed HTC Sync Manager (setup name setup_3.0.52.0_htc.exe), then uninstalled it...
because a tutorial said this would keep the drivers but remove the software. Still no luck on the MTP driver though.
• Found "Mass Storage Device" (my phone) under device manager, removed it, unplugged, rebooted, replugged.
• Plugged cord into back of PC, so I'm using USB 2.0 rather than USB 3.0.
• One suggestion said a certain registry section might have an upperfilter key that shouldn't be there.
But I don't have that upperfilter key so that's not the issue.
Some fixes require getting into my phone (one guy suggests turning off USB debugging)...
but I no longer have a working OS. I can get into my bootloader, I tried Factory Reset.
But after choosing this I go into TWRP and I have no TWRP backups that I can restore.
So my next guess is, I need to get a recovery ZIP (is that basically a ROM?) that TWRP can install.
If that's correct, what ZIP should I get? I was on Android 4.0.3 Sense 4.0, can I download jellybean with Sense 5.0,
and install it via TWRP?
That was my goal all along, but I'm determined to get S-OFF working, so if doing that means my phone gets wiped again,
I guess I just want whatever ROM/recovery/whatever that allows me to change this USB debugging setting,
and try other phone-related fixes to the MTP driver issue.
First of all, flash an ICS rom. I'm assuming that you are still using the same ICS firmware, and you will want to have your phone operational (to enable USB debugging). The link for MeanRom ICS still works. http://old.androidfilehost.com/main/EVO_3D_Developers/mikeyxda/LTEvo/MeanROM-ICS-v65-jewel-ltevo.zip
Ok....since you are on the old HBoot, I think that you need to use the older S-Off methods (LazyPanda or DirtyRacun), if I'm not mistaken. You can not download and flash Sense 5.0 through TWRP as of yet, because you need to be using the new firmware to do so. You may want to pay http://unlimited.io/jewel.htm a visit. Also, to use LazyPanda or DirtyRacun, you need to be using Ubuntu. Another option that you have is to use the regular RUU and update directly to Sense 5.0. You will be stock, unrooted, but you can easily use the latest S-Off method.
Lastly, for your rooting/S-Off needs, you can also use a handy-dandy toolkit from @WindyCityRockr that can handle everything that you need to do. I usually encourage manual labor, but there are some exceptions. http://forum.xda-developers.com/showthread.php?t=2436217
Thanks again for jumping in.
I'm getting somewhere, but still so many difficulties.
Fix one thing, break two more.
I finally have a new working rom, but almost against my will it ended up
being CyanogenMod.
The short version:
- unlocked bootloader, got TWRP going, finally got ADB working (don't think it's the right driver,
but whatever, ADB commands work fine), wiped everything... factory reset, Dalvik, external storage.
- Didn't wipe Internal storage, I wiped only /data/ per some post's recommendation.
- I used ADB PUSH to get a few possible roms onto /sdcard/
PJ75IMG_1.13.651.1.zip (failed with "unable to open zip")
(ROM)_Stock_Rooted_OTA_(3.16.651.3)V2.zip (failed with "unable to execute updater binary in zip")
cm-10.2.0-jewel.zip (cyanogenmod) - success!
So, the phone works. It appears to be at least based on android 4.3... and I'm guessing CM, which updates
frequently, has all those OTA updates bundled into it. Any downsides to CyanogenMod?
I could just proceed from here to reinstall my old apps etc.
I'm still not "S-OFF" which annoys me, but I read a post suggesting it's not really that necessary.
The way they put it is, s-off allows you to access partitions so they can be modded,
but nobody is developing anything interesting for those partitions. Like nobody's doing custom radios and such.
Should I still pursue S-OFF anyway?
If so, is there a way to do it with CyanogenMod?
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Should I still pursue S-OFF anyway?
Click to expand...
Click to collapse
Yes! Being S-On is a complete pain in the BUTT when switching AOSP roms. Have you tried to flash the rom that I posted, MeanRom ICS? I'm really trying to get you to stay on Sense, because S-Off and other different tools work so much better while using Sense. AOSP is better after S-Off. But that's up to you.
If so, is there a way to do it with CyanogenMod?
Click to expand...
Click to collapse
I am not sure. You can try if you have the time. I suggest making a nandroid of your CM rom, and try to flash a Sense ICS rom, not JB...yet.
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Click to expand...
Click to collapse
CM might be the issue here, as well as it might not.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Click to expand...
Click to collapse
Yes, TB will still work. There are some apps that might cause the restoration process to freeze, so I suggest killing TB and skipping over the app that froze the process when you return.
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Click to expand...
Click to collapse
If your keyboard preferences was not backed up, then no. If you were using the stock Sense keyboard, then that is a no as well. As long as your texting history was backed up, it can be restored. Texts are not like apps...their data is typically stored in XML files which are readable through any version of Android (2.3+).
I'm still soliciting my help if you need it.
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
CreeDo said:
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
Click to expand...
Click to collapse
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
CreeDo said:
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
Click to expand...
Click to collapse
Can't remember if it wipes or not. Best thing to do is make a backup with TWRP and keep the backup on your external SD card. If it wipes you can always restore your backup.
Sent from my HTC device
Thanks for the help so far guys. I am currently really enjoying Cyanogenmod. I suspect it's eating battery more,
but then against I am on the phone for hours redoing everything that got changed/removed.
Does anyone know if there's a simple way (or even a difficult way) to restore my texts?
Because the app is totally different, and the old text app was the one that came
with the stock rom, I cannot restore it in titanium. But if I could extract even the raw text that'd be helpful.
Get back to Sense, or get someone with Sense to restore it for you, and save it using a different app. Or maybe try using SMS Backup & Restore from the Play Store. I'm not sure if it can read the backups saved through Sense, but it's worth a try. You just have to navigate to the location of the old backup.
It looks like I can import an XML in this messaging app so maybe if sense offers an export to XML option, I'll be set.
Sense is sort of an OS on top of the OS, right?
Can sense be loaded without flashing a new rom? or is it too integrated with the OS?