Root Help me PLEASE (advanced problem need really smart guy)

[scotty85]

cool,i think ive gotten myself up to date.

in a nutshell:
you cant see anything on the screen
you dont know if a recovery is working or not
now adb isnt seeing the phone in fastboot
you have no idea what happend to it in the first place

does that about sum it up?

 

[iowabowtech]

Was there a single vibrate when you entered Clockwork?

 

[TestToDeath]

ok ill recap lol


i have no idea how it happend.
Flashed it to high hell didnt do anything.
Reboot loop
.7 i cant see screen
.92 i can see screen but no recovery.
.7 possibly recovery
Fastboot sees it


Unknow wether any recovery is working yet.



also when i did the boot command into recovery

fastboot boot recovery

it vibrated and then didnt vibrate again. BUT!! i cANT See T3H fu8CKUN Screen





C:\Documents and Settings\safe>cd\

C:\>cd program files\android\android-sdk\tools

C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery1
sending 'recovery' (3058 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s

C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery
sending 'recovery' (4608 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s

C:\Program Files\Android\android-sdk\tools>fastboot devices
HT0CRHJ07939 fastboot

C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recoveryimg
error: cannot load 'recoveryimg'


C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery.img
sending 'recovery' (3582 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s

C:\Program Files\Android\android-sdk\tools>fastboot boot recovery
downloading 'boot.img'...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s

C:\Program Files\Android\android-sdk\tools>fastboot devices
HT0CRHJ07939 fastboot

C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery
sending 'recovery' (4608 KB)...
OKAY [ 0.828s]
writing 'recovery'...
OKAY [ 1.453s]
finished. total time: 2.281s

C:\Program Files\Android\android-sdk\tools>

C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery.img
sending 'recovery' (3830 KB)...
OKAY [ 0.703s]
writing 'recovery'...
OKAY [ 1.219s]
finished. total time: 1.953s

C:\Program Files\Android\android-sdk\tools>fastboot boot recovery
downloading 'boot.img'...
OKAY [ 0.828s]
booting...
OKAY [ 0.000s]
finished. total time: 0.828s

C:\Program Files\Android\android-sdk\tools>ADB DEVICES
Android Debug Bridge version 1.0.26

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments

will disconnect from all connected TCP/IP devic
es.

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb help - show this help message
adb version - show version num

DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.

C:\Program Files\Android\android-sdk\tools>ADB Devices
Android Debug Bridge version 1.0.26

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached


C:\Program Files\Android\android-sdk\tools>



^^^^^^^^^^^^ i should be in recovery because it didnt vibrate again

 

[iowabowtech]

Vibe once makes me think it may have went into recovery. If it were looping, I'd think you'd get multiple. So what recovery did you flash?

Whoa, wait a minute, you can ADB now?

 

[scotty85]

when i first skimmed thru things,my idea was if you could get to a working recovery,you go go to the mounts menu and possibly toggel emmc on so you could see what files are in there on your PC. from there maybe replace needed files.

but after reading it,looks unfortunately like your prollem is a little more in depth than that

 

[TestToDeath]

yeah *insert sad face here*
I dont know where it is right now because of the black screen, for all i know it could be chillin in recovery

 

[iowabowtech]

Whoa, wait a minute, you can ADB now?

^^^^

 

[doug piston]

I just spent a couple of nights on this with another person. Same issues but he was on a amoled and he could see hboot. Fastboot worked yet it never booted. Conclusion.... Hardware failure. Or a the misc partition is effed. You can't get to recovery to fix that so I would say your SOL. Sorry mate.

 

[iowabowtech]

It's odd that it's giving him a list of available ADB commands...I thought when in fastboot the user gets a list of fastboot commands? If you by some stroke of miracle are able to ADB, there may still be a chance.

 

[TestToDeath]

no the devices in hardware (in computer properties) is still reading ABI
We cant erase and replace misc partition? i couldnt imagen hardware failure i have been very nice to my pho- WAIT A MINUTE! before this happened my phone accidently got superheated.. .(57C) i was running a wireless tether so i could see.. you think that might be it.

 

[iowabowtech]

before this happened my phone accidently got superheated.. .(57C) i was running a wireless tether so i could see.. you think that might be it.

Uh....yeah. 135 degrees? Sorry for your loss.

 

[TestToDeath]

it was accidental. But the odd thing is that it worked afterward no problem.

 

[TestToDeath]

well until 3 or 4 days later when this happened XD

 

[doug piston]

no the devices in hardware (in computer properties) is still reading ABI
We cant erase and replace misc partition? i couldnt imagen hardware failure i have been very nice to my pho- WAIT A MINUTE! before this happened my phone accidently got superheated.. .(57C) i was running a wireless tether so i could see.. you think that might be it.

Bold = fail.

 

[TestToDeath]

Bold = fail.

well it might have been 53c cause 47c is what i wanted to stay under so i might have gotten the number wrong . i remember it being 119 degrees. still hot though.

 

[doug piston]

well it might have been 53c cause 47c is what i wanted to stay under so i might have gotten the number wrong . i remember it being 119 degrees. still hot though.

Meh, I still really think its a hardware failure. Sorry

 

[TestToDeath]

Meh, I still really think its a hardware failure. Sorry

thanks for all the help guys. I had it under warrenty and im getting a new one doug thanks for all tge help i learned alot. now i can help people in the rescue squad forum X)