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!
Related
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?
Bros, please help
My Desire is running Froyo 2.2 and I rooted it.
There is an OTA today for version 2.29. I already download it. But when it restarted and installed, it failed with error like wrong signature or sth like that.
Please help me if you got any clue on this.
warmest regards,
Don't apply OTA updates on rooted devices, either use a custom rom which is based on 2.29 or use a 2.29 RUU and root again.
TheGhost1233 said:
Don't apply OTA updates on rooted devices, either use a custom rom which is based on 2.29 or use a 2.29 RUU and root again.
Click to expand...
Click to collapse
Exactly. I think you have too little knowledge of rooting. Don't even think about the word "official" when you rooted your phone.
Actually I toggled Sig off in Clockwork mod and
was able to install the update, it went well and the phone was working
fine, i did loose my root tho , so I had to root again....
I am a beginner, so don't take this as advice, cause I don't know
the downside off togling Sig off. I just wanted to state that in fact
it is possible to ota a rooted device..
grtz
Lanbase said:
Actually I toggled Sig off in Clockwork mod and
was able to install the update, it went well and the phone was working
fine, i did loose my root tho , so I had to root again....
I am a beginner, so don't take this as advice, cause I don't know
the downside off togling Sig off. I just wanted to state that in fact
it is possible to ota a rooted device..
grtz
Click to expand...
Click to collapse
Thx for your advice.
It's generally considered that if you're rooted you should not apply an OTA as you won't truely be back to 'stock' and it can cause issues further down the line. It can be done, though, as highlighted above but if people just used some common sense as opposed to just saying OK to any updates this question wouldn't get asked 30 times a day
Hi guys, I'm confused.
I have a stock HTC Desire on Orange with 2.10.405.2. I've been having problems with the radio (losing data connectivity but not showing it, text messages being delayed for hours, etc) and decided to root it with Unrevoked and put a new radio and RIL pack on. Well, I did that OK (although the connectivity problems persist).
The trouble is that now there's an OTA update to 2.29.405.2, which I would quite like to try out. When I tried to run it, Clockwork Recovery gave a signature check error.
Could someone explain how to fix this? I don't mind losing root, but I would very much prefer to run an update rather than flash a rom and lose everything on the phone! A clear description of what's going on would be appreciated, cheers!
I'm pretty sure, running the OTA would brick your phone,thats why it wont go through, what you need to do it, flash an Stock rom on your phone, then do OTA
Read the Wiki or Ask in the Desire forum for more help
Oh my, this reply came in just after I had managed to start an update (by moving/renaming the update file to update.zip in the root directory and using clockwork recovery). And as I read the update, the phone had been on the HTC splash screen for quite some time...
I almost had a heart attack.
But it's booted now The update failed due to not having enough free memory.
I suppose I'll just have to back up what I can and flash the stock rom. It's really annoying that rooting the phone in order to give me more flexibility has taken away the option to update painlessly.... That is, unless someone can point me towards a rooted update file?
Oh, the radio I updated to was Radio Froyo 5.11.05.27 (I flashed the RIL zip file separately), I am not sure how much that could affect things.
too bad that my phone had enough memory and now I'm trying to flash a stock rom.
The 1st one I tried was 2.09, and it failed saying kind of "invalid ruu version".
Now downloading 2.29.....
I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,
Kokuyo said:
I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,
Click to expand...
Click to collapse
Why did you root your phone? There is no need to update your phone to the latest OTA update if you are wanting to install custom ROMs.
Because I was testing custom mods and wanted to go back to stock?
Kokuyo said:
Because I was testing custom mods and wanted to go back to stock?
Click to expand...
Click to collapse
ahhh, I thought you had just rooted it. I updated the day after I received my new phone. I had problems with bluetooth (music wouldn't resume after ending phone calls) and wound up here on the XDA forums looking for answers. I ended up rooting my phone, installing CM6 and now CM7 and never looked back. There is no bluetooth switching problems using CM builds so I'm happy.
Found this:
http://www.thinkthinkdo.com/trac/project1/wiki/back_to_stock
Thanks, that looks interesting. Now the only question: Do I need my original CID? And if so, how do I find it now that the CID has been changed by gfree?
That link is about a procedure to restore the stock G2 ROM. Since you seem to have a DZ ROM, I'm not sure if you want to flash a G2 ROM (though the other bits might be useful).
The 1.72 OTA update has been rootable for some time now, so you can safely accept the update if you want. But it might be easier just to flash the 1.72 ROM in its entireity (you can get it from the dev forum).
With SuperCID and S-OFF you should have no problems flashing 1.72.
steviewevie said:
With SuperCID and S-OFF you should have no problems flashing 1.72.
Click to expand...
Click to collapse
Really? Then I don't quite understand the stickied warning thread that says to never, ever attempt that.
Anyhow, I gave the Virtuous mod another go. Since it has sense and 1.72 I'm thinking of testing this one out a bit more, before I go flashing stock.
Thanks for the replies, though.
Hi,
Using the search option gives me temporarily not available... So don't blame me if there already was a topic about it
I'm on android 2.2, rooted and S-OFF and changed a couple images here and there, some stockappsn removed, but nothing big.
So, I got a prompt to install systemupdate 2.3
My question is: can I do this safely while my DHD is rooted and all? Or do I need to restore my phone back to stock-version? I remember that updating from (i believe it was) 2.1 to 2.2 it errored because it verified all the files on it (and it failed because I had some **** tweaked). Will this happen to me (and leaving me with a brick maybe)?
Thanks !
Maurice
im not 100% sure, i've heard different people say different things.
In my opinion, i dont think anything will happen, but i havent tried it so....
but if it does work,..., you will lose root for sure.
what i did is downloaded a stock-rooted ROM from HERE. - this is the official update, but just modified to be rooted. check it out.
i just flashed it with CWM recovery