Related
Preamble
This is the S-OFF upgrade from GingerBread to HoneyComb
Do not perform this procedure if you have the official HTC hboot, it will not work. You must have a revolutionary hboot (see prerequisites).
***If you performed this procedure with previously and have hboot version 6.14.5555 please update to the new hboot, 6.14.5555 is no longer supported***
Upgrade instructions at the bottom of the procedures.
Prerequisites
You must have performed Revolutionary S-OFF
If running on windows you will need these fastboot drivers
If running the procedure on Linux or MacOS you must have fastboot working.
There are no other software prerequisites for this procedure, it does not matter what ROM/Kernel or recovery you are using.
Don't bother asking for help if you try to do this on a virtual machine, you won't get any.
Run on a real machine.
Windows Instructions
Download this file MD5=c62cc1d0453799a7277abfea444d20e4
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the RUU_Express_B02 directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Alternative Installation Instruction (Any OS)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the RUU_Express_B02_RAW.zip file PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Do not mirror files from this post.
No discussion of Honeycomb content or changes or the relative merits of Gingerbread and Honeycomb. This thread is for the procedure and support thereof only! Also please don't quote the first post because your post becomes an automatic TLDR.
Update Instructions
Use these instructions if you currently have hboot 6.14.5555 - Your data should be preserved but take a backup first just in case.
Method 1
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Copy the file to the root of your external SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
Method 2
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip PG41IMG.zip
[I][COLOR="Red"]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/COLOR][/I]
fastboot reboot
[Revision History]
B02 - updated full version: hboot 6.14.5556
New bootloader to patch bugs with fastboot flashing
- Fastboot flashing splash1 fixed
- Fastboot flashing hboot fixed
Patch for upgrading from a previous version added.
B01 - Initial full version: hboot 6.14.5555
BETA- Developer preview
Special thanks: contradude for the early and riskiest testing, and Maine_Coon for all the ongoing testing
Downgrade to Gingerbread
Preamble
This is the S-OFF downgrade from HoneyComb to S-OFF GingerBread if you are not S-OFF and have a HTC (not revolutionary) hboot then do not do this it will not work.
The full versions of these files will give you a fully functional Gingerbread installation with S-OFF, CWM recovery and boot image with the secure flag turned off.
Windows Instructions
Download this file MD5=f5afc4b457a17f88cc611b40e6c7cdc8
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the Express_Downgrade directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Alternative Installation Instruction (Any OS)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the file downloaded in step1 to PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Do not mirror files from this post.
wow you are really fast, excellent men.
One for me please
reserved 2
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
vancraft said:
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
Click to expand...
Click to collapse
This is an attempt to make downgrading easier for us.
spartan1987 said:
This is an attempt to make downgrading easier for us.
Click to expand...
Click to collapse
Right. That's the "recovery" part.
But its also described as "root, and all". I'm wondering if this allows the installer to root the OTA Honeycomb? Or will more work be required before the install can be further changed (i.e. s-off, eventually upgraded to ICS, etc.)?
It works
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
risb577 said:
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
Click to expand...
Click to collapse
so, does that mean you could, in theory, flash a custom HC rom once we get one?
Throw up some screenshots or a video would you?
edit: oh and test rom manager and titanium backup if you don't mind.
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
stuck on soft brick..
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Maine_Coon said:
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
Click to expand...
Click to collapse
No, as it says in the OP, You MUST be s-off and THEN run an RUU. Accept all updates to include the HC update and the view will be soft bricked. THEN use fastboot to push the mini ruu.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
myowin said:
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Click to expand...
Click to collapse
If it says it's an unrecognized command, then either you do not have fastboot installed, or you haven't gone into environment variables (assuming it's a windows box) and added those commands to the path. try that first (google is your friend and you can google in XDA). Good luck.
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
thank you so much for quick respond..
I think I found it here how to do that.. (for someone like me... )
http://forum.xda-developers.com/showthread.php?t=532719
root
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
I haven't done this yet, but I'm dling the RUU right now to do it and help people troubleshoot.
To answer your question, if you hold down the power button long enough, the view will power off, then you can hold power + vol down to get back into the bootloader and select fastboot mode, then open cmd, type fastboot devices and check to make sure yours shows up, then proceed with pushing the mini-ruu. If I'm wrong guys, correct me. Hope it works out for you.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
Im not sure if this matters, but when I was in soft brick, I rebooted a few times and could not get into the bootloader. It just seemed to ignore the vol down keypress. I then unplugged the usb, powered off from soft brick, and held the vol. down button down even before I hit the power button as I was turning it on. Once I was in bootloader, I just plugged the usb back in.
EDIT: More tips:
1.After I flashed the initial stock ruu, and before I accepted any updates, I turned off fastboot in the power options and enabled usb debugging.
2. I did this from a Windows 7 laptop. When I initially tried to perform the softbrick steps, I got an access denied error message. The files were sent ok, but errored on saving. I closed the command prompt, and re-lauched the command prompt as administrator. The commands sent successfully.
3. Also, once you send the mini ruu over, the Tablet sat in the the oem loader with a 70% full progress bar after I successfully sent the mini ruu. I waited about 10 minutes because I was unsure how to proceed. I finally issued:
fastboot reboot-bootloader
Once back into bootloader, I mounted usb storage, copied SU to the card, and flashed from zip
risb577 said:
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
Click to expand...
Click to collapse
Yeah, rom manager won't work bc we don't have official support from Koush for CWM recovery so that's no issue, I was just curious is all lol. I'm glad to hear titanium detects root, as that was an issue initially for the view. Try to backup your apps, test radios (3g, 4g, wifi, bluetooth, GPS, ETC), run quadrant. I don't know how familiar you are with honeycomb to test out all of it's functions, but we are going to need a few people to test this out for globatron so he can make fixes and/or adjustments as necessary, which is why he specifically asked for devs and people familiar with troubleshooting to do this first. That's the beauty of open source, we're all guinea pigs.
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
soft brick screen
ElAguila said:
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
Click to expand...
Click to collapse
It looks like this pic. Plus another clue you are soft bricked is it stays here longer than 10 minutes if you care to wait lol
Back from Moto-land with Rezound. I've flashed several ROMS and one I would like to flash now says that I must firs be on the leaked 3.11.605.22 firmware.
I thought that when I flashed a rom and it rebooted into bootloader to install the PH98IMG.zip file, that it was installing the necessary firmware. I'm confused.
How do I get to the necessary Leaked firmware. I've searched and googled, but everything I find, indicates that I cannot install the leak, because I have already used the HTC unlock tool. Again, confused
I appreciate your help!
ruu isn't a Tom that loads the kernel afterwards. the leak is flashed all at once which appears to be how kernels are flashed. flashing the leak requires the lock then it flashes everything together but remember it wipes all data with exception of external sd
Followup Q1: So is it possible to get to the RUU 3.11.605.22 firmware, WITHOUT re-locking and flashing the leak? (not concerned at all about full wipe, do it with each rom)
Q2: If I do have to re-lock and then flash the leak, do I first have to return to a 100% stock state (ie, restore all the bloat-ware and such)? (if you've ever had a Bionic you know what I'm talking about)
http://forum.xda-developers.com/showthread.php?p=23700622
Sent from my ADR6425LVW using Tapatalk
nukeboyt said:
Followup Q1: So is it possible to get to the RUU 3.11.605.22 firmware, WITHOUT re-locking and flashing the leak? (not concerned at all about full wipe, do it with each rom)
Q2: If I do have to re-lock and then flash the leak, do I first have to return to a 100% stock state (ie, restore all the bloat-ware and such)? (if you've ever had a Bionic you know what I'm talking about)
Click to expand...
Click to collapse
Originally Posted by JoelZ9614 View Post
Here are the instructions...
Download...
rename the zip to PH98IMG.zip
put on your sdcard
reboot to bootloader
fastboot oem lock
reboot to bootloader again
flash.
reboot to bootloader
[if it says security warning and tampered at the top flash again..after continue to next step]
fastboot flash unlocktoken Unlock_code.bin [of course only if u have ur original Unlock_code.bin if not do the whole htc thing again]
reboot......
A little confused. Android Police says you have to be fully stock with a locked bootloader to install 605.22. According to this, I don't have to be stock, I just have to relock it, and be aware that the full RUU install with radios will wipe my entire phone except external SD? (I wouldn't ask this except that it directly contradicts the AP post.)
And do we have the ability to re-root the resulting ICS installation?
And there's no other way to apply just the radios and the pre-rooted (Non-RUU?) version?
Does the pre-rooted version also do a full wipe?
cpurick said:
A little confused. Android Police says you have to be fully stock with a locked bootloader to install 605.22. According to this, I don't have to be stock, I just have to relock it, and be aware that the full RUU install with radios will wipe my entire phone except external SD? (I wouldn't ask this except that it directly contradicts the AP post.)
And do we have the ability to re-root the resulting ICS installation?
And there's no other way to apply just the radios and the pre-rooted (Non-RUU?) version?
Does the pre-rooted version also do a full wipe?
Click to expand...
Click to collapse
So far no other way to get the new radios , sounds like the only reason the OTA leak worked was the way it was packaged. This new leak isn't packaged the same way so you would have to relock and run the RUU to get the new radios.
Personally, all I did was reflash stock recovery before hand, but I had to run it a few times to get it to work fully and at one point I just relocked with amon recovery installed and ran it and it worked just fine. It wipes recovery as part of the installation and installs the updated stock recovery.
andybones said:
Originally Posted by JoelZ9614 View Post
Here are the instructions...
Download...
rename the zip to PH98IMG.zip
put on your sdcard
reboot to bootloader
fastboot oem lock
reboot to bootloader again
flash.
reboot to bootloader
[if it says security warning and tampered at the top flash again..after continue to next step]
fastboot flash unlocktoken Unlock_code.bin [of course only if u have ur original Unlock_code.bin if not do the whole htc thing again]
reboot......
Click to expand...
Click to collapse
Sorry for the questions, but when I do all of this, will I still have the Amon Ra recovery, or does this return to the stock recovery (which I assume it does)?
When the PH file is flashed in recovery it will overwrite whatever recovery you had flashed previously and leave you with stock everything...including recovery.
Sent from my ADR6425LVW
I was able to upgrade to the new ROM and then re-unlock my phone. But when I put Amon Ra in SD folder as PH98IMG.zip and reboot to the loader, I am never prompted to install it. Furthermore, attempts to get into recovery result in a green circular icon followed by a red triangle with exclamation point.
I tried all sorts of resets and reboots. Right now I have a green recovery option, but no working recovery. The top line says "UNLOCKED".
I've tried Amon Ra 3.13 and 3.14.
Download this file.
Place it in the same folder that you setup for the HTCdev unlock.
Rename it to "recovery."
Go to the command prompt and type in this command: cd c:\nameoffolder (mine is c:\Android for example)
Boot into Hboot
Select Fastboot
Connect to PC
Then type this exactly : fastboot flash recovery recovery.img
That should get you loaded with Amon Ra.
http://forum.xda-developers.com/showthread.php?p=19205213
Installation instructions are in the OP.
What you see now when you select recovery in hboot is what is considered stock recovery
Sent from my ADR6425LVW using Tapatalk
EmerikL said:
Download this file.
Place it in the same folder that you setup for the HTCdev unlock.
Rename it to "recovery."
Go to the command prompt and type in this command: cd c:\nameoffolder (mine is c:\Android for example)
Boot into Hboot
Select Fastboot
Connect to PC
Then type this exactly : fastboot flash recovery recovery.img
That should get you loaded with Amon Ra.
Click to expand...
Click to collapse
Thank you. I had already figured it out, and this is exactly what the problem was. Last time I flashed with a PH98IMG version of recovery, but this latest version that I have is for Fastboot. Thanks!
Never thought it would be such a relief to see the "TAMPERED" warning, lol.
All is good!
ZIP to fix mainver problems
http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4
I've just unlocked my rezound and i'm trying to root via my mac. i downloaded the amonra recovery and put it in my android folder. i've got my phone rebooted and i'm in the fastboot usb menu. i have bootloader, reboot, reboot bootloader, and power down as options.
a little help?
maybe i'm just not meant to root my phone :-(
On mine the command was ./fastboot recovery recovery.img as long as you are in fastboot in the bootloader.
Sent from my ADR6425LVW using XDA
Since you're in fastboot usb, make sure the recovery image is in the android tools folder containing fastboot.exe. The command is "fastboot flash recovery recovery.img" without the quotes and recovery.img being the name of the image file you put in your android tools folder.
OLDsJUNKIE said:
Since you're in fastboot usb, make sure the recovery image is in the android tools folder containing fastboot.exe. The command is "fastboot flash recovery recovery.img" without the quotes and recovery.img being the name of the image file you put in your android tools folder.
Click to expand...
Click to collapse
Damn knew i was missing something lol well said.
alright, got amonra installed with the right path and all, went to dev options, installed su & superuser, rebooted, i see superuser, but NOTHING is getting root access.... titanium backup, file explorer... nothing.
so, i don't think it's really rooted. sigh.
if it makes a difference, i was on the ICS leak prior to all this. make a difference?
Not really sure are you on stock right now or did you flash a rooted Rom?
Sent from my ADR6425LVW using XDA
tp62688 said:
Not really sure are you on stock right now or did you flash a rooted Rom?
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
stock right now, no rooted rom.
brewner said:
stock right now, no rooted rom.
Click to expand...
Click to collapse
Have you rebooted since rooting through Amon and installing SU? If that doesn't solve it, installing one of the rooted ROMs should.
OLDsJUNKIE said:
Have you rebooted since rooting through Amon and installing SU? If that doesn't solve it, installing one of the rooted ROMs should.
Click to expand...
Click to collapse
I concur lol
OLDsJUNKIE said:
Have you rebooted since rooting through Amon and installing SU? If that doesn't solve it, installing one of the rooted ROMs should.
Click to expand...
Click to collapse
Suggestions?
I would just flash a prerooted Rom thats what I did with mine installed the root user access from amonra didn't work for me. You gonna go with GB or ICS?
tp62688 said:
I would just flash a prerooted Rom thats what I did with mine installed the root user access from amonra didn't work for me. You gonna go with GB or ICS?
Click to expand...
Click to collapse
I would prefer ICS.
I would read up on BAMF ICS or Cleanrom ICS and follow the steps to flash as long as you are on the new firmware. There are others but those are the ones that I've tried I'm currently on BAMF.
BAMF looks more straightforward. waiting for a response on a question over there.
What did you need to know?
it *appears* that i'm ready to flash. there are two files that i've downloaded. one is a rom, the other a kernal. i'm trying to figure out which is which and what my next steps are.
here are the instructions, and i'm wondering how important the nandroid backup is, since i'm basically starting fresh.
Download rom file and PH98IMGnewfirmwarepeople.zip
Rename PH98IMGnewfirmwarepeople.zip to "PH98IMG.zip" without the quotes
Place both files on external SD card and reboot to recovery
Make a nandroid backup
Wipe data, cache, dalvic cache, and system
Flash the rom through the "Flash Zip Menu" in recovery
From main recovery screen, choose "Developer Menu"
Select "Reboot to Bootloader" from the developer menu
Phone will reboot to hboot, you may have to select bootloader from hboot screen
Bootloader will load the PH98IMG.zip, select "Yes" to update.
Rock on with your bad self and reboot system
The one with BAMF in the title is typically the Rom and the kernel would either be oldfirmwarepeople.zip or newfirmwarepeople.zip this file has to be renamed as PH98IMG.zip and place on the ext sd card. Then in amon-ra wipe everything and flash the rom zip then from the developer menu boot into bootloader and let it apply the kernel update then it will reboot then profit.
do you see any issues with following the directions above?
I am running a rooted Rez with Amon Ra Recovery which is otherwise stock ICS. I have tried three times to install the latest Global OTA. Each time the install fails after an attempt is made to install the downloaded package. The phone reboots into Amon Ra and I see the following messages.
Installing Update
Wrong Task ID 221384E: Error in /cache/fumo/OTAPkg.zip
Status 1
Installation Aborted
Anyone know what is happening? Thanks in advance for the help.
You need the stock recovery to do update....
Sent from my SCH-1605 / Galaxy Note 2 using Tapatalk v 2.4.13
more
Found out hard way: you can't just be on the last official RUU (3.14.605.12) to get the new update from Verizon.
ALSO dammit you have to have previously taken the small February update to 3.14.605.13. The update's name mentions
605.13 in its title. The problem is that you can't get that little update anymore!!!!
Those of us with only 605.12 may have to wait until the next RUU is issued. Gripes me.
You realise someone posted the full ruu zip in this thread. You don't have to get it from software update thing
Sent from my ADR6425LVW using xda app-developers app
tried that
still looks for 605.13 and craps out with an error message!
how to solve that
In February, Flyhalf205 uploaded the 605.13 OTA.zip in another thread.
The one I could not find anywhere.
You take that little one, rename it update.zip, and flash in hboot.
Do a factory reset and it'll boot up.
Then you can get the current OTA from Verizon.
13 zip is here
13 zip
http://forum.xda-developers.com/showthread.php?p=40819479
Sent from my SCH-1605 / Galaxy Note 2 using Tapatalk v 2.4.13
Here is the FIX
michaelbsheldon said:
still looks for 605.13 and craps out with an error message!
Click to expand...
Click to collapse
Download the PH98IMG.zip in the Attachment and put it on your SD Card
1. Flash the above file in Hboot and delete it after done flashing
2. Put the new update.zip on to your SD card.
3. Reboot into Bootloader and choose Recovery
4. It will flash the new update.
5. Download the new.global.firm.PH98IMG.zip from HERE ,rename it to PH98IMG.zip and flash it in Hboot to get the latest Hboot, Radio, ......
6. Done
Just to Be Sure
I managed to get the OTA getting me to 605.13. So if I want to get to 605.14, do I just get the new firmware zip file, rename it, place it onto the sd card, and install it in HBoot and I am good to go? Just checking to be sure. Thanks.
rjr1049 said:
I managed to get the OTA getting me to 605.13. So if I want to get to 605.14, do I just get the new firmware zip file, rename it, place it onto the sd card, and install it in HBoot and I am good to go? Just checking to be sure. Thanks.
Click to expand...
Click to collapse
I just tried but no go. It said there is no update script or something. Any solution?
nbhnohome said:
Download the PH98IMG.zip in the Attachment and put it on your SD Card
1. Flash the above file in Hboot and delete it after done flashing
2. Put the new update.zip on to your SD card.
3. Reboot into Bootloader and choose Recovery
4. It will flash the new update.
5. Download the new.global.firm.PH98IMG.zip from HERE ,rename it to PH98IMG.zip and flash it in Hboot to get the latest Hboot, Radio, ......
6. Done
Click to expand...
Click to collapse
Is this the same process if the device is s-on?
nissmo66 said:
Is this the same process if the device is s-on?
Click to expand...
Click to collapse
You can only use the official update with your bootloader locked and a non modified stock rom or you need to wait for a new RUU to come out.
mjones73 said:
You can only use the official update with your bootloader locked and a non modified stock rom or you need to wait for a new RUU to come out.
Click to expand...
Click to collapse
-or- s-off if s-off and on the latest ota it doesn't matter if you are locked or unlocked. You will need to flash a custom recovery and su when the ruu is done but the update will complete. You can also downgrade the bootloader (hboot) back to a modified one such as vinyl freaks if and only if s-off.
Sent from my Nexus 7 using Tapatalk HD
dottat said:
-or- s-off if s-off and on the latest ota it doesn't matter if you are locked or unlocked. You will need to flash a custom recovery and su when the ruu is done but the update will complete. You can also downgrade the bootloader (hboot) back to a modified one such as vinyl freaks if and only if s-off.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
If you're s-off, you can flash the firmware on it's own and not have to touch the recovery...
mjones73 said:
If you're s-off, you can flash the firmware on it's own and not have to touch the recovery...
Click to expand...
Click to collapse
True also.....
Sent from my Nexus 7 using Tapatalk HD
to get stock recovery open the zip take the recovery and use fastboot and flash recovery.img right guys?
dcasun said:
to get stock recovery open the zip take the recovery and use fastboot and flash recovery.img right guys?
Click to expand...
Click to collapse
yes... put the recovery.img in the same directory as your fastboot command and from a command prompt (at the same directory as your fastboot.exe) issue the command fastboot flash recovery recovery.img
dottat said:
yes... put the recovery.img in the same directory as your fastboot command and from a command prompt (at the same directory as your fastboot.exe) issue the command fastboot flash recovery recovery.img
Click to expand...
Click to collapse
place the recovery.img in platform tools
type fastboot flash recovery recovery.img
and lock the bootloader
run the update
reunlock the bootloader
flash custom recovery
and done
dottat said:
yes... put the recovery.img in the same directory as your fastboot command and from a command prompt (at the same directory as your fastboot.exe) issue the command fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I was on 605.13 stock ICS, rooted and with Amon Ra recovery. I grabbed the 605.12 recover and flashed it and relocked the boot loader. I have tried multiple times to run the OTA (both pulling from Verizon and by putting it on the SD card). It keeps failing with the same 'Wrong Task ID' error mentioned by OP. I even wiped the SD Card, did clear storage from stock recovery, a couple of factory resets to no avail.
Can someone help? Is it possible that the 605.13 OTA a month or so ago didn't install properly since I had Amon Ra. In Software it shows I am at 605.13 so I doubt that. But would you suggest running the 605.13 Update.zip manually and then try to pull the OTA?
misalies said:
I was on 605.13 stock ICS, rooted and with Amon Ra recovery. I grabbed the 605.12 recover and flashed it and relocked the boot loader. I have tried multiple times to run the OTA (both pulling from Verizon and by putting it on the SD card). It keeps failing with the same 'Wrong Task ID' error mentioned by OP. I even wiped the SD Card, did clear storage from stock recovery, a couple of factory resets to no avail.
Can someone help? Is it possible that the 605.13 OTA a month or so ago didn't install properly since I had Amon Ra. In Software it shows I am at 605.13 so I doubt that. But would you suggest running the 605.13 Update.zip manually and then try to pull the OTA?
Click to expand...
Click to collapse
You will need to relock the bootloader then run the 605.12 RUU and let that boot up and not modify anything then you will get the 605.13 update first and then the latest after that, that is how I got the update and had no problems at all.
I have been trying to download the WinDroid HTC Rezound Toolkit 2.1.zip and everything I click on to download seems to be spam please help!
I just want to get root access for arliborator for appradio2. I have unlocked the bootloader on htcdev.
Thanks
jipper331 said:
I have been trying to download the WinDroid HTC Rezound Toolkit 2.1.zip and everything I click on to download seems to be spam please help!
I just want to get root access for arliborator for appradio2. I have unlocked the bootloader on htcdev.
Thanks
Click to expand...
Click to collapse
if you want root all you gotta do is download amon ra 3.1.6 and flash it via fastboot....in that recovery you will see a developers option (advanced options) select that and inside it youll see install su & superuser...once you do that you are rooted bud
Yeah, the toolkit is... ummm... less than optimum.
Remember you don't even have to flash Amon Ra, or any other recovery... just download and unzip into your adb/fastboot directory, then reboot into hboot and start fastboot and enter:
fastboot boot recovery.img (replace "recovery.img" with the img name from the Amon Ra ZIP file)
then use the options in Amon Ra to install SuperSU (root) from there you can update to the latest version after it is installed.
acejavelin said:
Yeah, the toolkit is... ummm... less than optimum.
Remember you don't even have to flash Amon Ra, or any other recovery... just download and unzip into your adb/fastboot directory, then reboot into hboot and start fastboot and enter:
fastboot boot recovery.img (replace "recovery.img" with the img name from the Amon Ra ZIP file)
then use the options in Amon Ra to install SuperSU (root) from there you can update to the latest version after it is installed.
Click to expand...
Click to collapse
thank yall for the responses!
oh ok. Where would you download it from? Could you send me a link? It would be great if you could point me to a youtube video of someone doing it or I would need a little more in depth of what to do to install (step by step).
jipper331 said:
thank yall for the responses!
oh ok. Where would you download it from? Could you send me a link? It would be great if you could point me to a youtube video of someone doing it or I would need a little more in depth of what to do to install (step by step).
Click to expand...
Click to collapse
there is guides posted for this already...amon ra can be found in the rezound original development thread....at the top right type in the search options for it and it will come up...also in google type in rezound fastboot recovery and theres many ways to show you how....for fastbooting a recovery the code ace javelin posted above is correct...im not at all trying to come of rude just very busy developing kit kat right now
jipper331 said:
thank yall for the responses!
oh ok. Where would you download it from? Could you send me a link? It would be great if you could point me to a youtube video of someone doing it or I would need a little more in depth of what to do to install (step by step).
Click to expand...
Click to collapse
If your bootloader is unlocked already, then it is super simple because you are already unlocked and therefore have working ADB...
1) Just download a recovery, CWM, TWRP, or Amon Ra
2) Extract the ZIP to your [adb sdk directory]\platform-tools\ directory (or mini-adb if you went that route)
3) Download the latest SuperSU here: http://download.chainfire.eu/supersu
4) Copy UPDATE-SuperSU-v1.80.zip to the root of your SD Card
5) On your PC open a command prompt in your adb directory
6) type "adb reboot bootloader", wait for it to complete and start fastboot
7) type "fastboot boot recovery.img" (substitute the name of the img file from the recovery zip for recovery.img)
8) Install/flash (depending on recovery) and find the UPDATE-SuperSU-v1.80.zip file and install/flash it
9) reboot
10) done, enjoy root
acejavelin said:
If your bootloader is unlocked already, then it is super simple because you are already unlocked and therefore have working ADB...
1) Just download a recovery, CWM, TWRP, or Amon Ra
2) Extract the ZIP to your [adb sdk directory]\platform-tools\ directory (or mini-adb if you went that route)
3) Download the latest SuperSU here: http://download.chainfire.eu/supersu
4) Copy UPDATE-SuperSU-v1.80.zip to the root of your SD Card
5) On your PC open a command prompt in your adb directory
6) type "adb reboot bootloader", wait for it to complete and start fastboot
7) type "fastboot boot recovery.img" (substitute the name of the img file from the recovery zip for recovery.img)
8) Install/flash (depending on recovery) and find the UPDATE-SuperSU-v1.80.zip file and install/flash it
9) reboot
10) done, enjoy root
Click to expand...
Click to collapse
Will this work on Windows 8.1 64 bit? I've managed to unlock the bootloader, but cannot get SU installed. Thanks.
Lodingi said:
Will this work on Windows 8.1 64 bit? I've managed to unlock the bootloader, but cannot get SU installed. Thanks.
Click to expand...
Click to collapse
I think you need different drivers for Windows 8, I don't have a Windows 8 machine so I really can't help you with that, sorey... Maybe @REV3NT3CH can help here.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
I think you need different drivers for Windows 8, I don't have a Windows 8 machine so I really can't help you with that, sorey... Maybe @REV3NT3CH can help here.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
sadly with windows 8 drivers can be a big issue...i do have some drivers that may work that i can upload when i get back from lunch but cant guarantee if it will...its trial and error for some people...windows 8 to me anyway has still way too many bugs to iron out so i try to stay away from it but ill be glad to help with what i can do
[
found the twrp link and downloaded it. Verizon Open Recovery - TWRP
Then copied it to where my fastboot file is.
C:\Android\
then tried fastboot thing again nothing.................,
Bill-dry said:
[
found the twrp link and downloaded it. Verizon Open Recovery - TWRP
Then copied it to where my fastboot file is.
C:\Android\
then tried fastboot thing again nothing.................,
Click to expand...
Click to collapse
When in fastboot, type fastboot devices and see if it sees your phone... My guess is you have a driver issue.
Sent from my Nexus 4 using Tapatalk