[Q] brick after flashing blay0 0.7? - Legend General

i'm at a stage where advice would be much appreciated
i just downgraded and rootet and flashed my legend. all went well, after flashing blay0 0.7 i started to set up the phone, and then decided to change the font back to the stock htc font cause i didnt like the one comming with the rom.
installing the stock_fonts.zip from the blay0-thread didnt work as "the package wasn't signed" as i was told. restart from recovery and from there on everything stopped working...
1st problem: legend doesnt mount sd-card
2nd problem: accsessing the legend via adb doesn't work (not found with "adb devices")
and 3rd: my pc suddenly tells me it's missing the drivers for the legend
so all was working as it was supposed to till the point i tried to flash the stock font
so, is there any possibility to install a different rom without adb or sdcard?
any ideas how i can make the legend recignise the sd again?
i'm grateful for any ideas how to save the day...

Follow this guide since you're obviously usb bricked:
http://forum.xda-developers.com/showthread.php?t=751265

Ur are obviously right mate, thanks! Done it this way, everything back to normal...

Related

Recovery Help Needed

Hi all, been a great fan of this forum and had some much info/help from.
I have a Vodafone HTC Magic (32B)
I rooted it and installed the Hero Rom, I used the unlockr method
I used flashrec-20090815.apk and recovery-RAv1.2.1G.img to root it, which worked fine.
I used Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.6 Swap for the ROM, which worked fine.
However upon using the Hero ROM, I wasnt happy with it so wanted to get rid of it and go back to original or maybe use another version of the Hero ROM.
I selected the "format SD: fat32+ext2+swap" option from the system recovery, yes I know silly me. I wasn't fully concentrating when doing it
Now my phone keeps rebooting the Hero screen until I take out the battery.
I can get to the system recovery and the fastboot usb screen, lights are working also. So I don't think it is bricked.
As my phone keeps resetting I can not get my SD Card to mount so I could add the OTA files to the card.
I even installed the USB driver from the SDK package, to see if it would work that way. But to no avail.
I can not access the drive from command prompt either.
I have searched on here, but cant seem to find someone else who has experienced this problem.
Any help would be greatly received.

[SOLVED] 2.1 Rooting issue & GSM Hero (White screen, green htc logo, stuck)

[Solved]
Hi there.
I got hold of this second hand phone.
I dont think its been modified in any way yet.
Last night the phone asked me about doing a update. So i did.
After the green progress bar completed i got to a white screen containing a green htc logo. And its stuck there in a loop.
So... I cant turn my device on... whyyyy? :'(
All i can do is to get into the standard htc recovery.
And into the hboot. Some place there it says:
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.15.11
Aug 4 2009,19:43:30
I have done a wipe and a hard reset. Still it get this white screen on death. (WSOD) Im sodding of to bed...
You now know that it doesnt have a nandroid backup, and that I cant connect the phone via a usb connection to pc. And I dont have any custom recovery installed.
Ive tried to recover from a offical rom with a update.zip copied with a card reader onto the sd. Ive tried a few. The recovery see's the file. But when i try to install it it says "Verification failed Installation aborted"
Ive tried the recovery-RA-hero-v1.7.0.1.img, but without a usb I cant figure out how. Is there a way around for installing RA with just a sd card?
Please, does anyone have a good solution here.
Or some helpfull info to point me in the right way.
Sincererly,
Thor
See these threads similar,... Should be easy to sort.
http://forum.xda-developers.com/showthread.php?t=786938
and http://forum.xda-developers.com/showthread.php?t=787483
Good morning
Thanks, ive been looking at that.
My Win7 pc wouldnt show the ADB Interface in manage devices.
Only thing that pops up is a disk drive called HTC Android Phone USB Device, USB Mass Storage Device and a USB Composite Device.
Im gonna try this on my windows xp machine later today.
Hope it finds my phone, if not... what can i do?
So you need to update drivers as per the link in those threads,... Have you done that already pal?
Sent from my HTC Hero using XDA App
Hi again
Yes, I followed every step on that RUU driver guide on my win 7. But the drivers doesnt pop up as they should.
So I cant install the correct drivers since it doesnt show.
Halfway solution!
I got a breakthrough.
1. Remove the battery and replace it.
2. Hold volume down/up and tap power button. (htc enters hboot)
3. Taps back (enters fastboot)
4. Connects USB Cable (fastboot changes to fastboot usb)
5. Computer finds device My HTC.
Then i run this:
_HTC Hero_RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
I got this from the htc pages. The software says i have ROM version 3.32.405.1
So i have a newer one installed then the one they have on web!?
I choose update on the software, now it tries to install 2.73.405.5
I got a half working usb connection now.
Fastboot restarted and changed to RUU USB.
Then i get a Error: 140 / 131 Bootloader version fail.
Can it be that the hard reset ive done messed up the bootloader version.
For me it looks like the phone is still in a new version ROM.
Anyone vise got anything to say about this?
Kind regards,
Thor
Aha,.... Ok, thats probs because the RUU you're using is older than the ROM already installed.
Try this one... RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6 .35.15.11_release_signed.exe
That is the unbranded ROM,...
Wow
Suddenly everything klicked back into place!
Im past the white screen of death!
That RUU link was flawless for my device.
And the fastboot RUU USB installed everything.
Im back in business.
Much appericated m8
No problem. Now do us a favour and put [SOLVED] into your thread title. Thanks.
So...
Any suggestions on what i should do with it now?
Gotta root it i guess.
Then install recovery RA.
Any suggestions for a good rom to try?
Thanks again,
Thor
theres loads, but my suggestion would be villainrom 12 for a 2.1 sense rom, or froydvillain for a 2.2 rom
Ok
How do i know if i have a 2.1 sense rom or a 2.2 rom?
Or was that a dumb question from me, since you meant to install those?
Im kind of new, just left ye olde nokia behind
lol... Ok,... So you used the 3.32 RUU yeah? That is stock 2.1. If you used the other one, that is 1.5. Use BTDAGs guide in my sig to find out how to flash custom ROMs.
I also recommend Villain 12 for 2.1,... Or Froyd for 2.2. Depends if you like the SenseUI or not. Take a look at both in the Dev section.
Ok
Yes, I definitly want to have the Sense UI.
So then i wanna try out installing a villainrom 12 on a 2.1 sense rom.
Settings - Software Information now says:
Firmware version: 2.1-update1
Baseband version: 63.18.55.06PU_6.35.15.11
Kernel version: 2.6.29-063c4d24 [email protected] #1
Build number: 3.32.405.1 CL191507 release-keys
Software number: 3.32.405.1
This is what i have on it now.
I tried doing the phone software update again, when it asked me again.
Got the same error. So I did the usb install over again. All ok again.
Note: The update it tries out is 3.32.405.2 (5.87MB)
So... can i follow BTDAG's guide from here?
Or do i have to downgrade or update something first?
Guess i have to choose Superuser for Android 2.0~2.2 when i do the rooting with androot.
I got a problem in that guide when typing su in the terminal window.
I didnt get the "Super User Request Prompt" as it told about.
Ive now tried terminal from both usb and the terminal emulator.
WHen i try to do the SU or the flash_image recovery command i get permission denied!?
Without su rights i can do the flash_image recovery /sdcard/recovery.img command, since i need the su permissions.
Thanks again,
Thor
Hi again
I cant seem to get the SU rights i need.
Ive used universal nandroid for the rooting! (it tells its now ok)
But i cant flash in the custom recovery image.
Ive now tried a different approach:
1. Installing the ROM Manager and trying out ClockworkMod recovery(its installs ok)
2. Then I boot into recovery by holding the home(house) and power on, I get the white screen of htc death again and it goes into a black screen with a red triangle and a ! on it.
3. Then I release home and power on.
4. Presses down volume up and taps power on.
5. The hero boots into the standard recovery!?
(I think the way im starting up, are reflashing the recovery. am i right?)
Clockwork also have a "flash RA 1.7 recovery" option, ive tried that one too.
But with the same result...
Any one know about this?
Best regards,
Thor Elvin
Solution for life!
After a lot of surfing i found it!
This great tut worked for my device:
http://www.villainrom.co.uk/forum/s...o-Root-The-2.1-RUU-or-OTA-Update-For-The-Hero
I got a blue carebear in the background, and im making a big grin!
Now im rooted and backed up.
Great thanks to Pulser for a great tut.
Edit: VillainROM12 installed 1
PEACE Y'ALL!!!
QUOTE=thorelvin;8284640]After a lot of surfing i found it!
This great tut worked for my device:
Pulser did...
I got a blue carebear in the background, and im making a big grin!
Now im rooted and backed up.
Edit: VillainROM12 installed 1
PEACE Y'ALL!!![/QUOTE]
Dude, nice that you got sorted. I have kids so Carebears are good to have around. Respect to Carebears, and at the same time it would be cool and revisit the forum and thank Pulser, else thank him here as Pulser_g2 (i think). He sort of wrote, reworked the tut originally from the cdma version here. Sorted me too going 2.1 to 2.2. I had shedloads of fun with roms in between but its only thanks to him.
I guess this could be classed as one of those "Circle of life" philosophy budhist type **** things cuz the answer was really where you started, but for me... its all about takin care of the Carebears....
For the record his contract ends around May so get your Hero fix requests in early...!
Soz Pulser... And massive thanks for the opening to a new dimension for my hero...

[Q]

Hi, firstly I used unrEVOked to root the phone and thought I had backed up the original rom with clockwork recovery. I then installed Cyanogenmod, but due to various issues I want to revert back to the original ROM.I have tried clockwork recovery but it just keeps booting back to Cyanogenmod.
Next I searched for the original rom downloaded it to the phones sd card but if I try to install it it does not show in Clockwor recovery, but when I plug the phone into the pc and open the phones sd card it shows the rom on there.This is what I downloaded....1501_signed.exe(cannot post link in 1st thread)
So what am I doing wrong or what have I done wrong?I had several issues with things not working using Cyanogenmod. Apps were not downloading the clock did not show properly only half of it was visible,amongst other things.And to cap it all I cannot revert back to the original rom.I have obviously made some mistake along the way and I have searched the forums but cant find clear instructions of how to switch back.I am acomplete noob and have tried to run before I could walk!
Any help will be greatly appreciated
Thanks
If you have downloaded a RUU (.EXE), connect your phone to the PC, and run the EXE on your PC. It will proceed from there.
But remember, if you flash a FroYo RUU (Original ROM), you will lose your ability to root the phone. If you want to retain that, download a "Safe" version of the RUU (Untouched, only HBOOT Removed) from here:
http://forum.xda-developers.com/showthread.php?t=877243
(Download WildPuzzle v0.0. Its the original ROM with just HBOOT Removed as stated above)
Hi thanks for the reply, I tried to load that but it eventually came up with :-
Error 131 please get the correct update for your phone,or words similar to that.So how do I know what rom is the correct one for my phone?If I download it to my desktop do I then need to move the zip to the phones sd card then start it with power+ volume down pressed and select the zip from the sdcard?
Thanks
check this out---->http://forum.xda-developers.com/showthread.php?t=807983
or maybe this will help
http://forum.xda-developers.com/showthread.php?t=877091

[Q] USB problems after rooting

Hi all,
Yesterday I tried to root my legend to flash a custom rom (CyanogenMod 7).
Everything worked fine until I decided I also wanted to flash an unsigned Data2Ext zip.
So I first Wiped everything, then flashed CM7 ( successful ) and then tried to flash Data2Ext.
This didn't work (I think the error was something like "no signature").
After that I quit the recovery mode and my legend was stuck in a boot loop. Also, when connecting my legend to the pc and trying to get into recovery mode, my Legend was recognized as being "Qualcomm CDMA Technologies MSM". Windows tries to install drivers but unsuccesful, so I can't get into recovery mode anymore.
The only solution I found to get out of the boot loop was to unroot my Legend again. (Using this guide )
However, I still can't get into recovery mode for the same reason (and thus can't root my Legend anymore).
Also, when connecting my legend with the pc when already booted (I'm back to htc sense android 2.1), it doesn't let me get a good usb connection. My phone is charging, but windows says "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it".
I think these problems might be related, but the first problem is my main concern, as I want to flash a custom rom again.
I've used many search terms, but could not find an answer that would solve my problems. Does anyone know how to solve this?
Note: I don't have root access anymore and am running Windows XP.
Also, the rest of my phone's functions is working correctly it seems.
Hi!
First I would try to install some FOTA, since you obviously can't install anything else... you might look to Shipped ROMs...
(don't install Froyo if you can, you'd probably end up with HBOOT 1.01 which is not that easily rooted, but still can be done...)
As those are most probably properly signed, you should be able to flash them from SD card, so no USB connection needed...(choose LEGEIMG starting archives, .exe needs USB) - the filename to flash from SD must be legeimg.zip
That should fix your USB connection issues I hope...
Then I'd try to re-root (See stickies in Development)
I tried flashing a FOTA (LEGEIMG_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7
.05.35.26L_release_126592_signed.zip) but I think that's the one I already flashed using this topic. It reads the legeimg.zip but doesn't give me the option to update, so I guess they're the same?
For some reason I now also get the "Qualcomm CDMA Technologies MSM" notification when trying to connect as USB Disk station to the computer, so not the "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it" error.
Edit: Now I get the malfunction error again..
Could the solution to my problem be to find the drivers for the Qualcomm thing? And if so, where can I find those?
Edit2: New development;
Legend now freezes completely when connecting to USB. I have to take out the battery to get it working again..
Edit3:
I've taken another look at the hboot screen and it gives me the following info:
LEGEND PVT SHIP S-ON
HBOOT-1.01.0000 <-- isn't that strange, since I'm running 1.31?
MICROP-0816
TOUCH PANEL-SYN07-0103
RADIO-7.05.35.26L
Nov 8 2010,15:24:15
Also, when I try to flash the 2.03 zip from here, it finds the legeimg.zip and asks me if I want to update. When I do so, it tells me "CID incorrect! Update Fail!"
Oh maan, I guess HBOOT-1.01 and 1.31 is not working out then...And since there's no way to downgrade HBOOT, you have to flash Froyo ROM...but to do that you need a goldcard: Here is a HowTo
Then you can flash a ROM with different CID then your own...
note: 2.03 is not Froyo, and since shipped-roms only has RUU, you might look into this: HowTo Extract RUU
And then you just ROOT again
Could the solution to my problem be to find the drivers for the Qualcomm thing? And if so, where can I find those?
Click to expand...
Click to collapse
try using attached driver by replacing the current one on your xp box. had the same problem before. HTH
aw, man! you missed your chance on s-off. anyway, since you're on hboot 1.00+ already (& from the looks of it, you lost your root), Dr Romca's link for rooting should work
Dr.Romca said:
Oh maan, I guess HBOOT-1.01 and 1.31 is not working out then...And since there's no way to downgrade HBOOT, you have to flash Froyo ROM...but to do that you need a goldcard: Here is a HowTo
Then you can flash a ROM with different CID then your own...
note: 2.03 is not Froyo, and since shipped-roms only has RUU, you might look into this: HowTo Extract RUU
And then you just ROOT again
Click to expand...
Click to collapse
Thanks for the help!
However, yesterday I couldn't make a new goldcard, since my device wasn't recognized. I will try to make one again this afternoon, using a W7 machine.
I will let you know the results!
maxq1 said:
try using attached driver by replacing the current one on your xp box. had the same problem before. HTH
aw, man! you missed your chance on s-off. anyway, since you're on hboot 1.00+ already (& from the looks of it, you lost your root), Dr Romca's link for rooting should work
Click to expand...
Click to collapse
Thanks! I will try this as well!
Edit:
Still no luck trying to create a goldcard, since the pc doesn't recognize my device, regardless what type of connection (charge-only, htc sync etc) I select. In windows 7 I also get the device malfunctioned error.
Trying to use the adb command only returns "No Device found" (or sth like that).
Using the driver Maxq1 gave me doesn't seem to work (unless I'm doing it wrong that is)
edit: usb bug fixed
Azaruc said:
edit: usb bug fixed
Click to expand...
Click to collapse
You mean you've rooted your Legend?
I am experiencing the exact same problem as you've described while trying desperately to root my HTC Legend.
I start up Fastboot, run Step1, then go into Bootloader (and also getting the same error message about the .zip file), then Recovery mode, and my computer (W7) recognizes the device at this point as Qualcomm CDMA Technologies MSM, and fails to install the drivers.
When trying to run step2, I get an error message telling me "device not found".
I am also running 1.31 and Hboot 1.01.0000
Would really appreciate some help
I didn't really document my steps (I should have ), but I think the Qualcomm bug was fixed by following this guide.
Let me know if it works out for you.

[Q] please help! G2 is stuck at the htc screen

hey guys,
I am really stuck and don't know what to do. i usually am able to find an answer by searching but I can't find an exact problem like mine so any help is appreciated & thanks in advance.
This morning i flashed cyanogenmod 7 rc 1. At the time I was running synergy rom. Everything booted up fine but i decided to restore back to synergy since i wasnt able to use flash in my browser with cyanogenmod. Upon opening rom manager i was told to flash clockworkmod recovery (which i already had) so i did so, then i tried to restore. I was given an error message saying "the rom manager script failed, open rom manager to report this error & make sure you have rom managar 4" (which i do). i then tried to manually restore my backup from recovery and it froze. now i am stuck at the htc screen my phone will not boot up.
I held down+pwr to get into hboot and it says "vision pvt eng s-off" & radio-26.03.02.26_m. I also tried to click on recovery and the phone sticks at the htc screen. i don't know what to do in this situation. Please help.
Thanks in advance.
Sounds like you've had an issue with the new cwm recovery. You're not the only one. Sounds like your best bet is to try and flash the recovery through fastboot.
Sent from my CM7-powered T-Mobile G2
http://forum.xda-developers.com/showthread.php?t=1243327
I'm also one of those who had fits with CWM Recovery 5.0.0.1/5.0.1.0 (and downgraded back to 3.0.2.4 as a result).
Basically the recommended procedure is as follows:
a) Pop the battery
b) Reboot (it should behave this time)
c) Go into ROM manager, go to "All ClockworkMod Recoveries", select 3.0.2.4, click "OK", let it do its magic.
d) Grumblemuttergrr over the idea of upgrading when something wasn't broke
If that doesn't work, http://forum.xda-developers.com/showpost.php?p=17157985&postcount=19 explicitly gives instructions on how to restore 3.0.2.4 via fastboot (adb required, but not as scary as it sounds).

Categories

Resources