I just got my new Virgin Mobile HTC Evo V today. My previous device was a Samsung Galaxy-class phone (Infuse 4G), so I'm a bit lost with all of the HTC-specific terminology and procedures. All I've read seems to be written by and for people who already have some idea of what's going on. Sadly, I don't.
All I know is that my Evo V is on Hboot version 1.57. I basically want to put it in a state where I can flash ANYTHING I want, which I assume means that I'll need to be S-off with a custom recovery. Do I absolutely need to dowgrade Hboot? Must I be S-off? I just need an initial push in the right direction. If someone could give a brief synopsis of exactly where I need to start, along with some links to the corresponding tools, that would be very much appreciated. I hate feeling like a newb all over again, but hacking HTC doesn't seem to be nearly as simple or intuitive as it was with Samsung. I'm fairly adept at following directions, I just don't want to follow the wrong ones and do something stupid.
ApexPredatorBoids said:
I just got my new Virgin Mobile HTC Evo V today. My previous device was a Samsung Galaxy-class phone (Infuse 4G), so I'm a bit lost with all of the HTC-specific terminology and procedures. All I've read seems to be written by and for people who already have some idea of what's going on. Sadly, I don't.
Click to expand...
Click to collapse
Since you have an Evo V you might want to start here. There are no forums that are specific to the Evo V on XDA.
I do have a guide here in the general forum that works for getting root and S-OFF on the Evo V.
ramjet73
ramjet73 said:
Since you have an Evo V you might want to start here. There are no forums that are specific to the Evo V on XDA.
I do have a guide here in the general forum that works for getting root and S-OFF on the Evo V.
ramjet73
Click to expand...
Click to collapse
Isn't this 3D the EVO V? Thought they were the same D:
Sent from my shooter using xda premium
'Blu said:
Isn't this 3D the EVO V? Thought they were the same D:
Click to expand...
Click to collapse
Same hardware but not the same firmware and network configuration as was confirmed by Sprint users who flashed the "leaked" VM firmware last May. The custom ROM's can be configured for either carrier but not the firmware and the serial numbers (ESN's) are hard wired to a specific service provider.
Also, Virgin Mobile users also don't have the roaming options that Sprint offers.
ramjet73
ramjet73 said:
Same hardware but not the same firmware and network configuration as was confirmed by Sprint users who flashed the "leaked" VM firmware last May. The custom ROM's can be configured for either carrier but not the firmware and the serial numbers (ESN's) are hard wired to a specific service provider.
Also, Virgin Mobile users also don't have the roaming options that Sprint offers.
ramjet73
Click to expand...
Click to collapse
Well that sucks a tad bit. I forgot that the phones had very different network make up.
Sent from my shooter using xda premium
Gotta love a long and convoluted process that involves a lot of downloading. At the moment, I'm visiting a relative who doesn't have internet, so my only web access is to tether to my now-throttled data connection. Got about 6 more hours to go before the QADERSO download finishes. Thanks for the help so far. I took a quick peek at the htcdev site and unlocking procedure. I noticed that they don't have one that's VM specific. Should I just use the Sprint one when I get to that point?
ApexPredatorBoids said:
Gotta love a long and convoluted process that involves a lot of downloading. At the moment, I'm visiting a relative who doesn't have internet, so my only web access is to tether to my now-throttled data connection. Got about 6 more hours to go before the QADERSO download finishes. Thanks for the help so far. I took a quick peek at the htcdev site and unlocking procedure. I noticed that they don't have one that's VM specific. Should I just use the Sprint one when I get to that point?
Click to expand...
Click to collapse
Yes, you can unlock the Evo V 4G by selecting the Evo 3D on the htcdev website.
I don't consider downloading an all-in-one file "a lot of downloading" and if you think my guide is "convoluted" you're welcome to use the collection of guides that preceded it, including several on the other site that I linked above.
I've unlocked Samsung and other phones before and I know about the "one click" root utilities, but that's not the way HTC does things so we need to deal with it or stay stock.
ramjet73
ApexPredatorBoids said:
Gotta love a long and convoluted process that involves a lot of downloading. At the moment, I'm visiting a relative who doesn't have internet, so my only web access is to tether to my now-throttled data connection. Got about 6 more hours to go before the QADERSO download finishes. Thanks for the help so far. I took a quick peek at the htcdev site and unlocking procedure. I noticed that they don't have one that's VM specific. Should I just use the Sprint one when I get to that point?
Click to expand...
Click to collapse
It's quite a simple process, but it is a fairly long process. Takes about 30 minutes total to get unlocked, rooted, and running all good. Add that to getting ROMs and stuff. That totaled up to 3 days for me because I just could not find the best one, and I've found that Viper3D is great . Getting a 8000-9500 benchmark.
Success
Well, I didn't manage to bust it out in 30 minutes, but I got it done. Probably wouldn't have taken quite so long if I were less inept with command prompts. The "wire trick" was simultaneously simple and a huge pain in the ass. I spent probably 15 minutes doing it over and over and over. But all's well that ends well. I'm now HTCdev unlocked with S-off, and I'm running NegaLite BluROM. So, thanks, ramjet73, for the advice and putting your time into writing the guide.
I do have a few general questions still:
-what will absolutely need to be flashed with fastboot; kernels, radios, alternate Hboot versions?
-as far as having some semblance of universal compatibility, should I be fairly safe sticking with Jbear's Hboot version 1.57.5757?
-is there another Hboot version I could flash that would be more likely to be compatible with the vast majority of available ROMs?
ApexPredatorBoids said:
Well, I didn't manage to bust it out in 30 minutes, but I got it done. Probably wouldn't have taken quite so long if I were less inept with command prompts. The "wire trick" was simultaneously simple and a huge pain in the ass. I spent probably 15 minutes doing it over and over and over. But all's well that ends well. I'm now HTCdev unlocked with S-off, and I'm running NegaLite BluROM. So, thanks, ramjet73, for the advice and putting your time into writing the guide.
I do have a few general questions still:
-what will absolutely need to be flashed with fastboot; kernels, radios, alternate Hboot versions?
-as far as having some semblance of universal compatibility, should I be fairly safe sticking with Jbear's Hboot version 1.57.5757?
-is there another Hboot version I could flash that would be more likely to be compatible with the vast majority of available ROMs?
Click to expand...
Click to collapse
I myself have kept with the Jbear hboot and have been able to run the ROMs I wanted fine (that being MeanROM-ICS, Viper3D, and Harmonia) and it was all good. I have no clue about your other questions, sorry :[. I'm quite new to the Evo 3D and it doesn't seem as simple as my old One V.
ApexPredatorBoids said:
I do have a few general questions still:
-what will absolutely need to be flashed with fastboot; kernels, radios, alternate Hboot versions?
-as far as having some semblance of universal compatibility, should I be fairly safe sticking with Jbear's Hboot version 1.57.5757?
-is there another Hboot version I could flash that would be more likely to be compatible with the vast majority of available ROMs?
Click to expand...
Click to collapse
I usually recommend the JBear GB 1.50.5050 hboot. It will flash and boot all ROM's except the stock ICS ROM and one or two based on that version, as opposed to the 1.57.5757 version that won't boot any GB or AOSP based ROM's.
ramjet73
I've never been much of a fan of Android version 4.x. I just stumbled on what appears to be a very promising Gingerbread ROM, so it looks like I'm going to have to downgrade to Hboot 1.4. I'd assumed that since the phone came with ICS, I'd be stuck with 4.x. Apparently, that's not the case. I love me some GB.
ramjet73 said:
I usually recommend the JBear GB 1.50.5050 hboot. It will flash and boot all ROM's except the stock ICS ROM and one or two based on that version, as opposed to the 1.57.5757 version that won't boot any GB or AOSP based ROM's.
ramjet73
Click to expand...
Click to collapse
Will Jbear 1.50.5050 flash This ROM? I'm thinking someone posted in that thread that you had to be below Hboot 1.50 to flash it. If it will work with that ROM, could you supply a D/L or thread link?
ApexPredatorBoids said:
I've never been much of a fan of Android version 4.x. I just stumbled on what appears to be a very promising Gingerbread ROM, so it looks like I'm going to have to downgrade to Hboot 1.4. I'd assumed that since the phone came with ICS, I'd be stuck with 4.x. Apparently, that's not the case. I love me some GB.
Click to expand...
Click to collapse
Just be aware that all the GB ROM's are based on Sprint builds and as a VM user you will need to figure out what needs to be changed to get things like MMS working properly on the VM network.
I'm not saying you shouldn't do it, just be aware that it will take more than just flashing the ROM and you can get more help with the Evo V on the androidforums.com website in the forums for that version of the device.
ApexPredatorBoids said:
Will Jbear 1.50.5050 flash This ROM? I'm thinking someone posted in that thread that you had to be below Hboot 1.50 to flash it. If it will work with that ROM, could you supply a D/L or thread link?
Click to expand...
Click to collapse
Yes. The JBear 1.50.5050 hboot will flash and boot anything that the 1.4 or ENG 1.04 hboots handle and is based on a more current version of the Evo 3D bootloader. It also allows you to run more fastboot commands than a stock hboot like 1.4.
ramjet73
ramjet73 said:
as a VM user you will need to figure out what needs to be changed to get things like MMS working properly on the VM network.
Click to expand...
Click to collapse
Is it as simple as finding and using the proper APN settings, or is there more to it than that?
ApexPredatorBoids said:
Is it as simple as finding and using the proper APN settings, or is there more to it than that?
Click to expand...
Click to collapse
At least that, and maybe some changes to the build.prop file. I'm a Sprint user so I've never had to do it, but there are VM users here and on androidforums.com that can probably help answer that.
ramjet73
Related
has anyone attempted to write a new hboot using a goldcard? will this method work to gain s-off?
nixxofugi said:
has anyone attempted to write a new hboot using a goldcard? will this method work to gain s-off?
Click to expand...
Click to collapse
Since you are the first person I have seen even mention this "goldcard", I imagine the answer would be no.
I am curious, and I'm sure there are others. Could you give a brief explanation of this "goldcard" witchcraft with which you are acquainted?
I'd settle for a link to read, if you know of one.
A little info
http://forum.xda-developers.com/showthread.php?t=572683
nixxofugi said:
http://forum.xda-developers.com/showthread.php?t=572683
Click to expand...
Click to collapse
Interesting.
Has this been successful on any of HTC's more recent devices? I can't imagine an exploit that dates back to the Hero, would work on the more recent devices. I imagine what we are dealing with now, has been in place since the MT3G Slide. Wasn't that the first device that could not be S-OFF'd?
Would be awesome if it did, though.
devcurious said:
Interesting.
Has this been successful on any of HTC's more recent devices? I can't imagine an exploit that dates back to the Hero, would work on the more recent devices. I imagine what we are dealing with now, has been in place since the MT3G Slide. Wasn't that the first device that could not be S-OFF'd?
Would be awesome if it did, though.
Click to expand...
Click to collapse
I did a little digging, and it appears that this would not work on anything that shipped with Gingerbread.
This only works on devices that have both a stock Gingerbread and Froyo ROMs. The Gingerbread ROM is exploited with the "goldcard", which allows a downgrade to a Froyo ROM. The Froyo ROM is then the one that is actually used to S-OFF the device. Once the S-OFF flag is set, it remains in perpetuity.
Since there is no Froyo ROM to downgrade to, it won't work, we wouldn't be able to make use of an HBOOT that old on the Amaze ROMs. I think someone already tried to flash an older version of an ENG HBOOT, and was unsuccessful.
You can try this if you like... I'm still waiting for input. I'm too cowardly to try it myself since a phone is of vital importance for me.
http://forum.xda-developers.com/showpost.php?p=18770379&postcount=54
And a few posts prior to that said that the goldcard method didn't work. ref post #49.
Don't try it guys this is a year old or so and it was hard to do on the devices it was made for.
Sent from my HTC_Amaze_4G using XDA App
Hi all I am currently using a ics Rom with hboot 1.5 s on my goal is to be able to flash these roms with out using chads fix which helped me a lot thanks chad but it looks like the kernel won't be updated to fix breaks. So I have gone thru forums and have seen downgrading to 1.4 s off. My question is this if I downgrade will I loose the flash I have for metro pcs? And is it nessasary to downgrade to accomplish what I would like to achieve having ics without the breaks. Thank you all for the help.
sorry
Hi again sorry didn't say. I have a HTC EVO 3d cdma
Some roms have built in support for metro (like nocturnal ics), so you could downgrade and then flash one of those.
Or you could do a nandroid of your current setup and restore it after the downgrade process.
Sent from my PG86100 using Tapatalk 2
evo3d6 said:
Hi all I am currently using a ics Rom with hboot 1.5 s on my goal is to be able to flash these roms with out using chads fix which helped me a lot thanks chad but it looks like the kernel won't be updated to fix breaks. So I have gone thru forums and have seen downgrading to 1.4 s off. My question is this if I downgrade will I loose the flash I have for metro pcs? And is it nessasary to downgrade to accomplish what I would like to achieve having ics without the breaks. Thank you all for the help.
Click to expand...
Click to collapse
Before you attempt to downgrade, please write down all MetroPCS radio/PRI/PRL, etc info. Someone asked a similar question somewhere else about Boost. I believe he warned everyone that it will erase and you need all the info to restore his Boost (MOST LIKELY metroPCS) service.
You can also take a screen shot of the settings as well.
#Root-Hack_Mod*Always\
Thanks for the help
Ok Thank you all for your help but let me ask this there's this (wire trick) I hear there's a lot of success and I hear that some fail. If I did choose to use this method would it too remove flashed metro info? And does it have to be h-boot 1.4 s.off to flash the i.c.s roms or can I use 1.5 h-boot s.off? I'm still pretty new to this but starting to get the hang reading what a lot of great people are posting.
evo3d6 said:
Ok Thank you all for your help but let me ask this there's this (wire trick) I hear there's a lot of success and I hear that some fail. If I did choose to use this method would it too remove flashed metro info? And does it have to be h-boot 1.4 s.off to flash the i.c.s roms or can I use 1.5 h-boot s.off? I'm still pretty new to this but starting to get the hang reading what a lot of great people are posting.
Click to expand...
Click to collapse
From my reading, it seems either is ok. I still would suggest 1.4 s-off as that's what I have and it is solid for me. Roms flash with no trouble and I get no bootloops. But the 1.5 s-off method is easier so maybe someone with 1.5 s-off can report their success rate (ease of flashing roms, stability, etc).
Sent from my PG86100 using Tapatalk 2
evo3d6 said:
Ok Thank you all for your help but let me ask this there's this (wire trick) I hear there's a lot of success and I hear that some fail. If I did choose to use this method would it too remove flashed metro info? And does it have to be h-boot 1.4 s.off to flash the i.c.s roms or can I use 1.5 h-boot s.off? I'm still pretty new to this but starting to get the hang reading what a lot of great people are posting.
Click to expand...
Click to collapse
I think that's actually the thread where someone warned about his Boost info getting wiped, I could be wrong.
After s-off is achieved, hboot is sorta irrelevant. You can always flash a new hboot. I'm on eng hboot 1.04.
I upgraded my hboot from 1.4 to 1.58 and my Evo 3d reverted back to sprint, I had to pay again to flash it back to metropcs.
The same happened when I flashed a jelly bean rom. Tried 3 times different roms with no success. I've spent enough money already to buy a 4G LTE.
Sent from my PG86100 using Tapatalk 2
Long story short… I have been very busy for the last 6 months and not been keeping up with all the changes for the CDMA EVO 3D. I am not really sure the best way to get from here to there. I am not a noob and don’t really need my hand held or a dummy’s guide (I have been messing with Android since the HTC Hero and rooted lots of phones and pads). There has been just to many new ways to root and leaked roms…etc. It would be nice to skip all the BS and get caught up with what most people are currently doing.
My current config…
H-Boot: 1.40 s-off via Revolutionary Method
Recovery: TWRP v2.1.1
Rom: ViperRom Redline v2.5 RC2
Would it be better to just RUU back to stock Gingerbread then upgrade to ICS and re-root or is better way to get to ICS with root???? I am not trying save anything on my phone. I am a big fan of wiping and super wiping multiple times before loading a new rom. Also is there any benefit to H-Boot 1.5 or higher?
If this has already be asked can you point me to the correct thread.
Any help would be greatly appreciated.
Shark_HTC said:
Long story short… I have been very busy for the last 6 months and not been keeping up with all the changes for the CDMA EVO 3D. I am not really sure the best way to get from here to there. I am not a noob and don’t really need my hand held or a dummy’s guide (I have been messing with Android since the HTC Hero and rooted lots of phones and pads). There has been just to many new ways to root and leaked roms…etc. It would be nice to skip all the BS and get caught up with what most people are currently doing.
My current config…
H-Boot: 1.40 s-off via Revolutionary Method
Recovery: TWRP v2.1.1
Rom: ViperRom Redline v2.5 RC2
Would it be better to just RUU back to stock Gingerbread then upgrade to ICS and re-root or is better way to get to ICS with root???? I am not trying save anything on my phone. I am a big fan of wiping and super wiping multiple times before loading a new rom. Also is there any benefit to H-Boot 1.5 or higher?
If this has already be asked can you point me to the correct thread.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
If I'm reading right, just search the development forums for an ics rom, flash it and you're good to go. NEVER TAKE OTA
Sent from my EVO 3DMA with a little "Common Sense"
Tl;dr.
Just kidding. I'm running the latest ics rooted Roms on hboot 1.4 revolutionary s-off. I ran freeza's firmware update without the new hboot. This lets me run everything except the new kernel (which most new Roms don't use). If you insist on the new kernel, you can upgrade the hboot too, but you lose the ability to flash aosp and GB Roms.
So, in short, you just need to pick a rooted ics Rom and go. I like zr3dx, Meanrom, homebrew, or common ground.
I also recommend you change to 4ext recovery. It's really nice.
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
Tl;dr.
Just kidding. I'm running the latest ics rooted Roms on hboot 1.4 revolutionary s-off. I ran freeza's firmware update without the new hboot. This lets me run everything except the new kernel (which most new Roms don't use). If you insist on the new kernel, you can upgrade the hboot too, but you lose the ability to flash aosp and GB Roms.
So, in short, you just need to pick a rooted ics Rom and go. I like zr3dx, Meanrom, homebrew, or common ground.
I also recommend you change to 4ext recovery. It's really nice.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
Thanks that was exactly what I needed and I was getting tired of reading all the posts about the VM fiasco, and sticking a wire in the SD card…etc.
You are right it was “Tl;dr” but I also hate threads that go on forever because you don’t have enough info to answer the question.
Thanks again
Shark_HTC said:
Thanks that was exactly what I needed and I was getting tired of reading all the posts about the VM fiasco, and sticking a wire in the SD card…etc.
You are right it was “Tl;dr” but I also hate threads that go on forever because you don’t have enough info to answer the question.
Thanks again
Click to expand...
Click to collapse
More information > less information :thumbup:
Read, Search, Read again, ... Then Ask with Tapatalk 2
after downgrading from ICS to GB, my free ram become low from free 380mb on ICS to 222 on GB
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
First and foremost, I sincerely apologize if there is some information out there that I have missed or failed to read. I am a noob to this forum as far as posting goes but I've been reading posts here for some time and thus far I have been unable to find a solution to my problem.
This is the third time that I'm flashing my EVO 3D, however it is the first time I've actually used S-OFF. This particular iteration of my phone was completely vanilla ICS on hboot 1.58. I followed the dummy-proof guide stickied to this forum all the way through getting S-OFF through the "wire trick" method. At this point I wound up with a "jbear" version of hboot 1.58. Sweet deal.
Problem is I decided I wanted to try CM v10.1 so I had to change hboot to something below 1.57... No biggie. Except for I messed with the thing for hours and had absolutely no luck getting it to boot. The only thing that worked was returning to the jbear 1.58 hboot and restoring an earlier backup from 4EXT with the stock ROM.
Long story short after multiple flashes, going from jbear 1.58 to jbear 1.50 and back several times I finally got the phone running on CM v10.1 "Wild for the Night" with hboot ENG 1.04.
So... my question is as follows. Have I hosed something up in my tinkering by going back and forth between hboots multiple times? I'm concerned that doing the v1.58 "wire trick" S-OFF and then jumping from one hboot to the other only to wind up with ENG 1.04 might cause issues in the future.
I apologize for any incoherence on the above. It is now 6am and I've been at this for hours...
kriz225 said:
First and foremost, I sincerely apologize if there is some information out there that I have missed or failed to read. I am a noob to this forum as far as posting goes but I've been reading posts here for some time and thus far I have been unable to find a solution to my problem.
This is the third time that I'm flashing my EVO 3D, however it is the first time I've actually used S-OFF. This particular iteration of my phone was completely vanilla ICS on hboot 1.58. I followed the dummy-proof guide stickied to this forum all the way through getting S-OFF through the "wire trick" method. At this point I wound up with a "jbear" version of hboot 1.58. Sweet deal.
Problem is I decided I wanted to try CM v10.1 so I had to change hboot to something below 1.57... No biggie. Except for I messed with the thing for hours and had absolutely no luck getting it to boot. The only thing that worked was returning to the jbear 1.58 hboot and restoring an earlier backup from 4EXT with the stock ROM.
Long story short after multiple flashes, going from jbear 1.58 to jbear 1.50 and back several times I finally got the phone running on CM v10.1 "Wild for the Night" with hboot ENG 1.04.
So... my question is as follows. Have I hosed something up in my tinkering by going back and forth between hboots multiple times? I'm concerned that doing the v1.58 "wire trick" S-OFF and then jumping from one hboot to the other only to wind up with ENG 1.04 might cause issues in the future.
I apologize for any incoherence on the above. It is now 6am and I've been at this for hours...
Click to expand...
Click to collapse
no, switching your hboots won't cause any issues with your phone. I will tell you however, always make sure you're on a compatible hboot for any ROM you flash
You can change hboots 10 times a day until you change your phone, nothing will break because of that. The problem is that some hboots are incompatible with some roms and some android versions. For most Jelly Bean you need the x hboot, while for Ice Scream Sandwitch you need the y hboot. You get the point l. Nothing breaks as long as you properly change hboots and don't get errors in the process of doing so.
Relax and flash away whatever you want
When flashing a new HBOOT you need to boot into recovery and wipe your cache partition then reboot again to recovery using the reboot to recovery option within recovery. Then flash ROM and GAPPS. Also make sure to be using the VERY latest 4ext recovery. The test version
私のEVO 4G LTEから送信される。
Thanks!
Thanks for the responses, that's reassuring.
dastin1015 said:
When flashing a new HBOOT you need to boot into recovery and wipe your cache partition then reboot again to recovery using the reboot to recovery option within recovery. Then flash ROM and GAPPS. Also make sure to be using the VERY latest 4ext recovery. The test version
私のEVO 4G LTEから送信される。
Click to expand...
Click to collapse
I saw these suggestions on your development thread and followed them. This is how I finally got it to work with the ENG 1.04 and so far the ROM is working great.
Not to take my own thread off topic but is there a list of supported kernels for this ROM? I'm interested in under clocking, etc. and not sure if that's possible on stock.
kriz225 said:
Thanks for the responses, that's reassuring.
I saw these suggestions on your development thread and followed them. This is how I finally got it to work with the ENG 1.04 and so far the ROM is working great.
Not to take my own thread off topic but is there a list of supported kernels for this ROM? I'm interested in under clocking, etc. and not sure if that's possible on stock.
Click to expand...
Click to collapse
Stock kernel has what you need.
私のEVO 4G LTEから送信される。
Thanks!
dastin1015 said:
Stock kernel has what you need.
私のEVO 4G LTEから送信される。
Click to expand...
Click to collapse
Thanks. I found the option, I apologize for the noobishness.
you're fine. i swapped a few hboots a few months ago so I could run CM10.1 roms. i think im on 1.50 with no problems
A sense stock kernel? Can I get the link to a underclocked kernel for cm10.1? Because I think this might solve my problem of 3g not toggling off.
Sent from my HTCEVOV4G using xda app-developers app
SkinnyBiggs said:
A sense stock kernel? Can I get the link to a underclocked kernel for cm10.1? Because I think this might solve my problem of 3g not toggling off.
Sent from my HTCEVOV4G using xda app-developers app
Click to expand...
Click to collapse
Not sense. AOSP stock with max cpu 1128.
Sent from my Evo 3D CDMA using xda premium
SkinnyBiggs said:
A sense stock kernel? Can I get the link to a underclocked kernel for cm10.1? Because I think this might solve my problem of 3g not toggling off.
Sent from my HTCEVOV4G using xda app-developers app
Click to expand...
Click to collapse
Seems like we can no longer flash different kernels on cm10. What I suggest you do is try out dirty unicorns with dirty Mac kernel. Or kernel of your choice.
Sent from my Evo 3D CDMA
Astrikz said:
Seems like we can no longer flash different kernels on cm10. What I suggest you do is try out dirty unicorns with dirty Mac kernel. Or kernel of your choice.
Sent from my Evo 3D CDMA
Click to expand...
Click to collapse
If you want your favorite kernel to work on CM bug the developer and get them to update their code. There's no reason to be running legacy code when we're all about having the latest and greatest
私のEVO 4G LTEから送信される。
I went through about 5 versions of HBoot also before ending up on 104 eng... everything seems to be fine!