yashsingh1/xdaforums huggingface dataset:
[Legend Q&A, Help & Troubleshooting] zerodi:
I took a screen shot, that's flashing the rom.zip from cmd it installs all the way but then the next step .... fastboot OEM boot

.. always fails

Status read failed, too many links
[Legend Q&A, Help & Troubleshooting] BlaY0:
Try 'fastboot reboot' instead.

Sent from my HTC Legend
[Legend Q&A, Help & Troubleshooting] zerodi:
That worked but the phone gets stuck on the HTC boot screen ( without quietly brilliant written)

darn i thought we had it !:(
[Legend Q&A, Help & Troubleshooting] bonesy:
Man next time use CODE tags lol, Try it again see if it gives you a different output?
[Legend Q&A, Help & Troubleshooting] BlaY0:
For how long did you wait at htc boot screen.

Try this... get rom.zip from 3.15.405.3, rename it into LEGEIMG.zip and put it onto SD card. Power on and if you get into fastboot reboot it using 'fastboot reboot-bootloader'. It should flash it automatically and reboot at the end.

Sent from my HTC Legend
[Legend Q&A, Help & Troubleshooting] zerodi:
Hehe sorry

For about 10mins I waited on the HTC screen
[Legend Q&A, Help & Troubleshooting] zerodi:
Cool ill try that now! Thanks
[Legend Q&A, Help & Troubleshooting] zerodi:
just tried it BlaY0, i tried power on to fastboot (with 3.15 rom.zip renamed on the sdcard to LEGEIMG.zip) then apply the command you said, fastboot reboot-bootloader

it just boots stright back into fastboot usb , doesnt seem to do anything

...

I also tried going into HBoot, letting the LEGEIMG.zip load and it jumps right into the fastboot menu also
[Legend Q&A, Help & Troubleshooting] BlaY0:
OK, when in fastboot and connected via USB issue 'fastboot reboot'. After green htc shows issue 'adb reboot oem-42'. This should reboot your device and bring you directly into hboot. Then after several seconds hboot checks for LEGEIMG.zip (mind the case and that your goldcard is formatted as FAT32) presence (green text running over the screen)and if it finds it it starts flashing automtically. After flashing your device should reboot automtically and start to write radio image (black screen with big green sync circel in the center and grey status bar below the circle). Only after radio firmware is written to its place, the phone is ready to reboot.

Sent from my HTC Legend
[Legend Q&A, Help & Troubleshooting] zerodi:
Hi BlaY0,

After green htc shows issue 'adb reboot oem-42' im getting :-

C:\android\tools>adb reboot oem-42
adb server is out of date. killing...
* daemon started successfully *
error: device offline

I already have the correct adb drivers installed, in device manager on the green htc screen, its showing

ADB Interface - My HTC

C:\android\tools>adb devices
List of devices attached
HT07NNX02121 offline

C:\android\tools>adb reboot oem-42
error: device offline

Im thinking it might be my Goldcard and now i have the device showing up on adb devices ill try to make a new goldcard:)

Edit : opps bugger cant make a goldcard didnt notice it still says device- Offline

I have the goldcard.img though so i can still do the hexeditor stage but that goldcard.img is from a different htc Legend

Didnt work still shows as Device-Offline (I think if we can get it Online we can fix it !!)

--- I saw on a G2 thread that "downloading the fastboot binary " might help --- ?

not sure its of any relivence though http://xdaforums.com/showthread.php?t=841555
[Legend Q&A, Help & Troubleshooting] zerodi:
Doing a bit of digging into bricked legends - i guess mine is in that kind of cat lol

found this http://android.modaco.com/content/htc-legend-legend-modaco-com/309961/usb-brick-rickrolled-b0rked-fixed/

But it needs root, but maybe i could give it a try ? what do you think?

-------------

Ok Ill delete this comments hehehe
[Legend Q&A, Help & Troubleshooting] BlaY0:
Nope, that's not your case. You have to have working system to be able to do what upper post said.

Your only problem is that you can't navigate through bootloader. Try 'fastboot oem keytest' to test your HW keys again.
[Legend Q&A, Help & Troubleshooting] zerodi:
Ok Thanks blaY0, looks like my HW keys are ok

C:\android\tools>fastboot oem keytest
...
(bootloader) start keypad testing ...
(bootloader) <BACK>
(bootloader) <VOL UP>
(bootloader) <OJ PUSH>
(bootloader) keypad testing is finished.
OKAY [ 0.035s]
finished. total time: 0.036s

:)

Working again but still showing - adb - Offline

I tried this approach using an extracted 3.15 rom.zip -

C:\android\tools>fastboot boot rom.zip
creating boot image...
creating boot image - 148389888 bytes
< waiting for device >
downloading 'boot.img'...
OKAY [ 17.372s]
booting...
FAILED (remote: not allowed)
finished. total time: 17.378s

C:\android\tools>fastboot oem boot rom.zip
...
(bootloader) setup_tag addr=0x60000100 cmdline add=0x9D07B198
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x22F00
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is VODAP001
(bootloader) setting->cid::VODAP001
(bootloader) serial number: HT07NNX02121
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =438
(bootloader) active commandline: board_legend.disable_uart3=0 board_legen
(bootloader) d.usb_h2w_sw=0 board_legend.disable_sdcard=0 diag.enabled=0
(bootloader) board_legend.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=false androidboot.baseband=7.13.35.05 androidboot.c
(bootloader) id=VODAP001 androidboot.carrier=VODA-UK androidboot.mid=PB76
(bootloader) 10000 androidboot.keycaps=qwerty androidboot.mode=normal and
(bootloader) roidboot.serialno=HT07NNX02121 androidboot.bootloader=1.01.0
(bootloader) 000 no_console_suspend=1 console=null
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
FAILED (status read failed (Too many links))
finished. total time: 0.956s
[Legend Q&A, Help & Troubleshooting] BlaY0:
So what's the problem then???? Boot into fastboot, choose bootloader, press power button to enter hboot, wait for LEGEIMG.zip to flash, scroll with vol up to fastboot, choose it, scroll up to reboot, choose it...
[Legend Q&A, Help & Troubleshooting] zerodi:
Hehe i dont know what is the problem because when im in fastboot menu, if i press power button (nothing happens, its none responsive) and also the vol buttons dont respond

If the phone is off i can vol+down +power and enter HBOOT screen with the blue hboot, but NO HW buttons are functioning again same as fastboot mode

When i try Hboot / Power off / Vol Down +Power , it loads LEGEIMG.zip then

checking.. LEGEIMG.zip

After checking LEGEIMG.zip it boots into fastboot mode automatic

if i press any of the HW buttons its None Responsive

I hope you see what i mean - i wish the buttons are working but there really not doing anything one in the fastboot or hboot menus , its so fustrating
[Legend Q&A, Help & Troubleshooting] zerodi:
video

Heres a video + photos (zipped) of me pressing vol down + power to get into the HBoot mode then letting it do LEGEIMG.zip , hope you see what i mean that it automatic goes stright to the fastboot mode after

hope you can watch it to see what i mean.............

I can post another video of me pressing the buttons to show you they really dont function within the Hboot and Fastboot Menus ??
[Legend Q&A, Help & Troubleshooting] BlaY0:
Yeah, that's normal if hboot throws an error it reboots bootloader. You are trying to flash older version which your hboot doesn't allow that's also normal if you have hboot 1.00+. So you have to make LEGEIMG.zip from RUU rom.zip that is the same version or newer as one on your device...
[Legend Q&A, Help & Troubleshooting] zerodi:
ok thanks , i get that

so all of these didnt work as LEGEIMG.zip's

RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7.05.35.26L_release_126592_signed

RUU_Legend_HTC_WWE_1.23.405.1_Radio_47.26.35.04_7.05.35.26L_release_120393_signed

RUU_Legend_Froyo_S_HTC_WWE_3.15.405.3_Radio_47.51.35.17_7.13.35.05_release_160328_signed

RUU_Legend_Froyo_S_hTC_Asia_WWE_3.15.707.3_Radio_47.51.35.17_7.13.35.05_release_160424_signed

RUU_Legend_Froyo_S_Chunghwa_3.18.751.2_Radio_47.51.35.17_7.13.35.05_release_164781_signed

Do you know what other ones i could try that would be the same or newer than my bootloader ?

Thanks BlaY0

I saw on another post you said "The significance is such, that you have to tamper it with a version number that is older than one you are trying to flash. That's how you trick the fastboot. Flashing a RUU will then overwrite the version number again "

Would that work in my case ?

http://xdaforums.com/showthread.php?t=845512&page=9 Post#88
[Legend Q&A, Help & Troubleshooting] zerodi:
Hey BlaY0 i found this thread http://xdaforums.com/showthread.php?t=751265&page=6

post #60

part -

"In a MSDOS command window in Windows XP I executed from the AndroidSDK subdirectory containing the fastboot executable (in my case C:\...android-sdk-windows\tools\) "fastboot oem enableqxdm 0" which enabled fastboot usb-plugin on the phone (see it com up in red text in the fastboot menu).

In another MSDOS command window I changed to the unzipped "r4-legend-root" directory and ran "fastboot-windows.exe oem rebootRUU" that allowed me to execute the latest RUU (either execute the RUU from this MSDOS command window or click on the file in Windows File Manager) and install the stock HTC 2.2 rom normally following the RUU menus. I used the available RUU_Legend_Froyo_S_HTC_WWE_3.15.405.3.....160328_s igned.exe.

I now have a fully functional Legend with the stock unrooted HTC Android 2.2 with hboot 1.01. "

Im going to try this, as i have the r4-legend-root also
[Legend Q&A, Help & Troubleshooting] zerodi:
Feck !! Didnt work - Bootloader version error again

Image Version is - 3.18.751.2

Edit i tried this RUU -

RUU_Legend_Froyo_S_Chunghwa_3.18.751.2_Radio_47.51.35.17_7.13.35.05_release_164781_signed.exe

its the same one 3.18.751.2 It completed Successfully !!!!!!!!

The phone Rebooted and its STILL stuck on the Green HTC Logo !

omg i cant belive it, i thought that would work hmmmmm

so all i can try now is the same RUU but in the rom.zip LEGEIMG.zip way of doing it, other than that im trumped

------------

BlaY0 , now it flashed 100% it would have all the system files on it correct?

Is there anything we can do now, before i try somthing else to get it booted? I dont know why it got stuck on the green htc screen after a successful flash from the 3.18 RUU !! darn darn darn
[Legend Q&A, Help & Troubleshooting] BlaY0:
Nope. You have to have a working system to be able to do that.

I honestly don't know what's wrong with your phone... as if it isn't able to run the kernel.

There's another 3.30 RUU lying around somewhere.
[Legend Q&A, Help & Troubleshooting] zerodi:
Ill look for that 3.30 RUU

I just LEGEIMG.zip the 3.18 one and tried it that way but gets stuck on the parsing...[SD ZIP] see photo

... Thanks for all your help btw and the posters in the beginning its got quite far but seems to fall on the last hurdle every time lol
[Legend Q&A, Help & Troubleshooting] zerodi:
Could you point me in the direction of that 3.30 RUU , ive tried to search the Legend forums and outside Xda but it turns up nothing :confused:

I tried again but still no luck - cannot get past the darn green htc boot screen - I think this Legend is Officially Dead!
[Legend Q&A, Help & Troubleshooting] madito12345:
Okay man,

Now I dont know if your as dumb as I am but i tried the most basic step of troubleshooting.

I took the battery out of the phone and left it that way for a few hours and.. voila! The Legend is back in business.

Cant believe I'm that stupid..:rolleyes:
[Legend Q&A, Help & Troubleshooting] alexhtclegend:
You could try sending it to HTC, they might just replace it?
[Legend Q&A, Help & Troubleshooting] zerodi:
hehehe u mean it booted up into the o/s, or the hboot screen and fastboot screen vol buttons worked?
[Legend Q&A, Help & Troubleshooting] zerodi:
Yeah i might just do that, its in pretty bad shape though outer casing has lots of scratches and needs a new speaker grill hehe , it also doesnt have warranty anymore im guessing

im back in the uk soon, so might try to find out how much that would cost - thanks
[Legend Q&A, Help & Troubleshooting] SharkDog2:
I have the exact same problem that Zerodi is having with the legend of my girlfriend. I've been trying to fix this aswel but with no luck. Whenever i press the power button on the phone it automatically goes into the hboot and none of the HW keys work.

Crappy thing is that my warrenty is voided since the white (water) stickers on the inside turned orange :(
[Legend Q&A, Help & Troubleshooting] bonesy:
You dont need warranty for a repair you just have to pay!
[Legend Q&A, Help & Troubleshooting] SharkDog2:
Yeah I know, but I am not gonna pay for something that clearly just a faulty phone.
[Legend Q&A, Help & Troubleshooting] SharkDog2:
I tried the phone a few days ago and it booted up normally, so I immediately rooted it and put cm7 on it because I was thinking it might have been something with the software. It seems to be running fine now.
[Legend Q&A, Help & Troubleshooting] opfobo 1:
Hi,

I have a very similar problem. After my Girlfriend did something I am not sure of my phone is bricked.

After reading a lot here on the forum without luck I will post a screenshot.

The stuff I have done:

- several goldcards

- several extracted rom.zip via HBOOT with vol down + power and LEGEIMG.zip

results were either to old... or this (screenshot) gbimg.org/p.php?q=mHFWb

Kind regards
[Legend Q&A, Help & Troubleshooting] Hypriit:
Hi,

I had same problem. Everything exactly as you described.

Only way to get some control was through usb fastboot.

Using Android-SDK. I made restart (fastboot reboot) and got green logo screen. ´

I waited some time (quite long compared normal boot time) and finally it booted up in safe mode but hard buttons did't work.

I made restart and again was stuck in boot screen, made reboot again but this time it was stuck on logo screen too.

I removed battery for some minutes and tried again with success. And it was not even in safe mode. And keys were working.

But.. i noticed that after some time even when i didn't touch my phone volume screen came on and vol went up and after that my hard buttons didn't work again. I managed to get them working just lifting vol up button a bit.

So maybe the problem is in vol button. its somehow stuck.

-That's way it went on that boot screen (You need to press vol button and power to do that).

-That's way you didn't have control in boot screen because vol button is stuck and others don't work.

-And that's way it went in safe mode (You need to hold some button down when booting).

I lost my hard buttons control after i saw that vol up screen.

In one case solution was leaving battery out for some time. Maybe you phone did get some humidity and dried out with that time and worked fine after that.

In my case i think that the problem was humidity because buttons started working again when when phone was near car climate.

So maybe that helps someone with similar problem. When hard buttons don't work there is a big chance that its hardware problem : )

So when nothing else helps clean you button contacts.

All the best,

R
[Desire Q&A, Help & Troubleshooting] sgb101:
can i turn the Bluetooth connection notification sound off, with out turning off all notifications. as in car i get a notification beep every 5 mins, and is very annoying when listening to Audible.

i cant see the setting anywhere please help, as i love this Rom, but this could be a deal breaker for me.
[Desire Q&A, Help & Troubleshooting] Meaple:
Delete the audio file?

Sent from CM7
[Desire Q&A, Help & Troubleshooting] ChristTheGreat:
Hi, Sorry for bringing up an old topic, but I found a way to disable the notification sound when you connect an headset with bluetooth.

Parameter, cyanogenMod, sound, then uncheck Notifications priority (worked for me).
[Milestone XT720 General] Tavinsky:
anyone know how or if there is any way to clear the cache dalvik without entering recovery mode?
[Milestone XT720 General] Mioze7Ae:
What do you mean? I don't think you can wipe it while the system is running... Are you locked out of open recovery?

What ROM are you using? If you're using one of khal's recent ROMs or Dexter+bugfix-v3 you should be able to use Motorola's recovery to wipe the cache partition (dalvik cache is moved to /cache by default on these roms, otherwise it's on /data (or you could have moved it to ext partition)).
[Milestone XT720 General] Tavinsky:
Now I'm using the ROM dexter, You're right, it is not possible while the system is working ....

Thanks.!
[Desire Themes and Apps] Klewe:
Hi,

I link my contacts with my whatsapp contacts. Everything works fine when I link them, but every now and then it asks me again to link them all. Anyone else got this issue?

I'm running the insert coin v30 rom, but had it also in other versions of the rom.

Thanks for your help.

Klewe
[Galaxy S II Q&A, Help & Troubleshooting] Locster126:
On auto brightness my brightness level never stays at low when in the dark, it goes low and then straight away back to being bright. Any way to keep auto brightness at a lower level?
[Vibrant Q&A, Help & Troubleshooting] CriticonX:
I got my wife a Vibrant the other day to replace her current non-smartphone. She does not have a data plan. She will, however, be adding the pay per use data to her account so she can sporadically use data on a trip next weekend, but she wants to be able to turn the regular data off (as to not incur charges when she does not explicitly want to use the data) while still being able to use MMS (as she has a messaging plan).

Is there a way to toggle the Data on and off at will but still be able to send and recieve MMS with the regular data off? I have read that APNDroid does not work on the vibrant (and other galaxy s phones), though other people say it does.

The phone is stock Froyo 2.2 and only has one APN (T-Mobile US, epc.tmobile.com). Should I create a separate apn for MMS only and change the regular apn's type to just "internet" from "internet + mms"? Or would that still not work with APNDroid in the way I'd like?

Thanks for any help. :)
[Vibrant Q&A, Help & Troubleshooting] }{Alienz}{:
No. Go into the APN setting. At the VERY bottom, there is APN type. Set it to MMS only. That way it will only activate when an MMS is received/sent. That is the same setting you describe in your post.

Be aware that MMS data usage will NOT get charged. Yes, it is technically using data but if your wife has texting, sending and receiving MMS messages will not incur you ANY charges, even though it uses data.

Note though that it's not perfect. Sometimes MMS gets bugged where it fails to download because the phone bugged and didn't establish a data connection. In that case, just go in the same menu and refresh it or go to the market so it establishes a connection and everything will work. Hope that helps.

Source: I have my Vibrant with data completely shut off. I don't pay for data and never have since I bought it. I have wifi most places.
[T-Mobile LG G2x] foethalove:
I am having serious browser lockup issues.

My stock browser will normally load to about 90% and then just freeze . I will have to let it sit for a good 5 or more minutes to finish loading. It sometimes requires a battery pull. I have the same lockup issues with Opera mobile.

I have tried tweaking my cpu with pimp my cpu but the issue persist regardless of the changes I make.

Has anyone else experienced this and found a solution?

Bionix RC1

Trinity Kernel
[T-Mobile LG G2x] moshe22:
I noticed that and started to happen when I flashed Trinity.
[Nook Color Q&A, Help & Troubleshooting] Omega Ra:
I can't seem to get any other keyboards to work. I have a stock NC 1.2 that was rooted first with MiniRooter (I think it is called) that OC'd it with the 1.2 GHz Kernel and then I MN with the most recent one as it had more options I wanted. But I can't seem to get a keyboard to work.

I have the gingerbread keyboard and thumb keyboard apk's and put them both in system/app with Root Explorer, reboot and nothing, I have tried to manually install them by clicking and using the package installer, nothing. Don't know what is up. none of them show up in the nook color tools under keyboard, but they show up in the manage programs...
[Nook Color Q&A, Help & Troubleshooting] Omega Ra:
anyone? It doesn't seem to make sense and I don't know enough about Android to troubleshoot.
[Nook Color Q&A, Help & Troubleshooting] boxcar8028:
all i have to do to try new keyboards is:

1) download new kb from the market.

2) install the new kb.

3) go into settings and make sure the keyboard is checked.

4) go to a text field and long press.

5) keyboard options will appear.

6) check the kb you want to use.

thats it. thats all i have to do for a new keyboard.

not sure about pushing the kb apk into syetem/app maybe its best to just install them.
[Nook Color Q&A, Help & Troubleshooting] Omega Ra:
my problem is that when I go into settings it isn't there to be checked..
[Nook Color Q&A, Help & Troubleshooting] KWKSLVR:
I'm pretty sure that you'll HAVE to use ADB. Here's what I just did with the SlideIT keyboard on rooted 1.2. I put the apk on C: of my PC. Then in adb typed:

cd \
adb push <application_name>.apk /system/app
adb reboot

After the Nook reboots go into NookColor Tools, tap Keyboards and you should see it there.

If we're talking about SlideIT downloaded from the Market, then in ADB you may need to do:

adb shell remount rw
adb pull /data/app/<application_name>.apk
adb rm /data/app/<application_name>.apk
adb push <application_name>.apk /system/app
adb chmod 644 /system/app/<application_name>.apk
adb shell remount ro

Then reboot >nookcolor tools>keyboards>slideit.
[Nook Color Q&A, Help & Troubleshooting] Omega Ra:
when I get a chance I will give it a go. Thanks :-)
[Nook Color Q&A, Help & Troubleshooting] Omega Ra:
I can't get the first part to work, it says not found. Where do I put the apk? I have it on c: on my comp.
[Nook Color Q&A, Help & Troubleshooting] KWKSLVR:
Which part specifically doesn't work?

Are you getting that after typing:

adb push <application_name>.apk /system/app

If so, try typing

adb kill-server

and try again

The apk is in the right place if it's in root on C: (and it is). Typing cd \ is pointing adb to look into C: for the apk you're trying to install. It's probably not the cleanest way to do it, but I've just always done it that way so people might wanna paint me silly. :D
[Nook Color Q&A, Help & Troubleshooting] Omega Ra:
okay, let me try the kill server thing
[Nook Color Q&A, Help & Troubleshooting] Omega Ra:
no go, still says not found. I even renamed the apk to make sure I knew how many spaces and such...nothing...

hang on, I was in adb shell, went to normal root, I have to mount it as r/w first...

how do I do that lol

EDIT: Nevermind, I used rootexplorer to get it r/w and now the keyboard is there :) thanks a lot!
[Nook Color Q&A, Help & Troubleshooting] KWKSLVR:
Are you in recovery or is your nook booted up?

Reboot your Nook and try

adb kill-server

again. Then

adb start-server

And attempt to install again. If that doesn't work, if your nook is still booted up (not in recovery), try:

adb remount

and try to install. If that doesn't work, try:

mount -o rw,remount

If you're trying to do this with your Nook booted into recovery, try:

mount -o rw,remount /dev/block/mtd3 /system

to get read/write and go from there.
[Nook Color Q&A, Help & Troubleshooting] KWKSLVR:
I almost suggested that, but it seemed so janky. But what works, works!

Glad you got it running!
[Nook Color Q&A, Help & Troubleshooting] Omega Ra:
yeah, but sadly I had a beta of thumbkeyboard that was expired lolol, then put in perfect keyboard and that didn't show at all...ugh..lol