Develop Bugs

[Q] Need help getting stock recovery flashed

First thanks for all the great help on this forum...awesome! That said I am a noob with all this so please forgive my ignorance.
Asurion sent me a new phone due to overheating. I had my phone rooted, s-off, with the stock recovery flashed back to receive the OTA upgrade. Now I need to return this phone.
I put back clockworkmod and applied s-on. I downloaded and tried to flash a stock rom according to the 10 minute video put the recovery wouldn't accept it. Long story short I now have a stock rom, s-on, but still have CWM recovery. I can't flash the stock recovery files I've downloaded with s-on and if I apply s-off to do it then I guess I won't be able to apply s-off from a stock recovery.
I downloaded a 2.1 RUU file that is an .exe. I was told to install HTC sync and run it. Either it won't run or I am not doing the right thing with it. (opened HTC sync, plugged in phone, chose HTC sync, got connection, tried to run the .exe. All I got was a brief dos window. Am I supposed to extract files from the .exe and do something with them?
I'm so close. Hoping I'm just being dumb and the solution is easy.
Thanks..............mm

Resolved
Problem solved with the PB13img file provided with Diego Mejia's 2nd video. Worked perfectly. Did not even have to do all the adb pushing of sys files since I never put in the leaked OTA. His file version was just accepted by hboot. Awesome!

[Q] What exactly is meant by 'run the RUU'?

This phrase seems to be one of those everyone knows...well except me. What the heck are the EXACT steps to running an RUU?
I am in fastboot with usb showing...then I attempt to double click on the file on my desktop and get an error about it not being a win32 file. Seriously have searched google for hours and the search here is down.
Anyone got the steps to do this?

[A] What exactly is meant by 'run the RUU'?
RUU = Rom Update Utility
http://www.htc.com/uploadedFiles/Common/Software_Download/Detailed_RUU_Instructions_09232009.pdf
Well if this is all you don't know, you are way ahead of me, sheez.
Now root, get nand unlock, install new custom recovery, new PRI, new radio and Burnt 1.2 and you will be good to go, laughing...

An RUU is a Rom Update Utility. It is a program that you run on your desktop that flashes a new ROM image on your phone. So the phrase "run an RUU" literally means to run an RUU. They are version specific. Meaning it is not a program that can flash any ROM for you. There is a different RUU for every OS version.
What file are you clicking on on your desktop that's giving you an error?

[A] What exactly is meant by 'run the RUU'?
I am not quite sure what you are trying to do, but I do have a suggestion. Take a look at regaw_leinad thread on [GUIDE] How to root Android 2.2 on the EVO 4G. He put this out way before unRevoked 3.21. BTW: This was the method I used to root my 2.2 EVO, worked like a charm. Anyway, it's not about the process he used to root an EVO, it's more about all the steps and what does what that you learn going through the process. May help you achieve whatever it is you are trying to do.
Good Luck
the link: http://forum.xda-developers.com/showthread.php?t=765496&page=45

I am already rooted and running a rooted version of 1.47. I have a file called...RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe.
This was in an attempt to try to get a 'more' stock version of 1.47 on my phone so that then I could accept the OTA.
I have all of the sdk loaded and yes I have that fastboot in same folder as the adb...(if that means anything.)
When the first 2.2 rolled out many many people with rooted phones accepted the OTA and lost root. So I know it is possible to load the OTA when you have a rooted phone but for some reason I am getting an error. (In another thread, but it is an apply patch error?)
So again....does running a RUU mean...1)You boot to recovery, 2) You go to fastboot, 3) You plug in USB, 4) After you see Fastboot USB (and phone shows up in device manager) you double click the RUU
Is that the process?

Since I didn't see it mentioned. But when you run the RUU, you lose root. If you want to run a "closer to stock" ROM then download SteelH's ROM, and flash that through Recovery.

No, running a RUU is running a PROGRAM that does the update for you. Run the RUU right now without connecting your phone, it will tell you the steps.
Don't even worry about accepting the OTA. Flash this PC36IMG file and it will bring you completely current.

Hmmm...ok. Metalhead, I'll re-read your post when I get home and probably go in that direction.
Debugguy, that document was pretty good at showing me what I should be seeing, but now I am wondering if the file I got was a windows file or not...because it doesn't do that at all.
Thanks ya'll.

Something that may help, go to the unRevoked web site, some really good "back to stock" info here, may
give you some ideas.
go here: http://www.unrevoked.com/#evo
select (1) unrevoked3, then more
select (2) unrevoked Forever, then more

Attempted to Update my HBoot version and now have a bricked INC..Help! 10 bucks

I tried to update my Hboot the other day to .92 i believe from .78. Thinking it was as simple as flashing it through bootloader and thats it. I was stuck at the white htc screen for hours so I figured I was screwed. I wiped everything with no luck and then I flashed something so now my HBoot is 0.77.0000 and my Radio is 1.00.03.04.06. I was previously running CM7 nightlies. After flashing whatever zip I did I was trying to reverse what I did by "downgrading" and what I did was delete everything. I cant boot and I also dont have recovery anymore. I can only use Bootloader. PLease any help I can get is appreciated. If u can tell me how to fix this ill make a 10 dollar donation to your paypal. My e-mail is [email protected] if u want me e-mail any information. Thanks a ton

Try the following link.
You may need to get an usb sd card reader. That way you can put the needed files using your pc.
I am sure someone more knowledgeable will come along to help you.
I read somewhere that if you can get to the bootloader, it might have not neen bricked yet.
http://dougpiston.com/?page_id=77

Download this file
http://www.fourty.net/~berzerker/sto....605.1_RUU.zip
Rename it to PB31IMG.zip, put it on the root of your SD card, Boot into the bootloader (hold vol- and pwr) and let it run the update. After it is done you will be back to a stock 2.2.

I forgot to mention in my initial post that I also updated my radio to the newest 2.15 but still had recovery after I did that and after that is when I tried to downgrade everything and lost my recovery. Didnt know if that makes a difference or not. Thanks for the quick replies

Goos3y that link you sent me says 404 not found.

ok there is hope. I am a littl confused though. Do you have recovery?

No i do not have recovery only hboot. I am using my lady's Droid X with my SD card to put any files on the card that I need to.

http://dougpiston.com/?page_id=108 download the PB31IMG.zip put it on the root of the sd card and flash through bootloader as previously stated. Make sure it is named PB31IMG.zip or it wont get recognized. You will loose root and have S on. Thank doug piston for the dl.
sent from my streak7

this is not in the right section but if you can still get into recovery restore a working nandroid back up. after that go to backup and restore>advanced restore and restore your boot image. im pretty sure upgrading you hboot erases your boot image.

EDIT: I saw that someone posted a PB31IMG up earlier. I'd try that one first,
This is for the RUU exe.
An RUU is a program which links to any phone that can get into bootloader, and installs a completely unrooted stock image to your phone. It can be done either by using the linked program (an exe) or getting an ruu version that is a zip and running it on bootloader with a specific filename "PB31IMG.zip"
This tutorial is for the EXE version linked below.
WARNING: I have no idea what happens if this is used on an SLCD incredible.
Therefore, you need to know what kind of screen you have, and I'm no expert on that.
DONT use this RUU if you find out you have an SLCD screen.
I am not sure whether android sdk tools or htc usb drivers are nessesary for the ruu, so if anyone can comment on the necessity of these, i would appreciate it.
Heres what you need:
1. A PC
2. The RUU exe file
3. a cable to connect the PC to your phone
4. The knowledge of whether your phone is an SLCD or not.
Instructions:
1. Hook up your phone to the computer
2. Put the phone into hboot
3. Run the ruu
4. If it messes up at the usb detection thing, keep the phone plugged in, exit the ruu program, and then run it again. It should work then.
At the end of this process you should have a fully functional unrooted froyo incredible.
You dont need to give anyone $10. We all want your phone to work.
The link:
http://forum.xda-developers.com/showthread.php?t=829783&highlight=ruu
Thanks Football!

Hellzya said:
http://dougpiston.com/?page_id=108 download the PB31IMG.zip put it on the root of the sd card and flash through bootloader as previously stated. Make sure it is named PB31IMG.zip or it wont get recognized. You will loose root and have S on. Thank doug piston for the dl.
sent from my streak7
Click to expand...
Click to collapse
You will lose root (easy to get back) but will still be S-off.
You can either use the PB31IMG or the .exe method. Just grab the files off doug piston's website. We've had a lot of problems with SLCD owners grabbing the RUU off youtube and other sites then having a screen that no longer works.

I tried the PB31IMG zip method but in hboot after searching through the file it says no image. I am going to try the RUU now. Do i need to have the android sdk stuff on this computer for the RUU to run correctly? I am using a different laptop, one which does not have the driver files installed that I needed to initially root my INC.?

s197 said:
You will lose root (easy to get back) but will still be S-off.
You can either use the PB31IMG or the .exe method. Just grab the files off doug piston's website. We've had a lot of problems with SLCD owners grabbing the RUU off youtube and other sites then having a screen that no longer works.
Click to expand...
Click to collapse
Unfortunately Marty, its not easy to tell which is amoled and SLCD without having the phone on to verify that its hardware revision is 002 or 003.
002=amoled
003=slcd
If you still have the box i'd recommend looking at it.

I thought you loosed s-off but ok. Did you make sure the PB31IMG.zip was not named .zip.zip?
sent from my streak7

marty454 said:
I tried the PB31IMG zip method but in hboot after searching through the file it says no image. I am going to try the RUU now. Do i need to have the android sdk stuff on this computer for the RUU to run correctly? I am using a different laptop, one which does not have the driver files installed that I needed to initially root my INC.?
Click to expand...
Click to collapse
Well, if you run it without them, and it doesnt work, it wont make anything worse. It just wont work, and then youll know. It probably has nothing to do with the SDK and more to do with HBOOT USB drivers. I would say go for it without any of that.
The most important thing you can know is that your incredible is not bricked. Its totally fixable.
I screwed mine up in precisely the same fashion early on, and used the EXE with good success.

Im positive. I got the phone in august of 10 through verizon. I dont have the box anymore. I have looked into it before and think "think" I have the amoled screen.

marty454 said:
Im positive. I got the phone in august of 10 through verizon. I dont have the box anymore. I have looked into it before and think "think" I have the amoled screen.
Click to expand...
Click to collapse
August = AMOLED
SLCD didnt start to ship until september.

The RUU is loading now. Its at 76% on Updating system. So, if this does work where does my phone stand? Do I need to re-root get s-off and things of that nature?

You will still have s-off. Your phone will be on a .92 hboot with the 2.15 radio. You will need to either rerun the root tool to get recovery back or use a recovery that is flashable through hboot. If using the PB31IMG didn't work for you before I suggest rerunning the tool.
Once recovery is installed do not attempt to restore from within recovery, instead download another rom and flash it through recovery.

Just wanted to drop back in and say thanks to everyone who helped me get my INC back. I really appreciate it and I can throw the BB Storm back in the closet!

[q] help unroot my htc desire

Hey guys,
I'm having a problem I hope someone out there can help me with;
I have the HTC Desire (ACR 6275 Bravo C CDMA) from Cellular South. Bought it in OCT 2010, and I soon realized the space on it sucked. I was jealous of all my friends that had already gotten the 2.2 update and could store apps on the memory card. So I researched the information and learned I could ROOT it and then manually update the system. So, I rooted it, however when it came time to manually update it, I found the instructions to be confusing and I got scared I would BRICK it so I just gave up. Well now that I can get the REAL update, it wont update due to me rooting it. I have researched how to unroot and have tried several RUU downloads, including the ones through unlocker.com but nothing seems to work. The error on the update asked if I wanted to reset back to Factory Settings and I selected yes, but that hasn't helped.
HOW DO I EITHER unroot the phone, or find an easy way to manually update it myself.
I have recently installed ROM Manager but I am unsure how to use it.
I am a Novice at this stuff.
Thanks, Paul

I was wanting to install this update on my cell south desire also however I have not found a way to do so. Ultimately, I think a RUU for the cell south desire is needed. I've tried flashing the recovery.img from the froyo OTA update and it still fails to install.
For anyone contemplating on helping out, the initial problem is assertions from CID checks in the update script. Removing the assertions for the CID check from the update script and attemping to apply with clockwork mod recovery doesn't get the update installed either, rather it runs through and kicks back to the main menu in the recovery without updating anything or showing any errors. I don't know if the results are the same with the stock recovery.img from the OTA update because I don't know how to do a manual update via the stock recovery.
I'm no expert so hopefully someone can chime in on how to get this update installed.

Same here, I have tried almost everything to unroot my phone. I thought that the OTA update was just supposed to over write the root apk and all that, but it refuses to. It gets about a 1/4 of the way done and just "!". I've tried SuperOneClick to unroot and it always hangs up also. Any help would be greatly appreciated.

You can't install an OTA over a rooted handset - it buggers it up
If you wanna go stock you'll need the RUU

The problem is there are no cellular south RUU's available, at least not publicly. There is also no way to S-ON that I'm aware of, the unrevoked forever S-ON patch does not support CDMA desires.
I have read where people were applying OTA updates with other phones (and thus losing root) so there is a lot of mixed information going around about what you can and can't do with OTA updates (really anything regarding android and modding). I read one thread last night here on xda where Desire Z (or maybe HD, can't remember) where successfully applying the OTA froyo updates to their phones back in december with modified update scripts to get past the assertions (that's where I got the idea from in my previous post). The OTA update contains boot, recovery and system images... I personally fail to see how these updates can't be made to work, but then again I'll admit that I'm new to the scene.

I've read that since the cellular south desire is a CDMA device that any CMDA RUU will work. I'm unsure about this... If we did this, I doubt that everything will work correctly and it will not prompt for the new 2.2 update on our networks. Has anyone tried this out yet?
Sent from my Xoom using XDA App

I've been thinking about this most of the day while working and I honestly don't see why we couldn't flash the boot, radio, recovery, and system images from the oTA update with adb and go on about our business. Does anyone have any experience doing this and have any reason not do it other than potentially loosing root? What are the dangers?

So, I've got the update installed. Took lots of trial and error before I got it, my phone is not bricked/buggered/otherwise unusable. The update went without a hitch once I got things right, now running the OTA HTC Desire Android 2.2 update from cellular south. Ok, so, on to how I did it.
Requirements
a. Android SDK (need adb) or another way to flash the stock recovery image
b. The OTA update zip (if you let it download, it saves to /sdcard/download/)
c. A goldcard.
d. A stock system.
Before you get started, you need to restore your system to the stock rom via a nandroid backup or whatever you maybe have used to do backups. If you don't have a stock system (all stock apps, including cell south apps), the update will not install. It will error out about a quarter of the way through.
Once the system is back to the stock (other than the S-OFF and Super User), you need to create a gold card. If you don't have a gold card, you are going to get assertion errors in regards to ro.cid. There are lots of guides out there on how to do this, I used the unlockr guide:
theunlockr.com/2010/03/10/how-to-create-a-goldcard/
After your goldcard is ready, insert it into your phone, download the OTA update, don't install it. Once it's done downloading, copy it to your computer and extract the archive. In the archive, there is another archive that contains the hboot, recovery, system and radio images. Extact this archive (had to use 7zip over here) and copy the recovery.img to your sdcard. Reboot your phone again into recovery (I was using clockword mod), and launch a shell via adb. When you get the shell, you need to mount your sdcard (mountall -a didn't work for me like some guides suggest). My sdcard was /dev/block/mmcblk0p1. After that flash the recovery image. Complete instructions (with adb in %PATH%):
Code:
C:\Users\jp>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # ls /dev/block
ls /dev/block
mmcblk0 mtdblock0 mtdblock2 mtdblock4
mmcblk0p1 mtdblock1 mtdblock3 mtdblock5
~ # mount /dev/block/mmcblk0p1 /sdcard
mount /dev/block/mmcblk0p1 /sdcard
~ # cd sdcard
cd sdcard
/sdcard # flash_image recovery recovery.img
flash_image recovery recovery.img
/sdcard # exit
exit
Once the stock recovery has been restored, you can download and install the OTA update as normal or continue the installation from your previous download to get recovery.img.
The super user app is still there, however, as expected root is lost. I don't think unrevoked (what I used) supports the hboot version 1.06 that comes with this update so don't expect to get root back.
There is a new wifi tethering app which doesn't show up in the app drawer under sense, however it's there in launcher pro and probably any other launcher besides sense.
Forgot to mention:
If for some reason the update won't install, you can reroot and reflash the clockwordmod recovery. I did this several times while trying to get the update installed. When I encountered problems, I would re-run unrevoked and start over.
superuser.apk
If you want to get rid of superuser.apk, do it before you install the update. Since this procedure doesn't turn security back on, I think that it can probably be done with an update.zip however I haven't figured out how to properly sign the updates yet. I've tried a few tools and a custom script to delete it, but I can't get past the signature verification with the stock recovery.

What hboot version does 2.2 come with?

HBOOT is at 1.06 in this update.

Well, I'm screwed... I didn't backup my phone before rooting it...
Sent from my Xoom using XDA App

Doesn't matter if it's rooted, you just need to restore the stock system (os and apps) if you did a nandroid backup after rooting. The gold card will get you around the rooted issue, at least I think that's what allowed me to finally install the update. I fear that from here out I'll need the gold card to install any updates unless I can turn security back on. There is another thread where a cellsouth user had unrooted his desire however he didn't give any details. I think he used an altell RUU to do it though. I haven't looked at how the RUU's work but I'm wondering if they can be made to use the files from the OTA update. This would really solve a lot of problems in regards to unrooting cellsouth desires.

Has anybody found a more simple way to update a rooted CS Desire to 2.2?
I am currently stuck with 2.1 due to this issue.

fd59 said:
Has anybody found a more simple way to update a rooted CS Desire to 2.2?
I am currently stuck with 2.1 due to this issue.
Click to expand...
Click to collapse
Yes, flashing a 2.2 ROM
Seriously it's nothing difficult to flash ROM's, if you want to flash a new one:
download whichever one you want and place it onto your SD-Card (somewhere you can remember).
Turn off the phone. Hold volume down and power at the same time, which will boot you into HBOOT.
Use the volume down key to locate RECOVERY, and press the power key.
This will boot you into recovery, you use the trackpad to navigate, and not the volume down/ power key. From here, go to "Backup & Restore", and backup your current ROM.
Once that's finished, go to "Advanced", and select "Wipe Dalvic Cache". Then, go back to the main menu, select "Install zip from sd", "choose zip from sdcard", and find the ROM you want to install.
Select the ROM, scroll down to "yes", and press the trackball.
Hope this helps
If you need any help post or PM me.

I didn't want to start a new thread for this so I'm posting it in this one. I just came across the solution in this thread to update from rooted 2.1 to 2.2 with the OTA update. For warranty purposes I want to return to stock, only on 2.2. However, now when I try to check for software updates and download the OTA 2.2 update, my phone says "your phone is up to date" "no update is available for your phone." Even though on the previous screen it says 2.1 update 1. Someone who has the OTA update downloaded to their phone, could you please upload it? I would really appreciate it.

AbuseTheElderly said:
I didn't want to start a new thread for this so I'm posting it in this one. I just came across the solution in this thread to update from rooted 2.1 to 2.2 with the OTA update. For warranty purposes I want to return to stock, only on 2.2. However, now when I try to check for software updates and download the OTA 2.2 update, my phone says "your phone is up to date" "no update is available for your phone." Even though on the previous screen it says 2.1 update 1. Someone who has the OTA update downloaded to their phone, could you please upload it? I would really appreciate it.
Click to expand...
Click to collapse
I need the 2.2 update too!

Why can't you guys use the 2.3.3 RUU? HTC accepts its warranty as well.
Sent from dGB using Transparent XDA App

Installing GB OTA from SkyRaider?

I got the notification this morning, and (since I'm S-Off) assumed I could just install the OTA and re-root (flash Clockwork, install SU). The OTA went through the download > verify > reboot dialogue, but froze up on the reboot step so I just rebooted it manually, expecting to have to re-run the updater. Oddly enough, I haven't gotten the update notice again, despite multiple shut downs/reboots.
TL;DR - Do I need to have the stock Froyo ROM installed for the OTA to succeed?

You do need to have the stock recovery, which is likely why it failed during the reboot. If you really want to receive the OTA, it's probably easiest to just flash the stock 2.2 RUU.

no, for two reasons.
1. assuming you are on a custom rom, your phone is rooted, and root often blocks the update.
2. in order to get gb on the rom, they need to new kernal...or a re-worked one, ginger sense and the two senseless roms already have it. yanked em from the ruu.

k_nivesout said:
You do need to have the stock recovery, which is likely why it failed during the reboot. If you really want to receive the OTA, it's probably easiest to just flash the stock 2.2 RUU.
Click to expand...
Click to collapse
Thanks, that's exactly what I thought. I'm not sure why I'm so eager to install it, I just think it'd be nice to take it for a test drive before reverting to SkyRaider/Cyanogen/whatever my flashing-heart desires
Kiboe said:
1. assuming you are on a custom rom, your phone is rooted, and root often blocks the update.
Click to expand...
Click to collapse
So I need an non-rooted ROM (stock Froyo..) to install the update (I understand I don't need it to install a version of GB, I was referring to the stock GB update that just got pushed out). Thanks for also confirming my suspicions

Novice Rooted incredible Unrevoked3
I have been scouring forums and have only found bits and pieces of how I should handle the Gingerbread upgrade to my rooted Inc. I am rooted with Unrevoked3 NOT Forever. I really only use root for Wireless Tether and TIBackup. What should I do if I am prompted for the upgrade to my phone? What is the process and will my phone get pushed the update. Essentially, I would like the Gingerbread update, reamain rooted so I don't loose the Wireless Tether.
Should I apply the update then go back to Unrevoked? I here people say that I should install Unrevoked Forever then flash 2.2 apply the update then i guess I can use unrevoked 3 again? Is there a step by step how to guide to handle this. I am really confused and afraid off messing something up.
Thank you in advance.

If you were prompted for the update it would fail unless you have s-on and the stock recovery.
Just flash one of the OTA leak roms in the dev section if you want to try stock gingerbread. In the event you choose to return to complete non-root status and update to Verizon's gingerbread OTA, you will not be able to root again until (or if) Unrevoked finds another root exploit.

SlimSnoopOS said:
If you were prompted for the update it would fail unless you have s-on and the stock recovery.
Just flash one of the OTA leak roms in the dev section if you want to try stock gingerbread. In the event you choose to return to complete non-root status and update to Verizon's gingerbread OTA, you will not be able to root again until (or if) Unrevoked finds another root exploit.
Click to expand...
Click to collapse
Not exactly true you dont have to be s-on, actually you dont want to ever go s-on for any reason unless you are under waranty and need to take it to verizon. Flashing an update to gb while s-on will make you loose root possibly forever.
You do need to be compleet stock to run an update including all bloatware still installed.
The update still may be on your phone in the /cache directory look for a zip file with vzw and a bunch of numbers in the name. Copy it to your sd card and rename it update.zip and reboot into hboot to install the update.
Or you can just flash this it is compleet stock gb 4.06.605.3 other than being rooted deodexed and busybox installed.
http://forum.xda-developers.com/showthread.php?t=1247253

Touché, I stand corrected haha

can't get past 4.06.605.2
OK, I have been reading up all I can find about going from 2.2 to 2.3.4 on Incredible. I was able to download the 4.06.605.2 build and got it to install on my phone, but I can't seem to get any of the 4.06.605.3 to install. I am not sure if I did something wrong. I have also tried to get the OTA by going to system updates but nothing there. Any ideas that I can try?
Also I noticed something odd under Hardware Information it thinks my display is 4.3 inch WVGA resolution but everything seems to show up right on the screen, nothing gets cut off.
This is what my phone shows under Software Information
Android Version
2.3.4
Baseband version
2.15.10.07.07
Kernel version
2.6.35.10-g5e15ac4
[email protected] #1
Mon Jul 18 19:36:11 CST 2011
Build number
4.06.605.2 CL111240 release-keys
Software number
4.06.605.2
Browser version
WebKit/533.1
PRI version
1.50_022
PRL version
52341
ERI
5

If your still rooted just flash the rom in the above post. If not reroot and install it. It is pure stock and the screen size info was fixed.

I was able to put 2.3.4, 4.06.605.2 on my Droid with S-ON and no root, at least I never rooted it myself and as far as I knew it was brand new when I purchased it from Verizon. So I am going to have to find out how to root then. Never quite understood how to do it, although when I was with ATT I was able to put custom roms on my Pure and Fuse. I am assuming there is a thread for rooting?

louisianarod81 said:
I was able to put 2.3.4, 4.06.605.2 on my Droid with S-ON and no root, at least I never rooted it myself and as far as I knew it was brand new when I purchased it from Verizon. So I am going to have to find out how to root then. Never quite understood how to do it, although when I was with ATT I was able to put custom roms on my Pure and Fuse. I am assuming there is a thread for rooting?
Click to expand...
Click to collapse
Well if you are stock as you say just download the below file, rename it update.zip and stick it on your sd card not in any folders. Then go to settings/manage applications and make sure fastboot is unchecked. Then power off your phone. Then hold the vol down button while pressing and holding power till a white screen pops up. It should automaticly find the update.zip and install the update.
http://dl.dropbox.com/u/32165623/e53...ase_211679.zip

cmlusco said:
Well if you are stock as you say just download the below file, rename it update.zip and stick it on your sd card not in any folders. Then go to settings/manage applications and make sure fastboot is unchecked. Then power off your phone. Then hold the vol down button while pressing and holding power till a white screen pops up. It should automaticly find the update.zip and install the update.
http://dl.dropbox.com/u/32165623/e53...ase_211679.zip
Click to expand...
Click to collapse
Ps: If you are already on gingerbread 605.2 and s-on, then there is no current method to root available yet.

This it was appears when I do that
INCREDIBLE XD SHIP S-ON
HBOOT_0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224–16ab
RADIO-2.15.10.07.07
Jul 23 2010, 10:06.51
then says HBOOT and gives options of Fastboot, Recovery, Clear Storage, Simlock, Factory Reset
does seem to won to read the update.zip

louisianarod81 said:
This it was appears when I do that
INCREDIBLE XD SHIP S-ON
HBOOT_0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224–16ab
RADIO-2.15.10.07.07
Jul 23 2010, 10:06.51
then says HBOOT and gives options of Fastboot, Recovery, Clear Storage, Simlock, Factory Reset
does seem to won to read the update.zip
Click to expand...
Click to collapse
Hmm should automaticly find it. Did you download it with your pc or from the phone?

downloaded to my laptop then transfered the SD card

louisianarod81 said:
downloaded to my laptop then transfered the SD card
Click to expand...
Click to collapse
Do you have file extensions set to show on your pc? What i mean by that is when you downloaded the file did it already say .zip at the end of the file or was there no . anything.

that link you posted a few spots earlier is dead can you post it again, it my have something to do with the ..... in the middle, maybe it didn't copy and past right.

It does show .zip

louisianarod81 said:
that link you posted a few spots earlier is dead can you post it again, it my have something to do with the ..... in the middle, maybe it didn't copy and past right.
Click to expand...
Click to collapse
I guess the link went down. here is a new one. With this file you will not have to rename it anything just delete the old one you put on your sd and replace it with this one and try again.
http://dinc.does-it.net/update.zip