Related
I have 2 XDAIIi and I upgraded my last one only to have a serious problem during in the process.
I thought I followed everything ok. set it all up and left my XDA to update, when I got back about 20min later my XDA was black and the software on my PC had dissapeared?
Went to reboot XDA and nothing except Serial v1.01
I think its dead and needs to be sorted by a repairer but as a last resort, can anyone advise me please if this is fixable?
Thanks
Paul.
Rerun the upgrade program and wait for several minutes.
Don't worry!
I have the exact same problem.
How can I rerun the program? I can´t even reset my Magician, and even if I tried, it can´t connect to the comp with Active Sync.
´cause I´ve tried it before, but it turned off after some minutes, and everything go back to before... Serial v1.0.2
it's stuck in bootloader mode, put the PDA in, run the update application and stop worrying.
you know the sequence you sue to put the PDA in Bootloader mode? pretend you've done it already and run the update.
thanks guy, it worked!
So that´s why... I was stucked in Boot Loader mode.
Just a minor question : is there a way to exit the Boot Loader mode without install the program again?
My DOPD - bought in China was running a chinese version of WM5.0 and I wanted to install a english version.
After upgrading my DOPOD 900 with the upgrade : Universal_Upgrade_v1.30.68_radio_1.09.0.zip I have problem.
It is really DEAD. soft reset does nothing and a hard reset only gives the option of "0" and "X" which do nothing.
the USB is no longer recognised and nothing seems to want to communicate with the Dopod. It seems the USB loader program is no longer running on the Dopod.
Has anybody any idea how I can attach to the device an install a new bootloader, or something.
I had the same issue and I have a solution. But, let me tell you my process that got me where you are.
I tried performing the update using the No_ID (or whatever) method and kept getting errors. I rebooted my PC and changed the Operator ID using the HTC64 Extended ROM Tool.
After this, I was able to use the typical installer. The flash went fine and I hard reset as instructed. From that point on, I had your exact problem.
A dead screen. I was able to redo the hard reset after pulling the battery but I would just end up with the dead (blank) screen again. ONCE, I did get it into boot loader mode where I could actually read the screen. But, of course I reset and again had a dead screen.
My solution was to revert back to a true O2 ROM. Even though I couldn't see the screen (still can't), the ROM update is proceeding as I type this. I'm at 44% of the radio ROM installed.
Hope this gives you hope!
Well, good news. I just finished the ROM update and I'm looking at the O2 boot image.
Is there any indication that the QTek ROM looks for the Carrier info to be QTek or it will fail once installed? Just wondering why I had this problem.
ARG! Reflashing with QTek ROM did the same thing. :evil:
Blank screen and all.
check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again
Thanks and another question
Well thanks for the hope. but I have tried this already with no luck, however after this message I will try again. My biggest problem is that I cant regain communication over the usb.
I would like to know how your system behaved when you plugged in your apparantely dead device. My system just says device un recognised and I cant begin a download with or without active sync.
So I cant get another rom image to download.
regards
Nick
dolebole said:
check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again
Click to expand...
Click to collapse
This was the first thing I did.
The problem is that I cannot get any communication over the USB.
The device is unrecognised on USB and after starting any ROM download it just timesout after "checking information from device" message .
Ever seen a dead USB interface like this ?
The USB PnP mgr sees the hardware but cannot establish the device type !!
Nick
@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss
ta_mobile said:
@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss
Click to expand...
Click to collapse
Why don't you guys take it to your respective service centres and get it fixed?
Even if you have to pay something, it will certainly be better than these bricks occupying table space.
Have you tried going back to an original O2 ROM? I went to 1.13.139 WWE and all is fine now.
Just to share my experience with you guys here:
I posted my problem way back during the Radio Upgrade from 1.04 to 1.06. My Dopod 900 got stuck on the splashscreen. I couldn't get my device to pass the splashscreen even after upgrading/downgrading the radio ROM back and forth two times.
Finally, I just forced my device into bootloader mode (Backlight+Reset+Power). Even after doing this, the dopod screen was completely blank (no indication of serial/usb letter on the screen). I downloaded the official O2 exec ROM and plug my device (in bootloader mode) back to the USB port. It said unrecognized port on my PC. Despite that, I reflashed my Dopod back with the NoID tool the complete O2 ROM (Radio, Main ROM & The extended). Once completed, my device regained its consciousness.
I managed to flashed back the 1.06 radio after that. And has since been upgraded 4 times (two i-mate, one Orange and the latest QTek ROM) with no problem whatsoever.
I had the exact same problem as you to guys, i tried to update it, and it wouldn't budge...
It constantly, without fail timed out... I tried everything...
As my hope started to wain, i gave it one last shot...
I took out everything, sim and sd and battery, then connect the battery back and from the bootloader menu, connected it to the pc, with usb cable...
Finally it worked!! Like normal, i was able to load any and all rom and radio updates...
Wouldn't work, from the normal working screen (which was working for a while, i later tested this out, and found out ) and also wouldn't work, from the bootloader (power+backlight+reset) with sim+flash in there....
Hope you guys have some luck.. I htink you should, because i was in the exact same boots as you guys...
It worked for me
My O2 Exec did exactly the same thing, and I spent (on and off) 24 hours trying to get the damn thing to go again - wouldnt charge either....
I too finally took out everything, SIM and sd and battery, then connect the battery back and from the bootloader menu (which I only found about from this site), connected it to the pc, with usb cable...
It worked as well - bloody brilliant. I now have the latest 02Exec Upgrade (Version 1.30.162 AKU2 Release) and all is great.
Cant believe that 2 days after logging email with O2 site, they have not responded...
Would almost kiss you guys.....
Solution for getting stuck in bootloader
http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen
I flashed my phone a couple of weeks ago with Schaps 4.31 Rom. It has been working a treat ! This is the first time I flashed a phone and I followed MR.Vanx instructions.
All was working fine untill yesterday. I had my 3rd freeze of the day. Oh well I thought, thats 3 in 2 weeks never mind must just be having a bad day.
It got worse. I soft reset my phone and now all I get is the Olipro bootloader 3 colour screen ! So I took the battery out and left it for 2 hrs. Still the same.
Whats wrong with it ?
Does this happen like that ?
Can I recover or do I need to flash again or is this permanent ?
HELP HELP HELP
Anyone know ? Phoen still not working. Can someone help ?
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
dan1967 said:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
Click to expand...
Click to collapse
<Sarcasm mode> Thanks. Like I never thought to look there. </Sarcasm mode>
I was more interested in the other questions I asked ... IE is this normal after 2 weeks operation ? etc
no, shouldnt happen like that. try putting the .nbh file on a sd card after formatting fat 32. rename to hermimg.nbh then put in phone. if you're in bootloader it should automatically start the flash. this should get you out of bootloader and back into windows. make sur ebattery is more than 50% by putting on to charge for awhile first. hope this helps. Cheers.
Thanks for the response.
I think I can do it via USB as usual I am just waiting for the phone to charge a bit first. Obviously with no OS I have no idea how much battery % it has !! DOH !
Oh well I will post back for those interested once I know if it is goign to work or not !
Previously been stuck on bootloader before, and I just flashed a different ROM via USB. This worked fine for me. Would also try what ultramag69 said previously
Suggested sd as this has become my favourite way of flashing. No chance of NASTY accidents like computer resets, someone unplugging usb or other little things t5hat seem to happen to people as they flash there precious hermes. Sorry if this sounds like a hard sell but I really believe this is the safest way to flash your device. I've even flashed below 50%... Plugged in power. Was in a rush and had no time. Its never failed while I have had bricks and glitches with the usb. And thats my two cents......
Well it just gets stranger, I waited untill the phone was fully charged. It was plugged in to PC via usb swtiched off so I could see the charge light go green. When I switched the phone on with USB connected to go to bootloader screen to reflash, it booted windows !
Its now working fine ! I did nothing except charge it.
How very dare it !
Suggest you check the device for bad blocks.
Put the device into bootloader, start mtty.exe
connect to USB and run the command "Info 8".....this will report if the device has bad blocks (three should turn up even on a normal device).
then run "task 2a" to fix any bad blocks that are evident.
It might be worth flashing a new ROM to it to overwrite any corrupted sectors, just as a precautionary measure?
Have you tried hard resetting the device by holding the 2 left and right buttons (below the screen) and then reseting with the stylus?
This will then ask if you want to reset to factory..or if you have a cooked ROM reset back to the cooked ROM?
Helped me out and then promptly re-ROM'd the thing...
Hope this helps.....
ultramag69 said:
no, shouldnt happen like that. try putting the .nbh file on a sd card after formatting fat 32. rename to hermimg.nbh then put in phone. if you're in bootloader it should automatically start the flash. this should get you out of bootloader and back into windows. make sur ebattery is more than 50% by putting on to charge for awhile first. hope this helps. Cheers.
Click to expand...
Click to collapse
Ok had a problem today JASJAM seemed to loose phone reception has done this before , since I had the offical Telstra ROM on there for some time thought I would re-install , however stopped at 12% then was stuck on bootloader, tried the SD card method above get through the IPL , BOOTLOADER SPLASH 1&2 and EXTROM but seems to stay on GSM in the list any ideas as to what the problem maybe?
You need to loas SPL 1.01 MFG, then connect using MTTY.EXE.
after issueing:
USB>task 32 (you will get)
Level = 0 (now issue)
USB>set 14 0
USB>task 8
p.s. if you have other than SPL 1.01 MFG, you may need to use set 16 0 or other value. Do search.
Now the device should boot, if it does not:
Press the soft keys (the ones below CONTACTS and CALENDAR) together with the RESET. The device should go through installing windows procedure.
Good luck.
Simple.
Hey guys,
I have a very annoying and reproducible problem with my Desire. Everytime I connect the phone via USB (no matter if dock, laptop, wall) it reboots ~2 seconds after removing the USB cable from the phone.
I have had this problem for about 2 weeks now, across 4 or 5 Custom Roms (Sense and Non-Sense) and right now I am on CM6.1 Nightly 214.
It just annoys the crap out of me, for example when I got the Desire in the dock next to my desk and I receive a call, I can only accept the call handsfree, because removing it from the dock would cause a reboot and I would lose the call...
Please give me some kinda advice, I just flashed the latest radio and it worked twice without rebooting and now I'm back to square 1.
All the best,
Paul
Sounds like a faulty battery or some kind of defect at the power supply.
I suggest you try this with another battery, maybe from a friend.
You should check the usb connector on the phone too for some sort of deformation or smudge.
I thought that it could be the usb cable you are using, but since it does the same with the dock, it's not it.
The easiest and the most not likely way to fix it is with the calibration of the battery, if you have luck maybe it's just the OS that errs.
Thanks for your thoughts on my problem. Right now I am waiting for an important call but I got a spare battery from a friend of mine already and will later check and see if the problem occurs with the spare battery as well.
But the other point you mentioned was a calibration of the battery: how exactly do I do that? Just AmonRA Wipe Battery Stats or are you talking about another method?
Cheers for the advice!
this is for the calibration of your battery.
http://forum.xda-developers.com/showthread.php?t=755903
Hi, hope it works with the other battery, otherwise you'll have to send it for repair.
The battery thing I mentioned, has a minimal chance of working, but at least when I am desperate I try things that have even the smallest chance of fixing it. So in essence the process is: charge untill full when powered on; disconnect charger (which will automatically reboot your phone in your case);
don't let it boot, enter hboot for example and turn it off; then charge till full again; now boot into recovery wipe stats; and finally just boot into android.
Another thing worth checking I think is the pins where the battery connects to the phone, they should look clean (I wipe pins with rubber for a pencil) and intact.
Edit:Well seems like Marios already posted a link but mine is specific for your situation
did you solve the problem?
i have the same thing... very strange.
calibrating the battery didn't help.
No, I still haven't found a solution. Strangely though, it doesn't reboot anymore if I charge it via USB on my laptop. On my desktop and via the wall charger it still reboots every time I unplug it. Sorry I can't be of more help
my phone reboots when disconnecting from my laptop too.
even when in recovery, very strange...
have you tried to try the unbricking process with the misc.img?
Actually, I haven't tried that one. Can you give me a link to what you're talking about?
IT WORKED!
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
just flashed the update.zip and i can copy the files to/from my laptop using the usb cable.
and it doesn't reboot when unpluging too
Got the same issue, tried modaco´s workaround, same thing... it started happening after i flashed CWM3.0x wich reovery do u use?
gonna try flashing Ra again and see what happens....
Solved It
Like i said, happened after flashing cw3.x finnaly i got home, flashed RA-desire-v2.0.0-CM again, then flashed update.zip from modaco´s thread, and for now it stoped....
just gonna see what happens when the battery get fully charged....
EDIT: Fully charged 4192mV removed it, and.... nothing happened...
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
congrats
powlemann said:
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
Click to expand...
Click to collapse
NICE....
How did u solved it, u never know.....
I tried all things listed in this thread and some more, too.
But, it still reboots when removing from power supply (pc connection works now).
Perhaps you tried some things not listed here?
I am not sure when the problem started for me.
I installed cm7 nightlies with no reboot-problem, also switched from alpharev1.5 to alpharev1.8 and from cwm2 to cwm3.
All in a few days.
Somewhere along these days the problem appeared.
Btw.:
I got reboots on both kinds of usb connections (PC/power supply).
Debugging connection (adb, fastboot) worked.
Accessing the phone as usb storage device worked, too.
So this may be a little bit different from the cases described in the thread.
To solve the issue, I tried several things:
First I restored older backups (versions of cm7) with no success.
Then I restored my last backup of cm6 nightly from just before cm7, and it didn't work either.
As I was 100% sure that this worked before, I now concentrated on the remaining parts, recovery and boot loader.
So I first tried downgrading to clockworkmod2.
Then I tried updating to a newer alpharev1.8 (as it was a little bit newer than my installed version).
After finding this thread, I became a little happier again...
I applied the fastboot oem ... thingy (hmm, what does it do exactly?).
Then I calibrated my battery, which seemed to work well, as it shows 99% now, which it didn't before.
And at the end I installed the fixmisc-update.zip as linked above.
Between each step I checked if the issue disappeared.
Nothing of those steps completely solved the problem.
However, when disconnecting from PC, the reboots don't appear anymore, so at least something has changed.
So, powlemann, ferreinf and others being successful with the steps above, which configurations do you use now?
Can you tell me which change solved the issue for you?
Do you use alpharev1.5 or 1.8 (and the later from which date) or none of them?
Did you install cwm3 again after solving the problem and did the problem re-appear?
Good News for you, hg42!
I am 99% sure you can fix the problem when first flashing AmonRA recovery and then do Mocados Usb Brick rickrolled.
Do you know how to flash a different recovery?
I fixed it with modaco's zip, that was very annoying!!
Hey i hope all is good.
I really need your help. I have a TILT 2 cell phone and by mistake a friend activated the bootloader. Previously the ROM has been updated. the phone got stuck in that screen and the only way to turn it off is removing the battery. so, i try to reboot the phone and it only loads the bootloader with a flash message saying "no image file". ok, i though, the ROM was damaged and after reading a lot in the forums, i followed the instruction to put a new ROM. I connected the phone the the computer and the message in the phone changed to USB and my PC installed the HTC USB Sync driver (but Active Sync does not detect the phone); anyways, i ran the task 29 and a new rom. I was able to see the progress bar in both (PC and Phone) but then the phone reboots and loads again the bootloader. I tried to use the HARD SPL 1.00 as well but it does the same thing after finishing the flash it loads again the bootloader.
can some help me pls?? i'm new in this and the phone is a work tool for me i really need your help.
rgds
You should do the HSPL before flashing a ROM (unless it was already done).
I would try to flash the newest HSPL, then a ROM.
Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls
jsolanon said:
Hi, and thank you for you reply.
I already did it and apparently it flashed the HSPL . Now in the bootloader says SPL 0.85 OliMex; then i flashed the ROM and it showed me the progress bar in both system (PC and phone) but when it finish it booted back to the bootloader. I just noticed that sometimes (after been off for a while) if i turn it on it boots to the rom but it happens randomly and if I turn it back off i just got the bootloader again.
I really need your help pls
Click to expand...
Click to collapse
Hrm, have you tried doing a task29? Re-flash the ROM after task29.
yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do
jsolanon said:
yes already tried the task 29 and then flash the rom but the same issue...i've been reading a lot of post regarding issue with the bootloader and follow the instruction but nothing seems to work. I even tried the update from the AT&T site but the same issue...i have no idea what else to do
Click to expand...
Click to collapse
So you've flashed the stock ROM? Have you tried relocking? Probably won't do much, but worth a shot I guess.
When you flash back to stock you flash the stock ROM, then relock, then reflash stock.
Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help
jsolanon said:
Yes, but the issue persisted.
I have noticed something. If i leave the cell phone turn off for a while (hours) and then i turn it on. Most of the time it works and all the things are fin; but as soon as i turn it off and turn it back on the bootloader starts appearing.
So, now i can use the cell but i cannot turn it off or leave the battery died on me...any suggestions?
BTW, thank you very much for your help
Click to expand...
Click to collapse
My phone is never turned off. I'm not sure what else to suggest, you've tried seemingly every step that could remedy this problem. Radio firmware probably won't help, but it shouldn't hurt either - you could try a new radio...
hi , this happened to me, solved it by reloading the rom again via sd, once it finish maybe you will see the bootloader screen again, so with stylus pres the reset buttom a few times until the rom boot , this can take several times to make it boot. after revive your cell , do a task29 then reload the rom again then do a hard reset, this happened to my 2 times, and its still alive ,good luck.
Same Problem
Hi,
I'm having the same problem. Installed the latest official ROM from HTC/ATT (gorgeous), and same problem after install. Whenever you try to reboot, it gets stuck in the bootloader screen. The last 50 tries it will not reboot at all, even after removing the battery and hitting the power button. This used to work occasionally.
Any other process anyone knows for getting the device to read the ROM?
Is the phone just worn out?
I suggest you reflash the shipped rom to your device and after the flash finishes and your device begins to boot immediately remove the battery to turn it off before it boots. Then replace the battery and press and hold the Send and End keys and while holding them down press the Power button and follow the instructions to factory reset(hard reset).