[how to] manually update to ICS without losing data
first and foremost,id like to apologize to anyone whom ive told it does not matter if you have apps deleted. during this little experiment,i have found that to not be the case. the updates will fail,if they try and apply a patch file to an app or file that is not present.
it does not appear to matter if things have been frozen. freezing bloatware makes it invisible to the app drawer and not useable,but does not delete it from system files.
first time i tried it,i went thru and deleted a bunch of files. update failed. crap! second time,i froze a few and things seemd to go fine. i only froze a few in the interest of time,so if anyone has any different expereinces,please let us know
so,if youve actually deleted system files or apps,the process will be a little longer if you want to update and preserve your curent setup.
WARNING!i am not responsible if this melts your phone into a smoldering pile of goo. you took on the responsability of owning a rooted devices the instant you rooted it.
I HAVE TESTED THIS on my s-off phone. i updated using this method several times in attempt to make sure it worked predictably. however,lots of folks seem to be having prollems with it,and i have no idea why. procede at your own risk! it may work fine,,or it may result in issues that we do not understand or have answers for,resulting in the need to run the full 3.14.605.12 ruu,wich will wipe your data.
prerequesites:
-that you have rooted with my guide,or are at least familiar with the "miniadb" folder i use in my guides. if not,read thru the root guide and get it set up. Scottys noob friendly root guide-start to finish
-that you are somewhat familiar with amon recovery menu navigation(exact menu options and selection are not given)
before you start:
*check your hboot version. you must be on on the most current firmware and software to manually apply the updates,or recieve the OTA.
if you are on hboot version 2.10,you are on older firmware and must update fully to 2.01.605.11(containing hboot 2.11). substitute step 2) for the step 2) in post #2
1)download files everyone:VIGOR-manual-ICS-update.zip
md5: VIGOR-manual-ICS-update.zip b2e94b379f1df696a35dde0581f5eb06 (double check,please )
extract it to somewhere convenient. stock recovery and amon are included in this download. move them to mini-adb_vigor if needed. the OTAPkg files are the important ones.
*make a backup of your data partition using amons menu options on the phone screen. simply remove the X's from everything but data on the backup screen,then "perform backup". you do not need to backup boot or system. you may also want to perform a full backup in case something goes wrong,but this is optional.
-using the phones amon ra menu options,flash "SetMainVersionLOW.zip" just like you would any other rom. no need to wipe anything,just flash it.
-boot back into bootloader adb reboot bootloader
-check main version fastboot getvar all
-if your main version is now 1.00.000.0 then procede:
-erase cache fastboot erase cache
-enter "RUU mode" : fastboot oem rebootRUU
run mini ruu: fastboot flash zip miniRUU2.01.605.11.zip
-reboot to fastboot fastboot reboot-bootloader
-reboot the phone fastboot reboot
your phone wil reboot to a freshly factory reset state. chose language,sign into google,etc. give the phone a few minutes to sync and settle. turn off "fastboot" in settings/power,enable usb debugging in settings/apps/development
now restore your data by:
reopen your cmd window,and change back to mini-adb_vigor directory if needed. then:
-using the amon recovery menus,wipe cache,wipe dalvik cache. flash superuser. if superuser aborts, reboot,and try again.
-once superuser flashes successfully, you can restore your data. select your data only backup from the restore menu. remove the X's from everything but data.
-once the restore is complete,reboot. give the phone a few minutes to settle. skip ahead to step 4,since you have the stock recovery
3)install the stock recovery if needed
*if you have only temp installed amon,you should still have the stock recovery in place. skip ahead to step 4
otherwise,reopen your cmd window,and change back to mini-adb_vigor directory if needed. then:
-place OTAPkg_stage1 onto the root of your sd card. rename it to "update"
-boot to the factory recovery via adb reboot recovery (optionally,you can select recovery from the hboot menu if you dont wish to use cmd)
-youll see a yellow error message about cache. dont worry,this is normal
-hold vol UP and power until you see blue writing that is the stock recoverys menu
-using the vol rocker and power button,wipe cache
-select apply update from sd card
-choose "update.zip"
*sit your phone down and let it do its thing. youll see yellow writing as the update applies patch files,then a couple different screens as it makes firmware changes. as long as your stock rom isnt heavily modded,the update will get you ready for ICS,and update your main version to 2.01.605.12.
*if you see an "install aborted" error message,make note of what it is,and reboot using the stock menu option
-when the updates are finished,the phone will reboot. it wont look any different,and youll have lost your root access. thats ok for now. give the phone a few minutes to settle.
-remove "update" from the sd card.
-place "OTAPkg_stage2" onto the root of the sd card. again,rename to "update"
-boot to the factory recovery via adb reboot recovery (optionally,you can select recovery from the hboot menu if you dont wish to use cmd)
-youll see a yellow error message about cache. dont worry,this is normal
-hold vol UP and power until you see blue writing that is the stock recoverys menu
-using the vol rocker and power button,wipe cache
-select apply update from sd card
-choose "update.zip"
*sit your phone down and let it do its thing. youll see yellow writing as the update applies patch files,then a couple different screens as it makes firmware changes. if the first update worked,then this one should as well.
*if you do see an "install aborted" error message,make note of what it is,and reboot using the stock menu option
-when the updates are finished,the phone will reboot. give it a few minutes to settle.
congratulations! you are now on ICS 3.14.605.12 only thing lost during this should be your root access.
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers. donate to my device fund
Last edited by scotty85; August 20th, 2012 at 04:58 AM.
The Following 6 Users Say Thank You to scotty85 For This Useful Post:
*make a backup of your data partition using amons menu options on the phone screen. simply remove the X's from everything but data on the backup screen,then "perform backup". you do not need to backup boot or system. you may also want to perform a full backup in case something goes wrong,but this is optional.
-using the phones amon ra menu options,flash "SetMainVersionLOW.zip" just like you would any other rom. no need to wipe anything,just flash it.
-boot back into bootloader adb reboot bootloader
-check main version fastboot getvar all
-if your main version is now 1.00.000.0 then procede:
-relock bootloader fastboot oem lock
*you may get a security warning after it locks. dont panic,this is normal when relocking with custom software
-run the .exe file on your PC with our phone still in fastboot. follow the onscreen directions. it will reboot when finished
-your phone wil reboot to a freshly factory reset state. chose language,sign into google,etc. give the phone a few minutes to sync and settle. turn off "fastboot" in settings/power,enable usb debugging in settings/apps/development
now restore your data by:
reopen your cmd window,and change back to mini-adb_vigor directory if needed. then:
-using the amon recovery menus,wipe cache,wipe dalvik cache. flash superuser. if superuser aborts, reboot,and try again.
-once superuser flashes successfully, you can restore your data. select your data only backup from the restore menu. remove the X's from everything but data.
-once the restore is complete,reboot. give the phone a few minutes to settle. skip ahead to step 4,since you have the stock recovery
Last edited by scotty85; August 10th, 2012 at 07:42 AM.
Hey Scotty, Im stuck trying to run the mini RUU, I ran the fastboot oem rebootRUU command and got a black screen with HTC in white. When I run the" fastboot flash zip RUU-2.01.605.11-mini.zip" command, I get
error: cannot load RUU-2.01.605.11-mini.zip"
So, just observing, but noticed that Scotty85's filename is "miniRUU2.01.605.11.zip" and the one on the instructions is "RUU-2.01.605.11-mini.zip" perhaps try the first instead?
Hey Scotty, Im stuck trying to run the mini RUU, I ran the fastboot oem rebootRUU command and got a black screen with HTC in white. When I run the" fastboot flash zip RUU-2.01.605.11-mini.zip" command, I get
error: cannot load RUU-2.01.605.11-mini.zip"
thats may fault,apparently i pulled a name switcheroo on ya... the flash zip command should use the same name as the md5sums command(miniRUU2.01.605.11.zip)
ive edited the OP to reflect it,it should work for you now.
So, just observing, but noticed that Scotty85's filename is "miniRUU2.01.605.11.zip" and the one on the instructions is "RUU-2.01.605.11-mini.zip" perhaps try the first instead?
ninja answered me! that is correct,use the miniRUU2.01.605.11.zip filename.
Hi Scotty, great instructions so far! I'm curious, I've finished up to where I start Step 4 for manually ICS. I am completely up to stock (recovery, all apps, S-ON, unlocked bootloader, etc) and received the OTA prompt. Theoretically, do you think I could install the actual OTA or should I proceed with the manual ICS files you provided?
Hi Scotty, great instructions so far! I'm curious, I've finished up to where I start Step 4 for manually ICS. I am completely up to stock (recovery, all apps, S-ON, unlocked bootloader, etc) and received the OTA prompt. Theoretically, do you think I could install the actual OTA or should I proceed with the manual ICS files you provided?
if you have the stock recovery,and all your apps you could take the OTA if you wanted. it will download the exact same files that you will apply manually,so i guess it comes down to wich will download them faster the phone or your PC,and wich one do you trust more to download without error
the end result is exactly the same,neither loading the files manually or letting the phone download them will provide any advantage over the other.
great post! I didn't delete any apps, because I had read on another forum that deleting system apps had messed up a previous OTA for someone on a rezound. I just had frozen apps, so I'm going to try your other suggestion:
Quote:
-reflash GB backup and take OTA
-restore current backup(dont reboot after)
-wipe cache and dalvik cache
-reflash rom
-reboot
I am thinking about using this opportunity to install another ICS rom, not sure if I want to install nils or a senseless ROM...hmm. I am happy with newts but I'm worried ROM won't be updated any further.
So I'm going to try ViperRez for now. Someone asked on the other thread which ROMS were based on the .12 software build. It's basically the ones that have updated in July, I think. So ConROM, nils business sense (Sense 4 version), viperrez, senseless chaos, neomax (senseless) and OTA-ICS-Plus (stock ICS rom with a couple of addons).
I am not sure whether newts one xxx 3.2.1 (6/30) or ineffablis deus (updated 6/26) are based on .10 or .12. Not that there's a huge difference but still...
EDIT: Guess I will be trying this method after all, as my GB backup didn't restore through Amon RA (
Last edited by obscuro; August 6th, 2012 at 09:52 AM.
Thanks Stotty! I've attempted to follow your instructions on Step 4. Renamed the first package to "update.zip," (verified that it did not have .zip.zip) and received a red caution icon rather than the yellow one you mentioned. Had to remove the battery on stock recovery since there was no option to reboot. Created a new copy of the package, and I even reflashed stock recovery on your instructions here (I first flashed stock recovery from your "root guide"). Still receiving the same icon. Not entirely sure what is happening here? I'm going to attempt to install the OTA and see if I receive the same thing.
Black screen, picture of phone with the red caution sign. No other messages, and no other response from the volume rocker and power button. Pull the battery to remove myself from stock recovery. I am also S-ON; not sure if the manual didn't work because I wasn't S-OFF? I did try the OTA installation when I received the prompt, so on a positive note, the installation that route was a success! So I have ICS with all my data!
Scotty, I managed to perform the first update, but can't get the second (stage2) update.zip to work.
The first one seemed like it got picked up automatically through hboot, for the second one, I started stock recovery and chose the apply update from sdcard option.
It gave me the cache error and then said it was rebooting with error:
Invalid operation
success rebooting by reason oem-00
any ideas?
EDIT: Do you have to be locked? My installation of the mini-RUU worked just fine, got GB up and running, just FYI. Cleared the cache and dalvik cache, like u said. I do have superuser 0.94 installed, and flashed Setmainverlow.zip.
EDIT3: I tried flashing Setmainverlow.zip again, then trying to install update2, still didn't work. Going to see if I can get the OTA on the phone connection.
EDIT 4: Got the OTA over wifi, so that's good. Still don't know why it wouldn't work manually.
Earlier I had an issue when restoring the data part of my most recent backup. It sent stock GB into bootloops and I had to clear storage. My goal is to be running ViperRez with my data restored. My most recent backup is from newts, so I just want to make sure there are no conflicts, as long as I don't restore boot/system/cache.
Last edited by obscuro; August 6th, 2012 at 01:04 PM.
Black screen, picture of phone with the red caution sign. No other messages, and no other response from the volume rocker and power button. Pull the battery to remove myself from stock recovery. I am also S-ON; not sure if the manual didn't work because I wasn't S-OFF? I did try the OTA installation when I received the prompt, so on a positive note, the installation that route was a success! So I have ICS with all my data!
Brilliant instructions, sir!
You are at the point where you have to 1) hold down the volume up button 2) then press the power button
That will launch the stock recovery menu. The red icon is just kind of a safeguard to keep people from messing with stuff unless they know what they are doing.
The Following User Says Thank You to obscuro For This Useful Post:
You are at the point where you have to 1) hold down the volume up button 2) then press the power button
That will launch the stock recovery menu. The red icon is just kind of a safeguard to keep people from messing with stuff unless they know what they are doing.
Ah! Good to know! Appreciate the info! I'm fairly new at this process and the stock recovery system on HTC devices. I came from the OG Droid. I have a new appreciation for ADB thanks to you. I appreciate all your help.
At the beginning of the "Update1" portion I get this error
--Invalid Operation. --
Success Rebooting by reason: oem-00...
Did you flash SetMainVersionLow.zip that scotty linked to in his original post? Try flashing that zip in amon ra recovery, and then try the update.zip again.
Yup just tried it and same error message again. Everything went smoothly step by step..Currently Unlocked S-On, and Rooted.
OK, how about this. With the update.zip on your SD card, instead of typing 'adb reboot recovery', type 'adb reboot bootloader.' Then when the stock boot menu pops up, choose bootloader from the menu. On my phone it seemed like the screen that normally checks for PH98IMG.ZIP picked up the update.zip for phase 1 automatically, you have to tell it yes go ahead with update. Try that and let me know what happens.
OK, how about this. With the update.zip on your SD card, instead of typing 'adb reboot recovery', type 'adb reboot bootloader.' Then when the stock boot menu pops up, choose bootloader from the menu. On my phone it seemed like the screen that normally checks for PH98IMG.ZIP picked up the update.zip for phase 1 automatically, you have to tell it yes go ahead with update. Try that and let me know what happens.
Just ran the ADB Reboot-Bootloader, hit bootloader, looks like it was looking for alot of files related to PH98IMG.ZIP which were not there and that's it. If I go into recovery once i'm there, same thing.
Did you remember to wipe the cache from recovery before applying update? That's the only thing I can think of.
And just so we're on the same page, you did go through the steps to install the GB mini-RUU, right? Scotty has said that stock GB + stock recovery is all you need to be able to install the OTA. I was only able to get the first phase done manually, then I had to download the big OTA using wifi.
Did you remember to wipe the cache from recovery before applying update? That's the only thing I can think of.
And just so we're on the same page, you did go through the steps to install the GB mini-RUU, right? Scotty has said that stock GB + stock recovery is all you need to be able to install the OTA. I was only able to get the first phase done manually, then I had to download the big OTA using wifi.
Yup, deleted the cache and the davlik cache. I even followed his instructions and made it stock again, then ran through the root unlock again. Followed by the instructions listed on this page and same results. I'll play with it more when I get home, i'll even try a different MicroSD card.
Side note, i still have not been prompted for the OTA install yet either.
You may need to Go to settings->about phone-> software updates and check for the OTA manually. If you do get it, after downloading it, it will prompt you to click OK then it will take its sweet time rebooting the phone, so be patient. Scotty usually works til around 5, maybe he can help better when he gets off.
Scotty usually works til around 5, maybe he can help better when he gets off.
sorry guys,i dont know if i have anything real useful to add,im new to these OTAPkgs myself they were taken from the cache partition of my phone immediately after downloading. i dont think either contain info that is specific to my phone,but i could be wrong.
Quote:
Originally Posted by obscuro
Scotty, I managed to perform the first update, but can't get the second (stage2) update.zip to work.
The first one seemed like it got picked up automatically through hboot,
hmm,hboot started the update? how did you have it named? "update","Update",or "UPDATE"? it could be that my s-off phone didnt do some security check that your s-on phones are doing.
after the update,did you check your build number? did stage1 take you to 2.01.605.12?
Quote:
Originally Posted by obscuro
for the second one, I started stock recovery and chose the apply update from sdcard option.It gave me the cache error and then said it was rebooting with error:
Invalid operation
success rebooting by reason oem-00
any ideas?
none,whatsoever. if the first update worked,im not sure why the second would fail.
unless the first update didnt really work. but in that situation,i dont think youd have picked up the second stage via wifi,as youd have still been on 2.01.605.11. the OTA should have porompeted you for the 7mb one,if the first one hadnt really worked.
you did wipe cache with the stock recovery before chosing update from sd card?
Quote:
Originally Posted by obscuro
EDIT: Do you have to be locked? My installation of the mini-RUU worked just fine, got GB up and running, just FYI. Cleared the cache and dalvik cache, like u said. I do have superuser 0.94 installed, and flashed Setmainverlow.zip.
no,i dont believe you need to be locked or relocked. my s-off phone was unlocked,and i have defiantely accepted OTAs while unlocked and s-on,so i wouldnt think this to be any different.
Quote:
Originally Posted by obscuro
EDIT3: I tried flashing Setmainverlow.zip again, then trying to install update2, still didn't work. Going to see if I can get the OTA on the phone connection.
EDIT 4: Got the OTA over wifi, so that's good. Still don't know why it wouldn't work manually.
i actually would have thot changing your main version with the mainversionlow.zip would have been somewhat counterproductive,as i dont know how the updater scripts check for release firmware. changing the main version in the misc image may confusion,as other places that list the build number wont match it. but again,since you got the 2nd stage to download and apply,it must not have mattered much.
Quote:
Originally Posted by obscuro
Earlier I had an issue when restoring the data part of my most recent backup. It sent stock GB into bootloops and I had to clear storage. My goal is to be running ViperRez with my data restored. My most recent backup is from newts, so I just want to make sure there are no conflicts, as long as I don't restore boot/system/cache.
newts is a different build alltotheger(inc 4g,not rezound),different framework,different sense version. im not surprised restring data from newts to stock GB sent it into a state of confusion.
in otherwords,yes,id think there to be conflicts! you can only restore your data back to the same rom.
Quote:
Originally Posted by darksideofjae
At the beginning of the "Update1" portion I get this error
--Invalid Operation. --
Success Rebooting by reason: oem-00...
had you run the mini ruu?
were you competely stock?any apps frozen or deleted?
you were on build 2.01.605.11,correct?
youre using the stock recovery to try and wipe cache,and flash update.zip,correct?
Quote:
Originally Posted by darksideofjae
Yup, deleted the cache and the davlik cache.
this comment makes me think you were maybe not using the stock recovery,as it does not have option to erase dalvik cache. only factory resert,and wipe cache
again,sorry guys. im not really sure why its not working correctly. i did this exact procedure to my phone twice(and a few failed attempts prior) so i thot since OTAPkg was a signed by htc file that you s-on'ers should have any prollems.
hopefully we can figure it out,as i was really hoping to to find an easier way for the folks that werent getting the prompt,or had failed attempts.
after the update,did you check your build number? did stage1 take you to 2.01.605.12?
I did check this, because I was pasting the results of 'fastboot getvar all' on another thread and then later deleted it. So I'm 99 percent sure the first update worked, and was the .12 version number.
Now, I don't remember wiping the cache between update1 and update2, so that may have been my problem.
To the other poster, I would try doing as scotty said and flashing stock recovery.
I was wiping the cache and dalvik-cache using amon ra (fastbooted) and then rebooting into stock recovery for the update process. In your shoes I would try trying the cache wipe from within stock recovery, then trying to do the update.
Scotty, at some point darksideofjae said, "I even followed his instructions and made it stock again, then ran through the root unlock again."
Whereas I had never had to re-unlock my phone during this process, and I've always been S-ON. I went from rooted ICS on GB firmware, to running GB mini-ruu, to installing OTA update phase 1, to installing OTA over wifi. Never had to do the unlock token, just had to install superSU 0.94 where you had it in your instructions. (It worked on GB for me, too.)
darksideofjae, if you can use adb/fastboot commands, can you type 'fastboot getvar all' and copy and paste what it says here? (Blank out the fields that say serial number and IMEI, just for your privacy.)
As for my own problem, are you saying that if I tried to nandroid restore data.img from newts, then re-installed ViperRez completely, that my apps wouldn't be there? There is a market app called Nandroid browser that can extract single files from nandroid backups, but I'm not really looking forward to that LOL
I did check this, because I was pasting the results of 'fastboot getvar all' on another thread and then later deleted it. So I'm 99 percent sure the first update worked, and was the .12 version number.
Now, I don't remember wiping the cache between update1 and update2, so that may have been my problem.
To the other poster, I would try doing as scotty said and flashing stock recovery.
I was wiping the cache and dalvik-cache using amon ra (fastbooted) and then rebooting into stock recovery for the update process. In your shoes I would try trying the cache wipe from within stock recovery, then trying to do the update.
aha! maybe we are on to something here. the stock recovery is capable of wiping parts of the phone that amon is not,so maybe that had something to do with it.
also,you were defiantly trying to install stage2,correct? its easy to get them mixed up once theyre both named "update"
Quote:
Originally Posted by obscuro
Scotty, at some point darksideofjae said, "I even followed his instructions and made it stock again, then ran through the root unlock again."
Whereas I had never had to re-unlock my phone during this process, and I've always been S-ON. I went from rooted ICS on GB firmware, to running GB mini-ruu, to installing OTA update phase 1, to installing OTA over wifi. Never had to do the unlock token, just had to install superSU 0.94 where you had it in your instructions. (It worked on GB for me, too.)
darksideofjae, if you can use adb/fastboot commands, can you type 'fastboot getvar all' and copy and paste what it says here? (Blank out the fields that say serial number and IMEI, just for your privacy.)
As for my own problem, are you saying that if I tried to nandroid restore data.img from newts, then re-installed ViperRez completely, that my apps wouldn't be there? There is a market app called Nandroid browser that can extract single files from nandroid backups, but I'm not really looking forward to that LOL
if im understanding you correctly,if you
-restore newt backup
-flash viperrez with no data wipe(but with cache and dalvik)
-reboot
your apps would have tried to have been there,but i dont believe the frameworks of these 2 roms are close enuff to work. i believe this is what caused the bootloops and prollems with your other thread. at the least,when you "dirty flash" a rom overtop of another thats not compatible,youll end up with FCs and potentially crashed,reboots,and loss of other functionality.
even if youre installing drastic differences in versions of the same rom,you can experience this. thats why most rom devs always reccomend a full wipe for their updates,so that folks dont blame code incompabilties as rom bugs.
as for getting your app data back,see the other thread
last and not least,thanks for the extra detail and info
aha! maybe we are on to something here. the stock recovery is capable of wiping parts of the phone that amon is not,so maybe that had something to do with it.
also,you were defiantly trying to install stage2,correct? its easy to get them mixed up once theyre both named "update"
That is what I am thinking, especially since I don't think I wiped the cache between update1 and update2.
I definitely installed phase 1, deleted it from SDCard, then put phase 2 on sdcard and renamed it update.zip
However, darksideofjae never got phase1 to work. Hope he can follow our train of thought with these recent posts.
Basically, try 'fastboot flash [stock recovery]" per scotty's original post, launch stock recovery (adb reboot recovery) and use the wipe cache option in there before trying to reboot and install the update. See if that works!
The Following User Says Thank You to obscuro For This Useful Post:
darksideofjae,id be willing to bet it wont take becasue you are not on 2.01.605.11 firmware(indicted by 2.10 hboot).
i believe to get this to work,you will need to:
-backup your data as described
-relock and run full ruu for 2.01.605.11
-reunlock
-relaunch recovery and restore data
i believe that then step 4 will work
2.10 is the hboot for 1.02.605.6. so,alternately, restoring that may let you OTA to 2.01.605.11,then to 2.01.605.12,then to 3.14.605.12
The Following User Says Thank You to scotty85 For This Useful Post:
So I just got done following the FullMUU and this is what my getvar all states. Just wanted to make sure everything was kosher before moving on.
H:\mini-adp_vigor>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.11.0000
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.01.605.11
INFOserialno:
INFOimei:
INFOproduct: vigor
INFOplatform: HBOOT-8260
INFOmodelid: PH9810000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 4194mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-bc948b45
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.500s
So now i'm going to do the unlock from the tutorial. Since I have no data to backup (titanium backup) I'm going to then go straight into step 4. Do I need to have a main version of 2.01.605.11 or the 1.00.000.01?
*EDIT* After doing that and then reunlocking my phone, after it booted up, I was prompted with the OTA install. It looks like I'm good to go so far. Starting phase 1 now.
Last edited by darksideofjae; August 7th, 2012 at 07:59 AM.
The Following User Says Thank You to darksideofjae For This Useful Post:
So now i'm going to do the unlock from the tutorial. Since I have no data to backup (titanium backup) I'm going to then go straight into step 4. Do I need to have a main version of 2.01.605.11 or the 1.00.000.01?
C:\mini-adb>fastboot flash zip miniRUU2.01.605.11.zip sending 'zip' (463936 KB)... FAILED (remote: not allowed) finished. total time: 0.000s
If I key in the failed command a second time, it just says sending zip, and never clears. I have to pull the usb cable and when I do, the phone says "RUU" of which never clears till I pull the battery.
What am i doing wrong?
All I want to do is update to ICS WITH the new radios, and if possible keep my data - if I'm going about this the hard way, someone please show me the way, or shoot me now.
Edit: Just for fun, I tried to reflash the OEM recovery...
C:\mini-adb>fastboot flash recovery recovery_signed_stock_2.01.605.11.img
sending 'recovery' (5598 KB)... FAILED (remote: not allowed)
finished. total time: -0.000s
If I key it in again, it starts: I get the green bar rising on the right side, it gets close to the top and just hangs there. I have to pull the usb cable to get it to clear.
Any suggestions?
Last edited by 95wolverine; August 13th, 2012 at 12:23 AM.
as far as the mini-ruu,did you flash the main version tool prior to running it?
some basic things to check:
-make sure htc sync,pda net,or any other program capable of comunicating with the phone is not runing
-try different usb ports
-try different usb cables
a copy of the entire session may be helpful.
The Following User Says Thank You to scotty85 For This Useful Post:
as far as the mini-ruu,did you flash the main version tool prior to running it?
some basic things to check:
-make sure htc sync,pda net,or any other program capable of comunicating with the phone is not runing
-try different usb ports
-try different usb cables
a copy of the entire session may be helpful.
Guess I was too tired, it was EasyTether. I turned that off, and everything went according to plan. I did forget to turn on debugging after flashing the miniRUU, but figured it out after a couple of "adb devices" not finding anything.
Thanks SOOO much Scotty.
It was very difficult for me to give up Cleanrom GBE 1.7 - that rom has done me right in ever which way possible since I installed it. I never even had any force closes. Let's see if Rooted Stock ICS will treat me as well.
Thanks again for the help.
Last edited by 95wolverine; August 13th, 2012 at 10:37 AM.
Guess I was too tired, it was EasyTether. I turned that off, and everything went according to plan. I did forget to turn on debugging after flashing the miniRUU, but figured it out after a couple of "adb devices" not finding anything.
Thanks SOOO much Scotty.
It was very difficult for me to give up Cleanrom GBE 1.7 - that rom has done me right in ever which way possible since I installed it. I never even had any force closes. Let's see if Rooted Stock ICS will treat me as well.
Thanks again for the help.
your quite welcome glad you got it.
did you use the OTAs,or did you manually apply the files?
I have the cached zip for the new, second ICS OTA. I'm not sure that I made a backup for stock ICS, but I have the android police zip of the first OTA. Now that I'm on ICS firmware, can I just flash those two zips to get up-to-date?
I have the cached zip for the new, second ICS OTA. I'm not sure that I made a backup for stock ICS, but I have the android police zip of the first OTA. Now that I'm on ICS firmware, can I just flash those two zips to get up-to-date?
im confused... i thot you had allready done both OTAs? what is your current baseband?
did you use the OTAs,or did you manually apply the files?
Scotty, I couldn't get the first ota update to take - it just acted like there was no update to be applied and did nothing.
I needed my phone for work, so I just rebooted it stock (2.01.605.12 with my data restored) and let it pull the OTA from the web via my wifi here at home - it's rock solid stable, so I didn't fear any connection issues. The update went without issue.
I had some odd behaviour, and have read that doing a factory reset after getting the OTA has helped many. So I booted Ra and did a data backup, then did a factory reset, rebooted... gmail, etc, let it settle, then did Ra and a restore of data. All seems to be better - like many have said on other forums (all of whom did the automated OTA, not manual).
Interesting thing... I was thumbing around this morning, snooping for info about the followup 104mb OTA that's rumored to be out... and found this site:
What was of particular interest to me, were the manual flashing instructions (I copied them from the site word for word):
"Okay, I flashed it. Here's how:
1. Install the ICS OTA full firmware.
2. Boot it up at least once. I skipped setup and just let it boot.
3. Extract the firmware.zip out and rename to PH98IMG.zip. (Don't remove it, just extract a copy.)
4. Place the PH98IMG.zip on the SDCard.
5. Rename the entire package to Update.zip and put it on the SDCard.
6. Reboot to recovery (which should now be stock.)
7. Press vol up and power.
8. The update will start and patch your files.
9. The phone will reboot to HBOOT and load the PH98IMG.zip file you put there.
10. Vol up to install.
11. PWR to reboot.
12. Profit!
Enjoy playing!"
Notice the capital "U" on "Update.zip" ? I wonder if that was my flashing problem for this user's guide?
Last edited by 95wolverine; August 14th, 2012 at 07:08 AM.
funny... i was just about to link that out in the forum i saw a rom based onit on xda and went a-searchin as well
when you say you rebooted to "stock 2.01.605.12" wsa that a typo? if not,then the first update had somehow applied itself allready. stock, pre OTAs, was 2.01.605.11
as far as update vs Update,i couldnt say for sure that it makes a difference on s-on devices. i went thru the procedure i outlined twice on my s-off phone and it went smoothly,and i had mine named "update". i person could certainly try Update and UPDATE if they wish...
i also didnt extract the firmware packages. if youre using the stock recovery to apply the Otapkg,im not sure why they did that... the stock recovery will extract and install the firmware
im downloading OTapkg now... i plan to play with it later of course
funny... i was just about to link that out in the forum i saw a rom based onit on xda and went a-searchin as well
when you say you rebooted to "stock 2.01.605.12" wsa that a typo? if not,then the first update had somehow applied itself allready. stock, pre OTAs, was 2.01.605.11
as far as update vs Update,i couldnt say for sure that it makes a difference on s-on devices. i went thru the procedure i outlined twice on my s-off phone and it went smoothly,and i had mine named "update". i person could certainly try Update and UPDATE if they wish...
i also didnt extract the firmware packages. if youre using the stock recovery to apply the Otapkg,im not sure why they did that... the stock recovery will extract and install the firmware
im downloading OTapkg now... i plan to play with it later of course
Typo? Me? Are you serious? Why, yes, yes it was. lol
As for the update, please report back as to what else is included besides making the Rezound "World Capable".
Flashing is fun... when it fricking works! lol
Last edited by 95wolverine; August 14th, 2012 at 08:07 AM.
im confused... i thot you had allready done both OTAs? what is your current baseband?
I'm talking about the new world phone OTA that started rolling out this week. It contains new radios. But I think I am just going to wait until viperrez updates to include them, I have no desire to go to stock ICS so I might as well just wait since it seems like this is more of a bug fix update anyway.
Notice the capital "U" on "Update.zip" ? I wonder if that was my flashing problem for this user's guide?
I named mine update.zip while S-ON and it worked fine, don't think it matters. One thing we sort of theorized while helping another poster who was having trouble getting the first ICS OTA update to install was that you need to clear the phone cache from the stock recovery before trying to flash the first update.zip (and then again before you try to install the second.)
Glad you got it work the automated way. The above tip probably needs to be done for the OTApkg, but I'm going to let Scotty test it out first
I named mine update.zip while S-ON and it worked fine, don't think it matters. One thing we sort of theorized while helping another poster who was having trouble getting the first ICS OTA update to install was that you need to clear the phone cache from the stock recovery before trying to flash the first update.zip (and then again before you try to install the second.)
Glad you got it work the automated way. The above tip probably needs to be done for the OTApkg, but I'm going to let Scotty test it out first
yes,dont mess with it yet... i stopped at the house for a second and flashed the firmewar. there are new radios and takes you to hboot 2.27
yes,dont mess with it yet... i stopped at the house for a second and flashed the firmewar. there are new radios and takes you to hboot 2.27
installed only the firware and my phone wont boot
more later...
Ruh-roh. I am having issues of my own with viperrez, so I figured now is as good a time as any to go back to stock and get the new OTA. Hope you get your issues sorted out.
Ruh-roh. I am having issues of my own with viperrez, so I figured now is as good a time as any to go back to stock and get the new OTA. Hope you get your issues sorted out.
i flashed the firmware and it wouldnt boot. i assumed it was becasue of some sort of mismatch,since i was on viperrom. so i flashed back some older firmware and rebooted. still no boot so i popped my sim in the thunderbolt and took them both with me.
wiped system/boot/cache/data/dalvik cache and restore the 3.14.605.12 backup. that time it booted
so now im running the 3.14.605.12 ruu so i can install the OTAPkg. afterward ill flash a rom and make sure that i dont have any "no booting" issues
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
i flashed the firmware and it wouldnt boot. i assumed it was becasue of some sort of mismatch,since i was on viperrom. so i flashed back some older firmware and rebooted. still no boot so i popped my sim in the thunderbolt and took them both with me.
wiped system/boot/cache/data/dalvik cache and restore the 3.14.605.12 backup. that time it booted
so now im running the 3.14.605.12 ruu so i can install the OTAPkg. afterward ill flash a rom and make sure that i dont have any "no booting" issues
Okay scotty, I think I'm about to go the route you're on since my battery just plain ol' sucks on Viper Rez I loved that ROM, too.
To run the 3.14.605.12 RUU, do I follow the same instructions on your post from method #2)"full ruu" method to unroot? Do I still need to flash SetMainVersionLOW.zip? I did make a Nandroid backup of the stock (OTA) ICS; maybe I can just use that Nandroid backup instead of the full RUU?
Okay scotty, I think I'm about to go the route you're on since my battery just plain ol' sucks on Viper Rez I loved that ROM, too.
To run the 3.14.605.12 RUU, do I follow the same instructions on your post from method #2)"full ruu" method to unroot? Do I still need to flash SetMainVersionLOW.zip? I did make a Nandroid backup of the stock (OTA) ICS; maybe I can just use that Nandroid backup instead of the full RUU?
Thanks in advance
yes,you can use those directions,just substitue the ruu for 3.14.605.12
you can prolly forgo the main version tool,i doubt anything youve installed as changed your main version to something higher than 3.14.605.12
as long as you OTAed and have the matching 3.14 firmware,you are prolly fine in just restoring a stock nandroid.
if you want the whole update,youll need to install it just like described in the OP:
*charge your phone to 100%!
-place OTAPkg_stage1 onto the root of your sd card. rename it to "update"
-boot to the factory recovery via adb reboot recovery (optionally,you can select recovery from the hboot menu if you dont wish to use cmd)
-youll see a yellow error message about cache. dont worry,this is normal
-hold vol UP and power until you see blue writing that is the stock recoverys menu
-using the vol rocker and power button,wipe cache
-select apply update from sd card
-choose "update.zip"
*sit your phone down and let it do its thing. youll see yellow writing as the update applies patch files,then a couple different screens as it makes firmware changes.
you dont need to extract firmware and rename it PH98IMG as the android police directions state. the stock recovery will apply all firmware and software all by itself
alternately,you can keep checking for system updates and just apply it OTA
yes,you can use those directions,just substitue the ruu for 3.14.605.12
you can prolly forgo the main version tool,i doubt anything youve installed as changed your main version to something higher than 3.14.605.12
as long as you OTAed and have the matching 3.14 firmware,you are prolly fine in just restoring a stock nandroid.
if you want the whole update,youll need to install it just like described in the OP:
*charge your phone to 100%!
-place OTAPkg_stage1 onto the root of your sd card. rename it to "update"
-boot to the factory recovery via adb reboot recovery (optionally,you can select recovery from the hboot menu if you dont wish to use cmd)
-youll see a yellow error message about cache. dont worry,this is normal
-hold vol UP and power until you see blue writing that is the stock recoverys menu
-using the vol rocker and power button,wipe cache
-select apply update from sd card
-choose "update.zip"
*sit your phone down and let it do its thing. youll see yellow writing as the update applies patch files,then a couple different screens as it makes firmware changes.
you dont need to extract firmware and rename it PH98IMG as the android police directions state. the stock recovery will apply all firmware and software all by itself
alternately,you can keep checking for system updates and just apply it OTA
Thank you so much for the writeup scotty, but I ran into a problem.
First, I followed all the steps above, but whenever I get to step "-select apply update from sd card" it doesn't give me the option to choose the update.zip. I get this yellow message "Invalid something (maybe operation) then underneath that in yellow: "Rebooting now... OEM..." I'm not really sure what it said.
The update didn't install with that method. So I read the androidpolice method, followed the steps, only I DID NOT put the extracted firmware.zip (renamed to PH98IMG.zip) on the sdcard, only the renamed update.zip (former OTAPk-sumthin.zip).
I went into HBOOT menu via vol. down, power up method, and my phone right away installed the update. I couldn't stop it. I let it install, it rebooted, got past the green HTC, beats audio screens, but I'm now stuck on the 4G LTE screen.
Edit: SOLVED
After trying again to install via HBOOT menu and ending up on that 4g LTE screen, I just grabbed a card reader, plugged it in to PC so I can put the PH98IMG.zip there, took a shower (optional), pulled battery, went into HBOOT menu via the vol.down, power.up method, updated again and everything updated correctly this time.
scotty, for sum reason it was looking for a boot image file so I said what the hey, might as well try it the "original" method's way. I guess maybe b/c I came straight fr. a fresh RUU that I was missing a boot image or something? But everything's smooth as silk now!
Big big THANK YOU again. You've helped me out so many times
Last edited by NEXTLOVER; August 18th, 2012 at 03:35 AM.
The Following User Says Thank You to NEXTLOVER For This Useful Post: