Recovery Image for View* Found CWM* - HTC Flyer, EVO View 4G

I have the revolutionary tool and I wanted to run it. I was wondering if anybody knows of a recovery image that works with the View. I know there is one the forum that works with the flyer but I don't know if it will work with the view. If any of you View users get a recovery image to work, please post it here so that others can do the same.
Found it here. It is the one for the View/Express:
http://forum.xda-developers.com/showthread.php?t=1122694

In my amon port I got the buttons to function correctly. Because amon hasn't updated his github in some time (and his evo version is up to 2.3) I had to go in and manually change all the key button events to reflect the view(express) key buttons.
I also had to manually add the return function that amon added to his newer versions. Right now I'm just trying to clean up the source code that I am editing by taking out lines that don't affect anything (like the btn_mouse call or alt buttons for example).
I'm going as fast as I can but for the most part I'm making some decent (albeit small) progress.

That is good news. It would be nice to have a choice between a cwm and ra recovery image. Just an fyi for others. I did a nandroid backup this morning and it took 1.8GB so make sure you have plenty of room on your sdcard.

theres a recovery image for the view at this thread

lovethyEVO said:
In my amon port I got the buttons to function correctly. Because amon hasn't updated his github in some time (and his evo version is up to 2.3) I had to go in and manually change all the key button events to reflect the view(express) key buttons.
I also had to manually add the return function that amon added to his newer versions. Right now I'm just trying to clean up the source code that I am editing by taking out lines that don't affect anything (like the btn_mouse call or alt buttons for example).
I'm going as fast as I can but for the most part I'm making some decent (albeit small) progress.
Click to expand...
Click to collapse
That is great news. I was a CWM fanboy for the longest time but then on my Evo 4g it started giving me problems. I switched to amon and never looked back. Be nice to have good ol amon back.

Related

Trackball not responding in recovery mode

So I've just flashed one of the new Eris based rom's, and it boot-looped, and when I wen't back into recovery mode, my trackball wouldn't respond to movement, although it would click. Luckily I can use the volume keys, atm, but does anyone have an idea of why this might have happened, and/or how to fix it?
(I restored my nandroid backup, and it worked fine, but roms shouldn't affect the recovery image should they?)
Thanks
easy work.
flash RA-Recovery under the exist one. RA-Recovery works well with track ball. It's here:
http://forum.xda-developers.com/showthread.php?t=561124
I think you need to post your existing Recovery's version before others can look into it.
Ah, sorry, it was on RA-hero-v1.5.3.1

[Q] phone calls

Can't receive phone calls. Just shows up in missed call log. No ringing.
An answer would be easier to obtain with more information.
Sent from my Eris using XDA App
It would be very helpful if you would consolidate all your issues into one of your post, as they may be connected, and included more information. Usually the basics needed are atleast which ROM you are using, what changes have been recently made, and a detailed description of the problem.
I put vanilla cynogen mod rom on. And now it wont get calls when. Someone. Calls me it just shows up as missed call in call log.
I'm not trying to be an asshole, but I would just like to impress upon you how perfectly useless you have been to yourself. Vanilla Cyanogen Mod ROM, really, which one, there is no "official" CM for Eris, so which port are you using. If it's showing up in your missed call log, the call reached your phone, missed calls due to no service, airplane mode, phone shut off or any reason except they were simply not answered, do not show up in the missed call log. If it's in the call log you can almost certainly receive calls, your notifications may not be working. Have someone call the phone while you are watching it, if the display does not indicate an incoming call then you do have a novel problem. Try this and please report.
Sorry for the lack of knowledge on this I'm just having alot of problems with it and don't know where to start. My friend introduced me to rooting n different Rome on his phone n said to try it out. So sorry. I tried someone calling me and no display of them calling then I checked call log when they hung up n it showed a missed call. If that. Helps any.
I have modle. Number- froshedyo. Android version-2.2.1. Kernel version-2.6.29-decafuctcfs-dirty-c6271491. Mod version-froshedyo-6.2-rci-desierc. Build number-frf91
If that helps
lol "if that helps," dude that exactly what you've been asked for in each of your threads, I'll do some tinkering, see if I can find you a way to get Amon-RA Recovery without too much hassle, that can help resolve most of your issues I've read about. I'll post back later tonight.
Alright! Thank you so much. I know I'm a retard.
BTW what method did you use to root the phone, a direct link to the tutorial or the name of the app, whatever you used, please.
One click root
joejoemotorcycle said:
One click root
Click to expand...
Click to collapse
Well, before I get too far into this, One Click Root (jcase's I presume) installs Amon RA Recovery, RomManager doesn't actually install ClockWorkMod Recovery, it's a sort of one time run overtop of Amon, try booting into recovery directly.
Turn the phone completely off, Press and Hold the VolumeUP key while Pressing and Holding the Power/EndCall button. Alternatively, with the phone on Press Power/EndCall, chose reboot, recovery, ok.
If you have a menu with several options in green text that you highlight with the trackball you are in Amon, and this will be easy.
Yup it's in green using trackball.
Outstanding, read this first post very carefully and follow it step by step, if you want to try FroShedYo again, make sure to re-read this first post entirely. The reason you did not have market was because you did not flash this file. If you want to start over completely from stock you may also use bftbo's FlashBack21
While you are in Amon Recovery, connect your phone to the computer with the USB/Charging cable, select the "USB-MS toggle" option in Amon, press the trackball. On your computer find the phone, transfer whatever ROM you wish to flash to the SD Card, do not place it in any folders. Follow step by step the instructions here. If you are flashing FroShedYo, (or any CM ROM that requires a gapps flash) after you Flash the ROM, but before you reboot, flash gapps.
Make sure you understand all of the instructions before you do anything, if something is unclear feel free to ask.
Alot of this stuff can get overwhelming if your new to it, I bricked the first phone I rooted because I wasn't paying attention, but be cautious, and be sure you understand anything new you want to do to your phone.
USSENTERNCC1701E said:
If you have a menu with several options in green text that you highlight with the trackball you are in Amon, and this will be easy.
Click to expand...
Click to collapse
BTW this is based on the assumption that you "flashed" ClockWork Mod Recovery from RomManager, both Recoveries use this same styling. The procedures are also very similar for both, as long as you have a custom recovery you should be able to fix this. Amon is "preferable" for the reasons bftbo brought up in another of your threads. To definitively tell which Recovery you are using look for white lettering on the bottom of the screen,
Amon-RA Recvoery - Build : RA-eris-v*.*.*
ROM Manager - ClockworkMod Recovery v*.*.*.*
It says build : eris-v***
Did you have any luck reflashing the ROM with a full wipe?
joejoemotorcycle said:
It says build : eris-v***
Click to expand...
Click to collapse
Apologies for butting in.
Amon_RA should look like this: http://i756.photobucket.com/albums/xx209/erisuser1/Amon_RA_stuff/Main_Menu.jpg
FWIW, there is a mini-tutorial with lots of pictures (of the Amon_RA menus) in this post on AF
Now, back to the regularly scheduled programming.
Yeah, I googled and couldn't find anywhere a build : eris-v*** So I'm kinda banking on a bit of oversight or a typo. That pic is very handy, much more specific than "menu with several options in green text" lol
Thanks bftbo
Yes did everything u wrote n put gapp. In n flashed all n seems to be working awesome. Thank you so much. If I have any issues then I will repost. Thanks again

[Q] Regarding the charging program...

Regarding the charging program (the program that draws the charging animation when the phone is "off" but on the charger) on the Aria/Liberty, would people prefer the animation (that tells you nothing, except that it's charging and it hasn't locked up), or would they prefer a program that displays some info (like, battery level, temp, source, amps, etc.)?
The reason I ask is because I got bored and hacked together a new offmode_charging program that, currently, tells the battery level and the power source. Probably not all that useful, but I threw together a custom recovery image (based on CWM 5.0.2.6) with my program after testing it out (though my battery is probably screwed with all the on/off charging cycles).
Everything works, it honors the androidboot.mode prop (so it doesn't interfere with CWM), it shuts down the phone after the charger has been disconnected, and it will "power on" from charging (although that isn't handled by the charging app anyway). Also, it displays the info through a hacked CWM UI. Just two lines of text at the bottom of the screen. Really simple.
So, feedback? Opinions?
EDIT: Attached zip file with recovery.img inside. It is *not* an update.zip. Just a plain img file that you will have to flash with hboot, flash_image, unrevoked, revolutionary, etc. Again, give feedback. It should work without problems (it's a simple program), but if something doesn't behave as expected, let me know. Both CWM and charging mode were tested and everything seemed to be working.
battery level would be sweet. would it be possible for you to build 2.5.0.7 with the battery level?
hi2u2 said:
battery level would be sweet. would it be possible for you to build 2.5.0.7 with the battery level?
Click to expand...
Click to collapse
Short answer, no, you would have to use revolutionary and gain S-OFF to use this. (Requires S-OFF and you to flash a custom recovery image).
(EDIT: Okay, as the post below informs me, that's not true. But S-OFF does make things a helluva lot easier.)
Long answer, I can't really build 2.5.0.7 with the battery level because it's not a "permanent" flash. ROM Manager leaves behind a couple of files for the recovery system to "update" itself to that version every time the recovery system is booted up. The reason for this being is that most Arias are S-ON, unless you've used revolutionary, chances are high that yours is S-ON too. S-ON prevents writes to both the recovery and system partitions (and probably some others). So, that's why ROM Manager does the above. Like I said, however, if you have unlocked your phone (and gained S-OFF) using revolutionary, then there's no point in using 2.5.0.7 unless you reboot into recovery through ROM Manager (it can't check for S-OFF atm, so it sticks with what it knows best). Rev flashes CWM 4.x.something during its process, which is far better than 2.5.0.7 (it has a bug which causes some glitches when the USB is connected anyway). Then, from there, you can flash whatever recovery you want.
(EDIT: Even more of a explanation: The 2.5.0.7 that comes with ROM Manager (which is I'm guessing what you were referring to, sorry if I'm mistaken) is in update.zip form ("fake flash"). I was not aware of it existing in a flash-able .img format. Until I found the 2.5.1.7 "updated" .img (in the zip) posted below.)
Hope that answers your question.
ZeroSigea said:
Short answer, no, you would have to use revolutionary and gain S-OFF to use this. (Requires S-OFF and you to flash a custom recovery image).
Long answer, I can't really build 2.5.0.7 with the battery level because it's not a "permanent" flash. ROM Manager leaves behind a couple of files for the recovery system to "update" itself to that version every time the recovery system is booted up. The reason for this being is that most Arias are S-ON, unless you've used revolutionary, chances are high that yours is S-ON too. S-ON prevents writes to both the recovery and system partitions (and probably some others). So, that's why ROM Manager does the above. Like I said, however, if you have unlocked your phone (and gained S-OFF) using revolutionary, then there's no point in using 2.5.0.7 unless you reboot into recovery through ROM Manager (it can't check for S-OFF atm, so it sticks with what it knows best). Rev flashes CWM 4.x.something during its process, which is far better than 2.5.0.7 (it has a bug which causes some glitches when the USB is connected anyway). Then, from there, you can flash whatever recovery you want.
Hope that answers your question.
Click to expand...
Click to collapse
Actually it's possible to install a custom recovery version of your choice with Unrevoked. You just select the img file before connecting the USB cable after starting up the Unrevoked program.
That said, my hunch for the actual reason that he wants a 2.5.x version instead of 3.0 or newer is because 3.0 and newer versions don't support ROMs that use the older amend scripting. Notably that includes FR008 which a lot of people are happy with. Other than that though there's really no reason to use an old version of CWM.
drumist,
Yeah, I had forgotten about that (it's been awhile since I've used unrevoked).
And the amend scripting is another valid point.
Heh, wow, didn't mean to sound like a ROM bigot.
How about this then hi2u2. I'll take this 2.5.1.7 recovery.img and mod it, test it, and let you know that goes.
No problems there, eh?
Ok. So upon further inspection, the recovery I linked earlier is in fact 2.5.0.7 or at least identifies itself as such. So yeah, hindsight and all. Next time, I should do more research before I open my trap.
Anyway, it's been built, tested and seems ready. I'll post it later this evening.
Sent from my Liberty using XDA App
awesome dood. that was the exact recovery i wanted to be modded.
hi2u2 said:
awesome dood. that was the exact recovery i wanted to be modded.
Click to expand...
Click to collapse
Posted the file in the OP.

[RECOVERY][Fascinate]TWRP 2.3.1.1 touch recovery [2012-10-16]

Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Two thumbs
Flashes fine and boots into recovery and can flash files as well. On aokp 35.1 for the record.
Sent from my SCH-I500 using Tapatalk
I will warn you all to use care with this, it does not play well with other recoveries and roms, and sometimes even with Odin. I used it a lot trying to test things for steve and we decided to put it on the back burner, it is cool but causes trouble sometimes. Basically, it's awesome to use and has lots of handy features (zip queue ftw) but try not to flash anything with it if you aren't near a computer that you can Odin with just in case.
Sent from my SCH-I500 using Tapatalk 2
Thanks for the heads up. I did go ahead and flash to play around with it. You are right. There are a bug or two in there. Is there a easy way to get the reg cwm back on like Odin or flashing, or do I need to Odin back to stock first. Its no biggy, just didn't want to waste time when I get home tonight. It is very responsive and easy to navigate though and looks very promising
edit:so odin back to stock and then restore is the way to go. I still like it a lot either way.
Sent from my SCH-I500 using Tapatalk
shelby04861 said:
Thanks for the heads up. I did go ahead and flash to play around with it. You are right. There are a bug or two in there. Is there a easy way to get the reg cwm back on like Odin or flashing, or do I need to Odin back to stock first. Its no biggy, just didn't want to waste time when I get home tonight. It is very responsive and easy to navigate though and looks very promising
edit:so odin back to stock and then restore is the way to go. I still like it a lot either way.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Reflashing AOKP glitched version should work? Unless TWRP messes with the way it handles scripting.
tonu42 said:
Reflashing AOKP glitched version should work? Unless TWRP messes with the way it handles scripting.
Click to expand...
Click to collapse
yeah it changes some boot stuff and tries to reinject itself when you flash kernels. Which is handy if you want it but if you don't it causes problems. I was able to flash a glitch kernel from twrp but then it would just keep rebooting to glitch (cwm) recovery as though I had done three finger reboot. I flashed cm7 which put me back on blue older cwm5 and after flashing it again the phone booted so then I flashed back to ics.
Sent from my SCH-I500 using Tapatalk 2
It is really a 50/50 as to which way to go, a bunch of flashing or a bunch of Odin and then restore. Time difference is not to much. Were you able to do any backups and restores with it. I didn't have time to try that out yet. I also didn't have time to check to see if the problems made the bug report or not
Sent from my SCH-I500 using Tapatalk
Things I would like tested before I include it in AOKP.
1) data wipe. You can flash the ROM again boot and if all is well go back and restore.
2) flash the ROM or Efpophis kernel and tell me what recovery you have. It should be blue or red not twrp.
If those are good I'll look into including it.
Sent from my Glitched AOKP Unicorn.
Stephen, I have not tried those due to time. I can tell you I tried flashing the cwm fixed for cm7 twice and I still remained on twrp. I tried once with the injection button checked and once with it unchecked. Same result but no boot loop issues at all from that or any other flashing. This recovery is a tricky one for sure. When I get more time I will try some of your requests. I have limited time at my home computer lately because of work and studying for a test for work.
Sent from my SCH-I500 using Tapatalk
shelby04861 said:
Stephen, I have not tried those due to time. I can tell you I tried flashing the cwm fixed for cm7 twice and I still remained on twrp. I tried once with the injection button checked and once with it unchecked. Same result but no boot loop issues at all from that or any other flashing. This recovery is a tricky one for sure. When I get more time I will try some of your requests. I have limited time at my home computer lately because of work and studying for a test for work.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
How did you flash the CWM CM7? If you (or the zip) used flash_image, then you might need to use erase_image first. flash_image checks the first 2KB of the image against what's already in boot. If it matches then it refuses to flash. The 2KB approach works fine for "normal" Android kernels because the first 2KB contains a "unique signature" but it doesn't always work well for Samsung SGS1 kernels because they are packed differently. I've found that I sometimes had to use erase_image in order to get flash_image to work. I've thought about submitting a patch to CM to fix this issue but haven't gotten around to it yet.
TWRP has been tested on the Epic 4G here:
http://forum.xda-developers.com/showthread.php?t=1622947
And there's a zip here that should re-inject CWM. It would need to be modified slightly to work with the Fascinate, but someone could use this as a base if they wanted:
http://forum.xda-developers.com/showthread.php?t=1651012
I think most of the issues that you'll experience will be due to the "injection process". If your kernel or ROM developer already includes TWRP in their builds then you don't need to try to reinject TWRP every time and we do make it optional. The recovery itself should be pretty solid because we use the same code across all devices (except for the optional injection code) so there's nothing that's specific to the SGS1 devices. Also, for the record, because sk8 loaned me his Fascinate, I was able to add /datadata support to TWRP, so that issue gone now too.
If you do run into any issues, please let me know. It's best to PM me, submit a bug report on github, or catch me in #twrp on Freenode. With over 20 devices to support I can't frequent the threads on the forums or I won't get any coding done.
Dees_Troy said:
How did you flash the CWM CM7? If you (or the zip) used flash_image, then you might need to use erase_image first. flash_image checks the first 2KB of the image against what's already in boot. If it matches then it refuses to flash. The 2KB approach works fine for "normal" Android kernels because the first 2KB contains a "unique signature" but it doesn't always work well for Samsung SGS1 kernels because they are packed differently. I've found that I sometimes had to use erase_image in order to get flash_image to work. I've thought about submitting a patch to CM to fix this issue but haven't gotten around to it yet.
TWRP has been tested on the Epic 4G here:
http://forum.xda-developers.com/showthread.php?t=1622947
And there's a zip here that should re-inject CWM. It would need to be modified slightly to work with the Fascinate, but someone could use this as a base if they wanted:
http://forum.xda-developers.com/showthread.php?t=1651012
I think most of the issues that you'll experience will be due to the "injection process". If your kernel or ROM developer already includes TWRP in their builds then you don't need to try to reinject TWRP every time and we do make it optional. The recovery itself should be pretty solid because we use the same code across all devices (except for the optional injection code) so there's nothing that's specific to the SGS1 devices. Also, for the record, because sk8 loaned me his Fascinate, I was able to add /datadata support to TWRP, so that issue gone now too.
If you do run into any issues, please let me know. It's best to PM me, submit a bug report on github, or catch me in #twrp on Freenode. With over 20 devices to support I can't frequent the threads on the forums or I won't get any coding done.
Click to expand...
Click to collapse
Looks good both issues look fixed. I'll play with it a bit more. But I think you did a great job.
Sent from my Glitched AOKP Unicorn.
I guess you have your answers. I was flashing the zip version, but I do not ha e the further details you want.
Sent from my SCH-I500 using Tapatalk
Yeah everything looks great I made the changes needed to build it in aokp as soon as I get server access back up I'll test some builds with it in there. Great job dees looks great.
Stephen.k.spear said:
Yeah everything looks great I made the changes needed to build it in aokp as soon as I get server access back up I'll test some builds with it in there. Great job dees looks great.
Click to expand...
Click to collapse
ill fershur test this after it gets outta alpha stage, i dont wanna screw up my phone
Okay so far I'm loving this recovery, still have more testing, but I'm insanely impressed!
~~~~There is no spoon~~~~
After serious testing on this recovery last night I have come to the following conclusions:
1 This is the ONLY recovery that will let me backup/restore my device correctly on this phone
2 USB Mount doesn't seem to work, but if I had to trade USB Mount for working backups it is NOT a hard choice.
3 This recovery is one of the simplest to use and most functional recoveries I have used on ANY phone
4 This recovery is extremely responsive, full featured and beautiful to look at with the theme I have on it. Oh yeah, did I mention you can THEME THE RECOVERY?!?! WIN!
5 Any more bacon packed in this package would cause massive coronary problems.
6 If you are scared to try it, don't be. I am using ONLY TWRP recovery from this point on. I'm sold.
So if any of you are on the edge about this recovery, take the plunge. I promise you will not regret it.
my only problem is that i cant restore my CWM backups with TWRP
ztotherad said:
my only problem is that i cant restore my CWM backups with TWRP
Click to expand...
Click to collapse
This is definitely worth starting fresh and making a new backup.
~~~~There is no spoon~~~~
Honestly? I used TWRP on my Acer & it was okay, but I did definitely have problems, but I'll try it
Can I go back to CWM if I don't like it?
ztotherad said:
Honestly? I used TWRP on my Acer & it was okay, but I did definitely have problems, but I'll try it
Can I go back to CWM if I don't like it?
Click to expand...
Click to collapse
I haven't tried that yet, I was waiting for the next kernel it ROM release before flashing just to see if I could get cwm back on.
~~~~There is no spoon~~~~

[Q] Is there a good documentation for all ROM flash steps?

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!

Categories

Resources