Saving Data from locked, bricked device - HTC One X

Hey there,
as the title of the threat already indicates, my HTC One X got bricked.
As this usually happens when trying to flash some custom roms or recoverys, in my case it is the result of an official HTC update for android.
I can boot into Fastboot, and via cmd "fastboot devices" does show me the connected phone.
Now my approach for solving this matter was to flash the clockwork mod and then boot into recovery.
From there i wanted to pull data from the phone via adb commands.
The only problem is that my phone is locked. I cannot unlock it at the moment without wiping all data (which obviously would miss the whole data recovery point).
When i try tp flash the CWM in fastboot i get:
sending 'recovery' (8100 KB)...
FAILED (unknown status code)
finished. total time: 0.933s
I also tried to directly boot a recovery via fastboot boot recovery.img.
This resulted in
downloading 'boot.img'...
FAILED (unknown status code)
finished. total time: 0.933s
Well now I am seriously frustrated and dont know how to get my data.
Any help is very much appreciated.
Cheers
Josef

Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?

joe1000 said:
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
Click to expand...
Click to collapse
You must to unlock the device qith locked you can't do anything but if you unlock it is possible to wipe all data on the SD card

well but thats exactly the problem...

Related

[Q] Flash system.img via fastboot error

Keep getting:
sending 'system' (955771 KB)
FAILED (remote: (00000006))
finished. total time: 0.004s
When trying to flash system.img
Can flash boot and recovery no problems, any ideas?
I've the same thing, I think it's normal.
How did you get around it?

[ERROR] message when flash any help

When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Do what everyone should be doing... use Rezo's tool to root and install CWM. Then use CWM to flash your ROM. Simple.
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Is your bootloader unlocked? It must be to do that
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Boot your device on HBOOT, and select FASTBOOT and then connect with PC. (USB Debugging must be enabled)
Follow the instructions here to Flash ROM :
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
It's done now.

[Q] m8 possibly corrupt hboot

Hi
I am not really sure what i have done wrong here, but i have got myself to a stage where i can get to fastboot, but i cannot get to the recovery, if i select hboot then i get the following:
TWRP: teamwin screen flashes a couple of times then the device reboots
CWM: black screen the the device reboots
Stock recovery: android driod with a red exclamation mark then the device reboots
I have tried multiple recovery's as you can see.
I know that i am currently in a state where i have NO os on the phone.
**TAMPERED***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.14.2133156.UA24G
OpenDSP-v26.2.2-00538-M8974.0106
OS-
eMC-boot 2048MB
Feb 26 2014,21:38:56.14307
This all started when i somehow got in a reboot loop when SuperSU tried to push the su binary to TWM.
Any help or directions to get me back ontrack would be appreciated.
Thanks
Darren
--
addition, just following some instructions about restoring to stock boot, recovery and rom from android reolution, output below:
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (8262 KB)...
OKAY [ 0.971s]
writing 'boot'...
OKAY [ 0.666s]
finished. total time: 1.638s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash recovery recovery
mg
target reported max download size of 1830711296 bytes
sending 'recovery' (15236 KB)...
OKAY [ 1.605s]
writing 'recovery'...
OKAY [ 0.992s]
finished. total time: 2.599s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.020s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash update update.zip
target reported max download size of 1830711296 bytes
sending 'update' (1387053 KB)...
OKAY [ 59.626s]
writing 'update'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 137.319s
Try fastboot erase cache

[Q] HTC BEATS AUDIO Cant install CWM [ Help ]

Hello i have a problem with this htc sensation of mine.. phone is Hang up in HTC logo only. i try to factory reset but its same. try to Recovery but theres no recovery only an image of unit with red triangle.. i try to download CWM here http://www.clockworkmod.com/rommanager via CMD command but its always failed. like below
i make a folder in my drive "d" name android and i put inside the recovery.img
C:\Users\Almutakhases\Desktop>d:
D:\>cd\android
D:\android>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
D:\android>
Click to expand...
Click to collapse
can someone give me a working CWM for this unit.? help me to solve this please.
Model HTC Sensation PG58130
Problem: Hang on Logo Only
Action Taken:
1. try to factory Reset = Same problem
2. Try to Recovery Mode = No Recovery Mode. displays a mobile with a triangle and red exclamation mark.
3. Try to send CWM via Fastboot or CMD command = Failed. logs below
4. try to JTAG via Riff box = same Problem
C:\Users\Almutakhases\Desktop>d:
D:\>cd\android
D:\android>fastboot flash recovery recovery.img
sending 'recovery' (5400 KB)... OKAY [ 1.476s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.175s
D:\android>
########################################################################
C:\Users\Almutakhases\Desktop>d:
D:\>cd\android
D:\android>fastboot flash recovery recovery.img
sending 'recovery' (4618 KB)... OKAY [ 1.142s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.740s
D:\android>fastboot erase cache
erasing 'cache'... OKAY [ 1.559s]
finished. total time: 1.559s
D:\android>
Click to expand...
Click to collapse
Any Advice to Solve this
Sounds like you are s on and locked. You'll need to either unlock the boot loader,or run a full,signed ruu
Also,If you have a sensation,you have put your problem in the wrong forum. This is one x
thanks scooty i found RUU for this model and its all ok now.... :good:

[SOLVED] Can't flash stock recovery 4.20.531.4

I downloaded the stock recovery for 5.0.1 from here http://forum.xda-developers.com/showpost.php?p=51836232&postcount=1
When I go into fastboot and try to flash I get an error:
$ fastboot flash recovery Tmo-M8-4.20.531.4-recovery.img
target reported max download size of 1826152448 bytes
sending 'recovery' (16046 KB)...
OKAY [ 1.753s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
This is with bootloader unlocked, if I try with bootloader locked I get:
$ fastboot flash recovery Tmo-M8-4.20.531.4-recovery.img
target reported max download size of 1826152448 bytes
sending 'recovery' (16046 KB)...
OKAY [ 1.757s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.763s
I notice theres a 1mb difference between twrp-2.8.7.0-m8.img (17.4mb) and Tmo-M8-4.20.531.4-recovery.img (16.4mb)
How am I supposed to get the stock recovery back without erasing anything else?
Device is S-OFF
Wow, turned out to be a bad download :| Redownloaded and it flashed fine
CHECK MD5 SUMS BEFORE FLASHING
Some screwed up stuff could have happened, thankfully even S-OFF does have some precautions.
MOD EDIT

Categories

Resources