Hello all.
I rooted my G2 using the gfree method and all went well(I have S-Off). It was much easier then the process for my G1.
Current setup
HBOOT-0.82.0000
RADIO 26.03.02.26_M
Cyanogenmod 6.1.1
So my question is should I bother to update my bootloader? A friend of mine with a similar setup said I should upgrade but what additional functionality would I get? Anyway I hope this does not seem like a stupid question.
The Eng HBoot gives you fastboot capabilities. That's about it. If you don't really use fastboot, then there is no reason to flash it.
Thank you for the reply but Im confused.
When I go into the boot loader it says fastboot and it shows up if I do 'fastboot devices' from the command prompt. I thought that meant I have fastboot capabilities? Or am I misunderstanding something?
If you have the stock bootloader, you don't have privileges like "fastboot flash" capabilities. It will show up with "fastboot device" because you have the phone in fastboot. It's like in adb, doing "adb devices" will show it up, even if you don't have superuser privileges.
Hope that clears things up a bit.
Ok now I understand. Thank you for your patience.
Looking back on the root instruction on the cyanogen site now I see the section referring to replacing the bootloader.
Now I hear alot about flashing the wrong radio and bootloader versions. How do I know for sure the file on the cyanogen site (0.76.2000) is the correct one?
That's the one that I have on my G2
Side note. I was looking at the wiki on XDA and it has the Eng HBoot for the G2 listed as 0.84.2000 and the DZ HBoot as 0.76.2000 that are hyperlinked to download.
Correct me if I'm wrong, but aren't those two supposed to be switched? My G2 has 0.76.2000, which is what I used when I first achieved perma root using the rage method before gfree. This is also listed on the CM wiki. I am by no means an expert, but I thought the two HBoot's were not interchangeable between the two devices.
Anyone care to chime in on this to share some light? I would hate to start a thread for this question of mine to be answered.
Yes I noticed the same thing. XDA has 84.2000 and CM has 76.2000. Relevent links posted below.
http://forum.xda-developers.com/wik...Z.2FG2.2FDHD.29_-_OPTIONAL_and_UNNECESSARY.21
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
tazz, what radio version do you have? Id like to update my radio as well, hopefully it will clear up some issues.
My radio version is the one dumped from the RUU_Vision_Hutch_AUS_1.85.861.3_Radio_12.28h.60.14 0f_26.06.02.27_M_release.
It's found in this thread http://forum.xda-developers.com/showthread.php?t=959488
The instructions to flash with fastboot are there, as well as an update.zip, so you should have no problems there.
Regarding the engineering hboot;
The ONLY known brick was made by scotty2 by playing with hboot commands that are only available in the engineering hboot. In other words, it allows you more freedom to control the device, but at the expense of potentially REALLY f-ing it up if you mess with things that you don't understand.
With a radio s-off phone, you can save the phone from literally anything, even without the engineering hboot. As a matter of safety, the engineering hboot is *not required*. In terms of convenience, it is nice, as long as you don't go playing with things you don't understand.
Tazz. Thank you for the info. but should I upgrade the SPL before that installing that radio?
If you want to upgrade the radio through fastboot then yeah, you need to upgrade the spl first.
Otherwise, you can just update the radio through the update.zip in bootloader the pc10img.zip way, then you can do the spl upgrade.
Its really a personal preference.
Sent from my thumbs
tazz9690 said:
Side note. I was looking at the wiki on XDA and it has the Eng HBoot for the G2 listed as 0.84.2000 and the DZ HBoot as 0.76.2000 that are hyperlinked to download.
Correct me if I'm wrong, but aren't those two supposed to be switched? My G2 has 0.76.2000, which is what I used when I first achieved perma root using the rage method before gfree. This is also listed on the CM wiki. I am by no means an expert, but I thought the two HBoot's were not interchangeable between the two devices.
Anyone care to chime in on this to share some light? I would hate to start a thread for this question of mine to be answered.
Click to expand...
Click to collapse
santaclaws said:
Yes I noticed the same thing. XDA has 84.2000 and CM has 76.2000.
Click to expand...
Click to collapse
You were right I updated the XDA Wiki to reflect the correct info on the ENG. Hboot for the G2 which is 0.76.2000 and the DZ which is 0.84.2000. Good Catch.
joemm said:
You were right I updated the XDA Wiki to reflect the correct info on the ENG. Hboot for the G2 which is 0.76.2000 and the DZ which is 0.84.2000. Good Catch.
Click to expand...
Click to collapse
You're a good man joemm. Thanks for fixing things.
I went ahead and upgraded to the Eng hboot. No Brick. Yay!
tazz. occasionally my phone loses data connectivity. i can still make phone calls but no data. i notice if i kill the radio process internet works after the signal comes back. do you think an update to my radio would help this issue?
Yeah it could help it. I upgraded my radio and I get better data reception now than I did with the older radio version that I had.
I had the same problem, where I would have to reboot the phone to regain data. It still happens once in a blue moon, but not like it did before.
At least I am not the only one having that issue. Its a bit annoying.
The only "solution" I found was to make a simple gscript to kill all radio processes. Its quicker then a reboot. Not sure if killing the radio process has any negative effect but the phone seems fine after.
I just leave the shortcut on the desktop and use it whenever I need it.
dhkr234 said:
Regarding the engineering hboot;
The ONLY known brick was made by scotty2 by playing with hboot commands that are only available in the engineering hboot. In other words, it allows you more freedom to control the device, but at the expense of potentially REALLY f-ing it up if you mess with things that you don't understand.
With a radio s-off phone, you can save the phone from literally anything, even without the engineering hboot. As a matter of safety, the engineering hboot is *not required*. In terms of convenience, it is nice, as long as you don't go playing with things you don't understand.
Click to expand...
Click to collapse
Thanks for the info here, I had been searching this forum for at least 2 days now, looking for information on the eng-hboot and was it needed or not.
Being new to all this, could this eng-hboot vs hboot be on the wiki somewhere? My thoughts are that once I got my phone rooted and backed up I was trying to figure out what the next step was before flashing any ROM. I really don't want to mess up my phone.
From what I gather the main thing with the eng hboot is that it lets you do the fastboot commands.
and apparently it has other stuff that can also brick your phone lol
Related
So it seems as there is still some uncertainty in terms of updating to new hboot. Read some people lost root by doing so and read some were successful possibly due to having unrevoked forever installed. I updated to latest radio, wimax and nv already. Has anybody been able to downgrade the radio? I ask as it seems if downgrading is possible than unrevoked could be installed and then the hboot could be updated without losing root s-off. I appreciate any information and all your help.
Sent from my PC36100 using XDA App
starkillers said:
So it seems as there is still some uncertainty in terms of updating to new hboot. Read some people lost root by doing so and read some were successful possibly due to having unrevoked forever installed. I updated to latest radio, wimax and nv already. Has anybody been able to downgrade the radio? I ask as it seems if downgrading is possible than unrevoked could be installed and then the hboot could be updated without losing root s-off. I appreciate any information and all your help.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Why would you want to upgrade the hboot?
Was reading a few threads that suggest we should. I believe calkulin posted saying that he would update the hboot if it weren't for the fact that he uses fastboot commands during his development. Page 110 of his thread.
xHausx said:
Why would you want to upgrade the hboot?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
From what I've seen the new hBoots are all backward compatible, and as long as you have already ran Unrevoked Forever you *should* keep S-OFF, but the new hBoot has been particularly stubborn when it comes to abiding by the S-OFF. The extended commands on the eng-hBoot may not be very useful to most people but they can be very handy if something goes wrong and you manage to fubar your phone. So as long as you retain S-OFF or a custom recovery you should be ok using the 2.02 hBoot but I would wait awhile to find out more about ver 2.10. Especially if you plan on upgrading your radio.
I have already upgraded radio, wimax and nv and I don't have unrevoked forever installed . My hboot is the original with fastboot commands.
xHausx said:
From what I've seen the new hBoots are all backward compatible, and as long as you have already ran Unrevoked Forever you *should* keep S-OFF, but the new hBoot has been particularly stubborn when it comes to abiding by the S-OFF. The extended commands on the eng-hBoot may not be very useful to most people but they can be very handy if something goes wrong and you manage to fubar your phone. So as long as you retain S-OFF or a custom recovery you should be ok using the 2.02 hBoot but I would wait awhile to find out more about ver 2.10. Especially if you plan on upgrading your radio.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I have 0.79, and as long as everything else is working, I don't see why it should be necessary to upgrade. And now that I've already updated all my radio's with the latest combo pack, I'm apprehensive about doing it anyway.
DarkAudit said:
I have 0.79, and as long as everything else is working, I don't see why it should be necessary to upgrade. And now that I've already updated all my radio's with the latest combo pack, I'm apprehensive about doing it anyway.
Click to expand...
Click to collapse
Same here except I think I'm at even a lower version... 0.76
What would the point be to upgrading hboot to 2.02? It's one thing I don't really understand all that well.
Anyone care to explain?
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
Are you following the guide in the wiki?
Sent from my T-Mobile G2 using XDA App
Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
First, yes you need S-Off to do a nandriod back up.
Second, you do not have permroot if you do not have S-Off. To get S-off there are several ways but I recommend using Rage+gfree found Here: in sub section "Rooting the Vision (G2/DZ) and DHD" This by far is the safest way to root.
But to let you make an informed decision there is also Visionary, now people in properly using this method, has produced a lot of soft bricks, I my self rooted this way, but again I still recommend using Rage+Gfree. But if you wish to still give Visionary a shot, Heres a link on how to properly use Visionary, make sure you follow everything to the "T". Read everything I have written in the post, do everything I have written in the post, then follow the videos exactly. But just to be clear, I am still recommending using the Rage+Gfree method. Happy Rooting.
ok joemm I tried the rage directions that you told me and I am not sure if it worked is there a way of knowing if it worked or not
Edit: nvm I can now get into CWM area which I could not get into before thanxs for the help and info.
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
Click to expand...
Click to collapse
LOL..........how does he flash a custom CWM recovery with out having a rooted phone? Remember he is using ClockWorkMod to do a back up?
KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
Click to expand...
Click to collapse
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
steviewevie said:
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
Click to expand...
Click to collapse
True you can't flash a custom recovery and have it stick after a reboot but you can package it into an update.zip and flash it when you get into recovery. Aside from that you're phone performs the same. That's how we did everything on the MT slide before some one found a method to gain s-off. Of course there were no custom MTD partitions and we couldn't change the splash but that falls into the 1% of things the average 'rooter' will not attempt. The only reason we needed the ENG hboot was so that adb would catch our phone in recovery every time without running a loop.bat and praying to god. As far as NAND write protection, normally when a dev manages to break s-on they also break the write protection. At least that's what I've seen in phones with s-off. Are there any not like that?
Hopefully I didn't come off as an ass earlier, didn't mean it. I got 3 hours of sleep and I'm pulling a 13 hour day with a foot of fresh snow outside
I think you might be drawing too much comparison with earlier phones. The DZ and DHD have much stronger security than earlier phones. People familiar with experience of older HTC Android phones have often made incorrect assumptions about how things work on the DZ, some things are quite different (and typically much more complicated to unlock)
Sent from my HTC Desire Z
steviewevie said:
People familiar with experience of older HTC Android phones have often made incorrect assumptions...
Click to expand...
Click to collapse
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
schaggo said:
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
Click to expand...
Click to collapse
Its become more difficult because device manufacturers have made it more difficult. The "official" means to root the Vision is posted on the Vision wiki page here at XDA.
Sent from my T-Mobile G2 using XDA App
Thanks for the answer. I got the thing cracked in the meantime. The device feels so much smoother without Sense... and Gingerbread is good for one's soul
Hey folks. I'm looking into updating to the latest radio, and so I've concluded it's finally time to get the engineering bootloader onto my phone. I have enough experience with my old G1 to not be super-nervous about it, but I have one quick question first.
When originally rooting using gfree back in late December, I decided to skip the SuperCID and SIM-unlock portions of the process. The wiki instructions for the eng-hboot, however, assume the user did all three options. With simply radio s-off, can I install the new bootloader, or do I need to go back and get SuperCID first?
Thanks for any help you can give.
You dont need an ENG Hboot to flash the new radio you can use the PC10IMG update method. Heres a link to the post with the download.
Thanks, joemm - reading through the various radio topics, I've gathered that you've been really helpful in providing PC10IMG files for people, and that's really appreciated.
My concern is if it turns out the new radio is worse than the old; it seems like the easiest way to go back to my current radio is through fastboot flashing, which is why I wanted to go to the eng hboot. I don't see a pc10img already out there with my current tmo, post-OTA radio (though it's listed in the mega-radio topic).
So, I guess my quesion is still open - do I need supercid to flash eng-hboot?
Actually I have a similar situation. I also skipped SuperCID and SIM-unlock when using gfree. (Not sure why I did, but Im sure it made sense at the time)
Anyway I have the eng hboot but would like to upgrade the radio.
Can I run gfree again to do the sim unlock and then upgrade the radio? Or upgrade to this radio - Vision_RADIO_12.28h.60.140f_26.06.02.27_M - and then run gfree again?
What does the sim-unlock change and supercid change acually happen anyway? I mean does it make a change to the radio itself?
Sim unlock makes a permission state change. Makes a 1 a 0, as I recall. Dunno bout SuperCID.
HTC Vision 1.8 OC, CM7 RC1==HAPPY!!
Thanks for the reply Daughain.
But where is that change made? is it made to the radio itself?
santaclaws said:
Thanks for the reply Daughain.
But where is that change made? is it made to the radio itself?
Click to expand...
Click to collapse
I don't think it changes the radio, because I've personally switched radios several times and I didn't have to unlock every time. Once, when I rooted the phone and that was it.
OK before i get SEARCH.. I did and here is what i have looked at so far (i am 3+ hours into my search)...
http://forum.xda-developers.com/showthread.php?t=838484
http://forum.xda-developers.com/showthread.php?t=842495
http://forum.xda-developers.com/showthread.php?t=905261
ANd a few others that link back to one of those 3.
This is not my phone. I am helping my buddy who attempted to perma-root his phone using Visionary+ 14. I have an evo, and several other android phones and understand the basics of ADB and how to do most this stuff.
After he applied the patch, we are stuck on the white HTC screen. The problem is, it does NOT have the ENG SPL, we are still s-ON and still have stock recovery.
Here is what i have attempted so far:
download and tried to have it reload PC10IMG.zip - Got an error that said the version i was trying to install was older than the one i already had. I downloaded the latest one i could find.
Since i can get into the stock recovery, i downloaded and tried to use update.zip to reinstall things correctly, but that didnt work. It didnt error out and looked like it installed correctly, but still just stuck at the white HTC screen.
I cannot access ADB (at least any way that i know how).
Yes, i have the correct USB drivers installed and ADB is working as i have accessed it for other phones.
Here is the phone stats:
VISION PVT SHIP S-ON
HBOOT-0.82.000
MICROP-0425
RADIO-26.03.02.26_m
eMMC-boot
Sep 2 2010, 17:59:38
I cannot find the right RUU to give that a try either. I have found a few that MIGHT be right, but i dont want to mess it up more by flashing the wrong thing (if this would even help.. i dunno)
ANY HELP WOULD BE REALLY APPRECIATED!!!!
Anyone?? Help????
frettfreak said:
this is why people post in the dev forum when they arent supposed to.... cause NOTHING happens if you post in q&a...
Anyone?? Help????
Click to expand...
Click to collapse
You only posted a few hours ago. On a weekend. Might want to be a little more patient than that...
And you stated you have S-OFF? But not the engineering HBOOT? So were you using Visionary to temproot and then used gfree to get S-OFF? If so, you should be able to flash a custom PC10IMG with the radio removed (so it doesn't check for the version number). I know there is a thread containing one made by Hot_Hands that some people have used.
Or did you actually mean you had S-ON and that was just a typo? If that's the case, you're at the same point as a lot of others who have semi-bricked their device with Visionary (there are lots of threads out there with people describing this exact situation---phone had the OTA already, still S-ON, no ADB access, stuck at the HTC screen). Don't think anyone's come up with a solution yet. Most are just waiting and hoping that an RUU of 1.22 comes out at some point.
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
ianmcquinn said:
You only posted a few hours ago. On a weekend. Might want to be a little more patient than that...
And you stated you have S-OFF? But not the engineering HBOOT? So were you using Visionary to temproot and then used gfree to get S-OFF? If so, you should be able to flash a custom PC10IMG with the radio removed (so it doesn't check for the version number). I know there is a thread containing one made by Hot_Hands that some people have used.
Or did you actually mean you had S-ON and that was just a typo? If that's the case, you're at the same point as a lot of others who have semi-bricked their device with Visionary (there are lots of threads out there with people describing this exact situation---phone had the OTA already, still S-ON, no ADB access, stuck at the HTC screen). Don't think anyone's come up with a solution yet. Most are just waiting and hoping that an RUU of 1.22 comes out at some point.
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
Click to expand...
Click to collapse
Good point!! Sorry.. just a little anxious. Dont want to tell him his phone is bricked....
Also... maybe no one responded cause i am a tard.... its s-ON still, not S-OFF
And just to make sure, you tried leaving the phone on for a while before connecting with ADB? And ADB didn't work in recovery either?
Click to expand...
Click to collapse
you mean leave it on the white HTC screen for a while? What is a while? I left it for a minute or 2 then tried and no dice... you think longer? Also, no ADB when in recovery (i think this is because its stock recovery maybe??)
i DO have access to fastboot (i think) but not sure if this gives us any where to go with it??
Sorry for the confusion and pushy-ness and thanks for your help!
frettfreak said:
you mean leave it on the white HTC screen for a while? What is a while? I left it for a minute or 2 then tried and no dice... you think longer? Also, no ADB when in recovery (i think this is because its stock recovery maybe??)
i DO have access to fastboot (i think) but not sure if this gives us any where to go with it??
Click to expand...
Click to collapse
Well, like I said before, this is the type of semi-brick that people seem to be stuck in when Visionary fails and I haven't seen a working solution. When I said to leave it at the HTC screen, it was just something mentioned in the how to recover semi-brick thread you linked to in the original post. Unfortunately, if that didn't work, you might by out of options.
EDIT: And oh, I forgot to mention about fastboot. Although it might seem like fastboot detects the phone properly, you cannot actually use it to flash anything unless you have the engineering HBOOT, so that doesn't help any.
Maybe geting the orginal stock rom and flash it through bootloader
Sent from my HTC Vision using XDA Premium App
lainvalenajr said:
Maybe geting the orginal stock rom and flash it through bootloader
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hmmm how do I do that? Is there a different way other than adb? I will check again but pretty sure I don't have adb access (I think this is what the eng spl does but I am just guessing here) does fastboot allow Me to do anything like that?
Howdy! Lemme preface all of this by saying that I'm less than a noob here....really inexperienced. Here's the background......
I rooted my DInc and I can't even remember which unrevoked tool I used. I was just reading along and punching commands and when the process was done I was rooted. I installed CWM successfully and flashed to CM7.2 which I've been running for quite some time. Lately I got an itch to try a JB ROM like infected, so when I looked into it, it clearly says I need S-off to accomplish that flash so I checked and realized I was S-on still.
At this point, I added the unrevoked-forever.zip to my sdcard root and tried to flash that ZIP by way CWM and i get these error messages:
E: unsupported radio version
E: update failed. Check/sdcard/soff.log
E: error in /sdcard/unrevoked-forever.zip (Status 42)
I am running Android version 2.3.7 and radio baseband version 2.15.10.12.20
Is this one of those things that I shouldn't be trying from CM7.2 and I should've dealt with before my initial flash to CM7.2?? Basically I'm totally freakin lost and in WAAAAY over my element, so any guidance would be duly appreciated. Thanks in advance!
Scott
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
PonsAsinorem said:
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
Click to expand...
Click to collapse
Sorry....i guess it pays to be extra thorough in the description of the problem. The link you left me is the one that I followed. I researched achieving S-Off on the DInc first and found this same page in my research. I followed the process and all went smooth right up until i started to flash the unrevoked-forever.zip from my sdcard via CWM. The aforementioned error messages came up on my phone and it said the process failed.
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
smvogel73 said:
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
Click to expand...
Click to collapse
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
PonsAsinorem said:
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
Click to expand...
Click to collapse
Yes thx....I'm gathering that! So this is where terminology gets so dang confusing for me. I didn't think unlocking my bootloader meant the same thing as achieving S-Off?? I already thought my bootloader was unlcoked, as I was able to flash CM7.2, which I didnt think I would be able to do if I had a locked bootloader. So wicked confused!!! And try as I miught to educate myself in these forums, I haven't located a sticky or guide that really thoroughly explains all the vernacular regarding android dev/modding/rooting/flashing/etc
So this other method will work with any radio baseband version then?? Or is it important to check compatibility there too??
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
PonsAsinorem said:
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
Click to expand...
Click to collapse
It says "UNLOCKED" and below that it says "S-ON
Thank u for the materials too!
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run. I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.
The ROM I'm looking to flash is Infection JB 4.2.2. The instructions say that if you're coming from. A non-AOSP ROM and are S-On that you've gotta extract boot.img and fastboot it after the ROM flash......whatever the heck that means???
smvogel73 said:
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run.???
Click to expand...
Click to collapse
Correct. Staying S-ON minimizes the danger. It locks your radio, and HBOOT, which are the main dangers.
smvogel73 said:
I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.???
Click to expand...
Click to collapse
Not really ROM flashing, but radio and HBOOT flashing, which is what unrevoked-forever tweaks.
I'd try to flash it one more time. When you do, what, if anything, are you wiping? You should be doing a factory reset, system, and boot wipe/format, then flash the ROM.
If that doesn't work (it might not, it's been awhile since I've worked with S-ON devices), then we'll move on to S-OFF (if you want).
Oh no.....I didn't even attempt to flash the Infection JB ROM specifically because I was not able to achieve S-Off. Whether it was intended or not, yea.....u sufficiently scared me about bricking the phone if I'm not to spec per the developer.
Are u saying I should wipe and then try to flash this ROM despite still being S-On?
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
PonsAsinorem said:
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
Click to expand...
Click to collapse
Well there you have it....I will trust your wisdom (as it is far supperior to my own) and I shall flash this ROM tonight!! I already have a nandroid backup of CM7.2 that Im running, as well as a Titanium backup of all my user apps/files.
Sincerest thanks for all your help!!
Hello. Im no expert but i think Cyanogenmod is aosp so you should be good.
I was where you were 2 yrs ago when I rooted my 1st phone: a friends froyo Dinc (ahhh...froyo). A few months ago I aquired my own and went to research how to root GB and everything has changed and is now vastly more complicated. Also I think every phone has a locked bootloader but not encrypted and I think Soff is extra security since I've only encountered it on htc phones. Anyway I've managed to get my inc to Soff but its still locked, idk how lol
Sent from my ADR6300 using Tapatalk 2