Detailed in this post is a way to downgrade your Incredible S Hboot version 1.16 and above to version 1.13 so it can be s-offed using revolutionary. This is made possible with the TacoRoot exploit, an unsecured kernel, misc_version_universal and an automated goldcard algorithm.
Please note that phones with the latest ICS hboot (2.02 currently) will have to be bootloader UNLOCKED from htcdev.com. If your hboot 2.02 phone does not have an unlocked bootloader, do NOT run this script.
(Insert usual disclaimer: not responsible for your bricked phone blah blah etc).
Beware also that you will lose everything on the phone so back it all up if necessary.
Always make sure the script has completed without error before continuing with the RUU downgrade.
Requires:
MicroSD card (2GB,4GB or 8GB recommended).
Windows PC.
HTC Sync (Installed then uninstalled for ADB drivers).
View attachment IncS_MVDTKv3.4.1.zip [highlight]Link to post, not attachment. No mirrors please.[/highlight]
RUU used for downgrade, model number PG3213000(Typical IncS)
Dropbox Mirror
Alternate RUU for Canadian Bell or South American IncS users, model number PG3212000
Dropbox Mirror
Procedure:
Extract all the files from the downgrade toolkit to your PC and run runme.cmd, following the instructions on screen. The only inputs you should be required to make are:
1. Answering y or n at the prompts
2. Rebooting your phone out of recovery (also when/if prompted)
You may receive this error during the script operation "rm failed for /data/data/recovery/log, No such file or directory" This error can be disregarded.
Then run the RUU Downgrade (takes a while, around 10 mins so be patient).
When its finished running, you can verify if you have 1.13.0000 hboot by entering hboot (power on phone + vol down).
Then you can run revolutionary to get your s-off!
Video Guide kindly provided by locn:
Use on stock ICS device
Part 1. This video goes through the process of down grading HBOOT to 1.13.0000 so that we can then use revolutionary method to gain S-OFF.
http://youtu.be/PbwE6pXOdco
Part 2. This video covers how to get S-OFF on the HTC IncS using revolutionary method.
http://youtu.be/alSEpJMJrjo
Support: (Before asking for help make sure you read and follow the instructions in both the procedure and the script)
While every possible precaution has been taken to ensure the script works on all versions of our phone under all windows environments, there is a possibility that you may get stuck on a step and require assistance. To make this process go as quickly as possible for both parties, please include the following information when requesting help:
A full output of the script, either by screenshot or copy/paste
The operating system specifics: hboot version, stock or custom(provide name) recovery or Rom and if the phone is rooted
(optional)An output of the command "fastboot getvar all" deleting imei and serial no.
Changelog:
v3.4.1 Corrected syntax causing errors for rooted users
v3.4 Added option for users on stock ICS hboot (2.02)
v3.3 Fixed main version downgrade and goldcard creation issues for some users & other minor fixes
v3.2 Repackaged and re-encoded in windows environment for compatibility issues
v3.1 Fixed issue with gold card creation on non-rooted phones
v3.0 Changed temp root method to TacoRoot changed misc_version to misc_version_universal & other minor fixes
v2.1 Changed downgrade version to help prevent user error & other minor fixes
v2.0 Added goldcard script and relock bootloader for users unlocked via htcdev
v1.1 Added option in batch file for rooted and non-rooted users
v1.0 original upload
Credits:
tpbklake: For his unsecured kernel
jcase: Author of TacoRoot
hyuh: For misc_version_universal
viperbjk from RevSkills: For the goldcard algorithm.
GenePoole: For the android goldcard binary.
Revolutionary Team: For s-off Hboot.
And to everyone who contributed. If I have missed anyone that would like to be credited on this guide, pm me and I will be happy to oblige.
Just ran through the process, worked flawlessly. S-OFF at last!
Forgot to try without creating the Goldcard so can't confirm that one.
Thanks again NonVerbose.
Just to confirm, the gold card is required.
So happy to finally have s-off. Very annoying not being able to use OTA updates.
Cheers for the confirmation st.matt. I'll edit the guide.
Can this method of downgrading to HBoot 1.13 be used after unlocking the HBoot 1.16 via HTC method?
There should be no problems using this downgrade with unlocked boot. Be aware though that when downgraded, the 1.13 may be locked... until you use revolutionary of course
Have to try this on my girlfriend's IncS. Haven't had any luck making goldcards though.. never seems to work for me
Should be able to restore her nandroid backup once it's all done though, right?
tangcla said:
Have to try this on my girlfriend's IncS. Haven't had any luck making goldcards though.. never seems to work for me
Should be able to restore her nandroid backup once it's all done though, right?
Click to expand...
Click to collapse
Yes, as soon as the s-off process is complete you can restore nandroid or any other backup with no fear of losing s-off.
Cant seem to get it working
Hey guys, I gave this a try last night with no success.
I have 2 IncS, 1 came with HBOOT 1.13, and the other 1.16. I have made a gold card in the past for my first IncS so that I could get temp root access and upgrade using an RUU without issues, but this time i ran into a few problems.
The second IncS has been unlocked via HTC dev, is rooted and has ARHD 1.19 on it (HBOOT 1.16)
Followed the guide exactly as described, but when I got to the point of running the IncS downgrader, there were a couple of errors (sorry, forgot to note them down), but by the time the process got to the end, it reported that is completed successfully?
When I ran the RUU, it said i was upgrading from 2.30.405.1 to 2.30.405.1? I was expecting to see from version 1? I got an error pretty soon saying I need to use the correct RUU to upgrade, and couldn't get any further.
So then I ran the downgrader again, but half way it got stuck in a boot loop. I left it alone, and 5 mins later, the batch file completed (without errors), but remained in the boot loop. I waited another 10, but it never left the boot loop, so I continued with the RUU upgrade. This time it told me i was upgrading from version 1 to 2.30.405.1, it got a little further (deleting user data, then sending....), but stopped again.
Removed battery, rebooted into fastboot mode. Ran the downgrader again, and it completed successfully without any issues! Ran the RUU, this time it got a little further again, it told me it was deleting user data, then sending.......
Eventually it threw another error, and remained on the black screen with the HTC logo (no progress bar, and nothing in the corners either)
I removed the battery and booted into bootloader. It went into what looks like the usual bootloader screen, only the following message was displayed:
ruu error
Security Check Failed!
At this point i thought I would have to restore the nandroid backup i made before beginning this process, but when i put the original micro SD card in and booted normally, the rom was exactly as i left it!
I did this on Windows 7, with all drivers installed (I use this notebook for android app development, so I know the SDK and drivers are complete, and my first IncS is used for debugging apps), and I used a very old 256Mb micro SD card to create the gold card.
I know it's a lot to ask, but any help would be appreciated.
Thanks for the feedback arhidi, sorry to hear that you're having problems.
arhidi said:
Removed battery, rebooted into fastboot mode. Ran the downgrader again, and it completed successfully without any issues! Ran the RUU, this time it got a little further again, it told me it was deleting user data, then sending.......
Eventually it threw another error, and remained on the black screen with the HTC logo (no progress bar, and nothing in the corners either)
I removed the battery and booted into bootloader. It went into what looks like the usual bootloader screen, only the following message was displayed:
ruu error
Security Check Failed!
At this point i thought I would have to restore the nandroid backup i made before beginning this process, but when i put the original micro SD card in and booted normally, the rom was exactly as i left it!
Click to expand...
Click to collapse
Security check failed points to a problem with the goldcard try creating it again using the steps in the guide.
Try turning fast boot mode off if you haven't already (Settings » Power » Fastboot)
Please run the downgrader while the phone is booted normally (charge mode) as the temproot could be negated between leaving fastboot and booting the rom.
I'm assuming you are using a stock rom, the RUU should be reporting that you are "upgrading" from a higher version to a lower version.
One last thing, the phone should not be rebooting through the main version downgrading process (runme.bat) if it does please run it again before continuing to the RUU downgrade step.
If you receive errors in the main version downgrade, please note them and report back.
Good luck
Edit: sorry didn't see you're rooted and running custom rom
An alternative to running the runme.bat you can just copy the misc_version to your ADB folder and enter the following commands:
Code:
adb push misc_version /data/local/tmp
adb shell
chmod 777 /data/local/tmp/misc_version
/data/local/tmp/misc_version -s 1.00.000.0
exit
Then run the RUU
Nonverbose said:
Security check failed points to a problem with the goldcard try creating it again using the steps in the guide.
Click to expand...
Click to collapse
I have a spare 2Gb micro SD, I'll try creating a gold card with that instead.
Nonverbose said:
Edit: sorry didn't see you're rooted and running custom rom
An alternative to running the runme.bat you can just copy the misc_version to your ADB folder and enter the following commands:
Code:
adb push misc_version /data/local/tmp
adb shell
chmod 777 /data/local/tmp/misc_version
/data/local/tmp/misc_version -s 1.00.000.0
exit
Then run the RUU
Click to expand...
Click to collapse
I'll try that instead, was going to look at those scripts but then ran out of time.
Thanks again.
No problem, let me know how it goes. The guide was actually written for stock ROM but it should be able to work with custom.
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again
arhidi said:
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again
Click to expand...
Click to collapse
Can you restore back to stock rom? The ruu must be checking the installed from before it updates.
If you're getting error 155 and your gold card definitely works then try going into fastboot before starting the RUU downgrade.
st.matt said:
If you're getting error 155 and your gold card definitely works then try going into fastboot before starting the RUU downgrade.
Click to expand...
Click to collapse
How do we know if the goldcard definitely works?
tangcla said:
How do we know if the goldcard definitely works?
Click to expand...
Click to collapse
As far as I know there's no software to verify the creation of the gold card. The only way to know for sure is if the card mounts properly and works with the ruu downgrade.
Ok - it's sending now... let's hope it works!
---------- Post added at 10:19 PM ---------- Previous post was at 10:11 PM ----------
tangcla said:
Ok - it's sending now... let's hope it works!
Click to expand...
Click to collapse
It worked! Yay!
Heh, congratz
tried with 2 different sd cards and cannot finish the process with the RUU
ERROR [155]
followed all the instructions and recomendations without success
i unlocked the bootloader previously, maybe is related
Related
http://alpharev.nl/x/beta/
Thought you might like to know it's now open, have fun
You're on XDA , welcome back. Great to see the public open beta is out too!
But...! It seems to be only for Hboot 1.x.x users!! If i have bootloader v 0.80.0007, i can't get s-off???
I have some trouble obviously after getting S-off, how do you root then on froyo ?
Unrevoked tells me firmware could be too new... I'll go through their FAQ perhaps some answers are there xD
S-off Process is flawless
You guys Rock !! Thanks !
great great news!
2morrow morning i will s-off my gf's wildfire!
can anyone post the step one by one? cz i dont really get. After i opened the alpharevx -> put the code-> Acquiring root (method 1) ...... unknown command
Then nothing
IT WORKEDDDDDD!!!! thanks to alphareev team
Why it not compatible with HBOOT 0.80xx ?
Dilemmaaaaaaaaaaaa...
The S/N start with HT0 or HTO???
IvanDeadWolf said:
Why it not compatible with HBOOT 0.80xx ?
Click to expand...
Click to collapse
0.80 was not the problem ,we had root or close
Anyway its worth updating your hboot with an official froyo (now)
i like the orange text and my new ability to flash a screen
thanks to alpha
Hi, how long will this public beta be?
Could use at step by step instruction?
I boot into HBOOT and run alpharevx.exe, a command prompt opens telling it's "Waiting for device"??
About a week ago I tried running Unrevoked, which ended up with the known error about hardware being to new - so I'm sure I have the correct HBOOT usb-driver.
I'm on 64-bit Windows at the moment - could it be that??
Please, anyone advice??
EDIT:
This was a question from a newbie early in the morning :d - Solved!
The utility should be run with Android loaded, not i HBOOT mode, and it helps enabling USB-debugging
After getting S-OFF I followed these instructions: http://forum.xda-developers.com/showthread.php?t=1130044
Finally I flashed: http://forum.xda-developers.com/showthread.php?t=957140
I feel pretty fine right now
Alpharev team promised at begining S-OFF for hboot 0.80.. Why they have not released it?
Some Questions to those who know.
I'm currently on HBOOT 0.80.XX having Rooted Hybrid Rom V6.
1. Do I need to update to HBOOT 1.00X to be able to use Alpharev X - if not - which option should I choose in dropdown menu on Alpharev X Beta page..? As it only shows two options - both being 1.00X
2. Do I need to Re-Root after alpharev X - or will my previous root stay (if I can use it without updating to HBOOT 1.00X)
3. Again - Do I need to Re-Flash Rom after alpharev X - or will my previous rom stay (if I can use it without updating to HBOOT 1.00X) *prays*
4. Can I use a (Fastboot) Clockworkmod that still uses Amend - rather than edify? Or is there one that can support both? As I quite dislike edify.
5. Will my old Clockworkmod be overwritten? (2.5.0.7)
I posted these questions in a few places as I haven't the faintest clue - which one is the right place to post them in...apologies for that.
morbosity said:
0.80 was not the problem ,we had root or close
Anyway its worth updating your hboot with an official froyo (now)
i like the orange text and my new ability to flash a screen
thanks to alpha
Click to expand...
Click to collapse
So you're telling me to update my phone with the last ruu, this will update my hboot as well, then i use the alpharev tool and then i root again?
0.80 still does not have S-OFF so this is a problem!
Hello,
Here is a short Guide to get S-OFF if you are at HBOOT 0.80:
1. Make a full Backup of your current ROM.
2. Download RUU Buzz Froyo HTC WWE 2.22.405.1 Radio 13.55.55.24H 3.35.20.10 release 160191 signed.exe
3. Connect your Plhone to your PC and Install it, after 10 minutes you are on HBOOT 1.01.0001
4. Download Alpharev follow the instructions and install.
Now you are S-OFF!´
You ony have to Restore your ROM and enjoy!
Sorry for my bad English.
1. not sure, but i did and it worked, i used
RUU_Buzz_Froyo_HTC_WWE_2_22_405_1_Radio_13_55_55_2 4H_3_35_20_10_release_160191_signed.exe
from
http://shipped-roms.com/index.php?ca...ile&model=Buzz
2.yes, follow this to get clockworkmod installed:
http://forum.xda-developers.com/showthread.php?p=14693680
ur phone needs to be in hboot 4 this to work
3. as far as i can tell not by defoult, but u installed ruu so yes
4. not sure, but i think there shouldnt be a broblem
5. if u run ruu, yes, hence fastboot method
i did a nand backup, installed ruu, ran alpharev, fastbot flash recovery, restoring nand backup as i type, and thats it.
another thing i was careful about is after nand backup, i switched to original sd card, so the ruu wouldnt put sense and other stuff on my primary sd. i switched back after flashing recovery. gl
Thank you!
I keep trying to enter my beta key and it says the key is invalid :S:S
Hmm I just flashed my phone with the new Hboot, ran alpharev and installed clockwork.
It worked perfectly, so maby you are somehow entering the wrong code...
Anyways It worked like a charm for me
(Windows 7 ultimate x64)
Hi, I tried to update the system on my phone and when it did a reboot after updating and installing, it is freezing on the white/logo startup screen. how can i proceed...?
Remove the battery to turn the phone off, and when turning back on, hold down the power+volume up buttons. This will put your phone in hboot mode and allow you to reflash your ROM from there.
Good luck.
Sent from my Incredible S using xda premium
thanks. Yes i did make it to that step. now i need to flash the official rom for my model which is S710e, but i found so many links that i'm confused which one is the official...can i have some indication...
thanks in advance
If you flashed a custom rom and it is stuck in white screen with logo, your boot partition is messed up. But no worries you can fix it.
Extract the boot.img file out of your custom rom (zip-file).
download the SDK files
put the boot.img in the same folder as the files
Boot phone in fast boot
connect phone through usb with a computer
open command prompt on the pc an go to folder
use command fastboot flash boot boot.img
wait 2 secs
reboot
whole proces takes maybe 10 min, very easy to do.
no i did not flash a custom rom. i just did a system update which was prompted to me on the phone itself; when i did this it got stuck on reboot. then i did a factory reset but it was in vain.
at this point what i want is to have my phone back as it was in the beginning...so I wish to know how i can flash a stock rom so that it will become like brand new. thanks.
atlam83 said:
... I wish to know how i can flash a stock rom so that it will become like brand new. thanks.
Click to expand...
Click to collapse
First, you have to know what your mainver is:
Boot into fastboot, open a cmd window in windows and type this:
Code:
fastboot getvar mainver
This will give you your mainver (e.g. 2.12.708.4)
And go here: http://www.filefactory.com/f/e45d6fe3dcf51228/
You'll find shipped rom list. The filenames are in format like this: RUU_[name][mainver][radio_version]_signed.exe You must select ones with WWE prefixes (for multi-language support) and higher mainvers than yours! For example, if your mainver is 2.12.708.4, then you can select RUU_Vivo_Gingerbread_S_Sasktel_Canada_WWE_2.33.669.2_Radio_20.2810.30.085AU_3805.06.03.16_M_release_203211_signed (this one's mainver is 2.33.669.2) in the shipped rom list.
Once you've downloaded, you'll face another problem: Flashing.
Flashing is not a real problem but needs some trickies.
The question: Have you rooted your phone?
If yes, this thread is your flashlight to enlighten your way..
If no, you have to obtain a goldcard. A goldcard is a special microSD which prevents the phone to check cid (Customer ID) while trying to flash an original rom. If you haven't created a goldcard yet and cannot boot your phone properly, find another Android based phone and insert your microSD card into it. Then read this thread to create your gold card. Once you've created your goldcard, then it's so easy for you to flash your original rom. Follow the steps in the link above (explaining how to flash).
hth.
-R
i downloaded and flashed a stock rom on my phone by placing the PG32IMG.zip file in my sd card . the update was completed successfully however the phone still got stuck in the htc startup screen. any ideas what the problem might be?
I haven't tried the goldcard yet however.
atlam83 said:
i downloaded and flashed a stock rom on my phone by placing the PG32IMG.zip file in my sd card . the update was completed successfully however the phone still got stuck in the htc startup screen. any ideas what the problem might be?
I haven't tried the goldcard yet however.
Click to expand...
Click to collapse
Did you previously use Revolutionary to gain S-Off on your phone. If so by trying to install the OTA update, you now have a HBOOT ROM mismatch. The OTA update requires that the HTC HBOOT 2.00.0000 be installed, but the Revolutionary S-Off HBOOT prevented the OTA from overwriting the hboot, thus creating the situation you are in.
Follow steps 1 - 2c on this thread.
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
The find the OTA file on your SD card and extract the file firmware.zip.
Copy this to the root of your SD card and rename it PG32IMG.zip and then reboot into bootloader and it should reflash the correct HBOOT and you should be good to go.
Thanks very much tpbklake, I managed to solve my issue following the thread you indicated. its been 3 weeks since last i used my mobile. Send it to various ppl including HTC (which did not want to fix my mobile) and no one fixed it. have tried that thread and now its fine working again )
HTC freezing on thie logo startup screen
Hi
Im new here I had read the all similar threads that the forum found but no one could help me to solve my problem.
Im using Android 2.3.3 and
Sense 2.1,
HBOOT : 6.13.1002
My baseband version is 3822.10.08.28_M
I recived an OTA update with Android 2.3.5 and Sense 3.0 and I proceeded with it, everything goes well until the phone restarts and stay freeze in the green HTC logo. Nothing else happens.
plz give me a link for the official ROM for Incredible S 710e.I tried the links but it didnt work for me...
hope someone could help me.. :'(
Aniok said:
Hi
Im new here I had read the all similar threads that the forum found but no one could help me to solve my problem.
Im using Android 2.3.3 and
Sense 2.1,
HBOOT : 6.13.1002
My baseband version is 3822.10.08.28_M
I recived an OTA update with Android 2.3.5 and Sense 3.0 and I proceeded with it, everything goes well until the phone restarts and stay freeze in the green HTC logo. Nothing else happens.
plz give me a link for the official ROM for Incredible S 710e.I tried the links but it didnt work for me...
hope someone could help me.. :'(
Click to expand...
Click to collapse
All you need to do is go to the Development section and upgrade from Revolutionary HBOOT 6.13.1002 to BlackRose 2.02.0002. That will allow your phone to boot.
http://forum.xda-developers.com/showthread.php?t=1509236
Thanx
..
Sent from my GT-I9300 using xda premium
Hi,
To start off with, I have no prior experience with rooting or the likes. Yesterday I decided to root my phone in order to use programs requiring SU access, which went fine. Along the way I decided that I'd also like to install a new ROM, and thus embarked on the journey from HBOOT2.02.0002 S-ON to S-OFF.
I've been following this guide to downgrade my phone in order to S-OFF it. After everything going smoothly apart from slow downloads, I am now attempting to downgrade using the following RUU provided in the thread:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe
Unfortunately for me, the installer stops with ERROR155. I have tried Googling around and have found that the RUU should be matched with the CID (HTC_Y13) of my phone, though I have come up short when trying to find an actual match and a link. So my question is, which RUU should I use to downgrade and where can I find it?
My phone is bought in Denmark if that's of importance.
Thank you so much in advance - this board has already been an amazing ressource to me!
Splintre said:
Hi,
To start off with, I have no prior experience with rooting or the likes. Yesterday I decided to root my phone in order to use programs requiring SU access, which went fine. Along the way I decided that I'd also like to install a new ROM, and thus embarked on the journey from HBOOT2.02.0002 S-ON to S-OFF.
I've been following this guide to downgrade my phone in order to S-OFF it. After everything going smoothly apart from slow downloads, I am now attempting to downgrade using the following RUU provided in the thread:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe
Unfortunately for me, the installer stops with ERROR155. I have tried Googling around and have found that the RUU should be matched with the CID (HTC_Y13) of my phone, though I have come up short when trying to find an actual match and a link. So my question is, which RUU should I use to downgrade and where can I find it?
My phone is bought in Denmark if that's of importance.
Thank you so much in advance - this board has already been an amazing ressource to me!
Click to expand...
Click to collapse
That RUU will work for you if you answered YES to create a goldcard.
The error 155 means that the bootloader did not get RELOCKED by the script. You should post the results of your command window when you ran the script so that we can assist you better.
tpbklake said:
That RUU will work for you if you answered YES to create a goldcard.
The error 155 means that the bootloader did not get RELOCKED by the script. You should post the results of your command window when you ran the script so that we can assist you better.
Click to expand...
Click to collapse
Thank you very much for the fast reply!
Having read on a bit, I have discovered Nonverbose's Downgrade kit which I have not been running before. I'm guessing that the creation of goldcard happens through running that script?
As I am having a bit fun with the tinkering, I've tried to do things as step-by-step as possible to understand the process. What does a goldcard do exactly, and why does it help the RUU run? Does it restore my CID to a manufacturer default or something?
Splintre said:
Thank you very much for the fast reply!
Having read on a bit, I have discovered Nonverbose's Downgrade kit which I have not been running before. I'm guessing that the creation of goldcard happens through running that script?
As I am having a bit fun with the tinkering, I've tried to do things as step-by-step as possible to understand the process. What does a goldcard do exactly, and why does it help the RUU run? Does it restore my CID to a manufacturer default or something?
Click to expand...
Click to collapse
The goldcard allows the bootloader to bypass the CID check when flashing the RUU. Therefore you can flash a RUU from a different region or carrier. It does not alter your CID in any way.
tpbklake said:
You should post the results of your command window when you ran the script so that we can assist you better.
Click to expand...
Click to collapse
Having now been through the Downgrade Kit, here is the resulting CMD prompt:
imgur. com/dIKhd (sorry for breaking up the link, I am not allowed to post outside links yet)
It doesn't look right, does it? What am I doing wrong?
Splintre said:
Having now been through the Downgrade Kit, here is the resulting CMD prompt:
imgur. com/dIKhd (sorry for breaking up the link, I am not allowed to post outside links yet)
It doesn't look right, does it? What am I doing wrong?
Click to expand...
Click to collapse
The error 'more than one device or emulator' is definitely not good. Also you took a screen shot instead of cutting and pasting the contents of the command window, so you did not capture or show the whole script execution.
Make sure you don't have the HTC Sync application running in the system tray or in the background. That would definitely interfer with the script.
tpbklake said:
The error 'more than one device or emulator' is definitely not good. Also you took a screen shot instead of cutting and pasting the contents of the command window, so you did not capture or show the whole script execution.
Make sure you don't have the HTC Sync application running in the system tray or in the background. That would definitely interfer with the script.
Click to expand...
Click to collapse
Ok - I tried running it again. I don't have the HTC Sync application installed just the drivers as suggested here.
Code:
Incredible S Main version downgrade toolkit v3.4.1 by Nonverbose
This script will:
------------------------------------------------------------------
(1) Boot using an unsecured kernel**
(2) Apply a temp root using the tacoroot exploit**
(3) Downgrade your phones version-main using misc_version
(4) Turn your phones SDcard into a Goldcard**
**(if required)
------------------------------------------------------------------
Before u begin:
------------------------------------------------------------------
(1) If you are on Official HTC ICS update you MUST have an
UNLOCKED bootloader to use this script.
(2) backup everything you don't want to lose
(phone storage and SDcard)
(3) make sure u have installed adb drivers for ur device
(4) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(5) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(6) connect USB cable to PHONE and then connect to PC
------------------------------------------------------------------
Tryk på en vilkårlig tast for at fortsætte . . .
Waiting for device to connect
* daemon not running. starting it now *
* daemon started successfully *
error: more than one device and emulator
Device found
Are you running Official HTC ICS on an UNLOCKED bootloader?
y OR n:y
Waiting for device to connect
error: more than one device and emulator
Device found
error: more than one device and emulator
rebooting to fastboot mode
< waiting for device >
It just waits now. Any ideas? Thanks a lot again for your replies.
You phone needs to be booted normally when you start the script. You cannot start the script if your phone is booted to the HBOOT menu.
Hello everyone,
This is my first post so I hope I don't end up being a "typical noob".
I'll try give the full info but keep it concise.
Background:
1) Carrier Unlocked HTC One M7 Originally on Rogers.
M7_UL PVT SHIP S-On RH
HBoot-1.44.000
Radio - 4A.14.3250.13
Open DSP 26.120.274.0202
emmc-boot
2) The phone was working perfectly after being hard reset, and configured without a sim.
3) After it was activated by the telco, the keyboard would would no longer work. Dialpad fine... menus fine... but no keyboard would pop up when selecting text fields. Did a full factory reset, and also tried clearing the Sense Touch data cache via Settings->App.
4) After trying various possible solutions I found online, I finally decided to try start from scratch by installing stock firmware.
WARNING: i'm the second owner of the phone. For warranty I would have had to send the phone to HTC. I suspect the HTC warranty won't apply to me anyhow. I suggest that in this situation, people just get the phone fixed on warranty if they have that option
First Steps:
A1) I unlocked the bootloader via HTCDev and used adb to flash CWM Touch Recovery.
A2) Restored the "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)"
A3) Phone now works correctly at this stage, but is still bootloader unlocked/tampered + CWM Touch Recovery
A4) While I may eventually flash the phone to an official Developer Edition
I would like to reinstall a factory recovery.img, then use revone to get rid of the bootloader "tampered" flag and relock it. (for OTA Updates, and the usual warranty concerns)
A5) I tried flashing both the boot.img and recovery.img from "OTA_M7_UL_JB_50_Rogers_WWE_1.29.631.17_R-1.29.631.4_release_318662" to get back to stock recovery, but I got a Red triangle.
Questions:
Q1): Does anyone know of a stock recovery.img I can use with Rogers firmware ? (SEE UPDATE BELOW)
Q2): Is there some trick to getting the OTA recovery/boot images I tried....working ? Is there some cache reset of somthing that needs to be done after flashing the stock recovery/boot imgs ? (SEE UPDATE BELOW)
Thanks in advance !
same issue
I too am looking for a rogers ruu or even the M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus) since bugsys page is down.
bump
LRail said:
Hello everyone,
This is my first post so I hope I don't end up being a "typical noob".
I'll try give the full info but keep it concise.
Background:
1) Carrier Unlocked HTC One M7 Originally on Rogers.
M7_UL PVT SHIP S-On RH
HBoot-1.44.000
Radio - 4A.14.3250.13
Open DSP 26.120.274.0202
emmc-boot
2) The phone was working perfectly after being hard reset, and configured without a sim.
3) After it was activated by the telco, the keyboard would would no longer work. Dialpad fine... menus fine... but no keyboard would pop up when selecting text fields. Did a full factory reset, and also tried clearing the Sense Touch data cache via Settings->App.
4) After trying various possible solutions I found online, I finally decided to try start from scratch by installing stock firmware.
So far:
A1) I unlocked the bootloader via HTCDev and used adb to flash CWM Touch Recovery.
A2) Restored the "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)"
A3) Phone now works correctly at this stage, but is still bootloader unlocked/tampered + CWM Touch Recovery
A4) While I may eventually flash the phone to an official Developer Edition
I would like to reinstall a factory recovery.img, then use revone to get rid of the bootloader "tampered" flag and relock it. (for OTA Updates, and the usual warranty concerns)
A5) I tried flashing both the boot.img and recovery.img from "OTA_M7_UL_JB_50_Rogers_WWE_1.29.631.17_R-1.29.631.4_release_318662" to get back to stock recovery, but I got a Red triangle.
Questions:
Q1): Does anyone know of a stock recovery.img I can use with Rogers firmware ?
Q2): Is there some trick to getting the OTA recovery/boot images I tried....working ? Is there some cache reset of somthing that needs to be done after flashing the stock recovery/boot imgs ?
Q3) If I eventually decide to install the Developer Edition firmware.. will the phone be effectively be a Dev phone ? (OTA updates... factory recovery/locked bootloader... no ID issues in the future..)
Thanks in advance !
P.S. For pure curiousity.... Am I correct in believing that revone can't clear the "tamper" flag and lock the bootloader with the custom recovery ?
Click to expand...
Click to collapse
double post
omgkush said:
I too am looking for a rogers ruu or even the M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus) since bugsys page is down.
bump
Click to expand...
Click to collapse
A lot of the RUUs and nandroid files were apparently "saved" to "Crushalot's" site: htc1guru.com
you can also get the file links in this thread: http://forum.xda-developers.com/showthread.php?t=2428276
I used that nandroid backup. I don't think a Rogers RUU exists (yet).
UPDATE ON MY PROGRESS:
1) I had success with using revone to get my M7 S-Off and removed the tampered flag in the bootloader.
I suspected that SuperSU wasn't working right becaue i hadn't been getting a root permission popup window on the phone.
On I reinstalled SuperSU, I got the root rights popup window when running revone, and it then worked.
2) I have realized that the firmware.zip, which is contained in the OTA update, contains the factory recovery and boot image I needed.
(I kept thinking that it was an incremental update and not a complete image or something, due to it's size.)
Therefore, instead of flashing the images individually, I used the firmware.zip from the OTA update to do a complete firmware update.
3) The Red triangle I was getting was, normal. I couldn't find clear info, so I assumed it was a bad sign because the only time i had seen the factory recovery was when it was upating with a red circle/arrow. So.. I thought the red circle/arrow was the icon you wanted to see.
Eventually I found a thread for a different HTC Phone, that also works for the M7
Result: You can use the volume up + power buttons to enter the recovery once the red triangle appears.
4) After installing the firmware (extracted from the OTA update), I used revone to set the phone back to S-ON, then locked it.
5) The OTA update then automatically installed, as a stock phone would.
6) After the OTA update, for some reason the tampered flag is back. I'll be using revone today to fix that.
UPDATE 2
:
6) After the OTA update, for some reason the tampered flag was back. I unlocked the phone, used revone to to get S-OFF, then used revone to reset the tamper flag and relock the bootloader, and then "fastboot oem writesecureflag 3" to set S-ON.
After 2 reboots the Tampered flag was back !
I'm suspecting that for the tampered flag to stay off I need to keep it S-OFF, which defeats the whole idea of trying to return it to stock.
Any ideas ?
Anyone working for Rogers want to leak an RUU ? hehe
Did you use CWM to flash the firmware.zip in step 2? I'm trying to follow your steps to get back to stock to obtain my stock rogers update but i'm getting lost as to what you're using to flash, recovery or fastboot.
LRail said:
A lot of the RUUs and nandroid files were apparently "saved" to "Crushalot's" site: htc1guru.com
you can also get the file links in this thread: http://forum.xda-developers.com/showthread.php?t=2428276
I used that nandroid backup. I don't think a Rogers RUU exists (yet).
UPDATE ON MY PROGRESS:
1) I had success with using revone to get my M7 S-Off and removed the tampered flag in the bootloader.
I suspected that SuperSU wasn't working right becaue i hadn't been getting a root permission popup window on the phone.
On I reinstalled SuperSU, I got the root rights popup window when running revone, and it then worked.
2) I have realized that the firmware.zip, which is contained in the OTA update, contains the factory recovery and boot image I needed.
(I kept thinking that it was an incremental update and not a complete image or something, due to it's size.)
Therefore, instead of flashing the images individually, I used the firmware.zip from the OTA update to do a complete firmware update.
3) The Red triangle I was getting was, normal. I couldn't find clear info, so I assumed it was a bad sign because the only time i had seen the factory recovery was when it was upating with a red circle/arrow. So.. I thought the red circle/arrow was the icon you wanted to see.
Eventually I found a thread for a different HTC Phone, that also works for the M7
Result: You can use the volume up + power buttons to enter the recovery once the red triangle appears.
4) After installing the firmware (extracted from the OTA update), I used revone to set the phone back to S-ON, then locked it.
5) The OTA update then automatically installed, as a stock phone would.
6) After the OTA update, for some reason the tampered flag is back. I'll be using revone today to fix that.
UPDATE 2
:
6) After the OTA update, for some reason the tampered flag was back. I unlocked the phone, used revone to to get S-OFF, then used revone to reset the tamper flag and relock the bootloader, and then "fastboot oem writesecureflag 3" to set S-ON.
After 2 reboots the Tampered flag was back !
I'm suspecting that for the tampered flag to stay off I need to keep it S-OFF, which defeats the whole idea of trying to return it to stock.
Any ideas ?
Anyone working for Rogers want to leak an RUU ? hehe
Click to expand...
Click to collapse
Tampered will come back the second you flash a recovery. Best to stay S-OFF
I've been in a similar situation where I had to send my phone in for repair and couldn't get the tamper flag to stay off.
I found out it was because I was trying to remove the flag and lock the bootloader and S-On on 1.29.631.17
What I had to do was restore using CWM back to 631.4 then flash stock recovery then remove flag, lock bootloader, then S-On.
The tamper flag should stay off you can try rebooting a couple of times then boot into bootloader to check.
Then I ran the OTA updates and i'm on 631.17 at the moment and my tamper flag is still off.
Hope this helps.
PS. I believe the latest JB4.3 OTA update upgrades the hboot to 1.55 so revone would not work on it. Not planning to try it myself but if anyone can verify this would be great
ysl00 said:
I've been in a similar situation where I had to send my phone in for repair and couldn't get the tamper flag to stay off.
I found out it was because I was trying to remove the flag and lock the bootloader and S-On on 1.29.631.17
What I had to do was restore using CWM back to 631.4 then flash stock recovery then remove flag, lock bootloader, then S-On.
The tamper flag should stay off you can try rebooting a couple of times then boot into bootloader to check.
Then I ran the OTA updates and i'm on 631.17 at the moment and my tamper flag is still off.
Hope this helps.
PS. I believe the latest JB4.3 OTA update upgrades the hboot to 1.55 so revone would not work on it. Not planning to try it myself but if anyone can verify this would be great
Click to expand...
Click to collapse
Thanks for the heads up. If I get a bunch of free time I may just test that after doing a new full backup.
Not sure about the Rogers 4.3 OTA.
I'm running currently the phone with Developer Edition ROM+CID and can confirm that it's 4.3 OTA updates hboot to 1.55.
After the update my phone is still s-off.
I have previously rolled back to an older hboot via a firmware flash.
Since the phone is still S-OFF, I assume I can do that again if needed.
EddyOS said:
Tampered will come back the second you flash a recovery. Best to stay S-OFF
Click to expand...
Click to collapse
Thanks For the reply Eddy.
Recovery flashing sets the tampered flag even if it's a factory recovery from an OTA being flashed ?
I agree on the S-OFF normally.
This was a test to see if I could get it back to full stock for warranty if needed, and S-OFF would not be acceptable in that case.
please help!
PLEASE! I have been trying to get Rogers stock Canada back on my HTC since the day after release lol..
I have this nandroid backup but can't figure out how to flash it... I also can't relock to try and flash a legit version
So pleaseeee how do I install this!!! I am using cwm I tried making a folder called backups in clockworkmod dir but it doesn't pickup the nandroid backup... Help plz!!!!
So what do I do with the M7 CWM Nandroid Backup CID ROGER001 1.29.631.17 2013-06-03.zip
I can't flash it and it won't recognise it as a backup, how do I even install it?
Nobody has mentioned how to use this zip, it isn't a tar file or flashable so what do I do with it?
millarrjm said:
PLEASE! I have been trying to get Rogers stock Canada back on my HTC since the day after release lol..
I have this nandroid backup but can't figure out how to flash it... I also can't relock to try and flash a legit version
So pleaseeee how do I install this!!! I am using cwm I tried making a folder called backups in clockworkmod dir but it doesn't pickup the nandroid backup... Help plz!!!!
Click to expand...
Click to collapse
Esposition said:
So what do I do with the M7 CWM Nandroid Backup CID ROGER001 1.29.631.17 2013-06-03.zip
I can't flash it and it won't recognise it as a backup, how do I even install it?
Nobody has mentioned how to use this zip, it isn't a tar file or flashable so what do I do with it?
Click to expand...
Click to collapse
Simply doing a web search for info would have given you the answers on many many webpages and some youtube videos.
http://bit.ly/1a6d88A
http://bit.ly/1a6ewZ5
Quick answer:
1) Nandroid backups are created and used by the custom recovery "clockworkmod"
2)You need to install a CWM custom recovery (i like the touch version), then unzip the nandroid backup file to the /clockworkmod/backup/ folder. It will create a new folder there. I used the program "Android File Transfer" to copy the files from my laptop to the phone.
3) Once the backup file is on your phone, to restore the backup, you simply boot into recovery and restore the backup as explained in those web pages or youtube videos.
If you have specific things you have tried.... folder names... etc. then ask a question in detail.
You will then have a much higher chance of getting a correct answer (or even an answer at all)
Hope that helps a bit...
Cheers
PS:
millarrjm
FWIW: Simply asking general questions with "pleaseee" and a bunch of exclamation points is a quick way to be ignored (especially in this forum meant for people with some technical skill) See this video (which you should have seen on signup to the forum) for info: http://www.youtube.com/watch?v=JmvCpR45LKA
re.
LRail said:
Simply doing a web search for info would have given you the answers on many many webpages and some youtube videos.
http://bit.ly/1a6d88A
http://bit.ly/1a6ewZ5
Quick answer:
1) Nandroid backups are created and used by the custom recovery "clockworkmod"
2)You need to install a CWM custom recovery (i like the touch version), then unzip the nandroid backup file to the /clockworkmod/backup/ folder. It will create a new folder there. I used the program "Android File Transfer" to copy the files from my laptop to the phone.
3) Once the backup file is on your phone, to restore the backup, you simply boot into recovery and restore the backup as explained in those web pages or youtube videos.
If you have specific things you have tried.... folder names... etc. then ask a question in detail.
You will then have a much higher chance of getting a correct answer (or even an answer at all)
Hope that helps a bit...
Cheers
PS:
millarrjm
FWIW: Simply asking general questions with "pleaseee" and a bunch of exclamation points is a quick way to be ignored (especially in this forum meant for people with some technical skill) See this video (which you should have seen on signup to the forum) for info: http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
I tried that. CWM version 6.+ doesn't save to the backup folder anymore. And won't read a restore I put in it either... Ie. The rogers off the bugzylawson site.
bklam said:
Did you use CWM to flash the firmware.zip in step 2? I'm trying to follow your steps to get back to stock to obtain my stock rogers update but i'm getting lost as to what you're using to flash, recovery or fastboot.
Click to expand...
Click to collapse
Hello bklam,
Sorry, I missed your question.
No. I used CWM only to restore the "Whampahoofus"' nandroid backup.
That backup is "almost" 100% stock. Unfortunately it contains a custom recovery and won't (in my experience) work for normal OTA updates.
To solve this I decided to extract the factory firmware from one of the old Rogers OTA ("unrar" will extact the files from the OTA), and flash that.
To flash it I used the quick instructions in the 1st post of this thread-->http://forum.xda-developers.com/showthread.php?t=2182823
(I believe there were more details instructions on firmware.zip flashing in another thread but I can't find it at the moment)
Note to other readers: There can be confusion about the word "firmware". Some people use it describe the Rom.
In this case, I'm referring to the hboot, boot and recovery images in a single special file called firmware.zip. I believe in some cases it can also include the radio software too.
If I ever get a chance to get this 100% tested and figured out, I'll post a step by step method.
At this point it's just a overview of what I tried, and looking for other members advice.
Unfortunately, as you can see from my posts, it didn't work 100% for me. It gave me the stock Rogers HTC One Rom/software with OTA updates, but the bootloader still had the tampered flag.
Check out ysl00's post above. He/She evidently had it working 100% without the tamper flag.
Not sure if Rogers has a 4.3 OTA yet, but that might fix the flag since it includes a firmware update along with the OS update.
Post back with your results !
Did you see my above reply lrail? .. just saw u post after thought you might have missed ot!! Thanks so much fpr the help and replies. You are the man!
figured it out.
I thoight the explorer I was using showed all files on phone. TO FIX this issue download root explorer and you can see the other directories... Goto data>media>clockworkmod>backups .. it isnt in the sd dir on your phone.
millarrjm said:
Did you see my above reply lrail? .. just saw u post after thought you might have missed ot!! Thanks so much fpr the help and replies. You are the man!
Click to expand...
Click to collapse
Sorry about that. No I didn't see it until just now. I guess thats the problem with having 20 browser tabs open at once. hehe
millarrjm said:
I thoight the explorer I was using showed all files on phone. TO FIX this issue download root explorer and you can see the other directories... Goto data>media>clockworkmod>backups .. it isnt in the sd dir on your phone.
Click to expand...
Click to collapse
Good to hear. I read your post. I thought..."Is he using a root file manager ?" then read your next post….
I was also going to suggest a guaranteed way to determine where the CWM backups are being stored on a phone.
This way it doesn't matter which version of CWM, which phone or if the back directory exists yet.
Simply create a test backup and see where it goes. Then copy the Nandroid backup that you want to restore, there.
I should mention that I'm currently running my phone as a Developer Edition (Brightstar) 4.3 with OTAs, S-OFF, and unlocked.
It's works perfectly. Only the Carrier ID (CID) needed to be changed. The MID is the same.
I assume that a brightstar RUU will work on it now, even if the phone was locked and S-ON.
I have a few more things I want to tweak on it, then I'll likely make a backup and try restore it to stock rogers again so that I can create a clear how-to.
What's interesting, is that the Developer Edition OS seems to be the same as the Rogers Edition OS (without the rogers apps which can be uninstalled).
The only reason I think it might be a better choice is that the Dev Edition should get OTA updates earlier than the Rogers Edition.
I tried the custom Viper Rom 2.6.x but couldn't get an LTE connection. I suspect that was due to APN settings, but I didn't confirm that.
Anyone got the Viper Rom fully working on a Roger HTC M7 ?
Alright so I've successfully re-installed that nandroid backup and enabled s-off, re-locked, and removed the tampered notification.
When I try to do the OTA update it just hangs at the bug fix1. It default opens and tries to install it through cwm recovery, I've never done any OTA updates before so I assume this is normal?
How can I fix it hanging at bug fix1?
Esposition said:
Alright so I've successfully re-installed that nandroid backup and enabled s-off, re-locked, and removed the tampered notification.
When I try to do the OTA update it just hangs at the bug fix1. It default opens and tries to install it through cwm recovery, I've never done any OTA updates before so I assume this is normal?
How can I fix it hanging at bug fix1?
Click to expand...
Click to collapse
The OTAs don't work with custom recovery. You need the factory recovery
Please read and understand the guide and accompanying links in their entirety before beginning.XDA and I am not responsible for anything you do to your phone.
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
While trying to run an RUU to reset my phone, I kept running into an issue: "htc_fastboot.exe has stopped working". I could get my phone to restart, but the RUU would not run successfully. I searched this site and the internet for an answer, but could not find anything that worked for me. Also, a lot of people in Q&A tend to have issues getting the RUU to work. That's why I'm writing this guide. Hopefully someone who is having trouble will search and stumble across it. I tried everything I could find - Windows 7, 8.1, different RUUs, etc and this is how I finally fixed it. I am s-off by the way and did this in Windows 8.1 Update so the guide is written from that perspective.
Steps:
1. Make sure that your computer can see your phone when you boot into fastboot. It should say Fastboot in red that changes to Fastboot USB when plugged into your computer. There are guides that help with this, so I'm not going to go into much detail. Basically you install HTC Sync to your computer and then uninstall it but leave the drivers.
2. Get a copy of fastboot and ADB. The easiest way is to get the SDK from Google (tools only) as it also includes drivers, but you can get just fastboot and adb from here (I did not use this tool personally).
3. To verify that your phone and computer are talking, open a command prompt window (I always open as administrator) and go to the folder that contains fastboot. Type "fastboot devices" (no quotes) and it should list your phone. If it does not, something did not work right with steps 1 and 2.
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes).
5. Download the Full Firmware from RUU here. While you're there, get the RUU as well. Make sure to get the one that is not decrypted (first link). Copy both into the folder with fastboot.
6. Flash the firmware file using fastboot following the directions in the OP from where you got it. To summarize, rename the firmware zip file to firmware.zip. Then at a command prompt, type "fastboot oem rebootRUU". When the phone shows a black screen that says HTC, type "fastboot flash zip firmware.zip". The command prompt window will show a bunch of stuff as it does its thing. When you get back to the command prompt, it's finished. At this point, type "fastboot reboot-bootloader" to restart back into the (hopefully now stock) bootloader. Personally, I had to repeat the last command again because it failed the first time.
7. At this point, you should be in the stock hboot. It should say fastboot USB in red. Now time to RUU.
8. The current RUU is an exe so run the RUU you download before (if you have a zip file, unzip the RUU and run ARUWizard.exe). I personally ran it as an administrator just to make sure limited privileges didn't cause an issue. Read each screen and keep clicking next. Eventually it will do its thing. It takes about ten minutes and sometimes seems to be frozen. Have patience grasshopper.
And that's it. I'm now running pure stock (not for long I'm sure), still s-off. If you are s-on, you will have to unlock your bootloader again.
Good luck!
I'll be the first to troll post in this guide
Nice work brother.
I've noticed the newer RUU's (M7 and M8) require you to have the matching hboot to run correctly even if your device is s-off.
I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!
kushanson said:
I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!
Click to expand...
Click to collapse
You're welcome. Glad it helped. Also, thank you for the heads up about the RUU being an exe now. It was a zip file when I wrote the guide. I've fixed the guide to reflect the change.
Dude...
I was soft bricked for about an hour until I found this. It seems fairly obvious to me now, but for some reason I had thought that only flashing the full_firmware zip in fastboot would suffice. I guess the tiny file size (80MB unzipped???) should have tipped me off.
Regardless, I'm back up and running. Thanks, coal.
i am getting error bootloader signature failed how to fix please
rajnshubham said:
i am getting error bootloader signature failed how to fix please
Click to expand...
Click to collapse
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.
coal686 said:
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
Good luck!
Click to expand...
Click to collapse
Thanks for your guided I was able to fix an old One that I had laying around, thanks again
coal686 said:
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.
Click to expand...
Click to collapse
i think the problem was due to same hboot error. i get to know this thing few days back. anyway thanks coal686. now i updated with the ruu having hboot 1.56 and now i m on kitkat 4.4.2 stock. i can update now to higher ones. thanks buddy
I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app
biker57 said:
I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for using my guide!
The first step is to flash the "full firmware from RUU" (it's actually labelled that way in the OP of the linked post). It's only the firmware, not the full RUU. Then, follow that up with the .exe file which is the entire RUU. For some reason, the RUU wouldn't run for me without flashing the firmware first.
Since you are already on hboot 1.6, you probably don't have to flash the firmware first, but I'd do it just to be safe.
I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app
biker57 said:
I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Just run it. Fastboot flash the firmware then just run the RUU exe.
Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.
cowboysgz said:
Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.
Click to expand...
Click to collapse
.
Thanks
Device not recognized
Whenever I plug in my device and go to fastboot, my computer tells me "USB Device not recognized". I've installed the drivers from HTC, I even went to Decide manager on my PC to see if the device appears at all. It shows on the top under "Android USB Device" and it's labeled "My HTC" but it has the error symbol on it, so o deviced to unistall the driver and install it manually. It said that I already had the correct driver.
The reason I'm trying to do all this is, back in 2013 I had put Viper ROM on my device, it worked great, I also installed cyanogen mod as well and that worked great, at the time I wanted to have the double tap to wake feature, so I installed a custom Kernel to allow that. When I had booted up my phone the HTC logo didn t go away, then the lock screen showed up, I unlocked my phone, the HTC logo was still there, then my home screen finally opened and some apps wouldn't open. Then it would restart, so I rebooted it and it would do the same thing, turn on, show the HTC, start then restart. I could go into recovery fine, Install updated version of rom, and the same problem persists
Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich
krakora said:
Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich
Click to expand...
Click to collapse
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469
coal686 said:
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469
Click to expand...
Click to collapse
Thanks so much Coal, that absolutely worked. The RUU exe runs for me, but getting 155 unknown error. Evidently its not the right RUU for my device. My bootloader is "relocked" already, S-on. So confusing. When I was following the directions on the guide, when flashing the firmware, I was getting the 12 missing signatures error also, I'm assuming its not reading it as an HTC signed firmware. Any ideas on my next direction? Best, Rich