So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
I'm unlocked but not s-off.
stock HTC Sense build that came with phone
Android 4.0.3
Sense 4.0
Software version 1.13.651.1
HTC SDK 4.2
So I've searched all over and its so scattered i don't know what to make of it.
If i take ota update what happens given my above specs? Lose root? Perm loss of s-off but can still root?
If it removes root privileges as a result or whatever, is there a method to get root back after the ota so i can wifi tether, etc?
If i don't take ota update is there a hacked zip package available i can run in recovery to get it up to date without causing ill effects?
And most importantly, going to a newer hboot and 4.0.4, does the end justify the means? Is there must haves in it that far out weigh the encumbrance of the process?
I know the easiest thing is go custom ROM, but I'm not looking to reinstall everything so that's why I'm hoping i can just ota or equivalent.
Thanks for any help!
Things are less of a hassle if you s-off your phone. I suggest you do that and then you can flash away. Never take an ota, not worth the risk.
metalfan78 said:
Things are less of a hassle if you s-off your phone. I suggest you do that and then you can flash away. Never take an ota, not worth the risk.
Click to expand...
Click to collapse
^^^^^^ Agreed never take an OTA and go S-OFF while you still can alot of guys would kill to have your phone and have the ability to get S-OFF
Here's the stuff you gotta do to update firmware if you don't get s-off
Relock hboot and run ruu
Unlock hboot
Reflash recovery
Reflash superuser and busybox or custom rom
Or
Restore stock rom and recovery
Relock bootloader
Accept ota
Unlock hboot
Reflash recovery
Reflash superuser and busybox or custom rom
Do yourself a favor and get s-off
I made the mistake of thinking I would stay stock and not unlock my phone since I got the LTE. I should have know I would be right back to XDA devs. I did the OTA and now have to deal with not getting s-off fast booting my new kernals
s-off does sound the way to go and was my next step. You completely convinced me what direction I need to go.
Thanks for the replies so far!
I have a new HTC One that doesn't have the August OTA update. I've used revone for S-OFF and unlock (agian, unlock from revone, not htcdev.com) and am getting ready to root and apply a custom ROM.
But, before I do that, I want to find out how I can get the most current firmwares/radios/etc from the OTA update, without sacrificing root/unlock capability. I'm not sure the best way to do it given that I have S-OFF and unlock via revone, and what files I need to get, beyond the radio.
^^^
Bump. I'm perm rooted, unlocked, s-off with custom recovery but still on hboot 1.44 and software is 1.26.502.12. I'd like to update my firmware too. Is there a suggested RUU or stock ROM for the m7att?
edditnyc said:
^^^
Bump. I'm perm rooted, unlocked, s-off with custom recovery but still on hboot 1.44 and software is 1.26.502.12. I'd like to update my firmware too. Is there a suggested RUU or stock ROM for the m7att?
Click to expand...
Click to collapse
I might be able to help you here. I went through all of this yesterday.
DISCLAIMER: IF YOU BREAK YOUR STUFF, IT'S NOT MY FAULT AND I PROBABLY WON'T BE ABLE TO HELP YOU FIX IT. DO ANY OF THIS AT YOUR OWN RISK AND DO YOUR OWN RESEARCH I still consider myself and Android newb (big time) as this is only my 3rd day into modding.
Go to this post: http://forum.xda-developers.com/showthread.php?t=2365506
Halfway down the first post is the "Firmware Flashing" section where you can download all the bases. Note that 3.06.1700.10 is the GE base and 3.09.401.1 is an early leak of the 4.3 base expected with the 4.3 Sense release . All but the GE one are labelled custom although I don't know what's custom about them to be honest. Also there is a link to HBOOT 1.44, get that.
I flashed all of them in order, except the (GE one) like this: 2.17.401.1-> 2.24.401.1 -> 2.24.401.8 -> 3.09.401.1
Why did I skip the GE one? Solely because the .ZIP didn't say "custom". I have no idea what is custom on it. There really shouldn't be anythin gin that GE base that would do anything bad, and thus probably no reason to not flash that one before 3.09.401.1, but I didn't, so just telling you my experience as it occurred.
!!! This will upgrade HBOOT as you go if you use the files as-is !!! (As I recall, 2.24.401.1 went to HBOOT 1.44 and 3.09.401.1 to HBOOT 1.55)
Since you are S-OFF, you can just downgrade back to HBOOT 1.44. Or, to prevent the upgrade in the first place, you can extract each zip and replace the hboot_signedbyaa.img from within each .ZIP with the HBOOT 1.44 download. Then just re-zip the file and flash it. I ended up downgrading back to HBOOT 1.44 because you can S-OFF it if you need to set yourself S-ON again for some reason.
!!! Also important, this process made my touchpanel stop working on the JB 4.1.2 stock ROM !!!!! I believe this is because the touchpanel update included in 2.24.401.1 requires JB 4.2.2, which AT&T has not pushed out for the HTC One, but it is available on International models. So, if you have no intention to put on a custom ROM that is 4.2.2 (even the international one) or 4.3, then you need to remove the touchpanel update file (tp_SYN3202.img) from all of the firmware.zip before flashing.
If you already have a 4.2.2/4.3 ROM, then leave the touchpanel file in there.
If you are JB 4.1.2 and plan to immediately go to JB 4.2.2 or 4.3, then you can update the touchpanel even though it will make it not work in JB 4.1.2. Why? When you boot into custom recovery, the touchpanel itself will work (at least with TWRP 2.6.1.0, which is what I have running). I don't know if CWM Touch will work in this scenario, but you can use the physical keys for that one. But anyway, the point here is that you can update the touchpanel then immediately flash a new ROM and the touchpanel will work again. This saves you a step of having to update the touchpanel after the new ROM.
Something else to keep in mind is Radio's. The Radio's will upgrade with these bundles and you will end up with a radio different than AT&T's newest radio. My personal opinion is to stick with the newest AT&T release radio, which you can download here: http://forum.xda-developers.com/showthread.php?t=2419699 - The one labelled AT&T latest is a flashable .ZIP you can load in custom recovery. Or you can extract the ZIP and copy radio.img over to your firmware bundles if you want it to just put in the latest radio with the rest of the firmware. You can also flash radio.img in fastboot with "fastboot flash radio radio.img".
Some people are saying the 3.09.401.1 is a little buggy. I'm not actually using my HTC One for anything but playing with ROM's right now. I'm using another phone as primary device still, so I can't provide any comments. You may want to stick with the 2.24.401.8 base which is the latest for 4.2.2 builds. That base will work fine with a 4.3 based ROM.
As for me, I currently have the 3.09.401.1 base but with the latest AT&T release radio and HBOOT 1.44 in place of what's in the original bundle download.
if i S-off and root and install a Rom will i still be able to get OTA and will taking the OTA brick my phone or Put it back to S-on and Stock
or should i S-On then take the new 4.2 or 4.3 ota when it comes
isu8023 said:
if i S-off and root and install a Rom will i still be able to get OTA and will taking the OTA brick my phone or Put it back to S-on and Stock
or should i S-On then take the new 4.2 or 4.3 ota when it comes
Click to expand...
Click to collapse
No, you cannot get an OTA while on a custom ROM, therefore, it cannot brick your device. And the only way to get back to s-on is to intentionally give the command to do so. Cannot be done by an OTA. If you get s-off and want to take an update, you will need to be totally stock to do so. However, you DO NOT need to go back to s-on.
From my S-Off BadSeed DNA
Stock only
OTA updates are for STOCK only, and do not affect the S-OFF/S-ON of your phone.
I hear an echo.
From my S-Off BadSeed DNA
If you THINK you might want root and/or s-off, you should definitely do it BEFORE the update. Updates tend to block currently known rooting/s-off methods.
If you do root/s-off, then the update will not affect your device. You COULD choose to go s-on and take the update at any future point.
Most people that have rooted and have s-off will NOT take want the update, instead we will wait for one of the dev's to grab the update and adapt it to be used on a rooted / s-off device. Generally, in less than 1 day of VZW pushing the update, there will be a base rom available for s-off users to install that is basically the OEM update with a few minor variations (root added etc). Within 2-3 days, there will be more custom roms available that are based on the update. (Most the of popular roms that are being used right now are actually based on the HTC One update that was already released.)
Greetings,
I apologize if this is dumb, but I have been away a while, and am fairly new to this scene as is.
A few months ago, I flashed my EVO 4G LTE to 1.13.651.1 710 RD with root s-off and HTC sense. Since that time, Sprint has released OTA updates that flash the phone to the most recent HTC rom (3.16.651.3 I believe).
I would like to upgrade, even if I have to lose root, but naturally a full featured solution is better.
I can't OTA update, and that just puts me into TWRP, not to surprising. I would like to know how to get the latest update without bricking anything. As it's been almost 8 months since 3.16.651.3, you can sort of tell how cautious I am.
I wouldn't say no to a non Sense (pun not intended, but kept) rom, but I have heard those cause issues with various parts of the EVO 4G LTE's hardware, and I would like the phone to remain fully functional.
What is the best option. I'm leaving this fairly open for everyone's superior expertise.
IF you are indeed S-OFF and just HTC-Dev unlocked you can update your firmware manually then flash whatever rom you wish.
And you're gone lol
Whoops. Nevermind the s-off.
I'm tampered unlocked and "JEWEL PVT SHIP S-ON RL" with
HBOOT 1.12.0000
Radio 1.02.12.0427
OpenDSP-v25.1.0.32.0405
I'm still looking for the safest way to get to the latest HTC sense, or any android version that won't reduce functionality of my phone hardware. My brother tried Cyanogen on his phone a while back, but he went back to sense after issues with his voicemail.
If you want the latest firmware you'll have to go back to stock using RUU or get S-OFF and manually flash the latest firmware. With your setup I would go for S-OFF and manually flash the latest firmware. You can find three different ways to get S-OFF in the HTC EVO 4G LTE Original Android Development section (they're stickied at the top). A little reading should tell you which version will work best for your setup between Moonshine, Facepalm, and DirtyRacun.
Once you're S-OFF you can update your firmware on your own. Captain_Throwback has a link to the zip file in his signature (It's the link for the Evo 4G LTE Baseband: 1.12.11.1210).
You'll be S-OFF with the latest firmware and you'll be ready to flash any of the latest ROMs.
Best thing to do is get S-off, as stated above. You can use Facepalm or Dirty Racun to accomplish that. Facepalm is the easier of the two and takes about five minutes or so from start to finish. After that you can update your firmware and flash a JB ROM. If you click on the link in my sig you'll find instructions on how to update your firmware, as well as a link to Captain Throwback's firmware thread.