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
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.....
Edit 3: Well more news. I have found that it's a problem with OTA and the new base with ICS builds. Seems like the cpu settings aren't wanting to stick at all. It's min/max is set at 100%. Disabling Perflock with Antutu and Setcpu seem to not be working as well. I saw on a different forum that someone else was having this same problem and was suggested to flash BAMF's new sense boot img. This unfortunately did nothing. Am and two other people only having this issue? If so, man i'm unlucky
So I ran the OTA from Con247's thread here And now I am having crazy issues:
Code:
1) Battery is overheating like crazy. Staying at 114F consistently
2) Had the "Dead Battery + CWM" issue like seen [URL="forum.xda-developers.com/showthread.php?t=1489687"]here[/URL]
Now I have resolved the second issue, pain in the ass but solved. I was wondering if anyone had any advice for the first problem? Or if running an older RUU I'm thinking RUU_Vigor_VERIZON_WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_221502_signed.exe
Any issues with going back? Is it even possible? This is a good arguement for having S-off so I can flash whatever I want. Thanks for the help!
Edit1: After further testing I have found that I can run GB with the battery hovering around 88F-92F while doing nothing and about 94F-96F while syncing. (Just flashed CleanROM GBE 1.7.5 for testing) Stock (from RUU) is running cool at 82F-86F
Edit2: Can anyone also give me some insight to normal battery temperatures? OC, stock, Heavy Use w/4g, Heavy Use Wifi, Screenoff... ect.)
My experience was similar. I think something in the OTA kernel is eating battery and causing heat. When I used that same process it didn't work quite right for me. I ended up RUUing to the latest official build and that helped some. Con's process does update your boot loader though and the old RUU will see that and fail. Your mainver should be updated too... So that can cause problems going back too.
I went to an ICS from and that helped my overheat issue some. I recommend the RUU and checking out one of those . You should see some improvement.
a-jive said:
My experience was similar. I think something in the OTA kernel is eating battery and causing heat. When I used that same process it didn't work quite right for me. I ended up RUUing to the latest official build and that helped some. Con's process does update your boot loader though and the old RUU will see that and fail. Your mainver should be updated too... So that can cause problems going back too.
I went to an ICS from and that helped my overheat issue some. I recommend the RUU and checking out one of those . You should see some improvement.
Click to expand...
Click to collapse
So run the acutal RUU? The latest or an older version?
If you took the OTA, you have to run the latest RUU. 2.01.xxx.xx.
So it seems that running the older RUU wouldn't work because it detects your version and will tell you that you have a newer version.
There's a new tool from drellisdee that will change your mainver using a script.
HERE: http://forum.xda-developers.com/showthread.php?t=1526316
So... I think you can use that and put yourself back to 1.x and run the 1.x RUU. You might want to check in that thread though. Also, I don't know for sure that it will revert your hboot and radios and such by running the older RUU or not. Worth a try though.
I also think I've read something about being able to revert the radios back to the original ones, not sure where that was though, and may have just been a post of someone else who thought it was possible.
Yeah good idea, I was thinking that too. I unfortunately cannot find an older RUU that isn't uploaded to FileFactory. Man that place is the worst. So what if every other uploader has shutdown in fear of persecution. And because of that they're severely overloaded. I need my RUU's dammit.
Can anyone also give me some insight to normal battery temperatures? OC, stock, Heavy Use w/4g, Heavy Use Wifi, Screenoff... ect.)
I mis spoke above... When I used Con's manual method it updated my HBOOT (not bootloader) which caused the 1. RUU to fail (I was using an older method to rewrite my mainver to 1.000.00.000, or whatever).
I used the newest official RUU which I found on football's sticky'd post in the dev section. If that's missing now let me know and I can hook you up the flash able RUU file.
As for norms, there a a few threads on the topic, but I usually max out at like 125 when playing games or surfing on 3G 4G. That's too hot IMO, but I saw 140 once playing GTA when I was in the same place you are now.
nolimit78 said:
Yeah good idea, I was thinking that too. I unfortunately cannot find an older RUU that isn't uploaded to FileFactory. Man that place is the worst. So what if every other uploader has shutdown in fear of persecution. And because of that they're severely overloaded. I need my RUU's dammit.
Can anyone also give me some insight to normal battery temperatures? OC, stock, Heavy Use w/4g, Heavy Use Wifi, Screenoff... ect.)
Click to expand...
Click to collapse
Don't know what to tell you. You can't run the older RUU even if you set your main version back. It will see the newer hboot and fail.
I did not change anything from the OTA update package. I just added root and turned it into a flashable rom. Any problems that you have are likely due the new radios or the new OTA rom itself. Alot of people have had back luck with the OTA rom and new radios/firmware. That is HTC's fault. All I did was simplify the install for rooted users.
con247 said:
Don't know what to tell you. You can't run the older RUU even if you set your main version back. It will see the newer hboot and fail.
I did not change anything from the OTA update package. I just added root and turned it into a flashable rom. Any problems that you have are likely due the new radios or the new OTA rom itself. Alot of people have had back luck with the OTA rom and new radios/firmware. That is HTC's fault. All I did was simplify the install for rooted users.
Click to expand...
Click to collapse
con... I read a post by someone who thought you had a method to go back to the old radios... Was that incorrect?
Sent from my ADR6425LVW using Tapatalk
No I don't have one. It is not possible without S-OFF. Whoever posted that does not know what they are talking about.
con247 said:
Don't know what to tell you. You can't run the older RUU even if you set your main version back. It will see the newer hboot and fail.
I did not change anything from the OTA update package. I just added root and turned it into a flashable rom. Any problems that you have are likely due the new radios or the new OTA rom itself. Alot of people have had back luck with the OTA rom and new radios/firmware. That is HTC's fault. All I did was simplify the install for rooted users.
Click to expand...
Click to collapse
For the record, I wasn't hating on what you put together, I had an error during my first try, and once I got it to take something was just still off. I'm sure it was a user error!
a-jive said:
For the record, I wasn't hating on what you put together, I had an error during my first try, and once I got it to take something was just still off. I'm sure it was a user error!
Click to expand...
Click to collapse
I am fully aware that you aren't hating lol... I was just making sure that you know that you would have had the same experience if you had installed from the RUU.
con247 said:
No I don't have one. It is not possible without S-OFF. Whoever posted that does not know what they are talking about.
Click to expand...
Click to collapse
Yeah, I think they were mistaking what your Stock OTA ROM was for. Thanks for clarifying.
Sent from my ADR6425LVW using Tapatalk
OP updated with more findings. Also I re-read some of what I posted. I wasn't trying to place any blame on any one. Especially con247. You've, from what I've been seeing, have been a huge help around the community and I meant no disrespect.
Also-- coming from the 3D forums have really made me post apologies just to make sure nothing is taken the wrong way. I don't want to piss anyone off and have them not participate anymore. Effin haters are driving devs from our forums..
i am having the same problem with new new radios and firmware. nothing i have tried has given me the good battery life and low temps i had before the new radios. i really want s-off or someway of flashing the old radios. i was even wondering if ou could add the radio from the old ota to the new leak ruu and trick it into flashing the old radios but i doubt that would work.
Try using Scotts super wipe tool and re flashing the ROM. That's what helped me, I think my manual wipes kept missing things and freaking my phone out. Also reinstall everything from the market, my experience with restoring backup apps on a new rom has caused problems. Anyway these are all just suggestions that have helped me! Good luck!
Edit: since doing the above steps my Rezound hardly ever goes above 100 unless I'm tethering on 4g. And my battery life is good enough to get me through the day on the stock battery
Sent from my ADR6425LVW using XDA
Esandorf said:
Try using Scotts super wipe tool and re flashing the ROM. That's what helped me, I think my manual wipes kept missing things and freaking my phone out. Also reinstall everything from the market, my experience with restoring backup apps on a new rom has caused problems. Anyway these are all just suggestions that have helped me! Good luck!
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
thanks I'm going to try them.
Sent from my HTC Rezound
nev310 said:
thanks I'm going to try them.
Sent from my HTC Rezound
Click to expand...
Click to collapse
Scott is testing a new kernel in the dev forum to try and help address the issues if what I already suggested doesn't work, check it out!
Esandorf said:
Scott is testing a new kernel in the dev forum to try and help address the issues if what I already suggested doesn't work, check it out!
Click to expand...
Click to collapse
ive been trying the kernel he posted and I'm still haveing the same issues.
Sent from my ThinkPad Tablet using xda premium
Ok I'm all set now, I got everything flashed, but now I sill have question.
I started with the ENG H boot then I wen to the safer hacked one.
I'm looking for ROMS now and they have a PH98IMG file. Is that the kernel or updated firmware? I wouldn't want to flash different firmware right?
also what about the old firmware patch for ICS roms?
http://forum.xda-developers.com/showthread.php?t=1614180
Do I need to be using that as Im still on the GM H boot?
and finally what about mainver errors? since Im s off will that still warn me?
I just want to be careful not to do anything I shouldn't now that most of the safety nets are gone.
Also sorry of my questions are silly, its late at work and I've been starting at this screen all day. Its time to go.
thanks
loki993 said:
Ok I'm all set now, I got everything flashed, but now I sill have question.
I started with the ENG H boot then I wen to the safer hacked one.
I'm looking for ROMS now and they have a PH98IMG file. Is that the kernel or updated firmware? I wouldn't want to flash different firmware right?
also what about the old firmware patch for ICS roms?
http://forum.xda-developers.com/showthread.php?t=1614180
Do I need to be using that as Im still on the GM H boot?
and finally what about mainver errors? since Im s off will that still warn me?
I just want to be careful not to do anything I shouldn't now that most of the safety nets are gone.
Also sorry of my questions are silly, its late at work and I've been starting at this screen all day. Its time to go.
thanks
Click to expand...
Click to collapse
ROMs generally will never have firmware present unless it specifically states otherwise (perhaps somebody will release one after an OTA if there's a new firmware update). Prior to last week, we all had S-ON (well most of us) so all ROMs came with a script that would dump the boot.img (kernel and RAMdisk) into a PH98IMG.zip, then reboot to bootloader so you can flash it.
Use the old firmware patch for ICS ROMs only if you are on HBOOT 2.11 or lower.
I'm not sure about mainver issues... I don't think they matter now... but if you do get that error there's a simple fix thats been around for awhile.
I am on 2.11 so I would need the patch. Is it ok to use even it I'm not on am ics Rom, should I flash it just in case or wait until I need it.
Yeah I was kinda thinking the same thing about the mainver. Not sure either though
Sent from my ADR6425LVW using Tapatalk
loki993 said:
I am on 2.11 so I would need the patch. Is it ok to use even it I'm not on am ics Rom, should I flash it just in case or wait until I need it.
Yeah I was kinda thinking the same thing about the mainver. Not sure either though
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
The patch is apart of the system so you only flash it when you are going to run a ics Rom based on the ics firmware. You already have the patch files in the Rom you are running if its GB. But when you flash a new Rom the system is wiped which is why you need to flash the patch. I hope I explained that ok.
Sent from my HTC Vigor
Thanks for this thread, answered some of my nagging questions
Andro X said:
The patch is apart of the system so you only flash it when you are going to run a ics Rom based on the ics firmware. You already have the patch files in the Rom you are running if its GB. But when you flash a new Rom the system is wiped which is why you need to flash the patch. I hope I explained that ok.
Sent from my HTC Vigor
Click to expand...
Click to collapse
I understand, its ok. You right though dont know what I was thinking, of course the system gets wiped.
Im debating which ROM to run now. I was going to go with one of the BAMFs, but I also would mind a senseless ROM either.
Is it wrong that I actually kinda like Sense, I just wish it didnt bog the phone at times.
Also I thinking its probably best to say on the 2.11 firmware, that way I can still run GB if I want and go to ICS ROMS too if I want with the patch.
I like sense too especially since this is my first HTC phone so its something different for me. I had Motorola's in the past. I'm on GB firmware with the eng hboot and running ics Clean Rom.
Sent from my HTC Vigor
Well Sense is certainly an upgrade for me from TouchWiz....I miss a few things but overall it is better...
I think you would be happy with CleanROM, extremely fast and reliable ICS build. You would never know it wasn't stock.
I have my own silly question...why do I need htcdev unlocked to get s-off. Just rooted and s-offed my of MT4G for the fun of it. Seems like we should be able to s-off without official unlock support
Sent from my ADR6425LVW using xda premium
Geoi1006 said:
I have my own silly question...why do I need htcdev unlocked to get s-off. Just rooted and s-offed my of MT4G for the fun of it. Seems like we should be able to s-off without official unlock support
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Not sure about MT4G, but I don't think the control bear program can access everything it needs on the Rezound without being unlocked. Just a guess mind you .
Geoi1006 said:
I have my own silly question...why do I need htcdev unlocked to get s-off. Just rooted and s-offed my of MT4G for the fun of it. Seems like we should be able to s-off without official unlock support
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
You have to be rooted to acquire s-off. Up until this point you had to be unlocked to acquire root. Now, if you are s-off you can root without unlocking. It's a vicious circle! Lol!
I just haven't gotten to unlock since I don't have home internet access
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
i am really curious as to what does flashing a new hboot does, reason i ask is because i unlocked my device without issues, i also obtained s-off thanx to our wonderful devs,and im running venom rom. however im still on the old software. to me everything is running fine as far as i know so i dont want to take ota and lose everything, now im also seeing new hboots or ENG HBOOT and im wondering if i should flashed them since i have s-off but i would like to know the benefits of it, thanx
Flip35 said:
i am really curious as to what does flashing a new hboot does, reason i ask is because i unlocked my device without issues, i also obtained s-off thanx to our wonderful devs,and im running venom rom. however im still on the old software. to me everything is running fine as far as i know so i dont want to take ota and lose everything, now im also seeing new hboots or ENG HBOOT and im wondering if i should flashed them since i have s-off but i would like to know the benefits of it, thanx
Click to expand...
Click to collapse
Most of the hboots in the section are for devs and modders. If you just flash roms to get root experience, there is no need to worry about updating to a new hboot. Only time it is absolutely necessary is when HTC releases a firmware update.
dragonstalker said:
Most of the hboots in the section are for devs and modders. If you just flash roms to get root experience, there is no need to worry about updating to a new hboot. Only time it is absolutely necessary is when HTC releases a firmware update.
Click to expand...
Click to collapse
Thanx man, do u recommend that I go ahead and take ota?
Flip35 said:
Thanx man, do u recommend that I go ahead and take ota?
Click to expand...
Click to collapse
Most of the devs are working on OTA updates to their individual roms. I would just wait for whatever rom you are running to be updated. Saves you the problems of trying to fix your device if anything does go wrong with the OTA.
dragonstalker said:
Most of the devs are working on OTA updates to their individual roms. I would just wait for whatever rom you are running to be updated. Saves you the problems of trying to fix your device if anything does go wrong with the OTA.
Click to expand...
Click to collapse
Yup thats the reason why i didnt update, everything is working fine for me n now s-off even better...thank for the help
Flip35 said:
Yup thats the reason why i didnt update, everything is working fine for me n now s-off even better...thank for the help
Click to expand...
Click to collapse
No prob. that's what we are here for.
Flip35 said:
Thanx man, do u recommend that I go ahead and take ota?
Click to expand...
Click to collapse
I would not take the ota update... But I would flash the newer radio to improve general connectivity that Verizon has implemented in the update... You don't need the eng hboot for that... Look in original development for the radio thread
Sent from my HTC6435LVW using Tapatalk 2