Now uh, go easy on me, my first time posting here.
I may seem like a total idiot here, but the amount of conflicting information I've seen is quite confusing. I've searched and searched and the more I read the less I seemed to be sure of.
My question:
Can I do the unrevoked method of rooting ('theunlockr.com - how to root htc desire unrevoked method' 20.9.10) [cant post links] on my specific device?
My handset information is
Bravo PVT3 SHIP S-OFF
HBOOT- 0.87.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.09.00.08
Android version: 2.2
Software number: 2.06.832.1
The 0.87 HBOOT seems rather rare on the forums, I don't know why. All I've read is that at one point the 0.87 version could not be rooted, but I don't know if that is still the case (this was information from April-July) and the unrevoked tutorial states that 'At this time, unrevoked3 works on all versions of the supported phones', which my phone would come under the CDMA Desire (BravoC) I'm pretty sure. Just would like some quick confirmation from you lot before I go and do something stupid.
Thanks!
it was mentioned that hboot version doesnt matter when using new unrevoked
If you've got S-OFF then you don't need to root do you? It should already be done...CDMA phones when rooted with unrEVOked get S-OFF
Sounds like you're already rooted, check to see if you've got Superuser Permissions in your program list
Nope, no superuser permissions, and the phones unused.
The fact that the phone supports WCDMA as well as GSM makes it the CDMA 'Bravo' model right?
Well if what you have written is indeed what it says in hboot, then you are s-off and it should be easy to flash or install super user to the phone
My phone supports WCDMA and GSM - it's not the same as CDMA...
Do you use a SIM card in your phone? If so, it's a GSM phone
Just double checked it, it definately says S-OFF, everything in the first post was 100% correct.
Strange, the phone is actually a Hong Kong model that I ordered, saving me quite a bit of money being in Australia. Seems a bit iffy that it was unlocked from the start, actually makes me think it's a used model, even though everything else looks and works flawlessly. Probably shouldn't complain, even though they've caused me a bit of confusion.
So these rooted ROMs that people are developing all contain the superuser permissions application, I can't seem to find that individual application for download though. Hmmm.
edit: found the application, installing.
Ah, so I have the GSM model.
When did you get the phone? The S-OFF 'hack' has only just come out so unless you're on an engineering Desire (which is highly unlikely) then someone cracked it before selling the phone...
If I were you, I'd follow this guide:
http://forum.xda-developers.com/showthread.php?t=768256
and go back to a stock WWE ROM and then root it using unrEVOked 3.14 and then you can flash whatever ROM you want...easier than faffing about with S-OFF and the like (you don't really need it unless you wanna change the initial splash screen or you're a developer)
I got the phone about a week ago.
Cheers for the advice.
EddyOS said:
When did you get the phone? The S-OFF 'hack' has only just come out so unless you're on an engineering Desire (which is highly unlikely) then someone cracked it before selling the phone...
Click to expand...
Click to collapse
Well the hboot version he is mentioning is not the same as the one patched by ieftm, so he might just have recieved a developer device? Sounds strange though.
And as eddyos is saying, you could just flash a ruu and go the traditional route, if you cant figure it out using the s-off hboot. It's pretty cool though.
edit: if it is an actual s-off device, wouldn't the flag for s-off be set and flashing a ruu would not help it? Just like unrevoked forever on evo?
Related
Hey, I'm gonna come with a really noobish question I gues... I've read alot of guides and such about this, but I still don't find anything that states it clearly, and it can get kinda confusing.
I have an HTC Desire that I want to root, it has HBoot 0.92 and OTA Froyo 2.2, I don't think this is a problem anymore though?
Now, I believe my phone is unbranded/unlocked - any way to check?
And what radio would I need to use? I'm from denmark and the tele company is called Telia... Does it matter?
And since I'm from denmark, I can't buy any paid apps off the market, and it pisses me off, rooting will fix that right?
I'd like to use the OpenDesire ROM. But it's a bit confusing with all kinds of topics refering to eachother, and the "Ultimate guide on rooting" says that I need HBoot 0.80 and a current rom of 1.15 (or something like that), I have 2.2 >.<
Thanks in advance.
Go to Settings>About phone>Software information
If your phone has S/W 2.09.405.8 then you're on a generic Desire - which is a good thing!!
Next is to check the box specification - if it says you've got a 3.7" AMOLED screen then you can downgrade the HBOOT and root your phone. If it doesn't say AMOLED then you've got a bit more work involved and the information you need is in the ROM Development forum
Hey, thanks for the quick reply!
I got everything you said.
So that means I can just use Unrevoked?
And how about the market? That's one of the main reasons for me to root, so that I'd be able to access the full market?
Bump? Or something
there's no way to root a Desire with the Bootloader HBoot 0.92 known yet, which you got after you've upgraded to Android 2.2.
This means you have to downgrade the bootloader first, root it with unrevoked, ...
There are several guides out there.
But the important thing is, that you must downgrade the Bootloader in order to root your device.
UpSpin said:
there's no way to root a Desire with the Bootloader HBoot 0.92 known yet, which you got after you've upgraded to Android 2.2.
This means you have to downgrade the bootloader first, root it with unrevoked, ...
There are several guides out there.
But the important thing is, that you must downgrade the Bootloader in order to root your device.
Click to expand...
Click to collapse
Aye, I kinda wrote that
I'm interested in the market problem for me.
Good evening.
I'm new to the forum, so I hope it's ok that I ask a question as the first thing?
(Oh and bear over with my english as it is not my main language)
I'm quite sure you guys get this question quite alot, but it is a bit hard for me to collect the necessary information needed for me to start working on my "problem".
My plan is too root my newly aqquired HTC Desire HD.
As an added information: I already temporary rooted it using the VISIONary+ application and that seems to work as it should. I can get root rights and everything. So far so good - I havn't tried using the permanent root option that this program allows as I want to know exactly what I am doing before doing anything (I heard all the scary stories of bricking and stuff)
So let's start out with the questions:
- How do I check what firmware, kernel, ect ect ect I've got so that I can get the necessary information?
- How do I know if it is branded or not? (Not sure what that even means... I live in Denmark and bought it at the shop, and it is not simlocked. Phone company is Telmore)
- Where the hell should I start?
I looked up this guide: wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide#Flashing_Radio
Would that help me?
Also looked at this: androidpolice.com/2010/04/16/complete-guide-how-to-fully-back-up-and-restore-your-android-phone-using-nandroid-backup-and-clockworkmod-rom-manager/
Could I just perma root with VISIONary+ without worrying and then using rom manager to get the recovery image on and stuff or is it better doing a manual root somehow?
Oh and by the way, I already got adb access to my phone through the pc!
(And please tell me if this is the wrong section of the forum.)
Thanks in advance!
I guess the first question is, did you purchase the telus desire hd in canada per chance?
The firmware /kernel info can be found in the about phone section of the settings menu.
As for rooting I personally favour the manual root specified by the good folks over at CyanogenMod here if you find that a bit daunting there are some automated one click tools over in the Development forums here on XDA, although most require that you have access to a computer running windows.
equlizer said:
I guess the first question is, did you purchase the telus desire hd in canada per chance?
Click to expand...
Click to collapse
Nope. It was bought in denmark.
Dunno if it's a telus model or anything (As I have no idea what a telus is lol)
Some Information about my device: (Btw I'm trying to translate from danish. So ask if something sounds wrong)
- Android Version
2.2
- Basebandversion
12.28b.60.140eU_26.03.02.26_M
- Kernelsystem
2.6.32.21-gf3f553d
[email protected] #1
Thu Oct 28 13:24:11 CST 2010
- VersionNumber
1.32.405.6 CL278359 release-keys
- SoftwareNumber
1.32.405.6
- Browser version
WebKit3.1
As far as I can see my VersionNumber (I guess that is my firmware??) matches the one that the cyanogenmod guide (As In I dont need to downgrade yay!):
wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide
Asks for.
Is there anything else I should check for before I begin, or would that be the guide I should follow?
Plus I forgot to say:
I'm pretty good with computers in general. So I don't care using an "advance" manual method as long as it is descriped well so I don't end up saying "Wait what? Where the hell should I go now?"
So no need to doing some noobish way (Not saying One click methods are noobish) I just need to know what to do and how it should be done.
ok for starters, dont worry about bricking, it's impossible to brick your device trying to root, infact there are only 2 ways you can brick your device, and thats flashing a radio or hboot you have the 1.32 software version and that can be easly permrooted using visionary, after you root, you may want to s-off aswell
AndroHero said:
ok for starters, dont worry about bricking, it's impossible to brick your device trying to root, infact there are only 2 ways you can brick your device, and thats flashing a radio or hboot you have the 1.32 software version and that can be easly permrooted using visionary, after you root, you may want to s-off aswell
Click to expand...
Click to collapse
First off, thanks for the quick help! *thumps up*
So I don't have to use the CyanogenMod guide? (would it be better if I did it that way?)
Or is it enough with a perm root with VISIONary?
Then after that I'm thinking of doing a backup (It's called Nandroid as far as I've read?)
Doing a perm root with VISIONary, followed up by flashing the recovery image using the one click option that ClockWork ROM manager allows.
Would I have to worry about doing that, or does my information say that my model should work perfectly fine with that?
I think it's quite important to say that I'm thinking of doing a Custom Rom later, but my first job is to get it rooted and backed up incase anything happens.
Oh and, how would I manage to do a s-off after I've got it rooted? Would that have to be done BEFORE doing the flashing of the recovery image and doing a backup?
you can use the Cyanogen method, thats just a manual way, i used visionary, and have had no problems at all, just click the permroot option and wait after you root, before you flash a custom recovery you need to s-off, this is because the nand chip has write protection, check out this thread http://forum.xda-developers.com/showthread.php?t=855403 jkoljo tool is awsome and although flashing a hboot is dangerous, no1 has bricked there device using his tool yet, thats how safe it is once you are s-off, you can download rom manager and flash a custom recovery
I can see that the tool is called "One click ENG s-off" as in ENGLISH.
Does it matter that my phone is bought in denmark and is in danish?? (Does the language matter at all? :O)
virtual-aidz said:
I can see that the tool is called "One click ENG s-off" as in ENGLISH.
Does it matter that my phone is bought in denmark and is in danish?? (Does the language matter at all? :O)
Click to expand...
Click to collapse
the ENG means engineering, there are two types of s-off, engineering s-off and Radio s-off, the engineering one allows you to issue fasboot commands though and the radio one dosent, either one will security unlock your bootloader though
Ah I see
I just noticed in the s-off guide: "tick "I have Radio S-OFF" in the tool"
Why do I have to tick that? I don't have Radio S-OFF? :O
And right now I can't even test out what we are talking about *sadface* I just noticed a dead pixel right in the center of the screen, so before I start messing around, I'm gonna take it to the shop and see what they say (God I hate dead pixels)
I know it's a bit (well alot) besides the subject, but I was just crossing my fingers that you were a dead pixel specialist and could answer a simple question: Would a dead pixel on a 1 month old phone (I think the pixel is red, but it could be black as in completly dead) have any chance of spreading or something?
Cause I could live with a single dot.. but if it has a chance of spreading, I would really wanna get it fixed before it's too late (And sorry for the off-topic in my own thread xD)
Notice the big OR in the requirements part? As you are not using a custom ROM, and you do not have Radio S-OFF, you should not tick it.
Dead pixels do not spread, and there are apps in market to revive dead pixels, you should try one of them.
jkoljo said:
Notice the big OR in the requirements part? As you are not using a custom ROM, and you do not have Radio S-OFF, you should not tick it.
Dead pixels do not spread, and there are apps in market to revive dead pixels, you should try one of them.
Click to expand...
Click to collapse
Haha... My bad.
As I mentioned in my first post, my main language is not english. So I misunderstood what it said
I think I'm ready now.
Just need to talk with the shop before I void the warranty for good.
Thanks for the help guys, and I will return when I get it working (or **** it all up.. who knows)
By the way, root, S-OFF and custom ROMs do not void warranty. It says nothing about software in the warranty terms, check it out yourself if you want to
Odd. There has been multiple cases where they did not fix phones that were just rooted.
jkoljo said:
By the way, root, S-OFF and custom ROMs do not void warranty. It says nothing about software in the warranty terms, check it out yourself if you want to
Click to expand...
Click to collapse
Oh and by the way. I see you're the creator of the s-off and radio s-off tools?
Is it true that you recommend Radio S-off (forum.xda-developers.com/showthread.php?t=857537)?
And how do I check if I meet all the requirements?
jkoljo said:
By the way, root, S-OFF and custom ROMs do not void warranty. It says nothing about software in the warranty terms, check it out yourself if you want to
Click to expand...
Click to collapse
actually it does............. "use of products, equipment, systems, utilities, services, parts supplies, accessories, applications, installations, repairs, external wiring or connectors not supplied or authorized by HTC" ........ custom bootloader, and software can come under the systems, applications and installations
Ah yay. I thought so
As far as I can see on the Radio S-Off (Again, is it recommended over s-off?)
System requirements:
Windows XP SP2 or higher
.NET Framework 4.0
HTC Sync (or ADB drivers)
Desire HD with stock kernel (or Apache14's 1.0.7 / 1.1.4 Sense)
It will not work on 1.72.405.3 or higher build, or new radio. Downgrade first!!
I got the 3 first ones covered.
But I'm not sure about the two last.
My Phone has HTC sense, but I dunno what version to be honest.
And I guess I got the last one covered too as I got the 1.32.405.6
You meet all the requirements
AndroHero said:
actually it does............. "use of products, equipment, systems, utilities, services, parts supplies, accessories, applications, installations, repairs, external wiring or connectors not supplied or authorized by HTC"
Click to expand...
Click to collapse
Please take a picture for me, that is not included in the warranty statement that came with my phone. I rang HTC about it, and they said that unless the hardware is modified, software does not matter. Also mike1986 sent his phone to be repaired with ENG S-OFF and everything, and nobody complained.
jkoljo said:
You meet all the requirements
Please take a picture for me, that is not included in the warranty statement that came with my phone. I rang HTC about it, and they said that unless the hardware is modified, software does not matter. Also mike1986 sent his phone to be repaired with ENG S-OFF and everything, and nobody complained.
Click to expand...
Click to collapse
How did you know I met the requirements with the HTC sense?
(I need to learn too)
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
I have a new(used) HTC EVO 4g. I am trying to root it before I activate it. I was following directions (can't post link as a noob, but) 4-GUIDE-WIP-How-to-achieve-S-OFF-after-unlocking-2-18-HBOOT-with-HTCDev-com-No-More-Watermark
and successfully unlocked the bootloader and removed the watermark.
However, when I get to the actual rooting step, it appears that either unrevoked is gone, or having some issue (or blocking me!) as I get 403 Forbidden errors. I have done an exhaustive search (including on this site, where I found someone had posted the file in dropbox but I get a 404 error on that one) and I cannot find either the unrevoked package or any other way to root my evo!
I would be very grateful for some help. Here are my specs:
android 2.2
baseband 2.15.00.11.19
software version 3.70.651.1
When I am in the bootloader menu, I see:
Supersonic evt2-3 Ship S-ON
HBOOT 2.10.0001
(I do not have the watermark saying "locked" or "unlocked")
Sorry to be a noob, but I have rooted several phones before but I just have no clue without the software...
As a side note- here are files I have found and managed to download (if there is a way to use them or if I haven't already used them to get this far): HTCDriver 3.0.0.0007, unrevoked-forever.zip, (I don't think this is the same as unrevoked3, which I need, but correct me if I am wrong) revolutionary-0.4pre4.zip, pc36IMG.zip (but not sure where i got this one from, so not sure what it is an image of.)
Get it activated first.. Then root it..
Sent from my PC36100 using xda app-developers app
hondafreak513 said:
Get it activated first.. Then root it..
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Is that really necessary? I could swear I read somewhere in the step-by-steps that it wasn't necessary to activate first. Since it will cost me $35 to activate it and the $35 to reactivate my existing phone if I can't get this rooted, I really have no desire to activate yet. Plus seeing as the problem I am having is in accessing the website I need to go to download the files for rooting, I can't see why activating would make any difference?
Rooted!
karenmolloy said:
I have a new(used) HTC EVO 4g. I am trying to root it before I activate it. I was following directions (can't post link as a noob, but) 4-GUIDE-WIP-How-to-achieve-S-OFF-after-unlocking-2-18-HBOOT-with-HTCDev-com-No-More-Watermark
and successfully unlocked the bootloader and removed the watermark.
However, when I get to the actual rooting step, it appears that either unrevoked is gone, or having some issue (or blocking me!) as I get 403 Forbidden errors. I have done an exhaustive search (including on this site, where I found someone had posted the file in dropbox but I get a 404 error on that one) and I cannot find either the unrevoked package or any other way to root my evo!
I would be very grateful for some help. Here are my specs:
android 2.2
baseband 2.15.00.11.19
software version 3.70.651.1
When I am in the bootloader menu, I see:
Supersonic evt2-3 Ship S-ON
HBOOT 2.10.0001
(I do not have the watermark saying "locked" or "unlocked")
Sorry to be a noob, but I have rooted several phones before but I just have no clue without the software...
As a side note- here are files I have found and managed to download (if there is a way to use them or if I haven't already used them to get this far): HTCDriver 3.0.0.0007, unrevoked-forever.zip, (I don't think this is the same as unrevoked3, which I need, but correct me if I am wrong) revolutionary-0.4pre4.zip, pc36IMG.zip (but not sure where i got this one from, so not sure what it is an image of.)
Click to expand...
Click to collapse
Okay, I actually fixed it myself--- Still have no idea what is going on with unrevoked site-- either it is my ISP or the site is bad. Either way, I finally found another way to root. Here on this site, I found a rooting method that was older, HBOOT 2.10 SOFF, and that worked fine for me!
(Wanted to post my solution so if anyone else found this thread while having the same problem, they would be able to fix it also.) Post was titled: [ROOT][GUIDE] HBoot 2.02/2.10 SOFF - Goodbye Stranger - Upd. 02.25.11
karenmolloy said:
Okay, I actually fixed it myself--- Still have no idea what is going on with unrevoked site-- either it is my ISP or the site is bad. Either way, I finally found another way to root. Here on this site, I found a rooting method that was older, HBOOT 2.10 SOFF, and that worked fine for me!
(Wanted to post my solution so if anyone else found this thread while having the same problem, they would be able to fix it also.) Post was titled: [ROOT][GUIDE] HBoot 2.02/2.10 SOFF - Goodbye Stranger - Upd. 02.25.11
Click to expand...
Click to collapse
The Unrevoked site is down.
I must point out that "YOU WERE LUCKY", as that root method only works on the older Evos with the old hardware. It has been known to brick the newer Evos, as you could have easily done if you had the new hardware. Without Unrevoked, the safest method to root the phone would be to update it to one of the later builds (Gingerbread) and either use Revolutionary or the HTCdev site, depending on the build to unlock the bootloader. Then flash a custom recovery followed by a superuser.zip file.
Yikes!
shortydoggg said:
The Unrevoked site is down.
I must point out that "YOU WERE LUCKY", as that root method only works on the older Evos with the old hardware. It has been known to brick the newer Evos, as you could have easily done if you had the new hardware. Without Unrevoked, the safest method to root the phone would be to update it to one of the later builds (Gingerbread) and either use Revolutionary or the HTCdev site, depending on the build to unlock the bootloader. Then flash a custom recovery followed by a superuser.zip file.
Click to expand...
Click to collapse
Yikes! Wow, glad I was a lucky one! Not surprised I have an older Evo, I got it off ebay.
I actually had started with Revolutionary, but my HBOOT was 2.18 (I think) and that only worked with 2.16 and 2.17. So then I went and downgraded to the 2.10, etc....
Just in case I need to know in the future, is the unrevoked site down temporarily or permanently?
karenmolloy said:
Yikes! Wow, glad I was a lucky one! Not surprised I have an older Evo, I got it off ebay.
I actually had started with Revolutionary, but my HBOOT was 2.18 (I think) and that only worked with 2.16 and 2.17. So then I went and downgraded to the 2.10, etc....
Just in case I need to know in the future, is the unrevoked site down temporarily or permanently?
Click to expand...
Click to collapse
I don't know for sure, but since mostly everyone is now on Gingerbread builds and very few are still using Froyo, don't be surprised if that root method is never up again.
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