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

[dididoner]

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

when I unlock, It get stuck in waiting for device But unlock wont work, see blow
----------------------------------------------------------
[email protected]:~/htc_acer$ ^C
[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.img< waiting for device >
-------------------------------------------------------------------
then I neeed to unplug, remove the batterie, plug in again, to find device, but then it will not find recovery, due to different name
-----------------------------------------------------------------------------
[email protected]:~/htc_acer$ fastboot flash recovery recovery.img
error: cannot load 'recovery.img': No such file or directory
----------------------------------------------------------------
then i lock the device, but as you can see, device was still locked!
---------------------------------------------------------------
[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.img
error: cannot load 'recovery.img': No such file or directory

[email protected]:~/htc_acer$
--------------------------------------------------------------
1. could it be I got the wrong hboot on the phone, now it says HBOOT-1.29.0000 before update messed everything up it was HBOOT- 1.27* ???
2. Can it be nothing works because USB-DEBUGGING is off ???

 

[jmcclue]

when I unlock, It get stuck in waiting for device But unlock wont work, see blow
----------------------------------------------------------
[email protected]:~/htc_acer$ ^C
[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.img< waiting for device >
-------------------------------------------------------------------
then I neeed to unplug, remove the batterie, plug in again, to find device, but then it will not find recovery, due to different name
-----------------------------------------------------------------------------
[email protected]:~/htc_acer$ fastboot flash recovery recovery.img
error: cannot load 'recovery.img': No such file or directory
----------------------------------------------------------------
then i lock the device, but as you can see, device was still locked!
---------------------------------------------------------------
[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.img
error: cannot load 'recovery.img': No such file or directory

[email protected]:~/htc_acer$
--------------------------------------------------------------
1. could it be I got the wrong hboot on the phone, now it says HBOOT-1.29.0000 before update messed everything up it was HBOOT- 1.27* ???
2. Can it be nothing works because USB-DEBUGGING is off ???

And again.. ur phone is in ruu mode, all u can do is flash the correct ruu for ur device. If ur phone is "carrier" unlock then flash a wwe or europe ruu for ur device.

 

[dididoner]

And again.. ur phone is in ruu mode, all u can do is flash the correct ruu for ur device. If ur phone is "carrier" unlock then flash a wwe or europe ruu for ur device.

Thanks again, but sorry Sir but what is carrier, and what a wwe or europe ruu ?
I tried many different ruu, all starting RUU_PYRAMID_LE_***** . What could be the problem?
And how can I unlock via fastboot? The only way I know is this and it wont work: fastboot flash unlocktoken Unlock_code.binsending 'unlocktoken'
-------------------------------------------------
[email protected]:~/htc_acer$ fastboot flash unlocktoken Unlock_code.binsending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
-------------------------------------------
But the start-screen where I stuck still says: ***LOCKED***
-----------------------------------
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
RADIO-11.22.3504.07_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34

RUU
--------------------------------------
CID: (bootloader) cidnum: 11111111
--------------------------------

 

[rzr86]

Thanks again, but sorry Sir but what is carrier, and what a wwe or europe ruu ?
I tried many different ruu, all starting RUU_PYRAMID_LE_***** . What could be the problem?
And how can I unlock via fastboot? The only way I know is this and it wont work: fastboot flash unlocktoken Unlock_code.binsending 'unlocktoken'
-------------------------------------------------
[email protected]:~/htc_acer$ fastboot flash unlocktoken Unlock_code.binsending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
-------------------------------------------
But the start-screen where I stuck still says: ***LOCKED***
-----------------------------------
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
RADIO-11.22.3504.07_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34

RUU
--------------------------------------
CID: (bootloader) cidnum: 11111111
--------------------------------

when you connect the device to pc you have to choose from bootloader screen fastboot
did you do that?
or does it directly prompts you to the ruu mode when connecting it to pc?
if yes use 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)

 

[dididoner]

when you connect the device to pc you have to choose from bootloader screen fastboot
did you do that?
or does it directly prompts you to the ruu mode when connecting it to pc?
if yes use 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)

It dirctly promts me to ruu mode. I have no selection what so ever to make.

 

[dididoner]

It dirctly promts me to ruu mode. I have no selection what so ever to make.

ADB cant find my device, only fastboot can find device, I believe I USB-DEBUGGING is off!
C:\htc_acer\Firmware 3.33 Universal\ADB_Fastboot_Windows\ADB_Fastboot_Windows>ad
b reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

C:\htc_acer\Firmware 3.33 Universal\ADB_Fastboot_Windows\ADB_Fastboot_Windows>ad
b devices
List of devices attached

C:\htc_acer\Firmware 3.33 Universal\ADB_Fastboot_Windows\ADB_Fastboot_Windows>ad
b reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

 

[dididoner]

It dirctly promts me to ruu mode. I have no selection what so ever to make.

Yeah, after one week I got a different display, THANKS TO YOU MY FRIEND!!!
What I did was:
C:\>fastboot erase cache
C:\>fastboot oem rebootRUU
C:\>fastboot flash zip PG58IMG.zip (the link you gave me 3.33*)
blablabla
OKAY [ 37.146s]
finished. total time: 40.108s
C:\>reboot
<waiting for device>
But now I am stuck, I see only the white screen wíth recovery and everything, but I cant do anything with it
And fastboot via PC ist not working anymore!!!
See pictures
1. When I start the phone just with power button, phone gets stuck with htc logo.
2. When I start with power and volume down button it gets stuck with white screen...see picture
3. When I select recovery the phone loops between "htc-logo-display" and "black screen with green-circulating-arrow+arrow-down-display"...last picture
4. When I remove battery, place it again, plug in to PC, phone loops also between "black screen with green-circulating-arrow+arrow-down-display"...last picture

 

[rzr86]

Yeah, after one week I got a different display, THANKS TO YOU MY FRIEND!!!
What I did was:
C:\>fastboot erase cache
C:\>fastboot oem rebootRUU
C:\>fastboot flash zip PG58IMG.zip (the link you gave me 3.33*)
blablabla
OKAY [ 37.146s]
finished. total time: 40.108s
C:\>reboot
<waiting for device>
But now I am stuck, I see only the white screen wíth recovery and everything, but I cant do anything with it
And fastboot via PC ist not working anymore!!!
See pictures
1. When I start the phone just with power button, phone gets stuck with htc logo.
2. When I start with power and volume down button it gets stuck with white screen...see picture
3. When I select recovery the phone loops between "htc-logo-display" and "black screen with green-circulating-arrow+arrow-down-display"...last picture
4. When I remove battery, place it again, plug in to PC, phone loops also between "black screen with green-circulating-arrow+arrow-down-display"...last picture

actually you could flash 3.33 universal directly from bootloader without using the pc at all
bootloader would scan for it and detect it for update

nevermind now do this
connect the device to pc and select fastboot
then try with fastboot devices command

 

[dididoner]

actually you could flash 3.33 universal directly from bootloader without using the pc at all
bootloader would scan for it and detect it for update

nevermind now do this
connect the device to pc and select fastboot
then try with fastboot devices command

I am so glad. I put 3.33 directly on sd, via another phone. Then bootloader detected itself 3.33 zip, made update complete.
I had to reboot, now it stucks always on white screen with green htc-logo
I removed the zip from SD, started again, but device stucks still on white screen.
Then I put 4ext-recovery on SD card and flushed it. 4ext recovery is booting now, but no Rom. In Recovery mode I have ADB access, and in bootmode fastboot access!!.
I have only CWM (not sure...dated 1980) and Titanium backups on SD card, how can I go back to my system now?
Nevertheless, I am very happy already, and hoping for another advice from you, how can I start a Rom now, dont want to mess it up again? I wiped dalvic and cache, didnt help. Really...Thank you so [email protected]:~/htc_acer$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) serialno: SH1BJV801896
(bootloader) imei: 355195000000010
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813001
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3948mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

 

[dididoner]

actually you could flash 3.33 universal directly from bootloader without using the pc at all
bootloader would scan for it and detect it for update

nevermind now do this
connect the device to pc and select fastboot
then try with fastboot devices command

Please my savior, could you help me out ...see my reply... Thanks once more

 

[rzr86]

Please my savior, could you help me out ...see my reply... Thanks once more

actually use the recovery.img i gave you via fastboot command if you want to use newest custom roms
it is the latest version of 4ext recovery
then try vipers 5.3.0 rom
it is a jelly bean rom with sense

 

[dididoner]

actually use the recovery.img i gave you via fastboot command if you want to use newest custom roms
it is the latest version of 4ext recovery
then try vipers 5.3.0 rom
it is a jelly bean rom with sense

Thank you so much again. I flashed 4EXT_Recovery_Touch_v1.0.0.6_RC3, it works perfectly.
Then I tried vipers 5.3.0; md5sum ok, wiped, flashed everything except SD card.
Everything seemed to go alright, but then:
E: Error in /sdcard/****name of rom
(Status 0)
Installation aborted
What can I do ?

 

[rzr86]

Thank you so much again. I flashed 4EXT_Recovery_Touch_v1.0.0.6_RC3, it works perfectly.
Then I tried vipers 5.3.0; md5sum ok, wiped, flashed everything except SD card.
Everything seemed to go alright, but then:
E: Error in /sdcard/****name of rom
(Status 0)
Installation aborted
What can I do ?

remove and reinsert the sdcard
then try again with flashing the rom

 

[dididoner]

remove and reinsert the sdcard
then try again with flashing the rom

First I formated SD card via 4ext, here I had same error then before (E: Error in /sdcard/****name of rom)
Then I reinsertet SD card as you said, installation stucked at 19,75%, tried it several times, with wiping, formating and so on. And now again I have always E: Error in /sdcard/****name of rom
1. What would be the right format for sd card?
2. How can I proceed now?

 

[rzr86]

First I formated SD card via 4ext, here I had same error then before (E: Error in /sdcard/****name of rom)
Then I reinsertet SD card as you said, installation stucked at 19,75%, tried it several times, with wiping, formating and so on. And now again I have always E: Error in /sdcard/****name of rom
1. What would be the right format for sd card?
2. How can I proceed now?

try to format the sdcard from pc
or use a different one if you have

also try this stock rom from 4ext
http://www.4shared.com/zip/ZYXJl3OSce/Stock_333401153_De-odexed.html

it is a flashable zip that can be used from 4et recovery

 

[dididoner]

try to format the sdcard from pc
or use a different one if you have

also try this stock rom from 4ext
http://www.4shared.com/zip/ZYXJl3OSce/Stock_333401153_De-odexed.html

it is a flashable zip that can be used from 4et recovery

Sorry Sir, I formated extern sdcard via pc, enabled smart flash on 4ext and installed twice, now, 4ext shows Current Rom: ViperS 5.3.0, but when restart it stucks a while in green htc logo, then autmatically 4ext boots again ??? Looking forward for another idea...really want to install viper... Thanks again

 

[rzr86]

Sorry Sir, I formated extern sdcard via pc, enabled smart flash on 4ext and installed twice, now, 4ext shows Current Rom: ViperS 5.3.0, but when restart it stucks a while in green htc logo, then autmatically 4ext boots again ??? Looking forward for another idea...really want to install viper... Thanks again

you are on S-OFF
do not enable smartflash you don't need it

now format all partitions except sdcard from 4ext
flash the rom again
see how it goes

 

[dididoner]

you are on S-OFF
do not enable smartflash you don't need it

now format all partitions except sdcard from 4ext
flash the rom again
see how it goes

I disabled smart flash formated all partitions except sdcard...
...at first try it got stuck at about 19% (no full wipe while installation)
...at second try again the error: E: Error in /sdcard/Viper...zip (with fullwipe while installation)

 

[rzr86]

I disabled smart flash formated all partitions except sdcard...
...at first try it got stuck at about 19% (no full wipe while installation)
...at second try again the error: E: Error in /sdcard/Viper...zip (with fullwipe while installation)

i don't know man
try with the flashable stock rom
see if you have any issues with that

 

[dididoner]

i don't know man
try with the flashable stock rom
see if you have any issues with that

:crying: Sorry! the flashable stock rom starts installation and it says sucessfully finished pls. reboot. But installation went in incredible short time.
4ext info says: Rom unknown and Rom booting impossible, stuck at green htc logo.
When I start 4ext it always say:
"The revovery hasnt been configured!
Use 4EXT Recovery Control or the free app...blabla...and to unlock configurable features.
Hint: check out recovery settings"

Could it be this has something to do with my problem?