[GUIDE]RUU related info (Extracting rom.zip, Restoring stock, going back S-ON, etc.)

dididoner

Member
Dec 2, 2014
43
2
0
Pls. see the pictures, this where I always get stuck, since a week. THANKS
Next two pictures show progress when I use the RUU_***.exe file.
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed.exe
MD5sum is ok!
I always get stuck in RUU, pls. anyone help me out here, I do not have any idea.
Maybe I do not have USB-DEBUGGING. ADB cannot find any device!
Can I activate USB-DEBUGGING with fastboot or any other way?
 

Attachments

Last edited:

danilandroid

Member
Nov 30, 2013
42
6
0
It's a common problem I think. I got exactly the same thing. If somebody knows how to solve this please react

Sent from my One M8 using XDA Free mobile app
 

jmcclue

Senior Member
Apr 3, 2012
3,788
1,489
0
Next two pictures show progress when I use the RUU_***.exe file.
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed.exe
MD5sum is ok!
I always get stuck in RUU, pls. anyone help me out here, I do not have any idea.
Maybe I do not have USB-DEBUGGING. ADB cannot find any device!
Can I activate USB-DEBUGGING with fastboot or any other way?
Maybe change ur CID back to what it was before supercid. Then run that ruu. Iv seen @rzr86 tell a few people that and it has worked.
 
  • Like
Reactions: rzr86

dididoner

Member
Dec 2, 2014
43
2
0
I have s-off. When you are s-off the Cid stuff doesn't have to match right?

Sent from my One M8 using XDA Free mobile app
Thats the case with my phone:
(bootloader) cidnum: 11111111
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU

---------- Post added at 07:01 PM ---------- Previous post was at 06:56 PM ----------

http://forum.xda-developers.com/showthread.php?t=1612969
can someone check if this thread could helb me, I have SENSATION XE

---------- Post added at 07:14 PM ---------- Previous post was at 07:01 PM ----------

changing cid won´t work:
------------------------------
C:\htc_acer>fastboot oem writecid htc__102
... INFOStart Verify: -1
INFOerase sector 65504 ~ 65535 (32)
OKAY [ 0.110s]
finished. total time: 0.110s

C:\htc_acer>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 3.300s]
finished. total time: 3.300s

C:\htc_acer>fastboot getvar cid
cid: 11111111
finished. total time: 0.002s
--------------------------------------------------

---------- Post added at 07:38 PM ---------- Previous post was at 07:14 PM ----------

Maybe change ur CID back to what it was before supercid. Then run that ruu. Iv seen @rzr86 tell a few people that and it has worked.
Thanks to you! I changed the cid as you said and flushed my extracted zip file "PG58IMG.zip". Still it got stuck exactly at same 1/3 of the progress-bar as always. I am desperate.

---------- Post added at 07:43 PM ---------- Previous post was at 07:38 PM ----------

Maybe change ur CID back to what it was before supercid. Then run that ruu. Iv seen @rzr86 tell a few people that and it has worked.
changing cid won´t work, but i still tried to flash as you said.
------------------------------
C:\htc_acer>fastboot oem writecid htc__102
... INFOStart Verify: -1
INFOerase sector 65504 ~ 65535 (32)
OKAY [ 0.110s]
finished. total time: 0.110s

C:\htc_acer>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 3.300s]
finished. total time: 3.300s

C:\htc_acer>fastboot getvar cid
cid: 11111111
finished. total time: 0.002s
--------------------------------------------------
 

dididoner

Member
Dec 2, 2014
43
2
0
Hallo, please someone give me advice. I am still totally stuck in RUU - Mode. Probably I have no USB-DEBUGGING.
I can use only fastboot via PC. I am stuck with 4 triangles black htc screen. Boot Mode is RUU.
 

rzr86

Senior Member
May 21, 2012
8,109
2,455
258
35
Nafpaktos
when I flash 4ext recovery, I get that error:
----------------------------
FAILED (command write failed (Bad file descriptor))
------------------------------
did you extract the recovery.img or did you try to flash the zip as it is?
you have to extract the recovery.img from the zip and use only the recovery.img
 

dididoner

Member
Dec 2, 2014
43
2
0
I did extract the recovery.img from the zip folder. Opend Zip file then drag and drop.

---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------

did you extract the recovery.img or did you try to flash the zip as it is?
you have to extract the recovery.img from the zip and use only the recovery.img
I did extract the recovery.img from the zip folder. Opend Zip file then drag and drop.
Thanks for helping me! :)
 

rzr86

Senior Member
May 21, 2012
8,109
2,455
258
35
Nafpaktos
I did extract the recovery.img from the zip folder. Opend Zip file then drag and drop.

---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------



I did extract the recovery.img from the zip folder. Opend Zip file then drag and drop.
Thanks for helping me! :)
did you gave the command right?
 

dididoner

Member
Dec 2, 2014
43
2
0
fastboot accsess only when 4 triangles show up

To explain my functionality of fastboot commands, maybe you should notice this:
When I newly place battery and I plug in the phone via USB Kabel (original htc) I see the black screen with 4 triangles maybe about 5 seconds, then screen turns into that white "hboot-thing" (dont no name for that display).
I can enter fastboot-commands only in these few seconds when I have black screen with 4 triangles. When I miss the moment I have at least to unplug usb for a second and plug in again, so I have "black screen" again for few seconds.
 

Attachments

dididoner

Member
Dec 2, 2014
43
2
0
rename the recovery.img as recovery and try again
When I try to unlock and immediatly flash recovery it got stock in "waiting for device"
-------------------------
[email protected]:~/htc_acer$ fastboot flash unlocktoken Unlock_code.binsending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.159s
[email protected]:~/htc_acer$ fastboot flash recovery recovery< waiting for device >
------------------------------------------------------------------
When I try to lock and immediatly flash recovery ..."not allowed"
-------------------------------------------------------------
[email protected]:~/htc_acer$ fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.006s]
finished. total time: 0.006s
[email protected]:~/htc_acer$ fastboot flash recovery recovery
sending 'recovery' (7216 KB)...
OKAY [ 1.862s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 2.178s
---------------------------------------------------------------
 

rzr86

Senior Member
May 21, 2012
8,109
2,455
258
35
Nafpaktos
When I try to unlock and immediatly flash recovery it got stock in "waiting for device"
-------------------------
[email protected]:~/htc_acer$ fastboot flash unlocktoken Unlock_code.binsending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.159s
[email protected]:~/htc_acer$ fastboot flash recovery recovery< waiting for device >
------------------------------------------------------------------
When I try to lock and immediatly flash recovery ..."not allowed"
-------------------------------------------------------------
[email protected]:~/htc_acer$ fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.006s]
finished. total time: 0.006s
[email protected]:~/htc_acer$ fastboot flash recovery recovery
sending 'recovery' (7216 KB)...
OKAY [ 1.862s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 2.178s
---------------------------------------------------------------

actually rename the recovery.img as recovery
but the command remains the same fastboot flash recovery recovery.img

edit: also unlock the bootloader again
probably the command won't work with locked bootloader