[Q] USB problems after rooting - Legend General

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.

Related

Sorry to be such an idiot but...

I was trying to upgrade my SX66 from the factory Windows2003 to WM6 with this HELMI_BA_WM6_R0_ installer. I started the install and it crapped out giving me an error saying that it could not communicate with my device and that I needed to plug my device back in and retry it. My SX66 is now stuck on the bootloader as I'm sure the ROM isn't complete, and the installer does nothing now. Can someone please help this noob out? I'd really like to have my phone back lol.
N1cholas said:
I was trying to upgrade my SX66 from the factory Windows2003 to WM6 with this HELMI_BA_WM6_R0_ installer. I started the install and it crapped out giving me an error saying that it could not communicate with my device and that I needed to plug my device back in and retry it. My SX66 is now stuck on the bootloader as I'm sure the ROM isn't complete, and the installer does nothing now. Can someone please help this noob out? I'd really like to have my phone back lol.
Click to expand...
Click to collapse
Did you unlock the device first?
In any case, just try to reflash your device back to WM2003 with a stock rom. It does seem to be a bad flash. Also, which OS are you using (XP or Vista)?
Follow this in order to perform the upgrade properly...
Good luck!
egzthunder1 said:
Did you unlock the device first?
In any case, just try to reflash your device back to WM2003 with a stock rom. It does seem to be a bad flash. Also, which OS are you using (XP or Vista)?
Follow this in order to perform the upgrade properly...
Good luck!
Click to expand...
Click to collapse
I'm running windows version 7. and no i didn't unlock the device. i just ran the installer application (i hadn't found a detailed install manual) i'm not entirely sure how i can re-flash now, because i can't get a usb connection made because it's stuck in the bootloader.
N1cholas said:
I'm running windows version 7. i'm not entirely sure i can re-flash now, because i can't get a usb connection made because it's stuck in the bootloader.
Click to expand...
Click to collapse
By bootloader, do you mean the three colored screen?
egzthunder1 said:
By bootloader, do you mean the three colored screen?
Click to expand...
Click to collapse
no, the screen that says serial/usb at top and 2.07 at bottom
I just wanted to make sure that we were on the same page
In my opinion (and this is just a theory), Windows 7 (since it is a beta) does not have the necessary drivers to recognize the "usb device". Hence, when you put it in the cradle, it just doesn't see it. Again, this is just a theory...
You may want to get a hold of a machine with XP (that is if you didn't make the one you are using a dual boot). You should be OK if you try to flash via XP.
If everything else fails, you can always use mtty and flash via SD card (the procedure can be found in the wiki).
I had the device synced up before the install. it's just having issues syncing while it's in the bootloader mode. The device actually appears in the usb devices, but doesn't sync. i was thinking that the device might have to be authenticated with local software(on the sx66) in order to sync. I'm using the windows vista drivers. I do have this machine dual boot, but it's not any other version of windows i'm using
Your device does not have to sync in order to up/downgrade. Think about it this way... the RUU will put the device in bootloader anyways.
Just run the installer of the stock rom (the upgrade from Cingular).
@N1cholas: Please correct me if I'm wrong. I'm just a little confused. Are you expecting MS Active Sync to show as it usually does when you are syncing your phone? If that is the case, it won't happen when on boot loader. Are you getting any error when trying to flash or you haven't tried to flash yet?
Advise:
1. Keep your hopes, don't get despert. Egzthunter is a master
2. Make sure you follow the guide... Step by Step to upgrade.
3. If it'll take you too long to complete the reading and flashing, reset your phone and put it to charge. You won't be able to flash with a dead backup battery. Main and Backup battery won't charge while on bootloader.
Edit: @Egzthunder: Sorry mate, while I was thinking, drinking coffee and writing you had already replied Like I said, your the help master. Once again, I encourage the MODS to propose you to be part of their teem. You're always there to help.
Mark
i'm going to head off to school, but it's not working. when i try to run any mods i get an error saying that it cannot communicate with device.
Yeah! Egz for MODS!!! Woohooo and Xplode too and someday..me! LOL (no i mean it!)
windows 7 uses the same drivers as vista
beakybal4 said:
windows 7 uses the same drivers as vista
Click to expand...
Click to collapse
Why do you think I don't trust it?
@N1cholas,
I apologize since I ended up going to bed yesterday night.
I think your best bet will be to find yourself a PC running XP and try the reflash in that since it seems to me that something is going on with the OS.
@red and mark
Thanks for the support, guys!!! But you guys are awesome as well!
yeah, it's weird, it's just not working anymore. It appears in the device list and everything, but in WMDC it doesn't show up, and the rom install wizzards can't communicate with it either. I have been unable to find the upgrade ROM from cingular as it seems that the siemens' page has been removed. Also, I have a 2gb SD drive, but haven't been able to find information about flashing the SX66 from the SD.
N1cholas said:
yeah, it's weird, it's just not working anymore. It appears in the device list and everything, but in WMDC it doesn't show up, and the rom install wizzards can't communicate with it either. I have been unable to find the upgrade ROM from cingular as it seems that the siemens' page has been removed. Also, I have a 2gb SD drive, but haven't been able to find information about flashing the SX66 from the SD.
Click to expand...
Click to collapse
You will not see the device in any type of sync software (call it ActiveSync, WMDC, etc). I hvae uploaded the SX66 stock installer from Cingular, so give that a shot
Here you go
SX66Update.exe
Like I said... XP computer. Also, for the SD flashing, you need to look for something called mtty and instructions on how to use it.
the proper solution
1.MTTY method for unblocking bootloader mode
2.Upgrade the same way as in Vista to stock rom
3.Sim Unock, Repartition DOC
4.Upgrade vista way to any rom you like
there are guides in WIKI about this
egzthunder1 which version extrom version and radio are in this rom - the one you sharing? As you know i make public BA shipped rom collection, and any rom which is not there is welcomed
xplode said:
the proper solution
1.MTTY method for unblocking bootloader mode
2.Upgrade the same way as in Vista to stock rom
3.Sim Unock, Repartition DOC
4.Upgrade vista way to any rom you like
there are guides in WIKI about this
egzthunder1 which version extrom version and radio are in this rom - the one you sharing? As you know i make public BA shipped rom collection, and any rom which is not there is welcomed
Click to expand...
Click to collapse
Hey xplode,
To be perfectly honest, I haven't flashed 2003 since 2006, so I would be lying if I told you. Feel free to add it to your database if you wish. FYI, this is the upgrade that Cingular Wireless used to offer when the SX66 was still available in the at&t website.
MTTY doesn't have a USB option, it's only giving me COM1, COM2, COM3...
N1cholas said:
MTTY doesn't have a USB option, it's only giving me COM1, COM2, COM3...
Click to expand...
Click to collapse
Did you try the update that I gave you?
i ran it, and it said it was trying to get the settings from the device, then it just disappeared lol. now when i run it, it extracts the install data to the temp folder on my pc, then just disappears

Radio 2.x non-root DI return

I recently updated my radio from 1.x to 2.x in the quest to improve my reception. However I will be going to return my DI to VZW soon for a replacement (since they believe that my phone is deflected). Do I need to downgrade my baseband back to 1.x or is it still in good shape for return?
My DI is not rooted.
Thanks for any response.
You should be fine but it wouldn't hurt to be safe
Sent from my ADR6300 using XDA App
Do you know how I should start with that?
Since my DI is not rooted, I guess I would start with the file RUU_IncredibleC_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_release_161494_NoDriver_0514.exe and skip the hboot thing step.
Correct me if I am wrong.
I tried the method that I suggested above. I have this USB error problem.
At first, the process went smoothly. The utility detected my WWE, and then it reboot my phone. Then I got the ERROR 171 USB Connection problem, then later I kept getting ERROR 170 USB Connection problem while the utility was trying to verify my phone. The only fix is to removed/reinstall HTC Sync and driver, but then I got back to error 171, then 170 there after.
Anyone have this problem?
Basically follow the steps outlined here. It's a good idea to revert it back to the original radio.
http://androidforums.com/all-things-root-incredible/123816-how-revert-back-earlier-version-hboot.html
After half a day, I finally got it back to the original state.
I had to root my phone first using unrevoke 3.
While unrooting, my DI refused to update saying that "Main Version Older!" I tried the method in the link from UndergroundWire, but I constantly got USB error message, even with the workaround (copy files from sdk/tools to temp folder), but in the process, a file names rom.zip is generated. I only had to rename that file into PB31IMG.zip, place that file on root directory of my sdcard (fat32), then boot into hboot, and it worked (no more older version complaint).
Thanks for all the helps, guys.
hkii said:
I tried the method that I suggested above. I have this USB error problem.
At first, the process went smoothly. The utility detected my WWE, and then it reboot my phone. Then I got the ERROR 171 USB Connection problem, then later I kept getting ERROR 170 USB Connection problem while the utility was trying to verify my phone. The only fix is to removed/reinstall HTC Sync and driver, but then I got back to error 171, then 170 there after.
Anyone have this problem?
Click to expand...
Click to collapse
I've found for RUU to work you have to install HTCSYNC and then run the RUU program again. After it's done I simply uninstall HTCSYNC and the HTC Drive (something about HTC drivers in the Wondows UnInstall screen). Make sure your phone is unplugged when you Install and UnInstall HTC Sync and the Drivers.
After HTCSync is gone the system reverts back to the modified SDK drivers, you do have those already installed I hope?
Good luck

[Solved] How to restore to stock when RUU doesn't work?

Hi!
So.. My HTC Hero GSM has some issues that need to be repaired. Touchscreen not working in the lower part of the screen, constant headset-icon, trackball not working good. So I've contacted my repair center and they told me to send it in. So I want to restore my phone to as close to original as possible to be on the safe side.
The problem is I can't use the official RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe(or any other version), without getting an error 155(apparently it has something to do with the rom not having correct filesize).
It doesn't matter what rom I'm currently using; Modaco, Villain, different kind of generics, but nothing affects the outcome.
I got a feeling it has to do with the recovery image I use(RA 1.6.2) or Hboot version(.0007), but I can't seem to flash a new one. Recovery flasher gives me "Backup FAILED: could not run command.", and since my HBOOT is .0007 I can't use remote command from fastboot to restore original.
1. Is it possible to downgrade HBoot from recovery mode? If so, does anyone have a update.zip I can use?
2. Could error 155 has something to do with the computer/OS im using?
3. Anyone has any other suggestions what I can try to restore?
Currently using:
HTC Hero GSM
Generic 2.73.405.38 (1.5)
Baseband 63.18.55.06OU_6.35.15.01
HBoot 1.76.0007
Any help is greatly appreciated!
/Jakob
Edit: Solved!
For anyone having issues with Error 155(CID-checks fail, perhaps?) or 171(USB fail) while trying to restore a rooted HTC Hero to stock with an official RUU-exe, this is what worked for me where nothing else did:
- Create Goldcard
- Extract ROM.ZIP from the Official RUU exe you want to use. I downloaded it from their main site
- Rename to HEROIMG.zip
- Boot to flashboot mode (Volume down + Power on)
- Flash.
- Reboot and enjoy your new stock HTC Hero.
1. Yes. There is an engineering hboot over at modaco (v2007).
2. No idea. You could just try re-downloading the RUU and doing an md5 check on it, might have been corrupted during download.
3. I forget what 3 was and I can't check cause I'm posting through tapatalk.
Hi!
Thanks for your fast reply.
I successfully flashed Hboot with 2007 and later with 0004, but it didn't make any difference when I tried to run the official RUU. I still get error 155 ("Unknown error").
I have since double, triple and quadruple-checked the download to make sure I've got the right RUU. And since I download it from HTCs official site, in the country where it is bought, it shouldn't be an issue. All the downloads I've made is also the same size..
I guess my last resort will be to try to flash the stock recovery image manually.
Anyone have that one lying around?
Du you have HTC Sync installed? Usb debugging on in the phone? Try flashing the RUU, when in fastboot. (VOLDOWN+ON)
I'm not sure what error 155 is.
HTC Sync installed, enabled on the phone. And the green little icon is green and the phone says connected. Usb debugging is enabled.
I will try starting in fastboot mode brb.
That didn't work either.
Still got error 155 Unknown error.
I also tried to restore my original recovery image in fastboot:
fastboot boot cm-hero-recovery.img
Click to expand...
Click to collapse
An this is what it said:
Downloading 'boot.img' ... FAILED (command write failed (Unknown Error)
Click to expand...
Click to collapse
The "unknown error" appears even here. Could it be that my phone is so broken it cant write to that area?
If you have access to recovery
Try;
HTC Generic 2.73.405.5 (update.zip)
http://www.romraid.com/paul/hero/update-hero-generic-2.73.405.5-signed.zip
if that fails try;
Goldcard Method
http://forum.xda-developers.com/showthread.php?t=572683&highlight=gold+card+method
if that fails try;
...... try the first 2 first then post back results. (Might be worth trying on another computer because unknown error 155 sounds like there could be an issue somewhere with the pc. Maybe build an XP vmware?
andrewb84uk said:
Try;
HTC Generic 2.73.405.5 (update.zip)
Click to expand...
Click to collapse
Already tried. Unfortunately didn't work.
andrewb84uk said:
if that fails try;
Goldcard Method
Click to expand...
Click to collapse
I did it, and now have a goldcard. Unfortunately I still get error 155. I also tried all this from a different computer than before. This time with win 7, but with no other result.
I guess next step will be to try it from XP. I will setup an virtual pc later and try it, but I have to admit I'm not hopefull... This is getting annoying.
Any other way you guys can think of? And I REALLY appreciate your help, this is driving me mad!
jakobahman said:
Already tried. Unfortunately didn't work.
I did it, and now have a goldcard. Unfortunately I still get error 155. I also tried all this from a different computer than before. This time with win 7, but with no other result.
I guess next step will be to try it from XP. I will setup an virtual pc later and try it, but I have to admit I'm not hopefull... This is getting annoying.
Any other way you guys can think of? And I REALLY appreciate your help, this is driving me mad!
Click to expand...
Click to collapse
Can you provide some screenshots, best thing you could do is do it from a fresh XP machine if you can.
Im setting up a new virtual xp just for this.
Ill be right back with some screens...
i usually do it thru the SD card
SiL3nTKiLL said:
i usually do it thru the SD card
Click to expand...
Click to collapse
I'm not sure what you mean. What do you do through the SDcard? And how?
jakobahman said:
I'm not sure what you mean. What do you do through the SDcard? And how?
Click to expand...
Click to collapse
HEROIMG via fastboot maybe?
But isn't that the same as using recovery mode to flash a rom?
As I stated previously I want to get my phone as close to stock as possible(ROM, Radio and recovery). Can this be done with HEROIMG? Am I missing something here?
jakobahman said:
But isn't that the same as using recovery mode to flash a rom?
As I stated previously I want to get my phone as close to stock as possible(ROM, Radio and recovery). Can this be done with HEROIMG? Am I missing something here?
Click to expand...
Click to collapse
I do believe... if you use the rom.zip taken from when you launch the RUU (remember to unhide hidden files) this also does radio hboot e.t.c. I did it with the tmobile rom and it did update radio. Rename it to HEROIMG.zip, put it on the root of the sdcard, boot into fastboot and it will find it and flash.
This is the contents of a rom.zip direct from an RUU i did tonight.
@android-info.txt
@boot.img
@hboot_7200A_1.76.0007_090804.nb0
@radio.img
@recovery.img
@splash1_Hero_TMO_G2_Touch.nb0
@system.img
@userdata.img
YES!!!
Finally!
Thank you Andrew and Silentkill!
For anyone having issues with Error 155(CID-checks fail, perhaps?) or 171(USB fail) while trying to restore a rooted HTC Hero to stock with an official RUU-exe, this is what worked for me where nothing else did:
- Create Goldcard
- Extract ROM.ZIP from the Official RUU exe you want to use. I downloaded it from their main site
- Rename to HEROIMG.zip
- Boot to flashboot mode (Volume down + Power on)
- Flash.
- Reboot and enjoy your new stock HTC Hero.
Thanks again for all the help!!
jakobahman said:
YES!!!
Finally!
Thank you Andrew and Silentkill!
For anyone having issues with Error 155(CID-checks fail, perhaps?) or 171(USB fail) while trying to restore a rooted HTC Hero to stock with an official RUU-exe, this is what worked for me where nothing else did:
- Create Goldcard
- Extract ROM.ZIP from the Official RUU exe you want to use. I downloaded it from their main site
- Rename to HEROIMG.zip
- Boot to flashboot mode (Volume down + Power on)
- Flash.
- Reboot and enjoy your new stock HTC Hero.
Thanks again for all the help!!
Click to expand...
Click to collapse
Well done... for a final outcome the error 155 means there is an issue with settings and if you get an error 155 more than likely a new windows setup will need to commence somewhere. (Install XP, Windows 7 et all. Error 171 is a usb driver issue to the phone I do believe.... glad to be of an assistance.
I don't think it has something to do with the OS. I tried the RUU .exe on three different setups; One laptop with Vista, one brand new laptop with Win7 home premium and one virtual PC with XP.
Maybe a "full" setup of XP would work, but I think it's more likely it is something else.
On the other hand, to just remove the OS from the equation solved it, so you might be right.
Oh, and the 171 error only occurred when the driver got messed up one time, so it really hasn't got much to do with my case. But this solution would work for people having that issue as well.
jakobahman said:
I don't think it has something to do with the OS. I tried the RUU .exe on three different setups; One laptop with Vista, one brand new laptop with Win7 home premium and one virtual PC with XP.
Maybe a "full" setup of XP would work, but I think it's more likely it is something else.
On the other hand, to just remove the OS from the equation solved it, so you might be right.
Oh, and the 171 error only occurred when the driver got messed up one time, so it really hasn't got much to do with my case. But this solution would work for people having that issue as well.
Click to expand...
Click to collapse
The errors are system related, thus when you use the HEROIMG.zip via fastboot you totally bypass the need for having a PC except to transfer files to the device. So I think it is a driver/OS issue.
EDIT: To the OP, edit your first post and add [SOLVED] to the front.... let users know there is a solution.
I hope you guys can help me, i have a G2 Touch and i'm about to try restore to stock by using SD-Card.
Problem is, when i unpack the RUU.exe (Firmware 2.73.111.26), there's no ROM.zip in it. Only thing i get is a Subfolder with several installation files and a data1.cab sized 104MB, which i can't open (nether with 7zip nor winrar)

[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...

[Solved][Q] Help needed for Nandroid Restore...

Hi,
Posting a new thread since I could not find any thread that could address my issue. If there is one, pls point me to it.
I have a GSM Hero. I flashed Froydvillain 1.7.2 ROM on it. However, for some reasons, I want to go back to stock 2.1 HTC ROM.
After rooting the phone, I had created a backup with Nandroid. However, when I try to restore it using Nandroid, I get following msg -
.android_secure.img not found Skipping restore of applications on external storage', and then also something about skipping restore of /sd-ext
After this, it says restore complete.
When I reboot, I am stuck on the Airtel screen (HTC India). Can not go past it.
Can anybody tell a way to load stock 2.1 ROM?
Thanks in advance.
I'm not sure, but it could be a missing file leading to a corrupted backup. If that is the case you can either get a stock 2.1 rom in zip form
(like this one for exemple http://forum.xda-developers.com/showthread.php?t=714075) or you could un-root by running a RUU (rom update utility) and remove the patched recovery image, in effect restoring your phone to factory condition.
There's a decent guide on how to do that here.
Hi,
Thanks for reply.
I actually prefer theunloackr.com method of unrooting. However, the problem is that since I am having a Froydvillain ROM, I can't use HTC Sync with it. So, can not use the RUU.
I think first installing the zipped generic OTA you mentioned and then using theunlockr.com method will do the thing for me. Isn't it?
Are there any other zipped RUU?
Thanks again
Just boot your phone into bootloader, plug it into your computer, and make sure it is on hboot-mode (it shows HBOOT on the screen) then go into Device Manager on Windows and look for "Android USB Devices" - if the device under there is named "My HTC" then everything is fine and you can start the RUU.exe, but if it's not you will have to update the driver with the one installed with HTC Sync (probably located in C:\Program Files\HTC\HTC Driver\Driver Files\(Your OS here)\ ) then it should be named "My HTC" and you should be able to go on
Hey...
mljjlm said:
Just boot your phone into bootloader, plug it into your computer, and make sure it is on hboot-mode (it shows HBOOT on the screen) then go into Device Manager on Windows and look for "Android USB Devices" - if the device under there is named "My HTC" then everything is fine and you can start the RUU.exe, but if it's not you will have to update the driver with the one installed with HTC Sync (probably located in C:\Program Files\HTC\HTC Driver\Driver Files\(Your OS here)\ ) then it should be named "My HTC" and you should be able to go on
Click to expand...
Click to collapse
**
I hope you can imagine the feeling of relief...
The Android USB device listed is indeed 'My Hero' so I hope it is completely safe to go ahead with RUU....
I have downloaded India RUU from some site...however can you tell me where can find authentic RUU?
Thanks again...
There has to be a thread with all the roms for the hero... including the official ruu. Also, you could try the xda wiki.
Sent from my HTC Hero using XDA App
Is it Generic HTC or is it branded in any way? If it's branded you will find it at your carriers homepage (hopefully). If it's generic you will find it on htc.com
androguns said:
**
I hope you can imagine the feeling of relief...
The Android USB device listed is indeed 'My Hero' so I hope it is completely safe to go ahead with RUU....
I have downloaded India RUU from some site...however can you tell me where can find authentic RUU?
Thanks again...
Click to expand...
Click to collapse
I usually go here: http://shipped-roms.com/index.php?category=android&model=Hero
They are all authentic and if one isn't compatible with your phone it should just say so (though the latest one with asia in the name should probably work).
Thanks
Hello all,
The issue is solved now.
I am back to the stock ROM.
I found that the method suggested by mljjlm worked perfectly for me.
The issue I faced was: Going back to stock HTC Hero 2.1 ROM from a rooted, Froydvillain 1.7.2 ROM
1. I had already downloaded appropriate RUU from following link -
http://shipped-roms.com/index.php?category=android&model=Hero
2. I followed confirmatory steps suggested by mljjlm in the post above
3. Just plugged in Hero to PC via USB cable, and ran the RUU. This pdf from HTC website tells more about running RUU (for a different device, but same procedure) http://www.htc.com/uploadedFiles/Co.../Touch_Detailed_RUU_Instructions_07152008.pdf
That's it.
Thanks all for help.

Categories

Resources