Background
I had already unlocked my phone using the HTCdev site.
I downloaded and installed clockwork recovery v5.8.1.4 using rom manager.
Issue
I can get to recovery but once there anything that I select gives me a black screen with the clockwork recovery icon in the middle. even if I have a zip file in my sdcard it won't read it.
I can't access my backups, I can't flash any image. everything was wiped. if I try to boot, I get the white screen that says HTC, and then a black screen.
If anyone could help me with this I would be very appreciative
Attempts at solving the problem
I read that there was an issue with clockwork before posting here and I tried to install Amon Ra's recovery. I tried the latest version 3.14 but when I try to fast boot it, I get the message "main version is older! Update Fail!"
Does your phone have the OTA? I'm on mainver 2.x and just flashed Amon Ra v3.14 with no problem. Fastboot doesn't usually care about mainver anyway.
You can try using the new Awesome Recovery Tool that con247n made but I think you have to flash Amon Ra in fastboot:
http://forum.xda-developers.com/showthread.php?t=1497984
What mainver are you on? Find out with this command:
fastboot getvar all
If you are coming from ICS to GB then you need to flash a GB kernel.
I just reread your post and you said everything was wiped. You can try using testdisk to get that stuff back so you can use one of your nands. Here's a post I just made about that:
feralicious said:
I made a post upthread about testdisk. It's free and should get your files back. I pm'd info to the person who posted their external was wiped and they thanked me then thanked me agian a couple days later so I assume it worked for them, which means the wipe must just delete and not reformat.
http://www.cgsecurity.org/wiki/TestDisk
I got all my nands and TiBUs off my external that stopped being read by phone or computer. I have gotten all my data, even that which had been deleted, off drives that every computer said needed to be initialized. Does what people charge thousands of dollars for.
You may have to pull the cards out and mount them on the pc, I can't remember if I tried to use testdisk while they were in the phone but I think I did and it didn't find them.
It will look like it's not going to work on the card but it does. After you select the drive and it comes up with the partition table list, select [None].
Then select [Analyse]
Can't recall exactly what happened next, I think it mentioned errors with the partition etc... but it listed the correct size of the card as if it were empty so I proceeded and then bam, it listed all my files. Copied them all off no problem.
Click to expand...
Click to collapse
Wenu wer in clockwork & saw logo didu hit power button to bring menu up?
http://forum.xda-developers.com/showthread.php?t=1459347
Mainver info here might help, also in dev/stickies there's threads on everything from recovery s to Mainver, hope it helps
Edit : sorry didn't see others post.
Sent from my ADR6300
feralicious
I did not install the OTA update, I am only able to get to the HBOOT screen which is HBOOT-2.10.0000.
I have a backup that I made before the running clockwork, I had that saved to my SDcard, I am not too attached to it and would want to just flash a new rom, I had gingerbread and was trying to go to ICS
Rom-Addict said:
Wenu wer in clockwork & saw logo didu hit power button to bring menu up?
Sent from my ADR6300
Click to expand...
Click to collapse
When I was in clockwork I hit the power button to get to the menu items, I would press the volume up and down to navigate. when I select the update from zip, i get the icon, and nothing else. If i press the power button it brings me back to the menu i was at prior but no option takes me further than a black screen with the icon.
ParanoidAndr0id said:
I did not install the OTA update, I am only able to get to the HBOOT screen which is HBOOT-2.10.0000.
Click to expand...
Click to collapse
I edited my post above since I didn't see the responses, there's info there about getting your nands off your external card.
So you must be on 1.x then. You can download and run the RUU for mainver 1.x, then accept the OTA and you'll be stock and updated. Then you can retry flashing Amon Ra and reroot.
You have to relock first:
fastboot oem lock
I am going to do that right now.
I tried downloading "The Root Thread: Currently Unlocked Bootloader, S-ON and Perm Root" but the links are dead.
I've been trying to download the one for my version and filefactory is too busy. I was just looking for an alternate download location and saw this one for v1.x:
http://forum.xda-developers.com/showpost.php?p=19878282&postcount=29
http://forum.xda-developers.com/showpost.php?p=20233270&postcount=30
They also made it as a zip you can flash in hboot if you prefer. Pretty sure the one you need is 1.02.605.6
Here's the filefactory link just in case:
http://www.filefactory.com/f/c2e320ee1d5c7886/
feralicious said:
I've been trying to download the one for my version and filefactory is too busy. I was just looking for an alternate download location and saw this one for v1.x:
http://forum.xda-developers.com/showpost.php?p=19878282&postcount=29
http://forum.xda-developers.com/showpost.php?p=20233270&postcount=30
They also made it as a zip you can flash in hboot if you prefer. Pretty sure the one you need is 1.02.605.6
Here's the filefactory link just in case:
http://www.filefactory.com/f/c2e320ee1d5c7886/
Click to expand...
Click to collapse
Thanks for the links, I tried the dropbox links and they are all 404ing is there. I haven't tried the filefacotry ones since I have no clue how to install them.
i did find this http://berz.me/other/vigor/
This one is still working!
http://forum.xda-developers.com/showpost.php?p=20951603&postcount=43
---------- Post added at 03:21 PM ---------- Previous post was at 03:14 PM ----------
Also... I know you can't use an RUU that has an older mainver than the one you have but I'm not sure about going to a newer mainver RUU. It seems that the link I just posted is working so that's the safest route, but if you can use the newer RUU then here is a working link for that, I just downloaded it myself:
http://forum.xda-developers.com/showpost.php?p=22045045&postcount=58
Maybe if someone else reads this and knows if it's okay to use the 2.x version on your 1.x phone they can chime in. But you might want to grab it while you can in any case for future use.
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
ParanoidAndr0id said:
Thanks for the links, I tried the dropbox links and they are all 404ing is there. I haven't tried the filefacotry ones since I have no clue how to install them.
i did find this http://berz.me/other/vigor/
Click to expand...
Click to collapse
That looks like it's what you need. You'd just need to rename the file before you flash it.
The ones that are not PHzips but are .exe files you just run on your computer by double clicking on them.
Cwm uses the home button to select, not power
Okay, I got an answer in the RUU thread that you can use the 2.x RUU and that will bring you up to date. So if you haven't already run the 1.x version and gotten the OTA you can just run the one from this link:
http://forum.xda-developers.com/showpost.php?p=22045045&postcount=58
You just need to relock the phone, have the phone in hboot and double click the file you download on your computer. Then you should be on hboot 2.11 I think it is and have new radios and a few other goodies.
Then you can move on to flashing Amon Ra, installing su in the developer menu of that and you'll be stock rooted with the update.
I hope that the PH98img works. I've been fighting the exact same issue all day. RUU would let me get close to then end, but then I would get a security error 155 before it flopped.
Does anyone know if the battery will still be able to charge when the phone is in this state? If not, I may not have enough battery to install the PH98IMG.
feralicious said:
I edited my post above since I didn't see the responses, there's info there about getting your nands off your external card.
So you must be on 1.x then. You can download and run the RUU for mainver 1.x, then accept the OTA and you'll be stock and updated. Then you can retry flashing Amon Ra and reroot.
You have to relock first:
fastboot oem lock
Click to expand...
Click to collapse
Any suggestions for "fastboot oem lock" not working? Mine just goes to "waiting for device".
Without the lock, the RUU still gives the 155 security error before failing.
esheesle said:
Cwm uses the home button to select, not power
Click to expand...
Click to collapse
this information was extremely useful.
wisenber said:
Any suggestions for "fastboot oem lock" not working? Mine just goes to "waiting for device".
Without the lock, the RUU still gives the 155 security error before failing.
Click to expand...
Click to collapse
Is the phone showing "fastboot USB"?
Sent from my ADR6425LVW using Tapatalk
feralicious said:
Is the phone showing "fastboot USB"?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Ding! Ding! You got it! Thanks!
After relocking the Rezound, the RUU still would not load.
I was able to amonra recovery.img and finally get into clockwork recovery. Since my mainver was newer than the RUU, I had to move ahead to ICS...which is looking pretty good so far.
wisenber said:
Ding! Ding! You got it! Thanks!
After relocking the Rezound, the RUU still would not load.
I was able to amonra recovery.img and finally get into clockwork recovery. Since my mainver was newer than the RUU, I had to move ahead to ICS...which is looking pretty good so far.
Click to expand...
Click to collapse
Fyi... there are work arounds to the mainver issue in case you want to go back to a GB ROM. There's a new tool by con247 called Awesome Recovery Tool that will help with that. You can find it in the dev section.
Related
Hey Guys, fairly new to posting here, but was hoping this could help some of you.
#####################################################################
# If you are running a stock ROM you can ignore this, there are better threads for you out there.
#####################################################################
When the OTA came out I knew I wanted the new radios, but have had nothing but problems putting them on.
I have spent the last couple of hours reading and generally just being frustrated. I eventually got to the conclusion I wanted and I thought having all of this OTA update junk in one place might be helpful for others.
History:
- I was running Ineffabilis 12/29. (great ROM)
- Went to Senseless ICS (great ROM, bluetooth problems, persistent with all current ICS's, was insurmountable for me)
- Went to Team BAMF Rezound Cubed ROM, used this ROM to get out of the ICS trap because it flashes a kernel after it flashes the ROM.
Coming From ICS, Team BAMF Cubed or the New clean GB rom:
If you have installed a ROM that updated the Main Ver (all ICS roms or Team BAMF rom, or the new clean GB rom, then you will need to reset the main ver to 1.00.000.00 to run the RUU.
To do that go to this thread: http://forum.xda-developers.com/showpost.php?p=21875151&postcount=1
Next:
Once you have your main ver set to 1.00.000.00. You will need to follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1466474 (summary below)
1) You will need to reflash the stock recovery (a great way to do that is using Cleanflash, get it here: http://www.scottsroms.com/downloads.php?do=file&id=57) -- You can find the stock flash recovery image in the thread above.
2) Reboot to Fastboot and run "fastboot oem lock" from your DOS command line. This will reboot your phone back into fastboot/hboot.
3) Run the RUU.exe from Windows using the download from scottsroms here: http://www.scottsroms.com/downloads.php?do=cat&id=11
4) Go through and install the OTA updates. Go to settings, and software update.
5) Go back to HTCDev.com and unlock the bootloader as you have in the past.
6) Flash a new recovery.img, such as amonRa, (fastboot flash recovery nameofrecovery.img)
7) The world is now yours! Install ICS if you would like or any other ROM or install su if you prefer.
Credits:
!! mrbracht for the mainver fixed (saved my bacon)
!! FlyHalf205 for the rest of this
!! scrosler for generally being awesome and all the great tool's, roms, ruu, etc.
I've downloaded the recovery and unziped it. Then I moved it to fastboot but when I type fastboot flash recovery recovery_sign.img I get a error cannot load.
FlagAZ said:
I've downloaded the recovery and unziped it. Then I moved it to fastboot but when I type fastboot flash recovery recovery_sign.img I get a error cannot load.
Click to expand...
Click to collapse
The stock recovery? What mainversion are you?
I checked today it was something like 1.0.6. I know that it was not updated.
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
I've been trying all day with no like...... I'm lost with all the post about how to do this (flash this, unload this, do it this way)......
okay so what is the text of the error?
i keep getting hung up in the RUU... my MainVer is the same version as the RUU, or was, but now i can't reboot my phone, just tuck in bootloader/fastboot, and with the stock recovery lol...
my ADB won't open either
---------- Post added at 09:26 PM ---------- Previous post was at 08:39 PM ----------
platinumrims said:
i keep getting hung up in the RUU... my MainVer is the same version as the RUU, or was, but now i can't reboot my phone, just tuck in bootloader/fastboot, and with the stock recovery lol...
my ADB won't open either
Click to expand...
Click to collapse
pah, gave up. unlocked reflashed amon ra, and restored my nandroid... :'(
Maybe this reply is too late. Sorry...
But, was it locked and having the stock recovery when you were trying the RUU? Also you run the RUU from windows while the phone is in hboot mode.
pngwyn said:
Also you run the RUU from windows while the phone is in hboot mode.
Click to expand...
Click to collapse
Yes, that is how I always do it.
Wow. I'm impressed with the details you provided. I was debating flashing ICS and had questions about going back. You answered all my questions. Thanks for posting your findings. I really appreciate it.
Updated
So by resetting the mainver, will I be able to flash ICS then say Ineffabilis 12/29 without worrying about updating any kernels? Also, just to confirm, once I flash ICS, I'd have to reset the mainver before going back to Ineffabilis 12/29.
Sent from my ADR6425LVW using xda premium
I go back and forth between ics and gb roms without any issues, never got a mainver error.
Sent from my HTC Rezound using XDA Premium
raider3bravo said:
Wow. I'm impressed with the details you provided. I was debating flashing ICS and had questions about going back. You answered all my questions. Thanks for posting your findings. I really appreciate it.
Updated
So by resetting the mainver, will I be able to flash ICS then say Ineffabilis 12/29 without worrying about updating any kernels? Also, just to confirm, once I flash ICS, I'd have to reset the mainver before going back to Ineffabilis 12/29.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Glad you found the post useful.
As far as I understand, you won't have any issues switching between GB and ICS and back to GB (other than needing to make sure you are running a compatible kernel). If you go back to ineffabilis after ICS you will need to find a way to get the kernel on the system (probably through fastboot or adb) and then flash ineffabilis, for me it was easiest to go back to GB using team bamf because it included the kernel and then you could flash ineffabilis and all should have been well.
The real reason to worry about main ver (as far as I know) is so that you can flash the ruu and return to stock. I guess there are also some other problems with kernels and them checking what mainver you have before flashing, but I am not familiar with those issues.
The nice thing is with the mainver hack above you won't ever have to worry by resetting the mainver, pushing the stock recovery, relocking and then flashing using the RUU utility it is possible to get completely back to factory condition.
Best Regards!
pngwyn said:
Maybe this reply is too late. Sorry...
But, was it locked and having the stock recovery when you were trying the RUU? Also you run the RUU from windows while the phone is in hboot mode.
Click to expand...
Click to collapse
I was using the ruu on Windows and had my phone in Hboot.
I relocked it, via an app someone made here on the forums because I couldn't get ADB to run at all. It would flash up in a window and close immediately. And I re installed SDK 10 Times and couldn't ever get adb to re instal or update.
Also had the stock recovery flashed...
When I used the app to relock the phone I had a "security warning" message under the relock status in fastboot, dunno if that's normal.
Then when trying to run the ruu I got a 155 error, but it wasn't the same one as listed in the report, or it didn't say the same thing at least. Then I kept getting battery lower than 30% errors so it wouldn't let me redo it after the 3rd try. Even though my phone was at like 85% when I got frustrated and decided booted it back up...
I'd like to try it again some other time but idk what else to do to get my ADB functioning ATM so I can check or change my MainVer (which was the same version as the ruu, also dunno if that mattered, I just though as long as it wasn't higher the ruu would work)
Any info would be mucho appreciated lol. :banghead:
platinumrims said:
I was using the ruu on Windows and had my phone in Hboot.
I relocked it, via an app someone made here on the forums because I couldn't get ADB to run at all. It would flash up in a window and close immediately. And I re installed SDK 10 Times and couldn't ever get adb to re instal or update.
Also had the stock recovery flashed...
When I used the app to relock the phone I had a "security warning" message under the relock status in fastboot, dunno if that's normal.
Then when trying to run the ruu I got a 155 error, but it wasn't the same one as listed in the report, or it didn't say the same thing at least. Then I kept getting battery lower than 30% errors so it wouldn't let me redo it after the 3rd try. Even though my phone was at like 85% when I got frustrated and decided booted it back up...
I'd like to try it again some other time but idk what else to do to get my ADB functioning ATM so I can check or change my MainVer (which was the same version as the ruu, also dunno if that mattered, I just though as long as it wasn't higher the ruu would work)
Any info would be mucho appreciated lol. :banghead:
Click to expand...
Click to collapse
I am not familiar with anything you experienced.
You shouldn't need adb for anything you are trying to do. It doesn't sound like you are getting the mainver error (if you were you would be getting the error after trying to go through the RUU wizard and it actually tells you your mainver is 2.00.###.## for whatever it is. If you are sure you haven't done anything to update your main ver than chances are your mainver is not the problem.
I am just guessing but this is what I am imagining could be solutions.
- Use 'fastboot oem lock' from the hboot prompt when in fastboot usb mode (ie your usb cable is plugged in.
- Make sure you are using the .exe version of the RUU. If you are not using the .exe version then that definitely could be the problem, if you are using the .exe version then perhaps the file got corrupted when you downloaded it. Try deleting and redownloading.
- You have said that you are running the stock recovery which sounds correct. But make sure you aren't using the stock recovery from one of your own backups use the one that is provided in the thread from my link above.
... In conclusion you shouldn't need ADB if your main version is the stock mainver. Flash the stock recovery first of all, then use the command 'fastboot oem lock' it will tell you it is locked it will reboot the phone (I think it even gives you an error in the dos prompt.) But then when it reboots it reboots to hboot and will say relocked at the top in the bright purple. Then be sure to run the RUU version .exe. If the RUU you have still isn't working download another (this is the one that worked for me: http://www.scottsroms.com/downloads.php?do=file&id=37)
Sorry wish I could be more helpful but I don't have relevant experience for what is happening for you but I do know what worked for me and I do believe it will work for you.
Good luck!
I doubt seriously that its my mainver. I'm wondering if it had something to do with that,weird security thing I had showing up in my fastboot. I will try it again maybe tomorrow night or something. Thank for your help
THANKS
I had to do the main ver fix and everything, great guide made everything super easy
Ok so I'm running the late july/early august update of newts one xxx RLS rom my Phone is currently S-off and I s-Offed with the 2nd leak of ICS as of late I've been having this problem with my rezound that whenever I shut it off the phoner won't turn back on UNLESS I plug it in into my car charger this is what happens when I try to turn it one
White HTC screen the screen will flash black once and then back to white htc screen, followed by a blank screen then comes in the mikroms with the roadrunner on top and it freezes there then black screen again and phone repeats the whole process again but if I connect the phone to the car charger process is kind of the same except the phone turns on is this problem fixable?
any help will be appreciated
croonux said:
Ok so I'm running the late july/early august update of newts one xxx RLS rom my Phone is currently S-off and I s-Offed with the 2nd leak of ICS as of late I've been having this problem with my rezound that whenever I shut it off the phoner won't turn back on UNLESS I plug it in into my car charger this is what happens when I try to turn it one
White HTC screen the screen will flash black once and then back to white htc screen, followed by a blank screen then comes in the mikroms with the roadrunner on top and it freezes there then black screen again and phone repeats the whole process again but if I connect the phone to the car charger process is kind of the same except the phone turns on is this problem fixable?
any help will be appreciated
Click to expand...
Click to collapse
Sounds like your having boot problems. Can you boot into bootloader just fine without being connected to a charger? If so try flashing the proper boot image for the Rom your on, using fastboot commands.
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------
The initial boot.IMG flash may have not been a complete success. Check the md5sum of your Rom.
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
famouscollin said:
Sounds like your having boot problems. Can you boot into bootloader just fine without being connected to a charger? If so try flashing the proper boot image for the Rom your on, using fastboot commands.
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------
The initial boot.IMG flash may have not been a complete success. Check the md5sum of your Rom.
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
Click to expand...
Click to collapse
yes sir , I am able to boot into bootloader and the other menu where i can install zip from forgot what its called, and how do I check the md5sum? and how do i install boot.IMG?
I haven't been keeping up with all the rezound modding scene like I used to with my first droid things got more complicated :\
Help
Download the latest RUU 4.03.605.2 (Link below), rename it to PH98IMG, and place on the root of your external sd card. Them boot into HBOOT, press Vol Up to confirm update and let it run
P.S. It won't take off S-Off but it will relock your bootloader
Hope this helps!
androidrevolutions.com/neo/files/GlobalRuuPH98IMG.zip
i would agree i would prolly update first just to get it outa of the way. hers an md5 checker DL click file<download: https://docs.google.com/file/d/0B0ZJtM40GdJ0Ymt4ZWRpU3hqVWs/edit go into the thread where you downloaded your rom, you should be able to find the proper md5 sum for your rom there. copy that md5 open and run md5.zip click paste. then browse below to your download for tha rom if the codes dont match retry download. if the do you good. lemme know if your md5 is good and well go from there.
---------- Post added at 04:57 PM ---------- Previous post was at 04:54 PM ----------
the latest global update ruu: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
darkghost568 said:
Download the latest RUU 4.03.605.2 (Link below), rename it to PH98IMG, and place on the root of your external sd card. Them boot into HBOOT, press Vol Up to confirm update and let it run
P.S. It won't take off S-Off but it will relock your bootloader
Hope this helps!
androidrevolutions.com/neo/files/GlobalRuuPH98IMG.zip
Click to expand...
Click to collapse
famouscollin said:
i would agree i would prolly update first just to get it outa of the way. hers an md5 checker DL click file<download: https://docs.google.com/file/d/0B0ZJtM40GdJ0Ymt4ZWRpU3hqVWs/edit go into the thread where you downloaded your rom, you should be able to find the proper md5 sum for your rom there. copy that md5 open and run md5.zip click paste. then browse below to your download for tha rom if the codes dont match retry download. if the do you good. lemme know if your md5 is good and well go from there.
---------- Post added at 04:57 PM ---------- Previous post was at 04:54 PM ----------
the latest global update ruu: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Click to expand...
Click to collapse
thanks for the help guys I'll let you guys know how it worked it tomorrow as I'm pretty busy and I'm about to leave as well thanks again and quick question as well if I'm s-offed would it even matter if my bootloader got locked?
croonux said:
thanks for the help guys I'll let you guys know how it worked it tomorrow as I'm pretty busy and I'm about to leave as well thanks again and quick question as well if I'm s-offed would it even matter if my bootloader got locked?
Click to expand...
Click to collapse
It shouldn't matter but I've heard reports of some people not being able to use fastboot commands and had to unlock. But that individual was using stock hboot aposed to joupunut hboot.. if you do have problems I guess you could just unlock..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
yeah stock locked/relocked hboots even if s-off won't let you fastboot things...
here http://forum.xda-developers.com/showthread.php?t=1853871
put one of those on you're sd card after you do the latest RUU so you can have fastboot capabilities.
CHECK MD5 very important when doing hboot or radio things
---------- Post added at 12:43 AM ---------- Previous post was at 12:42 AM ----------
croonux said:
I'm s-offed would it even matter if my bootloader got locked?
Click to expand...
Click to collapse
Nope doesn't matter that's what the moddified hboots are for. the link is in my above post
Ok so I just updated to the latest ruu today i didn't have time until today but things got worse now I updated first before checking md5, could that have been the error? and now it just keeps rebooting on the HTC screen and it won't go to the mikroms screen
I went to my roms page and I can't seem to find the md5 http://themikmik.com/showthread.php...ense-4-GB-4-0-3)-4-2-2012&p=197893#post197893 help??? (I'm extremely tired so my finding/logical sense are not working properly right now)
and now it seems as if my recovery has been deleted as I get a Phone screen facing up as if it was laying down on a table with a green refreshing sign/reloading sign fllowed by a phone screen facing me with a red triangle like the one where you turn on the hazard lights on your car
..
You could find Amon Ra 3.15 recovery in a zip that can be renamed PH98IMG.zip
and reinstall recovery. Your immediate problem may be solved, but if you have time, you can do more.
Amon Ra lets you look at either internal drive: your sdcard or the phone's storage:
toggle the sdcard, attach to computer, and remove the PH98IMG of just-installed Amon Ra recovery.
Now find the Android Police 4.03 version (large download if correct) , make sure the md5's match for it, and
copy it to extrenal sdcard renamed as PH98IMG.zip. It will run 1 1/2 times then boot
up to operating system. Many people say to do another reinstall and/or one or more Factory Resets at this point:
one from Seup- Storage - Factory reset with phone "on". Another factory resey is availble
by booting to recovery and choosing Reset. It's a good idea to do one or both style resets before
you reinstall a recovery. Every time you run an RUU or a zip that replaces the ROM, you have
to reinstall that Recovery. To avoid no-charging situations, I'd advise keeping Amon Ra 3.15.
Now you're at the point you can root and play with this powerful handset.
michaelbsheldon said:
You could find Amon Ra 3.15 recovery in a zip that can be renamed PH98IMG.zip
and reinstall recovery. Your immediate problem may be solved, but if you have time, you can do more.
Amon Ra lets you look at either internal drive: your sdcard or the phone's storage:
toggle the sdcard, attach to computer, and remove the PH98IMG of just-installed Amon Ra recovery.
Now find the Android Police 4.03 version (large download if correct) , make sure the md5's match for it, and
copy it to extrenal sdcard renamed as PH98IMG.zip. It will run 1 1/2 times then boot
up to operating system. Many people say to do another reinstall and/or one or more Factory Resets at this point:
one from Seup- Storage - Factory reset with phone "on". Another factory resey is availble
by booting to recovery and choosing Reset. It's a good idea to do one or both style resets before
you reinstall a recovery. Every time you run an RUU or a zip that replaces the ROM, you have
to reinstall that Recovery. To avoid no-charging situations, I'd advise keeping Amon Ra 3.15.
Now you're at the point you can root and play with this powerful handset.
Click to expand...
Click to collapse
ok so download amon ra and then check md5 but the only problem im encountoring so far is I don't know how to check md5 I've gone to my roms page (link on first page last post) and I can't seem to find where I can check the md5 and I do have time today and I don't really feel like reinstalling/reseting if I don't have too
croonux said:
ok so download amon ra and then check md5 but the only problem im encountoring so far is I don't know how to check md5 I've gone to my roms page (link on first page last post) and I can't seem to find where I can check the md5 and I do have time today and I don't really feel like reinstalling/reseting if I don't have too
Click to expand...
Click to collapse
Download MD5 checker from the play store. Load the PH98IMG as file 1, then paste the md5 from the amon ra thread into the second text area. Then press the button.
GrayTheWolf said:
Download MD5 checker from the play store. Load the PH98IMG as file 1, then paste the md5 from the amon ra thread into the second text area. Then press the button.
Click to expand...
Click to collapse
I can't boot my phone anymore as of today so i won't be able download the app, and what text area do I put the md5 from amon ra and is there anyother way to check md5 or should I jsut reinstall rom/ factory reset, but for that I gotta go to staples right now and buy a micro sd adapter as I can't modify my sd at all anymore
bump and another cry for help so I installed the latest ruu, bootloader got locked and recovery got erased, so i installed amon ra 3.15 as per the instructions up there, where do I go from here? what else do I install I'm having the same problems from first post... how do i check md5 if I can't boot into the phone? any more help will be appreciated
actually just by looking at my bootloader could it be possible that the global ruu didn't get install? this is the info I have when I hold power and vol -
****LOCKED****
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO- 2.22.10.0801R/2.22.10.0803R
OpenDSP-v14.6.0.7708.00.0507
eMMc-BOOT
AUG 6 2012, 19:24:37
.
2.27 is the newst Global firmware.
When you boot, are you still seeing something from MikRoms?
If yes, your RUU installation didn't work.
I'd use Amon Ra to wipe:
every choice several times and reinstall the whole Android Police 4.03 PH98IMG.zip.
If you don't get a nice clean oem-style stock bootup after that, then the RUU is suspect, may need
to get from another source.
michaelbsheldon said:
2.27 is the newst Global firmware.
When you boot, are you still seeing something from MikRoms?
If yes, your RUU installation didn't work.
I'd use Amon Ra to wipe:
every choice several times and reinstall the whole Android Police 4.03 PH98IMG.zip.
If you don't get a nice clean oem-style stock bootup after that, then the RUU is suspect, may need
to get from another source.
Click to expand...
Click to collapse
yup I get the mikroms thing again guess it didn't work when I wipe my data do I wipe ALL data/factory reset and does this include my SD card when it gets wiped or no?
.
yeppers:
in AmonRa, take Wipe, then do each one including the internal and external Sdcards
and dalvik cache and everything else a coupla times..
The RUU ought to have undone everything else in your phone incl MikMik, so it may
not be a good one.
After all wipes, put it back onto your external card as PH98IMG and flash twice.
If all is well, you'll have a fine virgin install ready to be rooted and messed with.
michaelbsheldon said:
yeppers:
in AmonRa, take Wipe, then do each one including the internal and external Sdcards
and dalvik cache and everything else a coupla times..
The RUU ought to have undone everything else in your phone incl MikMik, so it may
not be a good one.
After all wipes, put it back onto your external card as PH98IMG and flash twice.
If all is well, you'll have a fine virgin install ready to be rooted and messed with.
Click to expand...
Click to collapse
cool thanks for all your help man, and im glad i still got my droid 1 sd
Here's my situation. Got this new phone yesterday. I am (was) bootloader unlocked, s-on with htcdev method. Also am (was) using twrp for recovery. Then went looking for some roms... found one, moved it to the phone, wipe, blah, blah, done this before plenty on my old evo shift. Well, there was some problem, rom couldn't be installed, which is no problem for people who do regular nand backups. That was not me. So... stuck at htc screen.
Bottom line, after many hours of different ideas and methods, I've relocked the bootloader, downloaded an ruu, and I'm stuck. In hindsight I sort of backed myself into a corner, because though I supposedly needed to relock to run an ruu, now I can't get at twrp recovery. So I need help running the ruu from fastboot. In my searches, this seems possible, but it's not working for me. The phone is recognized, because when I enter into command "fastboot find devices" or whatever that was, a phone shows up. The .exe itself just won't open though. Tried running as administrator, tried compatibility mode, tried running it from the command line, each time it will give me the blue circley thing for about 5 or 10 seconds and then just do nothing.
I'm just out of ideas, feeling like I'm stuck here.
Remember: currently my screen reads TAMPERED RELOCKED Security Warning I'm in fastboot usb mode. Oh, and I tried to find the ruu to match my Hboot, but it currently shows 1.15.0000, and there is of course no ruu with that code, so I downloaded the newest one (2 point something)
Any help is appreciated
admsteff said:
Here's my situation. Got this new phone yesterday. I am (was) bootloader unlocked, s-on with htcdev method. Also am (was) using twrp for recovery. Then went looking for some roms... found one, moved it to the phone, wipe, blah, blah, done this before plenty on my old evo shift. Well, there was some problem, rom couldn't be installed, which is no problem for people who do regular nand backups. That was not me. So... stuck at htc screen.
Bottom line, after many hours of different ideas and methods, I've relocked the bootloader, downloaded an ruu, and I'm stuck. In hindsight I sort of backed myself into a corner, because though I supposedly needed to relock to run an ruu, now I can't get at twrp recovery. So I need help running the ruu from fastboot. In my searches, this seems possible, but it's not working for me. The phone is recognized, because when I enter into command "fastboot find devices" or whatever that was, a phone shows up. The .exe itself just won't open though. Tried running as administrator, tried compatibility mode, tried running it from the command line, each time it will give me the blue circley thing for about 5 or 10 seconds and then just do nothing.
I'm just out of ideas, feeling like I'm stuck here.
Remember: currently my screen reads TAMPERED RELOCKED Security Warning I'm in fastboot usb mode. Oh, and I tried to find the ruu to match my Hboot, but it currently shows 1.15.0000, and there is of course no ruu with that code, so I downloaded the newest one (2 point something)
Any help is appreciated
Click to expand...
Click to collapse
You can get the RUU here
This will help you get twrp and SuperSU back
It's really just an incompatible ruu? I'm about halfway through downloading the 1.22 version already, I thought I would try. I'll give it a shot, but wouldn't it give an error or something instead of just not responding on my pc?
admsteff said:
It's really just an incompatible ruu? I'm about halfway through downloading the 1.22 version already, I thought I would try. I'll give it a shot, but wouldn't it give an error or something instead of just not responding on my pc?
Click to expand...
Click to collapse
To be honest I have never flashed an RUU but I would think if you flashed the wrong one it could potentially brick your phone.
Thanks, these ruu files are so damn big, it's gonna be a few minutes. We'll see how it goes.
admsteff said:
Thanks, these ruu files are so damn big, it's gonna be a few minutes. We'll see how it goes.
Click to expand...
Click to collapse
You should try uploading them haha good luck.
Wait a minute, I noticed that the link you gave me is for a .zip file, while the one I'm downloading is for a .exe file? Isn't it supposed to be a self-installing program from windows? Do I need to be entering like a fastboot flash command for a zip instead because my phone is in fastboot and not fully booted? I can't believe I forgot the nand backup, this is like a whole wasted day of my life now...
admsteff said:
Wait a minute, I noticed that the link you gave me is for a .zip file, while the one I'm downloading is for a .exe file? Isn't it supposed to be a self-installing program from windows? Do I need to be entering like a fastboot flash command for a zip instead because my phone is in fastboot and not fully booted? I can't believe I forgot the nand backup, this is like a whole wasted day of my life now...
Click to expand...
Click to collapse
Like I said I have never ran an RUU so I'm not sure how it works you could PM om4 or read Don't Panic in the Q&A section
Yeah, problem is the same with the 1.22 ruu. It just wont execcute the program from my pc. Does anybody else have any ideas?
You only had to flash the kernel or bootimg. Seperately since your s-on...look for om4 guide " don't panic"...it should answer all of your questions...as far as the ruu make sure you're on the bootloader fastboot screen when you run it.
Sent from my EVO using xda premium
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
http://forum.xda-developers.com/showthread.php?p=31102864
mrlakadaddy said:
You only had to flash the kernel or bootimg. Seperately since your s-on...look for om4 guide " don't panic"...it should answer all of your questions...as far as the ruu make sure you're on the bootloader fastboot screen when you run it.
Sent from my EVO using xda premium
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
http://forum.xda-developers.com/showthread.php?p=31102864
Click to expand...
Click to collapse
Yes, I realize I dug myself into a hole by relocking. I just didn't want to learn how to put a new img on my phone (of course it was wiped, with a bad rom flashed) without having the thing mounted as a media device in the gui method. I'm sure it would have been quite easy, and that's kind of how the whole thing went, I wasn't scared enough and I just kept doing what I thought was the "easiest" way to get the phone back, and just was a dumbass overall. I read the "don't panic" guide. Maybe I missed something, but I don't think it would have got me out of the specific problem I made, once I was already in it. And I was certainly on fastboot usb when trying to run the ruu, and I had it in the right folder with fastboot.exe, etc.
Anyway, I never got it to work, but I ended up just returning the device to the retailer, and no questions were asked. It was cheating, I know. It could have been done, I was far from bricked, but when the phone is 1.5 days old and I can return it to a person who has no idea why my phone is "stuck", it was just too easy.
Thanks to everyone who tried to help
Hey guys,
I was running the latest Viper rom. Every great once in a while the phone would just turn off. I could get it back fine and this happened about 5-6 times. Today the phone got stuck in a boot loop. I figured something went wrong.
I attempted to restore the phone to stock using the RUU thread found here: http://forum.xda-developers.com/showthread.php?t=2152993
I restored it once fine, said it was good. Phone only rebooted over and over. The HTC logo came up 3-4 times then screen went blank. So I flashed again. Same thing, nothing.
Now I had been playing around and think I updated my radio. Now the RUU from that thread above says it cannot upgrade my phone. I can get to fastbook and lock and unlock the bootloader. I did install latest TWRP but it never enters recovery. I had hoped to just install a basic rom from the 2.04 update and be done. But I cannot get into recovery.
I'm stuck and don't know what else to do. Is there and RUU file like the one above for the new 2.04?
I still think something else is wrong with this phone. Somehow doubt VZW will take it back and exchange.
S-ON
Phone displays HBOOT-1.33.0001
RADIO-1.01.01.0110
Any ideas what I can do next please?
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Tersanyus said:
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Click to expand...
Click to collapse
Did you take the verizon update as you mentioned 2.04? If you did you will have to wait a bit yet to root again. Your only option would be stock verizon. Their software update basically closed the previously open window. If not...You HAVE updated radio per the # you posted, not sure if that really matters with regard to recovery. It seems like you have compounded many issues. I would try relocking bootloader and flash stock RUU again. Try to get back to stock verizon. If that's a no go, would try reflashing old radio and try stock ruu. How are you getting to try bootloader/recovery, turning on phone holding down vol button? Last ditch if it's says s-on and locked, I think you would be ok to try for a new phone.
I did not take the OTA from Verizon. I never got any prompt for an update. I did the updates for Viper that turned I think just turned that off.
Getting to bootloader is fine. I can lock it and unlock it fine. I know the RUU only loads if locked. I know recovery can only be installed if unlocked I believe. And yes I do that from vol down plus power button.
If I use newest TWRP recovery just gives a whole bunch of colored lines. If I try 2.4.0.0 I can see TWRP come up briefly then the phone reboots again.
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Tersanyus said:
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Click to expand...
Click to collapse
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
---------- Post added at 10:39 AM ---------- Previous post was at 09:48 AM ----------
rootntootn said:
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
Click to expand...
Click to collapse
Can you get to fastboot? adb can communicate with the phone? Says in red fastboot usb? Also how are you doing RUU, assuming your using executable from your pc? Forgot to ask..
Yes I can get to fastboot fine. I do a "fastboot devices" and it is read. adb doesn't seem to do anything though. The RUU is the .exe I found.
For the cid I did the old one so mine reads all 1's. I didn't think I could so the new cid as I cannot boot into Android at all.
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
rootntootn said:
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Click to expand...
Click to collapse
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
BTW There was nothing wrong with your phone, it's just that when you restored, you needed to flash the boot.img from your rom that you restored. It was most likely a kernel issue that we could correct with viper.
It sounds like you just need to install the matching rom and boot.img. If you're s off, just fastboot flash the boot.img for whatever rom you currently have installed. For the OTA update, you can install the radios without an RUU if you're s off.
I ran for several hours and several reboots on the RUU .exe file. When I downloaded a custom rom from http://forum.xda-developers.com/showthread.php?t=2150262 - That fan fine for an hour or so. Then boot loop over and over again. Thankfully I made a backup in twrp. I restored that and all is well.
I can't stand this factory rom, the part that really annoys me, besides the VZW bloat, is the recent apps button. For over a year with other HTC's I am used to making that the menu button. Had that in the custom rom.
So it looks like that rebooting loop just means I need to fastboot the boot.img?
I go back to the rom I linked about and fastboot the boot.img. I really liked viper rom but am going to stick to stock that is rooted and debloated.
My cid is all 1's since I did that before all this OTA came out. I did that about 3 weeks ago the day I got the phone.
Thanks for the tips. I'll let you know what happens when I go back to the rom above.
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry about the 2's info but read that the older cid apk would no longer work (from thread below) and myself put on the new one which yields the all 2's. Bottom line, glad you made progress, hopefully problem resolved
http://forum.xda-developers.com/showthread.php?t=2109862
I just came back from root, as I am selling the Rezound soon. I flashed the 3.14 RUU, and relocked the bootloader, and did a factory reset, and not it won't download the global OTA...even under full wifi coverage, or full 4G coverage, it just keeps saying "Service Unavailable"...any ideas?
Try RUU from the one on Neo's android revolutions... I did and was able to take both updates(there is a minor update then the official global update).
Sent from my Rezound using xda app-developers app
Uzephi said:
Try RUU from the one on Neo's android revolutions... I did and was able to take both updates(there is a minor update then the official global update).
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
Could you post a link to one please?
http://androidrevolutions.com/neo/RUU_Vigor_VERIZON_WWE_3.14.605.12_PH98IMG.zip
Be sure to rename it PH98IMG.zip and put to root of SD card and flash in hboot.
Also be sure to find a post by iamtheonetheycallneo and hit the thanks button for hosting the file. That RUU zip is the Official OTA which should connect for update when a Verizon SIM is in the phone.
Sent from my Rezound using xda app-developers app
jdailey1981 said:
I just came back from root, as I am selling the Rezound soon. I flashed the 3.14 RUU, and relocked the bootloader, and did a factory reset, and not it won't download the global OTA...even under full wifi coverage, or full 4G coverage, it just keeps saying "Service Unavailable"...any ideas?
Click to expand...
Click to collapse
If for some reason you can't load the ph98img.zip, you have another option.
First, if you are still on 3.14.605.12, load 3.14.605.13 from stock recovery:
http://www.wizwire.net/vigor/OTAPkg-3.14.605.13.zip
Then, download the otapkg.zip for 4.05.605.14 from here: http://forum.xda-developers.com/showpost.php?p=40757466&postcount=19 and load it in stock recovery:
Use the volume buttons to scroll and the power selects your option.
If selected stock recovery:
-Wait for stock recovery to boot (wait for red triangle with explanation point), once loaded, volume up button + power button will bring up stock recovery menu
-Use volume buttons to scroll, power button to select option.
flamewalker said:
If for some reason you can't load the ph98img.zip, you have another option.
First, if you are still on 3.14.605.12, load 3.14.605.13 from stock recovery:
http://www.wizwire.net/vigor/OTAPkg-3.14.605.13.zip
Then, download the otapkg.zip for 4.05.605.14 from here: http://forum.xda-developers.com/showpost.php?p=40757466&postcount=19 and load it in stock recovery:
Use the volume buttons to scroll and the power selects your option.
If selected stock recovery:
-Wait for stock recovery to boot (wait for red triangle with explanation point), once loaded, volume up button + power button will bring up stock recovery menu
-Use volume buttons to scroll, power button to select option.
Click to expand...
Click to collapse
Thanks alot! Downloading the recovery now. I am on 13, so we will see what happens. Do I need to rename it PH98IMG first or no?
Uzephi said:
http://androidrevolutions.com/neo/RUU_Vigor_VERIZON_WWE_3.14.605.12_PH98IMG.zip
Be sure to rename it PH98IMG.zip and put to root of SD card and flash in hboot.
Also be sure to find a post by iamtheonetheycallneo and hit the thanks button for hosting the file. That RUU zip is the Official OTA which should connect for update when a Verizon SIM is in the phone.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
Thanks for everyone's help. I am hoping this works
jdailey1981 said:
Thanks alot! Downloading the recovery now. I am on 13, so we will see what happens. Do I need to rename it PH98IMG first or no?
Click to expand...
Click to collapse
I couldn't get it to work on that ota.zip file. I had to launch stock recovery and load it from there. Doesn't matter what it's named from stock recovery as long as you can identify it
Just to be clear, it's not a recovery. It is an ota.zip file, that you load from stock recovery.
---------- Post added at 03:12 PM ---------- Previous post was at 03:01 PM ----------
jdailey1981 said:
Thanks alot! Downloading the recovery now. I am on 13, so we will see what happens. Do I need to rename it PH98IMG first or no?
Click to expand...
Click to collapse
I missed one. You could get the RUU for 4.03.605.2 (ph98img.zip) from here:
http://shipped-roms.com/index.php?category=android&model=Vigor
Then you should be able to OTA. If service unavailable message, then download the 4.05.605.14 from the link above and load it from recovery
flamewalker said:
I couldn't get it to work on that ota.zip file. I had to launch stock recovery and load it from there. Doesn't matter what it's named from stock recovery as long as you can identify it
Just to be clear, it's not a recovery. It is an ota.zip file, that you load from stock recovery.
---------- Post added at 03:12 PM ---------- Previous post was at 03:01 PM ----------
I missed one. You could get the RUU for 4.03.605.2 (ph98img.zip) from here:
http://shipped-roms.com/index.php?category=android&model=Vigor
Then you should be able to OTA. If service unavailable message, then download the 4.05.605.14 from the link above and load it from recovery
Click to expand...
Click to collapse
I mos certainly will try. Problem now is, when I got into stock recovery, it says "Invalid Operation, Reboot Success..." And a few other things when I try to flash zip from SD.
jdailey1981 said:
I mos certainly will try. Problem now is, when I got into stock recovery, it says "Invalid Operation, Reboot Success..." And a few other things when I try to flash zip from SD.
Click to expand...
Click to collapse
Are you still S-OFF?
flamewalker said:
Are you still S-OFF?
Click to expand...
Click to collapse
No, I am S-on
jdailey1981 said:
No, I am S-on
Click to expand...
Click to collapse
Have you tried the 4.03.605.2 ruu yet? That one is a ph98img.zip file that if placed on root of sd card should automatically load when booting to hboot. If it doesn't, make sure it is PH98IMG.zip... make sure there is no extra .zip at the end and try again.
flamewalker said:
Have you tried the 4.03.605.2 ruu yet? That one is a ph98img.zip file that if placed on root of sd card should automatically load when booting to hboot. If it doesn't, make sure it is PH98IMG.zip... make sure there is no extra .zip at the end and try again.
Click to expand...
Click to collapse
No, but I am going to try it once it is done downloading. Thanks again for your help.
cant get global ota either
Same here:
Have 2 rezounds getting ready for sale and can't get the second, larger download of OTA,
even after doing the steps suggested above. Have RUU'd and PH98IMG'd the 3.14 and can
receive the first smaller one but not the large one. Get download error # 503.
Likely a Verizon issue.
michaelbsheldon said:
Same here:
Have 2 rezounds getting ready for sale and can't get the second, larger download of OTA,
even after doing the steps suggested above. Have RUU'd and PH98IMG'd the 3.14 and can
receive the first smaller one but not the large one. Get download error # 503.
Likely a Verizon issue.
Click to expand...
Click to collapse
So, you need the 4.03.605.2? If you click the status under software update, it will tell you what version it is trying to download. Verify the version, and I can get you a download link
thanks
got the 4.03.605.2 from one of the prev links, thanks.
installing now.
Working now and update flashed. Thanks a lot for your help!
jdailey1981 said:
Working now and update flashed. Thanks a lot for your help!
Click to expand...
Click to collapse
Sure thing
Sent from my Nexus 7 using xda app-developers app