-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root evo 4g rooted 2.3.3 rebooting
- Thread starter ericsloan
- Start date
-
- Tags
- htc evo 4g
argedion
The TechnoFrog
First Welcome to the forums.
For future references anything root should be posted in the root section. I'm sure one of the mods will move this over there for you. Ok how did you root? do you have S-off and what su are you using? (the latest one has had some issues) did you do a nadroid backup?
For future references anything root should be posted in the root section. I'm sure one of the mods will move this over there for you. Ok how did you root? do you have S-off and what su are you using? (the latest one has had some issues) did you do a nadroid backup?
welcome to the forums!!!!!!!!!!!!!!!!!
moved you to the rooting section.
you can't use revolutionary again. so lets slow down and before you do anything else, let's see where you are at. can you boot up? what is your hboot? and you do have s-off right? what rom are you on? and what theme were you trying to flash? do you have a link for it?
dustwun77
Endeavor to Persevere :)
On my phone.
Read in rooting gingerbread about after root and wiping and flashing roms. I think you are fine, just need a new one. Look at roms and kernel thread. Basically just pick one of sense ones and flash it. Keep superuser dl on card, may need to reflash it, had a bad version going around.
Read in rooting gingerbread about after root and wiping and flashing roms. I think you are fine, just need a new one. Look at roms and kernel thread. Basically just pick one of sense ones and flash it. Keep superuser dl on card, may need to reflash it, had a bad version going around.
andygu3
Android Expert
It sounded like all you needed to have was a recovery
MizzouBrent
Android Expert
Ok, you've come to the right place for help, but I think you need to read up on several things.
1) Before, when you were seeing the triangle/exclaimation point, that means you didn't have a recovery. Recovery is which allows you to make changes to the nand on your phone, which is what you write to when flashing roms and such. I would HIGHLY suggest Amon RA 2.3 as your recovery. It is flawless in my opinion. Link:
[Recovery] [09-Feb-2011] RA-supersonic-v2.3 - xda-developers
Download the PC36IMG file in the post at the beginning of the thread and follow the instructions for "the bootloader way".
2) ALWAYS, ALWAYS ALWAYS make nandroid backups. They will allow you to restore your phone back to when you made the backup, so if you mess up something, you can always get back to a working state.
3) Not all themes are going to be compatible with all roms. This is where reading is important. If you read and you're still not sure, ask questions, we are a very helpful bunch.
4) When you start flashing stuff, make sure you always wipe cache and dalvik cache. When flashing themes, kernels, and other mods, you are almost always required to wipe both cache and dalvik cache.
5) Stay away from rom manager. I have no idea if you're using it or not, but just stay away from it. It's been widely reported to be buggy, and you should be learning to flash this stuff manually through recovery anyway.
Hopefully this helps, keep asking away. Rooting your phone is the single best thing you can do with it. If you're looking for rom suggestions, I would go with the most recent version of MikG (2.57) which is based on an upgraded version of HTC Sense from what comes with the stock Evo. For more of a pure android experience, I would suggest Cyanogenmod 7.1. That's what I'm currently running and I love it.
1) Before, when you were seeing the triangle/exclaimation point, that means you didn't have a recovery. Recovery is which allows you to make changes to the nand on your phone, which is what you write to when flashing roms and such. I would HIGHLY suggest Amon RA 2.3 as your recovery. It is flawless in my opinion. Link:
[Recovery] [09-Feb-2011] RA-supersonic-v2.3 - xda-developers
Download the PC36IMG file in the post at the beginning of the thread and follow the instructions for "the bootloader way".
2) ALWAYS, ALWAYS ALWAYS make nandroid backups. They will allow you to restore your phone back to when you made the backup, so if you mess up something, you can always get back to a working state.
3) Not all themes are going to be compatible with all roms. This is where reading is important. If you read and you're still not sure, ask questions, we are a very helpful bunch.
4) When you start flashing stuff, make sure you always wipe cache and dalvik cache. When flashing themes, kernels, and other mods, you are almost always required to wipe both cache and dalvik cache.
5) Stay away from rom manager. I have no idea if you're using it or not, but just stay away from it. It's been widely reported to be buggy, and you should be learning to flash this stuff manually through recovery anyway.
Hopefully this helps, keep asking away. Rooting your phone is the single best thing you can do with it. If you're looking for rom suggestions, I would go with the most recent version of MikG (2.57) which is based on an upgraded version of HTC Sense from what comes with the stock Evo. For more of a pure android experience, I would suggest Cyanogenmod 7.1. That's what I'm currently running and I love it.
MizzouBrent
Android Expert
I'd also like to add, installing superuser is really only relevant when trying to put it on the stock rom. Pretty much any rom you ever flash will have superuser preinstalled, so you don't need to worry about installing it again.
And most themes will say specifically what rom they are for. What is the link for the one you downloaded?
And most themes will say specifically what rom they are for. What is the link for the one you downloaded?
dustwun77
Endeavor to Persevere :)
Lately, Su has been hosed on some roms and folk have been needing a good version to flash. Had to twice myself.
it could be a bad download. try and re-download it and try again. plus 2.58 is out.
Granite1
Zercron Encrusted Tweezer
No ra2.3 is not a zip you flash in recovery. It is a PC36IMG.zip. your hboot will flash it automatically once it scans and finds it.
Rename the amon-ra recovery file to exactly: PC36IMG
Don't add the .zip, Windows automatically hides the extensions.
Boot up in hboot (white screen with Andy riding a skateboard)
Let the phone scan for the PC36IMG, once it finds it select update.
Reboot into hboot and select recovery. You should see amon-ra 2.3.
themes are rom specific. so you need to go to the either the op of the rom and scroll down. usually, the dev will have links or themes posted on the page. also you can go here and search for a theme you are intersted:EVO 4G Themes and Apps - xda-developers
Hi to all.
I have placed the PC36IMG.ZIP file in the root directory of the SD. When I turn on the Phone the HBOOT is finding the file it says:
Checking...[PC36IMG.ZIP]
But I'm not getting the option of UPDATE (I cannot select UPDATE). So I get back to the initial screen. It seems the system is just checking it but it is not actually updating anything.
COuld you know the possible reason?
Thanks
hboot is programmed to check for the PC36IMG file so it will always say that. if at the end it says no image or wrong image then hboot is not finding your
file. so either you are not naming it correctly or it is not in the right place.
the file needs to be named PC36IMG exactly. do not add an extra .zip as windows hides extensions. so make sure that it does not look like, PC36IMG.zip.zip. hboot will not see it otherwise.
also the file needs to be on the root of the card that means not in any folder. if it is not on the card directly then hboot will not be able to find it. it is programmed to look for it just on the card and not in a folder.
Hi all, new member to the forum!! I've tinkered with electronics quite a bit and seem to always look for ways of making things do more than factory-intended. Anywho, this is only my second time doing this much to a phone (the first being a much simpler process to add homebrew to a Palm Pre).
The issue: The title on this thread sums it up. I keep rebooting on my rooted 4G.
The first time this happened, it took restoring from a nandroid backup to be able to boot into the ROM again. The phone details then were:
Rooted 2.3.3 with revolutionary (smooth process, no hiccups)
Amon ra 2.3
Freedom kernel (less)
Mikg3.0 ROM
Auto-wired theme + few mods, look screen, keyboard etc.
I noticed the reboot has happened usually while on Handcent, but I'm there about 60% of the time.
While on heavier use, as in dl'ing and playing music, watching movies and such, I've never had a problem, which leads me to believe the problem isn't related to overclocking (set to 1152mhz)
Since then, I've only changed the kernel and still get random reboots. Kernel now is aggressive freedom. I believe the only reason it hasn't borked the ROM again is because I catch the phone before it gets past the white boot screen and pull the battery out, then proceed to boot recovery to wipe cache and dalvik cache. Maybe I'm being too cautious but I'd rather not do another nandroid recovery unless I absolutely have to. So guys, sorry for the lengthy post but do any of you have an idea of what could be causing the reboots?
The issue: The title on this thread sums it up. I keep rebooting on my rooted 4G.
The first time this happened, it took restoring from a nandroid backup to be able to boot into the ROM again. The phone details then were:
Rooted 2.3.3 with revolutionary (smooth process, no hiccups)
Amon ra 2.3
Freedom kernel (less)
Mikg3.0 ROM
Auto-wired theme + few mods, look screen, keyboard etc.
I noticed the reboot has happened usually while on Handcent, but I'm there about 60% of the time.
While on heavier use, as in dl'ing and playing music, watching movies and such, I've never had a problem, which leads me to believe the problem isn't related to overclocking (set to 1152mhz)
Since then, I've only changed the kernel and still get random reboots. Kernel now is aggressive freedom. I believe the only reason it hasn't borked the ROM again is because I catch the phone before it gets past the white boot screen and pull the battery out, then proceed to boot recovery to wipe cache and dalvik cache. Maybe I'm being too cautious but I'd rather not do another nandroid recovery unless I absolutely have to. So guys, sorry for the lengthy post but do any of you have an idea of what could be causing the reboots?
out of curiosity have you tried other roms?