Hey all,
I should be upgrading my EVO OG to the new LTE model late next week. But I just wanted to get some of the basic questions out of the way. I'm sure there's already existing threads like this, but the forums can be difficult to search sometimes. So apologies if this stuff has been answered 20 times already.
1. Is root achievable on all known versions of the stock OS?
2. S-off is limited to Hboot x.15 and earlier correct?
3. Since the batter is not removable how do I force the phone off in case of a boot loop or other problem
4. Is the partition mod available for this phone? It was a very useful tool with my old Hero and the EVO OG.
5. What is the preferred recovery?
6. Are there any details that I should know about or fixes I should apply right away?
Thanks for answering these questions guys. Again I apologize if this stuff has been answered before.
1. So long as the hboot can be unlocked the phone can be customized.
2. S-OFF is only available for hboot 1.12 and the is a toolkit being worked on right now for downgrade. It's been achieved and is being refined.
3. Hold power for 10 seconds and phone will reboot.
4. Not familiar with the particular mod you mentioned.
5. Twrp by TeamWin, right now there are a few issues with the latest 2.3 but 2.2 is still available.
6. Only issue is that unlocked phones with HBOOT 1.15 and higher must flash the kernel separately, there are several methods of doing so. Check my thread Don't Panic for all kinds of info
Brian419 said:
Hey all,
I should be upgrading my EVO OG to the new LTE model late next week. But I just wanted to get some of the basic questions out of the way. I'm sure there's already existing threads like this, but the forums can be difficult to search sometimes. So apologies if this stuff has been answered 20 times already.
1. Is root achievable on all known versions of the stock OS?
2. S-off is limited to Hboot x.15 and earlier correct?
3. Since the batter is not removable how do I force the phone off in case of a boot loop or other problem
4. Is the partition mod available for this phone? It was a very useful tool with my old Hero and the EVO OG.
5. What is the preferred recovery?
6. Are there any details that I should know about or fixes I should apply right away?
Thanks for answering these questions guys. Again I apologize if this stuff has been answered before.
Click to expand...
Click to collapse
1. Yes u can root
2. S-off for all hboot's is possible now. Making it easier for the non-dev masses is a wip.
3. Boot loops or freezes never happen to me like on og EVO. But to simulate a battery pull hold down power for 10 seconds and wait til capacitive buttons stop blinking to release. To boot into bootloader hold power and volume down.
4. Not sure. Never had a use for it. Will need to check and get back to u.
5. Team Win Recovery Project TWRP. CWM does not agree w EVO LTE. Likes to corrupt misc/partition.
6. The multitasking mod is absolutely necessary for me. But I use Flex360's stock w/ goodies rom where it is baked in. There's another mod by zeppelinrocks that works as well.
Hope that does u well.
Thanks for the answers, I'm this will come in handy once I get the phone and start playing around with it.
I haven't heard of the multitasking mod, I'll have to look that up.
The partition mod I mentioned was made by Firerat a few years back. I used it on my old Hero and EVO OG to change the size of the system, data, and cache partitions. Here's link to the EVO version: http://forum.xda-developers.com/showthread.php?t=855424&highlight=firerat
Here's one I forgot. To boot into recovery when the phone is off we press power and volume down like with other devices? Or is that changed with the EVO LTE?
Brian419 said:
Thanks for the answers, I'm this will come in handy once I get the phone and start playing around with it.
I haven't heard of the multitasking mod, I'll have to look that up.
The partition mod I mentioned was made by Firerat a few years back. I used it on my old Hero and EVO OG to change the size of the system, data, and cache partitions. Here's link to the EVO version: http://forum.xda-developers.com/showthread.php?t=855424&highlight=firerat
Here's one I forgot. To boot into recovery when the phone is off we press power and volume down like with other devices? Or is that changed with the EVO LTE?
Click to expand...
Click to collapse
Most of the custom roms will have improved multitasking built in so you shouldn't have to worry about that.
You won't need the partition mod, this phone is a beast!!
The recovery entry procedure is the same as before.
Thanks cruise!
I figured that with the amount of memory the device has I wouldn't need to repartition. But it's been such a useful tool I thought I'd ask about it.
Is there a guide in the Don't Panic thread or anywhere else that explains flashing methods in detail? I've always been able to do everything through recovery and it seems that this device requires more use of Fastboot.
If I'm understanding what I've read correctly, we download a ROM and extract the boot.img. Flash the ROM through recovery then use Fastboot to flash the boot.img? What about just flashing a stand alone kernel?
You guys don't have to explain everything here. A link to a thread would be enough.
Again thanks for the help. All this info will come in handy soon!
Brian419 said:
Thanks cruise!
I figured that with the amount of memory the device has I wouldn't need to repartition. But it's been such a useful tool I thought I'd ask about it.
Is there a guide in the Don't Panic thread or anywhere else that explains flashing methods in detail? I've always been able to do everything through recovery and it seems that this device requires more use of Fastboot.
If I'm understanding what I've read correctly, we download a ROM and extract the boot.img. Flash the ROM through recovery then use Fastboot to flash the boot.img? What about just flashing a stand alone kernel?
You guys don't have to explain everything here. A link to a thread would be enough.
Again thanks for the help. All this info will come in handy soon!
Click to expand...
Click to collapse
Yep, you've got it. This thread outlines the process of flashing via fastboot as well as some other options. The same applies to flashing kernels with a ROM or standalone.
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Some roms like MeanRom, have written a boot script to automatically install the kernel when the rom installs so no need to fastboot the kernel with MeanRom. Fastbooting kernels is only needed if you are s-on. There has been a major breakthrough in achieving s-off in the last couple of days and they are working on a refined method for everyone's use.
Sent from my A500 using Tapatalk
cruise350 said:
Fastbooting kernels is only needed if you are s-on.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Good to know, I was under the impression that it didn't matter if you were s-off or s-on.
Brian419 said:
Good to know, I was under the impression that it didn't matter if you were s-off or s-on.
Click to expand...
Click to collapse
That is one of the benefits of being s-off, you can write to boot partitions.
Sent from my icrap 2 using Tapatalk HD
Well I think I'm set. I've been checking other threads and reviewing various guides and descriptions. Provided all goes well and I get the phone next week I should be able to do everything I want with it.
If I have anymore questions I'll be sure to post them.
Again, thanks for taking the time to answer my questions, I really appreciate it
Update: I got my LTEVO today. Rooted, unlocked, and flashed MeanROM with no serious problems.I just wanted to thank you guys again, the info you gave me really helped.
So thanks!
Related
I have been experiencing ROM issues and of course this is the first time for me downloading ROMS; so please, I am not trying to live in ignorance. In fact, the opposite. I have done the research, checked multiple sites, blah, blah, blah.
I downloaded the latest version of CWM Pro Version. I backed up my current ROM and looked at some of the latest and greatest ROMS. I downloaded the SkyRaider Zeus ROM and liked it, but could not receive or make phone calls. I downloaded another ROM and the same issue. Plus, I had multiple issues with the certain apps not working (for example, LOCALE would open and close).
So, I reverted back to my stock ROM, which I like, but I keep having those annoying "updates" trying to download. Then, I also read on XDA...
ClockworkMod Recovery: The recent "5.x" update of ClockworkMod Recovery (CWR) has known issues. Particularly, it does not restore backups and will enter into a bootloop. For the time being, do NOT update to this version CWR and do NOT use Rom Manager to backup, flash ROMS, or restore backups because in order to perform these operations, CWR needs to be current. Links to how-to and alternate recovery images will follow after I've slept, drank some Jack, and further manipulated my mind into cooperating with reality.
So, some of you more experienced with Android could answer some questions...
Has this issue with CWR been taken care of?
Are these common problems with ROMS?
Will flashing a ROM in recovery take care of these issues?
Any help would be greatly appreciated! Thanks everyone!
Living by Faith in Christ,
Ryon
First off, never install a ROM in bootloader, you will brick your device.
I personally prefer to download the ROM from a forum, then place on sd card then manually go into recovery and flash it. I have never had a problem doing it this way.
Ah man! I used the wrong terminology. Thanks for setting me straight. I changed my first post so that people could answer the questions correctly in the future!
Any other wisdom out there would be great!
Ryon
RyonAdcock said:
Has this issue with CWR been taken care of?
Click to expand...
Click to collapse
Yes. Everything should be working correctly as of 5.0.2.1.
Are these common problems with ROMS?
Click to expand...
Click to collapse
Yes. If you did not flash the appropriate radio for that ROM (which from the description you gave is probably your problem). That may also be what is causing Locale to close depending on what it checks on startup. Remember, radios are flashed in bootloader and roms in recovery.
Will flashing a ROM in recovery take care of these issues?
Click to expand...
Click to collapse
No, you need to download a radio that is suggested for use with the ROM.
At this time, most use MR2-latest but the ROM threads should recommend one in their description.
Thanks for the quick reply! As with answered questions come more questions.
Could you help me understand the theory behind radios? I am not quite sure why the radio needs to be changed.
Also, what is the common program or app that most people are using to update or change their radios? I have heard of a few, but would like more wisdom.
Thanks again!
Ryon
RyonAdcock said:
Thanks for the quick reply! As with answered questions come more questions.
Could you help me understand the theory behind radios? I am not quite sure why the radio needs to be changed.
Also, what is the common program or app that most people are using to update or change their radios? I have heard of a few, but would like more wisdom.
Thanks again!
Ryon
Click to expand...
Click to collapse
Radios need to be changed since the 4g devices can't use *228 to update roaming like 3g devices. If you had a TB on froyo you will need to update radio prior to root cause you won't signal after you flash your first Rom or after flash you better have WiFi or be near a computer or you won't be able to use ur phone.
Sent from my Thunderbolt using XDA App
So im new to the Rezound but not to the rom and rooting world. I had made a N00b mistake by flashing ICS to my rezound without following the proper directions. Now I got myself in a situation that im hoping to get out of. When I try to boot it lets me get to my homescreen but then after 10's it restarts the phone. To top it off, I cannot mount my sd. It seems like the phone is getting worst by the minute. Is there a way out of this? Is there some sort of way to access my internal sd from my comp. Just at a clear loss of ideas. Please help.
supreme329 said:
So im new to the Rezound but not to the rom and rooting world. I had made a N00b mistake by flashing ICS to my rezound without following the proper directions. Now I got myself in a situation that im hoping to get out of. When I try to boot it lets me get to my homescreen but then after 10's it restarts the phone. To top it off, I cannot mount my sd. It seems like the phone is getting worst by the minute. Is there a way out of this? Is there some sort of way to access my internal sd from my comp. Just at a clear loss of ideas. Please help.
Click to expand...
Click to collapse
What did you flash? Was it the new RUU? If you can get to your homescreen then you are still not in bad shape.
The build from the android police leak. I never ran into these problems before. I had the Bionic for a while thought I would give HTC a whirl. My brain is at a stand still lol. I looked for hours and cannot find anything. I usually feel bad posting in a forum but hey im stuck.
supreme329 said:
The build from the android police leak. I never ran into these problems before. I had the Bionic for a while thought I would give HTC a whirl. My brain is at a stand still lol. I looked for hours and cannot find anything. I usually feel bad posting in a forum but hey im stuck.
Click to expand...
Click to collapse
I guess what I'm referring to is that you say you didn't follow directions. Which directions didn't you follow? The steps are pretty straight forward.
Reading back, I flashed it with the bootloader unlocked and I wasnt supposed to. Also I was supposed to chancg something in a file and i neglected to do as well. Just looking for some type of solution to bail me out.
supreme329 said:
Reading back, I flashed it with the bootloader unlocked and I wasnt supposed to. Also I was supposed to chancg something in a file and i neglected to do as well. Just looking for some type of solution to bail me out.
Click to expand...
Click to collapse
Flash the ruu then the Rom of your choice. All the instructions are in the ruu thread to lock, flash, unlock, recovery, etc. Then flash a Rom and not the AP one.
You also have the option to flash one of the ICS ROMe with the old firmware patch but I recommend the RUU path.
Not to thread hijack, but just out of curiosity, why don't you recommend using the patch? I know some people prefer to because it doesn't mark the bootloader as tampered, but are there some adverse effects?
bosox284 said:
Not to thread hijack, but just out of curiosity, why don't you recommend using the patch? I know some people prefer to because it doesn't mark the bootloader as tampered, but are there some adverse effects?
Click to expand...
Click to collapse
Just that the new firmware is more stable with the ROM and everything works as expected.
NilsP said:
Flash the ruu then the Rom of your choice. All the instructions are in the ruu thread to lock, flash, unlock, recovery, etc. Then flash a Rom and not the AP one.
You also have the option to flash one of the ICS ROMe with the old firmware patch but I recommend the RUU path.
Click to expand...
Click to collapse
Nils is right on this. You need to flash the RUU again. There are a lot of folks that needed to flash the RUU twice (myself included) to get everything to take.
It sound to me like you this happened to you. If you have the new RUU flashed properly, your phone will boot to the setup language preference screen.
If you had an incomplete/bad RUU update, you phone will boot to your last/current ROM with no SD or internal memory access. Nandroid backups won't restore properly either. Good luck, reflash the RUU with bootloader unlocked, allow system to reboot, flash a new recovery, and rock.
For one reason or another I went against my steadfast rule of always reading as much as I can from all the devs on here before flashing anything. Anyways, long story short, I had TWRP on my evoLTE and flashed CWM...which I am now reading doesn't really play nice & screws up the /misc partition. I'm stock/rooted & would really like to resolve that before doing anything else. I read about Viper's fix using the p23_dump (the fix that is for anyone, not just running his rom) and would like to use that but seems all the links I find are bad (likely due to the goo.im server issue. In any case, anyone have this file so I can get things fixed?
Also, I saw a question of "what does having a broken /misc partition do" posted a few times without real answer. Can someone enlighten those of us who are not as technically savvy & simply ride the coat tails of everyone doing the heavy dev lifting?
leo662 said:
For one reason or another I went against my steadfast rule of always reading as much as I can from all the devs on here before flashing anything. Anyways, long story short, I had TWRP on my evoLTE and flashed CWM...which I am now reading doesn't really play nice & screws up the /misc partition. I'm stock/rooted & would really like to resolve that before doing anything else. I read about Viper's fix using the p23_dump (the fix that is for anyone, not just running his rom) and would like to use that but seems all the links I find are bad (likely due to the goo.im server issue. In any case, anyone have this file so I can get things fixed?
Also, I saw a question of "what does having a broken /misc partition do" posted a few times without real answer. Can someone enlighten those of us who are not as technically savvy & simply ride the coat tails of everyone doing the heavy dev lifting?
Click to expand...
Click to collapse
A corrupt misc partition can cause a lot of problems. Here's a good read about a Android partitions:
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
What's your reason for switching to cwm? I've been using TWRP since day one and haven't found anything it can't handle...
Sent from my EVO LTE
premo15 said:
A corrupt misc partition can cause a lot of problems. Here's a good read about a Android partitions:
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
What's your reason for switching to cwm? I've been using TWRP since day one and haven't found anything it can't handle...
Sent from my EVO LTE
Click to expand...
Click to collapse
Great read there...thanks for the link!
I just came off the OG Evo and am used to CWM via Rom Manager. Was trying to see if there were any roms through RM that I might be interested in, but the app doesn't work without CWM flashed.....soooo, away I went flashing, didn't find anything (obviously) then stumbled across all the threads talking about how CWM isn't ready for the LTE. Anyways, went ahead & flashed back to TWRP, but still have an FNOC'd /misc, so I'm trying to track down the p23_dump that Viper put out so I can fix things then wade back in to flashing slowly. Guess I got ahead of myself in the end...had a Hero then the Evo (which were very similar for me as far as flashing), thought the LTE would be just the same but finding out I need to relearn some things now.
leo662 said:
Great read there...thanks for the link!
I just came off the OG Evo and am used to CWM via Rom Manager. Was trying to see if there were any roms through RM that I might be interested in, but the app doesn't work without CWM flashed.....soooo, away I went flashing, didn't find anything (obviously) then stumbled across all the threads talking about how CWM isn't ready for the LTE. Anyways, went ahead & flashed back to TWRP, but still have an FNOC'd /misc, so I'm trying to track down the p23_dump that Viper put out so I can fix things then wade back in to flashing slowly. Guess I got ahead of myself in the end...had a Hero then the Evo (which were very similar for me as far as flashing), thought the LTE would be just the same but finding out I need to relearn some things now.
Click to expand...
Click to collapse
Gotcha. Yeah, TWRP is pretty much the standard right now, most devs recommend using it to flash their stuff. Haven't tried cwm on the LTE, but I like TWRP a lot. Good luck with recovering misc...are you S-OFF?
Sent from my EVO LTE
premo15 said:
Gotcha. Yeah, TWRP is pretty much the standard right now, most devs recommend using it to flash their stuff. Haven't tried cwm on the LTE, but I like TWRP a lot. Good luck with recovering misc...are you S-OFF?
Sent from my EVO LTE
Click to expand...
Click to collapse
I thought I was S-Off, but looking at the bootloader it shows on with the whole "tampered" flag at the top. Not sure if flashing CWM did something there, but that's why I'm waiting to fix the /misc before doing anything else. So far I haven't seen any odd behavior out of it. If worse come to worse, can I flash the Viper Rom through TWRP even with S-On then fix the /misc & carry on?
leo662 said:
I thought I was S-Off, but looking at the bootloader it shows on with the whole "tampered" flag at the top. Not sure if flashing CWM did something there, but that's why I'm waiting to fix the /misc before doing anything else. So far I haven't seen any odd behavior out of it. If worse come to worse, can I flash the Viper Rom through TWRP even with S-On then fix the /misc & carry on?
Click to expand...
Click to collapse
Tampered is normal...that shows when the bootloader detects a change to the partitions after you root or unlock the bootloader. What root method did you use?
Sent from my EVO LTE
premo15 said:
Tampered is normal...that shows when the bootloader detects a change to the partitions after you root or unlock the bootloader. What root method did you use?
Sent from my EVO LTE
Click to expand...
Click to collapse
I used Regaw's root method. Didn't really pay attention to whether I was S-Off or not at the end as my main intention was to gain root, install Titanium & be able to restore stuff apps/data from my OG Evo onto my newly activated LTE.
Nobody ever did come up with the p23dump fix for me so I went ahead & flashed the Viper4G 1.0.0 Rom (which includes the VC scripts & subsequent /misc fix). Everything is working great now...just wanted to update in case anyone else has this issue.
Oh, and one thing I noted (again, I didn't read like I know I should) is that Regaw's root method does *not* include s-off. I'm guessing either I "upgraded" at some point or my phone shipped with 1.5 bootloader, so I'm stuck with s-off for now....but that hasn't really hampered anything for me at this point.
I'm in the same boat here. I did almost the exact same thing as the OP. I was used to using CWM, so just thought it was the way to go. Bad thought. Anyway, I'm on a T-mobile hotspot with extremely limited data (and speed for that matter), so I've been trying to track down the p23_dump file with no luck. Does anyone still have this file? Any help would be greatly appreciated. I've put my ROM install on hold until I fix the /misc partition.
Thanks in advance!
Ryan
If anyone else has this problem, I finally just downloaded an old Viper eLiTE ROM and extracted the p23_dump file from it. 550MB to get a 2k file. Anyway, send me a pm if you need the file and I'll e-mail it to you.
Ryan
leo662 said:
For one reason or another I went against my steadfast rule of always reading as much as I can from all the devs on here before flashing anything. Anyways, long story short, I had TWRP on my evoLTE and flashed CWM...which I am now reading doesn't really play nice & screws up the /misc partition. I'm stock/rooted & would really like to resolve that before doing anything else. I read about Viper's fix using the p23_dump (the fix that is for anyone, not just running his rom) and would like to use that but seems all the links I find are bad (likely due to the goo.im server issue. In any case, anyone have this file so I can get things fixed?
Also, I saw a question of "what does having a broken /misc partition do" posted a few times without real answer. Can someone enlighten those of us who are not as technically savvy & simply ride the coat tails of everyone doing the heavy dev lifting?
Click to expand...
Click to collapse
BTW goomanager has roms listed from devs that use goo.im
check this thread.. there's info how to fix broken misc partition... http://forum.xda-developers.com/showthread.php?t=1675430
bigdaddy619 said:
BTW goomanager has roms listed from devs that use goo.im
Click to expand...
Click to collapse
Viper4G is no longer on there ever since the go.im crash.
evo401 said:
check this thread.. there's info how to fix broken misc partition... http://forum.xda-developers.com/showthread.php?t=1675430
Click to expand...
Click to collapse
That's old information that has been depreciated & closed.
I never did find the dump file (but looks like somebody else has extracted it now) & just flashed on of the Viper Roms which has the fix built in.
leo662 said:
Viper4G is no longer on there ever since the go.im crash.
That's old information that has been depreciated & closed.
I never did find the dump file (but looks like somebody else has extracted it now) & just flashed on of the Viper Roms which has the fix built in.
Click to expand...
Click to collapse
i no its old but it works.. my misc partition was screwed from when i flashed cwm recovery months ago.. info in that thread helped me few days ago fix it :good:
hboot is 1.15 i am running 1.22.651.3 i have s-on and am unlocked... i am trying to get s off i am trying to flash to cm10 but i cannot get any were can someone please point me in the right direction ... i have read and read and read and nothing adds up to what happens.. .i use clock work mod to download and install when it boots into recovery it says it installs but the screen stays black i have to hard reset (power vol down and camera) it to get anywere then it goes back into recovery and i use the back up file i had to get my phone to work... what am i doing wrong...
No offense to the developer but I would steer clear on CM10 on the Evo. It ran fine on my Nexus but it really didn't do well on my Evo. The MMS didn't work worth a darn. The biggest issue I had was no data. I reflashed it. I wiped everything. I read the instruction 20 times. It just doesn't work well and has some bugs. There seems to always be some major bugs in the AOSP line of roms. Even on the Nexus G AOKP was a constant headache. I wish I could just say do these three steps and all will be flawless. Sorry, that just isn't the case.
Sorry to point this out but this topic goes on the q&a section not on development
HTC EVO LTE
Not sure what kc is talking about I have flawless data and mms on cm10. I have 4g and it works totally fine with no data issues whatsoever. Now the op is posting in the wrong place, but I would gladly help if the post was more clear. So are you s-off or not? If not it will require you to either get s-off or flash the boot.img separately. If you are s-off try using twrp not clockwork. I have been on twrp since I got the Evo in July and have had zero flashing issues.
Sent from my EVO using xda premium
---------- Post added at 09:52 PM ---------- Previous post was at 09:48 PM ----------
I will add mms has been flawless since using Gosms as has been discussed in the cm10 thread multiple times. Not sure if mms works otherwise, but go sms solves it if it is still being worked on. If you don't like/want to us Gosms then just install it solely for mms because it does send and receive them and they show up in the stock messaging app as well.
Sent from my EVO using xda premium
i have s on and all i can access is twrp and hboot
I'm not entirely sure how you managed to put [Q] in your thread title AND ignore the box that says "Is this a question?". There is a very, very clearly labeled section for questions and answers, and your question is one of the most asked here.
Here's your two step fix:
1. Learn where to post. (please)
2. You are S-ON. The reason why you see a black screen is because S-ON users can't flash kernels from recovery. You have to do it seperately. Custom ROMs like AOSP or ROMs that use custom kernels can't be flashed normally on S-ON.
3. No, you did not read. At all. We can tell because the very first thread in the Questions and Answers forum (http://forum.xda-developers.com/showthread.php?t=1869377) says the following:
Note: To those of you with CWM Recovery, it is recommended that you use TeamWin Recovery as it is better suited for our phones.
Brick This is a very serious problem, your device is catatonic and will not respond to the usual methods of power on/off or sim-pull. In some cases the phone comes back when the battery dies and is recharged, this isn't very often. There are un-bricking tools written by OEMs when they screw up (Samsung / Motorola) and there are tools written by developers working on S-OFF. They notice a very real danger and will supply the tool just in case (this is not possible in all cases). Bricking can and will be permanent in many situations
Boot loop There a different kinds of boot loop situations (also referred to as soft brick, please do not cry brick in the forums if it is a boot loop) the most common are a mismatch of kernel and ROM.
Help, my phone is stuck in a boot loop or my phone is stuck on HTC! Not a problem at all. Hold down the power button and continue to hold it, the capacitive buttons will begin flashing and phone will reboot. After the screen turns off let go of power for one second and the press and hold power and volume down to boot into the boot loader. This is known as a simulated battery pull. HTC built this in as a fail safe to reboot your phone, and it gives us a chance to jump into the boot loader should anything go wrong. Once you have successfully made it to the boot loader read through these forms of boot loop to understand what went wrong.
Known forms of boot loop
Generic Boot loop You have a working recovery and now you have installed your first ROM. There's just one problem every ROM you try boot loops but if you restore your back up and it runs fine. This is common when you haven't taken the time to wipe your phone before you flash. You can use a wipe script to clean your phone or you can systematically wipe Dalvik, Cache, Factory Restore, and then wipe System. Now you can flash your custom ROM (HBOOT 1.15+ requires you to flash the kernel separately)
Help my phone won't boot past the splash screen similar to a generic boot loop, the most common fix is to wipe the phone before flashing your ROM. Wipe your dalvik and cache, the factory reset and wipe system. You can now flash your new ROM
Kernel Issue You have flashed a kernel that may be corrupt, originate from a different base, or is just not supported by the ROM (not really the case these days, most developers are willing to share tweaks and custom code) The result is a phone that boots to a black screen and will hang or reboot.
Note: HBOOT 1.15+ requires you to flash the kernel separately, all relevant info to do so is in this guide.
Click to expand...
Click to collapse
In the future, if you have a question, consider placing it the forum that is meant for that. Sorry to sound like an ass, but I'm in a bad mood.
thank for the help...
I am running Cyanogen Mod 10.0 on the phone for 2 weeks and not even one issue. I updated to the latest TWP before I installed the ROM. I am never going back to gay Sense. Sorry but I can't stand sense. I love the build quality of the EVO more than any other phone on the market. I really hope they come out with a Nexus Device.
Download CyanogenMod from their site and you will not have an issue.
Go to the aokp thread and at the beginning says how to push the boot.img vías fast boot after that you should be fine flashing the rom
Sent from my EVO using xda premium
Can someone delete this thread? or move it? or help this guy read instructions on how and where to post things?
Yes I'm closing this. And OP WATCH your language. YOU posted in the wrong area, not the other way around... So it's YOUR fault and No ONE herer owes you ANYTHING.
On a side note, if everyone quotes the offensive language I have to delete that too... just an FYI
I've been trying to understand all the steps necessary to replace the OEM ROM in my HTC Amaze 4G phone, but I can only find a disjointed set of pieces about the various steps and not one overarching document that covers all the stages of custom ROM flashing. A lot of the docs are aimed at the "insiders" of the Android developer community and few to people like me who would just like to try something better than what that ICS update did to my phone.
Having dabbled at one time with Linux from version .98 to 2.6 and being software developer most of my working life, I figure this should be easy for me. Yet, I find the documentation frustrating. I only imagine what it must be for others with less computer experience than me.
Since Android is based on Linux, I don't understand the big fuss about rooting. In Linux having the rooting privilege simply meant having a root password. Why is Android so much more complicated than that? Also, loading a new Linux kernel used to be a fairly simple process if one used compiled modules. The installation script pretty much took care of it. Android totally obscures this process and the disjointed documentation doesn't seem to help much. A lot of it assumes certain knowledge by the reader as if he/she was also an "insider" in that circle.
On my part I would like to so the following steps documented:
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
2.) How to prepare the phone for installing a new ROM
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
5.) How the flashing process would look like? Expected phases and length?
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
7.) Any special issues when booting the new ROM for the first time?
8.) How would I restore the original factory ROM saved in step 1?
Some of you might think I ask too much from guys who do the dev work as a hobby but I always thought that if one does something, might as well do it right, regardless of pay.
Well, that's my 2 cents worth for the day.
Howdy. I'll try to answer some of the questions you asked.
I would also recommend talking with @ravike14 who can easily guide you through the back up and routing and s-off process. It's not that difficult really. The most bizarre thing for me was sticking a piece of wire into a hole in the back of the phone to short out a process to achieve s-off.
With the right recovery image installed, it won't matter where you place the Rom.zip. which may be named just about anything. But it will always be a zip file.
The important one is the PH85img.zip must be placed in the root of your external sdcard. That file is loaded when you boot into the bootloader. And is for updating firmware.
Once you have root, and have made a nandroid backup, flashing is easy.
If you download viper, it is vipera1.7.2.1.zip. you can have it anywhere on you internal or external sdcard.
If you use 4ext recovery, you can select install and it will take you to a directory that you can browse to the place where the Rom, whatever name it is, is stored.
Click the Rom zip file and you will be guided thru the install process, if it has an aroma installer, or it will just install otherwise.
Then reboot and go thru the set up as if it was a brand new phone.
If you don't do the s-off thing, 4ext offers a smart flash option. If you aren't s-off you can't just flash a Rom if it contains a kernel. So smart flash will be required.
There are a few guides in the dev section and the general section on how most of this process works.
Again, talk with ravike and he'll be glad to help. Plus the more people we can keep here and happy, the longer we will be creating roms and fun stuff to play with.
Regards,
Chevy
Sent from my HTC_Amaze_4G using xda app-developers app
Is there a good documentation for all ROM flash steps?
Thanks, Cowboy, for the helpful reply, though I don't see any HELP button to push that the end of your post refers to.
I think at this point I'd like to figure out on my own how to install a custom ROM, though I must say that your S-OFF reference is one of the things that confuses me because the HTC dev site itself spells out that it is not necessary to change S-On to S-Off. Go, figure ...
Also, I think I like what I've read about the Revolution ROM, so that's the one I'd like to install if that is working with T-Mo branded Amaze 4G phones, though mine is no longer locked to T-Mo.
Your welcome!
NWsoccerfan said:
Thanks, Cowboy, for the helpful reply, though I don't see any HELP button to push that the end of your post refers to.
I think at this point I'd like to figure out on my own how to install a custom ROM, though I must say that your S-OFF reference is one of the things that confuses me because the HTC dev site itself spells out that it is not necessary to change S-On to S-Off. Go, figure ...
Also, I think I like what I've read about the Revolution ROM, so that's the one I'd like to install if that is working with T-Mo branded Amaze 4G phones, though mine is no longer locked to T-Mo.
Click to expand...
Click to collapse
If you're using the web to look at xda, there is a thanks button on the lower left side of the screen before the very end of the post line.
If you're using the XDA app, you have to tap on my post, and it should have a thanks selection in the options that come up.
A few more suggestions.
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
A) one you are rooted you should be able to back up all of your user data through a nandroid which is available in TWRP or 4EXT recoveries. This will back up everything to be able to restore exactly like it was before you change roms.
(NRG is my ICS preference, and Afnan has a good modified stock rom. ARHD (revolution) is also a good one without too many frills.
2.) How to prepare the phone for installing a new ROM
B) again, Root - s-off (really a good idea and not too hard to do) - dev unlock - and Super CID
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
C) any roms listed in the dev section in the Amaze forum works. And, they should all be Zip fles. You can restore somone elses nandroid back up, but not adviseable.
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
D) anywhere (except the PH85IMG.zip MUST be on the root of your EXTERNAL sdcard)
5.) How the flashing process would look like? Expected phases and length?
E) There are two types of rom flashes, standard and Aroma (thanks @amarullz)
1) Standard just does it's thing and when it's done, it returns you to the recovery menu to reboot.
2) Aroma is a highly configurable installation (preferred for selections of different kernels and adding or removing apps, keyboards, cpu freq's and much more) after it's done, most often it can reboot directly from the installer. ARHD has this type of installer, also NRG roms, and mine!
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
F) all of the "Custom" rom's (even thought some may be stock) should be rooted. A rooted rom containd the busybox and super user bianaries and apps (IE chanfireSU or SuperSU)
7.) Any special issues when booting the new ROM for the first time?
G) You shouldn't have any issues when booting a new rom for the first time. Some do require a little bit of behind the scenes set up time. Most users see just the boot animation reach the end, or it may seem like it's not doing anything, but it's doing an unbelievable amount of background processing, dexopting, and some comminucation with the carrier for data and validation set up. Some may take five to ten minutes to complete depending on the amount of apps and goodies that are in the rom.
H) if you see the HTC logo for an extended amount of time, more than five minutes, and you dont see the boot animation (which varies by rom) then you are stuck in a preload loop. This happens when you flash a carrier specific rom without being "Super CID", or you may not have flashed the kernel (if you are S-Off this won't be a problem) because you didn't select smartflash from the recovery settings.
** I had issues trying to install ARHD at first because there is a firmware update, a requirement to be Super CID (probably the easiest of things to do), and some roms specify that you should be using TWRP recovery instead of 4EXT, or vise versa.
8.) How would I restore the original factory ROM saved in step 1?
I) nandroid restore There is also a rooted stock rom based off of the latest OTA ICS Update. It is just like the rom that comes preloaded, or updated to on stock non-rooted phones. If you go that route, flash the "Stock ICS" rooted rom and do an advanced nandroid restore and only restore your data. That will (should) get you back to where you started from but keeping root, S-Off, Dev unlock, and Super CID.
I rewrote some of what I noted befor so maybe other's can benifit from this knowledge. And I wanted to expand on a few items. All good questions!
There's a lot of things that happen in the background that people need to see sometime (pull a logcat) to see the crazy lines of code flying by on a terminal screen.
If more poeple took the time to understand all of this it would reduce the amount of errors while flashing and poeple would be more happy.
And in doing so I think people will learn more about what they are doing, and the more you do it, the better you get at doing it.
Enjoy!
Chevy
chevycowboyusa said:
If you're using the web to look at xda, there is a thanks button on the lower left side of the screen before the very end of the post line.
If you're using the XDA app, you have to tap on my post, and it should have a thanks selection in the options that come up.
Click to expand...
Click to collapse
I use the web for this and the only thing I see on the lower left side is a DONATE button. That's what you mean?
chevycowboyusa said:
A few more suggestions.
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
A) one you are rooted you should be able to back up all of your user data through a nandroid which is available in TWRP or 4EXT recoveries. This will back up everything to be able to restore exactly like it was before you change roms.
(NRG is my ICS preference, and Afnan has a good modified stock rom. ARHD (revolution) is also a good one without too many frills.
2.) How to prepare the phone for installing a new ROM
B) again, Root - s-off (really a good idea and not too hard to do) - dev unlock - and Super CID
Click to expand...
Click to collapse
Can I still use my phone after it is rooted but before the new ROM is installed? How would the phone behavior change on a rooted phone?
You did not comment on why the htcdev site recommends against the S-Off as not being necessary for installing a custom ROM.
chevycowboyusa said:
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
C) any roms listed in the dev section in the Amaze forum works. And, they should all be Zip fles. You can restore somone elses nandroid back up, but not adviseable.
Click to expand...
Click to collapse
OK, I've got that. Does this Nandroid backup the entire image of the phone's content sector-by-sector, or as individual files? To the external SD card or to the PC connected by USB cable? BTW, why are all flashing procedures requiring loading of the HTC USB drivers when such drivers must be on the phone already? Otherwise we could not link the phone to PC in the first place.
chevycowboyusa said:
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
D) anywhere (except the PH85IMG.zip MUST be on the root of your EXTERNAL sdcard)
5.) How the flashing process would look like? Expected phases and length?
E) There are two types of rom flashes, standard and Aroma (thanks @amarullz)
1) Standard just does it's thing and when it's done, it returns you to the recovery menu to reboot.
2) Aroma is a highly configurable installation (preferred for selections of different kernels and adding or removing apps, keyboards, cpu freq's and much more) after it's done, most often it can reboot directly from the installer. ARHD has this type of installer, also NRG roms, and mine!
Click to expand...
Click to collapse
Aroma? That doesn't smell too good to me.
chevycowboyusa said:
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
F) all of the "Custom" rom's (even thought some may be stock) should be rooted. A rooted rom containd the busybox and super user bianaries and apps (IE chanfireSU or SuperSU)
Click to expand...
Click to collapse
Oh, so this might answer my earlier question about how a rooted phone might behave. Essentially a user might not even know the difference, right? So, I could also do this process in two stages: First just root the factory ROM and use the phone that way till I am ready to actually flash the new ROM in the second stage, right?
chevycowboyusa said:
7.) Any special issues when booting the new ROM for the first time?
G) You shouldn't have any issues when booting a new rom for the first time. Some do require a little bit of behind the scenes set up time. Most users see just the boot animation reach the end, or it may seem like it's not doing anything, but it's doing an unbelievable amount of background processing, dexopting, and some comminucation with the carrier for data and validation set up. Some may take five to ten minutes to complete depending on the amount of apps and goodies that are in the rom.
H) if you see the HTC logo for an extended amount of time, more than five minutes, and you dont see the boot animation (which varies by rom) then you are stuck in a preload loop. This happens when you flash a carrier specific rom without being "Super CID", or you may not have flashed the kernel (if you are S-Off this won't be a problem) because you didn't select smartflash from the recovery settings.
** I had issues trying to install ARHD at first because there is a firmware update, a requirement to be Super CID (probably the easiest of things to do), and some roms specify that you should be using TWRP recovery instead of 4EXT, or vise versa.
Click to expand...
Click to collapse
I've got this.
chevycowboyusa said:
8.) How would I restore the original factory ROM saved in step 1?
I) nandroid restore There is also a rooted stock rom based off of the latest OTA ICS Update. It is just like the rom that comes preloaded, or updated to on stock non-rooted phones. If you go that route, flash the "Stock ICS" rooted rom and do an advanced nandroid restore and only restore your data. That will (should) get you back to where you started from but keeping root, S-Off, Dev unlock, and Super CID.
I rewrote some of what I noted befor so maybe other's can benifit from this knowledge. And I wanted to expand on a few items. All good questions!
There's a lot of things that happen in the background that people need to see sometime (pull a logcat) to see the crazy lines of code flying by on a terminal screen.
If more poeple took the time to understand all of this it would reduce the amount of errors while flashing and poeple would be more happy.
And in doing so I think people will learn more about what they are doing, and the more you do it, the better you get at doing it.
Enjoy!
Chevy
Click to expand...
Click to collapse
Thanks. I like your attitude about this.
When you get time stop by
XDA University.
I learned tons here its a great place to start and much better than trying to Google everything
http://forum.xda-developers.com/general/xda-university
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
been busy
NWsoccerfan said:
I use the web for this and the only thing I see on the lower left side is a DONATE button. That's what you mean?
Can I still use my phone after it is rooted but before the new ROM is installed? How would the phone behavior change on a rooted phone?
You did not comment on why the htcdev site recommends against the S-Off as not being necessary for installing a custom ROM.
OK, I've got that. Does this Nandroid backup the entire image of the phone's content sector-by-sector, or as individual files? To the external SD card or to the PC connected by USB cable? BTW, why are all flashing procedures requiring loading of the HTC USB drivers when such drivers must be on the phone already? Otherwise we could not link the phone to PC in the first place.
Aroma? That doesn't smell too good to me.
Oh, so this might answer my earlier question about how a rooted phone might behave. Essentially a user might not even know the difference, right? So, I could also do this process in two stages: First just root the factory ROM and use the phone that way till I am ready to actually flash the new ROM in the second stage, right?
I've got this.
Thanks. I like your attitude about this.
Click to expand...
Click to collapse
you're welcome! I wish everyone would try to learn this
and the university is also very helpfull as freakboy noted above,
I've been busy working at bringing the comunity the next greatest romz!