Currently running Vipers ROM on gingerbread firmware. Looks like most the newer roms require global firmware. Will changing the firmware screw up the current ROM? Any good tutorials on how to upgrade firmware?
Well by upgrading your firmware it will replace your rom with the stock ics one, and a nandroid backup won't work between different firmwares. Best you can do is backup your apps and stuff, you will have to re flash a recovery and your rom after you upgrade
Sent from my ADR6425LVW using xda app-developers app
That particular rom runs great on ICS firmware.. lock your bootloader (if your s-on if s-off disregard), here's the latest run it as ph98img .. http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ then unlock again(again if your s-on), flash recovery, then refresh viper all will be well..
Sent from my ADR6425LVW using xda app-developers app
Thank you both, I'm currently S-On, is there a recommended way to relock the bootloader?
Hopeful at the end to get S-Off
pmgreen said:
Thank you both, I'm currently S-On, is there a recommended way to relock the bootloader?
Hopeful at the end to get S-Off
Click to expand...
Click to collapse
Assumin you have android SDK installed on your comp.. boot your phone to bootloader and connect to you pc.. open a cmd prompt and type the following hitting enter at the end of each line:
cd c:/android (or whatever your folders called mines c:/android) [enter]
fastboot devices [enter]
fastboot oem lock [enter]
To unlock you'll need you unlock_code.bin in that folder and these commands:
cd c:/android [enter]
fastboot devices [enter]
fastboot flash unlocktoken Unlock_code.bin [enter]
*remember this does a factory reset*
Sent from my ADR6425LVW using xda app-developers app
pmgreen said:
Thank you both, I'm currently S-On, is there a recommended way to relock the bootloader?
Hopeful at the end to get S-Off
Click to expand...
Click to collapse
The way I've done it in the past is:
copy the PH98IMG.zip to the root of the external SD
"adb reboot bootloader"
"fastboot oem lock"
From the fastboot menu, select BOOTLOADER with the power button
It will switch to bootloader mode, scan the SD, and find the file
Press VolUp to start the flash
When it's done, remove the PH98IMG from the SD
Once you're done, go through the unlock and root process to get to stock rooted, enable ADB, run controlbear, do the wire trick when it tells you, and you're s-off
Related
Rooted my original 3d easily. Had to order a replacement and unlocked the bootloader with htcdev method. Now I cannot seem to flash recovery. Tried twrp 1.1, 2.0, 2.1 using PG86IMG through the bootloader.. finds the file , gets to parsing then stops....any suggestions?
Sent from my PG86100 using xda premium
H-boot 1.5?
If so check the forum there are a few work arounds. I unrooted and now want to root it back but not sure what version to use. Tried the htcdev unlock but my phone still shows locked. ! good thing is it is still s-off though and hope that will make the rooting process easier. Go to the Dev section and search there for the information to root.
Maybe try a different recovery file
Have you tried any other recovery files? I believe i had the issue too when trying to flash recovery, I ended up having to use CWM by revolutionary.
Mindripper72 said:
Rooted my original 3d easily. Had to order a replacement and unlocked the bootloader with htcdev method. Now I cannot seem to flash recovery. Tried twrp 1.1, 2.0, 2.1 using PG86IMG through the bootloader.. finds the file , gets to parsing then stops....any suggestions?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
a few things here....
your NAND internal memory is not unlocked (meaning you are "s-on") so you cannot flash recoveries through the bootloader if i am not mistaken.
install adb, and use adb to flash recovery.
either way, using adb will get the job done.
here is the command:
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot
My understanding is the best recovery to use with HBOOT 1.5 is 4EXT as it allows you to SmartFlash ROM's with S-On. Check that out first and see if it helps with your issues.
http://forum.xda-developers.com/showthread.php?t=1561999
xCLUx said:
a few things here....
your NAND internal memory is not unlocked (meaning you are "s-on") so you cannot flash recoveries through the bootloader if i am not mistaken.
install adb, and use adb to flash recovery.
either way, using adb will get the job done.
here is the command:
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot
Click to expand...
Click to collapse
He is HTC unlocked, which unlocks the NAND without touching the S-ON flag. Only the boot partition remains locked.
@OP
You cant flash unsigned PG86IMGs. So flash the recovery using fastboot.
Put your recovery.img in fastboot folder and Boot into boot loader > select fastboot > connect to PC > open command prompt > navigate to fastboot folder > type "fastboot flash recovery recovery.img" (without quotes).
then check if it works...
hope this helps.................
mnomaanw said:
He is HTC unlocked, which unlocks the NAND without touching the S-ON flag. Only the boot partition remains locked.
@OP
You cant flash unsigned PG86IMGs. So flash the recovery using fastboot.
Put your recovery.img in fastboot folder and Boot into boot loader > select fastboot > connect to PC > open command prompt > navigate to fastboot folder > type "fastboot flash recovery recovery.img" (without quotes).
then check if it works...
hope this helps.................
Click to expand...
Click to collapse
ah, yes you are correct. thank you for the clarification. i am not all there today.. ha. very tired.
Trying to re-lock my Rezound using fastboot. When I dbl click fastboot on PC, a black cmd window briefly flashes then disappears. help?
fastboot is a command line app. Open a command window and type "fastboot oem lock"
that's what i tried first, then got a "waiting for device" message. I figured i didn't have my phone set right? here was my process...
1. rebooted phone to hboot
2. connected to computer
3. opened command window
4. cd to the correct directory
5. typed the "fastboot oem lock" command
6. received "waiting for device" message
???
novakrj said:
that's what i tried first, then got a "waiting for device" message. I figured i didn't have my phone set right? here was my process...
1. rebooted phone to hboot
2. connected to computer
3. opened command window
4. cd to the correct directory
5. typed the "fastboot oem lock" command
6. received "waiting for device" message
???
Click to expand...
Click to collapse
Make sure you go into fastboot once you're in the HBoot menu or it won't be able to communicate with the device
Make sure you have HTC Sync or some other Rezound-compatible drivers installed. It needs that for fastboot and adb to communicate with your phone.
dplane said:
Make sure you go into fastboot once you're in the HBoot menu or it won't be able to communicate with the device
Click to expand...
Click to collapse
You have to be I fast boot, hboot
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
Same thing happened to me. Make sure when you plug in the usb cable, the phone connects as a disk drive, not charge only.
Are you trying to re lock or go S-on? I thought that flashing the command fastboot OEM lock would put S-on rather than relock.
Sent from my ADR6425LVW using Tapatalk 2
ended up i needed both bits of advice.
I hadn't reinstalled htc sync files since a pc reformat a month ago, and i needed to enter fastboot once in hboot.
thanks guys
Mr. Boom said:
Are you trying to re lock or go S-on? I thought that flashing the command fastboot OEM lock would put S-on rather than relock.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
no.
fastboot oem lock is changing hboot to relocked
s-on command is something like fastboot write secureflag3 or something- look it up don't use what i just posted. if you do go s-on make sure you just ran a RUU
Mr. Boom said:
Are you trying to re lock or go S-on? I thought that flashing the command fastboot OEM lock would put S-on rather than relock.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
"Fastboot OEM lock" is to lock the bootloader.
"Fastboot OEM writesecureflag3" is to go back to s-on
Sent from my Galaxy Nexus
1. Reboot to fastboot.
This can be done in 3 ways:
A. from the power menu (assuming the rom has it
B. Shut down completely. Battery pull to make sure. Then hold press amd hold Vol Down, then press and hold Power and keep holding down both.
C. Use the command:
adb reboot bootloader
2. Use fastboot to relock bootloader.
Sent from my Rezound
since last we spoke...
was able to relock
flashed the ruu to get back to stock
updated OTA to ICS
unlocked again
flashed aman ra in fastboot
rebooted
the plot thickens...
when i reboot to recovery, it reboots to android stock, not aman ra, hence, no root?
thoughts?
novakrj said:
since last we spoke...
was able to relock
flashed the ruu to get back to stock
updated OTA to ICS
unlocked again
flashed aman ra in fastboot
rebooted
the plot thickens...
when i reboot to recovery, it reboots to android stock, not aman ra, hence, no root?
thoughts?
Click to expand...
Click to collapse
just try flashing Amon Ra again
should i wipe anything first?
novakrj said:
should i wipe anything first?
Click to expand...
Click to collapse
No, just fastboot flash.
Sent from my Rezound
still no go on second flash attempt. still showing android system recovery, not aman ra. tried to install su superuser in the developer menu in android system recovery to achieve root but didn't take.
thanks if anybody has any ideas. I'll just keep searching threads...i usually miss something pretty obvious.
edit: just in case this helps...
when i boot into recovery the top of the screen reads "Android system recovery"
at the bottom of the screen it says:
RA Revamped
Build: RA VIGOR-v3.15-getitnowmarketing
novakrj said:
still no go on second flash attempt. still showing android system recovery, not aman ra. tried to install su superuser in the developer menu in android system recovery to achieve root but didn't take.
thanks if anybody has any ideas. I'll just keep searching threads...i usually miss something pretty obvious.
edit: just in case this helps...
when i boot into recovery the top of the screen reads "Android system recovery"
at the bottom of the screen it says:
RA Revamped
Build: RA VIGOR-v3.15-getitnowmarketing
Click to expand...
Click to collapse
Yeah that's amon ra.
Now flash the SuperSu zip file.
(the install su doesnt work last time I checked.)
You can get the SuperSu zip in Ashton's ICS thread.
Sent from my Rezound
beautiful....Thank you!
Have to ask this as I'm completely new to android and installing new ROM's...
The instructions for a certain rom say: Reboot to bootloader to flash PH98IMG.zip if you were identified as S-ON.
Does this mean to let the bootloader preform the "update" it's found? Because it seems to do this automatically when I get into the bootloader....
thanks for helping!
nissmo66 said:
Have to ask this as I'm completely new to android and installing new ROM's...
The instructions for a certain rom say: Reboot to bootloader to flash PH98IMG.zip if you were identified as S-ON.
Does this mean to let the bootloader preform the "update" it's found? Because it seems to do this automatically when I get into the bootloader....
thanks for helping!
Click to expand...
Click to collapse
I have never flashed a rom by flashing the PH98IMG.zip because for some reason it hasn't worked for me, maybe i just did something wrong.
What I do instead is extract the rom .zip on your computer. Then, put the boot.img file into the platform-tools folder in the android sdk (assuming you already have the android sdk installed). Then, flash the rom, then power the phone off, then press and hold power+volume down to boot into hboot. From there you select fastboot. At the top you should see fastboot usb in the red box. Then, type into command prompt or terminal (for mac) fastboot flash boot boot.img After that, just reboot and the new rom should boot just fine.
Idk if you have a mac, but this is the tutorial I used to download and set up the adb with my macbook. Its very easy, if you have windows, im sure you could google instructions.
When you put the ROM on your sd card, extract the boot.img and put it in a ph98img.zip file. Install ROM, go to bootloader and it should ask you it update. Update and you're good to go. Keep in mind I don't like using command prompts
Sent from my ADR6425LVW using xda app-developers app
jmez900 said:
When you put the ROM on your sd card, extract the boot.img and put it in a ph98img.zip file. Install ROM, go to bootloader and it should ask you it update. Update and you're good to go. Keep in mind I don't like using command prompts
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
To add onto that, depending on how you get to the bootloader, it may boot into fastboot initially. If so, just hit the power button on the BOOTLOADER option and it will do the rest.
I've read that the only way to flash a kernel with s-on from fastboot is you have to use adb. I guess when you reboot the bootloader from adb you gain access to the recovery partition but if your s-on just booting into the recovery doesn't work. I've decided to stay s-on (personal preference) and flashed multiple kernels with the zip. But back to your question is yes let the update go through and the kernel should be installed.
Sent from my SCH-I815 using XDA Premium HD app
Thanks all!
Sent from my Nexus 10 using xda app-developers app
I am trying to restock Verizon Droid DNA
Followed all the guided method , got to a point of where Relocked/S-ON
Unable to use RUU downloaded , check MD5 all correct
Try moonshine to enable S-OFF
flashed firmware and now stuck at 2.06 firmware
How do i restock?
I am unable to boot anything just the bootloader
fastboot is working fine
Unable to flash any zip hboot downloaded , keep getting signature fail
Unable to Unlocked the bootloader too
I am unable to execute adb commad tho
any suggestion?
BloodRaven2011 said:
I am trying to restock Verizon Droid DNA
Followed all the guided method , got to a point of where Relocked/S-ON
Unable to use RUU downloaded , check MD5 all correct
Try moonshine to enable S-OFF
flashed firmware and now stuck at 2.06 firmware
How do i restock?
I am unable to boot anything just the bootloader
fastboot is working fine
Unable to flash any zip hboot downloaded , keep getting signature fail
Unable to Unlocked the bootloader too
I am unable to execute adb commad tho
any suggestion?
Click to expand...
Click to collapse
You said you tried moonshine to get s-off? did it not work?
You need to be a bit more clear. You are trying to go complete stock or use moonshine to unlock and soff? What error do you get when trying to use ruu?
Hit thanks if I helped! Check out my site at www.circuitsaviors.com
Use moonshine to s off. Go to the thread on how to go back to stock. Follow the directions. The signature is obviously failing because you are s on...
Sent from my HTC6500LVW using xda app-developers app
You might want to check out my thread (http://forum.xda-developers.com/showthread.php?t=2438199), but it's not good news...
jtag is ur only answer. I have a htc dna sitting in my drawer because of this very same reason. I've looked and looked. Sorry
People, you need to RUU BEFORE issuing any s-on commands. I'm seeing this repeatedly.
Phaded said:
People, you need to RUU BEFORE issuing any s-on commands. I'm seeing this repeatedly.
Click to expand...
Click to collapse
This is where the problem rise
I did not realize that is no way to downgrade to stock HBOOT
and the worst part now is i cant do anything
yes , option is to JTAG
BloodRaven2011 said:
This is where the problem rise
I did not realize that is no way to downgrade to stock HBOOT
and the worst part now is i cant do anything
yes , option is to JTAG
Click to expand...
Click to collapse
You could've downgraded your hboot... This also needs to be done before issuing any s-on commands
I am unable to issue a new hboot , i got the signature verification failed. If anyone know how to , it be great , JTAG is my last option tho
Check your PMs. I'd be interested in your results.
I think I had the same signature error a few days ago u need to be on the 1.15 Hboot I couldn't figure it out until i read somewhere not to add a .zip when you rename the hboot zip file and it will flash correctly thru adb hope this helps
http://forum.xda-developers.com/showthread.php?p=42352912
Sent from my HTC6435LVW using Tapatalk 2
xaalfx said:
I think I had the same signature error a few days ago u need to be on the 1.15 Hboot I couldn't figure it out until i read somewhere not to add a .zip when you rename the hboot zip file and it will flash correctly thru adb hope this helps
http://forum.xda-developers.com/showthread.php?p=42352912
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
i am unable to use adb command.
I've been reading thru that before i ask this question
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
I'm confused. Maybe someone can answer.
He flashed the 2.06 firmware successfully. That will flash a the new hboot, radio and recovery.
Unless he has a custom splash screen, why would RUU'ing fail.
What happens if the 2.06 firmware it's flashed again?
Does it pass the checks?
Nvm: he can't RUU because the hboot has to 1.15.
Gungrave223 said:
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
Click to expand...
Click to collapse
all the above failing due to higher fw
and this causing sgnature verification fail
Gungrave223 said:
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
Click to expand...
Click to collapse
fr4nk1yn said:
I'm confused. Maybe someone can answer.
He flashed the 2.06 firmware successfully. That will flash a the new hboot, radio and recovery.
Unless he has a custom splash screen, why would RUU'ing fail.
What happens if the 2.06 firmware it's flashed again?
Does it pass the checks?
Nvm: he can't RUU because the hboot has to 1.15.
Click to expand...
Click to collapse
YEAP ,
It need 1.15
anyhow i can fake this to accept a lower hboot?
with a different sgnature?
BloodRaven2011 said:
YEAP ,
It need 1.15
anyhow i can fake this to accept a lower hboot?
with a different sgnature?
Click to expand...
Click to collapse
It's not a signature issue, it's encryption issue. Newer hboots are unable to decrypt the older ruu zip. If you have a "stockish" rom, you can reflash the 2.06 firmware zip. this will flash a signed kernel and recovery and allow the device to _attempt_ to boot to android. If you can get to android, you can then attempt to s-off again.
If moonshine repeatedly fails (don't drink and shine) and also revone repeatedly fails try this:
In moonshine folder you'll see dnashellroot.apk package
1.) adb install dnashellroot.apk
2.) adb shell
3.) am start -n c.fyf/.MainActivity
4.) (wait 10 seconds)
5.) /dev/sh ($ should turn into #)
6.) echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
^do NOT screw that command up, copy/paste it or risk a brick
7.) exit
8.) exit
9.) adb reboot bootloader
10.) fastboot getvar cid
if it's 22222222, you are good. Proceed to htcdev to unlock, then you can s-off using facepalm.
beaups said:
It's not a signature issue, it's encryption issue. Newer hboots are unable to decrypt the older ruu zip. If you have a "stockish" rom, you can reflash the 2.06 firmware zip. this will flash a signed kernel and recovery and allow the device to _attempt_ to boot to android. If you can get to android, you can then attempt to s-off again.
If moonshine repeatedly fails (don't drink and shine) and also revone repeatedly fails try this:
In moonshine folder you'll see dnashellroot.apk package
1.) adb install dnashellroot.apk
2.) adb shell
3.) am start -n c.fyf/.MainActivity
4.) (wait 10 seconds)
5.) /dev/sh ($ should turn into #)
6.) echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
^do NOT screw that command up, copy/paste it or risk a brick
7.) exit
8.) exit
9.) adb reboot bootloader
10.) fastboot getvar cid
if it's 22222222, you are good. Proceed to htcdev to unlock, then you can s-off using facepalm.
Click to expand...
Click to collapse
I wish i can execute adb command
What seems to be an issue
i dont have any ROM installed now , and the only thing that i can use is fastboot command
I am familiar with adb , and plus i've created custom ROM before but not for HTC
trying to help a cousin but hell , JTAG here is unfamiliar with this model ( not available in Malaysia )
so i would think , this is a deadend but i never gave hope.
Will try to figure something and all help is much appreaciated.
My buddy handed me his Amaze to unroot and get back to stock so he could give to his mom. I used the All-in-One kit to relock the bootloader and flash the "mainver fix" and followed the instructions step by step to get back to stock but am now stuck. When I try to install the stock RUU it says the hboot version is older and asks if I want to reboot. Ok, so I tried flashing a newer version of Hboot and am now on 1.93.0002 but same outcome. Now, even worse, I can't get to recovery nor will it let me flash an img to get a recovery in place so I only have the bootloader now. It see's the IMG and loads it but doesn't ask to accept the update like it normally would. No matter what I name it, nothing loads or flashes. Whats the next step?
Have you tried using adb to flash the ruu?
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
vgs929 said:
Have you tried using adb to flash the ruu?
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I was at work and didnt have ADB setup on my comp. Went home and used ADB and was fine, thanks for the reminder!
In case anyone ever stumbles onto this issue, this is what you need to do.
Go to your ADB folder in your C drive and paste the RUU file. Name it something easy to type, in my case I changed it to " PH98IMG ". Then, open a command prompt and type EXACTLY as follows:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip filename.zip (example: fastboot flash zip PH98IMG.zip)
When its finished:
fastboot reboot
Boom, back to stock. Only thing I can think of is make sure you have a charged battery and the phone placed somewhere to where it wont become unplugged or the battery fall out as that could easily brick your device..