Hello ,
Today I want test new rom but I get error in TWRP recovery can't mount system cache data I tried other recovery (4ext) same problem , wipe data system .... not succeed
I tried to flush a RUU (I flush this RUU version always in my phone with succeed ) after relock bootload S-ON I stuck in 39% I think it's stop in dzdata
know my phone stuck in black screen and HTC logo with 4 triangles in corner
Hboot just have RUU in yellow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
Thank for help .
popo020 said:
Hello ,
Today I want test new rom but I get error in TWRP recovery can't mount system cache data I tried other recovery (4ext) same problem , wipe data system .... not succeed
I tried to flush a RUU (I flush this RUU version always in my phone with succeed ) after relock bootload S-ON I stuck in 39% I think it's stop in dzdata
know my phone stuck in black screen and HTC logo with 4 triangles in corner
Hboot just have RUU in yellow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
Thank for help .
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
Thank you for reply
but I have different problem in Hboot I don't have any option like fastboot/recovery/rest ...
I have only RUU with yellow color like in this image
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg
please help
popo020 said:
Thank you for reply
but I have different problem in Hboot I don't have any option like fastboot/recovery/rest ...
I have only RUU with yellow color like in this image
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg
please help
Click to expand...
Click to collapse
post it again
i can't see it
but i think you have stuck in ruu mode
This what I have in my HBOOT
=================================
*** RELOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
RUU
=================================
like in this picture
#remove space from link
Code:
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg
If I want flash anything by fastboot i get
Code:
FAILED (remote: 12 signature verify fail)
popo020 said:
If I want flash anything by fastboot i get
Code:
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
since you are relocked you are limited to fastboot commands
try this one
fastboot reboot bootloader
edit: by the way did you use any wipe option from TWRP ?
rzr86 said:
since you are relocked you are limited to fastboot commands
try this one
fastboot reboot bootloader
edit: by the way did you use any wipe option from TWRP ?
Click to expand...
Click to collapse
yep this is it start with this problem I use wipe from TWRP but didn't work so I decide go back to stock RUU and have this problem
Code:
fastboot reboot bootloader
back to same black screen with htc logo and 4 triangle
popo020 said:
yep this is it start with this problem I use wipe from TWRP but didn't work so I decide go back to stock RUU and have this problem
Code:
fastboot reboot bootloader
back to same black screen with htc logo and 4 triangle
Click to expand...
Click to collapse
you shouldn't use any wipe option from twrp
your system and data partitoin are corrupted probably
also you are stuck in ruu mode
try to flash the ruu manually
see how it goes
otherwise your only option is the thread i gave you in my previous post
Thank you again
but Bootloader can't find PG58IMG.zip in my SD card how can I flash the RUU manually
phone stuck in 39% when start system flashing
popo020 said:
Thank you again
but Bootloader can't find PG58IMG.zip in my SD card how can I flash the RUU manually
phone stuck in 39% when start system flashing
Click to expand...
Click to collapse
try with fastboot flash zip pg58img.zip
rzr86 said:
try with fastboot flash zip pg58img.zip
Click to expand...
Click to collapse
I got this error :crying:
Code:
FAILED (remote: 12 signature verify fail)
any help bro ?
At first you said you have relocked your bootloader in order to flash the RUU.You have not S-OFF so you are forbidden to use the recovery right now and probably you are stuck in RUU mode.
As long as you have "relocked" status you could unlock your bootloader again by using the command
Code:
fastboot oem unlock
or by flashing the Unlock_code.bin again
Code:
fastboot flash unlocktoken Unlock_code.bin
After those steps you should have access to bootloader again and you should be able to use recovery to correct (the possibly corrupted) partitions by using the guide that gave you rzr86.
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
It's a painful proccess but it is the only solution I can think right now.
---------- Post added at 03:53 AM ---------- Previous post was at 03:35 AM ----------
You could also check this guide out how to reformat a partition from recovery.(This guide is for HTC One and the /data partition number is probably not the same with the sensation /data partition number but I think it's a good start to read this solution)
---------- Post added at 04:06 AM ---------- Previous post was at 03:53 AM ----------
If you have access to recovery you can use adb shell to give the command
Code:
cat /proc/emmc
so you can see the numbers for every partition in your device.
You can also check this guide out.
for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work
popo020 said:
for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work
Click to expand...
Click to collapse
The first command doesn't always work but the unlocktoken should unlock your bootloader again.
If you use the command
Code:
fastboot reboot bootloader
after the flash of unlocktoken you should be able to see the bootloader on the next reboot.(If you can't just try to remove the battery for some time ,put it back in and press (power) + (vol-) to get the phone in bootloader mode.
Adb commands doesn't work on fastboot or RUU modes.You can only use adb by using a recovery with that capability or with a working rom.
Anyway...If nothing of them can help you you could try (by relocking your bootloader at first) to flash an extracted system.img from an RUU by using fastboot
Code:
fastboot flash system system.img
You should better try to erase data and cache partitions before you reboot and see if you have a working ROM.
Code:
fastboot erase userdata
fastboot erase cache
fastboot reboot
Thank you for reply , I have only the tow screens displayed exactly like the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And [VOL -] +[ POWER BUT ] give the black screen
I think unlocktoken need ROM installed for choosing between unlock or not
and all flash commands failed
Code:
FAILED (remote: 12 signature verify fail)
:crying:
popo020 said:
for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work
Click to expand...
Click to collapse
popo020 said:
Thank you for reply , I have only the tow screens displayed exactly like the image
And [VOL -] +[ POWER BUT ] give the black screen
I think unlocktoken need ROM installed for choosing between unlock or not
and all flash commands failed
Code:
FAILED (remote: 12 signature verify fail)
:crying:
Click to expand...
Click to collapse
As I saw in your first post here you are saying you have hboot 1.27 (probably from a command you gave in RUU mode)
Code:
fastboot getvar all
Now as I can see in the image your bootloader status seems to be 0.85 for the model ACE (HTC DESIRE HD).If this is an enginering HBOOT and you reverted to S-ON you probably breaked your device.I just don't get it!
HTC Desire HD HBOOT
HTC Sensation HBOOT
The sensation phones are PYRAMID models!
If it has to do with wrong flash you could try this guide.
But before you try anything give the command
Code:
fastboot getvar all
one more time and copy-paste everything here.
the image not from my phone I found it in the net , just to show you what look like
This what I have in my HBOOT
=================================
*** RELOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
RUU
=================================
and getVar All
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3930mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
If you cannot unlock your device from relocked status and you cannot flash anything to it I don't think I can help you further.You can always use varius tools like riffbox to repartition emmc chip or maybe to s-off your device (Too).
Are you apsolutely sure you tried to flash a signed system.img with relocked bootloader and it didn't flash??
Related
hi every one
i was trying to match the RIL/basebande versions
i tried to flash some radio files and i dont know what it happend (i really forget what i did exactlly)
sudenlly i pressed the hard reset in the hboot (yes i remember i did this)
after that i tried to reflash a radio file via fastboot
i notices that in my hboot it's writen like this
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
now when i try to flash PG58IMG (radio) it says fail-PU
i thaught that i'm still s-on because that pink LOCKED which written above (even it's written s-off under it !!!!!!!!)
okay i was able to change between hboot version by just flashing the hboot zip file and that's all so i tried to do that like i was
now when i try to flash the hboot (PG58IMG) it says alsi fail-PU
and now i'm stuck into this screen
here is my getvar resault if some one could help me
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 9.99.999.999
(bootloader) serialno: (removed by me because it's not important)
(bootloader) imei: (removed by me because it's not important)
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.509s
specter16 said:
hi every one
i was trying to match the RIL/basebande versions
i tried to flash some radio files and i dont know what it happend (i really forget what i did exactlly)
sudenlly i pressed the hard reset in the hboot (yes i remember i did this)
after that i tried to reflash a radio file via fastboot
i notices that in my hboot it's writen like this
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
now when i try to flash PG58IMG (radio) it says fail-PU
i thaught that i'm still s-on because that pink LOCKED which written above (even it's written s-off under it !!!!!!!!)
okay i was able to change between hboot version by just flashing the hboot zip file and that's all so i tried to do that like i was
now when i try to flash the hboot (PG58IMG) it says alsi fail-PU
and now i'm stuck into this screen
here is my getvar resault if some one could help me
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 9.99.999.999
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.509s
Click to expand...
Click to collapse
As long as you have access to the boot loader and/or fastboot, you're not bricked. You can technically flash Universal firmware and a recovery to get around this but you might want to flash an RUU as it'll boot you into a ROM and give you a working setup to play with.
Since you're S-OFF download and flash an RUU via fastboot, upgrade or downgrade; it makes very little difference as it will put you in a position to flash a recovery and or universal firmware.
A note on RIL/Basebands, 3.32 and 3.33 have no adverse effects of using a non matching RIL baseband so long as your WiFi and mobile network works, you should be good.
P.S: remove your SN & IMEI from your post
Sent from my HTC
DennisBold said:
As long as you have access to the boot loader and/or fastboot, you're not bricked. You can technically flash Universal firmware and a recovery to get around this but you might want to flash an RUU as it'll boot you into a ROM and give you a working setup to play with.
Since you're S-OFF download and flash an RUU via fastboot, upgrade or downgrade; it makes very little difference as it will put you in a position to flash a recovery and or universal firmware.
A note on RIL/Basebands, 3.32 and 3.33 have no adverse effects of using a non matching RIL baseband so long as your WiFi and mobile network works, you should be good.
P.S: remove your SN & IMEI from your post
Sent from my HTC
Click to expand...
Click to collapse
i tried an RUU and it says error 171 usb connection error !
i'm in fastboot and i can see my device connected using the fastboot devices commande
by the way this problem happed while i'm trying to get my wifi working
any way now i'm trying to get my device booting
specter16 said:
i tried an RUU and it says error 171 usb connection error !
i'm in fastboot and i can see my device connected using the fastboot devices commande
by the way this problem happed while i'm trying to get my wifi working
any way now i'm trying to get my device booting
Click to expand...
Click to collapse
I skimmed over your other thread, and you probably should have tried a kernel with BCM drivers if you haven't already.
Try with a different (and known to work) USB.
Also, make sure HTC Sync is closed and that you run the RUU as administrator.
Sent from my HTC
DennisBold said:
I skimmed over your other thread, and you probably should have tried a kernel with BCM drivers if you haven't already.
Try with a different (and known to work) USB.
Also, make sure HTC Sync is closed and that you run the RUU as administrator.
Sent from my HTC
Click to expand...
Click to collapse
i tried Sultan kernel with BCM driver and it didn't work (wifi turning on................................)
any way this is not my current prb now
one other thing
when i try this commande fastboot oem rebootRUU
here is what it says
Code:
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.235s]
finished. total time: 0.257s
and RUU is still not working
specter16 said:
i tried Sultan kernel with BCM driver and it didn't work (wifi turning on................................)
any way this is not my current prb now
one other thing
when i try this commande fastboot oem rebootRUU
here is what it says
Code:
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.235s]
finished. total time: 0.257s
and RUU is still not working
Click to expand...
Click to collapse
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
DennisBold said:
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
Click to expand...
Click to collapse
okay i'll try
please stay connected, i really need you
specter16 said:
okay i'll try
please stay connected, i really need you
Click to expand...
Click to collapse
Sure. If the fastboot commands work I've got something you can try.
Sent from my HTC
DennisBold said:
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
Click to expand...
Click to collapse
not working !!!
fastboot erase recovery gives me this
Code:
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s
specter16 said:
not working !!!
fastboot erase recovery gives me this
Code:
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s
Click to expand...
Click to collapse
You are S-OFF?
Try:
fastboot oem unlock
Else move the universal firmware file into the folder with fastboot and type:
fastboot flash zip <zip name>.zip
Sent from my HTC
DennisBold said:
You are S-OFF?
Try:
fastboot oem unlock
Else move the universal firmware file into the folder with fastboot and type:
fastboot flash zip <zip name>.zip
Sent from my HTC
Click to expand...
Click to collapse
not working
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
specter16 said:
not working
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
Sorry, always getting commands mixed up.
Try:
fastboot update PG58IMG.zip
Sent from my HTC
DennisBold said:
Sorry, always getting commands mixed up.
Try:
fastboot update PG58IMG.zip
Sent from my HTC
Click to expand...
Click to collapse
archive does not contain 'boot.img'
error: update package missing boot.img
are you sure that i'm s-off my friend ??? because it's written in the hboot above with pink
*** LOCKED ***
but under this line it's written S-OFF with green
specter16 said:
archive does not contain 'boot.img'
error: update package missing boot.img
are you sure that i'm s-off my friend ??? because it's written in the hboot above with pink
*** LOCKED ***
but under this line it's written S-OFF with green
Click to expand...
Click to collapse
You're S-OFF, however your bootloader is locked. Meaning commands are locked, S-OFF disables security allowing you to flash things without being signed by HTC.
Could you try this:
fastboot erase cache
fastboot oem rebootRUU (if you get SDcard errors, take out your SDCard and try again)
fastboot flash zip PG58IMG.zip
fastboot reboot-bootloader
Sent from my HTC
DennisBold said:
You're S-OFF, however your bootloader is locked. Meaning commands are locked, S-OFF disables security allowing you to flash things without being signed by HTC.
Could you try this:
fastboot erase cache
fastboot oem rebootRUU (if you get SDcard errors, take out your SDCard and try again)
fastboot flash zip PG58IMG.zip
fastboot reboot-bootloader
Sent from my HTC
Click to expand...
Click to collapse
fastboot erase cache
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.024s
fastboot oem rebootRUU
SD card errors and the device reboot into hboot
specter16 said:
fastboot erase cache
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.024s
fastboot oem rebootRUU
SD card errors and the device reboot into hboot
Click to expand...
Click to collapse
Tried removing your SD-Card? And have you checked the SDCard still works?
Sent from my HTC
DennisBold said:
Tried removing your SD-Card? And have you checked the SDCard still works?
Sent from my HTC
Click to expand...
Click to collapse
nothing is inserted on my phone (SIM / SD)
and my sd card is working fine on my pc
omg what i did :s:s:s
specter16 said:
nothing is inserted on my phone (SIM / SD)
and my sd card is working fine on my pc
omg what i did :s:s:s
Click to expand...
Click to collapse
That's odd. Insert your SDCard after formatting it and placing the PG58IMG.zip on it. Then reboot into bootloader. See if it works, and let me know.
Sent from my HTC
Fail-PU errors generally correspond to firmware corruption
Which is pretty hard to solve
If Op can exactly tell flashing what caused this issue
Maybe we can have a chance
Btw can the phone go to recovery?
Also how did the patched hboot flash went?
Sent from my HTC Sensation 4G using xda premium
DennisBold said:
That's odd. Insert your SDCard after formatting it and placing the PG58IMG.zip on it. Then reboot into bootloader. See if it works, and let me know.
Sent from my HTC
Click to expand...
Click to collapse
- Fail-PU next to the bootloader line
i found this command
Code:
fastboot oem writesecureflag 3
i think this will return me back to s-on
but can i s-off my phone from hboot ??? if i want
or it's useless this command for me ?
Hi, was advised to post here instead as my phone is in fact the HTC One S Model PJ40110.
The issue with the phone is that upon pressing the power button, the phone vibrates, the HTC logo comes on and after about 20 seconds just shuts off. I need to recover some data first, the data from the internal memory not the sd card.
The phone is S-ON
I can get into the hboot menus but not sure on how to proceed to be able to recover the data.
Fixing this for a friend, i dont believe she is capable of rooting.. etc not sure how the phone ended up this way.
Appreciate your guidance
Not sure why you want "the data from the internal memory not the sd card"
You could unlock the bootloader and flash a custom recovery and mount usb storage to copy the pictures and media.
For S4 version of HtC One S
http://forum.xda-developers.com/showthread.php?t=1583427
After that you can run a RUU.exe to return to stock.
You will have to relock the bootloader
fastboot oem lock
Run the RUU when the phone is in bootloader.
http://www.androidruu.com/index.php?developer=Ville
Hi and thanks for the reply.
Basically I want to recover the contacts and any other personal data that was not on the sd card.
Will it be possible with this method or will it just bring the phone to life but wipe the data?
exclusivebiz said:
Hi and thanks for the reply.
Basically I want to recover the contacts and any other personal data that was not on the sd card.
Will it be possible with this method or will it just bring the phone to life but wipe the data?
Click to expand...
Click to collapse
Yes, you are right. When you unlock the bootloader and press "yes" I believe it wipes your phone. Sorry, wasn't thinking about that.
Sorry, couldn't help. There may be some adb commands, to pull the data, but I don't know them.
Contacts would be saved via google though. So not to worry about that.
Is it possible to boot into recovery? Then you could use adb.
I could boot into hboot. Are you referring to that as recovery mode? would you have any steps on using adb for recovering data?
Im not well versed yet with the backend of the android platform.
Some more details on the phone
*** locked ***
vle pvt ship s-on rl
hboot-2.15.0000
radio-1.11.50.05.28
opendsp-v31.1.0.45.0815
emmc-boot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.631.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **
(bootloader) imei: **
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: **
(bootloader) battery-status: good
(bootloader) battery-voltage: 4083mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Ive been reading some more on fastboot and tried to give it a go with a clockwork recovery img and "fastboot boot" command.
I get the following
downloading 'boot.img'...
OKAY [ 1.070s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.073s
Is this because S-On? Anyway around it?
What can adb do in regards to recovering data?
Thanks for your help thus far guys.
exclusivebiz said:
I could boot into hboot. Are you referring to that as recovery mode? would you have any steps on using adb for recovering data?
Im not well versed yet with the backend of the android platform.
Click to expand...
Click to collapse
In hboot click on recovery.
With "adb shell" you should have access to the phone. With "adb pull <filename>" you can transfer files to your pc.
Don't know about contacts.
---------- Post added at 07:48 AM ---------- Previous post was at 07:44 AM ----------
exclusivebiz said:
*** locked ***
vle pvt ship s-on rl
...
Ive been reading some more on fastboot and tried to give it a go with a clockwork recovery img and "fastboot boot" command.
I get the following
downloading 'boot.img'...
OKAY [ 1.070s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.073s
Is this because S-On? Anyway around it?
Click to expand...
Click to collapse
This is because the bootloader is locked. You could unlock it at http://www.htcdev.com/ but don't do that. It will erase the phone.
hi, thanks for the reply, i will work on setting this up.
question - how do i know the files names, is there a directory/file listing command so i see everything available that i can "pull"?
hi, so i got into hboot menu then clicked on recovery, waited for the red triangle and finally pressed volume up and power to pull up another menu consisting of the following:
Android system recovery ,3e.
...
reboot system now
apply from sd card
apply from phone storage
apply from cache
wipe data/factory
wipe cache partition
I understand this is the recovery section but when i connect my phone to the computer and run adb devices it shows blank. When i ran adb - s [serial number] shell i get error:device not found.
I did it a few times and one time i got
adb -s [serial] shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
How do i get it to find the device?
Running Win 7 64 bit here
Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.
theconverter said:
Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.
Click to expand...
Click to collapse
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now
rzr86 said:
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now
Click to expand...
Click to collapse
Hi,Yep tried that one still getting signed error.
Thanks for looking
You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **
lot's of problems
Gatosbil said:
You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **
Click to expand...
Click to collapse
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s
theconverter said:
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s
Click to expand...
Click to collapse
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
rzr86 said:
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
extract the recovery.img and flash it via fastboot command
Click to expand...
Click to collapse
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts
theconverter said:
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts
Click to expand...
Click to collapse
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked
rzr86 said:
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked
Click to expand...
Click to collapse
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?
theconverter said:
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?
Click to expand...
Click to collapse
i really don't know mate
rzr86 said:
i really don't know mate
Click to expand...
Click to collapse
Hi, just a update ive fixed my phone, :laugh: done so by making a gold card following the tut's on this fourm installed 4ext via the card booted into recovery cleared dalvik cache ect and now boot's without any loop's.
Looking forward to flashing cyanogenmod and maybe going s-off
Many thanks for all your help and suggestions ill hit the thanks button for you.
Just need to mark as " solved " not sure how ( mod's ? )
Hi guys,
So I got this RUU from a "friend". Here it is as promised. Have fun!
Code:
Don't try to flash this if you flashed the Lollipop RUU before this. It won't work.
Even if it does work, you may end up bricking your device.
If you end up bricking your phone, don't blame me.
Code:
0. Charge your phone to at least 60% to be on the safe side
1. Copy the file to an sdcard
2. Rename it to 0PAJIMG.zip
3. Turn off the phone
4. Press and hold valume down + Power till the HBOOT screen shows up
5. Follow the instructions
Don't forget to hit thanks if this helps you..
Hash Values: (please verify before flashing)
Code:
SHA1: A3492D5096005187DA1423416532B4932EC8BF21
MD5: 1A14A2DD4DDDF822E903D8EDAE885A77
CRC32: 355CEF2F
Download
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks buggerman for the effort. I am downloading it.
@ buggerman
i'm getting an error message saying
Device halted due to Large Image update fail! Press <POWER> to reboot.
Click to expand...
Click to collapse
I'm on stock recovery and s-on
Pls help
iamsuperuser said:
@ buggerman
i'm getting an error message saying
I'm on stock recovery and s-on
Pls help
Click to expand...
Click to collapse
Did you relock bootloader first?
Captain_Throwback said:
Did you relock bootloader first?
Click to expand...
Click to collapse
No i did not relock bootloader . Is it necessary ??
I'm on s-on , is s-off required for flashing ruu ??
iamsuperuser said:
No i did not relock bootloader . Is it necessary ??
I'm on s-on , is s-off required for flashing ruu ??
Click to expand...
Click to collapse
I think bootloader lock is required. As far as I know, S-Off is only required if you're flashing some other CID RUU..
buggerman said:
I think bootloader lock is required. As far as I know, S-Off is only required if you're flashing some other CID RUU..
Click to expand...
Click to collapse
How do I get s-off , sunshine did not work on 1.26.720.6
You said s-off maybe possible on 1.25.720.3, so where can I get 1.25.720.3 ??
iamsuperuser said:
How do I get s-off , sunshine did not work on 1.26.720.6
You said s-off maybe possible on 1.25.720.3, so where can I get 1.25.720.3 ??
Click to expand...
Click to collapse
SunShine doesn't work on all devices. Depending on the error message SunShine gave you when you tried it, you may just have to wait until SunShine 3.0 is released.
But yes, if you are S-ON, you MUST relock your bootloader to run an RUU.
Captain_Throwback said:
SunShine doesn't work on all devices. Depending on the error message SunShine gave you when you tried it, you may just have to wait until SunShine 3.0 is released.
But yes, if you are S-ON, you MUST relock your bootloader to run an RUU.
Click to expand...
Click to collapse
Is it possible to relock with s-on ??
Coz in THIS thread it says i must be s-off
Pls help
iamsuperuser said:
Is it possible to relock with s-on ??
Coz in THIS thread it says i must be s-off
Pls help
Click to expand...
Click to collapse
You only have to relock if you are S-ON. Just a simple "fastboot oem lock" takes care of that. But then you have to immediately flash a proper RUU to get back to a working device.
That thread you linked is unrelated to any of this. That's specifically for people that are already S-OFF.
Captain_Throwback said:
You only have to relock if you are S-ON. Just a simple "fastboot oem lock" takes care of that. But then you have to immediately flash a proper RUU to get back to a working device.
That thread you linked is unrelated to any of this. That's specifically for people that are already S-OFF.
Click to expand...
Click to collapse
Ok then to unlock Again " fastboot oem unlock " is that it ??
Sorry about the htc 101 Qs.
iamsuperuser said:
Ok then to unlock Again " fastboot oem unlock " is that it ??
Sorry about the htc 101 Qs.
Click to expand...
Click to collapse
No, you unlock following the instructions at HTCDev.
buggerman said:
Hi guys,
So I got this RUU from a "friend". Here it is as promised. Have fun!
Code:
Don't try to flash this if you flashed the Lollipop RUU before this. It won't work.
Even if it does work, you may end up bricking your device.
If you end up bricking your phone, don't blame me.
Code:
0. Charge your phone to at least 60% to be on the safe side
1. Copy the file to an sdcard
2. Rename it to 0PAJIMG.zip
3. Turn off the phone
4. Press and hold valume down + Power till the HBOOT screen shows up
5. Follow the instructions
Don't forget to hit thanks if this helps you..
Download
Click to expand...
Click to collapse
Man,you're a life saver!!! Do you know how long I've waited for this... ?
rdheepak said:
Man,you're a life saver!!! Do you know how long I've waited for this... ?
Click to expand...
Click to collapse
Glad I could help!
Sent from my HTC One_E8 dual sim
Can I flash and return to stock with twrp with this RUU ?
@Captain_Throwback.... I tried lollipop and now running phone with Twrp recovery. so If I put stock recovery and lock device can I execute this RUU. Earlier I was having error saying I am on newer version.
demail2006 said:
@Captain_Throwback.... I tried lollipop and now running phone with Twrp recovery. so If I put stock recovery and lock device can I execute this RUU. Earlier I was having error saying I am on newer version.
Click to expand...
Click to collapse
You can if you're S-OFF. Otherwise, no.
However, if you're unlocked and S-ON, there is a way to downgrade your ROM but leave the Lollipop firmware installed. It requires decrypting the RUU and creating a bootloader-flashable zip of boot, system & recovery from this RUU, which can be flashed via HBOOT directly on the device or through fastboot RUU mode. It doesn't require locking the device either, but it will delete your data and internal storage.
@buggerman i download your RUU rom and installed it i face no error throw installing but the device keep rebooting when working with wizard and after finishing the wizard quickly no network appear on both cards with unknown base-band please see my phone var's
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.12.30.0109
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.720.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------
(bootloader) imei: 35282506xxxxxxx
(bootloader) imei2: 35282506xxxxxxx
(bootloader) meid: A10000xxxxxxxxxxx
(bootloader) product: mec_dwgl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ40000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ca994270
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
ansi_11111 said:
@buggerman i download your RUU rom and installed it i face no error throw installing but the device keep rebooting when working with wizard and after finishing the wizard quickly no network appear on both cards with unknown base-band please see my phone var's
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.12.30.0109
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.720.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------
(bootloader) imei: 35282506xxxxxxx
(bootloader) imei2: 35282506xxxxxxx
(bootloader) meid: A10000xxxxxxxxxxx
(bootloader) product: mec_dwgl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ40000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ca994270
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
Click to expand...
Click to collapse
This is strange. It worked perfectly for one of my friends. I guess the only difference was that he is S-ON and is not on a SuperCID, but I don't think that matters here.
buggerman said:
This is strange. It worked perfectly for one of my friends. I guess the only difference was that he is S-ON and is not on a SuperCID, but I don't think that matters here.
Click to expand...
Click to collapse
How to bring my device back any idea
ansi_11111 said:
How to bring my device back any idea
Click to expand...
Click to collapse
Have you tried the TWRP backup restore?
Sent from my HTC One_E8 dual sim
I'm not sure where to start. My brother handed me his phone after stupidly following a friend's suggestion that his phone would be faster if he did a factory reset. The phone displays the white screen with the HTC logo, then goes to a black screen and gets stuck there.
I'm able to get to fastboot, but I'm not really sure where to go from there.
The phone's never been tampered with before. S-ON, locked bootloader.
Here's the text I'm seeing on fastboot:
Code:
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012 <- I assume this date is because of the factory reset?
If I understood correctly from what I've been reading, I'm probably gonna need to reflash a stock ROM from fastboot through adb.
I got this HTC_One_X_RUU_5.18.502.1.exe from one of the threads. How do I extract the ROM from there?
I'd appreciate if anyone pointed me in the right way. I'm a Samsung guy and this phone is absolutely alien to me.
EDIT: Here's some more info I got from fastboot:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Here goes Serial#
(bootloader) imei: Here goes IMEI
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3780mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
How did he do the factory reset? Through recovery?
The symptoms you list are identical to what happens when flashing a new Rom without S-OFF.
My understanding is that due to write restrictions it can't copy the boot.img file to boot, which is required begin running the operating system.
I'm not sure if this is the case for factory resets though. So it may depend on how he tried to do the factory reset.
If the above situation is the case, then the fix is to flash the boot.img file of the same stock rom. Alternatively, you could flash a new rom and it's respective boot.img file.
He did that through fastboot. In fact he did the factory reset several times after the phone didn't boot.
I already tried flashing a boot.img from a ROM I found in the development section, but fastboot just says (remote:signature verify fail).
I have absolutely no freaking idea where to get that specific stock ROM. (It's 3.18.502.6, right?)
I added some extra info in the OP in case its useful.
EDIT: I downloaded the 3.18.502.6 OTA update, extracted the boot.img and the phone keeps spitting (remote:signature verify fail)
Since he flashed through recovery it may have screwed up because the bootloader is still locked (this may be the reason why you're getting errors too).
Unlocking the bootloader is what allows you to write to internal memory and is required to flash a rom.
I unlocked my bootloader using this nifty tool:
http://forum.xda-developers.com/showthread.php?t=2470972
This should then allow you to flash the boot.img file with the command
Code:
fastboot flash boot boot.img
I don't think flashing a boot.img is going to help. You're gonna need to run an RUU, either of these should be fine:
http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Transmitted via Bacon
Hey timmaaa, thanks for the help.
This phone is insufferable. Now I'm getting this:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip rom_02.zip
sending 'zip' (798796 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
I actually managed to flash rom_01.zip and now I'm able to boot into recovery.
When I'm on recovery the log says:
Code:
Can not mount SD Card (No such file or directory)
What would you suggest I do next?
Why are you doing that though? That's not how you use an RUU, you're not meant to extract anything, it's an executable file so all you do is connect your phone in bootloader mode and run the program. Plus, who knows what's been done to the device at this point with all the mucking around that's happened with it, flashing just the ROM component won't achieve the desired result. You need to run the RUU as intended so it can update all aspects of the phone and bring everything back into line. There's a pretty good guide to using an RUU here:
Running a Rom Update Utility (RUU) on the HTC One XL Evita
Follow that guide exactly and your phone will hopefully be revived.
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Mighty_Rearranger said:
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Click to expand...
Click to collapse
All good, is the phone booting now?
Transmitted via Bacon
Yup, it booted up alright. I think I'm gonna see how to install a custom recovery so I can fix it easier if he screws the phone up again.
Cool, I have detailed instructions for this device here:
http://forum.xda-developers.com/showthread.php?t=2593382