Related
This is beginning to get out of control with all of the thread jacking and such with mainver issues. Anyway, read on.
NEW INFO: FLASH THIS: http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4\
PROBLEM SOLVED!
Old info if you care:
Q. What is MainVer?
A. MainVer is a string that HBOOT keeps track of that keeps the latest version of the RUU or PH98IMG.zip that has been flashed.
Q. Why does HTC have this?
A. In order to prevent downgrading with an RUU.
Q. I haven't run an RUU. How was my MainVer updated?
A. There are 2 reasons your MainVer could have been updated at this point.
The Original ICS Leak
DSB's new BAMF Rom (downloaded 1/17/2012 or later)
The original ICS leak that some of you flashed was still in RUU image form. Unfortunately, this was distributed with an updated MainVer string in the android-info.txt. When this was flashed, the new MainVer string was recorded into your device. DSB for some reason also included this new android-info.txt in his kernel PH98IMG.zip that is packed with his rom. I am not quite sure why he did that.
Q. What does this mean for me?
A. See new text at the top
Q. Why won't devs just add the new mainver to their roms to make my life easier?
A. They could, but then they would be forcing everyone to have this problem, not just you. It would also prevent everyone from using an RUU to repair their phones until a new one came out.
More Info:
No matter if you are going GB->GB or GB->ICS or ICS->GB you will need to have the correct mainver for your device. If you aren't having trouble going from rom to rom right now, you shouldn't even be looking at this guide. But if you got your mainver updated, you need to replace the android-info.txt for every single rom forever (until a new RUU comes out and it is safe to unify everyone's mainver)
Click to expand...
Click to collapse
That was quick! Nice work, Con. Hopefully this will help everyone out having these issues. I'll make sure I bookmark this page to link to if anyone should have issues. Thanks!
WasabiWa83 said:
That was quick! Nice work, Con. Hopefully this will help everyone out having these issues. I'll make sure I bookmark this page to link to if anyone should have issues. Thanks!
Click to expand...
Click to collapse
Thanks! That is a good idea about the bookmark. Ill do that too.
Yeah I had to answer this question a few times... this Q/A should make it easier.
I want to be sure I understand this correctly. If I flash an ICS rom I need to use the android-info mainver source 3.10.605.7 and if I want to revert back to a stock rom I need to use the android-info mainver source 1.02.605.6?
I have not installed any ICS roms yet, waiting for some more of the bugs to get worked out. I've been reading where many people are having issues with installing ICS roms and struggling with reverting back to stock.
I will try to make that more clear. Hold on.
I make a motion to sticky this thread. Anyone 2nd this motion?
Sent from my ADR6425LVW using xda premium
con247 said:
I will try to make that more clear. Hold on.
Click to expand...
Click to collapse
Thanks Con for the quick reply! I like to look over these forums and make sure I'm understanding some of the issues that are currently going on. I've been flashing roms for awhile but still consider myself a noob. Thanks again!
trickster2369 said:
I make a motion to sticky this thread. Anyone 2nd this motion?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yeah, definitely a 2nd for very this useful post. Especially since a lot of the ROM threads are getting off topic because of this. I saw Scott posted a link to this thread in his release posts. Good idea for the Devs to link back here too
Yeah this needs to be stickied...
Con... here is a post I did explaining Mainver... It is a bit more simplified, might be easier to follow for the new guys. (it also explains what RUU files are and what they do)
Marine6680 said:
RUU files are the official software releases from HTC.
RUU files are signed. (They give proper "official" codes to hboot to get past the s=on security)
This means that they can flash all parts of the device, even the bootloader and radio firmware, which we can not normally flash because it is write locked. (do to s=on we can't flash them even with root)
Sometimes people have issues and need to get the phone back to pure stock so they use the RUU.
Mainver is data on the software version number of the kernel (I believe... it may be for some other part, either way it is version info)
Think V1... V1.2... V1.5... V1.5.5
Because of s=on we are not allowed to "downgrade/revert" to older software versions.
The leaked ICS build has a newer Mainver, some people flashed the leak unmodified, and that changed the Mainver info. Now they need to use a special trick to trick the s=on security to allow flashing of older kernels. The ICS ROMs we have now, have been modified so they do not change the Mainver. This makes it easier to go back to GB or switch to other ROMs.
Click to expand...
Click to collapse
I am sorry but I am trying to make sense of all this. I am on Scott's CleanRom 2.1 will I need to use these instructions to go back to my stock room? This is my first HTC, I've only had Motorola phones up till now and I hate to admit it but this is all a bit over my head. I have been studying these forums for the last 2 days and I really have no clue how to use the backup I made of my stock GB Rom or even what kernel to use. I do regret not waiting to mess with this phone. Any help is greatly appriciated and I love all the work you have all put into this phone. Thanks in advance.
Sent from my ADR6425LVW using XDA App
snowride20 said:
I am sorry but I am trying to make sense of all this. I am on Scott's CleanRom 2.1 will I need to use these instructions to go back to my stock room? This is my first HTC, I've only had Motorola phones up till now and I hate to admit it but this is all a bit over my head. I have been studying these forums for the last 2 days and I really have no clue how to use the backup I made of my stock GB Rom or even what kernel to use. I do regret not waiting to mess with this phone. Any help is greatly appriciated and I love all the work you have all put into this phone. Thanks in advance.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
You're pretty much good because Scott's ROM does not update your MainVer. This is only for those ROMs that updated the MainVer. All you will need to do is restore your nand and flash the stock rooted kernel with Scott's Clean Flash tool. It's really more simple than you would think. You can find the Clean Flash tool and the stock rooted kernel in the dev forum. Just make sure that there is no PH98IMG.img on your ext sd card before you try to revert to your nandroid. Once you have restored your nand, you need to get to HBoot using the clean flash tool to make sure that you flash the stock rooted kernel. If you have the PH98IMG on your ext SD card, you would be kind of boned. Hope this helps a little.
So I flashed BAMF once, but it was weeks ago and I've since been using GingerSense without any issues, and that flashed fine after I tossed his boot.img back on, and then again after I did a full wipe a few nights ago. Is there any way to easily tell which mainver we're currently on? I'm assuming I'm ok since I haven't had to do anything else while flashing his ROM, guess I just wanna make sure.
rboddy said:
So I flashed BAMF once, but it was weeks ago and I've since been using GingerSense without any issues, and that flashed fine after I tossed his boot.img back on, and then again after I did a full wipe a few nights ago. Is there any way to easily tell which mainver we're currently on? I'm assuming I'm ok since I haven't had to do anything else while flashing his ROM, guess I just wanna make sure.
Click to expand...
Click to collapse
I believe mainver only changed if you flashed rezound cubed 1.0.2. If you didn't flash that, like I did, you should be fine.
Sent from my ADR6425LVW using xda premium
Well if that's true then yeah I'm ok, I see 1.0.2 is from 1/17 and I know I flashed it well before that, so I guess that explains why I haven't had any issues. Thanks!
rboddy said:
Well if that's true then yeah I'm ok, I see 1.0.2 is from 1/17 and I know I flashed it well before that, so I guess that explains why I haven't had any issues. Thanks!
Click to expand...
Click to collapse
Thanks, I added that date to the OP
It worked
Wasabi, I appriciate you giving me the little extra i needed to get back to stock. Thanks for the help.
So, is the MainVer stuck at the higher version number even if you manually flash the older boot.img from the PC?
The boot.img is independent of the mainver. Once you have it set higher, it can never go back. Possibly on an S-OFF device, but that would be pointless.
Oh thrill. So no ICS for us who flashed the dsb kernel? I hope the real HTC ICS is out soon then.....
This might be a dumb question but how do i return the rezound to complete 100% stock? thanks
If you never flashed ics ruu leak you can relock and use gb ruu.. if you did ics ruu, then best you can do is a gb Rom...ics not out yet...so gb is the ofical stock.
Sent from my ADR6425LVW using XDA
if you are running leaked ics ruu, then best you can do is back to gb stock rooted rom.
Thanks .where can I find the gb stock Rom?
Sent from my ADR6425LVW using xda premium
http://www.scottsroms.com/downloads.php?do=file&id=76
Here's the stock kernel
http://www.scottsroms.com/downloads.php?do=file&id=77
Don't forget to flash the GB SD Fix. I am having some difficulties locating a link for it.
EDIT:
Found it!
http://forum.xda-developers.com/attachment.php?attachmentid=952658&d=1332056950
Flash that after flashing the rom but before flashing kernel.
thanks for quick reply. how do i flash, im new to rezound.
If one changed the bootloader to be ra-vigor,
then how does one put back the stock bootloader?
Howard
angeloarzola said:
thanks for quick reply. how do i flash, im new to rezound.
Click to expand...
Click to collapse
First, are you unlocked?
Here check this out
http://forum.xda-developers.com/showthread.php?t=1418659
Go through read a few stickys. If you have any questions about the whole process, ask.
HowardZ said:
If one changed the bootloader to be ra-vigor,
then how does one put back the stock bootloader?
Howard
Click to expand...
Click to collapse
How did you do that one?!
it is unlocked
angeloarzola said:
it is unlocked
Click to expand...
Click to collapse
Ok good, just go through reading on how to flash custom roms, kernels, & AmonRA 3.15.
Once you read up and I mean READ you shouldn't have any issues if you decide to go to custom roms. Should be able to fix anything with the device once you have went through at least 3 custom rom flashes. I suggest one of the ICS roms as your first flash as it's rather straightforward vs rolling back to gingerbread from the RUU.
I thought the phone would say that you're re-locked if you tried to re-lock it. If that's the case, is there a way to revert that back to a "locked" status?
xustfosorcim said:
I thought the phone would say that you're re-locked if you tried to re-lock it. If that's the case, is there a way to revert that back to a "locked" status?
Click to expand...
Click to collapse
Only way for that to happen is if we get S-off for the device. Sounds like a method is done testing for the Rezound so a matter of them releasing it .
This doesn't return you to the old radios if you updated them, does it?
I have had bluetooth issues since going to the leaked firmware and ICS. Flashed everything multiple times, etc, etc with no improvements.
If there is a way to get back old radios and GB, or if this IS the way, I'll be ecstatic (or ex-static pun). From what I read I thought you couldn't get back to original radios.
Is this the solution to returning to old firmware?
Only way is with s-off and running a gb ruu. Doing those 2 things will give you back the gb radio.
You can run gb Roms until then....requires a sd card patch, check the op of a Rom and it explains it there. Might give a little better performance until s off is released.
Sent from my ADR6425LVW using XDA
Now that S-off is available is there a easier way of upgrading to the ICS firmware without having to lose root, have bootloader locked, having to unlock bootloader again and regain root?
Yes. Google android community rezound ics leak march 16. Download for both rooted and locked there.
johnc810 said:
Now that S-off is available is there a easier way of upgrading to the ICS firmware without having to lose root, have bootloader locked, having to unlock bootloader again and regain root?
Click to expand...
Click to collapse
Yes you can, but if you haven't noticed, people mixing and matching firmwares and hboots and ROMs without knowing what they are doing has been kind of a disaster today, since everybody now has S-OFF and is starting to screw around with crap they don't know about. The very fact that you are asking this question indicates that you shouldn't be flashing firmwares, radios, or HBOOTs until you've read up on each and can answer these types of questions on your own. Be careful!
If you aren't already aware of the sdcard issues, what causes them, and how to fix it, then you need to read a lot more before messing with anything else.
not trying to mix radios or anything like that just trying to upgrade my girlfriends phone an easy way. i found the gb firmware hboot but cannot find the ics firmware hboot
johnc810 said:
not trying to mix radios or anything like that just trying to upgrade my girlfriends phone an easy way. i found the gb firmware hboot but cannot find the ics firmware hboot
Click to expand...
Click to collapse
Just stay where you are! Your girlfriend will appreciate you much more if her phone just works correctly.. The ICS Firmware and radios are buggy at best and the results so far have been extremely hit or miss. GB is the latest working official firmware and HBOOT, so if you insist on running an ICS ROM, then use the old firmware patch. If you dont know what the old firmware patch is, then just leave your girlfriends phone alone.
Lol, the main reason I took s-off was so that I could get the ICS firmware out from under my GB. I can't tell you how much heat and battery problems that leak caused me! I will *not* be one of the first to d/l the ICS official build, no matter how much I liked actually using it.
haha i know what the ics patch is im no noob, i was just wondering if there was a flashable hboot with the ics firmware
johnc810 said:
haha i know what the ics patch is im no noob, i was just wondering if there was a flashable hboot with the ics firmware
Click to expand...
Click to collapse
Yeah, not getting it. Seems like the biggest problems with the ICS leak was the firmware. Why do you want that firmware?
johnc810 said:
haha i know what the ics patch is im no noob, i was just wondering if there was a flashable hboot with the ics firmware
Click to expand...
Click to collapse
There is, in the dev section there is a thread dedicated to radios in flashable zip format, and you can get the HBOOTs as well if you search. I highly recommend staying on HBOOT 2.11 and GB radios for now though, especially since the phone isn't actually being used by you.
i works well for other people ... it's his phone either help him or let him do what he wants even if that is bricking it ...
just help
im not sure if there is one sorry op
RoryHe said:
i works well for other people ... it's his phone either help him or let him do what he wants even if that is bricking it ...
just help
im not sure if there is one sorry op
Click to expand...
Click to collapse
Actually its not his phone, but then again I shouldn't expect people to actually read the thread either cause it never happens.
Having f***ed up my stuff mess with radios, I recommed you leave well enough alone. Its not nearly as staight forward on the Rezound as it was on the Inc, and there in lies my problem.
But I learned a lot today! So its not wasted experience.
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
Yeah I'd suggest you read a little more starting from the leak and forward. I had to reflash several time to get a stable ICS on my phone running the old-firmware patch, but then again I still ran into system problems. I have it all figured out now, and it didn't take long to solve the issue, but I'd recommend reading a bit. Jumping in the middle of development of rezound might be bad choice if you weren't here since day 1. .
dejahboi said:
Yeah I'd suggest you read a little more starting from the leak and forward. I had to reflash several time to get a stable ICS on my phone running the old-firmware patch, but then again I still ran into system problems. I have it all figured out now, and it didn't take long to solve the issue, but I'd recommend reading a bit. Jumping in the middle of development of rezound might be bad choice if you weren't here since day 1. .
Click to expand...
Click to collapse
Oh, now someone tells me to look before I leap.
I really should have known better...
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
heres my opinion, ics sucks. gb is silky smooth. jus sayin.
I say go for it. What could happen you piss your girlfriend off and spend the next 36 hr's trying to figure out what went wrong. Believe me I've been there. Lol
Sent from my ADR6425LVW using xda premium
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Why did HTC update hboot 1.15? Because they discovered an exploit flaw that we could gain S-OFF with, which is FAR better than being on HTC Dumlock. If you are not concerned with obtaining S-OFF via LazyPanda and the like, this should not be a concern.
Also, being on the new hboot means that backwards compatibility to ROMs that are not based on the new OTA could become an issue.
Sent from my LTEVO via XDA Premium
New h boot for you only means that you won't be able to get s-off for a very long time probably since nobody has figured out how to even s-off h boot 1.15 yet. You shouldn't have an issue flashing any rom from my understanding as long as it's through recovery.
Edit : I would listen to Michael on this one regarding ROMs sounds like he knows more lol.
Sent from my EVO using xda app-developers app
natefuhr said:
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Click to expand...
Click to collapse
Yes, you will be stuck flashing 2.13 roms with the 2.13 kernel. However, you can use one of the workaround methods (fastboot, flash image gui, twrp dumlock) to flashing an older kernel, and then flash roms based on a previous OTA base.
A ROM doesn't include an HBoot though, so there shouldn't be ROM/HBoot compatibility issues, right?
No, you can flash whatever version of android you want
Rxpert said:
No, you can flash whatever version of android you want
Click to expand...
Click to collapse
I don't think that's quite right (I could be wrong though).
If he wants to flash a JB-based ROM, he will definitely have to flash the boot.img separately via one of the workarounds mentioned.
If he wants to move between Sense-based ROMs, he *might* be OK. But he will not get any tweaks the dev may have made to the kernel included with his respective ROM.
I was referring to the question above me that asked about ROMs interfering with hboots
Having an old ROM on a new hboot won't cause issues.
Naturally, you need to have a working kernel for your ROM. So yes, you'll need to make sure you have the right kernel.
If he goes from any ROM to a ROM on a different base you'll have to install the correct kernel. . But I don't think that's what he was asking
Sent from my EVO using Tapatalk 2
Got it. I thought you were replying in general.
natefuhr said:
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Click to expand...
Click to collapse
I'd like to re-root after taking the OTA and I've searched all over for the instructions on how to load TWRP and SuperUser via fastboot, but can't find it. Can you assist?
Thanks
Rxpert said:
I was referring to the question above me that asked about ROMs interfering with hboots
Having an old ROM on a new hboot won't cause issues.
Naturally, you need to have a working kernel for your ROM. So yes, you'll need to make sure you have the right kernel.
If he goes from any ROM to a ROM on a different base you'll have to install the correct kernel. . But I don't think that's what he was asking
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
pbarrett said:
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
Click to expand...
Click to collapse
That's true for 1.12, since it allows you to flash kernels through recovery. The newer versions don't. That's the reason for using the fastboot or dumlock workarounds. That being said, I haven't heard anyone confirm yet that these methods still work on 1.19...I'm interested to know.
Sent from my EVO LTE
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
om4 said:
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
Click to expand...
Click to collapse
From what I can tell... No. You have to run HTC Dev first in order to get to where you can load a recovery program at which point you will have already had to wipe your phone to factory defaults.
It's unfortunate and the main reason I waited so long to unlock this way but as previously stated, Sense 4.1 was too hard to pass on
om4 said:
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
Click to expand...
Click to collapse
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
no, I let her take my phone for the weekend. she went camping with her her family and I dont feel comfortable knowing shes out in the middle of no where without a phone. her phone was disconnected because she lost her job 2 months ago and Im not about to pay $135 on top of my own bill
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Hell, I don't even let my girlfriend use my phone unless she asks nicely and I always keep an eye on her.
SoraX64 said:
Hell, I don't even let my girlfriend use my phone unless she asks nicely and I always keep an eye on her.
Click to expand...
Click to collapse
Mine doesn't even know how to use my phone...it's "confusing". IPhone ftw
Sent from my EVO LTE
pbarrett said:
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
Click to expand...
Click to collapse
Yes, every ROM includes a kernel.
But Hboot 1.15 and above do not let you flash things to the boot partition in recovery. The kernel goes in the boot partition. So you can't flash kernels normally through recovery.
If your on a sense ROM and flash an AOSP rom, the phone wont boot
If your on an AOSP ROM and flash a sense ROM, the phone wont boot
If your on an old base and flash a new base, the ROM will have issues (if it even boots)
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-wip.html
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Next, we are going to hear crap like, "my pet hamster ate my nandroid thumb drive."
Sent from my LTEVO via XDA Premium
Hey forum,
First off I'd like to say, I have done quite a bit of searching on this and either get caught up in endless pages of crap I don't fully understand or I just can't find the answer. My apologies if this issue is simple and out there.
With that said, I'm definitely a noob at all the rooting and ROMs for phones. I've spent 20 years using cell phones as.. well, phones! Had no idea the world that was waiting for me and the time consuming hours of research and trial and error.
So I got the Amaze and first off, wanted to root it so I used CWM which is currently running. I then get an update notification for ICS but every time I try to install it, I'm stuck at a green X logo.
Is there a way to install ICS with CWM already on my phone or do I need to remove it first? I have searched for both answers which is why I finally set up an account and created this thread.
Any and all assistance is greatly appreciated!
J
Get the all in one toolkit from hasoon it helps a lot n from where u at just find the ics ruu n flash thru bootloader
Sent from my HTC_Amaze_4G using xda premium
You might have to unroot it and install ICS firmware before upgrading to ICS roms, Im not completely sure, I might have done this the long way after reading into confusion. The shortest way to get ICS on your amaze is using 4ext to flash a rom if CWM does not work.
Well if ur coming from GB, make sure take everything back to stock..unroot.. stock GB and stock recovrry and relock the bootloader
Sent from my HTC Ruby using xda app-developers app
blindskater39 said:
You might have to unroot it and install ICS firmware before upgrading to ICS roms, Im not completely sure, I might have done this the long way after reading into confusion. The shortest way to get ICS on your amaze is using 4ext to flash a rom if CWM does not work.
Click to expand...
Click to collapse
Not accurate.
Perry977 said:
Well if ur coming from GB, make sure take everything back to stock..unroot.. stock GB and stock recovrry and relock the bootloader
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
Not accurate.
Download my toolkit. Relock your bootloader. Download the ICS ROM from here. Rename it to PH85IMG. Place on your EXTERNAL SD card. Boot into your bootloader. Let the stock ROM flash.
hasoon2000 said:
Download my toolkit. Relock your bootloader. Download the ICS ROM from here. Rename it to PH85IMG. Place on your EXTERNAL SD card. Boot into your bootloader. Let the stock ROM flash.
Click to expand...
Click to collapse
Thank you Hasoon! I actually wish I had seen this post earlier. I got stuck on so many different threads with users having the same exact issues and I finally was able to relock the phone. Not sure what I was doing wrong but it's all good now.
However, after relocking, I went back to stock instead of just doing the the ICS rom. As I'm typing this, my phone is in the process of of installing ICS via the OTA updater. Now I just want to root it again and move on for now. This crap is way too time consuming for me
**Edit - Is it normal for this phone to sit at the HTC Amaze 4g screen during boot for about a minute? I thought this thing booted super fast before I started messing with it
hasoon2000 said:
Not accurate.
Not accurate.
Download my toolkit. Relock your bootloader. Download the ICS ROM from here. Rename it to PH85IMG. Place on your EXTERNAL SD card. Boot into your bootloader. Let the stock ROM flash.
Click to expand...
Click to collapse
So you must flash to the stock ics rom before you flash into a custom ics rom if coming from GB?
blindskater39 said:
So you must flash to the stock ics rom before you flash into a custom ics rom if coming from GB?
Click to expand...
Click to collapse
Yes - you can't just flash the rom, as flashing the RUU in the bootloader as hasoon instructed actually repartitions the phone, and writes a bunch of files you can't flash anyways unless you had s-off(like radio, etc).
And for you or the OP, please click the amaze bible in my signature, it covers all of this, it is well organized- I challenege you to find a question that isn't answered in it(hint: if the question has been asked before, and it likely has, it is answered in that bible!)
Silentbtdeadly said:
Yes - you can't just flash the rom, as flashing the RUU in the bootloader as hasoon instructed actually repartitions the phone, and writes a bunch of files you can't flash anyways unless you had s-off(like radio, etc).
And for you or the OP, please click the amaze bible in my signature, it covers all of this, it is well organized- I challenege you to find a question that isn't answered in it(hint: if the question has been asked before, and it likely has, it is answered in that bible!)
Click to expand...
Click to collapse
Thanks... What is OP? Lol
blindskater39 said:
Thanks... What is OP? Lol
Click to expand...
Click to collapse
Original Poster I believe