yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Android Development] fastludeh22:
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.

Glad you got it! After drivers installed, did you fix it per a section of the op?
[G2 and Desire Z Android Development] -FuRBz-:
it all happened because i had tried flashing cm 6.1- it got stuck on the splash screen but i had done a recovery prior to trying to flash... once i got the drivers installed i was able to get in to adb and do a reboot-bootloader and was able to get into the recovery file
[G2 and Desire Z Android Development] marley097:
Lame....so how often do they release official pic10img's....? are we talkin a month....or a year? :(
[G2 and Desire Z Android Development] Hawon:
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?
[G2 and Desire Z Android Development] Phonekenstein:
read the first post from the OP, and read the scenarios and follow the detailed instructions from there. Good luck.
[G2 and Desire Z Android Development] Hawon:
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.
[G2 and Desire Z Android Development] Phonekenstein:
your hboot is s-on or s-off?

what recovery is installed, stock, g2 testkeys or clockwork?

what did you do to that put your phone in this state?
[G2 and Desire Z Android Development] amroush_1800:
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. :mad:

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. :confused:

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 :D
[G2 and Desire Z Android Development] fastludeh22:
Great, glad you got it going! You were able to do that cause the s-off hboot had worked before the other probs had started. If you had an hboot problem the phone would not boot at all.

I would have omitted the last step, that put u back to s-on.

Alterntivly I would have suggested the steps under "if hboot is s-off". That being manually install cwm recovery (like you did). But then wiping and fashing rom of your choice. You would be done at this point w/your new rom + root.

But to each their own, that's the beauty of android, many different ways to do something. The end result is your phone is working again, and that's all that really matters! Hope something in this guide helped you, and the info you added helps someone else.

I suggest the rage method next time to root. And the new true radio s-off from scotty2.
[G2 and Desire Z Android Development] fastludeh22:
Have you tried it all the different ways I described in the 2nd post?

How did this happen? I.e. using visionary on stock phone. Or did you have custom rom /kernel installed and did something to cause this? Or...
[G2 and Desire Z Android Development] curleecoleman:
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.
[G2 and Desire Z Android Development] amroush_1800:
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.
[G2 and Desire Z Android Development] curleecoleman:
Thanks for your quick response is there a way to flash the eng hboot since I cannot use adb and also I was wondering if the signed zip in the roms section in the sticky guide can be used as a pc10img.zip for my g2 because I did do the OTA with wifi calling and I have heard people say that there isnt a pc10img for the OTA and that we have to wait for one to be found.
[G2 and Desire Z Android Development] steviewevie:
I think I must be missing something here. Because one of the methods to root the phone (rage) uses adb, and at that point you have a stock everything (recovery, hboot, etc). And adb does work at that point. Is it only a certain part of adb that you're saying doesn't work ?
[G2 and Desire Z Android Development] DrLabRatOry:
Yes, if your phone is fully/mostly functional, adb works (assuming you've enabled USB debug). However, in these semi-bricked phones (of which mine is one, grrr), it never gets to the point where adb is enabled.

And so we wait for a signed 1.22+ ROM, which the author of VISIONary said he was going to try to get. A month ago. I'm not holding my breath. He's moved on to other things.

And yes, if you are comfortable with command line and adb, there are absolutely no advantages to using VISIONary, and several disadvantages. I'm just glad I hadn't yet sold my 3GS and iphone_dev figured out how to hack the baseband in the meantime. Life without a smartphone is a bit of culture shock. :p
[G2 and Desire Z Android Development] steviewevie:
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 ?
[G2 and Desire Z Android Development] DrLabRatOry:
S-OFF via gfree appears to also require adb to function, so no, we're still stuck.
[G2 and Desire Z Android Development] steviewevie:
I think that with radio S-OFF (gfree) there's another way (not adb) to communicate directly with the radio/OSBL though ?
[G2 and Desire Z Android Development] luis86dr:
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.

[G2/HTC Vision]
[G2 and Desire Z Android Development] steviewevie:
I think you're talking to the OSBL in that mode. I have no idea what you can do there though (obviously, be careful if you're experimenting ! :D )
[G2 and Desire Z Android Development] jlopez0109:
in same boat

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?
[G2 and Desire Z Android Development] IcedZ:
Did you do the hex edit?
[G2 and Desire Z Android Development] steviewevie:
Check out this guide to getting adb up and running - http://xdaforums.com/showthread.php?t=865685
[G2 and Desire Z Android Development] dragon-son:
lost

kernel 2.6.32.17-g9ab3677

stock rom with ota

S-off

Not exactly sure what i've done but im stuck at the htc boot screen. I have adb and it seems to be working. I can access fastboot and i can flash recovery.

so starting from the the top what I have done/did to cause this.

i had visionary r11 and wanted perma-root.

uninstalled visionary and superuser

installed visionary r14

temp rooted

tried to perma-root

phone rebooted, but no perma-root

tried several times and nothing.

uninstalled visionary and installed again

still nothing

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.

followed instructions in guide again

this time it gave me the function error on the first file from gscript

ran second gscript file and rebooted

now stuck at the htc logo screen

tried to factory reset, stays on the htc screen.

tried recovery, stays on the htc screen

flashed image for recovery

recovery still stays on the htc screen

found a dl for clockwork mod recovery

flashed with fastboot

still stays on htc screen and in fasttboot no additional options

recover still stays on htc screen as well

any suggestions/questions im lost at this point on what to do.
[G2 and Desire Z Android Development] steviewevie:
:eek: That's a Desire HD guide ! You could brick your phone following a guide for the wrong phone (assuming you're in the right forum, i.e. have a G2/DZ).

Do you have S-OFF ? Do you have the engineering bootloader (what does it say if, from power off, you go into hboot, at the top) ?

I think you need to flash a complete ROM, but we need to do so carefully depending on exactly what state (e.g. S-OFF etc) your phone is in at the moment.
[G2 and Desire Z Android Development] dragon-son:
lost

I realized it was the wrong phone guide after I had already followed the instructions. I do have the G2.

Hboot says

VISION PVT ENG S-OFF

HBOOT-0.85.2007 (PC1010000)

MICROP-0425

RADIO-26.03.02.26_M

eMMC-boot

Oct 11 2010, 12:44:14

I am alright with flashing a new ROM, and I will follow any instructions/advice you have.
[G2 and Desire Z Android Development] gee one:
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
[G2 and Desire Z Android Development] fastludeh22:
if he had the dz hboot on g2 (or vice-versa) it SHOULD work. same internals. yes partitions are different so would require a reflash of a rom though.

HOWEVER he has a desire HD hboot on there, and all i can say is HOLY **** YOUR LUCKY, it will still let you in fastboot. most time wrong hboot=true brick, but it must just be close enough to boot.

now here is what i would try, and should work but dont hold me responsible. grab the g2 hboot here: http://xdaforums.com/showthread.php?t=834228

it will be in that download under perm root folder, hboot-eng.img put that file on the root of your computers c drive. boot into fastboot and do:

fastboot flash hboot c:\hboot-eng.img

give that time to finish, then do:

fastboot reboot bootloader

when your back in it should say "HBOOT_0.76.2000"

if it does follow this post: http://xdaforums.com/showpost.php?p=9284754&postcount=187

if it does NOT say that post back here and we'll go from there
[G2 and Desire Z Android Development] dragon-son:
Thank you, my phone is now functional again. I have stock ROM with root as of right now. Thank you guys again.
[G2 and Desire Z Android Development] keitaro1986:
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.

Thanks again for any help. Greatly appreciated!
[G2 and Desire Z Android Development] steviewevie:
The system partition is where the programs and other important stuff for your ROM are located. So it seems there's something still wrong with that. But Clockwork seems to be installed correctly (though you have 2.5.1.2 and there is a 2.5.1.3 available, but that's not really an issue or important right now).

Yes, you won't be able to use adb with your phone in recovery mode, Android will have to be up and booted for adb to work. Though if you have the engineering bootloader you can use fastboot commands from your PC to flash images (and do a few other things as well) to your phone before it gets into Android.

Yes, you should be able to flash Cyanogen now. What radio you have shouldn't affect the flashing process.
[G2 and Desire Z Android Development] keitaro1986:
Thanks for the quick reply!

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.

thanks again!
[G2 and Desire Z Android Development] steviewevie:
Yes, you should be fine to go ahead and flash. You have S-OFF which is helping a lot, and flashing a new ROM should start things afresh.

Download the CM ROM onto your PC and transfer it onto your SD card.

Then go into Clockwork and select the option to wipe your current ROM (data/cache).

Then select the option to flash a ROM from your SD card.

See the Cyanogen thread for more info - http://xdaforums.com/showthread.php?t=841275
[G2 and Desire Z Android Development] fastludeh22:
Gonna have to correct you on this one. Adb won't work in our stock recovery, but it will in clockwork or eng recovery. In stock it would say recovery offline or something like that.

The rest of info is correct though. He just needs to wipe data/cache and flash zip from sdcard. Really I think everyone should have to learn to do it the manual way before using rom manager. Rom manager is great and convient, but when you play around with beta roms and kernels, sometimes android won't boot, then u need to know how to flash the old school way. (The only way in my opinion, lol)... good luck.
[G2 and Desire Z Android Development] keitaro1986:
Thanks for all the help! my phone is now back in working condition!

you are really helpful!!!!
[G2 and Desire Z Android Development] Shimpuu:
DZ dont start

Hello Guys!

I would back to S-ON. I used adb and the backup of part7backup and the "dd"-command. But, perhaps, I overwrite the wrong partition, this was mmcblk0p18, but in a guide was written mmcblk0p7. Now, my DZ dont start and no charging.

When I hold Power + Vol. Down and plug in the Battery, my phone will vibrate and the LED was shining green. When I connect to the pc, a Message will popup that new Hardware will install (Qualcomm cmda technologies) but no driver will found. Have anyone an idea, what can I do? I think, I send it to repair service.

For any Ideas, I very thanksful

With best reguards.
[G2 and Desire Z Android Development] compi_hu:
so did you use p18 or p7 as target in the DD command?
[G2 and Desire Z Android Development] Shimpuu:
p18 was the target
[G2 and Desire Z Android Development] compi_hu:
Then you just destroyed HBOOT. Does not look too promising :(
[G2 and Desire Z Android Development] Shimpuu:
thats not good! I send it to repair and hope, nobody see, that I played with hboot, because the warranty.

still thank you
[G2 and Desire Z Android Development] steviewevie:
Cool, I didn't know that, thanks for the info :)
[G2 and Desire Z Android Development] steviewevie:
Oops ! :eek:

Your phone is bricked now. I think that what has confused you is that gfree (which does the part7backup) edits the radio config partition of the phone. But the actual hboot is in a different partition. So the radio config partition needs to go back to partition 7. But you don't even need to do this, because gfree now has options (from version 0.02 on) to switch back S-ON without that backup (see the Wiki for details).
[G2 and Desire Z Android Development] Shimpuu:
So,

DZ was send to repair service, look forward, what will happen now. I hope, it will repairable.

Thanks for your Informations as yet.

With best reguards and a happy new year!

Shimpuu
[G2 and Desire Z Android Development] ohyonghao:
It's completely working now.

After having done all the above I then rebooted the phone. This didn't go so well, nothing at all from adb. I booted into the bootloader and then sent it to recovery.

Once I was in recovery I noticed some strange errors:

E:Can't mount CACHE:recovery/command

E:Can't mount CACHE:recovery/log

Using adb also brought up errors saying invalid argument when I tried to mount.

I quickly googled these errors and found this helpful link.

I tried flashing cm6.1.1 again but to no avail. When I got into the boot loop I still couldn't mount the cache.

I decided to try restoring my old backup that didn't work before. It took it a long time to boot but it did, without me having to tell it to mount. I think that's enough thrills for one day, I'll put off the experimentation till later.

Thanks especially to Broam from #Cyanogen IRC and fastludeh22 for this guide. I hope that my story helps and gives hope.
[G2 and Desire Z Android Development] souljah614:
Hello I'm kinda new to the G2 I used the visonary method to root my G2 and everything went well. I went to unroot and I got most of the way thru flashing the pc10 image and my phone rebooted and and attempted to continue updateing then it said update failed said that old version newrer... can't recall full error name becase my phone is still fully rooted meaning I can still flash roms and the like but s is on. The only thing I've noticed is I'm unable to remove system apps. I would love to get s off again just to clean things up. Any help would be great. Thanks.
[G2 and Desire Z Android Development] steviewevie:
If you were flashing an earlier stock ROM than is on the phone, you will need to go through this procedure, which you will need root for - http://xdaforums.com/showthread.php?t=831398 (it applies to downgrading the G2 from a custom ROM, just as it does for downgrading from the OTA).
[G2 and Desire Z Android Development] isaac970:
i have s off and i have cwmod 3 and i wipe my phone and i try restoring a nandroid back up but even after it still stays at the htc screen any help? im thinking about just calling tmobile already to get a replacement. any help please im really worried here. thanks in advance
[G2 and Desire Z Android Development] renn9420:
@isaac970

What backup are you trying to to restore? If you have any backups of CM 6.1.0 or 6.1.1 then I suggest you flash CWM 2.X.X.X then do a restore. Of those roms or Virtuous. And if you're trying to get back CM 7 then I still suggest flashing CWM 2.X.X.X and reverting to an old backup of a different rom. Then you can go.back and reinstall everything. And even better just reflash CM7 and see if you get past HTC screen. CWM 3.X.X.X is buggy and is only for CM7 that's why I assume you have it for.

Phone: T-Mobile G2/Vision Rooted/GFree'd

Rom: Latest Cyanogen

Recovery: CWM-PSFreedom 0.3.3
[G2 and Desire Z Android Development] isaac970:
I figured out the problem and did go back to cwm 2.X oh and I had cwm 3 for the ginger villian rom but the sense rom kicks ass than that ginger bread rom
[G2 and Desire Z Android Development] zeus34:
Same problem me Desire Z Android noot boot only boot loop

I've tried many roms always the same problem

E:Can't mount CACHE:recovery/command

E:Can't mount CACHE:recovery/log

3 days old Desire Z 500€ :mad: