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
Related
How do I achieve s-off? Can I revese HTC unlock method? Is there a thread or answer available? I'm not a complete noob at rooting but got excited and didn't read thoroughly before committing to the HTC process. Started sifting through threads and haven't discovered an answer yet... Please help
I've been trying to sift through them as well just out of curiosity. Here is what I have gleaned from all of the threads on this subject:
1) Unless you previously had s-off through revolutionary, the HTC method will not give you or currently allow you to get s-off
2) Although the HTC method does unlock the boot loader, other things are still locked preventing you from flashing a custom recovery.
3) Currently there is no way to root or get super user access once you've applied the HTC method
4) Currently there is no way to undo the HTC method.
Probably not what you wanted to hear but that is my understanding as it is currently. That doesn't mean that a Dev won't figure out how to allow you to do those things in the next few days or weeks. You'll just have to keep checking.
Thank you, maybe ill just "lose" my phone and get it replaced
I would wait a week or so. Someone will probably figure it out.
Try this thread. Apparently this version of CWM recovery will work with the 1.50 hboot.
http://forum.xda-developers.com/showthread.php?t=1225812
I think if you search other threads you'll see that it only works if you have previously had s-off.
evoLMaverick said:
Thank you, maybe ill just "lose" my phone and get it replaced
Click to expand...
Click to collapse
Wow...fraud...people like you are why we pay so damn much for insurance/phones.
Looks like you can install recovery and Roms. Look here: http://forum.xda-developers.com/showthread.php?t=1225974
housry23 said:
Looks like you can install recovery and Roms. Look here: http://forum.xda-developers.com/showthread.php?t=1225974
Click to expand...
Click to collapse
There you go! That didn't take long at all. Now you don't have to "lose" your phone.
thank you
I really appreciate the info... I'll check it out tonight and let you all know how it goes. This is my absolute favorite forum bar none. By the way, I was being facetious when I made the statement about "losing" my phone... laugh every once in a while! I did when I basically noobed my own phone.
How long do you guys think it will be before there is a method as simple as just flashing a honeycomb rom without having to do the method in the development section?
I really want honeycomb but i'm not sure the risk of bricking is worth it. i LOVE my flyer and would be devastated if i bricked it!
Just curious as to what you guys think.
Gumby63 said:
How long do you guys think it will be before there is a method as simple as just flashing a honeycomb rom without having to do the method in the development section?
I really want honeycomb but i'm not sure the risk of bricking is worth it. i LOVE my flyer and would be devastated if i bricked it!
Just curious as to what you guys think.
Click to expand...
Click to collapse
this up to HTC and does have nothing to do with what is going on here. true that the procedure is quiet difficult, but not impossible. if you addicted same me , sure you're not gonna wait till HTC will come with their release. it's up to you which method are you going to choice.....
Gumby63 said:
How long do you guys think it will be before there is a method as simple as just flashing a honeycomb rom without having to do the method in the development section?
Click to expand...
Click to collapse
Whatever method is used, it will still likely require the flashing of the HC HBoot and radio, so your risk of brickage is probably about the same regardless.
Regards,
Dave
Think what trips most people up is the usage of adb. I was having problems with my laptop recognizing my flyer when I was I hboot, so I couldn't get past the 1st step. :/ I only had a short time to mess with before I had to leave on business. My question is, I've flashed radios, kernels and tons on my Incredible and Thunderbolt, without using adb... I'm assuming that the same could be done, if the files were named correctly? (Pimgblah)
Well I would say I'm very familiar with adb, but I was still reluctant. (i went ahead and did it anyway ) and I'm incredibly glad I did. But answering your question, you don't only use adb in the guide. You also use fastboot. So I'm sure there is some difference there or something (i'm no expert) .
Sent from my HTC Flyer P510e using XDA App
its actually quite complete about the guide that flashing HC in development section, i took about 30minutes to complete it include understanding the step after all require item downloaded
Hey Guys,
I already use a Desire HD fully rooted and eng s-off. Now i bought a Flyer 16gb WiFi and after reading a couple of hours here I'm unsure if I should keep the device.
Is it possible to root the device?
Is it possible to install the HTC HC Leak which is made for the 32gb?
Is it possible to get back to stock?
Thanks for your help.
Regards
Daniel
Sent from my Desire HD using XDA App
I'm not really sure why it would be an issue with the German Flyers. HTC just announced that their bootloader unlocking tool officially supports the Flyer (see htcdev.com), so it should be even less of an issue. I have a US 16gb Flyer using the same stock HC 3.2 leak that people are using on 32gb Flyers (via Paul at MoDaCo). Have you found the thread at MoDaCo (sorry, can't post the link)? Someone might have reported running HC on a German Flyer there.
As far as getting back to stock, I hear there are a number of ways to do it. Someone has posted the shipped RUU's in the developer forum; I'm not sure if the German one is there. If you manage to get clockworkmod running, I believe you could just backup and restore.
Hi,
thanks for your reply.
Yes i already know this thread and as i've seen the instructions are definately working on the 32gb 3g but he's not sure if the 16gb will work fine.
And as i read a RUU for the 16gb is not available.
So in the end it's the same thing as on other phones. You have CWM and S-OFF after the procedure and can just install ROMs as you like, right?
Did you do everything like in Paul's thread? Or is there anything to keep in mind when flashing the 16gb?
Regards
Daniel
Dacoco said:
So in the end it's the same thing as on other phones. You have CWM and S-OFF after the procedure and can just install ROMs as you like, right?
Click to expand...
Click to collapse
Yes, this seems to be the case, although I don't claim to know the details behind needing the new boot, radio, and hboot images. From what I understand, it's required for the Honeycomb ROM, and I think Paul has some details about this on his thread. You might want to ask there, or someone here can enlighten us. I'm not sure if this will limit the ROMs you can install, but if you want to install Honeycomb on a 16gb model, I can attest to them working.
Dacoco said:
Did you do everything like in Paul's thread? Or is there anything to keep in mind when flashing the 16gb?
Click to expand...
Click to collapse
I followed Paul's instructions exactly, no special considerations. I'm not sure what it is in the RUU that would limit use for other models, as you would think the partition tables would remain the same and you would simply image your ROM to that. But I have limited experience with this. Again, I can attest to the image files posted on Paul's site to be working for the US 16gb Wifi-only model and maintaining the same partitions as before the update.
But Pauls Guide includes everything right?
So i don't need to S-OFF with this guide
http://forum.xda-developers.com/showthread.php?t=1062184
Correct?
That's correct. Paul's guide includes everything. It leaves out instructions for using Revolutionary and HTC's unlock tool since the links to those websites include the instructions.
If you're S-ON, the step with Revolutionary (Step 7) will make your Flyer S-OFF. I hear some Flyers, particularly those shipped to Europe, were S-OFF from factory, so you wouldn't have to do that part if you're already S-OFF. You can check by just going into bootloader (shut down, reboot by holding volume down and the power button). The first line or something will say S-On or S-Off.
Okay thanks, i will try it next week.
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 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