http://forum.xda-developers.com/showthread.php?t=1509754
This new app for sensation/e3d etc. got me thinking. It is for devices that have S-ON but are unlocked. I believe I can fix all of our boot image installing woes with the process this app outlined. Once I finish my physics homework, I am going to get some scripts cooking and I think we can have roms install the boot images from recovery.
con247 said:
http://forum.xda-developers.com/showthread.php?t=1509754
This new app for sensation/e3d etc. got me thinking. It is for devices that have S-ON but are unlocked. I believe I can fix all of our boot image installing woes with the process this app outlined. Once I finish my physics homework, I am going to get some scripts cooking and I think we can have roms install the boot images from recovery.
Click to expand...
Click to collapse
That would be awesome if you could get that working. That would definitely have me unlock and root. I've just been screwing with my Inc waiting for this to happen. Thanks
sent from my sexy Htc Rezound
It will eliminate mainver error too.
con247 said:
It will eliminate mainver error too.
Click to expand...
Click to collapse
that would cut alot of thread derailing as well lol
Sent from my ADR6425LVW using Tapatalk
I saw this also and immediately thought that it would be awesome for the rezound hope you can get this to work
Sent from my Galaxy Nexus using XDA App
Its gonna work... it won't have the nice app but it will work. And it will be easy. Really Easy. For both devs and users
con247 said:
Its gonna work... it won't have the nice app but it will work. And it will be easy. Really Easy. For both devs and users
Click to expand...
Click to collapse
If you can fix my MAINVERSION error, I would forever grateful! Sick of having to go into the roms and changing the android info! Its just a pain having this S-ON to deal with.
Yeah it works Should resolve mainver problems
boogerburns said:
If you can fix my MAINVERSION error, I would forever grateful! Sick of having to go into the roms and changing the android info! Its just a pain having this S-ON to deal with.
Click to expand...
Click to collapse
What I don't get is why the devs can't just agree en masse which mainver they're going to use, and then everyone uses that version.
Well they shouldn't use one higher than the RUUs we have so we can restore if necessary. I have had to RUU before because I corrupted my cache partition once.
But some devs used the ICS leak mainver and some people were idiots and installed the leak before it was ready and got their mainvers higher than what we have RUUs for.
con247 said:
Well they shouldn't use one higher than the RUUs we have so we can restore if necessary. I have had to RUU before because I corrupted my cache partition once.
But some devs used the ICS leak mainver and some people were idiots and installed the leak before it was ready and got their mainvers higher than what we have RUUs for.
Click to expand...
Click to collapse
That's one of the reasons I wait a day or so to flash a new ROM if it just getting released. I always wait to see what the problems are first.
I just check it first and replace the android-info as needed. I am still on the 1.x mainver because I am careful and I was one of the first to flash the ICS leaks
con247 said:
I just check it first and replace the android-info as needed. I am still on the 1.x mainver because I am careful and I was one of the first to flash the ICS leaks
Click to expand...
Click to collapse
I didn't know about the entire mainver thing until the leak came out. I'm new to HTC phones and stuff. But I'm on the 2.x mainver just because I forgot to change it the other day when I was in a flash frenzy. Oh well
u can roll it back if you want
con247 said:
I just check it first and replace the android-info as needed. I am still on the 1.x mainver because I am careful and I was one of the first to flash the ICS leaks
Click to expand...
Click to collapse
This will be great once you get it running.
I'm curious what the reason is that you want to remain on 1.x when the official update brought the phone to 2.x? I'm on 2.x but running a ROM from 1.x even though they just came out with an update for 2.x because I want to keep the red theme made for it.
Btw... the dsb kernel was installed in recovery, like the AnthraX one is. Flashed a zip in recovery that made the PHzip that flashed as an update. Is this different than that?
I haven't flashed the new radios and stuff.
con247 said:
u can roll it back if you want
Click to expand...
Click to collapse
and how would one go about doing that? You mean that crazy method that could brick the phone? If that's the case, I'll just stick with the one I have
con247 said:
I haven't flashed the new radios and stuff.
Click to expand...
Click to collapse
Understood. I'm wondering why you've chosen not to, not why it hasn't happened technically.
feralicious said:
Understood. I'm wondering why you've chosen not to, not why it hasn't happened technically.
Click to expand...
Click to collapse
If it ain't broke, don't fix it... I don't want to risk ****ty battery life or something for better signal because I have no signal/speed issues.
WasabiWa83 said:
and how would one go about doing that? You mean that crazy method that could brick the phone? If that's the case, I'll just stick with the one I have
Click to expand...
Click to collapse
It isn't that crazy or that dangerous. I have flashed my misc a few times when I was seeing if I could hex edit the CID to HTC__001 instead of VZW__001 which would have allowed HTC dev unlock before we got their blessing.
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
Im S-ON So When I Try To Flash A ICS ROM I Also Have To Flash The Rls Kernel. Well Unfortunately I Haven't Been Able To Try ICS ROMS Becouse Whenever I Try To Flash The Kernel It Says It's A Bad Package And Won't Flash. I've Re-Dwnloaded Multiple Times And Its Still Just Not Working. does Anyone Have Any Advice?
CDMA or GSM? What are you using to flash? What rom are you flashing? and why are you using that kernel? It's a little outdated...
netwokz said:
CDMA or GSM? What are you using to flash? What rom are you flashing? and why are you using that kernel? It's a little outdated...
Click to expand...
Click to collapse
CDMA, 4EXT, A Couple ICS Roms, And I Am Useing The Kernel Becouse Since I'm S-ON I Have To Flash This So I Dont Get Reboots On Startup And Such. And You Say Is Is A Little Outdated So Is There A New Kernel For This Problem?
Have you set up 4ext to know that you are s-on? I thought since that option is there, there is no need to flash a kernel separately? I'm not to sure as I am not s-on. And I don't think there is another kernel right now. but most ICS roms run best on the stock kernel for now.
netwokz said:
Have you set up 4ext to know that you are s-on? I thought since that option is there, there is no need to flash a kernel separately? I'm not to sure as I am not s-on. And I don't think there is another kernel right now. but most ICS roms run best on the stock kernel for now.
Click to expand...
Click to collapse
Yes I Have And There Isn't But It Seems Like Something Is Wrong With The Kernel Zip But Thanks Anyway
Flash image GUI?
Sent from my PG86100 using XDA
Have you tried to re-download the zip?
Threevo said:
Flash image GUI?
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
????
netwokz said:
Have you tried to re-download the zip?
Click to expand...
Click to collapse
Yes Multiple Times
NexusS4gFreak said:
Yes Multiple Times
Click to expand...
Click to collapse
Well, I'm not sure how much more help I can be... Have you looked into downgrading or using the new Juopunutbear method to get s-off? would make life a lot easier...
netwokz said:
Well, I'm not sure how much more help I can be... Have you looked into downgrading or using the new Juopunutbear method to get s-off? would make life a lot easier...
Click to expand...
Click to collapse
I Have, Just Wasn't Sure I Wanted To. Have You Tried One Of These? And Thanks.
No I have not, I've been unlocked since the beginning. I know the downgrade method is fairly easy now, but still tricky. The Juopunutbear I hear doesn't require you to downgrade. So I'm not sure, just read up on both threads and see which you are more comfortable with. If you don't want to, I'm sure someone else will chime in and give more advice on your current problem.
I've tried the hboot downgrade and its was so much easier than I'd expected. After finding the right files for my phone, the whole process took me about 20 mins. Hardest part was pricking the phone LOL. After that it was just load closeones's toolkit, and it pretty much does the rest of the work for u. Just read the guide 4x and watch some YouTube view beforehand.
I did a lot of reading and read 1000x diff guides on how to flash and used so many diff flash method to het my phone out of bootloop. So by the time I got fed up and decided to downgrade, i had some decent flashing experience.
NexusS4gFreak said:
I Have, Just Wasn't Sure I Wanted To. Have You Tried One Of These? And Thanks.
Click to expand...
Click to collapse
I used the live CD and had my phone downgraded and s-off inside of an hour. As long as you can follow the directions to a T, it's painless.
Sent from my PG86100 using Tapatalk
My buddy and i were one of the first among to attempt the bricking method
(scary as hell at first) and it was actually very simple. And i say first because we had only seen a few who had officially posted about it i could be wrong lol my laptop if dual booted with Linux so all i did was set up my other computer and ran the first set on that one, then ran the linux part on my alienware. The worse you can do is brick it- but then again thats what you want. I accidentally upgraded my firmware and now im 1.5 S-OFF lol doesnt bug me at all but my wife's 1.4 S-OFF as soon as mine was done. just read, read, READ before you attempt it and make sure you have every code written down or copied and its cake man! no shame in trying
:laugh::laugh:
Looking foward to RUU
Anyone can get it??
I NEED IT!
GuiDeJuShi said:
:laugh::laugh:
Looking foward to RUU
Anyone can get it??
Click to expand...
Click to collapse
I was messing around with the new boot loader on a new phone and managed to unlock and get a recovery, but SU wouldn't flash, then it said it flashed, but still didn't fash, So I went ahead and tried to flash a rom anyway hoping it would work because the rom was rooted, Wrong answer. lol
And the ONE thing I DIDNT do when I got the CWM was MAKE A BACKUP!!! So I screwed up bad.
Now I've bee stuck at splashscreens for 2 days on a 3 day old phone.
Yeah, me too. I need the RUU as well. I am running mean rom right now with the kernel that allows it to work with hboot 1.58. But I would like to be able to go back to stock if necessary.
If you're stuck with 1.58 like me I suggest you install mean rom and flash the kernel in the Mean-Rom folder on your SD card so your wifi and 4G work.
Yeah id like to have the official ICS RUU as well.
IAmSixNine said:
Yeah id like to have the official ICS RUU as well.
Click to expand...
Click to collapse
This is exactly what Sprint and HTC wanted to accomplish. I would give it time. The devs should have a smooth running ICS / kernel soon. I am betting they will have something for all HBOOTs out there. I am still sitting on my Mean ROM for GB... with 1.4. And I will wait to make the leap to ICS... because I don't feel we should have to leave 1.4
I like having the option of reverting back to stock in case I screw something up lol.
Sent from my PG86100 using Tapatalk
Yep gotta love s-off am I right?
Sent from my PG86100 using xda premium
http://uppit.com/o8enbe4dswzs/RUU_S...06__NV_NV_SPCS_1.43_release_271101_signed.exe
EGOvoruhk said:
http://uppit.com/o8enbe4dswzs/RUU_S...06__NV_NV_SPCS_1.43_release_271101_signed.exe
Click to expand...
Click to collapse
This link is not working, where else can I find this?
Tipharet said:
This link is not working, where else can I find this?
Click to expand...
Click to collapse
http://d-h.st/OXD
iNdioNicarao said:
http://d-h.st/OXD
Click to expand...
Click to collapse
Thanks for this!
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