Related
Hi everybody,
I look through the threads and I couldn't find a solution to my troubles. So here it is: I just bought a htc touch pro 2 which came with a window mobile 6.1. Before I transferred anything from my old phone, I thought better to do the official upgrade to 6.5 ROM version 1.86.401.0.
I wanted to flash the ROM through a USB cable as described on the HTC site, but after after having done 22% of the work, everything got stuck. And 5' minutes afterward the update windows on the PC disappeared and I had to disconnect the phone!!!
So now I have a beatiful telephone, which cannot boot up. Indeed, it gets stuck in the 4 colors bootloader.
i) I tried to do a factory reset (pressing power, send hang up buttons) to no avail.
ii) I tried to take out the batteries and pull them in again, then switching on the phone holding down the vol down + power up buttons, then reset.
iii) reconnecting the phone back to the PC by usb, I was never able to get a switch from "serial" to "usb"
Nothing is working, if anybody has an idea what I could try next.... I am wondering if it is possible to flash the phone from the SD card. I am really a newbie here.
Thanks
Max
Yea .. same thing happened to me ..
Check Here For Full Info: Click Here
*Go into BootLoader Mode (do a Soft Reset while holding the "volume down" key on the left side of the device. Keep holding the "volume down" key until you see tricolour screen which is the bootloader mode, then release it)
Flashing Via MicroSD Card
1. Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
2. Download your prefered Rom from the Rhodium Rom Develpoment Page and unzip/unrar it to your PC
3. Goto the Roms Folder and rename the .nbh file to RHODIMG.nbh
4. Copy the RHODIMG.nbh file to the root of your MicroSD Card
5. Plug the MicroSD Card into the phone
6. Enter the BootLoader screen, you will first see a tri-color screen with the phone and SPL Information at the top
7. Follow the On Screen instructions to start the update
8. After flash has completed, press the reset button with the stylus to reset the device.
Good Luck ! Worked For me !
Thanks for your help and the link to the thread!! I will use your approach next time. Indeed, in the day afterwards I was able to finally flash the phone from the same PC. I did the manipulation, which failed miserably, with a 64 bit Windows 7 RC. Then, I realised I had another version of W7 on the same PC, a 32 bit version this time. Thus, when I tried it with my dying telephone, the "serial" message on its screen switched "magically" to "usb" and I finally could flash the damned mobile! Frankly, I don't know what's wrong with my 64bit W7 if anything.
Cheers
Max
my htc pro2 failed upgrade: any help
WarlockW said:
Yea .. same thing happened to me ..
Check Here For Full Info: Click Here
*Go into BootLoader Mode (do a Soft Reset while holding the "volume down" key on the left side of the device. Keep holding the "volume down" key until you see tricolour screen which is the bootloader mode, then release it)
Flashing Via MicroSD Card
1. Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
2. Download your prefered Rom from the Rhodium Rom Develpoment Page and unzip/unrar it to your PC
3. Goto the Roms Folder and rename the .nbh file to RHODIMG.nbh
4. Copy the RHODIMG.nbh file to the root of your MicroSD Card
5. Plug the MicroSD Card into the phone
6. Enter the BootLoader screen, you will first see a tri-color screen with the phone and SPL Information at the top
7. Follow the On Screen instructions to start the update
8. After flash has completed, press the reset button with the stylus to reset the device.
Good Luck ! Worked For me
i tried this option but didn't work, is there any help, the phone can't come up again
it show this Error msg at 0% "BOOTLOADER - FAIL" update terminated
Click to expand...
Click to collapse
larryike said:
i tried this option but didn't work, is there any help, the phone can't come up again
it show this Error msg at 0% "BOOTLOADER - FAIL" update terminated
Click to expand...
Click to collapse
\
Did you try the stock rom from HTC loaded over the usb first?
Information about what unlocker you tried to use, what kind of phone you have, what kind of rom you tried to load would be helpful.
I can't get my Diamond to talk to activesync on two machines (one of which it used to be fine with). Given that, is it possible to flash it? What's the procedure?
Kallisti said:
I can't get my Diamond to talk to activesync on two machines (one of which it used to be fine with). Given that, is it possible to flash it? What's the procedure?
Click to expand...
Click to collapse
look in my sig
...
enter bootloader and plugin to pc. and pray it got detected as mobile device in device manager. if it does, run ruu.
if not, here's a work around.... turn on phone. go to setting > connection > usb to pc > and change to connect as storage device.
plugin to pc and copy .nbh file of your choice to internal storage (rename .nbh file to diamimg.nbh) (which will be most likely detected as a usb drive)
use stylus and reset phone. hold vol down and back button.... you'll be in bootloader and soon a screen will pop up "triggering movinand bla bla bla..."
press power button to start flashing. when done, use stylus to reset again, now press vol down and circle.
hard reset device > press vol up to continue.
wait for device to self customize.
by the way, this might not work.
Brilliant - updating it now. Thanks guys
So I currently have LightNHB flashed. Since WinMo wont work via USB until I check that one option (forget off hand) I can't establish a USB connection to flash my phone. I tried putting the RAPHIMG.nbh into my SD cards root but that also didn't work, during the boot it said there were no images to flash.
So I removed the Android OS files and reformatted my SD card then places the img file into the root again, and again no image was found.
How would I fix this issue? I cannot seem to flash my phone back to a different WinMo rom.
Got into LightNHB and it has no settings for the USB, it's all in ITA and only one thing I could find in the menus and it gives an error that the file cannot be found. Talk about bare-bones, no wonder I couldn't get this to connect to USB, I don't think it has the ability to.
Ideas?
Pull the battery, SIM(if you have one) and microSD card out.
Press and hold the volume down button while plugging in the USB cord and it should take you to the tri-color screen.
If you haven't already let go of the volume down button, do so now.
You should be ready to flash another ROM!
n-Joie!
R^7Z said:
Pull the battery, SIM(if you have one) and microSD card out.
Press and hold the volume down button while plugging in the USB cord and it should take you to the tri-color screen.
If you haven't already let go of the volume down button, do so now.
You should be ready to flash another ROM!
n-Joie!
Click to expand...
Click to collapse
Didn't know I could be like that but, sadly, error 260; followed to the letter :/
I can't get it to recognize .nbh. When I was able to get into the WinMo of LightNBH it seems it's WM5? CDMA? On my GSM phone... I know my version is dual CDMA and GSM. Though I use the latter.
It has HardSPL because Tri-colour screen says 1.90.OliNex
Can you get it to recognize USB in said bootloader mode? You should be able to flash from your PC using bootloader mode...
arrrghhh said:
Can you get it to recognize USB in said bootloader mode? You should be able to flash from your PC using bootloader mode...
Click to expand...
Click to collapse
No, from what I can gather LightNBH doesn't have the stock USB connection info included in WinMo. Settings > Connections was empty. In fact all of it is empty (settings), I couldn't get to my SD card to run cab files to give me control over my phone.
Is there anyone else running the LightNBH flash that can confirm this? I can't even establish a USB line within Android.
Ventrik101 said:
No, from what I can gather LightNBH doesn't have the stock USB connection info included in WinMo. Settings > Connections was empty. In fact all of it is empty (settings), I couldn't get to my SD card to run cab files to give me control over my phone.
Is there anyone else running the LightNBH flash that can confirm this? I can't even establish a USB line within Android.
Click to expand...
Click to collapse
Hrm, I figured bootloader mode would be separate from WinMo entirely... so not having usb drivers in WinMo should effect it.
So you're saying when you're in bootloader mode, and you plug in USB it still just says "serial"?
arrrghhh said:
Hrm, I figured bootloader mode would be separate from WinMo entirely... so not having usb drivers in WinMo should effect it.
So you're saying when you're in bootloader mode, and you plug in USB it still just says "serial"?
Click to expand...
Click to collapse
It doesn't even say serial.
Code:
RAPH100
SPL-1.90.OliNex
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36
That's all my boot-loader says and I didn't think drivers had any effect here but as it sits I get an error 260 unable to connect from the ROM updater's that came with Monfro, TAEL, and Energy, as well as Task_29.
Erm... It should definitely say "Serial" near the bottom. Give it 10 secs or so...
When you plug into USB, that should convert to say USB...
Did you remember to rename the .nbh file into "RAPHIMG.nbh"? You could also use a sd card adapter or another device that has working usb storage that takes micro sd cards and then drag the .nbh file on the sd card via another device.
See what happens when we get in a hurry? At least that's how i ended up with Litenbh on my TP stuck in a boot loop.
I tried the PWR + VOL DN while soft resetting. No luck. Then i was going to try holding those 2 buttons while plugging it in to USB, I was holding the buttons as i unplugged it. It jumped to the serial screen as soon as i unplugged it.
I'm sure you have gotten this fixed or a new phone by now, but in case ur as broke as me, and still playin with a TP cause you HAVE to.
Maybe this will help. Hold power + volume down while plugging/unplugging it from the PC. Might get lucky like i did.
I know it says Development discontinued, but the TP is old enough that the info i'm looking for is getting buried. Most d/l links i find are dead now, so i'm getting jumpy on the clicker finger.
But I for one think this link and the file itself needs to be taken down. I know it's only 2 of us so far, but dangit what a pain!!!
http://forum.xda-developers.com/showthread.php?t=601751
EDIT: Wow i didnt realize this thread was that old also.
Alltel Touch Pro (yeah it's old, and the keyboard doesn't work)
Using Updated Alltel ROM from HTC site.
Hmmm...
FroYo thread
Gingerbread thread
And yes, this are continuing projects...
Please read the first few posts before attempting anything. It's really does not hurt to try but your experience may vary slightly if you don't know what you are doing.
On that note, I am PMing the thread OP/forum mod to see if there is a way to link to the continuing project threads.
Actually the first post in that thread that you make mention of, has a link to the continuing project.. heh
[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work
Hi guys,
I've watched the n00b video and been googling for the last few hours as well as reading through various pages on the XDA forum. I've found a lot of problems that are kinda similar and tried various solutions but don't seem to be quite getting there.
Basically I had Virtuous Affinity as the OS and clockworkmod installed (should be the most up to date versions of both, they were put on no more than a week ago) as well. I also had a backup of current OS and so on on the SD card, as well as the original zip of the rom.
I decide I want to give ICS a go and so I downloaded the betamod ICS and then loaded it. It asked me if I wanted to do a dalvik cache wipe, a dalvik cache + data wipe and a third option I don't recall. I went with the dalvik cache wipe (at the time I was under the impression that was the correct course of action) then put it back in my pocket while ICS installed.
I get my phone out of my pocket later and it's kinda stuck on what looks like (but logically isn't, I'm guessing it was meant to be a splash screen type thing while ICS installed or some such) a screensaver which just loops endlessly. The only thing you can really do is take the battery out and turn her on again, in which case you once again end up in the endless screensaver loop.
I've tried booting to recovery using volume - and the power button and unfortunately it just boots straight into the looping screensaver again.
Getting a bit worried and feeling adventurous I tried seeing what I could do with ADB, however the computer seemed unable to recognise that any device was connected with ADB devices not listing anything.
I've read up a lot and I'm at a loss as to what to do - there's a rom on the SD card and there also should have been a backup but I just can't get it into recovery.
I do have the ability to view the SD card on another device and interact with it, so if there's a potential SD fix, that's certainly not out the window.
But yeah, I'm clueless how to proceed here and very green at the whole rom business. Can anyone advise what I might try to do from here? I don't care what state I end up going back to, or if I lose my data, I can get all that back, I just want the phone in some semblance of basic operation.
I'll be keeping an eye on the thread, if I've left out any pertinent data ask away and thanks in advance for anyone with a clue how I can fix this mess .
EDIT: Post may be better off in ICS thread above and I do apologise if so, I would move it but I seem unable to delete it.
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
ik222 said:
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
Click to expand...
Click to collapse
I have, it doesn't work. I've left the battery out for a fairly long period. Volume - + power still just brings it back to the "screensaver" loop.
Thanks for the suggestion though.
Turn the phone off completely; pull the battery out for a bit then replace it and don't touch anything. Don't try to turn it on. Plug the phone by usb to your pc (still turned off). At the command prompt in the folder containing adb.exe type "adb reboot recovery" - the phone should power on and go to recovery where you can wipe properly and reflash whatever you want.
You should be able to boot to recovery using the volume down + power button combo (hold the volume-down key, then press and hold the power button and keep both held until you get to the bootloader menu); the only thing that's wrong with your phone is that you've flashed one ROM over another without wiping it first, so the ROM can't load but this shouldn't affect your bootloader or recovery.
Worst case you can flash a RUU which will restore it to the official firmware; you'll then need to re-root and re-install a recovery image to be able to flash custom ROMs again.
Very helpful post, thanks! I'll try all that and see how I go, I'll post if I still have trouble.
Yeah I dunno why I can't boot to recovery it's weird. The volume button wasn't working, so I removed it and am pressing in the volume down portion of the volume button with a pen while holding down the power button. It's possible perhaps I'm not successfully depressing volume down, but I'm 99% sure I am and that that's not it. I am however doing it as you and other guides advise, depress volume down, hold it and then depress power and hold both for about three seconds, no joy!
Anyway, as said, I'll try what you're recommending and see how I go. Thanks!
hopscotchjunkie said:
At the command prompt in the folder containing adb.exe type "adb reboot recovery"
Click to expand...
Click to collapse
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Ethicistabdiel said:
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Click to expand...
Click to collapse
Yeah that was what I meant; I've got a feeling that that only works when the phone is powered off if you had USB debugging activated on the phone beforehand, so if that's not working that might be why.
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Accidental double post, sorry.
You need to try get into recovery mode, where you can do a full wipe and see if that fixes anything.
Firstly, remove your battery then re-install it, your phone should still be turned off at this stage. Press and hold the volume down button, then additionally press and hold the power butter, until something appears on the screen. If the bootloader appears, you can then boot into recovery from there.
If the above fails to work, report back with your results and hopefully something else will be suggested.
Ethicistabdiel said:
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Click to expand...
Click to collapse
Your only other option to get into recovery is the volume-down/power-on combination. Like I said, I can't think why that's not working unless it's related to your missing volume button (maybe it's not maintaining a constant pressure on the button when you're using whatever to press through the hole).
If you still can't get that to work, I would suggest finding a stock RUU and flashing that. It's an .exe file that runs from your PC and will return your ROM, bootloader and radio back to stock. Obviously that means you'll lose root and your custom recovery so you'll need to do all that again from scratch. There's a sticky in the dev section with a link to a thread with various RUUs (it's named something along the lines of "shipped & test ROMs" - I'll check that and link to it once I've dragged myself out of bed to the computer). You'll lose all your data, but if you took a backup beforehand you can restore that once you're back up and running.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
http://forum.xda-developers.com/showthread.php?t=824357&page=5
Guessing you mean that as far as the ruu thread. Am downloading a stock rom atm, with shaped internet till tomorrow, meh! Will see how I go. Have a feeling phone was probably Vodafone branded at stock though, so that could make for extra fiddling but yeah, fingers crossed.
If you are able too install a stock-rom you can work from their than install 4EXT recovery
touch than you doen't need the volume buttons.
I downloaded the most recent stock rom on the link above. When I try to install it though, phone off or on, it advises a USB connection error. Is this likely to be because I originally had vodafone stock and need to make a gold card, or should it still at least be recognising it? It does advise not to run any programs on the phone or anything when while installing the update, but of course, as long as my phones turned on it's stuck on the damned screensaver loop.
http://forum.xda-developers.com/archive/index.php/t-841890.html
Gonna give that a go, fingers crossed!
D'oh, just found out my mobile was Three at stock and not Vodafone, the search continues .
Gah, I'm about tearing my hair out here, I want my damned phone back . Stuck using a $79 Huwawei Vodafone thing at the moment and it's so so so awful.
Anyway. I was under the impression that making a goldcard would mean I could RUU a non-Three stock rom on the phone. I made a goldcard following these instructions; http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then I turned the phone on as the RUU advises, (meaning it's scrolling through the feckin' "screensaver") and start the process and once again get a USB connection error.
What's the better process at this stage, try and take it back to Three stock? I don't see how I can at the moment, the only Three stock I can find seems to be rom, not RUU, meaning I'd need to load from the phone, which I can't due to no recovery. Or should I keep trying to get the goldcard thing to work, maybe try some different RUU's or something?
I'm open to any other suggestions as well. Had a bit more of a fiddle around with my volume down button, no matter what I do though, I can't get recovery mode. Always boots first to the white HTC screen and then starts the infernal "screensaver" loop.
Ethicistabdiel said:
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
Click to expand...
Click to collapse
How come the volume down button be broken. When you were using Affinity Rom weren't you able to use your volume button for music. Remove SD card from phone then press "First - Volume down gently for 2 sec" & press-hold power button when it goes into bootload place your sd card back select option "REBOOT RECOVERY". I think your panicking too much just be patient nothing is wrong, i think your just hurrying it up...
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Ethicistabdiel said:
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Click to expand...
Click to collapse
The only option i can think of is "Fix your volume button from your nearest Service centre". Without that you cant do anything. I am Sorry....
Coming from a phone with microSD extension, I had never encountered such an issue:
I bought this phone with a stock 4.2 Rom installed and tried to install a custom Rom. I first installed the latest version of touch recovery (tried it and it seemed to work fine) and did a backup using the default settings. Then I erroneously chose to format system and data, thinking that I could then "install from zip". Strangely, these steps deleted everything in the /sdcard directory and I couldnt select "external SD" (because the phone isnt equipped with it anyways?). Then I made a second mistake and restarted the phone, despite the message warning that I no longer had an OS installed. I took the battery out, and then held the power down while pressing the power button. The phone couldn't get into recovery, but instead showed a screen with the android logo, a large "Start" sign above it, and "Downloading...", "Do not turn off target !!" below it. Pressing the power button now got the phone to show just "Google" and a lock logo under it. The PC (windows 7) can not detect the phone throughout the process.
I tried the latest tool kit and samsung's USB driver but couldnt get the phone recognized by the PC.
Does this mean that the phone is doomed???
Please help!!!
Trent
Relax, it's not easy to 'doom' your Nexus. Especially with all the hard-workers in XDA
Try accessing Recovery mode by holding down BOTH vol up + vol down, as well as power. Holding just vol down + power is 'Download Mode', and at the least you can get to this. Means your phones far from doomed
Thanks a lot for the reply!
As a matter of fact, I also figured out how to get back to recovery (if only I had read your post earlier, my pain would've been much less!). But the problem remains that I can not get a target ROM onto the phone, since: 1. whatever I did seemed to have gotten rid of the nand backup supposedly stored in /data/media/TWRP/BACKUPS/ (I'm using TWRP V. 2.3.2.1). 2. I can not get my PC(or Mac, for that matter) to recognize the phone or the internal storage.
Any pointer from here?
Thanks again!!!
Trent
You can download a factory image and install with fastboot. It's quite easy and instructions are readily available on this forum. You can then install a custom ROM afterwards if stock is not your thing.
Found the answer finally!
It's the adb push method. Basically, it's to install adb drivers and execute a few commands via the command window. Not too bad... Don't know much about fastboot yet though ... If anyone else needs more details, please PM me (to save public bandwidth).
Thanks a lot anyways, whpnhp and jocalderone!!!
Trent