Related
What does Hero CVT Ship S-ON mean?
And what about
<SEND> Simlock at Hboot Mode?
Nobody knows?
Ganii said:
What does Hero CVT Ship S-ON mean?
And what about
<SEND> Simlock at Hboot Mode?
Click to expand...
Click to collapse
It means that SPL has security turned on so you cannot use it to flash or boot the phone with custom kernel/recovery and other images.
Thanks!
And how can we change?
What are advantages disadvantages?
But to flash custom rom,I boot into recovery-RA-hero-v1.6.2 img.
what the difference?
Eddie1506 said:
It means that SPL has security turned on so you cannot use it to flash or boot the phone with custom kernel/recovery and other images.
Click to expand...
Click to collapse
That isn't correct. You can still boot flash custom recovery images with an S-ON bootloader - we were flashing and booting new recovery images long before an S-OFF SPL was made available!
I believe that the main difference is than an S-OFF SPL allows you to boot/flash unsigned images. You also need an S-OFF SPL to replace an operator boot logo (e.g. the T-Mobile G2 screen when I switch on my G2).
Regards,
Dave
foxmeister said:
That isn't correct. You can still boot flash custom recovery images with an S-ON bootloader - we were flashing and booting new recovery images long before an S-OFF SPL was made available!
Click to expand...
Click to collapse
Ofcourse, you can flash official images signed with HTC official private key.
How could you flash custom recovery and boot images if those custom images weren't signed by HTC, but instead test/self signed?
Eddie1506 said:
Ofcourse, you can flash official images signed with HTC official private key.
How could you flash custom recovery and boot images if those custom images weren't signed by HTC, but instead test/self signed?
Click to expand...
Click to collapse
if that was true you'd need the s-off spl to install ANY custom rom, since they are all signed with testkeys. if you don't believe it start a poll who has custom rom without unlocked spl, i'll betcha it's more than 80% here...
the s-on spl checks for a valid signature, but not for the key itself. the s-off spl doesn't even check the signature.
Eddie1506 said:
Ofcourse, you can flash official images signed with HTC official private key.
How could you flash custom recovery and boot images if those custom images weren't signed by HTC, but instead test/self signed?
Click to expand...
Click to collapse
An S-ON bootloader just required that the images are signed - the actual key itself is irrelevant.
An S-OFF bootloader will flash images that are unsigned.
Note that the S-OFF bootloader only appeared in the wild on the 24th November when Paul @ MoDaCo released one that he'd had for a while (see here), and many of us were flashing custom rom/recovery images long before then.
As Kendon has already posted, I doubt that most people here have ever bothered to flash the S-OFF bootloader, unless they particularly felt the need to replace the operator boot logo.
Regards,
Dave
Ok, then what's the purpose of GoldCard method if we can flash custom images that are properly signed with S-ON bootloader?
P.S. I'm also new to Android platform, so I also am trying to understand. Dont be harsh
what about the simlock part?
foxmeister said:
An S-ON bootloader just required that the images are signed - the actual key itself is irrelevant.
An S-OFF bootloader will flash images that are unsigned.
Note that the S-OFF bootloader only appeared in the wild on the 24th November when Paul @ MoDaCo released one that he'd had for a while (see here), and many of us were flashing custom rom/recovery images long before then.
As Kendon has already posted, I doubt that most people here have ever bothered to flash the S-OFF bootloader, unless they particularly felt the need to replace the operator boot logo.
Regards,
Dave
Click to expand...
Click to collapse
Thanks,now understand a little bit!
And Yes,what about the simlock part and is there a method
how I can check the sim-lock at my HTC Hero?
Eddie1506 said:
Ok, then what's the purpose of GoldCard method if we can flash custom images that are properly signed with S-ON bootloader?
P.S. I'm also new to Android platform, so I also am trying to understand. Dont be harsh
Click to expand...
Click to collapse
The latest version of the SPL (the so called "perfect SPL") specifically disallows remote booting via Fastboot, which effectively prevents you from replacing the recovery image and thus flashing custom images.
The Goldcard method just allows you to downgrade your firmware to an earlier version of the firmware (still with an S-ON SPL) that does not have this restriction. Once you have done this, you can replace your recovery image and flash custom ROMs.
Regards,
Dave
Ganii said:
Thanks,now understand a little bit!
And Yes,what about the simlock part and is there a method
how I can check the sim-lock at my HTC Hero?
Click to expand...
Click to collapse
I don't know what the "SIM-lock as HBoot" specifically means. I wouldn't be at all surprised if it just refers to a lock via SIM pin code.
If you want to check if your Hero is locked to a specific carrier, the easiest solution is just to stick a different carriers SIM in the device and see what happens!
Regards,
Dave
foxmeister said:
The latest version of the SPL (the so called "perfect SPL") specifically disallows remote booting via Fastboot, which effectively prevents you from replacing the recovery image and thus flashing custom images.
The Goldcard method just allows you to downgrade your firmware to an earlier version of the firmware (still with an S-ON SPL) that does not have this restriction. Once you have done this, you can replace your recovery image and flash custom ROMs.
Regards,
Dave
Click to expand...
Click to collapse
Ah, so! Thanks for explanation!
foxmeister said:
I don't know what the "SIM-lock as HBoot" specifically means. I wouldn't be at all surprised if it just refers to a lock via SIM pin code.
If you want to check if your Hero is locked to a specific carrier, the easiest solution is just to stick a different carriers SIM in the device and see what happens!
Regards,
Dave
Click to expand...
Click to collapse
Yes,that`s the easiest method,but I thought there is a method
which show`s me lock codes or similar!
For Windows Mobile devices I found a method,but not for Android!
Thanks anyway!
Sorry for the probably dumb question, but I'm unclear on something.
I know that the new SPL with the OTA Froyo update is perfected. Does that mean that we can't:
A. Flash a custom recovery?
B. Install a custom rom?
C. Apply SAPPIMG if I seriously **** something up?
D. MOST IMPORTANT - nandroid back to where I am now?
I really want to try the official update with new radio but I want to be able to nandroid back to where I am now if I decide for some reason that the update irritates me. Can someone shed some light?
Well the word "perfected" refers to the ability to get unrestricted access to the nand (the storage of the device). With a perfected spl, you have no access to nand + others important instructions. Which means that you cannot flash/erase any of the fun partitions, e.g. spl, radio or recovery. Nor can you flash/erase system, boot ect...
On some non-perfected spl, you had the restriction of the above, but you could load("boot") your images and therefore easily boot a custom recovery and do whatever you wanted.
With perfected spl the option of booting an img is not there.
On some devices, like the magic, we have engineering spl, which ignores the s-off flag. S-on/s-off refers to "security" off/on. With security off you have unrestricted access to the nand.
On some other devices, you have modified spl/hboot, E.g. The Desire device.
Their hboot will simply ignore the s-off flag and give you unrestricted access on the nand + the other fun commands, e.g erase and boot.
Now you aske, Ignore the s-off flag???
Yes, the s-off flag (called "secuflag" ) is actually set in something called Radio NVRAM.
This operate in a lower level then the radio image you flash.
The non + perfected spl reads this flag and behaves accordingly.
The modified hboot + eng hboot simply ignores it.
Going back to the magic device.
As long we can get root on the system, we can flash our own custom recovery. From the custom recovery we can flash the eng spl. And wooooot... we have unrestricted access to nand.
Remember, that the spl, radio and system all are simply partitions on the nand. With root we can flash what ever we want.
The only problem can be, if the 2.2 update has a radio img that do not play nicely with the current eng spl. But will still be able to load a custom recovery wit root access... so the option to flash custom roms will always be there if we can get root on the system.
Last i checked, the android 2.2 is no problem to root using a special exploid.
So don't worry... all is good :0)
Applying a sappimg, is a feature built in all spl. You can ALWAYS flash a sappimg.zip from fastboot if you have same cid nr as the sappimg.zip and the main-version of the phone is the same or lower of what you are trying to flash!
So don't worry :0)
What is goldcard used for?
A good question. Goldcards are used to skip the CID check. E.g. my nordic magic with cid HTC-Y13 can flash the Rogers update with CID ROGER001.
But still, the main-version check still applies :0)
No more knowledge from me today... my hands hurts
mumilover said:
Well the word "perfected" refers to the ability to get unrestricted access to the nand (the storage of the device). With a perfected spl, you have no access to nand + others important instructions. Which means that you cannot flash/erase any of the fun partitions, e.g. spl, radio or recovery. Nor can you flash/erase system, boot ect...
On some non-perfected spl, you had the restriction of the above, but you could load("boot") your images and therefore easily boot a custom recovery and do whatever you wanted.
With perfected spl the option of booting an img is not there.
On some devices, like the magic, we have engineering spl, which ignores the s-off flag. S-on/s-off refers to "security" off/on. With security off you have unrestricted access to the nand.
On some other devices, you have modified spl/hboot, E.g. The Desire device.
Their hboot will simply ignore the s-off flag and give you unrestricted access on the nand + the other fun commands, e.g erase and boot.
Now you aske, Ignore the s-off flag???
Yes, the s-off flag (called "secuflag" ) is actually set in something called Radio NVRAM.
This operate in a lower level then the radio image you flash.
The non + perfected spl reads this flag and behaves accordingly.
The modified hboot + eng hboot simply ignores it.
Going back to the magic device.
As long we can get root on the system, we can flash our own custom recovery. From the custom recovery we can flash the eng spl. And wooooot... we have unrestricted access to nand.
Remember, that the spl, radio and system all are simply partitions on the nand. With root we can flash what ever we want.
The only problem can be, if the 2.2 update has a radio img that do not play nicely with the current eng spl. But will still be able to load a custom recovery wit root access... so the option to flash custom roms will always be there if we can get root on the system.
Last i checked, the android 2.2 is no problem to root using a special exploid.
So don't worry... all is good :0)
Applying a sappimg, is a feature built in all spl. You can ALWAYS flash a sappimg.zip from fastboot if you have same cid nr as the sappimg.zip and the main-version of the phone is the same or lower of what you are trying to flash!
So don't worry :0)
What is goldcard used for?
A good question. Goldcards are used to skip the CID check. E.g. my nordic magic with cid HTC-Y13 can flash the Rogers update with CID ROGER001.
But still, the main-version check still applies :0)
Click to expand...
Click to collapse
Wow, thank you very much for the prompt and extremely detailed reply! That's exactly what I needed to know.
So since it's already been verified that the superoneclick root method works on mt3g with ota 2.2, I'll be fine if I decide I'm not happy.
Cool, that's what I needed to know.
Thanks!
Glad i could clarify :0)
I was wondering if it would be possible to flash a ROM without an S-OFF hboot. The logic is as follows:
The NAND lock is performed by the hboot.
Flashing is performed by the recovery OS.
We can now disable the NAND lock using a kernel module regardless of the hboot.
Could the recovery OS disable the NAND lock and flash a ROM without using an S-OFF hboot?
There are a few reasons against flashing the S-OFF hboot, namely, it's less risky, and easier to revert to factory if a warranty claim needs to be made.
Simple answer NO.
Long answer, you can't flash a custom rom without a custom recovery.
You can't flash a custom recovery without and unlock hboot.
So what ur saying will not work because u will not be able to flash the recovery.
Also no risk if u follow the steps. And reverting is as easy as running pc10img
Also this needs to be move to gen thread
Sent from my T-Mobile G2 using XDA App
Technically, you can probably use dd to reflash the recovery partition instead of hboot, which would allow you to install custom ROMs because the NAND is always unlocked in recovery.
But nobody is going to do that, and there are catches: even then you still can't write to /system without Android without the hack S-OFF is best.
I agree that S-OFF is best, but there might be people who are reluctant to flash an hboot. I figured ROMs can include the kernel module that disables the lock, so they would be able to write to /system.
If it's easy to restore to factory though, I guess there isn't much point in working around the lock all the time like that. S-OFF it is then.
If I missed it, would it be possible to go S-OFF, flash a custom ROM, then go S-ON again?
ok this is a debate i had going on in dz forum. you can flash clockwork recovery via rom manager and prob dd cmd after running the wpthis.ko. you can also perm root it as we know. it has been done in dz forum.
now i agree with you. at this point you should be able to boot into recovery and flash whatever you want and have perm root. however WP will still be on when booted into andriod which can be good and bad depending on how you look at it. (noobs vs pain in ass). this leaves u 2 options. reboot to recovery for any changes, or run the wpthis.ko make changes, reboot.
that being said. heres the prob with having s-on. if you screw up your phone you have less of a chance fixing it. (currently helping someone in this position).
ot anyone know of stock rom in update.zip format?
xile6 said:
You can't flash a custom recovery without and unlock hboot.
Click to expand...
Click to collapse
That's not true......i'm proof
Would need atleast a recovery which uses test keys or simply ignores them.
With the wpthis.ko u could dd other imgs but not enough for a rom as you can not access the system while you are on it.
If you had an S-off hboot u can atleast fastboot the images without the recovery.
Right?
Sent from my T-Mobile G2 using XDA App
This guide tells you how to create a goldcard very easily giving you the ability to flash custom rom and root again. Guide found here: http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/. There is a standalone pc application which allows creating a gold card. Link for app found here: http://android.modaco.com/content/software/308798/pc-application-goldcardtool/.
Note: Does not work for Aria but made here since at the time it wasn't tested.
Thanks ECEXCURSION for the link.
Very interesting, thanks for the guide! I don't need a GoldCard, but it's interesting to read none the less.
Just found this in that thread. Someone made a stand-alone PC application to generate GoldCards: http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
theonew said:
This guide tells you how to create a goldcard very easily giving you the ability to flash custom rom and root again. Guide found here: http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/. Please post your results.
Click to expand...
Click to collapse
Did you actually try this yourself?
Making a gold card won't help you root the Aria.
drumist said:
Making a gold card won't help you root the Aria.
Click to expand...
Click to collapse
Didn't think so but I tried it anyway. Created the gold card but the RUU failed when it tried to write the hboot.
drumist said:
Making a gold card won't help you root the Aria.
Click to expand...
Click to collapse
Oh.. Thought that was the purpose of a goldcard.
My mistake.
What is it that's holding one back from writing to the hboot?
m a r k said:
What is it that's holding one back from writing to the hboot?
Click to expand...
Click to collapse
HTC implemented a new hboot in the latest official 2.2.2 update for the Aria. The new hboot version is 1.0.2.0000. This hboot can not be overwritten by flashing back to the original RUU. The new hboot also fixed the exploit that was used to root the Aria previously.
To date the Aria with the new hboot is un-rootable without hardware.
m a r k said:
What is it that's holding one back from writing to the hboot?
Click to expand...
Click to collapse
HTC devices have a security flag that allows the phone's NAND memory to be written to. This is referred to as the S-ON/S-OFF flag. In order for the NAND memory which houses the HBOOT loader and ROM to be written to, the security flag needs to be OFF. The HBOOT loader can control this flag and when an official HTC signed RUU is used, the HBOOT loader will turn the flag OFF and allow the RUU contents to be written to the NAND memory.
Previous versions of the HBOOT had an exploit in it that allowed rooting and installing a custom recovery, i.e. ClockworkMod and this is how custom ROMs were installed. The current HBOOT version no longer has this exploit available via software. The only way a new HBOOT or Recovery module can be written to the Aria is if the security flag is turned OFF and as of now the only way to do that is to use the XTC Clip device.
tpbklake said:
HTC devices have a security flag that allows the phone's NAND memory to be written to. This is referred to as the S-ON/S-OFF flag. In order for the NAND memory which houses the HBOOT loader and ROM to be written to, the security flag needs to be OFF. The HBOOT loader can control this flag and when an official HTC signed RUU is used, the HBOOT loader will turn the flag OFF and allow the RUU contents to be written to the NAND memory.
Previous versions of the HBOOT had an exploit in it that allowed rooting and installing a custom recovery, i.e. ClockworkMod and this is how custom ROMs were installed. The current HBOOT version no longer has this exploit available via software. The only way a new HBOOT or Recovery module can be written to the Aria is if the security flag is turned OFF and as of now the only way to do that is to use the XTC Clip device.
Click to expand...
Click to collapse
Well done - nice summary of the situation.
I have rooted the updated Aria with my XTC clip. There is a guy that frequents the IRC channel in my thread who has a cell phone store and an XTC clip. I've coached him through a couple of updated Aria roots and he's competent to do the job. He won't charge much, and whoever wants him to do the work will have to pay a modest fee plus return shipping. All he would need is the device - no case, no batter cover, no battery, no sim, no sdcard, no cables - no box. This makes shipping in a small padded envelope via USPS cheap - even insured.
Anyone interested should stop by the IRC channel in my sig.
OP: please update post #1 so a lot of people don't spin their wheels on that process - it's futile.
tpbklake said:
HTC devices have a security flag that allows the phone's NAND memory to be written to. This is referred to as the S-ON/S-OFF flag. In order for the NAND memory which houses the HBOOT loader and ROM to be written to, the security flag needs to be OFF. The HBOOT loader can control this flag and when an official HTC signed RUU is used, the HBOOT loader will turn the flag OFF and allow the RUU contents to be written to the NAND memory.
Previous versions of the HBOOT had an exploit in it that allowed rooting and installing a custom recovery, i.e. ClockworkMod and this is how custom ROMs were installed. The current HBOOT version no longer has this exploit available via software. The only way a new HBOOT or Recovery module can be written to the Aria is if the security flag is turned OFF and as of now the only way to do that is to use the XTC Clip device.
Click to expand...
Click to collapse
After I went through the AlphaRev flashing process, I learned the truth of the previous HBOOT's exploit is that it let you gain temporary NAND unlock.
While it's unlocked and once you got temporary root permission from, for example, the famous RageAgainstTheCage, then you are allowed to put su and SuperUser.apk to your system partition to gain permanent root permission, and flash recovery image to recovery partition as well.
The above is basically how Unrevoked works, imo. As for AlphaRev, it needs your device to be rooted already. It gets temporary NAND unlock first, then flashes and runs a boot image with a NAND module that would add some extra partitions, including HBOOT of course, to the MTD table in order to flash an hacked HBOOT/SPL into your device.
The new 1.x HBOOT has that exploit patched, both Unrevoked and AlphaRev won't work anymore. This thread I found might be the last hope that doesn't involve XTC Clip:
How-To [Root] The myTouch 3GS if you updated to Offical 2.2.1 and lost root
ladios said:
After I went through the AlphaRev flashing process, I learned the truth of the previous HBOOT's exploit is that it let you gain temporary NAND unlock.
While it's unlocked and once you got temporary root permission from, for example, the famous RageAgainstTheCage, then you are allowed to put su and SuperUser.apk to your system partition to gain permanent root permission, and flash recovery image to recovery partition as well.
The above is basically how Unrevoked works, imo. As for AlphaRev, it needs your device to be rooted already. It gets temporary NAND unlock first, then flashes and runs a boot image with a NAND module that would add some extra partitions, including HBOOT of course, to the MTD table in order to flash an hacked HBOOT/SPL into your device.
The new 1.x HBOOT has that exploit patched, both Unrevoked and AlphaRev won't work anymore. This thread I found might be the last hope that doesn't involve XTC Clip:
How-To [Root] The myTouch 3GS if you updated to Offical 2.2.1 and lost root
Click to expand...
Click to collapse
The problem with this solution is it requires an HTC engineering hboot. Here is a thread posted by ATTN1 when the Aria was first released stating that a Liberty eng-hboot doesn't exist:
http://forum.xda-developers.com/showpost.php?p=6910622&postcount=12
tpbklake said:
The problem with this solution is it requires an HTC engineering hboot. Here is a thread posted by ATTN1 when the Aria was first released stating that a Liberty eng-hboot doesn't exist:
http://forum.xda-developers.com/showpost.php?p=6910622&postcount=12
Click to expand...
Click to collapse
It's worth to try. I don't think anyone has tried this on Aria before. Previously we just tried to install an old RUU with gold card hoping the hboot would be downgraded, but this is different.
Step 5-6, hboot installs LIBEIMG.zip. We can extract the rom.zip from RUU and rename it.
Step 7-9, DO NOT REBOOT and get into stock recovery. These must be the key if this happens to work.
Step 10, apply update.zip which is a clockworkmod flashable zip.
Again, it's worth to try, as they got this work on stock 2.2.1 espresso with hboot 1.x. We just need to make an MISC.img to let people try.
ladios said:
It's worth to try. I don't think anyone has tried this on Aria before. Previously we just tried to install an old RUU with gold card hoping the hboot would be downgraded, but this is different.
Step 5-6, hboot installs LIBEIMG.zip. We can extract the rom.zip from RUU and rename it.
Step 7-9, DO NOT REBOOT and get into stock recovery. These must be the key if this happens to work.
Step 10, apply update.zip which is a clockworkmod flashable zip.
Again, it's worth to try, as they got this work on stock 2.2.1 espresso with hboot 1.x. We just need to make an MISC.img to let people try.
Click to expand...
Click to collapse
Sign me up...it's worth a shot.
Sorry for the double post.
I did the following:
Created a gold card.
Obtained update.zip(clockwork).
Extracted rom.zip from the original 2.1 RUU.
Downloaded superoneclick v1.9.1.
Put update.zip and rom.zip on the gold card.
Unmounted the goldcard.
Ran superoneclick and got success on shell root.
Used adb shell and poked around.
My question:
How do we get around not having the engineering recovery package for the Aria?
Im keeping my eye on what happens here.
A$$h4t said:
Sorry for the double post.
I did the following:
Created a gold card.
Obtained update.zip(clockwork).
Extracted rom.zip from the original 2.1 RUU.
Downloaded superoneclick v1.9.1.
Put update.zip and rom.zip on the gold card.
Unmounted the goldcard.
Ran superoneclick and got success on shell root.
Used adb shell and poked around.
My question:
How do we get around not having the engineering recovery package for the Aria?
Click to expand...
Click to collapse
I did a little research about the mtd0.img that was mentioned in the referenced thread and found some posts about creating a mtd0.img (misc.img) for the HTC Desire. There is even a web site that lets you input the appropriate values from your phone and it generates one for you. Don't know if it will work on the Aria, but it may be a place to start. Just Google HTC+Desire mtd0.img and you'll find the various posts. That would be the misc.img that ladios mentioned.
tpbklake said:
I did a little research about the mtd0.img that was mentioned in the referenced thread and found some posts about creating a mtd0.img (misc.img) for the HTC Desire. There is even a web site that lets you input the appropriate values from your phone and it generates one for you. Don't know if it will work on the Aria, but it may be a place to start. Just Google HTC+Desire mtd0.img and you'll find the various posts. That would be the misc.img that ladios mentioned.
Click to expand...
Click to collapse
I'm unclear on this as I thought the CID was much longer than 8 characters yet the image creator only requires 8.
A$$h4t said:
I'm unclear on this as I thought the CID was much longer than 8 characters yet the image creator only requires 8.
Click to expand...
Click to collapse
We can use hex editor to make our own.
Open android-info.txt extracted from the rom.zip you are using
On the line begin with "cidnum: ", there's an 8-character CID number, copy that
On the line begin with "mainver: ", that's the rom version, eg. 1.35.707.5, then 707 would be the rom's region code
Use a hex editor to open mtd0.img extracted from espresso-eng.zip
At 0x0000, overwrite the CID number with the one you found in android-info.txt
At 0x00A0, overwrite the version number with 1.01.XXX.1 where XXX is the region code, eg. 1.01.707.1
Save and use it
To whom who also want to try, please use the files in this post and follow the instructions in How-To [Root] The myTouch 3GS if you updated to Offical 2.2.1 and lost root.
Liberty version of needed files:
(1) Engineering package: liberty-eng.zip is attached.
(4) Stock firmware: Download LIBEIMG_Liberty_hTC_Asia_WWE_1.35.707.5_Radio_47.41.35.10_7.09.35.13_release_138500_signed.zip and rename it to LIBEIMG.zip
(5) ClockworkMod Recovery: Download recovery-clockwork-2.5.0.7-liberty.zip and rename it to update.zip​
Do i need to be on an Eng Bootloader (85.0.0 or whatever) to flash custom ROMS?
I followed the steps to TRUE root and s=off with no issues...but before i start flashing ROMS i wanted to know if i need to install the Engineering bootloader or can i use the normal bootloader....
is there any real benefit of a Engineering bootloader if i dont need to use it?
rubbamade said:
Do i need to be on an Eng Bootloader (85.0.0 or whatever) to flash custom ROMS?
I followed the steps to TRUE root and s=off with no issues...but before i start flashing ROMS i wanted to know if i need to install the Engineering bootloader or can i use the normal bootloader....
is there any real benefit of a Engineering bootloader if i dont need to use it?
Click to expand...
Click to collapse
The eng. Bootloader will save your ass when you get in a jam. You can flash roms with either though.
Its highly recommended to take the extra steps & install the eng. Bootloader : )
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.2
get the engineering bootloader. nuff said.
Did you check your boot loader after rooting? When i rooted with visionary it change my boot loader to eng. one.
Sproket123 said:
Did you check your boot loader after rooting? When i rooted with visionary it change my boot loader to eng. one.
Click to expand...
Click to collapse
The visionary method basically is just flashing the eng hboot which spoofs your radio as s-off.
Sent from my HTC Glacier using XDA App
kimbernator said:
The visionary method basically is just flashing the eng hboot which spoofs your radio as s-off.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
The ROOT.SHzip is what contains the Eng Bootloader. The G-Free Method does not have the EB.
http://www.teamroyal.net/engboot.html
Yes, worth getting engineering bootloader. May save your phone more than once. Instructions at Team Royal's site.
Engineering bootloader does two things:
1. Spoofs S-OFF (as kimbernator put it)
2. Let's you use a tool called fastboot from the Android SDK to flash partitions via USB.
As stated before, root.sh script will flash engineering bootloader, whereas gfree will not, but gfree will actually turn S-OFF in the radio (as well as unlock SIM and CID if you want to) so you can flash ROMs with the stock bootloader. I recommend using gfree and then flashing engineering bootloader manually.
If you're flashing it manually, make sure you run an md5sum on that file before you flash it. If it somehow gets corrupted and you flash it, you could brick your phone (hard brick, unrecoverable).