Database Develop

[Q] How to S-on HTC Inc S after Revolutionary S-off to make OTA update to Sense3.0

HI,
I mistakenly seems to rooted my phone with something called revolutionary. I don't have a clue about all these rooting and unrooting stuff. I just wanted to have HTC sense 3.0 on my Incredible S phone so I followed the youtube video to do that but I was not successful. the step that I did was called getting your s-off.
now when I push the volume down button+Power button I see these things:
Revolutionary
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-3805.06.03.03_M
eMMC-boot
Apr 1 2011,18:34:39
A few days ago i received a OTA update for htc sense 3 but it cannot be updated. after booting you see a exclamation mark and an android logo. what should I do?!
I have been searching for 4 - 5 days and I could not fix this problem
Please help

k7azadeh said:
HI,
I mistakenly seems to rooted my phone with something called revolutionary. I don't have a clue about all these rooting and unrooting stuff. I just wanted to have HTC sense 3.0 on my Incredible S phone so I followed the youtube video to do that but I was not successful. the step that I did was called getting your s-off.
now when I push the volume down button+Power button I see these things:
Revolutionary
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-3805.06.03.03_M
eMMC-boot
Apr 1 2011,18:34:39
A few days ago i received a OTA update for htc sense 3 but it cannot be updated. after booting you see a exclamation mark and an android logo. what should I do?!
I have been searching for 4 - 5 days and I could not fix this problem
Please help
Click to expand...
Click to collapse
Follow this procedure to remove Revolutionary S-Off.

What procedure? Pleaseee helppp meee

tpbklake said:
Follow this procedure to remove Revolutionary S-Off.
Click to expand...
Click to collapse
k7azadeh said:
What procedure? Pleaseee helppp meee
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14

tpbklake said:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
Click to expand...
Click to collapse
In the link it says:
1. Install RUU ROM from: http://forum.xda-developers.com/show....php?t=1033922
But when I click on the address It says page not found.

k7azadeh said:
In the link it says:
1. Install RUU ROM from: http://forum.xda-developers.com/show....php?t=1033922
But when I click on the address It says page not found.
Click to expand...
Click to collapse
The official RUUs can be found here.
http://forum.xda-developers.com/showthread.php?t=1033922

tpbklake said:
The official RUUs can be found here.
http://forum.xda-developers.com/showthread.php?t=1033922
Click to expand...
Click to collapse
thanks a lot I managed to unroot my phone successfully but right now i faced a different problem. when i was rooted I received and OTA for updating to gingerbread 2.3.5 and htc sense 3.0 but since i was rooted i couldn't install them. now that I am unrooted again when i check for the update, it says that there is no update for your phone and I am still on gingerbread 2.3.3 and htc sense 2.1. what should I do?!

k7azadeh said:
thanks a lot I managed to unroot my phone successfully but right now i faced a different problem. when i was rooted I received and OTA for updating to gingerbread 2.3.5 and htc sense 3.0 but since i was rooted i couldn't install them. now that I am unrooted again when i check for the update, it says that there is no update for your phone and I am still on gingerbread 2.3.3 and htc sense 2.1. what should I do?!
Click to expand...
Click to collapse
Which RUU did you end up using to get back to GB 2.3.3 and Sense 2.1? If you didn't use the 2.10.405.1 RUU, then you won't receive the OTA because it is specific to that particular ROM version.

tpbklake said:
Which RUU did you end up using to get back to GB 2.3.3 and Sense 2.1? If you didn't use the 2.10.405.1 RUU, then you won't receive the OTA because it is specific to that particular ROM version.
Click to expand...
Click to collapse
i used this post:
"load this file
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed
http://www.filefactory.com/file/cc2d...308_signed.exe "
now what should I do?!

tpbklake said:
Which RUU did you end up using to get back to GB 2.3.3 and Sense 2.1? If you didn't use the 2.10.405.1 RUU, then you won't receive the OTA because it is specific to that particular ROM version.
Click to expand...
Click to collapse
i used this post:
load this file
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed
http://www.filefactory.com/file/cc2d...308_signed.exe
what should i do now?

k7azadeh said:
i used this post:
load this file
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed
http://www.filefactory.com/file/cc2d...308_signed.exe
what should i do now?
Click to expand...
Click to collapse
The link in the previous reply was broken this is the link:
http://www.filefactory.com/file/cc2...5AU_3805.06.03.03_M_release_199308_signed.exe

tpbklake said:
Which RUU did you end up using to get back to GB 2.3.3 and Sense 2.1? If you didn't use the 2.10.405.1 RUU, then you won't receive the OTA because it is specific to that particular ROM version.
Click to expand...
Click to collapse
k7azadeh said:
i used this post:
load this file
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed
http://www.filefactory.com/file/cc2d...308_signed.exe
what should i do now?
Click to expand...
Click to collapse
My mistake, you used the right version, 2.30.405.1 should allow ou to get the 3.08.405.3 OTA notification.

tpbklake said:
My mistake, you used the right version, 2.30.405.1 should allow ou to get the 3.08.405.3 OTA notification.
Click to expand...
Click to collapse
No it does not let me it keeps saying that my phone is up to date.
So you don't have any suggestion? It's very frustrating since the reason i rootet my phone in.the first place was to experience htc sense 3.0 which i could not completely do and now that there is an official update for it i can not have it

k7azadeh said:
No it does not let me it keeps saying that my phone is up to date.
So you don't have any suggestion? It's very frustrating since the reason i rootet my phone in.the first place was to experience htc sense 3.0 which i could not completely do and now that there is an official update for it i can not have it
Click to expand...
Click to collapse
If you want the official HTC 2.3.5/Sense 3.0 ROM, just flash the RUU 3.08.405.3 from the same place you found RUU 2.30.405.1.

this maybe an odd question i live in denmark what ruu should i choose for this?
android 2.3.3
sense 2.1
build number 2.30.405.1 cl88716
software number 2.30.405.1

pressytcn said:
this maybe an odd question i live in denmark what ruu should i choose for this?
Click to expand...
Click to collapse
I would start with the WWE version 3.08.405.3. I has most of the language support for Europe.

This procedure is tested only AplhaRevX.
1. Install RUU ROM from: http://forum.xda-developers.com/show....php?t=1033922
2. Downgrade HBOOT
2a. download this file: http://alpharev.nl/vivo_downgrade.img
2aa. Connect your phone to the USB
2b.Turn your phone into FastBoot not to HBOOT!!! (VOL DOWN + POWER Button)
2c. Install over fastboot: cmd: "fastboot flash hboot vivo_downgrade.img" (you must install sdk tools)
2d. still fastboot cmd: fastboot reboot-bootloader
3. Start Installation RUU ROM, but DON´T INSTALL !!!!
3a. go tu C:\Users\%username%\AppData\Local\Temp and at last folder find rom.zip
3b. open it, and copy tu folder sdk hboot and instal the same as step 2c.
i don't understand this correctly my hboot now says alpahdev
i now did this
3. Start Installation RUU ROM, but DON´T INSTALL !!!!
3a. go tu C:\Users\%username%\AppData\Local\Temp and at last folder find rom.zip
3b. open it, and copy tu folder sdk hboot and instal the same as step 2c
got the rom.zip what shall i do with it i tryied to use these commands
c:\android>fastboot flash rom.zip
unknown partition 'rom.zip'
error: cannot determine image filename for 'rom.zip'
c:\android>fastboot flash hboot_2.00.0000_af9874be_1026
unknown partition 'hboot_2.00.0000_af9874be_1026'
error: cannot determine image filename for 'hboot_2.00.0000_af9874be_1026'
c:\android>fastboot flash rom.zip
unknown partition 'rom.zip'
error: cannot determine image filename for 'rom.zip'
c:\android>fastboot flash hboot
unknown partition 'hboot'
error: cannot determine image filename for 'hboot'
c:\android>fastboot flash hboot_2.00.0000_af9874be_1026.iso
unknown partition 'hboot_2.00.0000_af9874be_1026.iso'
error: cannot determine image filename for 'hboot_2.00.0000_af9874be_1026.iso'
c:\android>fastboot flash hboot_2.00.0000_af9874be_1026.img
unknown partition 'hboot_2.00.0000_af9874be_1026.img'
error: cannot determine image filename for 'hboot_2.00.0000_af9874be_1026.img'

the correct command is
Code:
fastboot flash zip rom.zip

thanks it did send the file to the device but it gave me this message now
c:\android>fastboot flash zip rom.zip
< waiting for device >
sending 'zip' (339760 KB)...
OKAY [ 58.118s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 58.119s
i will try and do it all over again then see what happens

pressytcn said:
thanks it did send the file to the device but it gave me this message now
c:\android>fastboot flash zip rom.zip
< waiting for device >
sending 'zip' (339760 KB)...
OKAY [ 58.118s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 58.119s
i will try and do it all over again then see what happens
Click to expand...
Click to collapse
You may need to enter the
Code:
fastboot oem rebootRUU
command first.

Difficulties running RUU

I was getting ready to update to 4.3 by updating the firmware on my phone. Upon updating to the 3.04 firmware I realized that my screen would not respond. I'm s-off and thought I would just run 1.29's RUU but I get this error every time.
sending 'zip' (1032712 KB)...
OKAY [ 46.061s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 46.325s
Chepo:android Chepo$
Click to expand...
Click to collapse
If any one can help me out that would be appreciated!

Idea???
Chep0 said:
I was getting ready to update to 4.3 by updating the firmware on my phone. Upon updating to the 3.04 firmware I realized that my screen would not respond. I'm s-off and thought I would just run 1.29's RUU but I get this error every time.
If any one can help me out that would be appreciated!
Click to expand...
Click to collapse
I am am in no way any kind of pro...but I think you need to have S on and you can do that with an app called moonshine or revone...I think...Look in to getting your s back on

raykartell said:
I am am in no way any kind of pro...but I think you need to have S on and you can do that with an app called moonshine or revone...I think...Look in to getting your s back on
Click to expand...
Click to collapse
I thought I needed S-off in order to run the RUU process?
I'm wondering if I can just fastboot flash zip firmware.zip a 1.29.651.10 firmware in order to get my screen working again?

Chep0 said:
I was getting ready to update to 4.3 by updating the firmware on my phone. Upon updating to the 3.04 firmware I realized that my screen would not respond. I'm s-off and thought I would just run 1.29's RUU but I get this error every time.
If any one can help me out that would be appreciated!
Click to expand...
Click to collapse
All you need is the latest version of TWRP. If you do some reading the latest firmware isn't compatible with TWRP 2.5.0.0
So you need 2.6.3.0 (I think it's the number) download it and connect your phone in fastboot and the command you use is fastboot flash recovery (recovery name here)
Sent from my HTCONE using xda app-developers app

The S-Off process is a requirement to be allowed to DOWNGRADE your firmware through an RUU process. Do not S-On. Why not just go ahead and run the full RUU as an executable file through your computer? Much easier that way.
Sent from my HTCONE using Tapatalk 4

Konfuzion said:
All you need is the latest version of TWRP. If you do some reading the latest firmware isn't compatible with TWRP 2.5.0.0
So you need 2.6.3.0 (I think it's the number) download it and connect your phone in fastboot and the command you use is fastboot flash recovery (recovery name here)
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Yes I did read that 2.6.3 had to be installed before moving up to 4.3 which I did, but in a moment of desperation I thought my backup would save the day but in reality it took me back to 2.5.5 and made things worst. So now my recovery is also unresponsive.
So I tried updating TWRP via fastboot but got this
sending 'recovery' (8608 KB)...
OKAY [ 1.168s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.202s
Click to expand...
Click to collapse
Is it not allowing it to update because I am no longer unlocked? (Locked the bootloader while attempting to run RUU)
EPayne123 said:
The S-Off process is a requirement to be allowed to DOWNGRADE your firmware through an RUU process. Do not S-On. Why not just go ahead and run the full RUU as an executable file through your computer? Much easier that way.
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
I'm running a mac.. If I don't fix this soon I might just run to a friends house, does that have a higher chance of succeeding?

Just flash the latest recovery. Or I am not understanding the problem.
Sent from my HTCONE using xda app-developers app
---------- Post added at 07:56 PM ---------- Previous post was at 07:38 PM ----------
I guess I replied as you were typing your only hope might be this guide is there is no RUU for 4.3 yet http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app

EPayne123 said:
The S-Off process is a requirement to be allowed to DOWNGRADE your firmware through an RUU process. Do not S-On. Why not just go ahead and run the full RUU as an executable file through your computer? Much easier that way.
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
Got it to work, running over to my friends house to use his Windows did the trick! Thank you all!

[Q] 4.4.2 issues

so I took my sprint htc one with viperone loaded and did an ruu back to 4.3 version wiping everything, I successfully got my over the air update to 4.4.2 and decided I'd try to back down to 4.3 so I could restore my twrp viper backup however twrp won't flash currently and I think I caused issues with my bootloader. Since there is no 4.4.2 ruu available yet and I can still get to bootloader, but not recovery, I think I'm still not completely bricked. I've tried a factory restore but I end up at the white screen with green htc letters and it never goes further. Could flashing the 4.4.2 stock recovery fix my issue?
Any attempt to do manual ruu flash, fastboot flash zip rom.zip, fails with this message
target reported max download size of 1514139648 bytes
sending 'zip' (1082662 KB)...
OKAY [ 53.293s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 68.408s
current revs
m7_wls pvt ship s-on rh
hboot-1.56.0000
radio-1.00.20.1108
os-4.06.651.4
at this point I'd just like it to boot to android, any help would be greatly appreciated.
Thanks

Lock bootloader and run the latest ruu
Sent from my HTC One using Tapatalk

elvisypi said:
Lock bootloader and run the latest ruu
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks for responding, I think I'ved tried every combination of locked and unlocked bootloaders but hey what have I got to lose at this point.
ran fastboot oem lock
ran latest ruu I could find, RUU_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.04.651.2_Radio_1.00.20.0913_3_NV_SPCS_4.38_003_release_335355_signed_2.exe
I get error [155] unknown error
this worked to flash from viper one then take all the OTA updates to 4.4.2 but now I get this 155 error
I think I have to wait for the 4.4.2 ruu to be released to get back to a fully functioning but I wanted to check around.

You could try this... http://forum.xda-developers.com/showthread.php?t=2634256
[Guide] How to Downgrade from KK to JB S-OFF Required

jstn76rs said:
You could try this... http://forum.xda-developers.com/showthread.php?t=2634256
[Guide] How to Downgrade from KK to JB S-OFF Required
Click to expand...
Click to collapse
yeah I was starting there originally but getting s-off on 1.56 isn't possible yet.

InvaderSkooge said:
yeah I was starting there originally but getting s-off on 1.56 isn't possible yet.
Click to expand...
Click to collapse
AFAIK that's not correct. Try firewater http://firewater-soff.com
Sent from my HTC One using Tapatalk

elvisypi said:
AFAIK that's not correct. Try firewater http://firewater-soff.com
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
looks like firewater requires being able to boot into android and I can't get past the white screen with green HTC letters, I can get into the bootloader and fastboot but can't get further than that.
btw I really do appreciate the comments and suggestions, I feel like I'm just being negative and shooting each one down but I really am trying them as you post them before replying just in case I've missed something.
I can understand the older ruu versions failing as it won't let you downgrade firmwares with s-on but I'd think that some of the posted roms would work. is it possible to extract the boot and recovery from a 4.4.2 upgraded handset for flashing on another?

InvaderSkooge said:
looks like firewater requires being able to boot into android and I can't get past the white screen with green HTC letters, I can get into the bootloader and fastboot but can't get further than that.
Click to expand...
Click to collapse
Reflash the latest TWRP and than flash a 4.4.2 rom, I don't see why it shouldn't work. If you really messed up(flashed some gsm rom or whatever) you'll probably have to wait for the 4.4.2 ruu to come out
Sent from my HTC One using Tapatalk

elvisypi said:
Reflash the latest TWRP and than flash a 4.4.2 rom, I don't see why it shouldn't work. If you really messed up(flashed some gsm rom or whatever) you'll probably have to wait for the 4.4.2 ruu to come out
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
ok I'm an idiot, thanks for bearing with me here, I had tried twrp load again several times, using 2.6.3.3 instead of 2.6.3.0....

InvaderSkooge said:
ok I'm an idiot, thanks for bearing with me here, I had tried twrp load again several times, using 2.6.3.3 instead of 2.6.3.0....
Click to expand...
Click to collapse
There is no twrp 2.6.3.3 for Sprint

[Q] Need trying to get back to complete stock from ViperOneM8

I'm trying to get back to complete stock to grab OTAs for my HTC One m8. I have s-off and I was following the guide here http://venomroms.com/viperonem8_3-0-0-requirements/ and while following the guide and looking for my Main version number and CID Number the MainVer showed up as empty and my CID Number as SPCS_001. The CID does not match anything from here http://forum.xda-developers.com/showthread.php?t=2701376 What should I do next?

Use this guide:
http://forum.xda-developers.com/showthread.php?t=2826343
You'll need the latest RUU which can be found in the first post in the thread linked below. You can use the RUU for software version 3.31.651.2.
http://forum.xda-developers.com/showthread.php?t=2729173

I would also suggest sticking to the Sprint section.
You may do something to your phone that is not for the Sprint variant and really mess up your phone.

Magnum_Enforcer said:
Use this guide:
http://forum.xda-developers.com/showthread.php?t=2826343
You'll need the latest RUU which can be found in the first post in the thread linked below. You can use the RUU for software version 3.31.651.2.
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
Sorry I need more help the guide you sent me to is very confusing however, I understand that I need to use the RUU to go back to stock rom but which stock recovery do I install?

sadway15 said:
Sorry I need more help the guide you sent me to is very confusing however, I understand that I need to use the RUU to go back to stock rom but which stock recovery do I install?
Click to expand...
Click to collapse
Ruu is used through a pc

sadway15 said:
Sorry I need more help the guide you sent me to is very confusing however, I understand that I need to use the RUU to go back to stock rom but which stock recovery do I install?
Click to expand...
Click to collapse
The RUU will install the stock recovery. If you need info on how to run a RUU click the second link in my sig and read the RUU section.

Magnum_Enforcer said:
The RUU will install the stock recovery. If you need info on how to run a RUU click the second link in my sig and read the RUU section.
Click to expand...
Click to collapse
Okay so I think I get it now please confirm, I run the RUU with my PC then once its finished put the stock recovery corresponding to the RUU I installed in the phone then install the stock recovery using TWRP in my phone then I will have a stock htc rom with stock recovery and the phone will update from there.

sadway15 said:
Okay so I think I get it now please confirm, I run the RUU with my PC then once its finished put the stock recovery corresponding to the RUU I installed in the phone then install the stock recovery using TWRP in my phone then I will have a stock htc rom with stock recovery and the phone will update from there.
Click to expand...
Click to collapse
The RUU will put you back to completely stock...only difference is your bootloader will say ***RELOCKED*** instead of ***LOCKED***

BD619 said:
The RUU will put you back to completely stock...only difference is your bootloader will say ***RELOCKED*** instead of ***LOCKED***
Click to expand...
Click to collapse
Complete stock meaning stock rom and stock recovery right? Also what will happen if my bootloader is locked/unlocked?

sadway15 said:
Complete stock meaning stock rom and stock recovery right? Also what will happen if my bootloader is locked/unlocked?
Click to expand...
Click to collapse
Correct.
You will need to re-lock your bootloader to run the RUU if you are s-on, if s-off no need to re-lock.

BD619 said:
Correct.
You will need to re-lock your bootloader to run the RUU if you are s-on, if s-off no need to re-lock.
Click to expand...
Click to collapse
I'm trying to get to stock too but I'm s-on, besides locking the bootloader is there anything else I need to modify?

guissepi said:
I'm trying to get to stock too but I'm s-on, besides locking the bootloader is there anything else I need to modify?
Click to expand...
Click to collapse
No, just relock and run the RUU.

Magnum_Enforcer said:
No, just relock and run the RUU.
Click to expand...
Click to collapse
I tried relocking and when I ran the RUU this was the output:
Code:
./fastboot flash zip rom.zip
target reported max download size of 1830612992 bytes
sending 'zip' (1652270 KB)...
OKAY [ 47.785s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 108.972s

guissepi said:
I tried relocking and when I ran the RUU this was the output:
Code:
./fastboot flash zip rom.zip
target reported max download size of 1830612992 bytes
sending 'zip' (1652270 KB)...
OKAY [ 47.785s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 108.972s
Click to expand...
Click to collapse
Which RUU are you trying to run? Are you on Windows, and why are you trying to fastboot flash it? If you're on Windows simply double-click the RUU to start the installer. It's a exe file, unless you've pulled the ROM zip from the RUU file.
Also, since you've started a separate thread regarding this same issue, I would stick to it to minimize any confusion instead of posting back & forth. Makes it easier to keep up with what's going on

it's the non-hk from htc's page I'm on mac but I pulled the zip from the exe using parallels desktop, I could try doing it on parallels desktop with the windows exe though

bricked One 802W

Hi all,
I've tried to install WWE stock rom on this device, but now is bricked. I can get into fastboot and bootloader, but I can't install anything now. I've tried from fastboot to install the one's dedicated to my device from here:
http://forum.xda-developers.com/showthread.php?t=2617159
device info (before trying to re-install) were:
tampered/unlocked
m7 cdug pvt ship s-on rh
hboot: 2.23.000
radio: u2.05.3501.18
open dsp-v28.120.274.0328
qsc-1237.18.19.0528
os-2.25.1402.1
e-mmc-boot 2048mb
cid/mid: HTCCN703
now CID is gone, but it's still unlocked and S-ON, and
hboot is 2.27.0000
radio u3.08.35.07.17
open dsp-v31.120.274.0617
qsc-1237.25.32.0717
os-2.25.1402.1
eMMC-boot 2048mb
PN0771000
How can I restore it in a way, then to install a WWE version?

ady_uaic said:
Hi all,
I've tried to install WWE stock rom on this device, but now is bricked. I can get into fastboot and bootloader, but I can't install anything now. I've tried from fastboot to install the one's dedicated to my device from here:
http://forum.xda-developers.com/showthread.php?t=2617159
device info (before trying to re-install) were:
tampered/unlocked
m7 cdug pvt ship s-on rh
hboot: 2.23.000
radio: u2.05.3501.18
open dsp-v28.120.274.0328
qsc-1237.18.19.0528
os-2.25.1402.1
e-mmc-boot 2048mb
cid/mid: HTCCN703
now CID is gone, but it's still unlocked and S-ON, and
hboot is 2.27.0000
radio u3.08.35.07.17
open dsp-v31.120.274.0617
qsc-1237.25.32.0717
os-2.25.1402.1
eMMC-boot 2048mb
PN0771000
How can I restore it in a way, then to install a WWE version?
Click to expand...
Click to collapse
post here for windows HTC phone mate, you'll get a quicker response, beside, alot of us here are anti-windows phones lol even if you do just live down the road from me: http://forum.xda-developers.com/htc-8x

Seanie280672 said:
post here for windows HTC phone mate, you'll get a quicker response, beside, alot of us here are anti-windows phones lol even if you do just live down the road from me: http://forum.xda-developers.com/htc-8x
Click to expand...
Click to collapse
I'm not sure I follow you. This is 802W, not windows phone.
The error: remote not allowed.

ady_uaic said:
I'm not sure I follow you. This is 802W, not windows phone.
Click to expand...
Click to collapse
Sorry, your cid related to a windows phone when I googled it, ive never seen those details before, I think you've already found everything to do with the 802w, but i'll have a look around too.

Seanie280672 said:
Sorry, your cid related to a windows phone when I googled it, ive never seen those details before, I think you've already found everything to do with the 802w, but i'll have a look around too.
Click to expand...
Click to collapse
thanks a lot mate!
I think the only thing I need is to flash a stock RUU (doesn't matter which version, as long as it works, then to do again all the processes: unlock bootloader, s-off, custom recovery, root, stock WWE RUU).

ady_uaic said:
thanks a lot mate!
I think the only thing I need is to flash a stock RUU (doesn't matter which version, as long as it works, then to do again all the processes: unlock bootloader, s-off, custom recovery, root, stock WWE RUU).
Click to expand...
Click to collapse
trouble is, your current OS is 2.25.1402.1 and thats an OTA not an RUU, you need a full RUU, this one may work:
PN07IMG_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.30.1402.1_ Radio_1237.25.32.0717_release_332510_signed_2_4.zip http://d-h.st/NAf which is the next full RUU up from yours.

Seanie280672 said:
trouble is, your current OS is 2.25.1402.1 and thats an OTA not an RUU, you need a full RUU, this one may work:
PN07IMG_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.30.1402.1_ Radio_1237.25.32.0717_release_332510_signed_2_4.zip http://d-h.st/NAf which is the next full RUU up from yours.
Click to expand...
Click to collapse
I already tried that mate, thanks!
it returns after signature checking...:
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)

ady_uaic said:
I already tried that mate, thanks!
it returns after signature checking...:
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Click to expand...
Click to collapse
Umm, im a bit confused, its a zip file not an official RUU, im just downloading it to take a closer look, how are you trying to flash it ?
EDIT: ok its an RUU zip, it need to be flashed in fastbootRUU mode, using fastboot commands, bootloader needs to be locked as you are s-on, Its should work as this OTA states that RUU was your next update if you got it via OTA, OTA_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_TO THIS ROM VERSION 2.30.1402.1 --------------------- FROM THIS ROM VERSION-2.25.1402.1 SAME AS YOURS_release_332539.zip - 50.49 MB

Seanie280672 said:
Umm, im a bit confused, its a zip file not an official RUU, im just downloading it to take a closer look, how are you trying to flash it ?
EDIT: ok its an RUU zip, it need to be flashed in fastbootRUU mode, using fastboot commands, bootloader needs to be locked as you are s-on, Its should work as this OTA states that RUU was your next update if you got it via OTA, OTA_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_TO THIS ROM VERSION 2.30.1402.1 --------------------- FROM THIS ROM VERSION-2.25.1402.1 SAME AS YOURS_release_332539.zip - 50.49 MB
Click to expand...
Click to collapse
from fastboot, using the command line:
fastboot flash zip ....zip
I've locked back the bootloader, and still doesn't work:
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
and no, it was an UNICOM version, and my friend tried to update to WWE.

ady_uaic said:
from fastboot, using the command line:
fastboot flash zip ....zip
I've locked back the bootloader, and still doesn't work:
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
and no, it was an UNICOM version, and my friend tried to update to WWE.
Click to expand...
Click to collapse
You cant change to WWE without s-off, tell your friend to leave it alone lol, it requires you to change cid and mid etc first, then flash the corrisponding firmware and then the RUU.
Rename your RUU to rom.zip for ease, then issue these commands :
make sure its this RUU, not the WWE one PN07IMG_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.30.1402.1_ Radio_1237.25.32.0717_release_332510_signed_2_4.zi p
fastboot oem rebootRUU (case sensetive, type it exactly like that)
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
fastboot flash zip Rom.zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately) HTC typo, should be please flash immediately
Make sure device is still in ruu mode(black HTC screen)
now simply reflash the rom.zip, fastboot flash zip Rom.zip
Let it run and it should finish this time, make sure it says successfull at the end, if it does then fastboot reboot, you'll be full stock, if failed, report back here before doing anything else, dont reboot out of RUU mode.
The first flash is just a preupdate, the 2nd flash flashes the rom and firmware files.

Yes mate, I know that. Now I'm trying to put back any ROM then I will do the right procedure to install WWE.
But, now doesn't work at all. not even with that command (and it's not necessary to rename the zip file, as long as it's only one in the adb folder). I already tried that, and it doesn't work .
L.E. oh, wait mate! I think it works now! I'm waiting for the installation to be finished. do you have a good tutorial to upgrade to WWE version?

ady_uaic said:
Yes mate, I know that. Now I'm trying to put back any ROM then I will do the right procedure to install WWE.
But, now doesn't work at all. not even with that command (and it's not necessary to rename the zip file, as long as it's only one in the adb folder). I already tried that, and it doesn't work .
L.E. oh, wait mate! I think it works now! I'm waiting for the installation to be finished. do you have a good tutorial to upgrade to WWE version?
Click to expand...
Click to collapse
Im not really familiar with the dual sim versions, dont know how to s-off them, all the knowlege im giving you is just based on my M7, but to convert you will need to get s-off first, change your cid and mid to match the WWE RUU and then you'll need to flash the WWE full RUU as close to as possible to the version number you have now so that the firmware swap over goes smoothly.

Seanie280672 said:
Im not really familiar with the dual sim versions, dont know how to s-off them, all the knowlege im giving you is just based on my M7, but to convert you will need to get s-off first, change your cid and mid to match the WWE RUU and then you'll need to flash the WWE full RUU as close to as possible to the version number you have now so that the firmware swap over goes smoothly.
Click to expand...
Click to collapse
will do, thanks!

ady_uaic said:
will do, thanks!
Click to expand...
Click to collapse
When the flash has finished, let me know if it boots ok please and was successful.

Seanie280672 said:
When the flash has finished, let me know if it boots ok please and was successful.
Click to expand...
Click to collapse
with the chinese version yes, it boots ok. now I'm trying to use this tutorial for WWE: http://forum.xda-developers.com/showthread.php?t=2559891

ady_uaic said:
with the chinese version yes, it boots ok. now I'm trying to use this tutorial for WWE: http://forum.xda-developers.com/showthread.php?t=2559891
Click to expand...
Click to collapse
just had a quick read through it, I would be cautious flashing HBOOT before getting s-off, if I was you I would use the moonshine s-off method for your HBOOT and device version first before flashing the HBOOT, make sure these have not changed after flashing an updated RUU.
A bad HBOOT flash will hard brick your device.

Seanie280672 said:
just had a quick read through it, I would be cautious flashing HBOOT before getting s-off, if I was you I would use the moonshine s-off method for your HBOOT and device version first before flashing the HBOOT, make sure these have not changed after flashing an updated RUU.
A bad HBOOT flash will hard brick your device.
Click to expand...
Click to collapse
I will have a look right now. what do you mean by device version?

ady_uaic said:
what do you mean by device version?
Click to expand...
Click to collapse
sorry, forget that, they are all for the 802w, threw me out a bit as he labelled the moonshine one as (for the 802w version)
ps, firewater no longer works, its been discontinued, lets hope your not on that HBOOT. :fingers-crossed:

Seanie280672 said:
sorry, forget that, they are all for the 802w, threw me out a bit as he labelled the moonshine one as (for the 802w version)
ps, firewater no longer works, its been discontinued, lets hope your not on that HBOOT. :fingers-crossed:
Click to expand...
Click to collapse
problem solved. now it has wwe. thanks mate!