DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet. I take no responsibility or credit for the information.
Edit: This info primarily relates to the Sprint CDMA Evo3D. I am not familiar with phones flashed to other carriers (Vmobile, Boost, etc) and flashing Sprint Evo3D Ruu's etc may wipe out your carrier settings. If you know whether or not any of this works with other CDMA carriers, please feel free to respond.
------------------------------------------------------------------------------
SDX Version of this thread
I've had the Evo3D for a few months now and must say I really have come to like it.
If you want root, it's a bit quirky, You basically have 3 options:
(See the Hboot 1.5x HTC Unlock Guide in my signature for info & links)
1) HTCdev.com's "Bootloader Unlock":
Basically this leaves the bootloader's (ie, Hboot 1.50 & 1.58) security flag on (S-On) but "unlocks the bootloader" (kinda like the phones Bios) so that you can manually flash everything except for Radios (Baseband) and Boot Logo's (Splash Screen). Kernels & roms can be flashed once a custom recovery is installed, but there are "extra" steps involved because the /boot partition (kernel/zImage) can only be set to write access from the Android OS or by initiating custom recovery from a pc's "Fastboot Command Prompt". There are workarounds, some work better than others. To flash Radio updates, you have to relock the bootloader and flash an OEM Full Stock Ruu (Rom Update Utility), kinda like Samsung's Sw Updater for the Transform. You also have to register your device with HTC and it "may void your warranty".
2) Downgrade Bootloader from Hboot 1.50 to 1.40 (to get S-Off before you update to Hboot 1.58):
This has been around for a few months now & Unknownforce has a new "Ultimate Downgrade Tool" in the last few weeks that does even more. Basically involves corrupting the flashing process of the RUU by removing power in the middle of the flash and "bricking it" (more like mostly bricked). It forces the phone into a special eMMC Download mode that can only be fixed by pushing the older bootloader to the phone from a Linux pc. Good thing is that Closeone has a Linux LiveCD.iso that you copy to a USB Drive or CD and temporarily boot to a custom Linux Interface specifically set up for flashing the bootloader.
Once that's done, you rerun an earlier RUU (compatible with Hboot 1.40) to get the phone working fully, then root via "Revolutionary's site" (another fastboot/adb rooting tool) to get S-Off (Full root), load a recovery, update the radio, then you can flash roms & kernels like normal.
UPDATE: 2 Reports of this working with Hboot 1.58/2.89 FW by "Bricking it Twice"
3) Juopunutbear's S-OFF Wire Trick (Will reset the "Unlocked" status to "Locked" when a stock Hboot is flashed):
There is a similar third option now to brick (short out pins with a wire) & replace the bootloader on 1.50 with s-off but I haven't tried it. (Must HTC Unlock first & have a rooted "Stockish" rom installed).
Note: Jbear now works on the new OTA with Hboot 1.58.
dmdelgado said:
I wanted to share with everyone else suffering from HBoot 1.5 that if you have been using Chads ICS Firmware fix because of constant bootloops you dont need to downgrade your HBoot to 1.4. I know every time i would flash the firmware fix it would break many bugs that had already been fixed, I had to flash it to avoid getting constant boot-loops. But Juopunutbear's Wire trick to get S-Off was a miracle fix, and after it turns S-Off it asks if you would like to install a custom Juopunutbear Hboot. After this is done you are officially on HBoot 1.5 S-Off! And can flash any ICSense ROMS successfully without having bootloops! I really hope this helps someone enjoy their ROMs that much MORE because i know it feels good TO FINALLY BE FREED FROM THE CURSE OF S-ON!
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
HBoot & S-Off Background Info:
PLEASE ASSIST: If you have any comments/experience/verification of flashing different roms/kernels with the different Hboots please reply/post so we can get some certainty on the results below. Big thanks to the Mikeyxda, Ramjet, other MeanRom users, and everyone that has put out the firmware & Hboot updates.
mpgrimm2 said:
Here is a list of Hboot differences and compatibilities gathered from various posts.
If you are S-Off and want to change your Hboot/Bootloader, see the next post for a How-To courtesy of xhausx and a download links courtesy of RamJet73. (Remember to thank them both!)
Hboots: ____________________ Differences:
1.04.2000 (Eng Hboot) = Extended functions ................. Appear to be incompatible with newer 2.89 based kernels
1.30 (Stock Hboot with 1.07.651.1 Gb) .................... Appear to be incompatible with newer 2.89 based kernels
1.40 (Stock Hboot with 1.13.651.7 Gb) ................... Appear to be incompatible with newer 2.89 based kernels
1.40.1100 (incl. w/Revolutionary S-Off) ........................... Appear to be incompatible with newer 2.89 based kernels
1.50 (Stock Hboot with 2.08.651.3 Gb) ................... Appear to be incompatible with newer 2.89 based kernels (VM ICS Leak Kernel will boot)
1.57 (Stk Hboot w/ 1.13.652.1 VM ICS Leak) ...... May be compatible with other ICS Leak kernels & newer 2.89 based kernels. (some reports)
................................................................................edit: Nandroid of GB roms will boot, but Clean GB Installs bootloop.
1.50.5050 (incl. w/Jbear for GB S-Off) ........................... May be compatible with newer 2.89 based kernels & prior fw/kernels (some reports)
1.57.5757 (incl. w/Jbear for ICS S-Off) .......................... May be compatible with newer 2.89 based kernels & prior fw/kernels (some reports)
1.58 (Stock Hboot with 2.89.651.2 ICS) ............. Compatible with newer 2.89 based kernels (& Vm ICS Leak), not GB based (some reports)
.............................................................................edit: Some boot issues with AOSP/AOKP roms & kernels reported (ie CM9)
1.58.5858 (incl. w/Jbear for Sprint ICS S-Off) ............... Compatible with newer 2.89 based kernels (& Vm ICS Leak), not GB based (some reports)
.............................................................................edit: Some boot issues with AOSP/AOKP roms & kernels reported (ie CM9)
Hboot Note: Stock Hboots Do Not Support All Fastboot Commands (see below)
Kernel Note:
.......... VM ICS Leak Kernel: 3.0.16-g4211684
....... Sprint 2.89 ICS Kernel: 3.0.16-g294f767
Madmaxx & Ramjet73 have identified why kernels may not flash correctly AFTER the Sprint 2.89 Base kernel has been installed. See Madmaxx's explanation further down.
Click to expand...
Click to collapse
Major Thanks to Unknownforce for providing the following explanation!
Unknownforce said:
First, keep in mind, that there are technically two S-OFF's, the hboot and the radio. This is somewhat misleading. When you're phone displays S-OFF on the hboot screen, this is actually the Radio S-OFF, not hboot S-OFF. Gaining hboot S-OFF is actually just as simple as flashing a new modified hboot. (which is why there are revo hboot and now jbear hboot, they have been modified to now have hboot S-OFF)
hboot S-OFF is almost the same as unlocking your bootloader via HTC's method. Just that HTC's method doesn't get you S-OFF and is more limited than revo/jbear S-OFF.
So a few of the the differences here are:
1.) ENG Hboot is S-OFF and offers more fastboot commands and a few more unlocked features. This is an advanced hboot that you can do serious damage to the partitions in your phone if you don't know what you're doing. It's kind of like an all access pass.
2.) The stock hboots are S-ON, they don't allow very many of the fastboot commands. These are limited to very basic fastboot commands.
3.) revo/jbear are S-OFF, they allow for many of the "standard" fastboot commands, like flashing to partitions and whatnot, but not nearly as "feature packed" as the eng hboot, these are typically enough for normal users.
As to it providing any benefit to using a newer version of hboot, the only one that provides more features is the eng hboot for more fastboot access. What this means is that there's no major feature/performance difference between 1.30 and 1.57 aside from some appearance and some security adjustments (to allow HTC Unlock and also attempt to counter the S-OFF/exploits)
As I understand it, the differences between radio S-OFF and hboot S-OFF are basically as follows:
Radio S-OFF has signature verification off, what this means is that you can flash any PG86IMG.zip and it doesn't have to be signed by HTC. This will allow it to flash just about anything from there. This is why you can revert to a lower hboot without having to do anything special when you accidentally (or purposefully) flash a new hboot over your revo or any other hboot. Radio S-OFF also doesn't check the signature of most of the current partitions (so you don't get "security warning")
hboot S-OFF allows many more of the fastboot commands to be accepted and opens up the ability to flash some of the restricted partitions from it as well.
Hope this helps clear up some confusion.
Click to expand...
Click to collapse
To drive home these differences between Radio S-OFF & Hboot S-OFF, here's Ramjet73's post:
ramjet73 said:
I finally figured out what one of the main differences is between the custom bootloaders (Engineering (ENG), JuopunutBear and Revolutionary) and the stock boot loaders (1.40,1.50,1.57,1.58).
I was trying to boot a new version of TWRP recovery with the 1.58 bootloader installed using the "fastboot boot recovery.img" command from my PC and I kept getting "remote: not allowed" so I tried flashing it using "fastboot flash recovery recovery.img" and still got the same error. I then tried the JuopunutBear 1.58.5858 bootloader for the Sprint ICS build and the same commands worked!
After reading Unknownforce's description of the bootloaders again and recalling what the JBear developers said about their custom versions, it all makes sense. The ENG and custom bootloaders are "hboot S-OFF". Those fastboot commands (and some others) are restricted by the stock hboots unless you HTC unlock, even if you are radio S-OFF. However, the custom bootloaders are modified to allow those commands even when the bootloader status is ***LOCKED***, which mine has been since using the wire trick to gain radio S-OFF.
I think I'll just stick with the jbear 1.58.5858 or ENG bootloaders for now, since it's nice to be able to use those fastboot commands as an alternative to flashing PG86IMG.zip files from the bootloader.
ramjet73
Click to expand...
Click to collapse
Major thanks to Madmaxx and Ramjet73 for figuring the 2.89 Kernel to Custom Kernel Flash Issue out!
madmaxx82 said:
We've found the problem.
And it has absolutely nothing to do with any recovery.
In fact it is completely impossible to work in its unmodified form:
The problem is the boot.img that is flashed before: The 2.89 boot.img has its header at a different offset that wasn't common in earlier days.
That way utilities that are used for changing kernels in your current boot.img (in that case the 2.89 boot.img) will fail if they are not the latest version (unpackbootimg got updated by Koush not long ago).
However, the flashable zip used to install doesn't use unpackbootimg/mkbootimg, but something different: "abootimg" and this one wasn't made compatible yet officially (at least not where the source of the source comes from).
An unofficial, hidden, very dirty, modified abootimg does work.
Long story short: 2.89 was the bad boy
Ramjet73 and mpgrimm2 can tell you more about that.
Click to expand...
Click to collapse
If you flashed the Sprint 2.89 kernel and need to go back to the VM ICS kernel so u can flash a third party kernel afterwards, Ramjet73 put together a zip for you...
VM ICS Leak Kernel: 3.0.16-g4211684
Bootloader Flashing (CDMA) 8-9-12
Special thanks to xhausx for this background on Flashing the Hboots independently from his Eng Hboot thread (Req's S-OFF).
xHausx said:
Now that S-OFF is available we can use the eng bootloader to get extra fastboot commands.
If you set S-ON for whatever reason you must flash a SHIP (Stock) bootloader first or you will brick your phone.
If you aren't sure if you need this or not odds are you probably don't, it can be extremely useful but it assumes you know what you are doing so it is much easier to brick your phone with it.
To flash either rename to PG86IMG, place on your sd card and then reboot to the bootloader; or you can use 'fastboot oem rebootRUU' followed by 'fastboot flash zip PG86IMG_eng-hboot.zip'. A list of the available commands can be found here.
hBoot 1.04.2000, mirror - MD5: 3348C361FED927DABB853E49744BD7F2
If you would like to go back to the SHIP one you can download it here. The process to flash it is the same except over USB you can do it straight from fastboot without RUU mode.
PG86IMG_1.40-hboot - MD5: 1B994699EA226390B47282BCB54088DD
Thank you to the AlphaRev & Unrevoked teams for getting us all S-OFF! I also want to say thank you to TeamWin for making the wait bearable by getting us root and to everyone who has spent time ripping this phone apart.
Also thanks go out to SolsticeZero for being a guinea pig and making sure it flashed correctly
Click to expand...
Click to collapse
NOTE: All Available Bootloaders -> Ramjet's Pick Your Bootloader Post
So i took the OTA and i'm s-on with the new hboot. If i unlock via htc dev will i be able to install any ICS rom in the development section? Before I took the OTA i was on hboot 1.50 s-on and I couldn't successfully run ANY ICS roms.
KL45SiiK said:
So i took the OTA and i'm s-on with the new hboot. If i unlock via htc dev will i be able to install any ICS rom in the development section? Before I took the OTA i was on hboot 1.50 s-on and I couldn't successfully run ANY ICS roms.
Click to expand...
Click to collapse
I'm not 100% sure yet. It may depend on what kernel is included in the particular rom ie, 2.17 Based kernel (GB) won't work, but Vm ICS Leak kernel & Sprint 2.89 based kernels (& newer) should work. MeanRom ICS v2.6 works with the new fw, kernel & hboot 1.58.
On a sidenote, here is some Hboot testing courtesy of RamJet73 from the MeanRom ICS thread:
ramjet73 said:
I tested some additional bootloaders and here's what I found:
1.50 (2.17.651.5)
- boots and flashes GB ROM's
- boots VM leak but not 2.89 kernel
1.50.5050 (Jbear GB)
- same as 1.50
1.57 (VM Leak)
- boots GB ROM's restored from nandroid
- flash of GB ROM results in boot loop
- flashes and boots ICS ROM's and kernels, including 2.89
1.57.5757 (Jbear ICS)
- same as 1.57
1.57, 1.57.5757 and 1.58 display the OpenADSP release.
ramjet73
Click to expand...
Click to collapse
ramjet73 said:
Based on the results of my earlier testing, it appears that you can restore a nandroid of a GB ROM flashed with 2.17 firmware and boot it using hboot 1.58 and the rest of the new firmware, but fresh installs of 2.17 based GB ROM's result in boot loops.
I just tested reverting back to the ENG 1.04 bootloader and flashed MeanROM GB 4.3 and it worked. I could flash, boot and run 4.3 using the ENG bootloader with the rest of the new (2.89) firmware installed, but it wouldn't boot if I reinstalled the 1.58 bootloader. I didn't test it, but suspect I would get the same results using the 1.4 and 1.5 bootloaders.
This means that if you you need to flash a GB ROM based on the 2.17 build, a temporary install of one of the older bootloaders should work to flash and run that ROM even with the rest of the new firmware installed. The bootloaders I used for my testing are attached to this post.
A tip for switching bootloaders is to restore or flash a ROM that you know will boot with either bootloader, such as MeanROM ICS with the VM leak kernel, before you flash the new bootloader. If you can't boot the installed ROM after flashing a different bootloader you will have to delete the PG86IMG.zip file in the root of the SD card on another device since there will be no way to boot directly into recovery after the new bootloader is flashed.
ramjet73
Click to expand...
Click to collapse
Sent from my "Up all night, Sleep all day" EVO3D!
Wow awesome thread is awraome. Thank you
Sent from my EVO 3D with ViperROM via XDA premium
Madmaxx & Ramjet73 have identified why kernels may not flash correctly AFTER the Sprint 2.89 Base kernel has been installed. See more here
Pick your bootloader!
I thought it might be a good idea to post my collection of bootloaders so they could all be downloaded from one place. Attached are all the bootloaders I've tested, including the new JuopunutBear bootloader (1.58.5858) that was created for the Sprint OTA.
Note: All attached hboot files have been updated to work with both the Sprint Evo 3D (CID=SPCS_001) and Virgin Mobile Evo V (CID=SPCS_002)
Here are the MD5 checksums for the zip files:
PG86IMG_1.30-hboot: 92d5abf4f778a473b420a53a76f4a228
PG86IMG_1.40-hboot: 3dc952832e485f9d80ea1aee559fe298
PG86IMG_1.50-hboot: 50ead742f1cf2dec21dd39e2c952271b
PG86IMG_1.57-hboot: 6a07091016270452be23b7350cb749bf
PG86IMG_1.58-hboot: 44af7b2a809b901dde390cc7543bdfc6
PG86IMG_ENG_1.04-hboot: e20048034a5143b22e5faaec4686c36f
PG86IMG_JBear_1.50.5050_hboot_GB: a6c48789c16f60dcd484e861513edc61
PG86IMG_JBear_1.57.5757_hboot_VM_ICS: 9bcf8a954d66cd96422c134d10891b4a
PG86IMG_JBear_1.58.5858_hboot_Sprint_ICS: 9d19534761d24fadf2d4263a79ec110d
PG86IMG_Revolutionary_1.40.1100-hboot: d81adbbdc6e16521e8a170de650ab2c9
ramjet73
Thanks for posting here also Ramjet!
ramjet73 said:
I thought it might be a good idea to post my collection of bootloaders so they could all be downloaded from one place. Attached are all the bootloaders I've tested, including the new JuopunutBear bootloader (1.58.5858) that was created for the Sprint OTA.
ramjet73
Click to expand...
Click to collapse
I was looking for the 1.58 hboot for my CDMA Evo 3d so that I can switch back and fourth when I'm flashing different ROMs that call for it. Thanks for this post and for sharing.
I have one question though.
The one I want is the one that just says PG86IMG_1.58_hboot.zip and not the PG86IMG_jb_hboot_Sprint_ICS.zip correct?
I unlocked using revolutionary and not jb so I'm pretty sure I don't need that one but I want to be a 100%.
Thanks for any replies.
Sent from my PG86100 using Tapatalk 2
Lin,
To be honest once you are s-Off u can use whichever one you want.
I will say that the Jbear 1.58 hboot will likely support more fastboot commands & prove to be better than the stock 1.58 hboot, but I haven't tried it out yet. But yes, the Stock hboot 1.58 you indicated will work though. I didn't even know Jbear released it till Ramjet posted it.
Sent from my "Up all night, Sleep all day" EVO3D!
mpgrimm2 said:
Lin,
To be honest once you are s-Off u can use whichever one you want.
I will say that the Jbear 1.58 hboot will likely support more fastboot commands & prove to be better than the stock 1.58 hboot, but I haven't tried it out yet. But yes, the Stock hboot 1.58 you indicated will work though. I didn't even know Jbear released it till Ramjet posted it.
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
Have you heard if the jbear 1.58 works with the new kernel? The only reason I'm looking for just the hboot is so that I don't have to flash the whole all in one to go back and fourth. I would rather not flash the firmware and radios over and over, you know. More of a chance to mess something up that way. I usually don't care about flashing anything but radios I don't like lol.
Sent from my PG86100 using Tapatalk 2
I would think that it does. I'm waiting to see if Ramjet has any feedback. Why not try it out & see? You could also head over to http://unlimited.io 's site for more info.
Edit: just checked the site & that is the Jbear Hboot that is installed/compatible with the new 2.89 base (hboot 1.58) so I'd say your good for the new/custom kernels. Now Whether or not it will be backwards compatible with GB/AOSP/CM9 will require someone to load it and try it out.
Sent from my "Up all night, Sleep all day" EVO3D!
mpgrimm2 said:
I would think that it does. I'm waiting to see if Ramjet has any feedback. Why not try it out & see? You could also head over to http://unlimited.io 's site for more info.
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
Thanks but I think I'll just try out the regular 1.58 hboot unless someone posts something that would give me a good reason to use the jb version. I don't use fastboot often anyway.
One more question. Have you flashed the regular 1.58 in ramjet73's post?
Oh and its cool to see your on sdx. Thats the first android site I was on back when I had the Samsung Moment since they were the only site that had any development for it. I haven't been there in a while till a saw your link to it.
Sent from my PG86100 using Tapatalk 2
I came from a Transform at SDX. And no, I didn't use Ramjet's hboot 1.58 only zip, bit I know he's used the heck out of them flashing back & forth for testing so I know it works. (i did Virus's fw with hboot update).
Sent from my "Up all night, Sleep all day" EVO3D!
mpgrimm2 said:
I came from a Transform at SDX. And no, I didn't use Ramjet's hboot 1.58 only zip, bit I know he's used the heck out of them flashing back & forth for testing so I know it works. (i did Virus's fw with hboot update).
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
Great guide man.. Keep up the good work.
Thanks Grim!
----------------------------------------
Another update from Ramjet73:
ramjet73 said:
Yes, it (Jbear 1.58.5858) works with the 2.89 kernel and the VM leak kernel, but not with the AOSP and GB ROM's. It's the same as the 1.58 bootloader, with the additional write/erase partition commands that are added by the unlimited.io folks when they create a custom version of the bootloader.
As with all the custom bootloaders, people need to make sure they install a stock, signed bootloader if they ever decide to go S-ON via the fastboot writesecureflag command or they will brick their phone.
ramjet73
Click to expand...
Click to collapse
Sent from my "Up all night, Sleep all day" EVO3D!
This might sound crazy but I want to ask before I screw up something.
If your already rooted and running a custom ROM can the bootloader be upgraded without losing root.. so a new ICS ROM can be installed?
Sent from my Galaxy Nexus using Tapatalk 2
kratos313 said:
This might sound crazy but I want to ask before I screw up something.
If your already rooted and running a custom ROM can the bootloader be upgraded without losing root.. so a new ICS ROM can be installed?
Click to expand...
Click to collapse
Only if you are S-Off.
HTC Unlocked/S-ON : You must Relock the bootloader, flash a full RUU (If 2.17 Ruu, then take the 2.89 OTA). Then Unlock again (or get Jbear S-Off), install recovery/Su for Stock Root or flash a Rom.
Excellent informational thread, thanks!
I am currently 1.4 S-OFF and trying to determine if I should upgrade to 1.58 to be able to use 2.89 kernel. Since there appear to be 2.89-based ROMs using the older 2.17 kernel, which is compatible with 1.4, I am debating whether or not to upgrade HBOOT to 1.58.
Any difference on the boot loader itself that would indicate it is better to go to 1.58, since I would remain S-OFF?
If the only benefit I would see as an end-user (not planning on development work on this device) is the ability to use a newer kernel, then, is it worth it to be in the newer kernel?
MeanRom ICS Setup 8-30-12
hyuga said:
If the only benefit I would see as an end-user is the ability to use a newer kernel, then, is it worth it to be in the newer kernel?
Click to expand...
Click to collapse
It really just comes.down to the.kernel/Rom you want. Some newer custom kernels (not 2.89 based) will load on the older hboots with 2.89 fw.
I'm on hboot 1.58, 2.89 fw, S-Off, Meanrom ICS 2.6, Coolexe's LeeTweaks for new ota, oc/uv kernel v3.2.2 (or v3.0.4) at 1.72ghz: 4000 quad/7600 antutu. Running great, no plans to go back to gb. (Went back and added Coolexe's Cam/Sound mods from Ramjets post).
Edit to answer some questions about the kernel:
My typical settings (i'm on v3.2.8 otg now):
CPU Max Clock: 1.728 Ghz
CPU Min Clock: 192Mhz
CPU Max sleep: 384Mhz
Vsync: Off (not available in default MeanRom script)
2d/3d GPU: 266/320Mhz (OC'd. N/a in Meanrom script)
Gov: Lagfree
Sched: Noop
Zram: Enabled (Installed with/by Kernel)
- It works well with Mikeyxda's original post_boot.sh script, but to reduce any issues, it's recommended to rename/delete the script (Plus any files in the init.d folder and use the "DualCore beta " app (like SetCpu but custom built for the kernel):
Edits:
I use EsFileExplorer (or similar) with "root Explorer" & "Mount File System" enabled.
- Go to /system/etc/init.d ( /system/etc/init.qcom.post_boot.sh file also) and delete everything in there (I leave MeanRom's "99Wifi Watcher" and move the rest to sdcard/rename it).
- Wipe cache/dalvik, Flash your custom kernel, reboot. let it sit 5mins or so. Reboot again.
- Load up the DualCore Beta app and use it to adjust any settings higher that weren't part of the kernel flash.
(currently using)
- If you'd rather have a good post_boot script (with additional fixes/extras, ie Facebook pics fix) instead of using the DualCore app (you can keep it installed for "monitoring"), get Southern7's v1.9a file and install it in place of the MeanRom script (the zip will install it for you to the /system/etc/ ).
Then you can use esFileExplorer to edit the "user section" similar to MeanRom's Script.
There may be an issue with the zip installer, so I just copy S7's post_boot.sh out of the zip and paste it over with EsFileExplorer.
I moved/removed/deleted the following /system/init.d/ files that were installed with the kernel since they are controlled by S7's Post_boot:
- 99sweep2wake
- 99vsync
I leave Meanrom's: 99Wifiwatcher (it keeps wifi active when the screen is off and at "night")
Edit:
- That post_boot.sh file is the one & only to remove (no other sh files) from /system/etc.
NOTE: you can simply "disable them" by changing the extensions from ".sh to .bak"
- During the kernel install, I usually enable "zRam" so that script gets added to the /system/init.d/ folder. Everything else can ba left at "Defaults" and tweaked with Southern's post_boot.sh or the DualCore App.
Edit 2:
I have just left MeanRom's files alone and just installed the kernel with Zram enabled & GPU's oc'd. This has worked out fine for me. You can still go into MeanRom's post_boot.sh and adjust the governors/max clock/scheduler, but you wont be able to adjust any other kernel settings w/o the DualCore App and then you risk conflicts b/w the app & Mikey's post_boot.
------------------------------------------
Edit 3 (extras):
Everything above working out for you? Want some extras like Coolexe's 2.89 compatible Leedroid Tweaks, Sony xloud mods, Coolexe's Advanced Beats Control & HDR/Panoramic Camera mods?
mpgrimm2 said:
Thanks again to Ramjet73 for all the testing:
Ramjet's Meanrom Mods post worked out well.
Got beats with my BT headset, volume overall is louder and the Panoramic Camera pix are awesome. Now if ZSL gets added to the 3rd party kernel, that would be cool.
Click to expand...
Click to collapse
Related
This is a modified HBOOT that is designed to be compatible with ICS while retaining its S-OFF capabilities. It is NOT an ENG hboot, but rather a S-OFF hboot. It still has fastboot capabilities.
This is not my work, but I got the permission to release the modified leak (the full ICS leak) from Unlimited.io team (Hyuh).
This has the modified hboot in it, so you do not need to flash an engineering hboot before flashing the leak. It has everything in it. Just flash this as you would with the normal leak such as:
renaming it to PH85IMG.zip and then flashing it through hboot, or flashing this with fastboot under RUU mode, or whatever method works best for you
The only difference with this is that this is fully compatible with the ICS ROM, while the other ENG hboots are not. ENG hboots still will work, but it is said that this hboot is more compatible.
REMINDER: YOU MUST HAVE S-OFF BEFORE FLASHING THE MODIFIED ROM OR BEFORE FLASHING THE MODIFIED HBOOT!!!
Disclaimer: I am not responsible for bricks or malfunctions you may experience. Flashing a new hboot can be dangerous, so heed caution. (Insert standard disclaimer here)
LINK for the -FULL- modified ICS leak:
http://hyuh.net/files/ruby/PH85IMG_juopunutbear.zip
CREDITS: Unlimited.io and hyuh for their awesome work, and Football for releasing this leak!
I also took the liberty of pulling the hboot from the modified ICS leak, for those who need to flash the updated hboot on the ICS ROM, as I previously had an incompatible (but working) ENG hboot on the ICS rom. I just flashed this and it worked.
Again, you must have S-OFF!
Instructions: Download the file and then flash in fastboot with this command
fastboot flash hboot updatedhbootICS.img
Note: I used this method when I had an ENG hboot beforehand, so results may vary.
This updated hboot version is 1.93.2222
Link: Look at file attached
Thanks for the post, but the ENG boot loader DOES work just fine with ICS. Don't want other people to be confused.
If it is working, I'm not sure how it is supposedly incompatible.
Sent from my HTC_Amaze_4G using XDA
Keylogger_0 said:
This is a modified HBOOT that is designed to be compatible with ICS while retaining its S-OFF capabilities.
This is not my work, but I got the permission to release the modified leak (the full ICS leak) from Unlimited.io team (Hyuh).
This has the modified hboot in it, so you do not need to flash an engineering hboot before flashing the leak. It has everything in it. Just flash this as you would with the normal leak such as:
renaming it to PH85IMG.zip and then flashing it through hboot, or flashing this with fastboot under RUU mode, or whatever method works best for you
The only difference with this is that this is fully compatible with the ICS ROM, while the other ENG hboots are not.
REMINDER: YOU MUST HAVE S-OFF BEFORE FLASHING THE MODIFIED ROM OR BEFORE FLASHING THE MODIFIED HBOOT!!!
Disclaimer: I am not responsible for bricks or malfunctions you may experience. Flashing a new hboot can be dangerous, so heed caution. (Insert standard disclaimer here)
LINK for the -FULL- modified ICS leak:
http://hyuh.net/files/ruby/PH85IMG_juopunutbear.zip
CREDITS: Unlimited.io and hyuh for their awesome work, and Football for releasing this leak!
I also took the liberty of pulling the hboot from the modified ICS leak, for those who need to flash the updated hboot on the ICS ROM, as I previously had an incompatible (but working) ENG hboot on the ICS rom. I just flashed this and it worked.
Again, you must have S-OFF!
Instructions: EXTRACT the zip file and then flash in fastboot with this command
fastboot flash hboot updatedhbootICS.img
Note: I used this method when I had an ENG hboot beforehand, so results may vary.
This updated hboot version is 1.93.2222
Link: Look at file attached
Click to expand...
Click to collapse
I'm using the eng hboot with ics right now with no problems........ anyway is the hboot and eng hboot or is it just s-off
Fixed post. It is a regular S-OFF hboot. Hyuh himself said that this hboot update is more compatible with ICS, and that an ENG hboot is NOT necessary.
Keylogger_0 said:
Fixed post. It is a regular S-OFF hboot. Hyuh himself said that this hboot update is more compatible with ICS, and that an ENG hboot is NOT necessary.
Click to expand...
Click to collapse
While an eng hboot is not necessary its more useful then a standard release hboot and its not more compatible its just a bootloader the eng hboot and this hboot are equally compatible with any rom
sportsstar89 said:
While and eng hboot is not necessary its more useful then a standard release hboot and its not more compatible its just a bootloader the eng hboot and this hboot are equally compatible with any rom
Click to expand...
Click to collapse
I'm just rephrasing what hyuh mentioned to me that's all. Nevertheless, it is here.
Keylogger_0 said:
I'm just rephrasing what hyuh mentioned to me that's all. Nevertheless, it is here.
Click to expand...
Click to collapse
Yep just letting you know the facts
Any differences besides "compatability"??
Sent from my HTC_Amaze_4G using xda premium
rbaruch said:
Any differences besides "compatability"??
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Nope its just the same way jupuntobear modified the other stock hboot i would recommend sticking to eng hboot if you got it
rbaruch said:
Any differences besides "compatability"??
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
From what I've seen in the other thread, to flash the NFC part of the ICS update, you need the new HBOOT, and this allows the NFC part to flash correctly
Keylogger_0 said:
From what I've seen in the other thread, to flash the NFC part of the ICS update, you need the new HBOOT, and this allows the NFC part to flash correctly
Click to expand...
Click to collapse
Right, and the Tmous ICS RUU comes with a version of HBoot necessary to flash the updated NFC (and thus why it reboots on its own a few times).
So the point of having a "more compatible" HBoot I don't understand, unless for futureproofing a new version of NFC or something.
Sent from my HTC Amaze 4G using XDA
I flashed it and checked it out. This actually gives you the functions of both ENG and SHIP HBoots. You can SuperCID and run fastboot flash commands. Seems like this might be the better HBoot to flash. If only it didn't say "JuopunutBear" where it should say "Locked"/"Unlocked"
Stupid question... (the best kind!)
Will flashing this hboot wipe my device or my CWM?
I understand flashing the whole freakin leak will, but if flashing this hboot isn't going to change anything other than supposedly be more compatible - why not?
djxspike said:
Stupid question... (the best kind!)
Will flashing this hboot wipe my device or my CWM?
Click to expand...
Click to collapse
I don't see that as a stupid question, alot of people won't know that answer. Aren't we a community, here to help each other?
Sent from my HTC_Amaze_4G using Tapatalk 2
I had troubles with other hboots and this worked perfectly for me. Running ICS on my amaze 4g from mobilicty , thanks for all your help OP!
djxspike said:
Stupid question... (the best kind!)
Will flashing this hboot wipe my device or my CWM?
I understand flashing the whole freakin leak will, but if flashing this hboot isn't going to change anything other than supposedly be more compatible - why not?
Click to expand...
Click to collapse
No it will not wipe your device or your recovery
djxspike said:
Stupid question... (the best kind!)
Will flashing this hboot wipe my device or my CWM?
I understand flashing the whole freakin leak will, but if flashing this hboot isn't going to change anything other than supposedly be more compatible - why not?
Click to expand...
Click to collapse
No, the hboot alone will not wipe anything, I tested it myself.
Sent from my HTC_Amaze_4G using Tapatalk 2 Beta-5
ok ive never just done the hboot so how do we install it ,,,put on sd card and open comand prompt or what,,,,thanks in advance
crose948 said:
ok ive never just done the hboot so how do we install it ,,,put on sd card and open comand prompt or what,,,,thanks in advance
Click to expand...
Click to collapse
Download the file from post 1. Copy to your external sd card root folder and rename to ph85img.zip (do not extract the download). Reboot into bootloader and it will automatically update.
St Veronus said:
Download the file from post 1. Copy to your external sd card root folder and rename to ph85img.zip (do not extract the download). Reboot into bootloader and it will automatically update.
Click to expand...
Click to collapse
ah ezzz ok thank you so much ,,,
I am going to risk being told that I am an idiot here but I have to ask. I have had my 3D for almost a year now and I just can't take not rooting it yet! It is HBoot 1.5 and this the first smart phone I have ever had (the last 8) that I have not been flashing ROMs on. I just gave up that it will be possible but I have seen a bunch of forums on being able to do this.
My questions lie on the fact that I have a Mac and PC but no Linux system. I see the bootable CD options but not sure what is best. Either way it seems like a lot of work for a ROM but I just need to get a ROM on this damn phone! Is there any good videos? Where the hell do I even truly start. Way to many different options. I feel like a NOOB again even though I have flashed hundreds of ROMS and even cooked some back in my WinMob days!
Thanks guys for the help.
This is the General section. Refer to the Questions and Answers section. Just because you weren't rooting doesn't mean you can't post in the correct section.
Sent from my PG86100 using XDA
Evo3d HBoot/S-off Differences/Rooting Background Info 8-5-12
Edit: I will no longer be maintaining this post. Instead I have started a full thread to help track the changes:
http://forum.xda-developers.com/showthread.php?p=29844067#post29844067
I've had the Evo3D for a few months now and must say I really have come to like it.
If you want root, it's a bit quirky, You basically have 3 options:
(See the Hboot 1.50 HTC Unlock Guide in my signature for info & links)
1) HTCdev.com's "Bootloader Unlock":
Basically this leaves the bootloader's (Hboot 1.50) security flag on (S-On) but "unlocks the bootloader" (kinda like the phones Bios) so that you can manually flash everything except for Radios (Baseband) and Boot Logo's (Splash Screen). Kernels & roms can be flashed once a custom recovery is installed, but there are "extra" steps involved because the /boot partition (kernel/zImage) can only be set to write access from the Android OS or by initiating custom recovery from a pc's "Fastboot Command Prompt". There are workarounds, some work better than others. To flash Radio updates, you have to relock the bootloader and flash an OEM Full Stock Ruu (Rom Update Utility), kinda like Samsung's Sw Updater for the Transform. You also have to register your device with HTC and it "may void your warranty".
2) Downgrade Bootloader from Hboot 1.50 to 1.40 (to get S-Off):
This is a recent development by Unknownforce in the last few weeks. Basically involves corrupting the flashing process of the RUU by removing power in the middle of the flash and "bricking it" (more like mostly bricked). It forces the phone into a special eMMC Download mode that can only be fixed by pushing the older bootloader to the phone from a Linux pc. Good thing is that Closeone has a Linux LiveCD.iso that you copy to a USB Drive or CD and temporarily boot to a custom Linux Interface specifically set up for flashing the bootloader.
Once that's done, you rerun an earlier RUU (compatible with Hboot 1.40) to get the phone working fully, then root via "Revolutionary's site" (another fastboot/adb rooting tool) to get S-Off (Full root), load a recovery, update the radio, then you can flash roms & kernels like normal.
My current setup (keep coming back to MeanRom):
Hboot 1.40.1100 (Downgraded)
Firmware: 2.17.651.5 (Base)
Radio: 1.06.00.1216 (from 2.17 base)
Recovery: 4ext Recovery (Fully Compatible with CWM, which was a bit buggy except for v4.0.1.4)
Rom: MeanRom ICS
kernel: atx 1.9.1
Mods: LeeDroid Tweaks CDMA, ADW_Ex Launcher, Several Apps removed with SDX Stock App Remover (posted in SDX Evo3D General section).
3) Edit: Juopunutbear's S-OFF Wire Trick:
There is a similar third option now to brick (short out pins with a wire) & replace the bootloader on 1.50 with s-off but I haven't tried it. (Must HTC Unlock first & have a rooted "Stockish" rom installed)
dmdelgado said:
I wanted to share with everyone else suffering from HBoot 1.5 that if you have been using Chads ICS Firmware fix because of constant bootloops you dont need to downgrade your HBoot to 1.4. I know every time i would flash the firmware fix it would break many bugs that had already been fixed, I had to flash it to avoid getting constant boot-loops. But Juopunutbear's Wire trick to get S-Off was a miracle fix, and after it turns S-Off it asks if you would like to install a custom Juopunutbear Hboot. After this is done you are officially on HBoot 1.5 S-Off! And can flash any ICSense ROMS successfully without having bootloops! I really hope this helps someone enjoy their ROMs that much MORE because i know it feels good TO FINALLY BE FREED FROM THE CURSE OF S-ON!
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------
HBoot S-Off Background Info:
mpgrimm2 said:
To be honest I have not considered anything about the bootloader since downgrading and getting s-Off. I will point out that us "downgraders" don't have hboot 1.40 but "Revolutionary Hboot 1.40.1100".
My understanding is that it has more functions than stock hboot 1.40/1.50 but less functions than the Engineering Hboot. Kinda like your Jbear Hboot 1.50.5050, but I could be wrong. I'm sure one of the devs like Mike, Chad, Joeykrim, xhausx, freeza, Unknownforce, Closeone, etc would know.
Hboots:____________________Differences:
1.04.xxxx ? (Eng Hboot) = Extended functions .... Appear to be incompatible with newer 2.89 based kernels
1.30 (Stock Hboot with 1.07.651.1 Gb) .......... Appear to be incompatible with newer 2.89 based kernels
1.40 (Stock Hboot with 1.13.651.7 Gb) ......... Appear to be incompatible with newer 2.89 based kernels
1.40.1100 (incl. w/Revolutionary S-Off) ................. Appear to be incompatible with newer 2.89 based kernels
1.50 (Stock Hboot with 2.17.651.5 Gb) ........ 2.89 based kernels status unknown
1.50.5050 (incl. w/Jbear for GB S-Off) .................. May be compatible with newer 2.89 based kernels & prior fw/kernels (some reports)
1.57.5757 (incl. w/Jbear for ICS S-Off) ................. May be compatible with newer 2.89 based kernels & prior fw/kernels (some reports)
1.58 (Stock Hboot with 2.89.651.2 ICS) ............. Compatible with newer 2.89 based kernels (& Vm ICS Leak), not GB based (some reports)
...............................................................................edit: Some boot issues with AOSP/AOKP roms & kernels reported (ie CM9)
Click to expand...
Click to collapse
Unknownforce said:
First, keep in mind, that there are technically two S-OFF's, the hboot and the radio. This is somewhat misleading. When you're phone displays S-OFF on the hboot screen, this is actually the Radio S-OFF, not hboot S-OFF. Gaining hboot S-OFF is actually just as simple as flashing a new modified hboot. (which is why there are revo hboot and now jbear hboot, they have been modified to now have hboot S-OFF)
hboot S-OFF is almost the same as unlocking your bootloader via HTC's method. Just that HTC's method doesn't get you S-OFF and is more limited than revo/jbear S-OFF.
So a few of the the differences here are:
1.) ENG Hboot is S-OFF and offers more fastboot commands and a few more unlocked features. This is an advanced hboot that you can do serious damage to the partitions in your phone if you don't know what you're doing. It's kind of like an all access pass.
2.) The stock hboots are S-ON, they don't allow very many of the fastboot commands. These are limited to very basic fastboot commands.
3.) revo/jbear are S-OFF, they allow for many of the "standard" fastboot commands, like flashing to partitions and whatnot, but not nearly as "feature packed" as the eng hboot, these are typically enough for normal users.
As to it providing any benefit to using a newer version of hboot, the only one that provides more features is the eng hboot for more fastboot access. What this means is that there's no major feature/performance difference between 1.30 and 1.57 aside from some appearance and some security adjustments (to allow HTC Unlock and also attempt to counter the S-OFF/exploits)
As I understand it, the differences between radio S-OFF and hboot S-OFF are basically as follows:
Radio S-OFF has signature verification off, what this means is that you can flash any PG86IMG.zip and it doesn't have to be signed by HTC. This will allow it to flash just about anything from there. This is why you can revert to a lower hboot without having to do anything special when you accidentally (or purposefully) flash a new hboot over your revo or any other hboot. Radio S-OFF also doesn't check the signature of most of the current partitions (so you don't get "security warning")
hboot S-OFF allows many more of the fastboot commands to be accepted and opens up the ability to flash some of the restricted partitions from it as well.
Hope this helps clear up some confusion.
Click to expand...
Click to collapse
fergdogg23 said:
I am going to risk being told that I am an idiot here but I have to ask. I have had my 3D for almost a year now and I just can't take not rooting it yet! It is HBoot 1.5 and this the first smart phone I have ever had (the last 8) that I have not been flashing ROMs on. I just gave up that it will be possible but I have seen a bunch of forums on being able to do this.
My questions lie on the fact that I have a Mac and PC but no Linux system. I see the bootable CD options but not sure what is best. Either way it seems like a lot of work for a ROM but I just need to get a ROM on this damn phone! Is there any good videos? Where the hell do I even truly start. Way to many different options. I feel like a NOOB again even though I have flashed hundreds of ROMS and even cooked some back in my WinMob days!
Thanks guys for the help.
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=1585846
mnomaanw said:
Try this http://forum.xda-developers.com/showthread.php?t=1585846
Click to expand...
Click to collapse
I wouldnt try this.
I would first try to downgrade hboot or just unlock your hboot 1.50 and use 4ext to flash roms and flash GUI to flash kernels..
I ended up bricking my evo by using the Juopunutbear S-OFF wire trick.
fergdogg23 said:
I am going to risk being told that I am an idiot here but I have to ask. I have had my 3D for almost a year now and I just can't take not rooting it yet! It is HBoot 1.5 and this the first smart phone I have ever had (the last 8) that I have not been flashing ROMs on. I just gave up that it will be possible but I have seen a bunch of forums on being able to do this.
My questions lie on the fact that I have a Mac and PC but no Linux system. I see the bootable CD options but not sure what is best. Either way it seems like a lot of work for a ROM but I just need to get a ROM on this damn phone! Is there any good videos? Where the hell do I even truly start. Way to many different options. I feel like a NOOB again even though I have flashed hundreds of ROMS and even cooked some back in my WinMob days!
Thanks guys for the help.
Click to expand...
Click to collapse
I know exactly how you feel. I used to flash my HTC Wing all the time with Windows Mobile. Even tried my hand at cooking some roms. Coming over to Android many years later -- yeah makes you feel like a noob again.
Its not that hard really. You are already familiar with what is involved with flashing. All you have to do is take it one step at a time. Just like you did years ago with Windows Mobile. Lots of tutorials walk you right through it. After you do it, you'll look back and see how easy it really was.
You'll need to unlock your bootloader and root the phone. Once you've done that you can flash almost any rom on here. I would not go S-Off just yet. I have read that downgrading your H-Boot slows the phone way down. There really is no good way to do it with 1.5 yet. There may not ever be as Sprint stopped selling the Evo 3D and lots of people are moving on to other phones.
The night I did mine, I started at 7:00 pm and finally figured it all out and got it done it was 4:30 am.
Just have to do alot of reading. No way around that.
How does soff slow the phone?
Sent from my SPH-D710 using Tapatalk 2
patrao_n said:
How does soff slow the phone?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Just read on here, its not S-Off that slows down the phone, its the downgrade of H-Boot.
Here is the link to what I read:
http://forum.xda-developers.com/showthread.php?t=1661709
Here is what the guy says:
frexe said:
I recently downgraded to 1.4 hboot with revolutionary s off. I then updated with Freezas AIO. And running meanrom ics 1.0 now.
The problem is that my 3g speed is at slug speeds. Ping is up at 900ish download and upload is below 100.
Before I was on hboot 1.5 2.17.651.5_Radio_1.06.00.1216 and had decent speeds.
Just wondering if someone can shed some light to this problem. Or maybe I have to go back to 1.5hboot and live without a true root.
My Phone is flashed to boost.
Click to expand...
Click to collapse
iTzLOLtrain said:
I wouldnt try this.
I would first try to downgrade hboot or just unlock your hboot 1.50 and use 4ext to flash roms and flash GUI to flash kernels..
I ended up bricking my evo by using the Juopunutbear S-OFF wire trick.
Click to expand...
Click to collapse
This^
Unlock and try 4ext first it will allow you to flash roms and kernels without the need to downgrade. I downgraded to hboot 1.4 because I was getting boot loops but I read that a lot of unlocked hboot 1.5 S-On people are fine so try first before going through what can be a tricky and somewhat risky process to get S-Off.
I have experienced no slowdown from downgrading and I can't see how that would have an effect but I'll let someone more knowledgeable chime in if that is a factor or not.
I haven't seen any speed slow downs with Hboot 1.50 downgraded to 1.40 either. I have seen slow downs when sprint was working on tower upgrades that went away after a week or two (drove me nuts). I would point out that the person that reported downgrade "related" slow downs had flashed the phone to Boost mobile, so there's another factor to consider. Edit: Reading thru the rest of that thread proves it wasn't related to Hboot/S-off.
I'm a bit leary on the Juno method, but I've seen references to people shorting out the pin before in lieu of a Jtag setup, so it's pretty much as sound/risky as Unknownforce's Downgrade method. Although, the hboot downgrade has a huge number of successful attempts and the handful of permabricks where because someone got in a hurry and skipped a step/didn't pay attention to what they were doing.
mpgrimm2 said:
I'm a bit leary on the Juno method, but I've seen references to people shorting out the pin before in lieu of a Jtag setup, so it's pretty much as sound/risky as Unknownforce's Downgrade method. Although, the hboot downgrade has a huge number of successful attempts and the handful of permabricks where because someone got in a hurry and skipped a step/didn't pay attention to what they were doing.
Click to expand...
Click to collapse
Agreed.
I'll admit that the JuopunutBear (wire trick) method may look a little more risky than the HBoot 1.4 downgrade process, but I've done two Evo 3D's using a paperclip wrapped in scotch tape (not the preferred equipment) and haven't had a problem with either phone. Several of the "bricked" users have reported a USB status in Windows of "QHSUSB_DLOAD" in the HTC Unbricking Project thread and I added this post from the HTC Amaze forum to the thread which claims that status is not a real brick (if it was there wouldn't be any indication the phone was even connected in Windows) and it can be recovered using the ControlBear utility. I got no feedback from the people that were reporting that status, and the OP also indicated that the phones were probably not hard bricked.
I haven't seen any feedback from anyone with a "bricked" phone about contacting the developers via the IRC channel they advertise on their website (#juopunutbear on freenode) or PM'ing them as I suggested in the jb thread. I have only been able to identify a few users that claim to have bricked their phones via the jb method, but they seem to be posting about their negative experience with that process in many different threads.
I don't really care which method people choose to get to S-Off as they all have risks involved and it's up to each person to determine what level of risk they are willing to take. The JuopunutBear method was a lot simpler for me and I'm not convinced the risk is that high if you use the right type of wire (insulated copper wire is recommended) and follow the instructions as documented (which a lot of people don't), but that method is fairly new and I wouldn't blame people that are HBoot 1.5 S-On for waiting a little while longer to see how many more users claim to have bricked their phones with that method.
Most people can get by with HBoot 1.5 S-On using tools like 4EXT SmartFlash and Flash Image GUI, but for those that have problems with the stock ICS kernel or want to get to S-Off for other reasons, at least there are alternatives now.
ramjet73
just stay with 1.5 s-on
ive been on 1.5 for awhile with s on and it hasnt been that big of a deal. My old evo was soff and there were some nice rom switching with cwm but I uaes to use cwm to flash roms on my evo and it worked like a charm but it does not let you flash the kernal, I was having to flash kernal seperatly with flash gui which is a free download but 4xt works fine and dont have to flash kernal seperatly but eitherway is fine as I usually use specific kernals anyway. I found a routin that I am happy with and wont switch until I brick my phone or get a new one lol.
Good luck
i've been wondering if anyone else has been having any issues with mean rom ics, i've flashed it twice, and even done a full wipe and everything. but it seems every time i restart (or the phone powers down) i go through about 6 - 10 crashes before it can run stable enough for me to use it at all. has anyone else had this issue or have this issue and can shed any light on what could be causing it?
Strange. Are you s-on or s-off?
Read, Search, Read again, ... Then Ask with Tapatalk 2
Im s-off via Juopunutbear. My phone came with bootloader 1.50 but I updated for ics using what was posted Here, so I could retain s-off
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
ramjet73 said:
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
Click to expand...
Click to collapse
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
AlexxSeven said:
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
Click to expand...
Click to collapse
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Hboot 1.5 s-on and I'm running meanrom ICS 2.6 .
I did the HTC unlock. Then installed Su zip from this site. Then I installed 4ext and rebooted into recovery...flashed the meanrom zip (it flashed the kernel that comes w the Rom ) and that was it. Now I'm on sw 2.89 build w the 3.0.16 kernel and like I said still s off and hboot 1.5
If anyone knows any where to get a kernel to overclock please let me know
Sent from my PG86100 using xda app-developers app
ramjet73 said:
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Click to expand...
Click to collapse
i actually decided to give it a try after making a nand backup ofc, and still had the same issues :s after re-flashing from my backup though it seems to boot fairly stable now. even between switching roms im not sure exactly why but could it have been an issue with anything that is permanent between any rom?
Here is where I am with my phone.
Shooter XC Ship S-OFF RL
HBOOT-1.40.1100
RADIO-0.97.10.0530
Rooted
clockworkmod
Cool Sense v11
-----------------------------------------
I am hoping that I am not the only one that has NO idea what to do with the HBOOT and what HBOOT I need or should be running.
So here are a few questions I hope other have. I guess things have changed a bit since I was on my EVO 4G?
Seeing that for now I am on a ICS rom, will it hurt to upgrade my HBOOT?
Will I lose anything by upgrading my HBOOT?
Can I run ICS and JB ROMS on the new HBOOT?
What is the HBOOT really? (help me understand it a little)
Can I run ANY recovery with any HBOOT?
HBOOT anf KERNEL's, do they play nice?
---------------------------------------------------------
Here is the deal, I want to jump to a JB rom as soon as one is fully working, and want to try out the new Cool Sense v11 but I think being on the old HBOOT is giving me boot loops, but even if not I want to understand them a little more and know if I should upgrade it.
Thanks for filling me in a bit!
Its not the hboot that gives bootloop. its the firmware. You are S-off so hboot doesnt really matter.
http://d-h.st/Mf1
put in sdcard. reboot to bootloader and accept update.
will wipe data so make a backup.
As for the recovery try 4EXT. best out there for evo 3d
and as for JB try agrabrens Disarmed Toaster. still a few bugs but really smooth
EM|NEM said:
Its not the hboot that gives bootloop. its the firmware. You are S-off so hboot doesnt really matter.
http://d-h.st/Mf1
put in sdcard. reboot to bootloader and accept update.
will wipe data so make a backup.
As for the recovery try 4EXT. best out there for evo 3d
and as for JB try agrabrens Disarmed Toaster. still a few bugs but really smooth
Click to expand...
Click to collapse
Whoa!
That PG86IMG.zip file looks like a complete set of firmware for a GSM phone and the OP clearly has a CDMA phone.
And much testing on the Evo 3D CDMA model has proven that the version of the bootloader installed, not just the rest of the firmware, can cause booting problems. The bootloader is actually part of the firmware and works in conjunction with the other firmware to write and erase partitions, in addition to the other functions it performs.
ramjet73
Sorry, should of said I am cdma (Sprint)
Sent from my PG86100 using xda premium
OP, I was in the same situation as you until yesterday. Now I'm latest hboot and unlocked (still s-off)
I took the advice in Tribulattifather's rom on the last page. Jbear's cdma ics hboot and latest 1.58 yesterday and I'm G2G. No issues whatsoever. Also if you're s-off you can change hboot anytime you likely. PM me if you need more info but its simple even for me who has half a brain
Edit
Here's more
http://forum.xda-developers.com/showthread.php?t=1885108
oops.. sorry my bad :S
should have realized that *facepalm*
I'm sure the hboot does matter but i was just saying that its not really a requirement to have the latest hboot to run JB,kernels or recoveries. I have the revolutionary hboot and havn't had any problems with the latest roms/kernels.
EM|NEM said:
oops.. sorry my bad :S
should have realized that *facepalm*
I'm sure the hboot does matter but i was just saying that its not really a requirement to have the latest hboot to run JB,kernels or recoveries. I have the revolutionary hboot and havn't had any problems with the latest roms/kernels.
Click to expand...
Click to collapse
I guess the GSM and CDMA models are a little different in that respect, since the most recent Sprint ICS 1.58 bootloader has problems booting GB and AOSP ROM's on the CDMA model. The older hboots do run those ROM's.
ramjet73
So I should. . .
Use this HBOOT
http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7
PG86IMG_1.58-hboot.zip
This Recovery
http://forum.xda-developers.com/showthread.php?t=1561999
and I will be ok to run most, ICS or JB ROM?
Anymore I am only half sure what is going on, lol in the old days you could just flash away.
And thanks everyone!!!
Really, I am not sure if I have to do it in order or if it matters?
Also, I see 4ext will not let you update firmware or the radio. . . How do I know if I have the ones I should have. . ?
If coolexe's rom is using the new kernel, then the 1.4 hboot is causing the issue. You would need the 1.58 hboot.
1.58 hboot: needed to flash anything with the latest kernel. Can flash any sense based ics rom. Cannot flash AOSP, CM, or GB roms.
1.4 hboot: Can flash any custom rom except ones that use the new kernel.
No recovery can flash hboots or firmware , but since you are s-off, you can flash either hboot at will in the bootloader. You can also update to the latest firmware using freeza's 2.89 zip available in the development thread.
I think that answers all your questions, but if not, please reply.
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
If coolexe's rom is using the new kernel, then the 1.4 hboot is causing the issue. You would need the 1.58 hboot.
1.58 hboot: needed to flash anything with the latest kernel. Can flash any sense based ics rom. Cannot flash AOSP, CM, or GB roms.
1.4 hboot: Can flash any custom rom except ones that use the new kernel.
No recovery can flash hboots or firmware , but since you are s-off, you can flash either hboot at will in the bootloader. You can also update to the latest firmware using freeza's 2.89 zip available in the development thread.
I think that answers all your questions, but if not, please reply.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
That about does it, just one more thing that I am not to clear on. How is the firmware different than a ROM?
chaos67731 said:
That about does it, just one more thing that I am not to clear on. How is the firmware different than a ROM?
Click to expand...
Click to collapse
Technically it could all be considered firmware since it is all flashed to the NAND memory of the phone, and an RUU.exe flashes all of it, but generally people think of the boot, system and data partitions as the "ROM" and more as software than firmware. The system and data partitions are also modified during normal operation which is generally not true of the firmware partitions. The "firmware" consists mostly of the bootloader, radios and low level functions similar to BIOS on a PC, and it gets flashed to different partitions.
ramjet73
ooooook...this'll either get me killed or contented.
here goes.
the first part of this i basically stole from sullivan's post over at mik's.
there was no answer to his question...
there are too many guides, tutorials and suggested methods that I can't chose the right one to narrow it down...
i'm asking the same manner of question...
<<<<<
EVO 3d
sprint
-Revolutionary-
SHOOTER XC SHIP S-OFF RL
HBOOT 1.40.1100
RADIO-1.06.00.1216
eMMC-boot
Jun 8 2011,17:20:22
hardware 002
running smooth criminal (chose a random sense rom to update pri.prl)
kernel version is 3.0.50-ck1 butteredtoast ics rls 12.2+
Build # is 2.89.651.2 CL409645 release-keys
PRI Version 1.42_003
PRL Version 21090
i used htc unlock and closeone's toolkit.
was using mikvirgin for a while. vm leak without problems. couldn't update pri.prl
changed a few things here and there...then, i started having heat and drain issues. notably from browsing and swype beta.
figured it was time for a clean slate and new rom.
From what I've gathered I need an ics hboot, ie, 1.58 in order to run ics kernels the right way??
What should i do to be current??
start by updating my radio. (where's the latest file?)
should i upgrade hboot? 1.58?
Do I need to relock, ruu, then unlock again? (what method is most recent and where)
i thought i read that i can just change my hboot on its own and then also bootload the latest radio?
ideally, i'd love to be able to run a few aosp jb roms...cm 10...as well as any ics roms without issue.
also, is the deal with ext3 versus ext4 still the same? ext4 can't run sense roms...or, was that only for the evo4g?
>>>>>>>>>>>>>
advice would be considered a thankable and appreciated offense!
many, many thanks, everyone.
i need to head to bed.
clear my brain a bit.
between ramjet's and mpgrimm2's threads...i'm going into overload.
but, thanks. seriously. you guys rock.
--------------------------------------------------------------
what? you think just cause a guy reads comics he can't kick some a$$?
I would relock the bootloader and run the Sprint ICS ruu.exe. This will update you to the latest firmware, radio, hboot, etc, but you'll still be s-off. Then downgrade your hboot to 1.4 or 1.04 and install a custom recovery like 4ext. You should then be ready to install a custom Rom.
coal686 said:
I would relock the bootloader and run the Sprint ICS ruu.exe. This will update you to the latest firmware, radio, hboot, etc, but you'll still be s-off. Then downgrade your hboot to 1.4 or 1.04 and install a custom recovery like 4ext. You should then be ready to install a custom Rom.
Click to expand...
Click to collapse
i'm thinking running the ruu might be the way to go, too.
(if anyone would like to point me in the direction of the latest ruu "how-to" thread...much appreciated)
however, i'm not quite sold on the idea of downgrading hboot back to what i have (or, another 1.4 variation).
as per ramjet's thread on the subject...even the most flexible hboot "eng hboot" has issues with compatibility running 2.89 based kernels.
the ones that run ics and above are the 1.58 hboots and it's variables.
so, anyone have ideas as to what my specs should be to successfully run a cm 10 based rom and kernel successfully?
not to mention that i'd like to continue to swap into a sense based rom every now and again.
that leads me back to the ext3 vs ext4 question.
is ext4 still not a viable ext for sense based roms or was that only for the evo 4g?
thanks again, coal!
cipher77 said:
i'm thinking running the ruu might be the way to go, too.
(if anyone would like to point me in the direction of the latest ruu "how-to" thread...much appreciated)
however, i'm not quite sold on the idea of downgrading hboot back to what i have (or, another 1.4 variation).
as per ramjet's thread on the subject...even the most flexible hboot "eng hboot" has issues with compatibility running 2.89 based kernels.
the ones that run ics and above are the 1.58 hboots and it's variables.
so, anyone have ideas as to what my specs should be to successfully run a cm 10 based rom and kernel successfully?
not to mention that i'd like to continue to swap into a sense based rom every now and again.
that leads me back to the ext3 vs ext4 question.
is ext4 still not a viable ext for sense based roms or was that only for the evo 4g?
thanks again, coal!
Click to expand...
Click to collapse
This post was for a user in a situation similar to yours. It's basically what coal suggested and you can use my guide through Step2, but there is no need to relock the bootloader since you are S-OFF.
If your case, you might want to flash the ENG or JBear 1.50.5050 bootloader after running the RUU.exe since both of those will flash and run GB, ICS and JB ROM's except for a few Sense ROM's that require the stock 1.58 or JBear 1.58.5858 bootloader.
As far as EXT3 versus EXT4 goes, most current Sense and AOSP ROM's support both, but I usually just "format all partitions except SD card" in 4EXT recovery before flashing a ROM and let it default to that (EXT4) or whatever format the dev configured for the ROM. I just checked the nandroids on my SD card and they are all in the EXT4 format.
ramjet73
IMO, you should just update your radio (if you can find the latest PG86IMG.zip) or get the one from virus's thread which contains the latest hboot too. Then to install CM10 ROM downgrade back to eng hboot or 1.4 you should be able to run CM10 ROMs just fine. And if you want sense 3.6 ROM, you can try smoothcriminal ROM after updating your radio. It works with all hboots.
RUU vs OTA vs firmware zip file
mnomaanw said:
IMO, you should just update your radio (if you can find the latest PG86IMG.zip) or get the one from virus's thread which contains the latest hboot too. Then to install CM10 ROM downgrade back to eng hboot or 1.4 you should be able to run CM10 ROMs just fine. And if you want sense 3.6 ROM, you can try smoothcriminal ROM after updating your radio. It works with all hboots.
Click to expand...
Click to collapse
There's some good information about flashing an RUU versus taking an OTA in this thread on the HTC Desire forum, and flashing the firmware zip updates even less than taking the OTA. I've attached screen shots of the contents of virus's firmware zip file versus the RUU rom.zip file from the same build (Sprint ICS 2.89.651.2). As you can see, even discounting the boot, system, and data partitions, there's more that gets updated with the RUU than what's contained in the firmware .zip, which is why I recommend starting with an RUU flash (.exe or .zip) when upgrading to a new build.
ramjet73
ramjet73 said:
There's some good information about flashing an RUU versus taking an OTA in this thread on the HTC Desire forum, and flashing the firmware zip updates even less than taking the OTA. I've attached screen shots of the contents of virus's firmware zip file versus the RUU rom.zip file from the same build (Sprint ICS 2.89.651.2). As you can see, even discounting the boot, system, and data partitions, there's more that gets updated with the RUU than what's contained in the firmware .zip, which is why I recommend starting with an RUU flash (.exe or .zip) when upgrading to a new build.
ramjet73
Click to expand...
Click to collapse
Although mnomaanw makes a great point, I agree with ramjet on this one. My phone recently decided not to let me install ANY CM, GB, or JB based ROMs. The only ones that would successfully boot were Sense 3.6 and 4.0 based ICS ROMs. The rest would show my splash screen and then the phone would bootloop before even the boot ani showed. I tried to flash different radios, hboots, firmware, etc to no avail. Finally, I ran the ruu.exe, downgraded my hboot to 1.4 Revolutionary to try the MIUI ROM everyone is raving about and installed 4ext custom recovery. Everything is running great now.
I can confirm that it does more than just the firmware zip updates as it wiped my custom splash screen I had installed. Going through the hassle of running the ruu is worth it if you want to be sure that everything is completely updated properly.
ramjet73 said:
This post was for a user in a situation similar to yours. It's basically what coal suggested and you can use my guide through Step2, but there is no need to relock the bootloader since you are S-OFF.
If your case, you might want to flash the ENG or JBear 1.50.5050 bootloader after running the RUU.exe since both of those will flash and run GB, ICS and JB ROM's except for a few Sense ROM's that require the stock 1.58 or JBear 1.58.5858 bootloader.
As far as EXT3 versus EXT4 goes, most current Sense and AOSP ROM's support both, but I usually just "format all partitions except SD card" in 4EXT recovery before flashing a ROM and let it default to that (EXT4) or whatever format the dev configured for the ROM. I just checked the nandroids on my SD card and they are all in the EXT4 format.
ramjet73
Click to expand...
Click to collapse
first off...
huge, huge thanks for the responses, guys.
so, yeah...i've actually been using 4ext as my recovery for a while now. i have to say...it's quite good.
however, i always have wondered what the deal was with ext3 vs ext4. clearing that up more definitively than what i've been able to find on my own, as well as my own experiences, is great.
sounds like i'll be running the ruu executable.
just to confirm...already being s-off means that i don't have to relock my bootloader, yeah?
excellent. one less step.
as for the hboot...this seems to be where it gets tricky.
ramjet...you suggested downgrading hboot after the ruu flash to ENG or 1.50.5050.
i'm definitely dumb to NOT take your advice...so, i will. more than likely the 1.50.5050 hboot. seems to be more likely to play well with 2.89 kernels. otherwise, i'd do the ENG hboot.
from your thread, you mention that the only ones that DO run 2.89 based kernels are stock (1.58) and jbear's (1.58.5858).
do you think ENG hboot will be pliable enough at any point to be compatible with them? THAT would be pretty great.
thanks again, gang.
--------------------------------------------------------------
what? you think just cause a guy reads comics he can't kick some a$$?
cipher77 said:
ramjet...you suggested downgrading hboot after the ruu flash to ENG or 1.50.5050.
i'm definitely dumb to NOT take your advice...so, i will. more than likely the 1.50.5050 hboot. seems to be more likely to play well with 2.89 kernels. otherwise, i'd do the ENG hboot.
from your thread, you mention that the only ones that DO run 2.89 based kernels are stock (1.58) and jbear's (1.58.5858).
do you think ENG hboot will be pliable enough at any point to be compatible with them? THAT would be pretty great.
Click to expand...
Click to collapse
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D. Some ROM developers have incorporated the "VM leak" kernel in place of the stock Sprint ICS 2.89(.651.2) kernel just to avoid that requirement. The reason I'm recommending JBear GB (1.50.5050) or the engineering (ENG-1.04) bootloader at this point is that there are far more ROM's that can be flashed and run with those than the 1.58.x versions, and they both support the fastboot commands that would normally require an unlocked bootloader.
ramjet73
ramjet73 said:
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D. Some ROM developers have incorporated the "VM leak" kernel in place of the stock Sprint ICS 2.89(.651.2) kernel just to avoid that requirement. The reason I'm recommending JBear GB (1.50.5050) or the engineering (ENG-1.04) bootloader at this point is that there are far more ROM's that can be flashed and run with those than the 1.58.x versions, and they both support the fastboot commands that would normally require an unlocked bootloader.
ramjet73
Click to expand...
Click to collapse
gotcha.
makes sense that devs would swap out the vm leak just to avoid the hassle.
thanks for the info, btw.
about to flash the ruu from your qaderso zip.
not having to relock before doing the flash is nice.
thanks again for all of your help.
i'll report back with success...or, hang ups.
update...
just wanted to check in.
i went ahead and ran the ruu.exe without any issues.
since i was already s-off and unlocked via htc...i didn't bother relocking.
once the ruu did its thing it changed the hboot to stock and the previous REVOLUTIONARY in the bootloader header disappeared and it just read UNLOCKED.
not sure if this was right...but, i didn't have to unlock again.
i stayed s-off AND unlocked after the ruu.
i re-ran the ruu later in the day since staying s-off and unlocked didn't sit well with me after the intial run. but, the result was the same.
so, i'm all good, i suppose.
any takers?
installed SU, reinstalled 4ext (had been using it successfully for a while now. great recovery.) and busybox.
then, something strange happened.
rather, something i didn't expect.
after changing the hboot to 1.50.5050 via bootloader...
as instructed...i powered down.
extracted the zip from the root so i wouldn't be in a bootloop.
but, it still wouldn't load the stock rom.
is that weird? or, expected?
i actually had to reinstall via recovery another sense rom.
otherwise, i think everything's going well.
waiting to get some time to flash a cm10 rom at this point.
unless someone thinks otherwise!
thanks again...
cipher77 said:
then, something strange happened.
rather, something i didn't expect.
after changing the hboot to 1.50.5050 via bootloader...
as instructed...i powered down.
extracted the zip from the root so i wouldn't be in a bootloop.
but, it still wouldn't load the stock rom.
is that weird? or, expected?
i actually had to reinstall via recovery another sense rom.
otherwise, i think everything's going well.
waiting to get some time to flash a cm10 rom at this point.
unless someone thinks otherwise!
thanks again...
Click to expand...
Click to collapse
That's normal. As a reminder, I'll quote from a post I made earlier in this thread:
ramjet73 said:
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D.
Click to expand...
Click to collapse
The stock 2.89.651.2 ROM is in fact one of the few that currently require the 1.58 bootloader. That's why my guide recommends installing the JBear 1.58.5858 bootloader by default since the RUU installs the stock ICS ROM.
Also, the reason your bootloader shows unlocked is probably because you htcdev unlocked it before doing the hboot 1.4 downgrade for S-OFF. I've never done that method myself, but in discussing it with mpgrimm2, apparently the downgrade method doesn't reset the bootloader status to locked like the JupunutBear (wire trick) method does.
ramjet73
ramjet73 said:
That's normal. As a reminder, I'll quote from a post I made earlier in this thread:
The stock 2.89.651.2 ROM is in fact one of the few that currently require the 1.58 bootloader. That's why my guide recommends installing the JBear 1.58.5858 bootloader by default since the RUU installs the stock ICS ROM.
Also, the reason your bootloader shows unlocked is probably because you htcdev unlocked it before doing the hboot 1.4 downgrade for S-OFF. I've never done that method myself, but in discussing it with mpgrimm2, apparently the downgrade method doesn't reset the bootloader status to locked like the JupunutBear (wire trick) method does.
ramjet73
Click to expand...
Click to collapse
RE: hboot bootloop...doy! consider me FACEPALMED.
maybe, RAM-PALMED!
hell, i probably read over that line twenty times and never really READ it.
so, thanks again.
either way, since not many will stay on stock soft or stock hboot...i suppose it's not really an issue.
change hboot and change rom.
but, it did give me a scare for a minute.
as for the lock versus unlock...your guess is as good as, if not infinitely better, than mine.
everything definitely works, tho.
appreciate you seeing this through and checking in on me, btw.