Database Users

[Q] Kernel Issues and HBOOT

Hey all. I've been unable to flash any kernels except for the stock one and Baconbits. All others but my phone in a perpetual bootloop. I'm using compatible kernels, but it seems any that write a boot.img makes this happen (though I may be wrong on that). Does this have anything to do with the fact I have HBOOT Version .82? I've noticed in most people's screenshots that after they did S-Off, they have .76. Could this be the issue and if so, ho can I downgrade it? Thanks!

Anyone? I've looked around but haven't heard anything with this specific problem.
Sent from my T-Mobile G2 using XDA App

0.76 is the engineering hboot for the G2, with S-OFF. I recommend though that you look at the new "gfree" method of getting S-OFF, which also gives you SIM unlock, SuperCID etc. It's much safer than the eng hboot, though the eng hboot does have some extra functionality.

I don't need the SIM unlock, so I didn't think the gfree method was needed. With that though, I'm on HBOOT .82, and have S-OFF. How can I get it to .76 and S-OFF?

You've got a G2, not a DZ, right ? I'm not sure how you can have the .82 HBOOT and have S-OFF unless you've run gfree ? I might be missing something though.
The gfree method is a much safer way of getting S-OFF, even if you don't need to SIM unlock.

steviewevie said:
You've got a G2, not a DZ, right ? I'm not sure how you can have the .82 HBOOT and have S-OFF unless you've run gfree ? I might be missing something though.
The gfree method is a much safer way of getting S-OFF, even if you don't need to SIM unlock.
Click to expand...
Click to collapse
Yes I have a G2, and I used this http://forum.xda-developers.com/showthread.php?t=833965 to get S-OFF. Am I supposed to have .82? The reason I doubted myself in the first place is that all the screenshots I've seen people have .76 and S-OFF.

phoenx06 said:
Yes I have a G2, and I used this http://forum.xda-developers.com/showthread.php?t=833965 to get S-OFF. Am I supposed to have .82? The reason I doubted myself in the first place is that all the screenshots I've seen people have .76 and S-OFF.
Click to expand...
Click to collapse
I can only assume there's another engineering hboot version, at 0.82 with S-OFF for the G2 ? Sorry, having a DZ myself I'm not so familiar with the exact HBOOT levels on the G2 (since that's one difference from the DZ), but I'm sure someone else can help you with that shortly.
I recommend using gfree though, because with a proper radio S-OFF (not a kind of "fake" S-OFF via HBOOT) it will be a lot easier to recover your phone if somehow you semi-brick it.

steviewevie said:
I can only assume there's another engineering hboot version, at 0.82 with S-OFF for the G2 ? Sorry, having a DZ myself I'm not so familiar with the exact HBOOT levels on the G2 (since that's one difference from the DZ), but I'm sure someone else can help you with that shortly.
I recommend using gfree though, because with a proper radio S-OFF (not a kind of "fake" S-OFF via HBOOT) it will be a lot easier to recover your phone if somehow you semi-brick it.
Click to expand...
Click to collapse
but what if i don't want to sim-unlock it? or do u have an option to opt-out the other unlocks?

If you use the gfree program its all automated for you. However you CAN do it manually by following the directions in the wiki. You would really need to understand what you are doing before you try to skip steps to only turn s off. Is there some reason you really dont want sim unlocked?
Sent from my HTC Vision using XDA App

shortlived said:
If you use the gfree program its all automated for you. However you CAN do it manually by following the directions in the wiki. You would really need to understand what you are doing before you try to skip steps to only turn s off. Is there some reason you really dont want sim unlocked?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
well im rooted now with very detailed help from unlockr.com (w/o SIM unlock).. and i dont care for sim unlock at this time since im not leaving the county or switching carriers anytime soon.. so yea.

J-Hop2o6 said:
well im rooted now with very detailed help from unlockr.com (w/o SIM unlock).. and i dont care for sim unlock at this time since im not leaving the county or switching carriers anytime soon.. so yea.
Click to expand...
Click to collapse
So did you install the engineering hboot to get S-OFF ? Because if not, I highly recommend gfree. It's safe and it'll put your phone into a better state if anything bad does happen to it in the future (e.g. semi-brick), even if you don't want the SIM unlock. It gives you a proper radio S-OFF, the engineering hboot is kind of a fake S-OFF (because it reports S-OFF even though the radio is actually still S-ON).

[WIP]Temp-root Gingerbread EVOs

my evo is rooted already and i havent paid much atention since i got my 3d but was there an HBOOT update in the GB OTA as compared to the last Froyo 3.70?
If there wasnt, anyone should be able to a simple downgrade with a previous RUU and then use any of the working root methods for froyo.
just a thought i had while being bored.

Nope, new bootloader is locked. Cant downgrade.

EVOlvedAndroid said:
Nope, new bootloader is locked. Cant downgrade.
Click to expand...
Click to collapse
so there was a bootloader update?

I really don't even know what to say anymore. I give up. Someone else can do it.

github said:
I really don't even know what to say anymore. I give up. Someone else can do it.
Click to expand...
Click to collapse
+1 thats all i have to say about that

what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
The short version is there is no way around or tricking the bootloader. Pretty much every way imaginable to do this has been tried a bunch of times. We need to find a new exploit to get in. Several devs are working on it and itay happen soon. Seems to be more problematic than any one expected.

firket2000 said:
The short version is there is no way around or tricking the bootloader. Pretty much every way imaginable to do this has been tried a bunch of times. We need to find a new exploit to get in. Several devs are working on it and itay happen soon. Seems to be more problematic than any one expected.
Click to expand...
Click to collapse
yes, but you're not tricking the bootloader. the bootloader remains the same. the sys image is all you are changing and the signatures should remain intact if it is pulled out of a froyo ruu. for that matter even try placing a rooted OTA sys image in it. this would not gain s-off but you could run a shell root and su if it would work.

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
As far as I understand, the new bootloader won't allow for downgrading or flashing anything that doesn't match HTCs signature....so modifying files is out of the question....
Sent from my PC36100 using XDA App

t3project said:
what about replacing the system.img in in the latest pc36img with one from the last froyo? if the bootloader stays intact it should flash the froyo sys image and then you could at lease have temp root
Click to expand...
Click to collapse
Can't do that, it would break HTC's signature and the bootloader would not accept it

I need to save this response in a text file so I can just copy and paste it every day.
You can't modify the contents of a RUU provided by HTC on an S-ON HBOOT. The zip is signed by HTC with their private key. The HBOOT has the public key. Changing just 1 bit on the zip will invalidate the private key and HBOOT won't allow it to flash. This is the reason for wanting S-OFF, so you can flash anything via HBOOT (Recovery, for example) without any signature checks.
You also can't downgrade the HBOOT, as it will give you an error about an earlier version.
All the obvious ideas have been tried, over and over again over the past few months since the new update hit.
If you are still confused, please see this article on Wikipedia about Public Key Cryptography.

Don't forget to add that goldcards and battery pull microsd swaps do not work either.

Well, eff. I switched back to Sprint and back to the EVO today after a (very unpleasant) experience with T-MO and the G2X, only to find out my brand new EVO is already on Gingerbread and can't be rooted, ruling out the best part about owning an EVO... all the awesome custom ROMs. Lovely.

There's been all types of shenanigans occurring trying to root this thing. Including physically planting in the ground. No root from that either. Appreciate where you're coming from and trying to help and all though

jjones1983 said:
Well, eff. I switched back to Sprint and back to the EVO today after a (very unpleasant) experience with T-MO and the G2X, only to find out my brand new EVO is already on Gingerbread and can't be rooted, ruling out the best part about owning an EVO... all the awesome custom ROMs. Lovely.
Click to expand...
Click to collapse
Its being worked on right now so no worries
Sent from my PC36100 using XDA App

I'm rooted but jw is there any news on when that source will be out?
My stupid friends at work wouldn't let me root their froyo and now want to pay me to root their gb I don't even want $ .
Sent from my PC36100 using XDA App

root help

my wifes g2 broke so i got a new one, whats the best way to root now? its up to date on updates?

You can use the guide here.

Or if that's too much of a read: http://wiki.cyanogenmod.com/index.php?title=HTC_Vision
(PS: You're most likely going to be using the G2 Gingerbread unlock since I doubt a new one came with Froyo).

Read through that didn't know if there was different way because of the unlocked bootloader from htc

reeshmd23 said:
Read through that didn't know if there was different way because of the unlocked bootloader from htc
Click to expand...
Click to collapse
Htcdev unlock is pretty worthless compared to "ENG S-OFF"
Sent from my T-Mobile G2

kbeezie said:
Htcdev unlock is pretty worthless compared to "ENG S-OFF"
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Thats true and when u use HTC Unlock u lose garanty.

You may simply follow the xda-wiki. I rooted my desire z (2.3.3) this July 12th (though it was bought in April, 2011). I don't think htc is intelligent enough to unlock the bootloader in the first place. They still want people to come and ask them for unlocking and then loose warranty. And the warning they have written on the page, my God!. I almost fainted reading their warning.
I don't know but if the bootloader is unlocked, you should be able to boot a custom rom directly by putting it in your sd card (I'm a NOOB so Devs please confirm this).
I was going o use their method but then I read about its futility and decided to go the hard way:laugh:

if you use the offical htc unlocked bootloader you loose your warranty right then, you have to go through many annoying steps to change roms, and being you don't have true s-off it you will be locked out of loads of other stuff
just root and give yourself an engineering hboot with true soff and you will be much happier, if you have a warranty and something goes wrong you can always go back to stock and send it in without their knowledge of ever being rooted
Sent from my HTC Vision using xda premium

[Notice] HTC One Bootloader Unlocking Deletes Apps, Blocks Future Updates

HTC One Bootloader Unlocking Deletes Apps, Blocks Future Updates
HTC One owners looking to unlock the device's bootloader in order to install custom versions of Android are being warned that certain pre-installed applications are automatically wiped and future software updates blocked from the device.
According to testing by MoDaCo, unlocking the bootloader on HTC's latest top-end Android smartphone will wipe a special section of the data partition that contains four pre-installed applications: the Calculator, Flashlight, Ringtone Trimmer and Sound Recorder application. When the bootloader is unlocked - a step required for the installation of a third-party or otherwise modified operating system from a 'ROM' file - these applications are permanently wiped from the device and cannot be reinstalled.
Click for Full Article
We seriously need to get some more information about this phone. So far, we don't even know which variants are going to be released to which regions.

This is nothing new. Unless you want to run a stock ROM with root, this is not a problem.

Umm....why WOULDN'T I want to run a stock ROM with root? I'm guessing a huge majority of average users would want this. With manufacturers draconian policies on how we can't use the devices we payed almost $1000 for they are driving us into the ever loving arms of $350 Nexi.

I was going to switch from the Galaxy S3 to HTC One, but i never knew you can't s-off. Might just get the S4 now

fazzxx said:
I was going to switch from the Galaxy S3 to HTC One, but i never knew you can't s-off. Might just get the S4 now
Click to expand...
Click to collapse
HTC dev unlock unlocks the bootloader but you are still s on. With s on you can still flash roms via custom recovery and kernels via fastboot or flashgui app. Only thing is you can't flash radios. I'm positive s off is going to happen sooner than later.
Sent from my EVO using Tapatalk 2

eg1122 said:
HTC dev unlock unlocks the bootloader but you are still s on. With s on you can still flash roms via custom recovery and kernels via fastboot or flashgui app. Only thing is you can't flash radios. I'm positive s off is going to happen sooner than later.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Is that only HTC which need s off or do samsungs require that too?

I might hold of on purchasing the HTC One to see what sort of developer community emerges. How easy rooting becomes. Otherwise I waiting to see what Google/Motorola have to offer.
Don't want to stick with Samsung.

fazzxx said:
Is that only HTC which need s off or do samsungs require that too?
Click to expand...
Click to collapse
It's only HTC

I think carbon app by koush is better option to backup apps. It doesn't require root.
Sent from my HTC One X using Tapatalk 2

kopkiwi said:
I might hold of on purchasing the HTC One to see what sort of developer community emerges. How easy rooting becomes. Otherwise I waiting to see what Google/Motorola have to offer.
Don't want to stick with Samsung.
Click to expand...
Click to collapse
I accidentally thanked you. Anyhow, rooting is easy, already done, actually, but is completely difernt than S-off. S-off is done at the radio level. Evo LTE got s-off achieved within a few months of release (before the one X ) there are always subgroups of geniuses working on S-off. And rarely do they fail to deliver. But root and S-off are a million miles apart. You can't root and install custom recovery using htcstool before S-off.
Sent from my EVO using xda premium
Edit: somehow I combined your post with one asking about S-off. My apologies. Thank tullamore dew

scottspa74 said:
I accidentally thanked you. Anyhow, rooting is easy, already done, actually, but is completely difernt than S-off. S-off is done at the radio level. Evo LTE got s-off achieved within a few months of release (before the one X ) there are always subgroups of geniuses working on S-off. And rarely do they fail to deliver. But root and S-off are a million miles apart. You can't root and install custom recovery using htcstool before S-off.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Can you expand on that further?
I would want to root instantly and install Android HD

Do not S-ON your edited HBOOT!

As there are more and more firmware coming, people will be installing them more and more... Same thing about people that wants to go back to stock. This thread could be considered useless and will make people say "yeah man, I knew it I'm not so stupid" that's OK! You're right.
I just wanted to remember that you shouldn't ever ever ever S-ON your HBOOT if it is edited by someone else! This will immediately brick your device, if you want to check do it. You need first to replace your current HBOOT with a stock one and then you'll be good to go.
@Sneakyghost:
* Before resetting Security to ON (S-ON) you MUST flash a stock/unchanged HBOOT! Your device will brick instantly if you set Security ON and reboot on a modified HBOOT!
Click to expand...
Click to collapse

In all the hboot threads it clearly states this
And it's not locking your bootloader that bricks it, it's s-on that does it
Sent from my HTC One using Tapatalk

superchilpil said:
In all the hboot threads it clearly states this
And it's not locking your bootloader that bricks it, it's s-on that does it
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I thought it was if you: fastboot oem writesecureflag -3 it will check if it's a modified hboot.
Sent from my HTC One using Tapatalk

I knew That simply locking the hboot would have bricked the device
Sent from my HTC One using XDA Premium 4 mobile app

@superchilpil you were right, I've edited the OP now and it should be ok now... :good:

matt95 said:
@superchilpil you were right, I've edited the OP now and it should be ok now... :good:
Click to expand...
Click to collapse
Wow, I think I've read about 20 threads so far about this, and this is the first time I've seen this corrected... Lots of threads always mentioned locking the bootloader as the issue if you don't have stock hboot.
I actually had a few questions about this,
1. Does the hboot version have to match that of the firmware ? ( 1.54 for 2.24.x.x for example ?) or does it simply have to be any stock hboot ?
2. Are there any differences between hboot for various carriers ?
3. I've read multiple times that running an RUU will not allow you to downgrade unless you have superCID, I don't understand this. I thought the RUU wouldn't run if the CID didn't match. From what I had understood previous to reading that is simply that an RUU cannot be used to downgrade the firmware or the hboot version, that can only be done manually with S-off
Thank you for your time and for the clarification!

ieldra said:
Wow, I think I've read about 20 threads so far about this, and this is the first time I've seen this corrected... Lots of threads always mentioned locking the bootloader as the issue if you don't have stock hboot.
I actually had a few questions about this,
1. Does the hboot version have to match that of the firmware ? ( 1.54 for 2.24.x.x for example ?) or does it simply have to be any stock hboot ?
2. Are there any differences between hboot for various carriers ?
3. I've read multiple times that running an RUU will not allow you to downgrade unless you have superCID, I don't understand this. I thought the RUU wouldn't run if the CID didn't match. From what I had understood previous to reading that is simply that an RUU cannot be used to downgrade the firmware or the hboot version, that can only be done manually with S-off
Thank you for your time and for the clarification!
Click to expand...
Click to collapse
1. Matching firmware/hboot is always the best route possible as it can minimize any issues that may arise, so I suggest it.
2.As far as compatibility issues there aren't any, the hardware on all these devices are almost exactly alike so running another hboot is quite possible. Although I suggest keeping to your carriers hboot to minimize issues. Or atleast keep a backup of yours
3.You can downgrade only if you are S-OFF, otherwise you can only upgrade or flash the corresponding firmware you're currently on. SuperCID only allows you to flash RUUs/firmware from other carriers or regions. CID stands for Carrier Identification. So even with supercid you can't downgrade, there are security measures in place to stop you from downgrading you hboot without s-off, it either won't write or you will end up with a brick.
Sent from my HTC One using Tapatalk