Database Info

Delete

Delete

I don't know whether the unrevoked3 could work under 0.83,
it's confirmed that it could not work under 0.92.

You don't need unrevoked. This update.zip is applied using the stock recovery.

Hi lollylost100,
I'm just trying your instructions above to recover my desire.
I don't seem to get anything on the screen at any stage of the above.
Is this correct?
If so, I must just be pressing the wrong buttons in the wrong order as I've not been able to recover my device.

Well if you downgraded using this method: http://forum.xda-developers.com/showthread.php?t=745903 then you should be able to upgrade using the method in first post. Nothing will be displayed on the screen. You just have to follow the instructions without the screen.

I downgraded by creating a gold card and then running the ruu.exe for 1.21.
When I could not get the screen working I applied
RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.06.00.02_2_release_127568_signed
in the same way.
When I tried to downgrade using the RUU for a SLCD version, I get the bootloader incorrect version.
Am I screwed?

Try the HBOOT downgrade method again and then apply the fix in the first post.
It's because the file from first post is: OTA_Bravo_Froyo_HTC_WWE_2.09.405.8-1.21.405.2_release4dua3bcrut4wrv30.zip
2.09.405.8-1.21.405.2 - from 1.21.405.2 to 2.09.405.8 (WWE).

I have a goldcard I created at the start of all this but I can't create a new one as I get 'failed to get CID' using gold card tool 0.0.5.
I'm guessing this is because the device is not in the correct mode anymore?
Do I need to generate a new goldcard image based on where I am ?

Well done lollylost100!!!
My phone is okay but thanks just the same. I'm sure a lot of people will find this very useful.

wait, where can i get the update.zip ?

yuzz101 said:
wait, where can i get the update.zip ?
Click to expand...
Click to collapse
Download: http://liveimage.htc.com/OTA_Bravo_F...crut4wrv30.zip and rename it to update.zip

yuzz101 said:
wait, where can i get the update.zip ?
Click to expand...
Click to collapse
"Download: http://liveimage.htc.com/OTA_Bravo_F...crut4wrv30.zip and rename it to update.zip"
You need to read more carefully
edit: well damn you for being faster!

okay, now i know where is the update.zip.. after applying the update.zip, how many minutes should i wait? for the installation?

i dont have to be rooted right and isnt glodcard is only for branded Desire? cos, installing rom spos to be rooted and use ClockWorkMod? hmm. sorry for being such a noob. im just panic please..

Theoretically goldcard is only for branded phones. You don't need to be rooted. You should wait about 30 mins after applying update.zip just to be on the safe side.

Very nice. Well done!
Congrats to everyone with working screens now

yuzz101 said:
i dont have to be rooted right and isnt glodcard is only for branded Desire? cos, installing rom spos to be rooted and use ClockWorkMod? hmm. sorry for being such a noob. im just panic please..
Click to expand...
Click to collapse
Hi yuzz..nice too see Bruneian in this forum, i thought i'm the only one...sry for the off topic

Talz, do you have this kind of problem to?

Some extra information:
It is also possible to recover using a stock RUU. This may be useful if you want to run 2.1 instead of upgrading to 2.2, or you want to upgrade later.
The RUU that is compatible with SLCD phones is here:
http://shipped-roms.com/shipped/Bra...1.00.32U_4.08.00.09_release_137222_signed.exe
To run this, make sure your goldcard is inserted and start the phone in fastboot mode (hold back key and power button).
If you get a 140 error when running this, you will probably have to use the update.zip method for FroYo (of course if you do want FroYo you don't need to worry about this).

You don't mind if I include this in first post?

Weird problems

So i bought an inspire from my friend and all was good until yesterday when the volume down button stopped working on me. then after a series of crazy boots it started working again which is leading me to believe the software is effed up. Its running MDJ's Ultimate droid HD v 1.8 and is completely freaking out on me. Being new to android, i just want to flash it back to stock. Can anyone help me out? also, the volume button is again acting stupid so hopefully it starts working again.

Griff1220 said:
So i bought an inspire from my friend and all was good until yesterday when the volume down button stopped working on me. then after a series of crazy boots it started working again which is leading me to believe the software is effed up. Its running MDJ's Ultimate droid HD v 1.8 and is completely freaking out on me. Being new to android, i just want to flash it back to stock. Can anyone help me out? also, the volume button is again acting stupid so hopefully it starts working again.
Click to expand...
Click to collapse
This is the ROM/Radio RUU from the latest OTA Update (it has root though):
http://forum.xda-developers.com/showthread.php?t=1058042
You want the first download (RUU_Ace_Cingular_US_1.84.502.11-Radio-26_06_06_30_M_PD98IMG.zip - No side load (Unknown sources/3rd party app - original ATT) version
md5sum: f2c80025662eae4f68f205d5cda48fa2)
If you want pure stock here's (http://forum.xda-developers.com/showthread.php?t=952224) the RUU from ship (no root). After you install this at some point you will be prompted to install the OTA update

homeslice976 said:
This is the ROM/Radio RUU from the latest OTA Update (it has root though):
http://forum.xda-developers.com/showthread.php?t=1058042
You want the first download (RUU_Ace_Cingular_US_1.84.502.11-Radio-26_06_06_30_M_PD98IMG.zip - No side load (Unknown sources/3rd party app - original ATT) version
md5sum: f2c80025662eae4f68f205d5cda48fa2)
If you want pure stock here's (http://forum.xda-developers.com/showthread.php?t=952224) the RUU from ship (no root). After you install this at some point you will be prompted to install the OTA update
Click to expand...
Click to collapse
Note that will not get you s-on

and how do i go about flashing the non rooted one. i just want this phone to be out of the box. sorry for the noob questions, im brand new to android. And if it helps any its running a custom gingerbread 2.3.3 rom

Griff1220 said:
and how do i go about flashing the non rooted one. i just want this phone to be out of the box. sorry for the noob questions, im brand new to android. And if it helps any its running a custom gingerbread 2.3.3 rom
Click to expand...
Click to collapse
Turn off USB debugging (Settings-Applications-Development-Remove check from USB Debugging), connect phone to computer, make sure you're in Charge only mode. The file you download is in .exe, so just run the program and follow the prompts. As stated earlier, this won't turn S-Off to S-On, but you'll still have a pure stock, unrooted ROM and Radio. There's a thread somewhere that discusses getting S-On (which you'll need to do before you run RUU if you're worried about it). Give me a minute and I'll try to dig it up.
Edit:
Follow the instructions here (http://forum.xda-developers.com/showthread.php?t=1033353) under MISCELLANEOUS to get S-On before running the RUU. Needed files are provided.
Note: that thread says to run the RUU, then perform the modified hack kit instructions to get s-on, then run the ruu again. You should just be able start from running the hack to to step 3, running ./gfree -s on, then running the RUU - you shouldn't have to run it first.
Another note... make sure you download the hack kit from this thread. It's version 9. The newer versions worked a little differently and I don't think they use gfree to get s-off, so newer versions won't work like this.

What's Ruin? Why would I need to run it and what's s-off? Sorry I'm trying to learn as I go.
Sent from my Desire HD using XDA App

Griff1220 said:
What's Ruin? Why would I need to run it and what's s-off? Sorry I'm trying to learn as I go.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
S-Off is Radio Security off. This is what allows you to flash custom ROMs/Radios/Kernels. Part of the root process is gaining S-Off. If you want a straight from factory set-up, you would need to return to S-On. This would only be necessary if you're returning the phone to ATT or HTC for some reason, even then it's not likely they would check this setting. You can still be S-On and run the stock, unrooted ROM
The RUU is a combination of the stock ROM, kernel, and radio. When you run it, it wipes anything currently on the phone and installs the image that's installed at the factory. When it's done, you will have a stock, unrooted ROM and kernel with the factory radio
If you feel it's a software issue, why not try flashing a different ROM instead of going back to stock? There are plenty of ROMs out there that work flawlessly if not next to it.

I would like to thank you homeslice976, as I stumbled into this thread looking around, but I had this same exact question!

[Q] Quasi-Bricked?

Hello! I'm a long-time lurk and this is my first post. Why? Because you folks at XDA are extremely knowledgeable and very helpful! I actually enjoy reading the forums and usually can find my answer using search. Call me a masochist, I guess. I just wish I had the chops to develop and not just be a continuous noobish sponge. I have successfully rooted my own Inspire with Bubby’s method and have flashed several radios and ROMs, no problem (knock on wood).
Anywho, I have searched and have seen similar issues to mine, but I have what I consider a more unique problem (which, if I’m wrong, I’m sure you fine folks will let me know). I attempted to root my brother’s Inspire over the weekend and it is currently showing a black screen with three vibrations and amber light (If I try to go to Hboot manually, I get five whole vibrations with a green light). I can, though, pull the battery for 5 minutes or so, then the phone will boot normally. Although I think it’s on the downgraded ROM, because it shows the funky AT&T splashscreen instead of HTC. What I did was attempt root with Bubby’s and got stuck at the boot screen when the phone was trying to flash the PD98IMG.zip (downgrade I believe) after making the goldcard. It would show that it was trying to read the zip, however I never would get the “volume up to upgrade” option. I tried this three times. When that failed, I tried rooting with the Ace Hack Kit and after creating the goldcard image, when the script tried to reboot the phone to install the downgrade, I got the black screen, amber light with the 3 vibrations. My problem is that I don’t have root, can’t get to recovery from the Hboot screen (shows red exclamation with triangle) and was unable to install Clockworks Mod thru ROM manager because I’m not rooted, so no SuperUser privileges.
What can I do at this point? Maybe off base, but I believe I have somehow corrupted the boot partition or the like, including screwing up Hboot. Is it possible to fix this if I am not able to reboot without pulling the battery? I have tried going thru Bubby’s and the Ace kit again, but always fail when the phone reboots.
Thanks for your help!

I am far from an expert, or even a novice, but to me it sounds like you have a corrupted download for the bubbys one click.... Have you checked the Md5 on the downloaded file?
Sent from my Inspire 4G using XDA App

I could lie and say yes, but no I didn't check md5 the first go around (although I did the 2nd time I reinstalled, after it screwed up). I did have all antivirus programs uninstalled and firewall turned off.

It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk

@OP:
Follow the files and instructions in this post to get back to stock so u can start fresh. I followed these to get back to stock only today evening, and it worked.
--------------------
TO RETURN TO STOCK:
Make sure you S-ON (if able) BEFORE you Unroot. The S-On tool needs root permissions to function.
--------------------
Turn the phone on, connect to computer, and perform step 1. Make sure USB debugging is enabled.
Step 1 (S-On):
Run Bubby323's S-On tool: S-On Tool
Step 2 (STOCK ROM in ZIP FORMAT):
Place this .zip file on the root of your SD card. Disable fast boot in settings > applications. Turn off your phone. Hold down the volume down button and the power button at the same time. The phone will reboot into hboot. It will load the ROM automatically. Follow the steps to flash the ROM.
http://www.multiupload.com/JELMZNSKDF
I did this like a couple hours back, and mine's back to stock.
Note: I consolidated the links here from various posts on this forum.

Diablo: Was posting the reply below, when I saw your message. Would you still recommend I follow your steps to unroot, return to stock and run hack again?
Update: Well, I went thru Bubby’s root process again and was able to get the phone rooted (had to pull battery and wait 4 minutes when it needed to reboot). And I have confirmed root was successful. I also used Bubby’s fix to Eng S-Off (couldn’t hurt, right?). The phone now has the latest Android Revolution with Sense and the radio has been flashed (including full wipe and EXT4 wipe). However, it STILL won’t reboot correctly. I can boot directly into Clockwork from ROM Manager, but if I try to reboot normally (hold down power button and select restart), I get the black screen, amber light and 3 vibrations. Again, pull battery and wait 4 minutes and either power button to boot normally or power and volume down to get to Hboot works fine and goes to Clockwork from Hboot fine also. I guess I can keep up with the batter pull only when I have to manually restart, but WTH? There has got to be a fix for the reboot issue. Any ideas?

fernandezhjr said:
It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.

ogarlen said:
...I also used Bubby's fix to Eng S-Off (couldn't hurt, right?)...
Click to expand...
Click to collapse
Well, actually, wrong, it could hurt. I'm not saying that's the cause of your problems, but you really should've read up a little more before clicking on stuff so nonchalantly.
Eng s-Off means the engineering bootloader. If that process were to fail while in the midst of performing it on your phone, it would most likely hard-brick it.
Not to mention it's unnecessary. It was only included in that rooting method at the time for flashing radios, I believe, and since then a safer method for doing so has come into standard usage that doesn't require eng s-Off.
It's also one method of resolving the cwr blackscreen people were having, where you're actually in cwr, but the screen is black so you can't see what your doing. Not the same black screen your seeing, I don't think, because you're able to at least get into cwr.

ogarlen said:
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.
Click to expand...
Click to collapse
The vibrations with the blinking led, I have seen a few posts with this. Sadly, I haven't seen anyone post a fix yet.
Sent from my Desire HD using Tapatalk

Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.

ogarlen said:
Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.
Click to expand...
Click to collapse
Heh. Now that you explain it, I can see the sarcasm. I'm usually good a picking up on it, but you know how these internet textual posts go....smilies are crucial...
As to your problem, there seem to be a few posts in recent days describing the led/vibrations type of symptom.
I don't know if they're interrelated or not. I don't have an answer, but I'm curious and will drop in if I manage to come across any pertinent information.

Thanks for the replies! I will continue to research and update this thread if I find a solution. I really believe that it has something to do with the startup processes or boot cache or some other $10 phrase related to what happens when the phone is attempting to startup normally. I appreciate all help.
Sent from my Inspire 4G using XDA App

Just wanted to add a quick update for anyone searching that comes across this post: The phone in question is now working flawlessly (knock on wood). Restarting, power down and battery pulls work with no problems (no vibrations or flashes). I am honestly unsure what I did to cause this error or what the resolution was and can only speculate. Since my last post, I have made a Nandroid backup and flashed a couple ROMs (namely AR with Sense, then Virtuous Unity with full wipes in between), so I assume that somewhere in there the corrupted boot files (or whatever) were corrected. All's well that ends well...

Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.

Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.

seems like you got yourself a good taste of rom flashing issues. that's a good thing. i know that you have everything working flawlessly now, BUT i would still HIGHLY recommend that you download the Super Wipe script from the Android revolution thread and use that to completely wipe and format your partitions, then do a FULL wipe through clockwork and then install whatever ROM you would like. but i cant stress enough, MAKE SURE that the Md5 sums match always. this can be the difference between a working rom and a bricked phone. also i would like to add that through my experience i usually find that the first time you root the inspire, the very first rom you install on it almost always has issues. that's how it is for me atleast. Ive rooted plenty of Inspire's and all of them have had some sort of issue on the first flash. and as always, follow the directions per rom to the T or else it might not work.
P.S. Some roms run better with matching Radio and RIL. flashing these is AWLAYS good practice to get your phone to tunr the best possible.

Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
Thats why I posted the full steps in the guide , to s-on and ruu back to stock. On a side note bubbies s-on tool does not always work.
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.

mudknot2005 said:
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.
Click to expand...
Click to collapse
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.

Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
You are correct. I should have re phrased that differently. I know that S-Off would survive the RUU procedure so I should have said "almost out of the box". The RUU is still a very handy thing to have.

Gene Poole said:
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.
Click to expand...
Click to collapse
Please, sir.
Seriously, this would be, imo, a profound contribution to this phone.

<Collaboration><Dev><Ideas> HTC Evo 2.3.3 Gingerbread Root Collaboration.

<Collaboration><Dev><Ideas> HTC Evo 2.3.3 Gingerbread Root Collaboration.
* I love the color orange.​HTC Evo 2.3.3 Gingerbread Root Collaboration​
The Lowdown on Everything​
FASTBOOT
HTC's RUU releases basically run the adb reboot bootloader code, reconnect to the phone, verify the version and run a series of fastboot commands to install the contents of the PC36IMG (detailed below). In the same way it may be possible to run fastboot commands from command prompt with the SDK installed if you can time it just right in the flashing process, or not. The bootloader can be quite picky when it comes to letting anyone or anything flash anything lower than the version on the phone, or unsigned.
Click to expand...
Click to collapse
PC36IMG
The PC36IMG is what is flashed in the bootloader. The contents of the zip include the radio, system, and more. As long as S-ON is present the bootloader won't flash any PC36IMG that isn't signed by HTC themeselves, however with S-OFF you can flash custom PC36IMGs as well as downgrade, because the bootloader doesn't check the firmware version to see if it's newer or not. If someone was however to be a sneaky awesome ninja and steal HTC's secret sauce then we could simply sign any PC36IMG we wanted to and fake a newer version in the android info txt.
Click to expand...
Click to collapse
RECOVERY
From my understanding the stock recovery references alot with the bootloader to check for most of the same checks it looks for in the PC36IMG, but in the update.zip HTC includes for updates. The stock recovery won't flash anything but signed HTC update.zips either, which again you need the special sauce to sign. Custom recoveries like Amon RA or Clockwork remove the security and don't reference with the bootloader (since your phone has to be S-OFF anyways to flash a custom recovery.) A custom recovery is the key in flashing customs roms and kernels, if you can achieve it with the security on (S-ON) the you won't even have to worry about achieving S-OFF. However, that's near impossible due to the security in the bootloader HTC implements with updates. Which is why the bootloader has to be cracked to install anything.
Click to expand...
Click to collapse
RUU
The RUU is an official tool HTC puts out so people can reflash there phone with a stock firmware just like if it is brand new and your turning it on for the first time. The files included inside of the RUU frontend include the PC36IMG which is essentially what is flashed in the process, but in a fancy way I guess you could put it. The same security applies to the RUU, you can't downgrade versions without S-OFF because the bootloader still checks the version on the phone currently to see if it can flash the PC36IMG or not (when security is on [S-ON] )
Click to expand...
Click to collapse
APKS
I'm sure alot of you know of applications such as Visionary or Z4Root, they both use common exploits to root your phone in a simple application, first temp root then permanent root. They push the approiate resources, Superuser, su, busybox, set the permissions for everything to run, and clean up everything in the blink of an eye thanks to simple scripts. The same thing is still quite possible with any exploit, the exploit just has to be found in the software. You find the exploit you gain root. You have root you can do almost anything to your phone, but S-OFF still plays a role in everything with what you can and cannot flash. Sigh. I know right..
Click to expand...
Click to collapse
Our Mission​
The whole purpose of this thread is to collaborate on possible ways to obtain S-OFF and/or root on 2.3.3, either update. We are community, thus we must act like one, and not bash each other for trying. If you have a truthful idea or any questions feel free to post them. You never know, you could very well help with rooting the latest update. This has gone on far to long it's been almost 2 months and no root. This is our time to free each other from the chains of security because we all like to be dangerous sometimes.
Click to expand...
Click to collapse

Possible Rooting Ideas​

What Works What Doesn't​
I encourage everyone to try previous rooting methods, and methods to obtain S-OFF and experiment as much as they feel comfortable with, you never know what you might find. We could be overlooking something.
Click to expand...
Click to collapse

There is no right or wrong answer only better ones than others. Please do not bash users, or slander them for there ideas, everyone has a right to post, but please stay on topic. /end

Am I missing something?
Sent from my PC36100 using XDA Premium App

lil_bono said:
Am I missing something?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Just give me a few, I'm still typing.
<done></done>

<words>I'll be back on tomorrow, I'm going to go lay down and talk to my friend. Feel free to comment with any ideas. I, myself, am looking into and working very hard to achieve S-OFF and root for the 2.3.3 update, it will come in time. That's just the key; time.</words>

What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.

ill jsut post a small snippet of thanks for thaking this initiative, i dont know about android os myself one bit, so i can hardly contribute, but would there be a way to "fool" the hboot or Ruu version number ?
either fooling the hboot into thinking the ruu one is trying to flash ( to downgrade of course) is a higher version one, or to somehow change the RUU itself to report a different version number? i realize this may sound incredibly stupid as my programming knowledge is very limited, but jst throwing it out there...
once again, thanks for taking this initiative for the evo 4g community

I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...

This should take off
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671

skatrwannabe3 said:
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671
Click to expand...
Click to collapse
Hey, great idea. Just so you know, there is no "bounty" on rooting the ota. I dont even know where that term came from. I just started a thread to say that I am desperate for root, I will pay for someone to figure it out. I never asked anyone or expected anyone else to throw money in on it too. It has since grown into a 600+ dollar pot, and I think that its a good thing. The people that take the time to root it should get a pat on the back.
On topic: I see a bunch of people saying to downgrade, isnt temp root gonna come before that? Shouldnt temp root be the thing to focus on first?

I'm not much of a programmer but ill brick my phone as many times as needed lol
Sent from my PC36100 using XDA App

github said:
What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.
Click to expand...
Click to collapse
I've personally never been the leader of a rooting or S-OFF project before, but my knowledge of Android on a whole is pretty vast. I do develop roms and kernels as well as themes and apps for Android in general, so I guess I'm pretty qualified?

fldash said:
I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...
Click to expand...
Click to collapse
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.

Who rated the thread bad?

bubby323 said:
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.
Click to expand...
Click to collapse
but does the RUU update the hboot itself?
the point is , older hboots and android software are already rooted, if we can get back to those , the end result is the same, we get root, then upgrade using a stock rooted rom, problem solved

bubby323 said:
What Works What Doesn't​
Click to expand...
Click to collapse
My recent failures attempts while on 4.24 S-On:
Amon_Ra Recovery PC36IMG.zip flashed from Hboot
Signed 3.70 PC36IMG.zip flashed from Hboot
Signed 4.24 PC36IMG.zip flashed from Hboot (it loads/updates, but is basically a factory reset)
3.70 RUU exe
UnrEVOked3

some chucklehead
bubby323 said:
Who rated the thread bad?
Click to expand...
Click to collapse
Eh, I put in a 5 star vote to make it up, also to show the uselessness of voting.

Has anyone looked at the contents of a PC36IMG.zip? I am still decompliling one, but its a fun task to decipher all of the code. Another thing I need is for someone to tell me which files I should be looking for as far as HTC signing. What I would like to do is maybe strip it from the stock one, and insert it into a custom image.
Sent from the land of motorcycles!

[Q] need help with installing custom rom on htc sensation pyramid

hi everyone
i havebeen struggling with this for 2 years now. i have HTC sensation with hboot 1.18.xxxx that i bought in 2011. after the first year i have been keen to move to a newer rom. i have tried to look up inf in xda and elsewhere and got no where with this.
i have been worried about bricking so much that i didnt try to many weird procedures. i had even tried to go through with the android revolution installation procedure but failed right on. because revolutionary does not with with my device even though thr hboot is supported.
i badly need to move to a newer jelly bean based rom or later else my device is like a stone-age crap. i sincerely request some straight forward process / guidance of getting through this without weird, wire trick etc.
i really want to keep this device instead of buying a new device for no reason. but i dont know how to start and how to end. kindly help me out.

rajdeeprath said:
hi everyone
i havebeen struggling with this for 2 years now. i have HTC sensation with hboot 1.18.xxxx that i bought in 2011. after the first year i have been keen to move to a newer rom. i have tried to look up inf in xda and elsewhere and got no where with this.
i have been worried about bricking so much that i didnt try to many weird procedures. i had even tried to go through with the android revolution installation procedure but failed right on. because revolutionary does not with with my device even though thr hboot is supported.
i badly need to move to a newer jelly bean based rom or later else my device is like a stone-age crap. i sincerely request some straight forward process / guidance of getting through this without weird, wire trick etc.
i really want to keep this device instead of buying a new device for no reason. but i dont know how to start and how to end. kindly help me out.
Click to expand...
Click to collapse
1st
This is definately not the place to ask for "all inclusive help".
You should at least do some own basic researches or leave your phone as it is,
especially when you're worried about bricking your device.
There are so many excellent descriptions here, that could guide you to flash a custom rom.
2nd
If you are on hboot 1.18 you don't need to do the wire trick for s-off, just have a look at this.
If you searched a little bit, you'd find out yourself.
But even the wire trick is nothing "bad", I did it on 6 devices till now.
I'd like to encourage you to simply read/search a little bit more here in the forums before coming back and asking for help.

tom0769 said:
1st
This is definately not the place to ask for "all inclusive help".
You should at least do some own basic researches or leave your phone as it is,
especially when you're worried about bricking your device.
There are so many excellent descriptions here, that could guide you to flash a custom rom.
2nd
If you are on hboot 1.18 you don't need to do the wire trick for s-off, just have a look at this.
If you searched a little bit, you'd find out yourself.
But even the wire trick is nothing "bad", I did it on 6 devices till now.
I'd like to encourage you to simply read/search a little bit more here in the forums before coming back and asking for help.
Click to expand...
Click to collapse
thanks for the reply. as i mentioned revolutionary does NOT work for me. it says failed to get root. i have already tried those things about 8 times now and it didnt work for me. thats why i have posted here for help.
using htcdev i know i can try to unlock but it wont soff. so i dont know if that will help me or not.

rajdeeprath said:
thanks for the reply. as i mentioned revolutionary does NOT work for me. it says failed to get root. i have already tried those things about 8 times now and it didnt work for me. thats why i have posted here for help.
using htcdev i know i can try to unlock but it wont soff. so i dont know if that will help me or not.
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=2751187 to gain S-OFF. Don't worry about the htcdev part.
I did it on a complete stock sensation xe with hboot 1.27 or 1.29 (can't remember exactly).
Just use the temp root and rumrunner.
For any information read the thread first, before asking.
Also this thread should be moved, because it doesn't belong into the development section.

Sajito said:
Try this http://forum.xda-developers.com/showthread.php?t=2751187 to gain S-OFF. Don't worry about the htcdev part.
I did it on a complete stock sensation xe with hboot 1.27 or 1.29 (can't remember exactly).
Just use the temp root and rumrunner.
For any information read the thread first, before asking.
Also this thread should be moved, because it doesn't belong into the development section.
Click to expand...
Click to collapse
thanks i will try to read up and post back if needed. Admin please move the thread to appropriate category.

Sajito said:
Try this http://forum.xda-developers.com/showthread.php?t=2751187 to gain S-OFF. Don't worry about the htcdev part.
I did it on a complete stock sensation xe with hboot 1.27 or 1.29 (can't remember exactly).
Just use the temp root and rumrunner.
For any information read the thread first, before asking.
Also this thread should be moved, because it doesn't belong into the development section.
Click to expand...
Click to collapse
i went through the thread again and again but still find it somewhat confusing. I cant seem to separate the temproot process start and end in there. can someone outline just the temproot procedure and the pre-requisite for it ?
Does temproot require controlbear files ? rumrunner site says it requires a htc dev unlocked device. is that a must ?

rajdeeprath said:
i went through the thread again and again but still find it somewhat confusing. I cant seem to separate the temproot process start and end in there. can someone outline just the temproot procedure and the pre-requisite for it ?
Does temproot require controlbear files ? rumrunner site says it requires a htc dev unlocked device. is that a must ?
Click to expand...
Click to collapse
I'm not 100% sure about the exact steps anymore, but you don't need Controlbear, you just need the temp root.
When you have temp root, run rumrunner and follow the instructions.
I said read the thread, cause it might be possible that you get the message that it didn't work, while it actually did work.
You'll get everything needed in the thread. Otherwise just ask.

Sajito said:
I'm not 100% sure about the exact steps anymore, but you don't need Controlbear, you just need the temp root.
When you have temp root, run rumrunner and follow the instructions.
I said read the thread, cause it might be possible that you get the message that it didn't work, while it actually did work.
You'll get everything needed in the thread. Otherwise just ask.
Click to expand...
Click to collapse
Seriously dont know if i am plain unlucky or topic are not very useful for a newbie.
1. Revolutionary failed
2. i did temp root + rumrunner - failed (image attached)
I wonder if my device was not made on this earth or something. Just simply soff. Also dont know if i cant install a JB rom on this without soff safely.

rajdeeprath said:
Seriously dont know if i am plain unlucky or topic are not very useful for a newbie.
1. Revolutionary failed
2. i did temp root + rumrunner - failed (image attached)
I wonder if my device was not made on this earth or something. Just simply soff. Also dont know if i cant install a JB rom on this without soff safely.
Click to expand...
Click to collapse
What firmware and hboot do you have?

My rom is gingerbread stock version 1.52.xxxx and hboot is 1.18.0000

rajdeeprath said:
My rom is gingerbread stock version 1.52.xxxx and hboot is 1.18.0000
Click to expand...
Click to collapse
do you have sdk tools installed?(adb/fastboot)
also check if usb debugging mode is ticked

oh! hello again hope you are great.
yes i have adb setup properly. i do android dev so all development tools are setup properly. htc drivers are installed htc sync has been uninstalled.
i have tried on windows 8 and windows 7 pcs.

rajdeeprath said:
oh! hello again hope you are great.
yes i have adb setup properly. i do android dev so all development tools are setup properly. htc drivers are installed htc sync has been uninstalled.
i have tried on windows 8 and windows 7 pcs.
Click to expand...
Click to collapse
if revolutionary.io method doesn't work then try to update officially
see this thread
http://forum.xda-developers.com/showthread.php?t=1672425
then try with juopunutbear or rumrunner method again

rajdeeprath said:
My rom is gingerbread stock version 1.52.xxxx and hboot is 1.18.0000
Click to expand...
Click to collapse
One thing you could do is:
- get your phone updated to ICS (OTA over device settings) to get the latest firmware/hboot on it
- HTC Dev unlock your device (nothing complicated, you need to have fastboot running)
- Install/flash latest 4ext recovery (once more via fastboot) and enable smart flash option
Now in recovery with updated firmware/hboot make a nandroid backup and flash almost every rom you like.
In first place I'd not flash a CM12 rom.

tom0769 said:
One thing you could do is:
- get your phone updated to ICS (OTA over device settings) to get the latest firmware/hboot on it
- HTC Dev unlock your device (nothing complicated, you need to have fastboot running)
- Install/flash latest 4ext recovery (once more via fastboot) and enable smart flash option
Now in recovery with updated firmware/hboot make a nandroid backup and flash almost every rom you like.
In first place I'd not flash a CM12 rom.
Click to expand...
Click to collapse
firstly thank you very much for continuing to show hope. appreciate that. tell me thiss. i have a ota pending which i haven't gone for yet.
4.0 update sense 3.6 system upgrade 3.33.720.6
see attached image.
i never did that cause not everyone on htc blog had a good experience. Should i do that now ? will that help me move forward? will i be able to install android revolution or vipers or cyanogenmod after this? will i be able to soff?
i understand 3.33 is ics firmware ? right? what if i wish to go for jellybean ?
thanks

rajdeeprath said:
firstly thank you very much for continuing to show hope. appreciate that. tell me thiss. i have a ota pending which i haven't gone for yet.
4.0 update sense 3.6 system upgrade 3.33.720.6
see attached image.
i never did that cause not everyone on htc blog had a good experience. Should i do that now ? will that help me move forward? will i be able to install android revolution or vipers or cyanogenmod after this? will i be able to soff?
i understand 3.33 is ics firmware ? right? what if i wish to go for jellybean ?
thanks
Click to expand...
Click to collapse
since you update to ics you will be able to flash every ics/jb/kk/lp custom rom you like

so should i go ahead with the official ics update?

It's up to you.
Might be you're just satisfied with your new ICS firmware.
If you want to go further, unlock and custom recovery is an quite easy step.
For custom rom s-off is not necessarily needed.
Sent from my Sensation using XDA Free mobile app

rajdeeprath said:
so should i go ahead with the official ics update?
Click to expand...
Click to collapse
If you do the update, try again with rumrunner after it has finished.

Thanks. I updated to ICS and did a full factory reset. The device seems to be quiet smooth compared to GB though. The next update i do will be using what you suggested. Without SOFF flashing a custom rom.
When i get there i will message back on this thread. Going to test drive this ICS now for a while.time.