I thought that once I got unlocked from htcdev.com that unlocked the bootloader?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root LTEVO ROOTING FOR DUMMIES {The Complete Guide}
- Thread starter ocnbrze
- Start date
-
- Tags
- htc evo 4g lte
I thought that once I got unlocked from htcdev.com that unlocked the bootloader?
correct, but the folder that you should have used to get it unlocked is still needed. you need those files and without then you can't enter fastboot the commands. i would keep that folder with those files if you still have them. they are important and could come in handy. basically those files are needed for adb and fastboot commands.
The how-to guide I was going by didn't say anything about having to create any folder. Here is the guide I was going by " How to Root HTC Evo 4G LTE! [Unlock Bootloader][ICS/JB][4.1.1] | HTC Evo 4G Hacks! " Should I re-lock & start from scratch? Is there a certain how-to for dummies that you would recommend?
ok in order to unlock your phone you needed to enter a fastboot unlock command, correct? according to this guide you used the folder called Evo4GLTERoot2. this is where the fastboot command is in. this is where you will always enter the fastboot and adb commands.
so there is no need to re-lock it. you are unlocked you just need a recovery.
Ok, thanks for the info! I'm starting to understand this a bit better now thanks to you explaining these things. So, just to make sure, I have to run command prompt directly from the Evo4GLTERoot2 folder, correct? It should read on prompt as "C:\Users\EJ\Desktop\Evo4GLTERoot2>fastboot flash recovery openrecovery-twrp-2.4.
1.0-jewel.img" correct?
Did you fastboot flash the unlock code?
When you boot into your bootloader, does it say unlocked?
Sorry, but I'm trying to get my head around you being unlocked without fastboot already on your PC.
Apologies if I missed something.
Yes, providing that you've copied the recovery img file to that folder.
When you boot into your bootloader, does it say unlocked?
Sorry, but I'm trying to get my head around you being unlocked without fastboot already on your PC.
Apologies if I missed something.
Yes, providing that you've copied the recovery img file to that folder.
Yes it shows unlocked. I put the unlock token in the folder & flashed it. My bootloader screen shows unlocked with S-ON. I did everything up until step 25 correctly on the how-to guide. I'll try it again & hope the recovery works.
yeah earlymon the htc evo hack's guide has a zip that when unzipped it contains the folder with adb and fastboot. the part about recovery was not clear enough about where to open the command. it does show it in a picture though, just not worded.
so yes i think you now have the missing part to get you rooted and unlocked.
I think my computer wasn't picking up or installing the adb files when recognizing my phone. So THAT may have been the reason I was getting failed messages when attempting before. Because I didn't have htc sync installed on my computer, but I went download it today & installed it and now I noticed my computer recognized & installed the adb whenever it picks my phone up from boot.
what is your baseband and hboot? if you have the latest ota then you will need to go to the latest twrp which twrp 5.0 is out now. the latest ota added a new touch panel has created issues for aosp roms.
you can read about the latest ota here:
http://androidforums.com/evo-4g-lte...-new-ota-do-not-download-if-youre-rooted.html
Just reflash the newer one.
I'm still on some flavor of 2.4, 2.5 just came out, give it a few days for people to endorse it.
yeah good point on waiting. definitely 2.4.1 is the one you want.
My hboot is 2.09.0000
software version is 3.16.651.3
Radio- 1.12.11.1210
OpenDSP-v31.1.0.45.0815
Baseband 1.12.11.1210
yep you will need the 2.4.1 twrp i have it linked in the guide if you need that one.
So it would be better to go with 2.4.1 instead of 2.4.4? Or would 2.4.4 be ok, as long as it's not the 2.5 that hasn't been checked & confirmed as safe yet?
i'm on 2.4.1 i have not tried the newer ones yet. i know 2.4.1 works, if you like you can try any of the newer ones. they should all have touch panel included now.....so up to you.....lol
i might try 5.0 this weekend.
I'm not sure if I wanna take a chance going with 2.4.4 if A MOD here hasn't updated to it and is still going with 2.4.1, even though I'm not sure what updates and/or changes have been made with it. Lol
it is not that there is anything wrong with any of the new updates as far as i know, it is just that i'm have been kind of busy and lazy to update my recovery
for me though 2.4.1 just works with no issues so i do not see a reason to update, but i will try 5.0 this weekend.
here is the changelog from 2.4.1 on up:
CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
I may be running 2.4.4 actually, I just can't remember and some days I'm like that, sorry.
I tend to guinea pig recoveries like ocnbrze, between us or someone here, we'll let you know.
Anyway, yeah, 2.4.1 is good.
I tend to guinea pig recoveries like ocnbrze, between us or someone here, we'll let you know.
Anyway, yeah, 2.4.1 is good.
Well, I'm now rooted! Thanks guys, for ALL of the help! Now I just need a good rom to install & HOW to install it, if the method is different than flashing the recovery. My buddy is using MeanRom, any suggestions on what I should use based off of my hboot & software? I don't wanna put something on that gives me loads of issues by not being compatible with my boot. Thanks!
Consider backing up apps and data using MyBackup Root or Titanium Backup.
MeanRom and Viper4G are both excellent.
Download, place on sd card, verify MD5 sum.
Check out "AFV (Android File Verifier)" for that.
https://play.google.com/store/apps/details?id=sa.afv
The MD5 sum value will appear on the download site, check the MeanRom or Viper4G threads for details.
Boot into recovery.
Make a nandroid backup. Accept the defaults on that.
Always check the MD5 sum of every rom download, always make a nandroid backup before flashing a new rom.
Stay in TWRP, flash the rom from inside there.
Flashing instructions may vary slightly for roms, always follow the rom developer's instructions on that.
When your rom setup is complete and your apps and data and accounts are restored, go to recovery, make a nandroid backup of that.
If you're not sure about the rom you flashed, try another. If you want to go back to the previous, just do a nandroid restore, and wipe cache and Dalvik.
MeanRom and Viper4G are both excellent.
Download, place on sd card, verify MD5 sum.
Check out "AFV (Android File Verifier)" for that.
https://play.google.com/store/apps/details?id=sa.afv
The MD5 sum value will appear on the download site, check the MeanRom or Viper4G threads for details.
Boot into recovery.
Make a nandroid backup. Accept the defaults on that.
Always check the MD5 sum of every rom download, always make a nandroid backup before flashing a new rom.
Stay in TWRP, flash the rom from inside there.
Flashing instructions may vary slightly for roms, always follow the rom developer's instructions on that.
When your rom setup is complete and your apps and data and accounts are restored, go to recovery, make a nandroid backup of that.
If you're not sure about the rom you flashed, try another. If you want to go back to the previous, just do a nandroid restore, and wipe cache and Dalvik.
NICE!!!!!!!!!!!!!!!!!!!!!!!
ics and jellybean are just software updates. with what you have you should have no issues with anything other then flashing aosp roms. mean rom is ics while meanbean is jellybean. you will not see any more development with mean rom. the dev is going forward with meanbean for now.
as of right now there are somethings about your hboot and being s-on and that is that you will not be able to easily update your radios should there be another update and you will not be able to try any aosp roms at the moment.
aosp roms like cm10 are much smaller then sense roms. for me i think they perform better because of this. i get better battery life out of aosp roms then i do on sense based roms. however, aosp roms are not for everyone. and for you the only way you can try them out is if you go all the way and get s-off......not that you need to right now........just letting you know what the differences are.