M7_WLS PVT SHIP S-OFF RH
CID-11111111
HABOOT-1.44.0000
RADIO-1.00.20.0626
OpenDSP-v31.120.274.0617
eMMC-boot
May 8 2013,16:30:08:-1
I have no OS I was trying to run the RUU APPLICATION and I would get stuck in sending ...But when I try to flash via Fastboot
I get FAILED Remote :24 parsing android-info failed..now I have relocked bootloader.
no custom recover and no OS!
DarkLight1 said:
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HABOOT-1.44.0000
RADIO-1.00.20.0626
OpenDSP-v31.120.274.0617
eMMC-boot
May 8 2013,16:30:08:-1
I have no OS I was trying to run the RUU APPLICATION and I would get stuck in sending ...But when I try to flash via Fastboot
I get FAILED Remote :24 parsing android-info failed..now I have relocked bootloader.
no custom recover and no OS!
Click to expand...
Click to collapse
Found a solution ? I'm afraid ti be in the same case
Any chance you can unlock with your old unlock file?
OTA file (RUU) cannot be installed via the bootloader. it must be installed by the correct stock recovery. Your S-Off so should be pretty easy to fix, Try unlocking your bootloader. Check this out this may be helpful! http://www.htc1guru.com/downloads/stock-rom-downloads/
InsertCoin Flash not working
ryoung4316 said:
OTA file (RUU) cannot be installed via the bootloader. it must be installed by the correct stock recovery. Your S-Off so should be pretty easy to fix, Try unlocking your bootloader. Check this out this may be helpful!
Click to expand...
Click to collapse
I'm trying to fastboot flash InsertCoin Sense 6 ROM but I'm getting the same 'remote : 24 parsing android-info fail error'
Not an OTA, anyone know why i'm running into this issue? My bootloader is unlocked.
rr3mix said:
I'm trying to fastboot flash InsertCoin Sense 6 ROM but I'm getting the same 'remote : 24 parsing android-info fail error'
Not an OTA, anyone know why i'm running into this issue? My bootloader is unlocked.
Click to expand...
Click to collapse
insert coin is a custom rom, you flash it via recovery(twrp)not fastboot.make sure the version of insertcoin is sprint compatable, sense 6 is not yet.
Aldo101t said:
insert coin is a custom rom, you flash it via recovery(twrp)not fastboot.make sure the version of insertcoin is sprint compatable, sense 6 is not yet.
Click to expand...
Click to collapse
You can't flash custom roms through bootloader?
1. Is there a stock ROM I can find for HTC M8 (AT&T)?
2. Is there a way to flash TWRP onto my phone? I can't seem to load it up anymore.
rr3mix said:
You can't flash custom roms through bootloader?
1. Is there a stock ROM I can find for HTC M8 (AT&T)?
2. Is there a way to flash TWRP onto my phone? I can't seem to load it up anymore.
Click to expand...
Click to collapse
... answer of your 1st question cant be found here. this is m7 forum not m8
2nd if you are talking about m7, sure you can flash twrp via fastboot if you have already unlocked the bootloader ...
Would appreciate some advice before I move forward ....
I was running ViperOne 4.2.0 happily, albeit on a very old firmware version.
However on trying to flash a current firmware it failed with "FAILED (status read failed (too many links))" which left me stuck with the silver HTC on a black screen with the 4 warning triangles in each corner.
I then downloaded and flashed this: "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed" which got me back up and running ......
However, my current bootloader info is:
*** RELOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.13.3231.27
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 7 2013,20:01:03:-1
What steps do I need to take to get back to root, with custom recovery, latest firmware and be able to flash ViperOne again?
channelsurfer99 said:
Would appreciate some advice before I move forward ....
I was running ViperOne 4.2.0 happily, albeit on a very old firmware version.
However on trying to flash a current firmware it failed with "FAILED (status read failed (too many links))" which left me stuck with the silver HTC on a black screen with the 4 warning triangles in each corner.
I then downloaded and flashed this: "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed" which got me back up and running ......
However, my current bootloader info is:
*** RELOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4A.13.3231.27
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 7 2013,20:01:03:-1
What steps do I need to take to get back to root, with custom recovery, latest firmware and be able to flash ViperOne again?
Click to expand...
Click to collapse
So you've done an RUU , and it got stuck in the RUU screen?
Try "fastboot oem restart*
Then boot intro bootloader.
Download CMW/TWRP
then flash the recovery
Turn Adb-sideload on in recovery, use adb sideload to install ViperRom again.
Unlock using "revone -u"
Sent from my HTC One using Tapatalk
Gixy said:
So you've done an RUU , and it got stuck in the RUU screen?
Try "fastboot oem restart*
Then boot intro bootloader.
Download CMW/TWRP
then flash the recovery
Turn Adb-sideload on in recovery, use adb sideload to install ViperRom again.
Click to expand...
Click to collapse
No, the RUU finshed fine and it rebooted back into the stock ROM with stock recovery, however when I try to flash recovery (twrp 2.6.3.3) it fails with:
"FAILED (remote: not allowed)"
Is this due to the bootloader being "Relocked"? If so, any idea how to Unlock it again .... I used HTC Dev to initially unlock it way back when and rumrunners to get S-OFF
Thanks for the help!
You can do what nkk71 has suggested or unlock using htcdev by generating a new unlock key.
nkk71 said:
Unlock using "revone -u"
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
nkk, as I didn't use Revone to get S-OFF, would that still be a valid way of getting back to Unlocked, do you think?
Unlock using HTC dev? revone is for 1.44 hboot
SaHiLzZ said:
Unlock using HTC dev? revone is for 1.44 hboot
Click to expand...
Click to collapse
SuperCID, dont think that HTCdev has an unlock token for that
---------- Post added at 11:26 PM ---------- Previous post was at 11:24 PM ----------
channelsurfer99 said:
nkk, as I didn't use Revone to get S-OFF, would that still be a valid way of getting back to Unlocked, do you think?
Click to expand...
Click to collapse
revone -u
has nothing to do with s-off, it's just unlocking using; eg: http://forum.xda-developers.com/showthread.php?t=2475914
He ran the RUU zip. that assumes that phone is not rooted anymore.
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser. use the keep bootloader locked directions)
Click to expand...
Click to collapse
revone has m/'
Revone had m/c exploit!
Sent from my HTC One using Tapatalk
---------- Post added at 12:08 AM ---------- Previous post was at 12:08 AM ----------
nkk71 said:
revone has
Revone had m/c exploit!
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk
channelsurfer99 said:
No, the RUU finshed fine and it rebooted back into the stock ROM with stock recovery, however when I try to flash recovery (twrp 2.6.3.3) it fails with:
"FAILED (remote: not allowed)"
Is this due to the bootloader being "Relocked"? If so, any idea how to Unlock it again .... I used HTC Dev to initially unlock it way back when and rumrunners to get S-OFF
Thanks for the help!
Click to expand...
Click to collapse
When you run an RUU, i assume your bootloader has been locked, so if RUU is succesfull, your bootloader is currently locked/relocked.
Go to the HTC dev email you´ve received with the Unlock_code.bin . but this in your folder with adb & fastboot. Go into fastboot mode, and execute : ¨fastboot flash unlocktoken Unlock_code.bin¨
If you havn´t got this email anymore, go to the htcdev website and request your unlock code again as you did unlocking.
Then install TWRP/CMW, flash youŕe preffered rom
EDIT: Just read the other posts, use revone as
nkk71 suggested. Otherwise read up on the revone thread :
http://forum.xda-developers.com/showthread.php?t=2314582
As suggested, I used my original HTC Dev token to successfully unlock the bootloader from it's "Relocked" state.
Then I was able to flash TWRP and reflash ViperOne ... So I'm back to where I started from thankfully!
The only problem I'm having is getting the right PC drivers installed to connect the phone to transfer files ...... That's going to have to wait until tomorrow now as it's late here!
Thanks to everyone for the help and advice
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!