The only reason I had to do this was because I was rooted with stock kernal(prior to OTA), it downloaded the update and tried to apply. It didnt update properly.
Do a backup of your data using various programs on the market( I use My Backup Pro) and do a Nandroid backup always before trying to update anything(my advice)
****IMPORTANT*** Please make sure you follow steps 1-4 and have S-Off before you continue to next section ****IMPORTANT***
Before Applying OTA or RUU:
1. Root using the Unrevoked tool http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. Make sure you have S-Off using Unrevoked Forever (flash in Clockwork Mod) :if you need the file http://downloads.unrevoked.com/forever/current/unrevoked-forever.zip
3. Check to see if you have S-Off after press Volume Down + Power
4. Once you have S-Off you can continue
Applying RUU:
Apply this after having root prior to OTA------>RUU(stock): http://shipped-roms.com/shipped/Inc...4k_NV_1.50_PRL58006_release_143351_signed.exe
1. Run the RUU and let it reflash your phone to the new OTA
2. Phone will reboot with settings set to factory
3. You should see the new bloatware installed..you cant miss it!
Rooting after having S-Off and applying RUU:
1a. With phone on and make sure you have Debugging enabled (Settings>Applications>Development> check USB debugging)
1b. Use Unrevoked (not Unrevoked Forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. Wait for it to say waiting for root in the Unrevoked flash program(Unrevoked tool will not complete and say:Waiting for root(this is normal at this point) and phone is restarted, then exit Unrevoked.
3. Place clockwork mod on sd card as PB31IMG.zip(it already comes in this filename) and then power down the phone http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. Go into recovery(volume down + power button) and let it detect pb31img and let it install(have to manually click yes at the prompts)
5. Then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
6. Reboot and you will have root with superuser access
***short term fix until devs can streamline it for the OTA update or if you use the RUU(stock kernal and all the bloatware which can be removed easily)
Then i used Root Explorer(on the Android Market) or you can use ADB shell to delete if you prefer to delete the unwanted bloatware.
Will this work for an slcd incredible?
Also I've tried to root but I can't install the slcd fix file in the bootloader. It shows that it picks up the file but it won't let me install it.
Not Working!
I'm continuing to hack at this myself....I performed the return to stock, updated to the latest OTA, and now using steps 1 to 3 of this method fail, when the phone reboots it checks the zip file and just returns to the menu without install anything. I get the feeling the phone having S-ON right now is an issue.
maxnic said:
I'm continuing to hack at this myself....I performed the return to stock, updated to the latest OTA, and now using steps 1 to 3 of this method fail, when the phone reboots it checks the zip file and just returns to the menu without install anything. I get the feeling the phone having S-ON right now is an issue.
Click to expand...
Click to collapse
I'm guessing you're correct. I'm attempting this on a brand new Incredible and no dice. The PB31IMG.ZIP just gets glossed over.
It fails for me too. If we could just figure out how to get s-off............
Sent from my ADR6300 using XDA App
I should of made it clear that I had S-OFF previous to the procedure above.
Just wondering does the Unrevoked root method do that or no? Maybe someone can chime in with a solution to that.
Just wondering also have you guys done the RUU first to get to stock with the latest OTA?
magneticzero said:
I should of made it clear that I had S-OFF previous to the procedure above.
Just wondering does the Unrevoked root method do that or no? Maybe someone can chime in with a solution to that.
Just wondering also have you guys done the RUU first to get to stock with the latest OTA?
Click to expand...
Click to collapse
You can't use the PB31IMG.ZIP without S-OFF, end of story. Unrevoked can't turn S-OFF unless a custom recovery can be flashed, then flash the unrevoked forever zip and from a stock setting with the new OTA, that cannot be achieved. I activated this new phone and was forced into the new update without question so I'm stuck waiting on Unrevoked to update.
cosine83 said:
You can't use the PB31IMG.ZIP without S-OFF, end of story. Unrevoked can't turn S-OFF unless a custom recovery can be flashed, then flash the unrevoked forever zip and from a stock setting with the new OTA, that cannot be achieved. I activated this new phone and was forced into the new update without question so I'm stuck waiting on Unrevoked to update.
Click to expand...
Click to collapse
im going to try something, give me a sec
So I see that many of you tired it. I have the s-off file that I made into a zip file but since I have an slcd incredible I won't be able to go into recovery and load it.
I guess will have to wait for the unrevoked team to update.
I'm an IT admin at my company and I'm responsible for setting up the phones for every one and we're using Incredibles. I've had several rooted and unrooted users perform the update (against my warning). Thankfully, I got to investigate one of the rooted phones that performed the update. It seems that root was not taken away as SetCPU, ADB root, and other root applications still functioned properly. The phones that are rooted are using Calkulin's ROM and King's #5 BFS. The phones "applied" the update but it seems nothing was actually updated? The software version hasn't changed, the kernel hasn't changed but the baseband and PRI is the same as the new update.
cosine83 said:
I'm an IT admin at my company and I'm responsible for setting up the phones for every one and we're using Incredibles. I've had several rooted and unrooted users perform the update (against my warning). Thankfully, I got to investigate one of the rooted phones that performed the update. It seems that root was not taken away as SetCPU, ADB root, and other root applications still functioned properly. The phones that are rooted are using Calkulin's ROM and King's #5 BFS. The phones "applied" the update but it seems nothing was actually updated? The software version hasn't changed, the kernel hasn't changed but the baseband and PRI is the same as the new update.
Click to expand...
Click to collapse
That great news, but I can't even get my Inc to root.
alphatectz said:
So I see that many of you tired it. I have the s-off file that I made into a zip file but since I have an slcd incredible I won't be able to go into recovery and load it.
I guess will have to wait for the unrevoked team to update.
Click to expand...
Click to collapse
You have to use the Amon Ra port to get into a custom recovery with the SLCD DIncs. All of the new ones I've been getting here are SLCD. I've attached the recovery.img for it. Before plugging in your phone with debugging on and starting unrevoked, you can choose a different recovery than clockwork.
cosine83 said:
You have to use the Amon Ra port to get into a custom recovery with the SLCD DIncs. All of the new ones I've been getting here are SLCD. I've attached the recovery.img for it. Before plugging in your phone with debugging on and starting unrevoked, you can choose a different recovery than clockwork.
Click to expand...
Click to collapse
Thx, can I manually install it on the inc itself and try to push I threw them bootloader?
Or do I have to adb it?
Also if I can upload it manually on the inc. Should I keep the same file name or change it to PB31IMG.zip?
alphatectz said:
Thx, can I manually install it on the inc itself and try to push I threw them bootloader?
Or do I have to adb it?
Click to expand...
Click to collapse
I'd try both and see whichever works. You won't be able to use the PB31IMG.ZIP with S-ON, though. Guess we're stuck waiting on Unrevoked to release for this new update since I cannot root it at all.
cosine83 said:
I'd try both and see whichever works. You won't be able to use the PB31IMG.ZIP with S-ON, though. Guess we're stuck waiting on Unrevoked to release for this new update since I cannot root it at all.
Click to expand...
Click to collapse
I think I might have a fix. Give me a few mins to try if it works the I'll try to upload it on the third thread from my Inc. If I can't upload it I'll have to wait until I get home tonight.
Conclusion :
I've tired to manually downgrade by ruu and it just failed big time.
Hey cosine83 I tired to push that file it also didn't work out for me.
We need a fix for this asap
I see a lot of talk in this thread, by what maybe SLCD users, that there are problems?
So have AMOLED w/S-OFF other users confirmed this works?
I'm curious because I'm apparently running a Deodexed "stock" rom with Root and S-off via the Unrevoked tools, and the OTA pushed to me failed. I'd like to just get back to stock but rooted (I don't mind having to wipe and reload all my apps.)
KidJoe said:
I see a lot of talk in this thread, by what maybe SLCD users, that there are problems?
So have AMOLED w/S-OFF other users confirmed this works?
I'm curious because I'm apparently running a Deodexed "stock" rom with Root and S-off via the Unrevoked tools, and the OTA pushed to me failed. I'd like to just get back to stock but rooted (I don't mind having to wipe and reload all my apps.)
Click to expand...
Click to collapse
Naw..I am not slcd just got an amoled refurb that came fully
Updated
KidJoe said:
I see a lot of talk in this thread, by what maybe SLCD users, that there are problems?
So have AMOLED w/S-OFF other users confirmed this works?
I'm curious because I'm apparently running a Deodexed "stock" rom with Root and S-off via the Unrevoked tools, and the OTA pushed to me failed. I'd like to just get back to stock but rooted (I don't mind having to wipe and reload all my apps.)
Click to expand...
Click to collapse
Well the major problem is that we all updated to the lastest ota that Verizon has pushed out.
This means that us using. SLCD incredible's are stuck without a root method. The unrevoked team needs to push out an update.
As for amoled users they're fine since the recovery.img is working. SLCD recovery.img is messed up. In order to fix the recovery.img we need to have s-off in order to push the fix on the bootloader.
Since you want to update an return to rooted stock items advise you to find a rooted version of the lastest ota. It should be somewhere in the xda forms.
csseale said:
Naw..I am not slcd just got an ambled refurb that's came fully updated
Click to expand...
Click to collapse
Are you 100% positive that you have AMOLED?
Related
Making a thread for this for now since it will probably get buried in the RUU post.
Most important thing first, MAKE SURE YOU HAVE RAN UNREVOKED FOREVER AND HAVE S-OFF! IF NOT DO NOT ATTEMPT THIS!
Get the RUU here:
http://shipped-roms.com/shipped/Inc...4k_NV_1.50_PRL58006_release_143351_signed.exe
Follow this guide by IncredibleDoes to extract the rom.zip update here:
http://forum.xda-developers.com/showthread.php?t=695825&highlight=RUU
(don't download the file he tells you to, download the one linked above, but follow the rest of the guide to get the rom.zip file)
Once you get the rom.zip, follow this guide below:
1. Install this update, get rom.zip from the RUU file, rename to PB31IMG.ZIP (somewhere in this thread there is a post with link to rom.zip, but you still have to rename it), make sure your SD-Card was formatted as Fat32 and put this on the root.
2. Boot into hboot
3. Install PB31IMG.ZIP (not the one I attached to this post)
**Step 3 note** Your phone might reboot to either hboot or recovery after trying to install PB31IMG.ZIP, just get back to hboot and install again, when you get back to hboot you should notice its version .92 and S-OFF is still on, just install PB31IMG.ZIP again and all should be good. I believe at one point after it updates hboot it has to reboot to finish the install, so this might be what you are seeing.
4. Reboot, setup your google account, etc. (note first boot might take a few minutes and appear that your phone is stuck at the droid eye animation, be patient and don't do a battery pull)
5. Put the files I attached to this post on root of your SD-Card
***Files are PB31IMG.ZIP (this is not the update, either delete the other PB31IMG.ZIP or rename it to PB31IMG.BAK, this is just clockwork recovery in the PB31IMG.ZIP) , busybox.zip (remove the.zip extension, so the file is just busybox) ,payload-update.zip, and su-2.3.2.1-ef-signed.zip***
6. Power down phone and boot to hboot (hold optical button + power)
7. Install PB31IMG.ZIP in hboot, this installs clockwork recovery
8. Once that is done installing, press volume down, so your phone doesnt reboot, then select recovery
9. Once you boot into recovery choose install zip from SD-Card, then choose payload-update.zip
10. After that installs, choose to install another zip and install su-2.3.2.1-ef-signed.zip
11. Reboot and enjoy your rooted phone.
***Update*** I didn't realize busybox wasn't in the payload-update.zip I have attached it to this post. This site wouldn't let me post it without an extension, so rename busybox.zip --> busybox with no .zip extension. Also you can easily go to the market and download busybox, this requires root, which you will have, and it will install busybox for you after you click install.
Might as well put the usual disclaimer while I am editing this.
I take no responsibility for what you do to your phone, any issues, explosions, or bricks are caused at your own discretion.
Rom.zip will update the hboot, splash, OS AND Radio correct?
wpbear said:
Rom.zip will update the hboot, splash, OS AND Radio correct?
Click to expand...
Click to collapse
Yes
This updates your hboot to .92 and OS and I don't think the splash changes, but it is in the update. The radio will update if you don't already have the 2.15 radio installed.
Why can't we JUST flash the OS? I already have 2.15 radio, and I don't care about Hboot.
Can't we just flash the OS and leave everything else the same? Like other custom ROMs?
mobilehavoc said:
Why can't we JUST flash the OS? I already have 2.15 radio, and I don't care about Hboot.
Can't we just flash the OS and leave everything else the same? Like other custom ROMs?
Click to expand...
Click to collapse
You could, but this is just the way to do things now until someone puts out a rom. If you install this as-is, unrevoked 3 doesnt work anymore. This is a workaround to get root and recovery on your phone. I think the hboot .92 blocks unrevoked 3 from working, seems thats the part it failed for me was when it was in hboot. Of course we could always downgrade hboot.
mobilehavoc said:
Why can't we JUST flash the OS? I already have 2.15 radio, and I don't care about Hboot.
Can't we just flash the OS and leave everything else the same? Like other custom ROMs?
Click to expand...
Click to collapse
If you wait a little bit, I am 100% positive we will have that option. Give devs some time.
TNS201 said:
You could, but this is just the way to do things now until someone puts out a rom. If you install this as-is, unrevoked 3 doesnt work anymore. This is a workaround to get root and recovery on your phone. I think the hboot .92 blocks unrevoked 3 from working, seems thats the part it failed for me was when it was in hboot. Of course we could always downgrade hboot.
Click to expand...
Click to collapse
Ok, can't you just create an update with the system.img and flash that in Clockwork? Don't know enough about creating the package to do that but wouldn't that be all there is?
tats_06 said:
If you wait a little bit, I am 100% positive we will have that option. Give devs some time.
Click to expand...
Click to collapse
I know, like everyone else - the smell of a fresh leak is hard to resist. I can wait though. The 8/1 leak with some tweaks has been working great for me
mobilehavoc said:
I know, like everyone else - the smell of a fresh leak is hard to resist. I can wait though. The 8/1 leak with some tweaks has been working great for me
Click to expand...
Click to collapse
If you follow the guide above everything will be fine. Just you will have an updated hboot.
Anyone got a PB31IMG.ZIP that can downgrade hboot to .77?
I know its hard to resist installing a new leak, that's why I already did
TNS201 said:
If you follow the guide above everything will be fine. Just you will have an updated hboot.
Anyone got a PB31IMG.ZIP that can downgrade hboot to .77?
I know its hard to resist installing a new leak, that's why I already did
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=757927
Guys you gotta give devs time to DEVelope, and to POST there new stuff. this leak just came about last night.
if you notice this is the 4TH leak, AND like the 3 previous leaks, there has been ROMs built from the leaks, AND ROMs of the leak, so give it time, this is just for those who have S-OFF have no patience. and are WILLING and nice enough to test and share there information.
people with S-OFF have the option of doing this, and of coarse downgrading hboot, blah blah, if you don't want to deal with all that, (which is me) wait for the awesome devs to do there thing, and release there stuff. you know Adrynalye is all over this, and will have a 4th wave put out when he has the time. patience is a virtue. too bad me and most don't have much.
I just pulled a whopping 20.6 in Linpack...whoa, Nelly. I'm sure I'll get a speeding ticket with this beast!
(for those with are missing a sense of humor: I know, I just thought it was interesting)
TNS201 said:
If you follow the guide above everything will be fine. Just you will have an updated hboot.
Anyone got a PB31IMG.ZIP that can downgrade hboot to .77?
I know its hard to resist installing a new leak, that's why I already did
Click to expand...
Click to collapse
Why downgrade?
If you follow the guide above everything will be fine. Just you will have an updated hboot.
Anyone got a PB31IMG.ZIP that can downgrade hboot to .77?
I know its hard to resist installing a new leak, that's why I already did
Click to expand...
Click to collapse
Why downgrade?
Click to expand...
Click to collapse
he's assuming the downgraded hboot will work with unrevoked's tool
Ahh. I see. Thanks
obededom said:
I just pulled a whopping 20.6 in Linpack...whoa, Nelly. I'm sure I'll get a speeding ticket with this beast!
(for those with are missing a sense of humor: I know, I just thought it was interesting)
Click to expand...
Click to collapse
I got 34.246 MFLOPS
Using KiNgxKernel #3
I actually had to go back into HBOOT 3 times just to flash the initial zip. It had to update the bootloader twice with quick restarts for some reason, but then it continued the update fine after that. Scared me a little bit.
Question
I asked this in another thread, but this one seems to be a much more appropriate place to ask ... for those of us with SOFF but otherwise stock, is there a reason to go through the extraction/etc steps ... what is the downside of just running the RUU?
jdmba said:
I asked this in another thread, but this one seems to be a much more appropriate place to ask ... for those of us with SOFF but otherwise stock, is there a reason to go through the extraction/etc steps ... what is the downside of just running the RUU?
Click to expand...
Click to collapse
The RUU might not work, think some people tried and it didn't work. If you browse through the other post, you might be able to find someone who posted a link to download the rom.zip, but its really not that hard to do.
Nandroid Restore?
Thanks ... one more question.
If I try this, and hate it (or it turns out to be super buggy), can I restore a nandroid backup of my current setup (Radio 1.00.3.xxxx; HBOOT .77; Stock 2.1-Update) or will some of that not restore.
Thanks!
Those of us who flashed rootboot.img to install a rooted/insecure boot image were unable to update via the 2.3.1 OTA (Status 7 Error). A few different solutions have been posted. Here's one which worked for me, courtesy of momohammed20 and Luxferro:
Step 1: Restore the "2010-12-22.21.06.07" Nandroid backup which momohammed20 shared in this thread. That wipes your phone completely and gives you stock 2.3.1 without root.
Step 2: Follow the steps provided by Luxferro in this post. That gets you back root along with ClockworkMod Recovery.
Worked perfectly for me. Again, the solution is already out there in a few other threads, but I thought this deserved its own thread since a lot of folks have been stuck with the Status 7 error when trying to update.
Thanks again to momohammed20 and Luxferro!
Umm if we have 2.3 we can't nandroid a 2.3.1 backup. Ull get an error every time.
Sent from my Nexus S using XDA App
I followed these steps, and they worked nicely with no errors whatsoever. Others have done the same.
U were runninr2.3 rooted and then nandroid the 2.3.1 and u didn't get a MD5 error? Hard to beloved BC I've tried 5 times. Can anyone else try this out n let us know? ?
Sent from my Nexus S using XDA App
EDIT: just got it to work.. I re-downloaded it and it loaded. Seems the nandroid I dl from that thread the first time got renamed n it had a "(" in it, and recovery couldn't read the file...
Thanks alot tho, u were right!!
Sent from my Nexus One using XDA App
So will this allow the future flashing of OTAs without issue?
i also want to know if this will allow for future updates. i dont want to be reflashing my phone for every minor update.
Yes it will. The bootloader remains unlocked. But it restores everything to stock 2.3.1, and will have stock recovery, so next time there's a OTA it won't get an error when Its flashing BC u will be using the stock recovery n not CWR
Oh btw there's no root, in case u didn't understand what Stock 2.3.1 meant.
Sent from my Nexus S using XDA App
petep86 said:
Yes it will. The bootloader remains unlocked. But it restores everything to stock 2.3.1, and will have stock recovery, so next time there's a OTA it won't get an error when Its flashing BC u will be using the stock recovery n not CWR
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
From what I understand, the problem lies in the boot.img and not ClockworkMod.
TheBiles said:
From what I understand, the problem lies in the boot.img and not ClockworkMod.
Click to expand...
Click to collapse
What problem are u referring to?
That u can't ota the update??
Sent from my Nexus S using XDA App
petep86 said:
What problem are u referring to?
That u can't ota the update??
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
"Status 7" is the result of a rooted boot.img. It has nothing to do with ClockworkMod Recovery.
TheBiles said:
So will this allow the future flashing of OTAs without issue?
Click to expand...
Click to collapse
I don't know about that. For this particular OTA, it seems that the problem was the root boot. The method in the OP addresses that. However, I wouldn't assume that the next OTA will be compatible with a rooted device. My understanding (and I am no authority) is that the only way to know you're going to be getting OTAs is to revert to full stock. My intent was to have root and recovery in 2.3.1, not to get back to stock and stay there.
Wish this was posted this morning before i gave up
between some people getting it to work and other not working. People posting methods with stock boot.img but come to find out it wont work with rootboot....ect
Then realizing some people are on one root method while other used another...too confusing and i gave up after countless tries and gave and flashed modaco GRH78 r2 and glad i did because its pretty good..
IMO guys if this is going to require to you wipe your data save your self from headaches and just flash modaco GRH78 r2 with supercurio's EXT4 tweak it also rooted has new market and other fun stuff
demo, that's a good point. I'm using the r2 MoDaCo ROM now - it seems very good!
Amin Sabet said:
I don't know about that. For this particular OTA, it seems that the problem was the root boot. The method in the OP addresses that. However, I wouldn't assume that the next OTA will be compatible with a rooted device. My understanding (and I am no authority) is that the only way to know you're going to be getting OTAs is to revert to full stock. My intent was to have root and recovery in 2.3.1, not to get back to stock and stay there.
Click to expand...
Click to collapse
Nope, that is false. I had initially used superboot to root my phone when I first got it (w/ the pre-rooted modified boot.img). And I still got the prompt for the update. It will just give you a MD5 mismatch error when you accept the prompt and try to update.
deleted (accidental double post)
Luxferro, I think you misunderstood what I wrote. I too was rooted and got the prompt for this particular OTA, and some folks who were rooted (without root boot) were able to apply the OTA without an error. What I was trying to say was that the only way to be sure that they can receive and apply all future OTA updates would be to revert to stock (or have a means to revert to stock).
the status 7 error is a result of the patch process not finding a proper checksum for the things its patching if you have deleted system/framework apk's/odex's de-odexd the system/framework themed the system/framework changed the kernel this will cause status 7 error and will give you a hint on where the issue lies i.e. it will say somthing about calculator not match if you deleted it and error code 7
All,
I want to install the WWE_2.30.405.1 OTA upgrade that arrived yesterday but when I tried, it failed, so I need some help.
I have an IncS that came with Froyo and which I then upgraded OTA to gingerbread when it arrived.
I later unlocked with AplhaRevX and installed Clockwork Recovery, then rooted by following the great guide in the dev section.
I don't really care about S-OFF, clockwork or root anymore, been there done that, didn't really make much difference to what I want to do with my phone, so if I have to reset to a stock S-On phone with standard recovery etc then thats fine.
Can anyone help?
This is what I tried, but it didn't work...
Last night I got an OTA notification that there was an update, so went ahead and tried the install.
When it rebooted I got a a boot screen with an exclamation mark in a triangle and the Android guy. Then nothing..
After about 20 minutes I decided to take out the battery and reboot, that got me back in and my phone is working now, but without the upgrade, so now I'm here looking for help.
You can upgrade with the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_signed.
Donwload link on the forums.
Thanks, just found the link, but the hosting server is currently down so I can't test. Will post results when I can get the file and know what to do with it.
Some more questions...
The link is in the form of a windows EXE which makes me somewhat nervous.
I've only ever installed andoid rom's via the OTA update process, and so I'm not sure what I should do with this file.
I'll download later and see if I can figure it out, but have you explicitly tried this with the combination I have listed above?
I have a working phone right now so I'm not interested in anything that is untested.
Looking at other threads with the combination I have listed above, but applied in a different order, people have needed to resort to XTC-Clips to recover, I won't be able to do that so I need to fix this in software only.
abcprice said:
Thanks, just found the link, but the hosting server is currently down so I can't test. Will post results when I can get the file and know what to do with it.
Some more questions...
The link is in the form of a windows EXE which makes me somewhat nervous.
I've only ever installed andoid rom's via the OTA update process, and so I'm not sure what I should do with this file.
I'll download later and see if I can figure it out, but have you explicitly tried this with the combination I have listed above?
I have a working phone right now so I'm not interested in anything that is untested.
Looking at other threads with the combination I have listed above, but applied in a different order, people have needed to resort to XTC-Clips to recover, I won't be able to do that so I need to fix this in software only.
Click to expand...
Click to collapse
what you need to do is just to download the latest Ruu v2.30.405.1, connect ur phone to computer, double click the EXE file that you downloaded to run the Ruu program on a winxp/win7, click the confirm or ok button ,then you'll get what you want in about 15mins...remember not to do anything on ur phone or computer during this period.
OK Great. Will do as soon as I can download from filefactory again.
Again though I want to know has anyone tested this process and what will state will my phone be in when it is complete?
Just want a bit of reasurance that someone has actually done this with an AlpharevX S-Off phone and clockwork recovery installed.
abcprice said:
OK Great. Will do as soon as I can download from filefactory again.
Again though I want to know has anyone tested this process and what will state will my phone be in when it is complete?
Just want a bit of reasurance that someone has actually done this with an AlpharevX S-Off phone and clockwork recovery installed.
Click to expand...
Click to collapse
Those that were able to download the 2.30 RUU before the file server went down have reported that after upgrading to 2.30 AlphaRevX is no longer able to successfully run and S-OFF this version even though the HBOOT loader appears to be identical to the 2.12 RUU. If you currently have S-OFF and wish to retain it, then you shouldn't install the 2.30 RUU. You should wait for someone to build a rooted version of this ROM.
Or S-OFF with old rom, install ARHD 1.1.0 (2.30.405.1 based) and after the radio .06.03.03_M.
This is the right way.
tpbklake said:
Those that were able to download the 2.30 RUU before the file server went down have reported that after upgrading to 2.30 AlphaRevX is no longer able to successfully run and S-OFF this version even though the HBOOT loader appears to be identical to the 2.12 RUU. If you currently have S-OFF and wish to retain it, then you shouldn't install the 2.30 RUU. You should wait for someone to build a rooted version of this ROM.
Click to expand...
Click to collapse
OK Thanks.
Do you have a link to someone 'reporting' that they tried the RUU on a phone with AlphaRevX S-Off and Clockwork?
Not worried about losing my S-Off status or root, I want my phone to be able to take OTA updates again, in fact if I could restore to the state it was in before I unlocked, then that would be best of all.
Also anyone willing to post a copy of the RUU somewhere else for download, cos the filefactory link still seems to be down.
abcprice said:
OK Thanks.
Do you have a link to someone 'reporting' that they tried the RUU on a phone with AlphaRevX S-Off and Clockwork?
Not worried about losing my S-Off status or root, I want my phone to be able to take OTA updates again, in fact if I could restore to the state it was in before I unlocked, then that would be best of all.
Also anyone willing to post a copy of the RUU somewhere else for download, cos the filefactory link still seems to be down.
Click to expand...
Click to collapse
Here is a thread that discusses flashing the RUU and the attempts of AlphaRevX:
http://forum.xda-developers.com/showthread.php?t=1153871
OK That thread is all about how it didn't work, and the download site is still broken, so I'm not going to try anything for now.
I'll be away with work next week and need my phone to work, so I'll look in again when I get back and see if anything has changed.
Thanks for all your help anyway, I don't think this thread actually got even close to answering my question, but at least you tried.
If I try flashingthe RUU file then I'll be sure to let you know how it turned out.
Bye for now.
abcprice said:
OK That thread is all about how it didn't work, and the download site is still broken, so I'm not going to try anything for now.
I'll be away with work next week and need my phone to work, so I'll look in again when I get back and see if anything has changed.
Thanks for all your help anyway, I don't think this thread actually got even close to answering my question, but at least you tried.
If I try flashingthe RUU file then I'll be sure to let you know how it turned out.
Bye for now.
Click to expand...
Click to collapse
The point of mentioning that thread was that these users had previously used AlphaRevX to gain S-OFF and when they installed the 2.30 RUU and they lost root and S-OFF and they are now attempting to get S-OFF back which is the part that is failing.
OK So I'm back from my trip and today I had a chance to play with this a bit.
I downloaded this RUU http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1033922&v=1&libid=1310921120143&out=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d60f%2Fn%2FRUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe&title=%5BROMs%5DIncredible%20S%20Shipped%20ROMs%20Collection%20-%20xda-developers&txt=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d...308_signed.exe and tested an install.
I got what I wanted more or less, I have the update and all looks good..
However for those of you following from home, these are the trade-offs.
All data on my phone was erased. I had an 'out of box' experience when I booted the phone.
I lost S-Off status
I Lost root
I seem to have a corrupt recovery partition. (When I select recovery from the boot menu it hangs at a screen with a red triangle and an exclamation mark. Only way to boot the phone after that is to remove the battery and re-insert).
4 in particular bothers me a bit, as I'm not sure how to recover that and I'm not sure if I may need it in future. If you remember, what I originally wanted was to be able to get OTA updates in future, from reading around, I don't think that will be possible with a corrupt recovery image, so any tips on fixing that would be great.
Just download the latest or if you wanna keep s off a previous RUU from your carrier. And run the program it will return the phone to stalk
Sent from my HTC Incredible S using XDA Premium App
Hmm, thats what I think I've done.
My device is not tied to a carrier, so the WWE RUU Should have been the right one.
I have now also tried using fastboot to flash the recovery, but I get the following error
C:\Phone\>fastboot.exe flash recovery recovery.img
sending 'recovery' (3658 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
I tried with an older recovery from WWE 212 as well, but got the same error. Don't really know where to go next, but any help gladly recieved.
abcprice said:
OK So I'm back from my trip and today I had a chance to play with this a bit.
I downloaded this RUU http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1033922&v=1&libid=1310921120143&out=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d60f%2Fn%2FRUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe&title=%5BROMs%5DIncredible%20S%20Shipped%20ROMs%20Collection%20-%20xda-developers&txt=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc2d...308_signed.exe and tested an install.
I got what I wanted more or less, I have the update and all looks good..
However for those of you following from home, these are the trade-offs.
All data on my phone was erased. I had an 'out of box' experience when I booted the phone.
I lost S-Off status
I Lost root
I seem to have a corrupt recovery partition. (When I select recovery from the boot menu it hangs at a screen with a red triangle and an exclamation mark. Only way to boot the phone after that is to remove the battery and re-insert).
4 in particular bothers me a bit, as I'm not sure how to recover that and I'm not sure if I may need it in future. If you remember, what I originally wanted was to be able to get OTA updates in future, from reading around, I don't think that will be possible with a corrupt recovery image, so any tips on fixing that would be great.
Click to expand...
Click to collapse
That's not corrupt, that's what happens on stock
Ahh OK, if that is normal then how do I test that my recovery partition is good? I don't want to get buggered when the next OTA comes along.
Telstra ROM showing update available to ICS
System upgrade to 3.44.841.3
Anyone else getting this?
My phone is on the standard Telstra ICS ROM, however is S-off and unlocked... and has recovery if I update will this bork my phone?
Download Here https://docs.google.com/open?id=0B_yipCshKsIQa3B6bHl6UnVDMGs 58.8MB
I upgraded to this about 2 days ago, admittedly on a stock Velocity....rumblings seem to say that this is a radio fix from Telstra only at this stage (and an unsuccessful one at that)
Ah righto, I attempted applying it but it just made my phone display a belly up android with a hazard sign sticking our of its belly, I'm uploading the file now for people to play with should be done soon :laugh:
I did the upgrade on stock too, any idea what it was supposed to fix? I've yet to notice any differences, not that I noticed any problems before...
Sent from my HTC Velocity 4G using xda
I do believe this article may enlighten you.
Not sure.. That's really for the nexus in US only. Maybe related...
One thing I just noticed with this update is that it finally muted the camera sounds when the phone is on silent
Leigh Kennedy said:
I do believe this article may enlighten you.
Click to expand...
Click to collapse
I'm not sure that's it. The patent in my understanding is about apps/contacts/other stuff showing up in the universal search, which mine still does after the update.
Update fails. any hints welcome
I have a Velocity with the OTA 4.0.3 ICS update. When I bought it I tried to root it using hansoon2000s 1 in all kit. I did unlock the bootloader, but attempts to gain root access failed so at that time I relocked the bootloader and just forgot about it.
When I try to install the 3.44.841.3 update, the phone shuts down then reboots to the FASTBOOT menu which gives me the option of
BOOTLOADER,
REBOOT,
REBOOT BOOTLOADER or
POWER DOWN
and it shows at the top *RELOCKED*.
If I select BOOTLOADER I go to the HBOOT menu and I can see
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
I have limited skills but I am guessing if I got to the recovery menu I would be able to choose a zip file to run and I could point it at the OTA zipfile which it downloaded, but when I go to recovery it just goes back to the FASTBOOT menu.
Any ideas which course of action I should take. Because it's not rooted I don't have a good backup of app data so I'd really prefer not to take any action which is going to set the phone back to Factory unless I am fairly certain of the outcome. I'm still not even sure that I need to apply this update because I have no issues with my phone (but just for the sake of the exercise lets presume I'm trying to load a Jellybean OTA update, which is something I definitely would want to do even if I reset the phone).
Ideas or suggestions ?
Bro use all in one to unlock bootloader from the menu your talking about select recovery then when it boots into a recovery you chose from the all in one use the volume to navigate to the zip file there's a prerooted gb one that I'm using then once you install it and phone reboots let the phone update to ics
Sent from my HTC PH39100
I've got a feeling that this may have updated the Velocity to a custom hboot version, because now I'm having all sorts of trouble with custom kernals and roms. Investigating now to make sure it's not my own derpiness that's causing this.....
Demomanca said:
I've got a feeling that this may have updated the Velocity to a custom hboot version, because now I'm having all sorts of trouble with custom kernals and roms. Investigating now to make sure it's not my own derpiness that's causing this.....
Click to expand...
Click to collapse
Yeah same thing happened to me because of using a deodexed rom, but you can get it fixed pretty easily.
Only problem is I don't know how to get the update to work with the stock rom as i doesn't keep. I assume leigh kennedy knows how to apply the update to stock rom and then deodex, as he did it the for stock. Hope he does it for this too.
does anyone know exactly what the update does or are we all in the dark about it? It looks like its just an update to a few APK's, using my
*mad grand karate master winzip skillz, yo*
Is it a radio fix or what?
davidcampbell said:
does anyone know exactly what the update does or are we all in the dark about it? It looks like its just an update to a few APK's, using my
*mad grand karate master winzip skillz, yo*
Is it a radio fix or what?
Click to expand...
Click to collapse
Google result said the update was to fix radio reception issues for some users, I think it was mentioned on whirlpool and a telstra support site.
OTA update.
Hi I also have received the notification for an OTA update with a link to HTC.com for my Velocity 4G, But I am running "nightly Build 4" since it came out and it is running like a dream. I also got the error msg with Mr android, belly open and a triangle warning sign. Not surprised tho. However I am thirsty still and ofc with Jelly Bean bouncing in I am tempted to flash the new ROM when it is avail.. Any ideas when it will be? :fingers-crossed:
How can I flash this OTA manually?
My Velocity is stock non rooted an locked.
The phone is stuck at the HTC screen so really only have access to fastboot...
Also, does anyone have the stock build.prop for the velocity 4g?
Ryyuu said:
How can I flash this OTA manually?
My Velocity is stock non rooted an locked.
The phone is stuck at the HTC screen so really only have access to fastboot...
Also, does anyone have the stock build.prop for the velocity 4g?
Click to expand...
Click to collapse
If you have access to fastboot, try running the RUU while connected in fastboot (drivers must be installed). This will put the phone back to a factory state, then you can check for and install the OTA
Any word on this coming to rogers? I would hate having to revert to stock to accept the update
Screw the update lol
Sent from my Holiday using xda app-developers app
Homeslice's PACman ROM doesn't prompt me for an update
Sent from my Holiday using Tapatalk 2
I people!
I wanted to install the official update on my ICS 4 Incredible S that has the ClockworkMod recovery with the superuser and is S-ON.
I made an official OTA update but when I rebooted the phone it locks and stays with the symbol android with a triangle with an exclamation .The phone is unlocked by HTCDev.com. I am back to putting everything as it was with the ClockworkMod recovery. Can you help me to perform the update? Thank you for your attention.
The reference in HBOOT will attach.
View attachment 1201873
Figas said:
I people!
I wanted to install the official update on my ICS 4 Incredible S that has the ClockworkMod recovery with the superuser and is S-ON.
I made an official OTA update but when I rebooted the phone it locks and stays with the symbol android with a triangle with an exclamation .The phone is unlocked by HTCDev.com. I am back to putting everything as it was with the ClockworkMod recovery. Can you help me to perform the update? Thank you for your attention.
The reference in HBOOT will attach.
View attachment 1201873
Click to expand...
Click to collapse
subscribed to your thread as i am in the same situation as you are,
unrooting and relocking bootloader did not help.
Figas said:
I people!
I wanted to install the official update on my ICS 4 Incredible S that has the ClockworkMod recovery with the superuser and is S-ON.
I made an official OTA update but when I rebooted the phone it locks and stays with the symbol android with a triangle with an exclamation .The phone is unlocked by HTCDev.com. I am back to putting everything as it was with the ClockworkMod recovery. Can you help me to perform the update? Thank you for your attention.
The reference in HBOOT will attach.
View attachment 1201873
Click to expand...
Click to collapse
In order to apply the OTA you will need to return to a fully stock state. Locked bootloader and replace ClockworkMod with the stock HTC Recovery.
tpbklake said:
In order to apply the OTA you will need to return to a fully stock state. Locked bootloader and replace ClockworkMod with the stock HTC Recovery.
Click to expand...
Click to collapse
Thanks I'll try and see what happens, then I say anything.
Thank you
I have just been through this too.
Firstly I'd say be careful, ICS for me was not good - bluetooth connections were very fragile (sometimes did not auto-connect when the other device was turned on, and then when it did connect, the phone did not disconnect when the other device turned off. At this point trying to go into the phone bluetooth menu to cycle bluetooth off or manually disconnect caused the phone to crash. I even performed a factory re-set and it was the same)
But if you want to go ahead anyway, it's possible you may also need to have a standard system (un-rooted). Before I performed my update I flashed a standard system.img with fastboot. I'm not saying you will have to do this for sure, but for me since I was already flashing standard recovery.img with fastboot it was no bother to also restore the system.img - so it's just something you can try if your update doesn't work.
dingers01 said:
I have just been through this too.
Firstly I'd say be careful, ICS for me was not good - bluetooth connections were very fragile (sometimes did not auto-connect when the other device was turned on, and then when it did connect, the phone did not disconnect when the other device turned off. At this point trying to go into the phone bluetooth menu to cycle bluetooth off or manually disconnect caused the phone to crash. I even performed a factory re-set and it was the same)
But if you want to go ahead anyway, it's possible you may also need to have a standard system (un-rooted). When I did the update I flashed a standard system.img with fastboot. I'm not saying you will have to do this for sure, but for me since i was already flashing standard recovery.img with fastboot it was no bother to also restore the system.img - so it's just something you can try if your update doesn't work.
Click to expand...
Click to collapse
Along with the system.img file, you should have also flashed the lib.img file. That may be the cause of the flaky issues you are having with BT connections.
tpbklake said:
Along with the system.img file, you should have also flashed the lib.img file. That may be the cause of the flaky issues you are having with BT connections.
Click to expand...
Click to collapse
Thanks for the info. I am interseted in your comment both to learn a little more about the software structure and also because it opens up an avenue where I may re-attempt the ICS upgrade. So for these reasons, please allow me to ask:
- Do you mean I should have flashed lib.img before the update? I suppose I must ask what exactly is the lib.img?
The reason I didn't was, as I was running from a standard HTC rom as a base, I was under the impression that I'd only need to revert the parts that I had changed..... which (I thought) were the system (because I rooted) and the recovery (because I'd flashed 4ext)... to bring the phone back to standard trim.
- Are you saying that I might still have ended up with a 'non-standard' lib.img prior to the ICS upgrade? and if so which process (the rooting, installing recovery, or the boot unlocking) causes that?
- Also for this to be the potential cause of problems after the ICS upgrade, that supposes that the ICS upgrade would not have included a 'fresh' lib.img. Without knowing what img.lib is I don't know if this is this likely.. anyone?
dingers01 said:
Thanks for the info. I am interseted in your comment both to learn a little more about the software structure and also because it opens up an avenue where I may re-attempt the ICS upgrade. So for these reasons, please allow me to ask:
- Do you mean I should have flashed lib.img before the update? I suppose I must ask what exactly is the lib.img?
The reason I didn't was, as I was running from a standard HTC rom as a base, I was under the impression that I'd only need to revert the parts that I had changed..... which (I thought) were the system (because I rooted) and the recovery (because I'd flashed 4ext)... to bring the phone back to standard trim.
- Are you saying that I might still have ended up with a 'non-standard' lib.img prior to the ICS upgrade? and if so which process (the rooting, installing recovery, or the boot unlocking) causes that?
- Also for this to be the potential cause of problems after the ICS upgrade, that supposes that the ICS upgrade would not have included a 'fresh' lib.img. Without knowing what img.lib is I don't know if this is this likely.. anyone?
Click to expand...
Click to collapse
OK, I think I misunderstood at which point you flashed the system.img. I thought you had flashed the ICS system.img manually to force the OTA, not that you had flashed the system.img from the RUU/ROM you were currently running. My mistake.
Anyway, since you are eager to learn, hopefully this will give you some answers to your questions. Please reference this diagram from the BlackRose 2.02.0002 thread and perhaps my comments will make more sense.
http://forum.xda-developers.com/showpost.php?p=22789898&postcount=2
If you look at the contents of a RUU/ROM.zip file, you will notice that it contains various img files such as system.img, radio.img, recovery.img, boot.img, etc.
These represent partition of Android. Beginning with GB 2.3.5/Sense 3.0 ROMs, HTC decided to split the system.img into 2 parts, system.img and lib.img.
From the diagram, you can see that lib.img file actually gets mounted as the /system/lib directory, therefore if you flashed the system.img manually as part of trying to get the OTA going, you should also flash the corresponding lib.img so that you have a complete /system structure.
SOLVED
20545ZR16 said:
subscribed to your thread as i am in the same situation as you are,
unrooting and relocking bootloader did not help.
Click to expand...
Click to collapse
tpbklake said:
In order to apply the OTA you will need to return to a fully stock state. Locked bootloader and replace ClockworkMod with the stock HTC Recovery.
Click to expand...
Click to collapse
Figas said:
Thanks I'll try and see what happens, then I say anything.
Thank you
Click to expand...
Click to collapse
Is solved, I installed the stock HTC Recovery, locked bootloader and installed RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M
Everything worked perfectly.
Thank you for your help.
Hugs to you all