Related
If I'm running skyraider 2.5.2 sense, 2.15 radio and .77 hboot. A few questions...
1) is there a way to upgrade hboot?
2) is .79 the most up to date version? If not, what is?
3) if I can upgrade, is there a reason to? What is the difference between the different versions of hboot?
No reason, newer HBOOTs don't really offer you any performance increase.
Upgrading to hboot 0.79 is required for successfully installing the 2.2 OTA from Verizon (not leaked version). Can someone please answer this post? There appear to be a bunch of us stuck at this point.
Akhnaten
BTW, the error the update gives is "Signature verification failure" or something like that. This is occuring with hboot 0.77.
There appears to be an updated hboot in the May OTA update. You can find the file for the upgrade at the link. I will try this out and post an update.
Akh
http://shipped-roms.com/shipped/Incredible/
akhnaten said:
Upgrading to hboot 0.79 is required for successfully installing the 2.2 OTA from Verizon (not leaked version). Can someone please answer this post? There appear to be a bunch of us stuck at this point.
Akhnaten
BTW, the error the update gives is "Signature verification failure" or something like that. This is occuring with hboot 0.77.
Click to expand...
Click to collapse
Ok, but what steps do we follow to upgrade hboot to 0.79 so that we can install the 2.2 OTA update?
I thought .92 hboot was out.
http://forum.xda-developers.com/showthread.php?t=757798
http://adrynalyne.us/
0.92 (or something in that range) is the version that comes with Froyo 2.2. We are talking about trying to get to Froyo 2.2 while maintaining root. When I reverted to the May OTA to upgrade from version 0.77 to 0.79, that did the trick for the upgrade. Unfortunately, step 5 in the thread post by k.electron in the "[Q] Want root AND want OTA" thread does not work. I guess I undid the root work when I reverted. Now all I get after step 5 is my phone shakes at me 5 times when I try to go into hboot. Fortunately, I can still boot my phone regularly after a battery pull. BTW, when I say "May OTA" I mean the rom version 1.22.605.2 at the link I posted earlier.
lafester said:
http://adrynalyne(dot)us/
Click to expand...
Click to collapse
Should we host this file here? I don't want to cause adrynalyne any bandwidth issues with a direct link to his page.
akhnaten said:
0.92 (or something in that range) is the version that comes with Froyo 2.2. We are talking about trying to get to Froyo 2.2 while maintaining root. When I reverted to the May OTA to upgrade from version 0.77 to 0.79, that did the trick for the upgrade. Unfortunately, step 5 in the thread post by k.electron in the "[Q] Want root AND want OTA" thread does not work. I guess I undid the root work when I reverted. Now all I get after step 5 is my phone shakes at me 5 times when I try to go into hboot. Fortunately, I can still boot my phone regularly after a battery pull. BTW, when I say "May OTA" I mean the rom version 1.22.605.2 at the link I posted earlier.
Click to expand...
Click to collapse
That is the HTC diagnostic mode when it vibrates multiple times. S-off unlocked it. SEARCH THE FORUM it is a common problem.
Thanks for the reply, ToyTank. I haven't looked up what the correct way to get out of diagnostic mode is yet, but I will give one final update.
I tried to reflash (ruu) the 605.2 rom and it failed. However, in the process it got me back into hboot mode. I then noticed that I was still in s-off mode. I switched to using the appropriate directions on this thread:
(http://forum.xda-developers.com/showthread.php?t=771178)
Condition 3, in particular
I skipped the installing 2.2 part since I had that already (from Verizon) and the rest went great. Now I am running OTA 2.2 with s-off and root.
Can someone recommend a 2.2 rom w/o all the crapware from Verizon?
Thanks,
Akh
Instead of loading a different ROM, get Titanium Backup and remove the apps you do not want.
Sent from my HTC Incredible.
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
To be honest, I would say just wait for the OTA, Verizon themselves have confirmed it has been/will be released today 8/27. Then there will be no worrying, since you don't want root this would be the best way.
boomertwo said:
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
Click to expand...
Click to collapse
I'm sorry this has nothing to do with what you're asking, I've read, and don't know sorry man, but I do have a quick question for you. I see you have never rooted, or maybe or have, I thought maybe you hadn't for some reason, but anyway, I see you HBOOT it .77, how long have you had your phone since?
Yes I had rooted the phone recently for about 2 weeks then it got messed up but thanks to an unrevoked member I was able to recover the phone. It wasn't bricked or anything but some how the NAM was messed up which prevented me from using *228 to update roaming or my ability to activate the phone after a factory reset. I do remember it having hboot .79 before rooting though.
Update: I verified that the hboot in the stock restore img file I used had only hboot 77 in it and not 79. This means I downgraded to 77 without knowing it at first. (From the threads I have read it is stated that .77 and .79 are interchangeable so I don't think I need to worry about it when the ota comes I hope..)
I've had it for about 3 months now so I'm out of the return policy and I do like the phone and have no intention of returning it.
After trying root out for those 2 weeks I found that for me I didn't really gain anything that seemed worth it for my personal needs.
Also I like to tinker with stuff but since I'm in a 2 year contract I rather not take the risk of bricking it and having to pay for the next 2 years for service I can't even use due to my own fault of breaking the device.
Right now I'm just wondering if it is safe to apply the file that can be found in the ruu without root and without breaking the device since it has the same build number and radio number as the update that verizon has stated on the update page.
.77
I am on my third incredible, and all 3 shipped to me with v.77. Last one shipped was 8/9 (wow, maybe this one is a keeper).
jdmba said:
I am on my third incredible, and all 3 shipped to me with v.77. Last one shipped was 8/9 (wow, maybe this one is a keeper).
Click to expand...
Click to collapse
were these all brand new phones, refurbs..?
To my understanding of this whole .77, .79 HBOOT is that these two are interchangeable and doesn't matter which one you have. I was just curious because at first I used the RUU that gave me software 1.22.605.0 and the latest is 1.22.605.2 and I never got an OTA update for the latest 2.1. but I think this is normal since the servers are doing the new thing.
and from what I think, if you had .77, and got the OTA for the latest 2.1 that came out a while ago, it kept the .77, but if you did the latest 2.1 through the RUU on ur computer instead of OTA it updated the HBOOT to .79 as well.
This is how it was with the Droid Eris with the leaks and stuff which blocked you out of root.
...
BlazeD OnE said:
were these all brand new phones, refurbs..?
Click to expand...
Click to collapse
Phone # 1 - New ... would get hotter and hotter (even when not in use) until it would enter a reboot cycle. It would also reboot randomly during the day.
Phone # 2 - Refurb ... got it with a bad speaker, but otherwise it worked perfectly.
Phone # 3 - Refurb ... still going.
boomertwo said:
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
Click to expand...
Click to collapse
in theory that should work.
k.electron said:
in theory that should work.
Click to expand...
Click to collapse
Well I took the plunge and can confirm that the method in my original post does work and without a hitch(For me at least.)I did this after reading another question thread that had a guy basically asking the same thing and was recommended just to follow to step 6. I cannot link to anything yet so I will just give you the thread title that is located in the Q&A section of this forum for the droid incredible.
Thread Title: "[Q] Applying RUU update to stock phone"
The phone did however reboot the bootloader and put me into fastboot. I did not pull the battery but instead selected bootloader again and it continued the update on its own.
I'm successfully not root and s-on with android 2.2(HTC stock)
Hboot .92
Stock Recovery.
*Before you say it.. I know I'm now not able to get root till unrevoked or another dev team releases new tools for this version. I did this by choice*
*I in no way will recommend anyone to do this and will not take responsibility for your phone being turned into a paper weight* < You have been warned..
Sooooo.. anyone want to clarify how to extract rom.zip from the RUU please?
Just download the extracted ROM. It's on page 6 or 7 in the RUU thread.
NinjaRicky said:
Sooooo.. anyone want to clarify how to extract rom.zip from the RUU please?
Click to expand...
Click to collapse
did you get it?
hello all: im as newbie as it gets with this rooting,but very good at following instructions and very computer savy.I have a droid incredible with software 2.2,which Im trying to root.using unrevoked 3.21 I have followed all instructions to the tee,all goes well till the end,it says waiting for root,and stays that way for as long as you leave it. Ive tried 4 different computers all running win 7,one 64 bit,the other 3 are 32 bit,all with same result,(waiting for root) I first loaded the modified usb driver from unrevoked, it shows android bootloader interface good to go under android phone in device manager.I start the reflash program, made sure usb debugging was on made sure phone was connecting in charge mode,made sure unknown sources could be installed. I even tried installing htc sync,then uninstalling,because another site said drivers from htc sync were needed. nothing has got me by waiting for root. I have seen this same problem over and over on many different sites,but as of yet to see one fix, the procedure for unrevoked 3.21 seems very simple and straight forward, but every answer Ive seen to this problem,points back to original instructions,which Ive done over and over. any new ideas would be greatly appreciated. thanx in advance.
There are several threads here already discussing how the Nov 15th?? OTA firmware update that VZW pushed to the incredible can not be rooted in the same way as past versions.
And therefore the 3.21 version of the Unrevoked tool (reflash_package.exe) does NOT WORK, and we need to wait for them to update it.
Those who had the older firmware, rooted it, and used Unrevoked Forever to gain S-OFF (not the same as the "reflash-package.exe" rooting tool) do have options.
BUT Any one who has received in INC with this recent OTA firmware update but didn't have "S-OFF" (like due to a recent purchase, warranty replacement phone, being prompted about the upgrade and saying "yes" to accept it being installed), will have to wait.
Tips...
what is s-off? see -> http://unrevoked.com/rootwiki/doku.php/public/forever
What is the "reflash_pacakge.exe" rooting tool? (aka Unrevoked3)? see -> http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
Thanks Kid, I appreciate it, sorry for it being a stupid question,but I guess everybody has to start somewhere! reminds me when satellite tv cards were being programmed,you could ask almost any question,and many people would always reply,read ,read and read some more.I spent 2 days reading and trying to root my phone,simply because I should be able to delete any software on it I choose to.I've never bought any computer I couldnt delete software I dont use or like. After 2 days I thought maybe I was out of luck until new software,but wasnt going to give up until I was sure,thanx for being the ONE person to fill me in!!
AHHH, I was wondering what all this waiting for root threads were about. Guess since I'm s-off and running SR I was out of the loop. I think I'd be totally freaked by now if I lost root on my phone. LOL!
KidJoe said:
There are several threads here already discussing how the Nov 15th?? OTA firmware update that VZW pushed to the incredible can not be rooted in the same way as past versions.
And therefore the 3.21 version of the Unrevoked tool (reflash_package.exe) does NOT WORK, and we need to wait for them to update it.
Those who had the older firmware, rooted it, and used Unrevoked Forever to gain S-OFF (not the same as the "reflash-package.exe" rooting tool) do have options.
BUT Any one who has received in INC with this recent OTA firmware update but didn't have "S-OFF" (like due to a recent purchase, warranty replacement phone, being prompted about the upgrade and saying "yes" to accept it being installed), will have to wait.
Tips...
what is s-off? see -> http://unrevoked.com/rootwiki/doku.php/public/forever
What is the "reflash_pacakge.exe" rooting tool? (aka Unrevoked3)? see -> http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
Click to expand...
Click to collapse
KidJoe
I am not sure if UnRevoked has changed anything, but believe I was able to root today using the UnRevoked tool after taking the new OTA update. See the thread below and let me know what you think.
http://forum.xda-developers.com/showthread.php?p=9392730#post9392730
SortaSmart said:
KidJoe
I am not sure if UnRevoked has changed anything, but believe I was able to root today using the UnRevoked tool after taking the new OTA update. See the thread below and let me know what you think.
http://forum.xda-developers.com/showthread.php?p=9392730#post9392730
Click to expand...
Click to collapse
Not sure. Were you S-OFF before you tried that? If so that could be why it worked.
For those that are still S-ON, this set of instructions could work -> http://forum.xda-developers.com/showpost.php?p=9384491&postcount=199 It did for me on my GF's AMOLED Inc that was S-On and received the latest OTA update. Now she's S-Off and Rooted with the Nov 15th update. If you have SLCD, then read some of the posts after that one before trying, (like Post #205 & 206)
KidJoe said:
Not sure. Were you S-OFF before you tried that? If so that could be why it worked.
For those that are still S-ON, this set of instructions could work -> http://forum.xda-developers.com/showpost.php?p=9384491&postcount=199 It did for me on my GF's AMOLED Inc that was S-On and received the latest OTA update. Now she's S-Off and Rooted with the Nov 15th update. If you have SLCD, then read some of the posts after that one before trying, (like Post #205 & 206)
Click to expand...
Click to collapse
I have had S-Off but when I returned to the stock 2.2 it also turned S-On. I followed these instructions to return to stock with S-Off. Probably for AMOLED only.
http://androidforums.com/incredible-all-things-root/181255-how-downgrade-official-2-2-a.html
I took the OTA then I used the reflash tool as described in my other post.
Sounds like you did something similar.
unrevoked dev team
@unrevoked unrevoked dev team
Inc folks -- we're really sorry for the delay. We have a fix, left to do is testing it and packing it up to ship. Final exams eat time...
this is the newest update
hoag50 said:
unrevoked dev team
@unrevoked unrevoked dev team
inc folks -- we're really sorry for the delay. We have a fix, left to do is testing it and packing it up to ship. Final exams eat time...
This is the newest update
Click to expand...
Click to collapse
well this is good news!!
Hey guys, I should have posted this about a month (maybe even longer) ago, but I've been dealing with some health issues and couldn't be bothered. First off I have a rooted phone (with S-OFF) but I like keeping the stock sense build. I upgraded OTA to 2.2 some time ago, then there was an OTA update a few months after that (which I was able to install without any problems after I replaced a couple of files that had gotten modified), now this newer OTA update refuses to install.
It tells me it needs to reboot to start installing so I click the button to reboot and it counts down, but it never reboots. Is it somehow detecting that my phone is rooted? I would like to have the most up to date OTA update installed on my phone at all times so any help or ideas would be great (also I'm sorry if this has been covered before, I did search but I've been afk for a bit so I might have missed some things).
- DeeBG
Read this thread, it tells you how to get back to 2.2 stock, then download the latest Unrevoked to root again and obtain s-off...
RMarkwald said:
Read this thread, it tells you how to get back to 2.2 stock, then download the latest Unrevoked to root again and obtain s-off...
Click to expand...
Click to collapse
Blah I have to go back to 2.2 stock? Oh well, it's not the worse thing in the world (I already had to do it once) and those are great instructions (plus I've wanted to have the latest version of Clockworkmod installed for a while and using Unrevoked means I won't have to mess with the payload/su/etc files). Thanks!
I also thought of something (kind of late though). I was using a custom kernel, which might have been the issue too. But I went ahead and re-enabled S-On, however now for some reason my phone is checking for errors on my SD card (no idea how long it will take, or why it's doing that), but does anyone have a link for that 17.7mb file of the 3.26.605.1 update? I found the full RUU, but it's huge and I rather just upgrade than possibly wipe everything out (and I don't know when my phone will have the OTA ready again). Thanks for any help!
Is it necessary to update or downgrade then upgrade the OS?
sent from my Ultimate 2.33 Incredible
bigsapz said:
Is it necessary to update or downgrade then upgrade the OS?
sent from my Ultimate 2.33 Incredible
Click to expand...
Click to collapse
That seems to be what that linked thread says, but I don't believe that is correct (that's why I am looking for that 17.7mb OTA file). I was able to install the first 2.2 update (aka 2.2.1) without issue after I restored some files that were altered (either by rooting or installing the wireless tether app that's hosted on Google Code). However this OTA update (aka 2.2.2) isn't popping up again for me to install, so I am going to see if I can extract just the upgrade data from the official RUU. I have to wait until later tonight because I need my phone to be operational for another few hours but I'll post back with results (and files if need be =).
Yeah I tried the RUU update and as expected it did a total wipe... bringing back system via nandroid and will try something else.
Edit: http://forum.xda-developers.com/showthread.php?t=969973 <= using Jay's thread, which is much like the post that was first given to me in this thread. Not re-enabling S-ON seems to be the problem... lesson learned, don't try shortcuts unless you know what you are doing (and I've been afk from the "Dinc Scene" too long for that =p.
Edit 2: Up to date and 100% working!
I was able to run an older version of Unrevoked to establish SU access, but Unrevoked Forever is incompatible with my radio version. So, I have SU access, but I cannot remove or convert any applications using Titanium Backup. TB runs, but it reboots the phone if I try to remove system apps. HBOOT shows S-ON since Unrevoked Forever was not able to complete due to the radio version. So, am I stuck with S-ON? Is Unrevoked Forever going to continue developing releases to cover 2.15.10.07.07?
If I understand correctly, I cannot flash an older radio version with S-ON. Please correct me if I am wrong.
Thanks!
HTC Incredible
2.3.4
Baseband: 2.15.10.07.07
you are correct,s-on will only let you go forward with "approved by htc" files. that means no backpeddling firmware to a rootable version,no flashing only a radio or recovery. im surprised that unrevoked even worked to get you su access,i was under the impression that all exploits had been patched in 2.3.4 source code. what happens if you try and install clockwork?
if you truly have su access,it seems it may be possible to use adb to rewrite the misc image,and thus be able to flash backwards in firmware.
however,from the sounds of the behavior youre describing for tibu,i dont believe you have su access. it prolly only put the app in the drawer,and was unable to place the matching binary.
we have been telling folks for months that they should become s-offed before the GB update,as it would be unrootable.
i bought an xtc clip awhile back that is supposed to support the incredible. i dont know that it will actually work,ill know for sure when it gets here. im told it only works with sim card phones,wich the inc is not,but its clearly listed in the supported devices.
your only real hope at this point is that someone finde a new exploit that will allow temp root and re-writing of the misc image so that you can flash older rootable firmware,or that alpharev/unrevoked can add the incredible to its supported devices list,as they use some sort of hboot trickery to get a hard patched permanent s-off hboot onto the phone first. from there you load a recovery thru hboot,then flash su in recovery.
sorry this isnt the news youre hoping for.
Thank you for the help.
It is odd. I definitely have su access through terminal, and I am running opengarden and barnacle wi-fi tether. I ran an older version of Unrevoked, and it did not complete the final step of s-off. Clockworkmod installed successfully, and I created a recovery image. Can we expect some way to root after the GB update? Is this just an HTC thing? I'm sorry for all of the questions, but I was soooo close!
efizzle said:
Thank you for the help.
It is odd. I definitely have su access through terminal, and I am running opengarden and barnacle wi-fi tether. I ran an older version of Unrevoked, and it did not complete the final step of s-off. Clockworkmod installed successfully, and I created a recovery image. Can we expect some way to root after the GB update? Is this just an HTC thing? I'm sorry for all of the questions, but I was soooo close!
Click to expand...
Click to collapse
If you already have clockwork mod, flash the unrevoked forever zip from here
When I flash the zip file, I get E:/ unsupported radio version. E: update failed.
Do you have adb set up and running? Are you fairly comfortable copy/pasting commands?
Sent from my ADR6400L using XDA Premium App
still with us? waiting for an answer to the above so we can procede
also is it possible you can post or PM me a link to the version of unrevoked you used?
if you dont have a link,just email me the whole file( [email protected] ) im extremely interested in trying to duplicate your condition and figuring out a reliable way for folks to downgrade and root.
Scotty,
I'm sorry for the delayed response.
I do not have ADB setup, but I have no problem following directions to get S-off and reclaim some memory!
I have emailed you the Unrevoked file to your email address. This should run perfectly on 2.3.4 with the exception of the last step of flashing unrevoked.zip for S-off. You will see the "unsupported radio version" errors on the phone's screen. Please let me know if there is anything else that I can do to help. Thank you for your help with this.
I got your email. I will put some stuff together for you,and try it out and see if it all works the way I hope it will. If so ill upload a mini-adb with some exploits files and post a guide. Basically,were just going to rewrite the misc image so you can downgrade back to froyo and run unrevoked forever. After you reroot and get s-off back,you can restore a backup of what you have now.
Sent from my ADR6400L using XDA Premium App
Subscribing to thread. Looks interesting, Im hopeful it works out. Good luck!
Sent from my ADR6300 using XDA App
Ok after reading this thread again. My guide for the merge on froyo or the stuff I have for gingerbread for the merge will not work on a non emmc device. 2nd who buys a xtc clip and doesn't look what they buy? The way it works is with the sim card slot. Inc doesn't have one so it isn't going to work. It also isn't listed as supported as it would be pointless to say it does.
If I am not mistake with s-on you can't flash the recovery partition. So how did you get clockworkmod? If you have clockworkmod then you can flash non htc files. Well actually I am not sure how that would work as you have s-on but clockworkmod. Since I have never been in that boat I am unsure.
So are we talking about the inc or inc 2? If inc I am trying to think back to the desire and what was possible on s-on. If I remember right you can dump the misc then flash a lower version ruu. I just can't remember if it doesn't even flash or if it does and doesn't downgrade the radio. By the way I got it in a pm/here scotty was planning to base helping you off my merge guide. By the sounds of it anyway.
Where the commands are not the same. As the partitions would be different. The misc-image is also not the same so if he had you flash the merge misc it will more than likely bork stuff. I am more than willing to help though. How ever I do not check the forums so you are better off pming me. I will say that nothing will probably work until unrevoked supports the new radio.
Edit: If the incredible works with a goldcard. Dump the misc partition and edit it for the firmware version you want to downgrade to. Then run a lower version ruu. When that is done run unrevoked. Of course I don't have a inc so I am not sure if that will work either. I also jumped a bit to conclusions so sorry for that. I also do not get your one post about the xtc clip here, yet in that other post say the clip doesn't support the inc.
thanks for your input,but rest assured we are in no way shape or form refering to anything to do with drellisdees's guide,your copy of it,or any other files,guides,etc. you have linked or posted on this site or yours.
he allready has root access and a recovery partition.
again,thanks for your input,but please stop confusing the issue with your references to merge guides.
for others watching this,a crude guide is now up on android forums:
http://androidforums.com/incredible-all-things-root/427344-2-3-4-root-downgrade-s-off.html
root 2.3.4 with unrevoked 3.22 has now been done successfully twice,and 1 has successfully roled back to 2.2.
more testers welcome
Confirmed. Worked for me. Was s on 2.3.4.
Sent from my ADR6300 using XDA App
My Incredible also is S-on with Verizon 2.3.4 OTA and never rooted. I'll give that "crude guide" a try tonight and report back how it went.
I'm just tired of all the low memory notifications and the constant force closes. Hopefully, I can have a custom mod installed tonight if things go well.
SUCCESS!!
Instructions from the website flawlessly for me.
I first rooted the phone. Then I tested it with some root only apps. They all worked. So ideally you can stop here if all you want is root but next OTA will take away root and then you'll be stuck again.
I completed all the steps and they worked. I was able to downgrade to 2.2 and then run unrevoke3 to root and also turn S-off. It did wipe the data clean. No files from my SDcard were deleted.
This is the time i've rooted my phone and the whole process took me an hour because I was being extra careful not to miss any steps. It all went smoothly.
glad it worked out for you. we finally worked out enuff bugs i put it up here as well: http://forum.xda-developers.com/showthread.php?t=1306400
efizzle seems to have dropped off the face of the earth everyone who reads this should make sure to click the "thanks" button in his first post. we wouldnt have it if hadnt figured out the 3.22 secret.(we would still have zergRush,but not root with access and the ability to make nandroids and backups with tibu so easily).
once again,thanks efizzle
Worked like a champ. I did a recovery back to 2.3.4 and it worked as expected. Also brought back all my force close issues. So I used ROM Manager and installed Cyanogen7 and am loving it.
clicking the thanks button a few times for this help
Ok, I'm on Linux, Ubuntu Lucid Lynx 10.04.3 to be exact, and I have adb installed. Where can I find the Linux version of unrevoked 3.22. I have found several places on the interwebz but I'm not sure if I trust those sources.
Help Please
Just like the op I have a Dinc that is on Gingerbread 2.3.4 and baseband 2.15.10.07.07 and desperate to have root. S-OFF would be nice, but root would be just fine for now.
More than happy to be the Guinea-pig on a Linux system.
sorry,i have no idea. i did a quick search and couldnt even find the windows version of 3.22 that i uploaded... i wanted to link it at its source,since it was emailed to me,but im not sure where he downloaded it from. you might follow the link in the first post credits to the original xda thread and ask on that thread,or send efizzle a private message and see if he can help you. in a worse case scenario,as long as you have 3.32 for linux,you could get temp root and downgrade with the "zergRush" method described in past #2. it doesnt require 3.22,but you wont be able to make a backup,or run titanium unless you can push SU,the binary,and busybox to their respective locations after acquiring a temp root.