My phone is semi-bricked now.. and my problem is ADB command doesn't really work right now...
It keeps telling me my phone is offline. what should i do?
read the first post from the OP, and read the scenarios and follow the detailed instructions from there. Good luck.
well, i should explained myself better. I can't use ADB command at all. Since this semi-bricking, my phone does not recognized by ADB commands at all. ADB shows my phone is offline.
Here is how I managed to solve this boot loop
I PermRooted using VISIONary S-OFF using hboot_7230_0.84.2000_100908.nb0
but when i rebooted phone.... Oh **** !! i got stucked in a reboot loop.
my new phone became a semi-brick.
what i did:
* Android SDK
unzip to C:\android-sdk-windows
* HTC Sync
install to get necessary USB drivers for ADB & fastboot protocols
i connected usb cable, then started phone normally. I issued this
command several times before the reboot occurs again to dump
debug messages from android kernel
> adb shell dmesg
INFO [ 7.424316] mmcblk0: mmc0:0001 SEM04G 2.17 GiB
INFO [ 7.424621] mmcblk0:
INFO [ 7.537780] EXT3-fs: INFO: recovery required on readonly filesystem.
INFO [ 7.537994] EXT3-fs: write access will be enabled during recovery.
<2>[ 17.243713] EXT3-fs error (device mmcblk0p26): ext3_add_entry: bad entry i
n directory #80002: rec_len is smaller than minimal - offset=0, inode=0, rec_len
=0, name_len=0
INFO [ 105.371154] request_suspend_state: wakeup (0->0) at 99729444658 (2010-12-0
3 01:22:50.574279812 UTC)
ERR [ 105.374786] init: untracked pid 1368 exited
from the log, i see that android fails to load its kernel because of filesystem
errors on the ROM and this caused the endless boot loop. it seems that
VISIONary or hboot may incorrectly handle the ROM cache resulting in
cache faults. A scandisk may partially solve these errors.
start phone in fastboot mode (power + volume down). connect to pc by usb cable.
manually installed ClockworkMod Recovery to phone
>C:\android-sdk-windows\fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
reboot phone again into boot menu (power + volume down).
select recovery to get into CWM -> then mount data and system partitions.
with the usb cable still connected i am able to adb to the phone
From a cmd window on pc :
>C:\android-sdk-windows\adb devices
List of devices attached
HT0B6RT00035 device
>C:\android-sdk-windows\adb shell
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p27 /cache ext3
/dev/block/mmcblk0p25 /system ext3
/dev/block/mmcblk0p26 /data ext3
/dev/block/mmcblk1p1 /sdcard vfat
we need first to unprotect the ROM and unmount its partitions before these errors can be fixed
~ # adb push wpthis-pre-OTA.ko /data/local/wpthis-pre-OTA.ko
~ # insmod /data/local/wpthis-pre-OTA.ko
insmod: can't insert '/data/local/wpthis-pre-OTA.ko': Function not implemented
~ # umount /system
~ # umount /data
~ # umount /cache
~ # umount /devlog
~ # e2fsck -y -f -v /dev/block/mmcblk0p25
~ # e2fsck -y -f -v /dev/block/mmcblk0p26
~ # e2fsck -y -f -v /dev/block/mmcblk0p27
~ # e2fsck -y -f -v /dev/block/mmcblk0p28
~ # dd if=/sdcard/hboot_orig.bak of=/dev/block/mmcblk0p18
~ # reboot
then, restarted my DZ as usual.
Viola ! my DZ is back to life again
well, i should explained myself better. I can't use ADB command at all. Since this semi-bricking, my phone does not recognized by ADB commands at all. ADB shows my phone is offline.
My phone is semi-bricked now.. and my problem is ADB command doesn't really work right now...
It keeps telling me my phone is offline. what should i do?
Hello I'm new to posting but I am having the same problems as others ADB only works for me when I am in stock recovery but all it says is device offline I tried to manually flash clockwork recovery but it comes back fail. I also have S-on with the stock rom as well. This all happened when I used Visionary and temp root first and then right after that I perm rooted and phone rebooted and never gets past the htc screen. I tried to most of the options except the very last ones because I cant get ADB to work. Any possible solutions would be greatly appreciated.
If you have a stock recovery installed, adb/shell access is disabled by default. when you try to connect to phone by ADB it says device is offline.
If you have both a stock hboot (S-ON) and a stock recovery, i don't think you have any access unless the device boots normally or recovering an official signed pc10img.zip of version equal to or higher than what is installed.
If you have previously flashed an engineering HBOOT (fake S-OFF), you have a chance to connect to the device via FASTBOOT method to flash a custom recovery image.
C:\android-sdk-windows\fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
From there you have many options. you can either adb/shell to fix filesystem errors or restore a nandroid backup or wipe and and flash a custom rom.
If you have a stock recovery installed, adb/shell access is disabled by default. when you try to connect to phone by ADB it says device is offline.
If you have both a stock hboot (S-ON) and a stock recovery, i don't think you have any access unless the device boots normally or recovering an official signed pc10img.zip of version equal to or higher than what is installed.
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
S-OFF via gfree appears to also require adb to function, so no, we're still stuck.
With the new radio S-OFF (gfree), we have a new route to un-bricking now, don't we ? i.e. if you power on the phone while holding down the Volume *Up* button, at which point the phone vibrates and the LED flashes amber. I think this is some sort of mode in which you can talk to the radio via a PC (though the screen is blank).
Do we know anything about this yet ? Or are we waiting for someone (Scotty ?) to figure it out for us ?
Funny that you mentioned that. I was playing around with my device and noticed that. Haven't got as far as to seeing if I could make the device and my pc communicate under that mode. Maybe ill give it a try when I get home.
Hey all, I am in the same boat as a few of you out there. I did the permroot with visionary and now its stuck in the htc boot logo screen. Having a hard time installing adb with the java sdk and all, so I just dont know what I am going to do with this phone. Worse part is its practically brand new. I tried putting the stock rom in sd card and doing the recovery. It all goes well untill the phone reboots for like a second time...then just back again stuck in the HTC logo screen. Is there something I can do.....or is this g2 useless?
Hey all, I am in the same boat as a few of you out there. I did the permroot with visionary and now its stuck in the htc boot logo screen. Having a hard time installing adb with the java sdk and all, so I just dont know what I am going to do with this phone.
did some reading found this post http://xdaforums.com/showthread.php?t=834427
downloaded guide
followed instructions
my kernel wasn't on of the ones listed so i modified the one 2.6.32.21-gf3f553d to be 2.6.32.21-g9ab3677 where stated and moved files to sdcard root
ran gscript files
rebooted still no perma-root
noticed that i had kernel 2.6.32.17-g9ab3677 so changed the file to have 17 instead of 21 before the - in the kernel name.
I think you have the DZ engineering bootloader on your G2, which might explain why you have all the bootloops. I believe the partitions are different, so it will flash roms and recoveries to the wrong place.
Sorry, I don't have any advice on how to move forward.
Sent from my CyanogenMod Vision
hi all,
i have the following error on my clockworkmod recovery.
i've previously gotten into a semi-brick state and my phone went into a boot loop, so i followed a lot of other guides and finally got my clockworkmod flashed on the phone.
phone is S-OFF and i guess it should be rooted.
this is my first time working on android and any help will be really appreciated.
another issues, when i try to use adb devices command it returns me saying that my device is in the recovery mode, is that normal?
last question. if i get my clockworkmod to work, can i just flash the CyanogenMod-6.1 for Vision :: V6.1.1 rom?
I've read a lot about radios and such, i am kina worried if any of these will affect the whole flashing process.
can you point me to a guide for doing the rom flashing?
So as to speak, i can ignore the error above and start to do the rom flashing right? just to make sure before moving on, don't wish to end up in another semi brick state.