Hi there, about late December 2012, I got a System Update from HTC on my rooted Evo V ICS. I tried to update a few times with TEAMWIN, but I keep getting this error:
Code:
E:Bad boot message
"TIME"
Finding update package...
E:unknown volume for path [SDCARD:Download/OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p.zip]
E:Can't mount SDCARD:Download/OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p.zip
Installation Aborted.
Is there a fix for this, and what is this update about?
Thanks!
MrWinNT62 said:
Hi there, about late December 2012, I got a System Update from HTC on my rooted Evo V. I tried to update a few times with TEAMWIN, but I keep getting this error:
Is there a fix for this, and what is this update about?
Thanks!
Click to expand...
Click to collapse
It sounds like you are rooted and S-ON. If you are S-OFF this OTA installation procedure would be a little different.
You can't install the OTA with a custom recovery like TWRP installed. It also patches the stock ROM so it's best to relock your bootloader and flash the RUU if you want to get apply OTA updates, then htcdev unlock, flash a custom recovery and root again.
The OTA update includes firmware that fixes connection and texting problems, and patches to the stock ROM.
ramjet73
ramjet73 said:
It sounds like you are rooted and S-ON. If you are S-OFF this OTA installation procedure would be a little different.
You can't install the OTA with a custom recovery like TWRP installed. It also patches the stock ROM so it's best to relock your bootloader and flash the RUU if you want to get apply OTA updates, then htcdev unlock, flash a custom recovery and root again.
The OTA update includes firmware that fixes connection and texting problems, and patches to the stock ROM.
ramjet73
Click to expand...
Click to collapse
Thanks for the response.
I'm guessing I can use this thread for assistance, or is there a better alternative?
http://forum.xda-developers.com/showthread.php?t=1889438
Also, once I've rooted back after all this, do I have to go through these steps again for any future OTA Update?
MrWinNT62 said:
Thanks for the response.
I'm guessing I can use this thread for assistance, or is there a better alternative?
http://forum.xda-developers.com/showthread.php?t=1889438
Also, once I've rooted back after all this, do I have to go through these steps again for any future OTA Update?
Click to expand...
Click to collapse
Yes, you can use that thread through Step2 is you don't care about S-OFF, but that would make things a lot easier for you in the future. When you are S-OFF you can flash the RUU and do the OTA without unlocking the bootloader, then flash a custom hboot and recovery and you are back to where you want to be.
Make sure to download and install the OTA between Step1 and Step2 since once you flash a custom recovery it will not install properly.
ramjet73
Related
So, using Revolutionary alters your bootloader and so you can no longer receive OTA updates that check that your HBOOT (bootloader) is unmodified. This is pretty much all OTA updates, so you can't recieve OTA at all, save by flashing an uploaded image.
I'd like to receive OTA updates (especially with Honeycomb on the horizon), but I'd also like to root my Flyer. Is this possible? Via installing CWM through HTCDev.com bootloader unlock, maybe? Or does that break OTA updates too?
The HTCDev.com unlock leaves you with S-On, apparently.
porcupineadvocate said:
So, using Revolutionary alters your bootloader and so you can no longer receive OTA updates that check that your HBOOT (bootloader) is unmodified. This is pretty much all OTA updates, so you can't recieve OTA at all, save by flashing an uploaded image.
Click to expand...
Click to collapse
Completely incorrect
All that is required is that you reflash the stock revcovery once you have installed the su zip file.
globatron said:
Completely incorrect
All that is required is that you reflash the stock revcovery once you have installed the su zip file.
Click to expand...
Click to collapse
Really? Wow, great.
globatron said:
Completely incorrect
All that is required is that you reflash the stock revcovery once you have installed the su zip file.
Click to expand...
Click to collapse
Sorry for the dumb question... but stock recovery?
So flashing again once you have rooted, you will keep root and the updates will be ok?
Insinr8 said:
Sorry for the dumb question... but stock recovery?
So flashing again once you have rooted, you will keep root and the updates will be ok?
Click to expand...
Click to collapse
Stock recovery = the one from an RUU or OTA.
Yes, in theory at least. If you ever did get su disabled by an OTA, reflash cwm, reflash su.zip, reflash stock recovery again.
well i just purchased my view today and im trying to root it. where can i find the files and instructions?
In the development forum, the sticky right at the top of the page.
thanks man
I was going to install an ICS Sense ROM on my Rezound, but i just got a message that the OTA is downloading.
I'm rooted. I'm going to do S-Off soon as I can.
Should I get S-Off before installing the OTA?
Will the OTA break root?
Will the OTA break S-Off?
Are there advantages to using an ICS Sense ROM instead of the OTA? Vice versa?
Thanks!
I would s-off before you accept ota. It will not effect s-off. Installing an ics Rom wild give you better performance as well as better battery life
Sent from my ADR6425LVW using Tapatalk 2
I was in your exact position so I can help out here.
Note that before you accept the OTA you will need to flash the stock GB recovery, as that's how the OTA installs. Without it the OTA will fail. Also make sure you're 'locked' if you don't end up S-OFFing before the OTA. The S-OFF procedure automatically "locks" your bootloader even though you of course have full access.
I S-OFF'd before OTA just because the S-OFF method has been known to work with GB firmware. Others have reported the .5 ControlBear version on the unlimited.io website also works with the .22 OTA release so that's your call. IMO yes do it before, but it will likely work either way.
-Root will definitely break. Easy to fix: you just google Superuser and flash the latest ARM version.
-The OTA will not break S-OFF. HOWEVER, it will completely overwrite your "modded" hboot with its own secured version. To fix this, grab the ICS hboot from the unlimited.io website and flash it. This is necessary if you want to flash a custom recovery again.
-OTA advantages: support from VZW and probably *slightly* less bugs than a custom ROM. However you of course have to deal with the bloat. It's your call.
Ok, first step...
Where do I get the stock GB recovery?
And i guess i have to "flash" using my computer, not from within Amon?
So, all of the "flashing" you're talking about had to take place using my computer, not from within Amon?
Sorry I'm such a noob.
Anyone? I can't find the stock GB recovery for the Rezound... Anyone know where I can get it?
And do I flash it the same way I flashed AR recovery?
bloodymurderlive said:
Anyone? I can't find the stock GB recovery for the Rezound... Anyone know where I can get it?
And do I flash it the same way I flashed AR recovery?
Click to expand...
Click to collapse
http://www.mediafire.com/?wb21d2gdurui2c6
This is from a write up Scotty did a while back. It's worked for me in the past.
Rename to PH98IMG.zip and place on root of SD card and flash in hboot.
Or extract the recovery.img from that zip and flash in fastboot with the command fastboot flash recovery recovery.img
Thanks!
And now to get root back once I install the ICS OTA...
Do I simply flash the latest Superuser the same way that I flashed the recovery? ie: Do I rename it PH98IMG.zip and flash it in hboot?
You guys are awesome...
bloodymurderlive said:
Thanks!
And now to get root back once I install the ICS OTA...
Do I simply flash the latest Superuser the same way that I flashed the recovery? ie: Do I rename it PH98IMG.zip and flash it in hboot?
You guys are awesome...
Click to expand...
Click to collapse
The superuser zip you would flash in recovery not hboot. After you do the ota update you might have to re flash your recovery first though
Sent from my ADR6425LVW using xda app-developers app
Gottcha... So now I'm confused because the link for superSU in Scotty's n00b-friendly guide takes me here: http://forum.xda-developers.com/showthread.php?t=1538053
And the only link for superSU is to the Android market... How do I get the zip for superSU so that I can flash it in recovery?
bloodymurderlive said:
How do I get the zip for superSU so that I can flash it in recovery?
Click to expand...
Click to collapse
It's right there as CWM SuperSU v0.94
Thanks... It's confusing because it says CWM in the name, but I suppose that really just means you can install it with a custom recovery, not necessarily CWM.
CWM really screwed up charging on my phone before, so I was leary of it.
Got it rooted and ready to go now. Thanks!
So I was reading that you have to unroot, update, and then reroot via HTC's method if you are on hboot 1.50 and old firmware.
How would you go about doing this?
Are you s-on or s-off? It makes a big difference as to what you do.
Save the Drama for your Mama with Tapatalk 2
derik123derik123 said:
So I was reading that you have to unroot, update, and then reroot via HTC's method if you are on hboot 1.50 and old firmware.
How would you go about doing this?
Click to expand...
Click to collapse
No, you don't have to do all of that. If you want to run the stock kernel from the latest OTA, you have to update your hboot. But you do not need to unroot or anything to do that, just flash the firmware update with the new hboot. Or, you can run any ics rom, just with the 2.17 leak kernel without updating your hboot.
derik123derik123 said:
So I was reading that you have to unroot, update, and then reroot via HTC's method if you are on hboot 1.50 and old firmware.
How would you go about doing this?
Click to expand...
Click to collapse
You don't need to do all that. Just simply update over the air if you want the official update. If you want to install a custom rom, then simply root your phone(HTCdev), install recovery(4ext) and flash a custom rom. Always remember to do a nandroid backup before flashing.
Cheers.
sitlet said:
No, you don't have to do all of that. If you want to run the stock kernel from the latest OTA, you have to update your hboot. But you do not need to unroot or anything to do that, just flash the firmware update with the new hboot. Or, you can run any ics rom, just with the 2.17 leak kernel without updating your hboot.
Click to expand...
Click to collapse
Well htat's the issue. I can't install a new rom that has the new ics release. everytime I do I get thrown into a bootloop.
http://forum.xda-developers.com/showthread.php?p=30096947#post30096947
New issue above!
derik123derik123 said:
Well htat's the issue. I can't install a new rom that has the new ics release. everytime I do I get thrown into a bootloop.
http://forum.xda-developers.com/showthread.php?p=30096947#post30096947
New issue above!
Click to expand...
Click to collapse
replied to you on your new issue.
Cheers.
so i tried to update my phone through the normal update through my phone and it wouldnt work. so now i tried doing it through fastboot with clockwork that one aborts. i have no idea what is wrong. i have it stock rooted and i had it flashed from sprint to straight talk could that be the problem? if so how do i update any help would be greatly appreciated.
You need the stock recovery to install the OTA. It would probably be easier for you to run the RUU from Windows to update to the Sprint ICS release, but you will have to relock before if you are S-ON, then unlock and flash a custom recovery again when the RUU update is completed. After that, you can either root the ICS stock ROM or install a custom rooted ROM via the custom recovery.
ramjet73
ramjet73 said:
You need the stock recovery to install the OTA. It would probably be easier for you to run the RUU from Windows to update to the Sprint ICS release, but you will have to relock before if you are S-ON, then unlock and flash a custom recovery again when the RUU update is completed. After that, you can either root the ICS stock ROM or install a custom rooted ROM via the custom recovery.
ramjet73
Click to expand...
Click to collapse
how would i do this sorry im relativly new to most of this
ramjet73 said:
You need the stock recovery to install the OTA. It would probably be easier for you to run the RUU from Windows to update to the Sprint ICS release, but you will have to relock before if you are S-ON, then unlock and flash a custom recovery again when the RUU update is completed. After that, you can either root the ICS stock ROM or install a custom rooted ROM via the custom recovery.
ramjet73
Click to expand...
Click to collapse
i got it back to stock but what ruu am i supposed to be running i tried the one through htcdev and it wont run and it says its the same update that i have.
mataemon_araki said:
i got it back to stock but what ruu am i supposed to be running i tried the one through htcdev and it wont run and it says its the same update that i have.
Click to expand...
Click to collapse
Is your phone Gsm or Cdma? I use the Cdma version and if that's the case then you would need the ics sprint 2.89 ruu you file which you can find here http://d-h.st/AVU. If its Gsm then you'll need to check the Gsm development thread due to the fact that they are varieties of ruu files for different countries.
mataemon_araki said:
i got it back to stock but what ruu am i supposed to be running i tried the one through htcdev and it wont run and it says its the same update that i have.
Click to expand...
Click to collapse
Grab the RUU.exe from one of the links in this post and run it from Windows. Put your phone into fastboot USB mode in the bootloader before you run it.
ramjet73
First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed (error: i have 3.0.1)
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Flash new radios now my phone is bricked and get teh DLOAD drivers on windows.
I'm gonna take a guess and say you flashed the latest firmware 3.16 without flashing the previous firmware update 3.15.
There is no radio only zip available from the latest OTA update for this very reason.
If this is the case your phone is unrecoverable . back to sprint
Sent from my EVO using xda premium
Shad Stang said:
First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Click to expand...
Click to collapse
u must have did something u wasnt suupposed to do cause meanbean would not hurt your phone in anyway bro
I second this, I am having issues as well.
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Cruise was right, i thought i had the radio that came with 3.15 but i really had the radio that came with 1.22 XD.
Need to Update...not sure how!
cruise350 said:
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Click to expand...
Click to collapse
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
KEMODREAMS said:
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
Click to expand...
Click to collapse
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Need to Update...not sure how!
ronniemayo said:
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Ok so I did that and it says I'm s-on. Now what? Do I take the OTA update that says "This will update your ROM (MeanBean) to version MeanBean_3.06"? If so, once it's downloaded what do I do? Restart into bootloader? Also my Titanium backup is saying that it "could not acquire root privileges" What does that mean? Thanks for your help.
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Shad Stang said:
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Click to expand...
Click to collapse
You should read Captain _Throwback's firmware thread
You can root the latest OTA just click the link in my sig
Sent from my PoS MoPho