Related
Hey how are guys, i'm having some problem with my evo3d, I installed a kernel via Flash Image GUI after that my phone doesn't boot anymore. I made a backup before doing this and even restoring the backup keep doing the same. The screen stay on white with HTC letter.
erasmo0284 said:
Hey how are guys, i'm having some problem with my evo3d, I installed a kernel via Flash Image GUI after that my phone doesn't boot anymore. I made a backup before doing this and even restoring the backup keep doing the same. The screen stay on white with HTC letter.
Click to expand...
Click to collapse
What rom kernel combo are you using ?
Sent from my PG86100 using xda premium
reaper24 said:
What rom kernel combo are you using ?
Click to expand...
Click to collapse
-MikRunny-3vo-v1.1-CDMA-signed (After installing this one, start the problem)
-Radiance-RC-4 (I Install this one successful but it made a boot loop)
-MIUI.us_shooter_2.2.23_Eng_Deo_ZipA_Signed_scott951 (I Install this one successful but it made a boot loop)
-ICS-AOSP (error)
Shooter_2.08.651.2_odexed_rooted-signed (This one worked perfect but after MikRunny-3vo-v1.1 non of stock .Img works)
I take it your Hboot 1.5 since your using the Flash Gui.. I don't use that app..
Your suppose to flash the rom first then use that app to flash the kernel you want wipe the cache and davlik cache and it will flash the kernel and reboot for you.. Suppose to work that way... I think the kernel you may be tryin to use might be the issue..
Best way to flash is to...
Be in Hboot use adb:
Fastboot boot recovery.img wipe and flash the rom... You will have zero issues this route man..
Also I am on the 2.17 build and radios and what not haven't had any issues with things...
The problem your having is related to the kernel not flashin or rather the boot.img is messing up..
reaper24 said:
Be in Hboot use adb:
Fastboot boot recovery.img wipe and flash the rom... You will have zero issues this route man..
Also I am on the 2.17 build and radios and what not haven't had any issues with things...
The problem your having is related to the kernel not flashin or rather the boot.img is messing up..
Click to expand...
Click to collapse
Yes, I think so too, Im very new on this, that's the reason i having a bad time what is adb? is there any tutorial here about that?
Because before this happened to me I read that the first step when installing a Rom is installing the kernel. so I did that and then this happen to me.
So ill appreciate if you tell me what is adb... and thank you for ur quick respond
Ohhh im sorry, but I did abd and it does the same.
erasmo0284 said:
Yes, I think so too, Im very new on this, that's the reason i having a bad time what is adb? is there any tutorial here about that?
Because before this happened to me I read that the first step when installing a Rom is installing the kernel. so I did that and then this happen to me.
So ill appreciate if you tell me what is adb... and thank you for ur quick respond
Click to expand...
Click to collapse
How did you root ? Are you Hboot 1.5 you can check in your hboot? From the sounds of it you are. Did you root using HTC DEV...
To root that method you have to have java jdk and SDK along with htc sync installed.
Download java jdk and also SDK and HTC SYNC 3.0...
reaper24 said:
How did you root ? Are you Hboot 1.5?
Download java jdk and also SDK...
Click to expand...
Click to collapse
Yes I have Hboot 1.5 S-On
And SDK too
erasmo0284 said:
Yes I have Hboot 1.5 S-On
And SDK too
Click to expand...
Click to collapse
What is your OS on your computer? Go to your SDK folder open it click on android look for platform tools folder.. Hold shift down right click on it and say open cmd window... Now while in hboot and phone plugged in make sure you put your recovery.img you are using in the platform tools folder where adb is... Now type : fastboot boot recovery.img this will take you into recovery wipe everything not your SD card... Now flash the rom you want.. You should be set man...
My OS is Windows 7, and now im inside platform tools and I see abd and fast boot, but I dont understand when you say press shift and make right click, do you want me to make right click on abd or fastboot? thank you
erasmo0284 said:
My OS is Windows 7, and now im inside platform tools and I see abd and fast boot, but I dont understand when you say press shift and make right click, do you want me to make right click on abd or fastboot? thank you
Click to expand...
Click to collapse
Sorry ment hold shift and right click on platform tools open cmd window here ... Quicker way to use adb instead of having to type all the paths ways in...
reaper24 said:
Sorry ment hold shift and right click on platform tools open cmd window here ... Quicker way to use adb instead of having to type all the paths ways in...
Click to expand...
Click to collapse
ohh no pardon me, im the donkey here lol. ok im doing that right now
erasmo0284 said:
ohh no pardon me, im the donkey here lol. ok im doing that right now
Click to expand...
Click to collapse
When you get the cmd open also make sure your copy of the recovery.img you used is in your platform tools folder..
fastboot boot recovery.img
wipe not the sd card tho.. Now flash the rom and you should be set...
reaper24 said:
Sorry ment hold shift and right click on platform tools open cmd window here ... Quicker way to use adb instead of having to type all the paths ways in...
Click to expand...
Click to collapse
Done, but still doing the same
erasmo0284 said:
Done, but still doing the same
Click to expand...
Click to collapse
What is it doing???
You wipe then you flash the rom and reboot and it should take off...
What build are you tryin to use a 2.08 or 2.17 if your tryin a 2.17 build you may need to update your radios...
It takes it a few to go past the splash screen 1min to 2min sometimes longer depends on the rom...
Im doing it again do I have to wipe cache only? or both (user/factory)?
Yesssss thank you very much, I intall the Stock IMg, so with this process I have to install MikRunny-3vo-v1.1-CDMA-signed and its going to work???
I appreciate your value time
Another quiestion is,
System UIDS INconsistent
UIDS on the system are inconsistent, you need to wipe your data partition or your device will be unstable.
erasmo0284 said:
Im doing it again do I have to wipe cache only? or both (user/factory)?
Yesssss thank you very much, I intall the Stock IMg, so with this process I have to install MikRunny-3vo-v1.1-CDMA-signed and its going to work???
I appreciate your value time
Click to expand...
Click to collapse
Wipe cache davlik cache and factory reset... What is your recovery you using by the way? I use CWM 4.0..
This method works for all roms...
reaper24 said:
Wipe cache davlik cache and factory reset... What is your recovery you using by the way? I use CWM 4.0..
This method works for all roms...
Click to expand...
Click to collapse
I dont know which recovery im using because before doing this work i made a backup with clockworkmod but if there is a way to know that info ill do that, just tell me how to find it.
which rom can you recommend to me, sorry to bother again.
erasmo0284 said:
I dont know which recovery im using because before doing this work i made a backup with clockworkmod but if there is a way to know that info ill do that, just tell me how to find it.
which rom can you recommend to me, sorry to bother again.
Click to expand...
Click to collapse
I would say any 2.08 build if you wanna try the 2.17 build you would wanna upgrade your radios before you tried it.
What was your software build before your rooted were you 2.17 or 2.08?
reaper24 said:
I would say any 2.08 build if you wanna try the 2.17 build you would wanna upgrade your radios before you tried it.
What was your software build before your rooted were you 2.17 or 2.08?
Click to expand...
Click to collapse
I had 2.8.651 HTC sense 3.0
I'd like to have 2.17... I feel have to be better lol, Im looking on youtube how to upgrade radio because I think thats the problem as you told me before.
erasmo0284 said:
I had 2.8.651 HTC sense 3.0
I'd like to have 2.17... I feel have to be better lol, Im looking on youtube how to upgrade radio because I think thats the problem as you told me before.
Click to expand...
Click to collapse
K to do that.... You will need to download the 2.17 RUU exe.... Now you will need to use adb again make sure debug is turned on under applications ..
http://forum.xda-developers.com/showthread.php?t=1334473 Link for the RUU
Plug your phone in..
Adb reboot bootloader
fasboot boot recovery.img
wipe everything not your sd card
adb reboot bootloader or just go back to hboot
Now relock your phone... fastboot flash oem lock
now run that RUU 2.17 exe
let it do it's thing
boot the phone.
Update profile and prl
now turn debug on
adb reboot bootloader
unlock your phone again with that unlock code
fastboot flash recovery recovery.img
fastboot boot recovery.img
wipe and flash your rom 2.17 build roms
This will return/update your device's software to 2.17.651.5 Stock (Relocked/Unrooted)
I'm making this guide for people who want to Unroot/Relock, having problems with their phones or return to Sprint's Stock.
"If you updated from 2.08 to 2.17 and are having issues unlocking. I recommend doing the steps below and try to unlock your device again The RUU also fixes a glitch on some phone who aren't getting the Bootloader Unlock screen."
>>>Know this will also update your hboot to 1.50.0000<<<
Works with CDMA S-ON and S-OFF Evo 3D.
For Mac users, replace “fastboot” with “./fastboot-mac” in the instructions below.
For Linux users, replace “fastboot” with “./fastboot-linux” in the instructions below.
Click to expand...
Click to collapse
____________________________
_______________________________________
CONTENT NEEDED.
Rootevo3dnew.zip
Evo 3D RUU_2.17.651.5.exe
RUU Mirror
Make sure to download the correct RUU
"RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216"
________________________________________
_______________________________________________
S-ON Users
S-off users don't relock your bootloader until your at the very end.
Relock Bootloader
Do step 1 and step 2 first
Remove USB from phone (If connected)
Turn off device by taking out the battery and placing it back in .
(Remove SD Card and dont place back until told to do so)
Press Volume down then Power button.(Hold until you see the bootloader screen)
Select Fastboot and press Power button.
Connect USB.
You should now be on Fastboot USB.
Type these commands on cmd or terminal.
-Windows
Code:
[B]cd \rootevo3dnew[/B]
-Mac,Linux
Code:
[B]cd /rootevo3dnew[/B]
Now type.
Code:
[B]fastboot oem lock[/B]
______________________________________________________
-Lets begin
Step 1. Extract the rootevo3dnew.zip file and place it on C:\ Drive
Step 2. For Windows, install the HTC drivers HTCDriver3.0.0.007.exe in the zip file. For Linux and Mac you don’t need to install drivers.
Step 3. Enter bootloader and put your device in "Fastboot USB" (Make sure you have your phone connected to your computer
Step 4. Run the RUU.exe and follow the steps to update your device.
Step 5. Your device will reboot and you will be back to stock
Note- Most devices will enter bootloader and will show **Security Warning**
Click to expand...
Click to collapse
DO NOT TURN OFF YOUR DEVICE DURING THE UPDATING PROCESS.
IT COULD RESULT IN A BRICKED DEVICE.
=====================================================
S-OFF Users
Step 6. Enter bootloader one last time.
Step 5. Relock Bootloader (Instructions above)
Step 7. Type this command
Code:
[B]fastboot oem writesecureflag 3[/B]
Step 8. Reboot
Remember this will delete all your current data/apps so use Titanium Backup on the Play Market to back up all your downloaded content. Use this only if your going to unlock/root you device again because you need to be root access to use it.
Click to expand...
Click to collapse
Congratulation you are not back to 100% stock.
If you find any errors, message me and i will change them as quick as i can.
Helpers
Reaper24- taught me RUU process.
Wloftus- Linux fastboot command
WikdNoob- S-On command
If this helped you in any way don't forget to hit "Thanks".
Nice write up. This will be helpful with all the new faces around here.
Sent from my PG86100 using Tapatalk
Yeah. Lets hope it gets put as a sticky.
Sent from my PG86100 using xda premium
Sticky
Thx for share
godZson
XDA-MOD
Lol Nice man.. Glad you got it all sorted outo
Quicker way to open a CMD to ADB is go to your platform tools folder and hold shift down right click on it.. Say open CMD .. Your set..
Another way ...
Turn debug on ^^)
1. ADB reboot bootloader
2. Fastboot boot recovery.img for Hboot 1.5 users
3. Wipe like normal.
4. Go back to Hboot. Select fastboot
5. Now type in ^ Fastboot oem lock^
6. Now run that 2.17 RUU. DO NOT TAKE USB CORD OUT IN THE MIDDLE OF THIS WILL BRICK
7. Your set
If you wanna unroot again pretty simple..
Just redo that unlock code part your set.
Anyways if anyone needs help PM me or the OP.. I have done this 100 times or more lol well it feels like it..
yes, i'm a n00b
Just a silly question, the unroot/relock option... that should work for all EVO3D models?
Looking to return to stock (but with another RUU of course), can I follow these steps? (I'm HTCDEV unlocked)
KrewsialNL said:
Just a silly question, the unroot/relock option... that should work for all EVO3D models?
Looking to return to stock (but with another RUU of course), can I follow these steps? (I'm HTCDEV unlocked)
Click to expand...
Click to collapse
Yes it should.
Sent from my PG86100 using xda premium
this says back to stock 2.17 but mine came with 2.08 rom stock, i did the htc unlock method, rooted and now im running a 2.17 (zd3 rom)
i would like to update the radio and all, would this give me that?
then just unlock and flash rom again?
metalmenance said:
this says back to stock 2.17 but mine came with 2.08 rom stock, i did the htc unlock method, rooted and now im running a 2.17 (zd3 rom)
i would like to update the radio and all, would this give me that?
then just unlock and flash rom again?
Click to expand...
Click to collapse
Yes it will work. Know that it will also update your hboot.
Sent from my PG86100 using xda premium
ok just making sure, i am already on 1.50 so will still work right?
just lock, load stock RUU then unlock and flash?
will i need to do the htcunlock again or just unlock like posted above?
thanks and sorry just dont want to miss a step and be lost lol
metalmenance said:
ok just making sure, i am already on 1.50 so will still work right?
just lock, load stock RUU then unlock and flash?
will i need to do the htcunlock again or just unlock like posted above?
thanks and sorry just don't want to miss a step and be lost lol
Click to expand...
Click to collapse
Yes this will still work.
This only shows how to get back to stock.
I only show how to lock. But yes once your back to stock use the htc unlock method. You might have to get the Unlock_code.bin again.
ok got the Ruu its on card, followed steps, im relocked but hot do i run the ruu?
is it supposed to be renamed?
what am i missing?
metalmenance said:
anyone have another link? cant get through to download for nothing.....
Click to expand...
Click to collapse
Mirrors don't work either?
ok nevermind had the file and forgot it was on pc
anyway got it done ran the RUU on pc all went good
am running stock again now
i went back into fastboot and tried to relock but its not working
if i type ^Fastboot oem unlock^ it just says more?
do i have to do htc unlock or can it be done through this
metalmenance said:
ok nevermind had the file and forgot it was on pc
anyway got it done ran the RUU on pc all went good
am running stock again now
i went back into fastboot and tried to relock but its not working
if i type ^Fastboot oem unlock^ it just says more?
do i have to do htc unlock or can it be done through this
Click to expand...
Click to collapse
Htc unlock.
Follow this guide.
Its faster and you already have the rootevo3dnew file.
http://bit.ly/osKlF1
ok ran the htcunlock and did have to get new bin file but all is good and
up and running now off to flashing again lol
thanks for the help, it is a great write up and very usefull
thanks again
metalmenance said:
ok just making sure, i am already on 1.50 so will still work right?
just lock, load stock RUU then unlock and flash?
will i need to do the htcunlock again or just unlock like posted above?
thanks and sorry just dont want to miss a step and be lost lol
Click to expand...
Click to collapse
You just unlock again flash recovery and via fastboot boot recovery then wipe flash rom
Sent from my PG86100 using xda premium
um
Your device should reboot.
Don't let it reboot
Click to expand...
Click to collapse
that was a little confusing
i got this:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 6697713
FAILED (status read failed (Too many links))
phone says **** RELOCKED **** at top
is this correct?
SayWhat10 said:
um
that was a little confusing
i got this:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 6697713
FAILED (status read failed (Too many links))
phone says **** RELOCKED **** at top
is this correct?
Click to expand...
Click to collapse
Perfectly normal. and i understand. i will fix that.
EDIT: remove post
Please read posts 1-3 BEFORE posting.
______________________________________________________________________________
So I've noticed a lot of new threads with questions and problems relating to the ICS OTA that came out this morning. I figured I'd start a thread to post all the questions and problems in to reduce clutter of the Rezound forums. So if you have any problems or inquiries, post them here and we'll try to help you! :good:
Make sure to read the FAQ before posting in case it can solve your issue!
If you find my posts helpful, please thank them as well as the first three of these posts! It really means a lot to me and keeps me motivated!
If you're S-on and need additional help, please feel free to contact famouscollin
Frequently Asked Questions
_______________________________________________________
will update as they come in
Q: If my bootloader is Unlocked, or I'm on a custom recovery, can I take the OTA?
A: No, Relock with
Code:
fastboot oem lock
and make sure you're on the stock recovery.(linked in post #3)
Click to expand...
Click to collapse
Q: If I'm on one of the leaked ICS Firmwares, will I be able to take the OTA?
A: No, you have two paths you can take to get the OTA, you can downgrade GB and take the OTA (S-OFF only), or you can manually update using the RUU.exe or PH98IMG.zip (linked in Post #3).
Click to expand...
Click to collapse
Q: If I upgrade, will I be able to keep root?
A: You will lose it initially, but you should be able to get it back by unlocking and flashing Amon Ra, or by flashing the JBear HBoot and flashing a SuperUser.zip (linked in post #3)
Click to expand...
Click to collapse
Q: How do I unlock after taking the OTA or running the RUU?
A: If you kept the Unlock_code.bin in your fastboot folder, you can use fastboot to
Code:
fastboot flash unlocktoken Unlock_code.bin
Otherwise, redo the HTCDev steps like before
Click to expand...
Click to collapse
Q: How do I run an RUU?
A: See the link in post #3 it contains instructions for both the .exe and the PH98IMG.zip
Click to expand...
Click to collapse
Installation Instructions
_____________________________________________
For stock GB (may work if rooted): make sure you have a locked bootloader (instructions in FAQ) and the stock Recovery (link at bottom of post)
1. Open Settings by pressing Menu and tapping Settings (or opening the settings Icon)
2. Click about phone
3. Click Software Update
4. Accept and Download
5. When prompted, install and reboot (may take 20 mins to an hour depending on connection)
6. Profit!
For any ICS Firmware:
You have 2 options now. You can:
1. Run the GB OTA RUU.exe (linked below), and take the ICS update from there (S-OFF only)
*OR*
2. Relock bootloader (Only if S-ON) and run the OTA RUU
If you're on one of the ICS Firmwares, I'll assume you already know how to flash an RUU (as you have to to get on the leaked firmware) so I won't explain that in this post. If you really don't know how, see this guide: http://www.freeyourandroid.com/guide/flashing-ruu-htc
OTA RUU: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ (PH98IMG.zip)
GB 2.01 RUU: http://www.4shared.com/file/DCi69XHl/RUU_Vigor_VERIZON_WWE_20160511.html (thanks synisterwolf) (RUU.exe)
Stock GB Recovery: http://www.mediafire.com/?wb21d2gdurui2c6 (thanks, Scotty85)
SuperSU.zip: http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip (flash this if you have trouble getting root) (thanks, HowardZ)
AshtonTS said:
So I've noticed a lot of new threads with questions and problems relating to the ICS OTA that came out this morning. I figured I'd start a thread to post all the questions and problems in to reduce clutter of the Rezound forums. So if you have any problems or inquiries, post them here and we'll try to help you! :good:
Click to expand...
Click to collapse
This is the error i receive when attempting to install the update. I have an unlocked bootloader.
Assert failed : apply_patch_check(" /system/app/kindle.apk", "9bba894dffe:unknown command [2756cf50f5514ba2a1e622ffe335c",]
E:Error in /cache/fumo/otapkg.zip
(status 7)
install aborted
I'll start, because I don't think that I have seen a definitive answer yet.
Has anybody running a leak been able to pull and install the update OTA?
Sent from my ADR6425LVW using xda premium
Basicallyevolve said:
This is the error i receive when attempting to install the update. I have an unlocked bootloader.
Assert failed : apply_patch_check(" /system/app/kindle.apk", "9bba894dffe:unknown command [2756cf50f5514ba2a1e622ffe335c",]
E:Error in /cache/fumo/otapkg.zip
(status 7)
install aborted
Click to expand...
Click to collapse
Relock your bootloader, then try to take the update
demmo86rt said:
I'll start, because I don't think that I have seen a definitive answer yet.
Has anybody running a leak been able to pull and install the update OTA?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
If you're on a leak, you will have to either downgrade to GB and take the OTA, or run the full RUU.exe, or PH98IMG.zip
AshtonTS said:
Relock your bootloader, then try to take the update
If you're on a leak, you will have to either downgrade to GB and take the OTA, or run the full RUU.exe, or PH98IMG.zip
Click to expand...
Click to collapse
DO i go through the same steps as i did when i unlocked it >?
Same site and same unlock link or ?:
Basicallyevolve said:
DO i go through the same steps as i did when i unlocked it >?
Same site and same unlock link or ?:
Click to expand...
Click to collapse
To lock the bootloader, look in post #2 I included the fastboot code for it. To unlock again, you can just flash the same unlocktoken.bin that you used the first time if you kept it. If not, then you will have to use HTCdev to unlock again
does anyone have the stock recovery for s-on ppl? thanks.
AshtonTS said:
To lock the bootloader, look in post #2 I included the fastboot code for it. To unlock again, you can just flash the same unlocktoken.bin that you used the first time if you kept it. If not, then you will have to use HTCdev to unlock again
Click to expand...
Click to collapse
Could i get a link to a site or a guide of some sort to lock the boot loadeR . I dono where the code goes that you have supplied . I had to use steps to unlock my bootloader too >
Even on my Droid X i had to follow steps to get a custom rom on it . I have not dipped my toes in the world of phones too much
Basicallyevolve said:
Could i get a link to a site or a guide of some sort to lock the boot loadeR . I dono where the code goes that you have supplied . I had to use steps to unlock my bootloader too >
Even on my Droid X i had to follow steps to get a custom rom on it . I have not dipped my toes in the world of phones too much
Click to expand...
Click to collapse
All you have to do is open the command prompt app, type CD C:\path to the\folder you put\adb and fastboot in. (So if you had it in you desktop you'd type cd C:\Users\YourUserName\Desktop\Android-SDK [or whatever you called it])
Then type (without quotes) "fastboot oem lock"
It's that simple!
DigiDave said:
does anyone have the stock recovery for s-on ppl? thanks.
Click to expand...
Click to collapse
Here you go sir: http://www.mediafire.com/?wb21d2gdurui2c6
Credit to Scotty85 on phandroid for uploading it
AshtonTS said:
All you have to do is open the command prompt app, type CD C:\path to the\folder you put\adb and fastboot in. (So if you had it in you desktop you'd type cd C:\Users\YourUserName\Desktop\Android-SDK [or whatever you called it])
Then type (without quotes) "fastboot oem lock"
It's that simple!
Click to expand...
Click to collapse
IM sure it is simple .
But even that is confusing for me as i unlocked my bootloader many moons ago with step by step directions so i have not done this since then.
Like setting up an SBS server from scratch and configuring a network with computers and printers and a VPN and or working in exchange is simple cause i do it everyday haha.
Sorry to have wasted your time loL. I will stick around till someone uploads a youtube video or tutorial for this
Thank you for your efforts
Sorry again.
Basicallyevolve said:
IM sure it is simple .
But even that is confusing for me as i unlocked my bootloader many moons ago with step by step directions so i have not done this since then.
Like setting up an SBS server from scratch and configuring a network with computers and printers and a VPN and or working in exchange is simple cause i do it everyday haha.
Sorry to have wasted your time loL. I will stick around till someone uploads a youtube video or tutorial for this
Thank you for your efforts
Sorry again.
Click to expand...
Click to collapse
No problem man, hope you get it figured out soon
Why do I keep getting endless notifications, in gb all you had to do was keep background data off, that doesn't do shish now.
Sent from my ADR6425LVW
hchristy2013 said:
Why do I keep getting endless notifications, in gb all you had to do was keep background data off, that doesn't do shish now.
Sent from my ADR6425LVW
Click to expand...
Click to collapse
I think you might have to disable background data per app in settings>data usage
Basicallyevolve said:
IM sure it is simple .
But even that is confusing for me as i unlocked my bootloader many moons ago with step by step directions so i have not done this since then.
Like setting up an SBS server from scratch and configuring a network with computers and printers and a VPN and or working in exchange is simple cause i do it everyday haha.
Sorry to have wasted your time loL. I will stick around till someone uploads a youtube video or tutorial for this
Thank you for your efforts
Sorry again.
Click to expand...
Click to collapse
I'll try to help.
1.You have to use the command line so open that up.
2. navigate to where you placed the fastboot files
> type "cd\" without the quotes
> type cd where did you put the fastboot files
so if you put it in the C drive in a folder called android you would type
cd android
if you put it in a folder in a folder
as in the folder then in another folder in their called tools put
cd android/tools
then when you are where your fastboot stuff is type
fastboot oem lock
I have the first "official" ICS leak from back in March - no root or S-off just the leak which was loaded from a microSd card. Do I need to downgrade back to GB or simply wait until the update gets pushed to me? My phone currently says there are no software updates available.
Can all this be done on any ics based Rom* for instance I'm using the viperRez Rom with s-on.. would all I have to do flash stock recovery<relock bootloader<apply PH98IMG for update<re-unlock<and flash back to amonRa? Will I lose root or data? Would I be able to flash back to my current Rom
Sent from my s-on reZound rockin ViperRez Rom.. using xda app-developers app
AshtonTS said:
So I've noticed a lot of new threads with questions and problems relating to the ICS OTA that came out this morning. I figured I'd start a thread to post all the questions and problems in to reduce clutter of the Rezound forums. So if you have any problems or inquiries, post them here and we'll try to help you! :good:
Click to expand...
Click to collapse
Lol working towards RC I see...
Sent from my NeoMax Rezound
So I've explored different options on XDA's site for returning to stock and I guess this is why I'm here. I screwed the hell up. I posted this on Phaded's How-To page, but I figured it would also be best to post this in the general Help & Troubleshooting page.
Here's the best way I can explain my issue. Someone please help.
1. My phone is COMPLETELY formatted. No OS now. Zero data.
2. TWRP is installed as my recovery.
3. I can fastboot and adb (only from the recovery obviously)
4. I moonshined the phone in order to S-Off
5. I tried the method to remove S-Off by Phaded
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Click to expand...
Click to collapse
When I ran the RUU, I got that error 158 problem. I couldn't flash the HBOOT. downloaded it several times and tried.
6. I flashed it with an AOSP rom and tried the RUU again. No luck.
Now I'm stuck. u_u I tried
adb push "file name" "file directory"
Click to expand...
Click to collapse
so I can drop a zip file in the phone, but it seems to not work. Idk if I did it right. I was hoping to flash a ROM by doing that. smh.
Let me know if there's any other info I can provide. Considering the phone still turns on and I can still get to fastboot and adb, I don't think I'm a lost cause.
Thanks everyone!
UPDATE
I sideloaded a ROM (Carbon) and now I'm up and running. But I still can't RUU it! Figured this detail will help.
I'll keep reading and researching, posting my progress.
Thanks!
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
xlxcrossing said:
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
1. I obtained s-off with moonshine. I used the above command suggested by Phaded and when I put in
fastboot oem lock
Click to expand...
Click to collapse
(or something like that) it says my phone is locked.
2. What do you mean what bootloader? I guess moonshine, cause that's what comes up when I go to my bootloader screen.
3. I trying flashing the ruu and I get this (see image attached) which the suggested fix for error 158 was to flash the hboot 1.15 (or something). But I can't seem to flash it correctly. I can't even find straight forward instructions on how to do it.
Thanks for responding.
The reason I asked about the bootloader version and I'm not 100% sure about this so someone else may need to chime in is that when you ruu you are flashing firmware which includes hboot so if you upgraded hboot before doing s-off or otherwise went up a version then I'm pretty sure the ruu won't downgrade your hboot airgo the error message. Again this might not be true. At this point all that matters is that your s-off and NOT bricked so instead of toying with an ruu I would choose a stock Rom .zip to flash if its truly stock that you want. Your firmware should be up to date if you took 2.06. There is no ruu for 2.06.
Sent from my HTC6435LVW using Tapatalk 4 Beta
What is s-off?
Sent from my Galaxy Nexus using xda premium
93fuelslut said:
What is s-off?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
xlxcrossing said:
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
Click to expand...
Click to collapse
I'm not finding a solid explanation for error 158 which is disheartening - the best offerings are to change USB ports or restart the ruu. Like I said before you are fine on the software end, you can verify you have up to date firmware by comparing the latest below with what you have.
Baseband (radio) 1.01.04.0308
PRI 2.44_002
As for the hboot, how are you trying to flash it? In recovery?
The hboot needs to match the RUU. You need to find the original hboot . It is in a thread with hboot versions and radio versions.
Link to HBOOT please? and answering your questions
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was:
fastboot flash "file name.zip"
Click to expand...
Click to collapse
and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Moonshine isn't working because you are still s-off.
My thread has the original hboot and instructions to flash it. You do not flash in recovery. You do not put it on your phone at all. Do not push the file in recovery. Read and follow the instructions in the stock thread.
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
You're doing the command wrong or you renamed it PL83IMG.zip.zip
Please, go in my thread, read each step perfectly and follow. It's really quite simple.
Difference
Is s-off/s-on and being locked/unlocked two different things?
Screenshot
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Strike.
From my S-Off BadSeed DNA
ibthevivin said:
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
Click to expand...
Click to collapse
You need to cd to the directory the file is in, which should be where fastboot.exe is
So if it's in say C:\sdk\
Type cd C:\sdk\
Then run command to fastboot
BOOM!
Alright. Worked. I'll keep you all posted. No one really mentioned in any of the tutorials and how-to's that it is VERY important to make sure to CD to the directory. Like there are developers who say just add it to the PATH in Environment Variables. I figured it was enough, but hey, I was wrong.
Live and learn right?
Thank you Phaded.
So basically my problem was, calling the hboot.zip file is not included under Environmental Variables. I have to intentionally CD to that directory.
Hmm, I must have missed putting in the cd step for the hboot. I'll go edit it.
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have tried flashing several versions of 4EXT recovery to get SmartFlash, but it is not compatible with HTC Desire 601.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
black-venomz said:
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have read about 4EXT recovery and SmartFlash, but the only way to get 4EXT recovery seems to be through app and I don't have any OS so it's impossible.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
Click to expand...
Click to collapse
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
es0tericcha0s said:
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
Click to expand...
Click to collapse
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
black-venomz said:
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
Click to expand...
Click to collapse
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
es0tericcha0s said:
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
Click to expand...
Click to collapse
Ok great !
So I have access to a stock ROM apparently. I can't post links yet, but if you look up on Google "htcdesire 601 stock rom" you will find a google docs page with the stock ROM for desire 601 4.4.2.
Would you be king enough to walk me through the steps to achieve this ? There are many .img files in this folder and I am far from an expert.
Thanks again.
black-venomzz
I did :
1. Copy whole .zip file on sd card found when searched "htc desire 601 stock rom" on google in google docs pasge (can't post link yet).
2. Install .zip with TWRP.
- Failed (still bootloop) -
The tried :
1. fastboot flash boot boot.img (boot.img was found in the .zip file)
2. Copy whole .zip file on sd card
3. Install .zip with TWRP
- Failed (still bootloop) -
I'm probably missing something here...
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
es0tericcha0s said:
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
Click to expand...
Click to collapse
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
black-venomz said:
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
Click to expand...
Click to collapse
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
es0tericcha0s said:
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
Click to expand...
Click to collapse
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
black-venomz said:
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
Click to expand...
Click to collapse
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
es0tericcha0s said:
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
Click to expand...
Click to collapse
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
black-venomz said:
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
Click to expand...
Click to collapse
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
es0tericcha0s said:
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
Click to expand...
Click to collapse
Your a life saver thanks !
I'll make sure to relock.
The only thing is I have no clue how to use this RUU. It's not like a ".exe" that you execute.
The .zip file contains a .tar.gz file, wich contains another .tar file, wich contains binaries I believe.
The readme.txt file talks about using Linux commands but I'm far from an expert.
I'll do a little research on my own since you helped me a lot already, but if you have any tips feel free to share !
Thanks again,
black-venomz
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
black-venomz said:
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
Click to expand...
Click to collapse
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
es0tericcha0s said:
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
Click to expand...
Click to collapse
****e. How do people build RUU.exe in the first place ? Can't we build one with these binary files ?
Edit : Did some reading and found out only vendors can make RUU's.
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
black-venomz said:
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
Click to expand...
Click to collapse
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
---------- Post added at 12:16 AM ---------- Previous post was at 12:00 AM ----------
http://forum.xda-developers.com/desire-601/help/rogers-ruu-available-t2836217
https://drive.google.com/folderview...RFdlTWc&tid=0BzrP5DWIlpplWkNROHh6Y3o4UHc#list
es0tericcha0s said:
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
Click to expand...
Click to collapse
Thanks for looking around. Unfortunately the RUU failed (see picture).
I think my phone was updated with Android 4.4.2 when I bought it (recently) so it might be what's causing the error.
I wanted to try with a Telus RUU for 4.4.2 but it's not there..........
I'm starting to lose hope here.