Yeah I do have Snow Leopard on my mac and it is weird cuz I followed the same procedure that when I rooted last time but not it seems to not want to work. I'll keep trying maybe I would try it with a different computer to see what results I can get.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root ROOTING For Dummies
- Thread starter Matlock
- Start date
-
- Tags
- htc evo 4g
Yeah I do have Snow Leopard on my mac and it is weird cuz I followed the same procedure that when I rooted last time but not it seems to not want to work. I'll keep trying maybe I would try it with a different computer to see what results I can get.
wrapkgb
Android Expert
I wish I had some more ideas on what could be wrong, but I don't. Sorry we couldn't get it figured out!
Bob The Great
Newbie
Got an issue using this method, hoping someone can help me out.
I have an EVO running software version 3.70.651.1 Hboot 2.10.0001 radio 2.15.00.11.19. My PC is running Windows XP SP3 32bit.
I followed the directions in the first post up through section 2, step 6. Unrevoked ran, rebooted my phone, and reported root successful, then immediately after "This was a triumph", I got the following error in the unrevoked window: "Internal error: failed to unlock NAND flash?" My phone rebooted once more, but the error message remained in the unrevoked window, and that's where I am right now.
The only unexpected thing that happened was this: I successfully installed the "Android Bootloader Interface" driver as instructed on the unrevoked webpage, but when unrevoked prompted me to plug in my phone, windows detected a "Android Component ADB Interface" and asked for a driver. I pointed it to the same folder that the other driver was in, that I downloaded from unrevoked's website, and it successfully installed. As soon as it installed, unrevoked recognized that I had plugged in the phone and popped up its confirmation notice.
What should I do? My phone is booted up and running normally, but in terminal emulator, typing "su" returns "permission denied" and returns me to the $ prompt, so I don't think the root was successful. I'm not sure if I should try to uninstall the ADB driver and try again or where to go from here. Help!!
-----------------------------------------------------------------------
Ok, I figured it out. I found this post on the xda-developers forum from a guy who had the same problem.
xda-developers - View Single Post - [ROOT] unrevoked3 v3.31 (with support for new HBOOT, now with amend scripting!)
I think the issue was that I had never had HTC Sync installed at all on the computer I used to root the phone. I followed his advice and installed it, then uninstalled it, but left the drivers alone. I then went back to section 2 step 2 of this guide and reinstalled the unrevoked driver as instructed. Ran unrevoked again, and this time is was successful, and did not prompt me for any other drivers.
I'm now officially part of the rooted club.
Thanks for putting together this great thread!
I have an EVO running software version 3.70.651.1 Hboot 2.10.0001 radio 2.15.00.11.19. My PC is running Windows XP SP3 32bit.
I followed the directions in the first post up through section 2, step 6. Unrevoked ran, rebooted my phone, and reported root successful, then immediately after "This was a triumph", I got the following error in the unrevoked window: "Internal error: failed to unlock NAND flash?" My phone rebooted once more, but the error message remained in the unrevoked window, and that's where I am right now.
The only unexpected thing that happened was this: I successfully installed the "Android Bootloader Interface" driver as instructed on the unrevoked webpage, but when unrevoked prompted me to plug in my phone, windows detected a "Android Component ADB Interface" and asked for a driver. I pointed it to the same folder that the other driver was in, that I downloaded from unrevoked's website, and it successfully installed. As soon as it installed, unrevoked recognized that I had plugged in the phone and popped up its confirmation notice.
What should I do? My phone is booted up and running normally, but in terminal emulator, typing "su" returns "permission denied" and returns me to the $ prompt, so I don't think the root was successful. I'm not sure if I should try to uninstall the ADB driver and try again or where to go from here. Help!!
-----------------------------------------------------------------------
Ok, I figured it out. I found this post on the xda-developers forum from a guy who had the same problem.
xda-developers - View Single Post - [ROOT] unrevoked3 v3.31 (with support for new HBOOT, now with amend scripting!)
I think the issue was that I had never had HTC Sync installed at all on the computer I used to root the phone. I followed his advice and installed it, then uninstalled it, but left the drivers alone. I then went back to section 2 step 2 of this guide and reinstalled the unrevoked driver as instructed. Ran unrevoked again, and this time is was successful, and did not prompt me for any other drivers.
I'm now officially part of the rooted club.
Thanks for putting together this great thread!
Rolly32
Newbie
I have the same problem as you, I'm new to rooting and I followed the steps, but it tells me to connect my phone while in debugging mode. My phone is in debugging mode, it will not proceed to root. I don't have HTC Sync, and I disabled my antivirus, I still don't know what the problem is. I'm using Hboot 2.02
Edit: I figured out my problem, I tried rooting it on Windows Xp and it wouldnt work. So I decided to give it a shot on my Windows Vista laptop.
Now I have another question, When I try to root, it says "Getting root failed.... Is your firmware new?"
I have never updated before.
Matlock
Android Enthusiast
Added a new section to AFTER ROOT. ENJOY!
SECTION 6: UPDATING TO THE LATEST OTA (Over-The-Air Update)*
After ROOTing your device, it can be kind of stressful to keep it up-to-date with the latest OTA Upates because if improper combinations of RADIOs, ROMs, FIRMWARE, ect. This guide will help you keep your device going with the proper way to get the latest updates from either your Custom ROM Developers, or the lovely STOCK HTC SENSE ROMs.
The STOCK HTC SENSE ROMs are available from the following links. We'll try and keep the list updates with the latest OTAs as possible.
ROMs usually come in DeOdexed, and Odexed.
Odexed - In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
DeOdexed - Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
SteelROM - Usually up-to-date with the latest OTA
3.70.651.1 [ROOTED] [ODEXED] [DEODEXED]
STOCK HTC ROMs
3.70.651.1 [ROOTED] [ODEXED] [DEODEXED]
3.30.651.2 [ROOTED] [ODEXED] [DEODEXED]
3.29.651.5 [ROOTED] [DEODEXED]
RADIOs
[ Radios ][ 12-17 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
RADIOs come in two versions of zip files.
Separate - to be flashed one at a time.
Combo - or as a combo update.
It is up to the user to decide which to use. As a general rule, try the combo update, first. If there are stability issues, downgrade all, make sure everything is back to normal, then flash each one (Baseband, WiMAC, NV, PRI) one at a time to see which one causes instability.
In the latest OTA, and possibly others, PRI is usually the biggest offender.
STEP 1:
Backup WiMAX RSA keys. Refer to ROOTING & BACKUP - SECTION 5: WiMax RSA Keys (4G Signal).
STEP 2:
Open Terminal Emulator and type SU so T.E. will be granted Super User Access.
Verify WiMAX MAC, RADIO version, and current working status typing wimax_mtd record that information somewhere. (you may need to run it a second time if the first time fails)
This should be shown after typing wimax_mtd.
$ export PATH=/date/local/bin:$PATH
$su
# wimax_mtd
Open WiMAX partition ........ OK
Get HTC WiMAX Tag ........ OK
Verify WiMAX Tag (HTC-WiMAX-SQN1130) ........ PASS
Read WiMAX partition ........ OK
Check Firmware Version (4.6.2.2v26023_) ........ 4.6.2.2v26023_
Check Firmware File ........ MATCH
Dev MAC = 00:18:41:FC:5B
Read properties from flash ..... OK
+ in wmx_PropSetFromFlash.
+ in wmx_CheckPropTag.
- out wmx_CheckPropTag.
pPropName = presist.wimax.Cold_Boot_Flag
PropNameLen = 28
wmx_PropSetFromFlash: Find matched proper name in flash.
pMemaddr == pPropName = 1
pPropData = 1
Presist.wimax.Cold_Boot_Flag = 1
isColdBoot = 0
STEP 1:
Wait until the ROM Developer upgrades the base ROM to the software version of the OTA (or if switching custom ROMS, choose any from the complete list of ROMs, making sure the fourth column shows that the ROM has been updated to the latest OTA)
STEP 2:
Once it's ready, get the actual zip from the Developer's site/XDA thread. Do not use ROM manager.
STEP 3:
Get the appropriate RADIO version for the particular OTA/SW version from the link above (Or Here).
STEP 4:
Put both ROM and RADIOS (or combo zip update) on the root of the SD card
STEP 5:
Follow normal procedure to flash a ROM from AFTER ROOTING - SECTION 3: FLASHING ROMS (Use Recovery Method) - After FLASHING ROMS, stay in recovery when done.
STEP 6:
Skip to FLASHING RADIOS
STEP 1:
Download the zip of the latest OTA from the STOCK HTC ROMs links at the beginning of this section.
STEP 2:
Get the appropriate RADIO version for the particular OTA/SW version from the link above (Or Here).
STEP 3:
Put both ROM and Radios (or combo zip update) on the root of the SD card
STEP 4:
Follow normal procedure to flash a ROM (YOU MUST STILL DO A DATE WIPE) from AFTER ROOTING - SECTION 3: FLASHING ROMS (Use Recovery Method) - After FLASHING ROMS, stay in recovery when done.
STEP 5:
Skip to FLASHING RADIOS
STEP 1:
From RECOVERY select either the Single zip or the Combo update like any other flashable zip
STEP 2:
Once it is done, you will be prompted to reboot from RECOVERY
STEP 3:
Once the device turns back on, you will be taken to a black screen with a list of updates, where the phone may sit for up to 5+ minutes. It will reboot itself back into RECOVERY when done.
STEP 4:
Once in RECOVERY, reboot the phone normally
STEP 5:
The phone should boot back into Android, where you can verify the new radio versions by going to
Menu > Settings > About > Software Information - Verify Baseband and PRI.
CAUTION
If the phone is unstable (random reboots, wake time = uptime, etc):
1) Start by downgrading the PRI.
b) If that doesn't solve the problem, downgrade all, following the same procedure as updating, but one at a time.
iii) Upgrade one at a time to see which update causes issues
STEP 6:
To verify WiMAX, verify wimax keys are in tact. Perform a NAND Backup. Also, run SU & wimax_mtd from Terminal Emulator again and verify:
i) Wimax version - should be the new version
2) All tests pass
c) MAC address has not changed (should never be a problem anymore)
IMPORTANT
Once all is said and done, you need to go to
Menu > Settings > About Phone > Software Information
And verify that the RADIO is indeed updated. If not, re-apply the Radio ZIP until it is.
Flash ROM like normal
-If STOCK, use the the provided links
-If CUSTOM ROM, get the zip from the developer, or use ROM manager if desired in this case
BAD COMBINATIONS
- Older SW version than the new OTA + Radios from new OTA + stock HTC kernel
- SW version from new OTA + Old Radios (can cause instability. Some people do it and never have issues. Has been known to cause the phone to never sleep)
- Older SW version than the new OTA + PRI from new OTA + any non stock HTC kernel (fix - new radios are fine, but keep previous PRI - this is experience from current OTA - may not be the case always)
SAFE COMBINATIONS
- Older SW version than the new OTA + Radios from new OTA minus the new PRI + any kernel other than stock (e.g. netarchy).
ALTERNATE METHODS
- Sprintlovers ROM - Comes in a PC36IMG format, and flashed from hboot like any other. Includes ROM and radios. What don't know is if it updates hboot. If it does, this is a very important point. I will se if I can find out:
[ROM] 12/31/10 | SPRINT LOVERS | 2.2 | 3.70.651.1 | Radio/Wimax/PRI All-In-One - xda-developers
- Unroot, accept the OTA, reroot (WARNING: This will update HBoot)
REASONS WHY NOT TO UPDATE HBOOT
- Any NANDROID backups made before updating HBoot will be useless on a different HBoot version
- HBoot is typically upgraded for various debugging differences, etc., but a primary reason is to patch security exploits (i.e. THE WAY WE ROOT. Why would you want to upgrade to an HBoot designed to keep out root. Yes, each one gets root eventually, but I think my point stands.)
*This paticular guide was written by akazabam for ROOTING for DUMMIES. Some alterations were made to for the scheme of things.
(Guide may not be complete. This was completely new to Me, I was learning as I typed, so some things may not be 100% accurate, but they will be ASAP!)
REMEMBER!!!!!!!!!!!!!!!!!!!
If you have anything you'd think may be a good addition to the Guide, let me know via PM!!!!
I will consider everything submitted. Most go into the guide without problem!
SECTION 6: UPDATING TO THE LATEST OTA (Over-The-Air Update)*
UPDATING TO THE LATEST OTA*
After ROOTing your device, it can be kind of stressful to keep it up-to-date with the latest OTA Upates because if improper combinations of RADIOs, ROMs, FIRMWARE, ect. This guide will help you keep your device going with the proper way to get the latest updates from either your Custom ROM Developers, or the lovely STOCK HTC SENSE ROMs.
The STOCK HTC SENSE ROMs are available from the following links. We'll try and keep the list updates with the latest OTAs as possible.
ROMs usually come in DeOdexed, and Odexed.
Odexed - In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
DeOdexed - Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
SteelROM - Usually up-to-date with the latest OTA
3.70.651.1 [ROOTED] [ODEXED] [DEODEXED]
STOCK HTC ROMs
3.70.651.1 [ROOTED] [ODEXED] [DEODEXED]
3.30.651.2 [ROOTED] [ODEXED] [DEODEXED]
3.29.651.5 [ROOTED] [DEODEXED]
RADIOs
[ Radios ][ 12-17 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
RADIOs come in two versions of zip files.
Separate - to be flashed one at a time.
Combo - or as a combo update.
It is up to the user to decide which to use. As a general rule, try the combo update, first. If there are stability issues, downgrade all, make sure everything is back to normal, then flash each one (Baseband, WiMAC, NV, PRI) one at a time to see which one causes instability.
In the latest OTA, and possibly others, PRI is usually the biggest offender.
OTAs THAT INCLUDE THE RADIO UPDATE
GENERAL PRE-UPDATE
GENERAL PRE-UPDATE
STEP 1:
Backup WiMAX RSA keys. Refer to ROOTING & BACKUP - SECTION 5: WiMax RSA Keys (4G Signal).
STEP 2:
Open Terminal Emulator and type SU so T.E. will be granted Super User Access.
Verify WiMAX MAC, RADIO version, and current working status typing wimax_mtd record that information somewhere. (you may need to run it a second time if the first time fails)
This should be shown after typing wimax_mtd.
$ export PATH=/date/local/bin:$PATH
$su
# wimax_mtd
Open WiMAX partition ........ OK
Get HTC WiMAX Tag ........ OK
Verify WiMAX Tag (HTC-WiMAX-SQN1130) ........ PASS
Read WiMAX partition ........ OK
Check Firmware Version (4.6.2.2v26023_) ........ 4.6.2.2v26023_
Check Firmware File ........ MATCH
Dev MAC = 00:18:41:FC:5B
Read properties from flash ..... OK
+ in wmx_PropSetFromFlash.
+ in wmx_CheckPropTag.
- out wmx_CheckPropTag.
pPropName = presist.wimax.Cold_Boot_Flag
PropNameLen = 28
wmx_PropSetFromFlash: Find matched proper name in flash.
pMemaddr == pPropName = 1
pPropData = 1
Presist.wimax.Cold_Boot_Flag = 1
isColdBoot = 0
CUSTOM ROMS
STEP 1:
Wait until the ROM Developer upgrades the base ROM to the software version of the OTA (or if switching custom ROMS, choose any from the complete list of ROMs, making sure the fourth column shows that the ROM has been updated to the latest OTA)
STEP 2:
Once it's ready, get the actual zip from the Developer's site/XDA thread. Do not use ROM manager.
STEP 3:
Get the appropriate RADIO version for the particular OTA/SW version from the link above (Or Here).
STEP 4:
Put both ROM and RADIOS (or combo zip update) on the root of the SD card
STEP 5:
Follow normal procedure to flash a ROM from AFTER ROOTING - SECTION 3: FLASHING ROMS (Use Recovery Method) - After FLASHING ROMS, stay in recovery when done.
STEP 6:
Skip to FLASHING RADIOS
STOCK ROMS
STEP 1:
Download the zip of the latest OTA from the STOCK HTC ROMs links at the beginning of this section.
STEP 2:
Get the appropriate RADIO version for the particular OTA/SW version from the link above (Or Here).
STEP 3:
Put both ROM and Radios (or combo zip update) on the root of the SD card
STEP 4:
Follow normal procedure to flash a ROM (YOU MUST STILL DO A DATE WIPE) from AFTER ROOTING - SECTION 3: FLASHING ROMS (Use Recovery Method) - After FLASHING ROMS, stay in recovery when done.
STEP 5:
Skip to FLASHING RADIOS
FLASHING RADIOS
STEP 1:
From RECOVERY select either the Single zip or the Combo update like any other flashable zip
STEP 2:
Once it is done, you will be prompted to reboot from RECOVERY
STEP 3:
Once the device turns back on, you will be taken to a black screen with a list of updates, where the phone may sit for up to 5+ minutes. It will reboot itself back into RECOVERY when done.
STEP 4:
Once in RECOVERY, reboot the phone normally
STEP 5:
The phone should boot back into Android, where you can verify the new radio versions by going to
Menu > Settings > About > Software Information - Verify Baseband and PRI.
CAUTION
If the phone is unstable (random reboots, wake time = uptime, etc):
1) Start by downgrading the PRI.
b) If that doesn't solve the problem, downgrade all, following the same procedure as updating, but one at a time.
iii) Upgrade one at a time to see which update causes issues
STEP 6:
To verify WiMAX, verify wimax keys are in tact. Perform a NAND Backup. Also, run SU & wimax_mtd from Terminal Emulator again and verify:
i) Wimax version - should be the new version
2) All tests pass
c) MAC address has not changed (should never be a problem anymore)
IMPORTANT
Once all is said and done, you need to go to
Menu > Settings > About Phone > Software Information
And verify that the RADIO is indeed updated. If not, re-apply the Radio ZIP until it is.
OTAs THAT DO NOT INCLUDE THE RADIO UPDATE
Flash ROM like normal
-If STOCK, use the the provided links
-If CUSTOM ROM, get the zip from the developer, or use ROM manager if desired in this case
---------------NOTES----------------
BAD COMBINATIONS
- Older SW version than the new OTA + Radios from new OTA + stock HTC kernel
- SW version from new OTA + Old Radios (can cause instability. Some people do it and never have issues. Has been known to cause the phone to never sleep)
- Older SW version than the new OTA + PRI from new OTA + any non stock HTC kernel (fix - new radios are fine, but keep previous PRI - this is experience from current OTA - may not be the case always)
SAFE COMBINATIONS
- Older SW version than the new OTA + Radios from new OTA minus the new PRI + any kernel other than stock (e.g. netarchy).
ALTERNATE METHODS
- Sprintlovers ROM - Comes in a PC36IMG format, and flashed from hboot like any other. Includes ROM and radios. What don't know is if it updates hboot. If it does, this is a very important point. I will se if I can find out:
[ROM] 12/31/10 | SPRINT LOVERS | 2.2 | 3.70.651.1 | Radio/Wimax/PRI All-In-One - xda-developers
- Unroot, accept the OTA, reroot (WARNING: This will update HBoot)
REASONS WHY NOT TO UPDATE HBOOT
- Any NANDROID backups made before updating HBoot will be useless on a different HBoot version
- HBoot is typically upgraded for various debugging differences, etc., but a primary reason is to patch security exploits (i.e. THE WAY WE ROOT. Why would you want to upgrade to an HBoot designed to keep out root. Yes, each one gets root eventually, but I think my point stands.)
*This paticular guide was written by akazabam for ROOTING for DUMMIES. Some alterations were made to for the scheme of things.
(Guide may not be complete. This was completely new to Me, I was learning as I typed, so some things may not be 100% accurate, but they will be ASAP!)
REMEMBER!!!!!!!!!!!!!!!!!!!
If you have anything you'd think may be a good addition to the Guide, let me know via PM!!!!
I will consider everything submitted. Most go into the guide without problem!
Thanks! I was having the same issue until I tried your solution. It was really simple once I got past that issue. I'm now successfully rooted as well.
Bob The Great
Newbie
Thanks! I was having the same issue until I tried your solution. It was really simple once I got past that issue. I'm now successfully rooted as well.
Great! Apparently, not everybody has this issue, or else it would be more widely known by now, but I'm glad the solution I stumbled across was able to work for you too.
Bob The Great
Newbie
Wow, glad I could make a contribution!
Quick question: I just rooted my EVO that was running on the most current HTC kernel OTA #15 and with the 2.15.00.11.19 baseband. I want to flash Fresh EVO 3.5.0.1 onto the phone. Do I need to install an older version of it and then update it via OTA's to the current one? Do I need to do a data wipe and clear the cache? Or can I just overwrite the current ROM without doing a data wipe and cache clear with the 3.5.0.1 since it uses the same kernel and baseband? What does a cache clear do anyway?
Thanks.
Thanks.
I thought I'd try this thread too.... I used warm updater for RLS5 and selected many of the add-ons. Most worked at first, but the phone was VERY slow. Figuring that I did something wrong, I tried to restore previous backup through RM. While loading it wouldn't get past the white load screen. I tried to re-install rls4 zip from SD, it goes through the process, then sticks on the white screen. I've cleared all cache, dalvic, data/factory reset. I let it work overnight, still on white screen! Please help!
Thanks to Matlock and all the other guys that put all this stuff together...
Question about backups:
I've got a rooted Evo and still using HTC Sense. I want to know if I do a Nanroid backup, flash a new ROM and then do another nandroid backup on that ROM will I lose the first backup data or is it still there so that I can always go back to HTC Sense stock no matter how many backups I create?
I know I can just flash the latest Sense ROM from one of many links but I just want to know if there is a way to keep backups and select which one you want to restore or do they "overwrite" each other each time.. thanks
Question about backups:
I've got a rooted Evo and still using HTC Sense. I want to know if I do a Nanroid backup, flash a new ROM and then do another nandroid backup on that ROM will I lose the first backup data or is it still there so that I can always go back to HTC Sense stock no matter how many backups I create?
I know I can just flash the latest Sense ROM from one of many links but I just want to know if there is a way to keep backups and select which one you want to restore or do they "overwrite" each other each time.. thanks
You can create as many nandroid backups as you have room for on your sdcard. They will not overwrite each other. When you go to restore one, it will give you a list of previous backups to choose from.
Thanks man, it's crazy how much I've read and couldn't find that answer...
SaleenFiend
Android Enthusiast
Kernel Review:
NAME: SBC for Netarchy's 4.2.2 More Aggressive CFS
VERSION: 4.2.2 More Aggressive HAVS-CFS-V7
WEBSITE: [KERNEL][SENSE] - SBC. Update: 12/31/10! HTC kernel #15 SBC v7 - xda-developers
OVERALL RATING: 5
WHAT DOES NOT WORK IN THE ROM (ROM ONLY):
Currently running a Stock Rooted Rom and have yet to find any unstable situations or incompatibilities. I have found that any overclocking beyond 1.2 can cause screen tears on different reboots, but is easily fixed by rebooting. My settings for SetCPU stays set at 1.15ghz now. I have not updated to the latest OTA. Kernel works really well on a stock rooted ROM.
YOUR IMPRESSION OVERALL OF THE ROM/KERNEL:
I originally was using LauncherPro Plus with the kernel but eventually became fed up with lag and experienced no extended battery life, but no loss in battery life. I began using stock Sense UI, and found my battery life has almost doubled. Instead of one full day of operation with normal web, text, and phone use, I am seeing two full days on a little lighter use. Also note, I have began disabling 3G when not in use. This kernel is great and operates as advertised. If you are not happy there are plenty of options within the Netarchy family
How easy was it to install? Reboot into recovery & flash
How long have you been using it? 1 Week
Is it user-friendly? Yes, you do not need to do anything other than flash this.
Does it Force Close alot? None yet
What are your favorite features? Overclocking abilities - eliminates lag
What are your least favorite features? There are really no disadvantages with this kernel
What kind of battery life does it have? I have noticed doubled battery life.
Would you recommend this ROM/KERNEL to others? Yes, I recommend everyone try it!
What combination of ROM & KERNEL are you using? Stock Rooted Rom, SBC for Netarchy's 4.2.2 More Aggressive CFS
And of course, whatever else you want to add in your review.
http://androidforums.com/evo-4g-all...erior-battery-charging-4-18v-off-charger.html
add that to the list!
NAME: SBC for Netarchy's 4.2.2 More Aggressive CFS
VERSION: 4.2.2 More Aggressive HAVS-CFS-V7
WEBSITE: [KERNEL][SENSE] - SBC. Update: 12/31/10! HTC kernel #15 SBC v7 - xda-developers
OVERALL RATING: 5
WHAT DOES NOT WORK IN THE ROM (ROM ONLY):
Currently running a Stock Rooted Rom and have yet to find any unstable situations or incompatibilities. I have found that any overclocking beyond 1.2 can cause screen tears on different reboots, but is easily fixed by rebooting. My settings for SetCPU stays set at 1.15ghz now. I have not updated to the latest OTA. Kernel works really well on a stock rooted ROM.
YOUR IMPRESSION OVERALL OF THE ROM/KERNEL:
I originally was using LauncherPro Plus with the kernel but eventually became fed up with lag and experienced no extended battery life, but no loss in battery life. I began using stock Sense UI, and found my battery life has almost doubled. Instead of one full day of operation with normal web, text, and phone use, I am seeing two full days on a little lighter use. Also note, I have began disabling 3G when not in use. This kernel is great and operates as advertised. If you are not happy there are plenty of options within the Netarchy family
How easy was it to install? Reboot into recovery & flash
How long have you been using it? 1 Week
Is it user-friendly? Yes, you do not need to do anything other than flash this.
Does it Force Close alot? None yet
What are your favorite features? Overclocking abilities - eliminates lag
What are your least favorite features? There are really no disadvantages with this kernel
What kind of battery life does it have? I have noticed doubled battery life.
Would you recommend this ROM/KERNEL to others? Yes, I recommend everyone try it!
What combination of ROM & KERNEL are you using? Stock Rooted Rom, SBC for Netarchy's 4.2.2 More Aggressive CFS
And of course, whatever else you want to add in your review.
http://androidforums.com/evo-4g-all...erior-battery-charging-4-18v-off-charger.html
add that to the list!
wrapkgb
Android Expert
Ok... Not sure if this is a biggie or not, but after looking at matlocks update for after rooting regarding the Wimax mac... Im a little concerned. lol.
So here is matlocks example:
And then here is mine (the bold is the differencess):
$ export PATH=/data/local/bin:$PATH
$su
#wimax_mtd
Open WiMAX partition ........ OK
Get HTC WiMAX Tag ........ OK
Verify WiMAX Tag ()........ NOT MATCH
PASS
Read WiMAX partition ........ ERROR
OK
Check Firwmare Version (4.6.2.2v26023_) ........
Verify MFG Fireware Key ........ PASS
Verify APP Fireware Key ........ PASS
Verify BOOTS Fireware Key ........ PASS
Dump MFG firmware (2833448) ........ OK
Dump APP firmware (4957348) ........ OK
Dump BOOTS firmware (86081) ........ OK
[1] Segmentation fault wimax_mtd
#
And then I seem to be missing some... Not sure. I don't have 4g in my area so I dunno if it works or not.
So here is matlocks example:
And then here is mine (the bold is the differencess):
$ export PATH=/data/local/bin:$PATH
$su
#wimax_mtd
Open WiMAX partition ........ OK
Get HTC WiMAX Tag ........ OK
Verify WiMAX Tag ()........ NOT MATCH
PASS
Read WiMAX partition ........ ERROR
OK
Check Firwmare Version (4.6.2.2v26023_) ........
Verify MFG Fireware Key ........ PASS
Verify APP Fireware Key ........ PASS
Verify BOOTS Fireware Key ........ PASS
Dump MFG firmware (2833448) ........ OK
Dump APP firmware (4957348) ........ OK
Dump BOOTS firmware (86081) ........ OK
[1] Segmentation fault wimax_mtd
#
And then I seem to be missing some... Not sure. I don't have 4g in my area so I dunno if it works or not.
Yeah, I've found that it does the same to me from time to time (quits with a segmentation fault). I always rerun it if that happens, and it usually passes the second time. If it continually fails (or the info doesn't add up in some way), then you've got a problem on your hands. Otherwise, the second output looks normal.
Matlock
Android Enthusiast
I got that as well the first time. Nor do I have 4G where I am at. And do not intend on driving 'downtown' just to try it out. lol
Try closing out T.E. and start over. Run su then RSA a few times and it may give you what you want. I get I get ERROR and PASS on random instances. *shrug*
Heck, even had Firmware misspelled by the program. lol
Maybe you should throw in a disclaimer that you might get errors from time to time, and you really just need it to verify MAC address, check firmware version, and verify Wimax partition. Having pass at least once helps. Stupid thing seems to fail a lot, and I don't think it's best indication of working 4g.
wrapkgb
Android Expert
Thanks for the confirmation!
Well, I think all you really need to do is:
1) Verify your keys are in tact (grep RSA /dev/mtd/mtd0)
2) Verify your MAC address both before and after the update
3) Verify your wimax version before and after the update
None of those things are dependent on wimax_mtd passing everything (though, mac address and version may not all show if it doesn't pass at least some stuff). I haven't been able to prove any correlation between wimax_mtd failing and 4g not working yet, though, because of the high failure rate of wimax_mtd. It all seems so coincidental. Maybe we should find a better way of extracting wimax version and mac address, and drop the whole wimax_mtd thing all together until we can all understand it better. I'd hate to confuse people even more. I know it's possible. I just don't remember the commands off hand.