Related
alrighty so here it is the ota is coming and i silly as i may be rooted like 3-4 days ago. i didnt take the time to s-off just got the custom recovery updated the radio to 2.05 and downloaded sky raider vanilla. hboot is .79.
now from my research that ive gather and correct me if im wrong but all i need to do is :
*s-off
*flash the stock recovery
after that i should be good for the ota correct?
so far i got the s-off done looking for a lil bit of instruction as to how to get the stock recovery flashed safely.
Any and all help is greatly appreciated i thank you all very much.
inessi said:
alrighty so here it is the ota is coming and i silly as i may be rooted like 3-4 days ago. i didnt take the time to s-off just got the custom recovery updated the radio to 2.05 and downloaded sky raider vanilla. hboot is .79.
now from my research that ive gather and correct me if im wrong but all i need to do is :
*s-off
*flash the stock recovery
after that i should be good for the ota correct?
so far i got the s-off done looking for a lil bit of instruction as to how to get the stock recovery flashed safely.
Any and all help is greatly appreciated i thank you all very much.
Click to expand...
Click to collapse
I have attached the stock recovery that needs to be flashed from the HBOOT.
It is my understanding however, that you need to downgrade to the .77 HBOOT, 1.xx radio AND 2.1 system for the update to notify you, give you the option to download, and install successfully. However, I am a few drinks into my night.
If you choose to follow that path. I suggest you read this
awesome stuff really appreciate it man gonna give it a try now, fellow floridian lol
inessi said:
awesome stuff really appreciate it man gonna give it a try now, fellow floridian lol
Click to expand...
Click to collapse
w00t!
If you get hung up anywhere, pm me and I'll give you a number to call me at in the morning/afternoon and I'll walk you through it.
your my hero bud, my freaking hero stock recovery got s-off i think thats all i need to recieve the ota and do it yea?
thnx
See, from this point, I'm not sure if you need the .77 HBOOT 1.xx Radio and 2.1build-1 on your phone (I'm really questioning it, as I beleive I read in a few places that you do, but I'm not sure at this point in the evening). I don't think the Skyraider rom will get a notification when the update is available. I'd say if you don't get a notification for the update when everyone else in the free world is, then you may have to.
As long as you have S-OFF, it doesn't matter either way, you have complete control for the rest of your phone's life. Whatever you do, don't turn it back on lol.
hmmm well if it doesnt show up guess my next set of questions is how to get back to stock everything
inessi said:
hmmm well if it doesnt show up guess my next set of questions is how to get back to stock everything
Click to expand...
Click to collapse
The link I posted above with the "I suggest you read this" line is where you will need to go if it boils down to that.
o haha some how i missed that lil section of text did you just add that recently?
but ok sounds good ill run through it in the morning probably
and holy crap the link you posted makes this all look so simple hah
Well I have stock everything, except for my hboot is .79, im on stock 2.1 stock recovery just have .79 hboot not .77, i think i will still get the update though...
rdmerck said:
thnx
See, from this point, I'm not sure if you need the .77 HBOOT 1.xx Radio and 2.1build-1 on your phone (I'm really questioning it, as I beleive I read in a few places that you do, but I'm not sure at this point in the evening). I don't think the Skyraider rom will get a notification when the update is available. I'd say if you don't get a notification for the update when everyone else in the free world is, then you may have to.
As long as you have S-OFF, it doesn't matter either way, you have complete control for the rest of your phone's life. Whatever you do, don't turn it back on lol.
Click to expand...
Click to collapse
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?
magneto417x said:
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?
Click to expand...
Click to collapse
Other than the root, did you modify anything else to your phone?
If not, your still with the .77 HBOOT, 1.xx baseband, and 2.1update-1 system?
Add unrevoked forever to remove s-off, then flash the stock recovery back to your phone. Your goal here is to have S-Off
in order to get the OTA (from my understanding) you need the stock recovery, do a little search I have all the faith in the world that you will find what you are looking for. you want to run unrevoked forever BEFORE you accept the OTA2.2, so this is your steps, root, run unrevoked forever getting S-OFF, find the file for the stock recovery, PB..IMG file, flash that in hboot, this will set u back to stock 2.1 update1, stock radio, stock recovery, but still have S-OFF to regain root, after the OTA comes.
So if I have stock everything, and have hboot .79 will I still get the OTA I don't see why not...
BlazeD OnE said:
in order to get the OTA (from my understanding) you need the stock recovery, do a little search I have all the faith in the world that you will find what you are looking for. you want to run unrevoked forever BEFORE you accept the OTA2.2, so this is your steps, root, run unrevoked forever getting S-OFF, find the file for the stock recovery, PB..IMG file, flash that in hboot, this will set u back to stock 2.1 update1, stock radio, stock recovery, but still have S-OFF to regain root, after the OTA comes.
Click to expand...
Click to collapse
Currently the only thing I have done was rooted and removed CityID and but have not changed the radio or anything else. I have installed Unrevoked forever now. So do I still need to flash stock recovery even though I haven't changed the boot files or radio files at all?
Yes from what I've read you HAVE to have the stock recovery. what is your HBOOT once u get stock recovery?
BlazeD OnE said:
Yes from what I've read you HAVE to have the stock recovery. what is your HBOOT once u get stock recovery?
Click to expand...
Click to collapse
My HBOOT is 0.79.0000
Radio 1.00.03.04.06
Any input would be helpful as to whether I will get OTA or do I need to do something.
once in hboot, go to recovery, if you have clockwork you wont get it i dont think, if you get a red triangle you have stock recovery and you are good to go.
magneto417x said:
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?
Click to expand...
Click to collapse
Yes, install unrevoked forever. The fact that you are rooted will not affect the ability of your upgrade, it is the lack of the stock recovery that will halt you.
Unrevoked forever will allow you to flash ANY zip file you want to the phone (namely a zip that has su and Superuser.apk) and will allow you to regain root in the event that it is ever lost due to an OTA or user error.
S-OFF is a beautiful thing.
I would love to take my phone to Verizon right now with a manufactured problem, let him see the Superuser, official 2.2 system and then stock recovery. Could be priceless!
I have an HTC Incredible that i ran the first unrevoked2 update to get root on my device, then unrevoked3 to get s-off. I then was pushed the 2.2 OTA update, which when done through the phone fail. So, like an idiot of course, I ran the update.zip from clockworkmod and now my device is acting all strange (practically bricked).
After the update, the 'droid' eye loads, then goes to a white HTC page where a small dialogue box goes from 0 to 95% then reboots, repeatedly, until I interrupt this via a battery pull. I then get into my phone, but the camera, sdcard, wifi, etc are not recognized. Eventually I get a force close prompt for 'system' which I can wait or force close, either choice, my device will reboot at max 5 minutes.
I have the following showing at HBOOT
Incredible XC Ship S-ON (i ran the s-on update now)
HBOOT-0.77.0000
...
RADIO-2.15.00.07.28
I'd like to get my phone either running Froyo, or back to the stock ROM, and am in need of help. I've ran several PB31IMG.zip files located through numerous guides and dozens of searches to try and get back to stock, but I either get 'update failed' because of some kind of version check, or the update doesn't work (maybe now because I'm s-on?).
I'm in sad need of help, I found another thread where someone else was in my similar situation on another forum but its old, no one is responding, and the update worked for them and not myself. I'd really appreciate it if someone would walk me through un-screwing my device if possible. Much appreciated.
alright well if i was you i would do this.
turn security back off (s-off)
grab the PB31IMG.zip for 2.2 froyo/ or if you want the ota again grab the 2.1
then it should work fine. but i also see the your hboot is not up to date for froyo so maybe find the PB31IMG.zip for 0.92 hboot. i dont have any idea about where it is located but i have the file for 2.2. but alas, i dont have a place to upload it soo yeeaaah. anyway that is what my first choice would be. choose to follow or not.
p.s. i know i say but alot haha
BTW yes, PB31IMG's wont work because you are s-on. and the ota probably did not work because you had clockworkmod recovery instead of stock recovery. thats all i got for ya. hope my terrible explanations help
Well, this might be more promising.
I did notice that my HBOOT was quite out of date, so amongst all of the files I've downloaded, I'm pretty sure the one that might have done it for me was the RUU update file. I of course re-ran the s-off update from unrevoked-forever, then started hacking away at the RUU update. I downloaded the RUU update from Google, ran it, copied the rom.zip file from the temporary files location, renamed it to PB31IMG.zip, copied it to the root, and then poof, noticed the HBOOT was updated (looks like this could have been the root problem).
Needless to say, i'm back to setting up my device (raw), hope that I can still get to root on my device; but at least I'm back to an operating phone!
OK
Looks like I'm at HBOOT-0.92.0000 with IncredibleC XC ship S-OFF still; RADIO-2.15.00.07.28.
Doesn't look like I have a recovery mode (clockworkmod).
I'm guessing if I'm going to root my device I'll need to re-install clockworkmod? Thanks for any future help.
so you still have the reboot thing, going on
Sent from my ADR6300 using XDA App
tjamscad said:
so you still have the reboot thing, going on
Click to expand...
Click to collapse
No, my device is unbricked (so to speak). Since updating using the full RUU it successfully re-flashed everything. Only problem I have to fix now is rooting my device again.
Well I guess I have my work cut out for me searching how to get my s-off phone rooted again. Anyone got a suggestion?
Sent from my ADR6300 using XDA App
if your phone is s-off then search around for a custom recovery in the pb31img format. flash in bootloader, reboot into recovery and flash the rooted rom of your choice.
So my fix was:
1. Ensure phone is already rooted and S-OFF
2. download RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28.exe
3. Run the RUU file
4. Go to my temporary files location, sort by date, and look for the rom.zip file
5. copy that file off someplace else and rename it PB31IMG.zip, cancel RUU Update program
6. Copy PB31IMG.zip to the root of the SD Card
7. Boot my device holding volume down (HBOOT)
8. Allow the update to proceed (will reboot phone almost immediately to update HBOOT from 0.77 to 0.92)
9. Once update was completed, phone reboots final time after prompt
10. Setup phone again (RUU Update is a clean flash)
Still looking out for better instructions on how to re-root my device other than a manual one, but if I must then I must =) Was hoping that I could use unrevoked3, but the last push didn't work out.
you have to do it manually cause unrevoked doest work on newest ota
I can help you reroot if you need it. Im glad you have everythig else worked out though. Congratulations!
sent from Ioslver
ok well basically load this in bootloader and you are rerooted.
the download link for the file is here:
http://www.mediafire.com/?oj6aqi1ceqpm58g
patalo said:
ok well basically load this in bootloader and you are rerooted.
the download link for the file is here:
http://www.mediafire.com/?oj6aqi1ceqpm58g
Click to expand...
Click to collapse
So that PB31IMG.zip (renamed) will re-install the most recent clockworkmod recovery? I saw some other post which also had a 'payload-update.zip' and a 'su-2.3.2.1-ef-signed.zip' file ... not sure if I'm missing something.
Also, according to their latest release (their = unrevoked), http://unrevoked.com/rootwiki/doku.php/public/unrevoked3 - This supposedly works with all versions of supported phones. Of course, when I go to http://unrevoked.com/rootwiki/doku.php/public/unrevoked2 it says that unrevoked3 doesn't work with stock Android 2.2 phones... which I'm guessing might be my condition since I had to flash the rom.zip file from RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe that I got from google.
Some clarification would be appreciated.
Looks like I'm back to root. Ran the PB31IMG.zip that was about 2.86mb, then payload-update.zip and the Su zip (anyone know where the most recent one is? Says there is an update).
Now to test WiFi tether again, see if I still need that evo driver still.
Sent from my ADR6300 using XDA App
You don't need the payload and stuff. After s-off all you need is the clockworkmod PB31IMG.zip to get root back
sent from Ioslver
The wifi tether has nothig to do with root. On some roms or just sometimes it wont work.
sent from Ioslver
I Have a Question, Would it be Possible to Root the Phone With a Update.zip From Android Recovery, Where it Says (Install From Update.zip)? Either That or Turn S-Off, Or Install Su, Clockwork Recovery...... Something? If Someone Can Help Please Do!! Or If Someone Can Try to Sign a Update.zip For Me With S-Off in it!! (Unrevoked.4Ever) I'd Loveto Find a Easier way that can be Done WITHOUT CONNECTING TO A (USB) PORT PC!!
Technically no. Because rooting your device is getting rid of the stock recovery so you can install rims and whatnot. But you can root through hboot easily with s-off or with s-on use unrevoked.
sent from Ioslver
So I'm wondering if the payload-update.zip was damaging in some way.
In any event, now I'm constantly being nagged about another 17.7mb update from Verizon which of course, like the Android 2.2 update, won't apply via the usual system update message.
I don't know where I can find this file, but it says this:
---
Android Update
Downloaded and verified 17.7 MB
This software update includes the installation of V CAST Apps, Slacker, and many other improvements for your DRIOD Incredible by HTC. ... blah blah blah ...
---
I don't know if this is the infamous 'November' update or not. I know that I updated my rom from the RUU file downloaded from dl.google.com, so its possible that I don't have this patching. Some clarification on what this download is, where I can find it (online or my phone), and if it is possible to apply this update and how (so I don't keep getting annoyed with it).
My wife got her replacement Inc2 today after the one she got last week just died. She was on Froyo so I might of.. swapped her phones.. anyways, I rooted, went to the bathroom and the stupid ota ran I guess because when I came back the phone was on GB 2.3.3 however my boot screen shows S-OFF. Can anyone help me to verify that S-OFF is indeed still off. I can post any screen shots etc.. I am still a noob when it comes to the Inc2.
If your boot screen says S-Off, you are S-Off
Sent from my stock, bloated ADR6350 using XDA Premium App
Did you flash clockworkmod recovery when you rooted? I didn't think the OTA would take if you had a custom recovery. In any event, since you're still s-off, you're fine.
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
kujayhawks77 said:
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
Click to expand...
Click to collapse
Alpharev changed ur hboot to a higer version than the one in the OTA.. this is why it kept you S-OFF.. if I'm wrong someone correct me.
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
kujayhawks77 said:
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
Click to expand...
Click to collapse
No. stock hboot is .97. alpharev bumped you up to 1.something.. idk I used XTC clip.. since your hboot is newer than the OTA.. it keeps you S-OFF, pretty smart by alpha.
So does this open a gateway to first root in Froyo and then go gingerbread and retain the root?
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Now when I use the term "gateway" I say this loosely because it doesn't fix anything for anyone who is already on GB. If indeed this works, it would only work for a small percentage who get Froyo and don't flash clockwork before running the OTA.
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
tnez said:
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
Click to expand...
Click to collapse
2.1??? I think you are mistaken, sir
beenz said:
2.1??? I think you are mistaken, sir
Click to expand...
Click to collapse
He was mistaken cause it is sense 2.1 but android 2.2
Sent from my Incredible 2 using XDA Premium App
kujayhawks77 said:
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Click to expand...
Click to collapse
I've been wondering about this. I got my Dinc2 early July and I'm still on stock, unrooted Froyo. Somehow the OTA update to GB hasn't hit yet. Could I run ApharevX to get S-off and stop there for now? I am happy with bloated stock for the time being and want to be able to receive OTA updates, but would like to have the option down the road to add Clockworkmod and flash custom ROMs. From kujayhawks experience it seems that this should be possible.
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
P.S. First post, though I've been lurking around for a while. Great forum/community.
xenakis said:
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
Click to expand...
Click to collapse
It appears from reports that S-off stays after the OTA to 2.3, so yea, that would seem to be the case.
If you turn S-off with AlphaRev, you might want to just go ahead and install Clockwork recovery at the same time. Doing so won't root or install SuperUser or anything, but you would be able to then backup your phone and be ready to flash if you wanted.
If you install clockwork recovery you won't be able to receive OTAs though, just keep that in mind. You can flash back to the stock recovery, but unless you are familiar with ADB, it won't necessarily be an easy process.
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
What problems are you having with the RUU that you flashed? You can't downgrade, as you found out, so being stock S-ON you don't have many options other than flashing a different 2.3 stock image, and/or waiting for the actual OTA.
resyek83 said:
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
Click to expand...
Click to collapse
The only way i know to get back to 2.2 is to s-off your phone then ruu the 2.2. which will get you back to s-on 2.2, but you will be get the update nag every day once they start pushing the OTA out again.
resyek83 said:
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
Click to expand...
Click to collapse
For the moment, I think you are SOL, only because the same thing happened to me.
If you have 2.3.4 and S-ON, there's not really a way to downgrade back to 2.2, as HBOOT won't allow a downgrade. In fact, only PB31IMG.zip files that are signed by HTC will allow to be flashed. All others will not be recognized by HBOOT.
Unrevoked will no longer root after you have flashed RUU and have S-ON. You will get the error you are describing.
I have also tried newer root tools, such as Revolutionary, which is in the Beta phase.
Unfortunately, this method is not supported for the Incredible, and per Unrevoked's support channel on IRC, this is not likely, as apparently a phone that is only over a year old is considered a 'Legacy' device.
At this point we can only hope for the following:
HTC unlocks the Bootloader for the Droid Incredible on HTCdev.com. Only a handful of devices are listed at the moment.
Team Unrevoked releases a new version of Unrevoked that can find an exploit for 2.3.4 and enable root.
Revolutionary adds support for 'legacy' devices such as the incredible.
We are in a small minority, but hopefully enough devices will get the OTA, or refurbs get sent out with 2.3.4 that users will eventually require a new way to root.
Hang in there.
Yeah, if you're s on then from everything I've read, your screwed for now.
ahh ok....yea i kinda figured. I should have done a tad more research before I did it....everything works ok at the moment, except my battery life isnt as good as it was, but its not terrible. I guess I'll wait for the official OTA or wait and see if Unrevoked can come up with a solution.
your best option woulda been to root first. While you still had S-off flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-on.
TheBr0ken said:
your best option woulda been to root first. While you still had S-on flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-off.
Click to expand...
Click to collapse
Doing that with S-On is what has OP in this position in the first place. You have the right idea but mixed up S-On and S-Off.
TheBr0ken said:
your best option woulda been to root first. While you still had S-on flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-off.
Click to expand...
Click to collapse
Thank you, Captain Hindsight. In my situation, I was coming from a Rooted, 2.3 Sense 3.0 ROM, with S-Off.
I believe S-off is swicthed back to S-ON when you flash the RUU.
In the mean time, my phone is borked. Too new of a firmware on too "old" of a device.
SlimSnoopOS said:
Doing that with S-On is what has OP in this position in the first place. You have the right idea but mixed up S-On and S-Off.
Click to expand...
Click to collapse
yup, fixed.
deadsoulboy said:
Thank you, Captain Hindsight. In my situation, I was coming from a Rooted, 2.3 Sense 3.0 ROM, with S-Off.
I believe S-off is swicthed back to S-ON when you flash the RUU.
In the mean time, my phone is borked. Too new of a firmware on too "old" of a device.
Click to expand...
Click to collapse
what killed you was you musta flashed the s-on patch for some reason. I ran the same file you did. I still have s-off
The RUU does NOT turn the security flag to -ON. You do lose root until you flash a custom recovery and superuser, which is done easily.
Any hope for us S-ONs with 2.3.4? Is there something by way of unrevoked or something we can flash to try and get back to root?
There has to be something...
So I have a droid inc that I'm sending back in, and I want to revert it to stock. Right now, I'm running s-off, with a rooted stock OTA 2.3.4 (Incubusj's, I think) with the latest CWM. What do I need to do to make this thing bone stock to return it? I've done a search, and maybe I just suck at searching, but I can't find good, concise directions, and I don't want to screw it up.
sk8erord said:
So I have a droid inc that I'm sending back in, and I want to revert it to stock. Right now, I'm running s-off, with a rooted stock OTA 2.3.4 (Incubusj's, I think) with the latest CWM. What do I need to do to make this thing bone stock to return it? I've done a search, and maybe I just suck at searching, but I can't find good, concise directions, and I don't want to screw it up.
Click to expand...
Click to collapse
Search for the Ultimate get back to stock thread. It'll tell you what you need to to to get back to Stock 2.2 with S-ON.
That thread seems rather old. I'm running the 2.15.10.07.07 radio on hboot .92. Do I still just run the s-on and then run the RUU?
Well, was probably unnecessary, but I reverted to the old radio, flashed a rooted stock rom, then ran s-on through recovery, then a stock pb31img rom through bootloader. So it is bone stock again.
sk8erord said:
That thread seems rather old. I'm running the 2.15.10.07.07 radio on hboot .92. Do I still just run the s-on and then run the RUU?
Click to expand...
Click to collapse
True, that thread is old, but the info is still good. Good call on reverting back the radio, as you don't want that to cause any troubles. Pretty easy to get back to stock and S-ON huh?
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