[Q] Need to flash my phone back prior to the recent ota (1.63... doubleshot) - T-Mobile myTouch 4G Slide

I am trying to attempt messing with this type of thing for the first time so noob handling will be required. My reason is simply my phone is a nice wallpaper display three days after the ota from tmobile 1.63.531.2 710rd.
I began by trying to follow:
http://forum.xda-developers.com/showthread.php?t=1505999
To no avail. Of course I noticed afterwards that for some reason it says to turn s-on in the header... exactly the opposite what what I need to flash the phone back to (PG59IMG_Doubleshot_TMOUS_1.28.531.9_Radio_10.48.9007.00U_10.12.9007.07_M2_release_201815_signed.zip) I have had problems with the phone ever since its first ota a year or so ago. With this latest ota the phone is more or less bricked as of the phone using power saver when I went to sleep last night... Wont call or check into the network...no dial tone. Took me 3-4 restarts for it to even show the antenna symbol and the 4g icon in the taskbar.
My phone is set as S-on for now. The only instructions I have found through the search tool relay how to do it to the sensation... I believe that is the mytouch 4g not slide. However I have the slide which is doubleshot. So my question is, is this instruction on http://forum.xda-developers.com/showthread.php?t=1192300 safe to use with the doubleshot since the (T-Mobile branded HTC myTouch 4g Slide ( doubleshot ) Developers Reference) page links to it indirectly. Using the link at the top of the how to S-on after s-off... again the opposite of what I need so I tried following the link at the top of that page " Guide to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on " which takes you to the s-off instruction page for the sensation (Link: http://forum.xda-developers.com/showthread.php?t=1192300 )...I am guessing that it will work and sensation refers to HTC sense, but I don't care to make the mistake of doing it wrong and bricking my phone due to being derp.
I know there is a bit of overdone explanation and redundancy in the addresses I have left here. I am just trying to cover all my bases thanks for the help in advance.
The short and sweet is I need a link by link list with instructions on how to step my phone back for multiple reasons. First the recent OTA more or less broke my phone and I don't want a refurb phone with inferior parts from Assurion...(They were in class action lawsuits for this in the past.) nor do I want to pay 130$ for said replacement. Next from what I just read the 1.63 update has some serious security compromises that are awaiting response from HTC for an update. Basically it gives full accesses to all your data to include your sim and SD card contents to all apps. Regardless of user specified/agreed permissions.

Following ANY routine or procedure for another phone is just too dangerous & will never work anyway. The bad part being you may very well create a brick in the process. If you have the MT4G SLIDE, this is where you will get all that you need so don't even consider other threads.
Since you've done the OTA & are sitting at Hboot 1.63.XXX now you will HAVE to get S-Off before you can go back to your previous Hboot. To DO that you will have to follow the instructions HERE.
If all you are wanting to do is start flashing ROMs, then the instructions you need are HERE.
Keep us informed & we'll try to help if you need it. Good Luck!

WeekendsR2Short said:
Following ANY routine or procedure for another phone is just too dangerous & will never work anyway. The bad part being you may very well create a brick in the process. If you have the MT4G SLIDE, this is where you will get all that you need so don't even consider other threads.
Since you've done the OTA & are sitting at Hboot 1.63.XXX now you will HAVE to get S-Off before you can go back to your previous Hboot. To DO that you will have to follow the instructions HERE.
If all you are wanting to do is start flashing ROMs, then the instructions you need are HERE.
Keep us informed & we'll try to help if you need it. Good Luck!
Click to expand...
Click to collapse
Thanks for the hasty post reply any other suggestions...I have win7ult 64bit. Or will will juopunutbutter work even though they have the below disclaimer?
"Supported Operating Systems:
We only support Windows 7 32bit or Ubuntu 12.04 (and newer) 32bit, you may use a LiveCD if you have the wrong OS installed natively. Win XP 32bit might work for you but we do not support it as we did not test on it."
Also, this, "Be on the Stock RUU and be rooted (have superuser flashed). No other ROMs are supported, Fresh ROM will not work regardless of what you have read elsewhere."
-I am not rooted. Which is something else I want to accomplish so I can set up firewalls that block certain things.
Oh btw provided I can get this phone working again I am also going to attempt to reflash my older mytouch 3g... back to original as well that thing worked better than any of the current phones for my purposes before it got the update prior to the 2.2.1... the original update didn't work with adobe which is fine with me, people need to move on from adobe's garbage anyway. Specifically with the old mytough 3g though that really did add functionality at the sacrifice of sanity since it slowed the phone down so much. On that note though I may just put on a custom if I can get comfortable with this stuff. The last time I looked at a pc this hard was back in win98se when you had to know how to do tricks to make it faster like modifying available rame to twice as much above and below physical ram and a few other tweeks I have long forgotten.
That brings me to another question. If I go custom rom and unlocked this looming threat of brick is weighing in on me. If a phone is bricked is it possible to recover using some of the same tools that bricked it in the first place... flash install original rom as a fix? Just trying to see how much margin of error I have to work with.
Thanks again.
PS who do we talk to about backing off all the java on the site since it is so compromised right now? This sight has more java permissions than most sights of ill reput... though I have been reading these forums off and on for a while so I trust it more than most with this much tracking. I doubt patch 11 actually fixed the issue...since the day before they said it would take two years or more to actually resolve the java zero day exploit.

You should be fine with your pc, I used a 64bit win7 too. If you're worried dual boot linux.
Your my touch 3g is rooted diferentley, go to that forum for details, its not true radio soff but its close enough.
If you brick it its dead, depending how it was bricked jtag could bring it back to life or this phone is part of the unbricking project which will fix some other bricks. Problem is people use brick as a term that means a whole lot of things so its hard to answer. Usually a brick is forever dead, most people don't actually brick their phone though and usually have to be neglecting things to do it.
As for java... just read up on a bunch of trustworthy places for more info and understanding
Sent from my HTC Vision using xda premium

I'm afraid I just don't know about Win 7 64bit and how it will react but I'm sure there has to be a person or two around with experience concerning that OS. It may very well work fine. I CAN tell you that the "wire trick" (junoptobear?) will work fine on MikTouch because that's what I used. It's a stripped down GB stock ROM which is all you're really looking for. Why....I don't know.
As far as bricking goes, there's not a GREAT deal to worry about as long as you follow all instructions to a tee. You REALLY don't have to even have S-Off to flash ROMs as you read in that link. You just need to flash the kernel after you flash the ROM. It WILL limit a few things you can do but not ROM flashing.
When it comes to rescueing a bricked device though, there are only a very few instances that can be done as far as I know. But I'm no developer either. But if you can make it to your bootloader and/or recovery you not bricked. It may be a hardware of software issue but most of the time you can come back from those.
As far as the Java issue you spoke of goes, you may be able to get an answer to that one by PM'ing one of our moderators or admins.

I want to step it back to previous versions because they worked better...primarily the first version... Also, I am not seeing a guide that refers to doing it to the 1.63 patch. keyboard hasn't swyped right since the first ota update. Also my intent is to root an older version so I can remove crapware like dt sync, friend stream, kidzone, tmobile mall, tmobile tv, tmobile setup, telenav gps, and zinio reader.

X-Lander said:
I want to step it back to previous versions because they worked better...primarily the first version... Also, I am not seeing a guide that refers to doing it to the 1.63 patch. keyboard hasn't swyped right since the first ota update. Also my intent is to root an older version so I can remove crapware like dt sync, friend stream, kidzone, tmobile mall, tmobile tv, tmobile setup, telenav gps, and zinio reader.
Click to expand...
Click to collapse
It's a simple flashing process but you HAVE to achieve S-Off first with the "Wire Trick". You can flash it forward without S-Off but not backwards. Does it work at all or is it just frozen to some point in the boot process? Can you access your SDcard? Can you boot to Hboot & recovery? These are a couple of things you will have to be able to do to go forward if I understand you correctly.

Related

[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.

[Q] What exactly do I need to start changing around roms

Hi folks.
You'll have to excuse me, as I know next to nothing about putting roms and whatnot into my phone - but I am super excited about being able to learn how, etc.
I'm currently using a totally stock and normal HTC Sensation 4G and have been since roughly the time it came out with my carrier. The phone has started being... weird, so I'm looking to change things around with it.
Anyways - I've been looking around the site and trying to find what exactly is the best starting point for somebody with absolutely no experience.
I've seen some noob threads here and there, but I'm not sure if they're leading me to readying my phone to throw no a new rom. Is there just some sort of state to put my phone into and then be able to flash whatever rom is available for it?
This is what I started looking at but I'm not sure if this a good jump off or not to ready my phone for fun changes.
Thanks for being patient with me on this.
Read this guide: http://forum.xda-developers.com/showthread.php?t=1192300
Basically, you need to S-OFF your phone, and install a new recovery. Then you can flash new roms from your new recovery.
Use the Revolutionary method in the guide to unlock your phone. Install the Clockworkmod Recovery, and Super CID if you want. That just means that you'll be able to flash a rom meant for *any* carrier, not just your own.
That's it.
59seconds said:
Read this guide: http://forum.xda-developers.com/showthread.php?t=1192300
Basically, you need to S-OFF your phone, and install a new recovery. Then you can flash new roms from your new recovery.
Use the Revolutionary method in the guide to unlock your phone. Install the Clockworkmod Recovery, and Super CID if you want. That just means that you'll be able to flash a rom meant for *any* carrier, not just your own.
That's it.
Click to expand...
Click to collapse
Thanks!
That's exactly what I needed. I plan on digging around when I get home.
Good luck. Just remember to read everything all the way through before you do anything, and make sure that you understand all of the steps. Most of the problems that people have is because they just don't read the information/guides.
59seconds said:
Good luck. Just remember to read everything all the way through before you do anything, and make sure that you understand all of the steps. Most of the problems that people have is because they just don't read the information/guides.
Click to expand...
Click to collapse
Fair advice for nearly anything!
Question about doing all this...
Do I have to have my phone connected to my computer? Or is this done primarily through the phone?
You'll need to transfer over some files. Super CID requires you to run commands to your phone from your computer, but that's it. It's definitely worth it to have fastboot and adb running on your computer in case you need it.
59seconds said:
You'll need to transfer over some files. Super CID requires you to run commands to your phone from your computer, but that's it. It's definitely worth it to have fastboot and adb running on your computer in case you need it.
Click to expand...
Click to collapse
Great! I will keep that in mind for when I'm there!
Is this generally a long winded process?
Nah The first time is a bit of work since you have to S-OFF your phone and install a recovery. But it's a breeze after that. So many people have done it and the xda forums are very helpful. I followed that guide the first time and had zero problems.
So, hopefully somebody will have a bit of an idea what to do here...
First things first. I'm doing this all through a bootcamp-esque program from my Macbook - and currently on Windows 7, as there's only Windows and Linux available for the Revolutionary method.
I've downloaded the program. Opened it into a folder, etc. Turned on USB debugging and done everything else the tutorial has mentioned.
Has anybody had similar issues before?
speps said:
Hi folks.
You'll have to excuse me, as I know next to nothing about putting roms and whatnot into my phone - but I am super excited about being able to learn how, etc.
I'm currently using a totally stock and normal HTC Sensation 4G and have been since roughly the time it came out with my carrier. The phone has started being... weird, so I'm looking to change things around with it.
Anyways - I've been looking around the site and trying to find what exactly is the best starting point for somebody with absolutely no experience.
I've seen some noob threads here and there, but I'm not sure if they're leading me to readying my phone to throw no a new rom. Is there just some sort of state to put my phone into and then be able to flash whatever rom is available for it?
This is what I started looking at but I'm not sure if this a good jump off or not to ready my phone for fun changes.
Thanks for being patient with me on this.
Click to expand...
Click to collapse
You mentioned the phone being "weird", in what way is it weird? If this turns out to be a hardware issue or something that requires you to send the phone back to the manufacturer, rooting the phone can void your warranty (if you have any warranty left).
Please keep this in mind prior to rooting your phone. There is a way to flash your phone back to stock and return S-ON but from what I hear it is a little risky and there is a chance of bricking your phone while doing it (as with any part of the rooting process).
When following directions for rooting, I would advise you to read the whole instructions list first to ensure you have an understanding of the whole process, so you don't get stuck at any steps. Make sure you follow the guides exactly as well.
Never heard of anyone doing this through bootcamp on a MAC, but as with any compatability issues, if you have any strange issues with any of the steps it is best to use a native Windows or Linux machine to perform the rooting process.
I have never had any issues with any rooting process, for my SGS and Sensation XE using a Windows 7 64bit computer.
rickadlee said:
You mentioned the phone being "weird", in what way is it weird? If this turns out to be a hardware issue or something that requires you to send the phone back to the manufacturer, rooting the phone can void your warranty (if you have any warranty left).
Please keep this in mind prior to rooting your phone. There is a way to flash your phone back to stock and return S-ON but from what I hear it is a little risky and there is a chance of bricking your phone while doing it (as with any part of the rooting process).
When following directions for rooting, I would advise you to read the whole instructions list first to ensure you have an understanding of the whole process, so you don't get stuck at any steps. Make sure you follow the guides exactly as well.
Never heard of anyone doing this through bootcamp on a MAC, but as with any compatability issues, if you have any strange issues with any of the steps it is best to use a native Windows or Linux machine to perform the rooting process.
I have never had any issues with any rooting process, for my SGS and Sensation XE using a Windows 7 64bit computer.
Click to expand...
Click to collapse
It's been doing a lot of the issues listed here - plus, the battery life is just absolute crap. I've ordered new batteries for it (the 1900mAh Anker ones people here discussed before) and taken a few other steps to try and make it work in my favour a bit more.
I was able to almost complete the S-Off process last night, although I hit a brick wall as it just continued on the "Zerging root" while using Revolutionary. Damn.
I may try again when I get home.
One thing NO ONE ever points you to do but is, in my mind, the most important thing is to try a make sure there is an RUU available for your current ROM.
An RUU (ROM Upgrade Utility) is a complete ROM from HTC which will restore your phone to stock should you need to send it back for a warranty claim.
To check for an RUU, you first need to know your current ROM version that your phone came with. Go to Settings>About phone>Software information and make a note of the 'Software version' e.g. 1.50.401.3
Once you have that, go here and try to find a file name matching the version:
http://forum.xda-developers.com/showthread.php?t=1074559
If you find one, download it and keep it safe
EddyOS said:
One thing NO ONE ever points you to do but is, in my mind, the most important thing is to try a make sure there is an RUU available for your current ROM.
An RUU (ROM Upgrade Utility) is a complete ROM from HTC which will restore your phone to stock should you need to send it back for a warranty claim.
To check for an RUU, you first need to know your current ROM version that your phone came with. Go to Settings>About phone>Software information and make a note of the 'Software version' e.g. 1.50.401.3
Once you have that, go here and try to find a file name matching the version:
http://forum.xda-developers.com/showthread.php?t=1074559
If you find one, download it and keep it safe
Click to expand...
Click to collapse
I'll be sure to do that. Thanks!
Would anybody know why I keep getting stuck at the "zerging root.." portion?
Unless it usually takes a few minutes, it seems to just... hang.
As far as I can tell, everything else is set up correctly for this to work.

SOLVED - OTA - update downloads but fails to install - Rev & Root

Nobody could help but finally i managed to take the risk and it paid off thankfully.
It is the easiest way to unroot, remove superuser, revolutionary and to restore hboot back to normal and S-On again, to get official updates including ICS.
Download the attachment "usmanxhmed.rar", it has Android Flasher and FlashENGHBOOT.
Attach your phone to PC with USB cable, make sure you have HTC fastboot drivers installed.
Open Android Flasher and select bootloader and browse to the file FlashENGHBOOT which you downloaded in file "usmanxhmed.rar", boot phone into fastboot and click flash.
It will remove REVOLUTIONARY **** from the phone.
Now download your specific RUU from this link http://www.filefactory.com/f/c64d333a2755a421/ i was unsure which is my RUU for the phone as i bought it second hand, my phone was unbranded, i matched the software version and radio version in my software information of the phone and downloaded the specific RUU.
After flashing the RUU my Desire S became factory fresh and back to S - ON and updated my phone with Android 2.3.5 and Sense 3 and hopefully/ may be i will get ICS in future as well
--------------------------------------------
ORIGINAL POST
(Please Don't tell me to search the forums, as my situation is bit different and i am newbie here)
I have Desire S (I bought used from Market and sadly it has S-off with Revolutionary and Superuser App installed)
Problem is that, i get notification of update 1.47.401 and it gets download, when it tried to install after reboot i see android icon with triangle exclamation mark.
Now my situation is different because i have a feeling despite S-off i am on official rom which is 2.3.3, so i want to jump to 2.3.5 and later on official ICS
So i think if i just remove revolutionary and root and S-off to S-On may be, i may able to install the update as i already have official or stock rom in my phone i think.
I have android 2.3.3
software number 1.28.401
Update that i download is 1.47.401
Revolutionary S 0ff
hboot 6.98
I dont even know which hboot i need to get this update to inslall or what i need to do? is there any caring guy who can help beside just taunting as i have seen here?
Forget update, simply flash a custom ROM
Would also suggest that you out ENG boot loader over the alpha Rex one
See INDEX (in my signature) for links
Swyped from my DesireS
@poster
for u to conviniently use htc OTA updates u need to S-ON again
or just forget it and install custom ROMs like Ben just said
cheers
Thanks both of you for replying, its the beauty of God that we all have different mind sets, unlike most guys here, i am a man who would prefer official/stock rom and would prefer to have official updates instead of amateur ROM. May be because
- It causes far less phones to brick
- Manufacturer understands device better then amateur developers
- i see no special advantage of custom ROM over stock rom
- i can live life without root and s off as i can have more secure android experience
- Manufacturer invests may be billions to understand the best combination of hardware and software may be that's they don't usually port gingerbread on g1.
- Official update can remove few bugs where as most custom ROMs have bugs as we often read in almost all the posts here thst camera or wifi or tethering is not working yet and so on
- Customs ROMs can over heat the hardware and can damage it as they lack proper hardware knowledge, training and research.
There are endless points due to which some poeple like to stay stock, unlike most here and by above points i am not saying lovers of custom that they are wrong or not demotivating them at all, just sharing my own thoughts due to which i think i better have stock rom in normal circumstances.
So is there any (expert) guy who can help me to resolve my problem instead of telling me to get custom ROM, which i know my self, and which i said i don't want. Its ok not having 2.3.5 but i will be unlucky not to have official ICS if it gets available on my phone.
Wow! where to start...I'll leave that for now (although you may wish to re-consider your use of the word amateur as its rather insulting).
I believe that you need to flash the (98.2) ENG hboot over your Revolutionay (6.98).
See previous post of instructions here
You need to know if the phone is branded or un-branded and from which country/region its from in order to download the correct RUU.
I'd then suggest that you download your stock RUU and run that from the PC which will reset your recovery to stock and un-root you phone, you should then be in a position to request an OTA.
@usmanxhmed
A simple question comes to my mind after reading your post: why are you posting your issue here instead asking HTC support? I hope they will be as half friendly as Ben is. Thanks to God of course
Sent from my HTC Desire S
Well? support from HTC? firstly they may not bother to reply being HTC, not the best in customer service like any big company, secondly my phone is rooted, so its not there fault for them to fix it, thirdly here i have common guys just like me, may be someone with situation just like me.
Yeah use of word Amateur sounds rude here, bit insulting too, but if we are willing to face the reality, that is truth, they are not developing to earn living, they are not manufacturing devices giving warranties, instead saving there soul in every post we are not responsible, as they are greatly unsure about the validity of everything they are teaching/guiding here and on and on and on, so all of this must be categorized as Amateur.
See the people of Revolutionary? after ruining/screwing the warranty and OTA of all phones, they are unable to give simple guide to undo there mess? Most procedures here are with warnings and posts users that they bricked there devices? With custom ROMs no processor is converted from single core to dual y magic so i should want custom ROM so badly.
It may work, it may brick phone, my screen stuck there, it stuck here, camera not working, wifi not working, lagging? For a poor guy like me who can't change phone weekly these things are somewhat burden. Nokia/HTC/Apple will give one click software updates and they will not tell you do it on your own risk, you may brick your phone, they online tell you if you disconnect cable than your device may not work, it does not mean they are brick prove, but more reliable thats why they are professional and brothers here are amateurs.
I don't know, i just bought used phone with revolutionary root and i can't install update even after downloading it, i don't know my phone belongs to which compnay, which RUU i need, which hboot i need out of 20 out there, single mistake can brick my phone without even letting it fall on ground from my hand, let me sleep and live with 2.3.3
usmanxhmed said:
Well? support from HTC? firstly they may not bother to reply being HTC, not the best in customer service like any big company, secondly my phone is rooted, so its not there fault for them to fix it, thirdly here i have common guys just like me, may be someone with situation just like me.
Yeah use of word Amateur sounds rude here, bit insulting too, but if we are willing to face the reality, that is truth, they are not developing to earn living, they are not manufacturing devices giving warranties, instead saving there soul in every post we are not responsible, as they are greatly unsure about the validity of everything they are teaching/guiding here and on and on and on, so all of this must be categorized as Amateur.
See the people of Revolutionary? after ruining/screwing the warranty and OTA of all phones, they are unable to give simple guide to undo there mess? Most procedures here are with warnings and posts users that they bricked there devices? With custom ROMs no processor is converted from single core to dual y magic so i should want custom ROM so badly.
It may work, it may brick phone, my screen stuck there, it stuck here, camera not working, wifi not working, lagging? For a poor guy like me who can't change phone weekly these things are somewhat burden. Nokia/HTC/Apple will give one click software updates and they will not tell you do it on your own risk, you may brick your phone, they online tell you if you disconnect cable than your device may not work, it does not mean they are brick prove, but more reliable thats why they are professional and brothers here are amateurs.
I don't know, i just bought used phone with revolutionary root and i can't install update even after downloading it, i don't know my phone belongs to which compnay, which RUU i need, which hboot i need out of 20 out there, single mistake can brick my phone without even letting it fall on ground from my hand, let me sleep and live with 2.3.3
Click to expand...
Click to collapse
huhu...i dont think that peoples here are amateurs...they've come up with much better custom roms than official one i believe...
I believe this can be quite long and useless discussion. Just to mention some of the devs around ARE working for the big companies.
Anyway back to topic. To restore to stock you will find all the necessary info in the second half of the amateur guide about emmc in my signature. Good luck
Sent from my HTC Desire S
For someone after assistance, I do find you're attitude negative and insulting. The forum is full of various guides and sticky threads which contain most of the information that you require, your problem is not unique and therefore had been solved many times over in the past and therefore is well documented here on the forum.
While you may be correct in that many people here at Xda are either young and starting out or merely interested novices and therefore could be classed as ameteurs
I think that you'll find that the developers of the most popular ROMs are in fact professional programmers who code here, in their spare time for the benefit of others.
Swyped from my DesireS
I have nothing against the love for developing, that people have over here, obviously its a skill, but do let me know they develop for the benefit of whom or i mean what are the benefits of developing to a normal consumer.
Over here i found good guides for revolutionary and rooting but there is no detailed/complete guide to undo the stuff, in fact the most of famous guide to undo now claims that i closed this topic, you can find that forum everywhere here which most people link to me, the guy says he is sick of brick phones so he is taking off the guide.
No guide tells for which stock version which hboot is required, nobody tells which RUU version i need when i don't know my Desire belongs to which country, as i cannot find where to locate it.
The only thing i understand here revolutionary dirt is most painful to undo as i remember i unrooted my xperia x10mini with almost one click with some software like superone by connecting to my PC.
Now i understand what benefits developers are giving to consumers here, which can be
- Loss of warranty
- Plenty of dead phones
- One developer narrates if your phones bricks during my guide and if you will complain from me, i will laugh on you, sure you must
- Robbing you from facility of One Click OTA
- OTA usually remove bugs and adds functionality so you can't have it
- And on and on and on
According to my thoughts, xda developers should be bringing solutions to current problems and limitations, instead of doing above mentioned thing to already working phone, Now i think my Old Symbian phone was better at least i could get OTA just by changing product code in a second with ease.
Anyways thanks for everyone who tried to help and i am sorry for being bit cheeky and playful here.
usmanxhmed said:
I have nothing against the love for developing, that people have over here, obviously its a skill, but do let me know they develop for the benefit of whom or i mean what are the benefits of developing to a normal consumer.
Over here i found good guides for revolutionary and rooting but there is no detailed/complete guide to undo the stuff, in fact the most of famous guide to undo now claims that i closed this topic, you can find that forum everywhere here which most people link to me, the guy says he is sick of brick phones so he is taking off the guide.
No guide tells for which stock version which hboot is required, nobody tells which RUU version i need when i don't know my Desire belongs to which country, as i cannot find where to locate it.
The only thing i understand here revolutionary dirt is most painful to undo as i remember i unrooted my xperia x10mini with almost one click with some software like superone by connecting to my PC.
Now i understand what benefits developers are giving to consumers here, which can be
- Loss of warranty
- Plenty of dead phones
- One developer narrates if your phones bricks during my guide and if you will complain from me, i will laugh on you, sure you must
- Robbing you from facility of One Click OTA
- OTA usually remove bugs and adds functionality so you can't have it
- And on and on and on
According to my thoughts, xda developers should be bringing solutions to current problems and limitations, instead of doing above mentioned thing to already working phone, Now i think my Old Symbian phone was better at least i could get OTA just by changing product code in a second with ease.
Anyways thanks for everyone who tried to help and i am sorry for being bit cheeky and playful here.
Click to expand...
Click to collapse
Buddy I hope you get well soon...really bad way to ask for help and insult people here....if you have so many problems with you phone please return it and never buy a HTC phone and before you say something about other have a look at their profile and I belive this is the most friendly forum and no other forum would ever tolerate what ever you have posted....
Anyways all the best....
Risk it to get the biscut...
Sent from my HTC Desire S using XDA
usmanxhmed said:
but do let me know they develop for the benefit of whom or i mean what are the benefits of developing to a normal consumer.
Click to expand...
Click to collapse
Let me see....
- Overall (way) faster phone
- Batterylife that doubles or more (this alone is worth a custom rom!)
- OTA updates are still added to the custom roms, so no benefit for you
- Sometimes bugs that the 'great HTC developers' left in are removed
- Lot`s of 'under the hood' tweaks that make your phone faster, safer and better
- Garbage from HTC that is removed
- Nice tweaks in screenbrightness, wakeup with volume keys etc. etc.
Since you are already s-off with revolutionary i can`t see why you want to take the hard and tricky way to go back to s-on. (The OTA reason is not legit and your warranty is already gone)
Just fyi, there are also 100% stock untweaked up-to-date roms you can flash with ClockWorkMod Recovery...
usmanxhmed said:
(Please Don't tell me to search the forums, as my situation is bit different and i am newbie here)
I have Desire S (I bought used from Market and sadly it has S-off with Revolutionary and Superuser App installed)
Click to expand...
Click to collapse
Hi,
I can understand you. I was thinking nearly same like you when I bought my DS. After 6-7 months later of purchase my DS, I decided to S-OFF and flash a custom rom. First I flashed Endymion (than 2-3 roms too but used them for 1-2 hours) and I started to like my DS again. It took months for Sense 3 update and we're still waiting for ICS for ages. I can understand about your worries but XDA's Dev community working harder than manufacturer's devs. Getting new updates very quickly, and there lots of ICS roms by devs. So you should respect them.
You can flash Eng Hboot (this topic) then download official stock 2.10.401.8 rom from here. Follow instructions after connect your DS to PC
Thanks for helping and being kind, my rude language was partially explained by my current rude life may be and thanks for tolerating me. Custom ROMs may be cool, but don't you guys think the % of bricked phones are more here? for example if i download and install a ROM from clockwork by following instructions, can i be next to sure if i will boot up next time?
I may have to have it the hard way or i will have to ignore android versions and just use the phone for the sake of phone like an Old Man or a Girl.
Yet i hope, men at Revolutionary or at XDA could bring one easy and assured way to undo revolutionary and its root.

[ruu] [stock] att 2.20 ota

Here is the RUU for the OTA ATT 2.20 update.
Warning if you use this RUU you cannot go back to a lower RUU ( 1.85, etc ) or lower firmware as the HbOOTS are different! This is more for us that have already done the update. This will help us get back to stock if something goes foul.
There is no benefit for anyone to run this RUU as of now until root, etc is sorted out. Like I said for now mainly for us that already updated.
Thanks to scrolser for the link and DvineLord for initial find
Issues:*
1. If you update you will get a newer hboot, you may not be able to use other older ruu's such as 1.85, etc. Recommend immediately making a backup once rooted, unlocked, etc.*
2. Updating results in boot.IMG from custom roms not being flashed again. Have to flash the boot.IMG of custom Rom in fastboot as before.*
3. Radio.img will not flash on new hboot either must be done in fastboot same as boot.img.
HTC One X for AT&T ROM Update | 8.02.2012
Starting August 2nd 2012, HTC will be rolling out a system update for the HTC One X.
This update will only be available for AT&T HTC One X customers and will be sent to the device over the air. Once the release is ready, users will receive a notification on their device advising them of this update and provide instructions to receive and install it. Users can proactively check for this update by going to Home > All Apps > Settings > AT&T Software Update > Check for updates.
As an alternative solution, the system update can be downloaded to a PC and manually applied to the device. See the section at the bottom of these instructions for more information.
This system update includes:
New features:
NFC Capabilities
Additional content added to HTC Hub
Third party music applications accessible from the Car application.
Fixes/Updates:
Wi-Fi connectivity fixes
Improved Bluetooth automobile compatibility
3G/4G connectivity improvements
HTC Sense fixes
Contacts synchronization fix
Network time fix (clock displays 30 minutes off)
WARNING: During the upgrade process the device will reboot multiple times and show software upgrade screens. Do not remove the battery as this will stop the update and your device may be rendered inoperable!
Getting Started
Before you proceed with the update, make sure you have done the following:
Set aside approximately 20 minutes to allow the device to update, possibly longer based on Wi-Fi network speed
Connect the device to a charger
Ensure the battery is charged to at least 30%
Connect to a stable Wi-Fi network to download the software file.
Installation instructions
To manually perform the update, follow these steps below:
From the Home screen, tap All apps and then tap Settings.
Tap AT&T Software Update.
Tap Check for updates.
Tap OK to download the update.
After you select your method of download, you will be prompted with a Wi-Fi or Data fee warning message. If this is acceptable, tap OK to start the upgrade process.
Status of the download can be viewed in the Notifications pull down.
Once the download is complete, the user will be prompted to install from the Notifications pull down. Tap the System update to begin the upgrade process.
Tap OK to begin the update process to software version 2.20.502.7.
Device will reboot and begin installation. Users will not be able to use their device during the installation process (approximately 10 minutes).
System update complete. Tap OK to continue
Manual system update instructions:
If you are outside of AT&T/Wi-Fi coverage, or the update is not found, you may perform a manual system update.
Performing the system update manually will delete all information from the device. Ensure all information is backed up before proceeding. See the Help & How To section of this website for more information on backing up your device contents.
Performing the ROM Update:
Download and save the HTC One X™ for AT&T ROM update to your PC.
Connect your device to your PC via the supplied USB cable. NOTE: You must have HTC Sync Manager installed on your PC in order to run the update.
NOTE: If you do not have HTC Sync Manager installed already, you may download the software from http://www.htc.com/us/support/.
Ensure the device is properly recognized on the PC, then locate the HTC One X™ for AT&T ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
Follow all of the system update wizard instructions shown on your PC.
Once the update is complete, click Finish in the Wizard and the device will reboot.
Once the device reboots, the initial setup wizard will appear.
Once the initial setup process is complete, the device is ready for use.
Download
portions of this post copyright HTC 2012. All rights reserved to them.
kewl
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
.
Third party music applications accessible from the Car application.
Click to expand...
Click to collapse
WOOT.
Thank you for not using File Factory haha
"NFC capabilities"????
Sent from my HTC One X
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
XsMagical said:
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
Click to expand...
Click to collapse
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
slippers67 said:
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
Click to expand...
Click to collapse
yeah if you know what you're doing, but damn I'm going to miss the one stop flashing we used to have.
eraste said:
Here is the RUU for the OTA ATT 2.20 update.
Warning if you use this RUU you cannot go back to a lower RUU ( 1.85, etc ) or lower firmware as the HbOOTS are different! This is more for us that have already done the update. This will help us get back to stock if something goes foul.
There is no benefit for anyone to run this RUU as of now until root, etc is sorted out. Like I said for now mainly for us that already updated.
Thanks to scrolser for the link and DvineLord for initial find
Click to expand...
Click to collapse
I thought that was good?
XsMagical said:
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
Click to expand...
Click to collapse
This was to be helpful for us that already did OTA. I agree tho if one isint literate in the world of android wait to use this until all the things above are worked out.
scribed on my 2.20 HOX
slippers67 said:
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
Click to expand...
Click to collapse
yea thats fine if you know how, but why make everyones life harder when this upgrade is older then the asia 2.23.
its just going to make a lot of un needed posts to developers asking why the rom dont boot and so on. Run this ruu and it will cause more problems then anyone needs. As well as set you back from any S-Off development.
But that is my warning. Just saying, i cant see it from my house, my phone flashes
kernels just fine and always will. One Stop flashing.
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
gunnyman said:
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
Click to expand...
Click to collapse
I know i am, Ive been down this road several times in the past and i know what to flash and not to flash. That being said, I,m just trying to warn anyone that thinks the ruu is better then the rom alone...
gunnyman said:
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
Click to expand...
Click to collapse
I prefer ATT based things, not racist lol just prefer the ATT stuff it works better for me as I'm in America. I would like to think root, mount points, etc will be available so everyone can benefit. This is important because of your statement. Anyone needing a new phone now for some reason be it broken, screen etc will get this build. Not 1.85 anymore. I definitely don't think it needs to be backseated just because asia is 2.23. Us in America will be screwed as new phones ship with 2.20 not 2.23. I have faith lol who knows new hboot may have a flaw that finally allows s off.
scribed on my 2.20 HOX
To be honest I jumped on the update. It fixed a lot of the issues I had with 4.0.3 sense. I still have my unlock and I'm rooted. These times are like mini vacations from flashing. I also happen to have confidence in you devs, and also know that sooner or later (probably later) HTC will release source for this updated kernel and the dev will kick off again.
Although I don't envy you devs having to deal with people who don't read.
Thanks eraste for posting this as well as the guide for updating safely.
Sent from my HTC One X using Tapatalk 2
Nrod0784 said:
To be honest I jumped on the update. It fixed a lot of the issues I had with 4.0.3 sense. I still have my unlock and I'm rooted. These times are like mini vacations from flashing. I also happen to have confidence in you devs, and also know that sooner or later (probably later) HTC will release source for this updated kernel and the dev will kick off again.
Although I don't envy you devs having to deal with people who don't read.
Thanks eraste for posting this as well as the guide for updating safely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Anytime
scribed on my 2.20 HOX
eraste said:
I prefer ATT based things, not racist lol just prefer the ATT stuff it works better for me as I'm in America. I would like to think root, mount points, etc will be available so everyone can benefit. This is important because of your statement. Anyone needing a new phone now for some reason be it broken, screen etc will get this build. Not 1.85 anymore. I definitely don't think it needs to be backseated just because asia is 2.23. Us in America will be screwed as new phones ship with 2.20 not 2.23. I have faith lol who knows new hboot may have a flaw that finally allows s off.
scribed on my 2.20 HOX
Click to expand...
Click to collapse
Well I'm in america too! but i thought a warning would be nice, But what do i know
i think his warning was sufficient enough. he stated no benefits of flashing. unless you already did it prior. plus there are other threads who state warnings as well. people dont care or dont read and will flash anyway :laugh:
not taking sides i see what people do here that go against there better judgments or even when told not too :laugh:
Drop box just suspended my public links for excessive traffic lol lame. Changing hosts now sorry guys.
eraste said:
Drop box just suspended my public links for excessive traffic lol lame. Changing hosts now sorry guys.
Click to expand...
Click to collapse
whoa and i just downloaded too lol. just in time add to the RUU collection lol

[Q] tried many things, now need help for daughters phone

Hi Guys,
I'm trying to get a 'stable' rom for a phone I've given to my daughter (Evita / Telstra one XL).
I've tried a heap of things, tried to s-off, change radio files etc... Anyway, current status is that it's been unlocked, s-on, and I have twrp.. I'm using KickDroid XL v4.0.0 ROM, looks great, but the phone keeps on rebooting... Also loosing 3G signal, so have to reboot it quite a few times a day to resolve. (tired another rom, same problem, loss of 3g signal and multiple reboots during the day)
I'm sure it's got to do with the radio file, but can't seem to fix that. I've read 'so much!' information, but really confused now. I've tried to supercid it, unsuccessfully, tried to find the all-in-one toolking (bt it looks like its been removed)..
So, this is what I have when I boot it:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.11.0000
RADIO-0.23a.32.09.29
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7 2012,13:10:34
TWRP recovery
2.6.3.0
htc one xl
Evita​
Any help in how to (or if I should) get the radio/hboot up to hopefully resolve the loss of 3G?
I'm no expert, but not that dumb either. I follow instructions from the start, but most of the time it gets stuck half way (ie, when doing supercid, boots to the HTC logo, but won't go any further)..
Any help really appreciated.
The problem is not that the ROM is unstable, the ROM is perfectly stable if you meet the requirements. The problem is your current firmware version. You need to update to the 2.15 firmware package. It does state that very clearly in the "You Need" section in the beginning of the Kickdroid thread. Please search/research properly before posting in future, it's part of the XDA rules. This issue has been discussed extensively in every single Sense 5 ROM thread, plus this is probably the 100th thread like this in our Q&A section.
Sent from my Evita
Why are you even giving your daughter a rooted/modded phone at all? Unless she has an understanding of what root means, its not a good idea. Does she even need anything except a bone stock phone?
thanks timmaaa, I appreciate you taking the time out to reply.
I'll do some more checking on firmware 2.15... I've honestly read about 5 hours last weekend on various threads... some lead to dead ends (it toolbox), some I can't get to work (supercid)... I tried this a couple of months ago, and almost bricked it, but managed to get twrp working...
Redpoint73, are you asking why give her a phone, or why a rooted phone? The answer to the first one is that she is 11, and catches the bus to and from school. The phone is used in an emergency. I've rooted it to give her some new features, and because it was locked with Telstra and that is not the carrier we are using anymore (much cheaper options here than Telstra), so I needed to get rid of the firmware...
Overall, I appreciate any help. I actually run 5 forums (car related), and I fully understand noob's coming on and asking the same question week after week. Our forums have a lot less posts than this one (< 200,000), but we still have members, week in-week out, answering the same questions because they like to help, and because sometimes there is too much information out there to sift through, especially when somebody is willing to point you in the right direction with a friendly smile
duplicate post, (sorry, hit save twice!)
jnrdavo said:
Redpoint73, are you asking why give her a phone, or why a rooted phone? The answer to the first one is that she is 11, and catches the bus to and from school. The phone is used in an emergency. I've rooted it to give her some new features, and because it was locked with Telstra and that is not the carrier we are using anymore (much cheaper options here than Telstra), so I needed to get rid of the firmware...
Click to expand...
Click to collapse
Its pretty clear from my post that it was root/mod that I was referring to. Root has nothing to do with Subsidy (SIM) Lock, and the firmware has little to do with the carrier you are on (I've been using the German T-Mobile stock ROM for a while now, despite being on AT&T).
Of course its up to you to decide what you do with the phone. But you should consider (if you haven't already) the security risk of giving a rooted device to a user that knows little or nothing about such things. Even more so for s-off, which is necessary for the solution that timmaaa suggested.
My question has less to do with exactly "who" the phone is for. But more to the point, when people come on here saying they are modding the phone for "someone else" (be it mom, third cousin, or whatever), if that person isn't doing it for themselves, its pretty questionable whether they need such mods at all.
ok, thanks redpoint73..
I understand where you are coming from, and appreciate your comments.
Now, anybody else like to point me in the right direction (to a link to get the latest firmware, or a compatible one working)?
jnrdavo said:
Now, anybody else like to point me in the right direction (to a link to get the latest firmware, or a compatible one working)?
Click to expand...
Click to collapse
You serious? timmaaa already told you where to find it.
Since I'm feeling charitable right now, here it is, complete with step-by-step instructions (only need to follow Posts #2 and 4): http://forum.xda-developers.com/showthread.php?t=2485865
The original thread where Turge posted his firmware package (see under "OPTIONAL", s-off is required before doing this): http://forum.xda-developers.com/showpost.php?p=45072132&postcount=1
Or just install the Beastmode kernel (S-off not required): http://forum.xda-developers.com/showthread.php?t=2165880
thanks mate. I appreciate the charity, I really do I'm trying not to be a nob.. I'm actually having another go this morning... I've got win 8.1 (yeah, I know) so trying to get the latest driver to work is a pain.... Just trying x_factory windows, backups up twice, but then doesn't run the next command (to change CID)...
Anyway, thanks again. I'll persist on...

Categories

Resources