I am hoping someone can shed some light on a possible solution:
Generic UK Hero.
Clockwork ROM Manager installed and have backed up and successfully restored my standard Hero Rom.
I recently updated to the newest Radio rom and am hugely impressed with the signal improvements. So some aspects of what I am doing is working.
However I have tried. Vanilla, Chronos and Damage control and whenever I try to update when I get to the reboot stage the phone just sits there on the startup screen that says HERO. No little droid poking his head out, no shiny effect on the Hero logo, just the static logo. Latest update attempt has been sitting there or 12 minutes now.
I can pop the battery out and restore my original backed up settings no problem.
This has been tried while charging, while plugged into the USB and while not plugged into anything.
Any ideas ?
Thanks
Are you using a CDMA or GSM Hero? Vanilla could be either, but as far as i know, Chronos is for GSM only, and Damagecontrol is CDMA only.
Dont put the wrong type on the wrong handset.
CDMA or GSM ?
not sure what the difference is, I have a UK Hero that does 3G. I have tried UK specific (I think) roms (Vanillain) with exactly the same result. When rebooting after applying the zip update I just sits on the HERO screen.
hmmmm
Bit more info
I have been playing with fastboot/hboot and while it's a bit quick, hboot is reporting no image or wrong image aginst these (and more files)
HERODIAG.ZIP
HERODIA3.nmh
HERODIA2.nmh
etc. there's more of these.
This indicates I have loaded the wrong ROM image? Or have screwed up the (seemingly) simple process of flashing a rom.
Arse!
God I feel such an arse. Loading CDMA ROM Image on GSM Hero will not work.. Just loaded VillainRom 5.5 and it's working.
Mebbe not
A bit too impatient posting there. No Villain has the same problem.
Fastboot gives me
Fat32 INit ok
Open File Fail
Reboot Device?
wodswods said:
Fat32 INit ok
Open File Fail
Reboot Device?
Click to expand...
Click to collapse
Sorry i dont know what that means. the only thing I can suggest is to follow BTDAG's guide which is linked in my signature,.... Or wait to see if anyone can shed any light on the error you get?
Or look for a thread with support for that Clockwork ROM Manager?
Wait longer and get a logcat running to see what is happening.
Related
Hey, I just tried to install DCD's newest ROM and it looks as if i may of bricked my phone. When i connect it to my PC, Active Sync will not even pick it up. this happened right after i ran Hard-SPL-MFG to unlock the phone... I did try and run the titan_exitbl but no luck. I also attempted to run the relocker but i would not even run.. any ideas?
thanks!
recover from flash
Are you at the 3 color screen? If so you need to unplug the USB and replug it again as per the instructions. You MUST follow the instructions EXACTLY or your flashing will be very scary experience.
If you are not at the 3 color screen, you need to get back to the bootloader by pressing power+camera and soft reset. This will get you to the 3 color screen. Then have a look at the version of bootloader you have. If it doesnt say Olipro 1.20 or 2.40 you still have the locked bootloader and you can flash a stock carrier rom. If you have 2.40 you can flash to the 3.16+ rom and then flash the new radio this way or via sd card install which will be more painless and less scary.
If you dont know what an sd card flash is, I would search the forums here. Over at ppcgeeks you can look up imcokeman's posts and see instructions how to do a sd flash.
If you are are real noob, I would suggest staying with non gps roms at this stage because the change of radio rom needed to enable you to flash a gps rom will almost certainly lead to sleepless nights wondering if you have bricked your machine.
Most important thing to realise is that the machine is almost certainly not bricked. But you might have a few more scary moments before you get your machine back working again. You might also need to call your carriers service desk a number of times to get your provisioning data back working.
Check all the way through these two posts and dont sweat too much. With effort you will get your machine back. The answer to your problems is listed in one of these threads, but you need to dig a fair bit to find it. The posts contain lots of problems that people had flashing this rom, and I am sure your exact problem was there and solved. Its I believe somewhere in the second link I have listed here.
Good luck. i feel for you.
http://forum.xda-developers.com/showthread.php?t=371314
http://forum.xda-developers.com/showthread.php?t=362566 particularly this bit http://forum.xda-developers.com/showpost.php?p=1856032&postcount=216
thanks ill take a look, as a side note i am currently at the verizon logo, i can boot to the bootloader screen (red,green,blue) and when i connect the USB cord it does switch from Serial to USB on the screen... but gets stuck there. Active Sync shows no device connected.... I am running 2.40.Olipro
Thanks again
optyhtp said:
thanks ill take a look, as a side note i am currently at the verizon logo, i can boot to the bootloader screen (red,green,blue) and when i connect the USB cord it does switch from Serial to USB on the screen... but gets stuck there. Active Sync shows no device connected.... I am running 2.40.Olipro
Thanks again
Click to expand...
Click to collapse
It doesn't need to active sync. Once it switches to USB you are ready to flash.
Stuck at Verizon Screen/HTC Mobilty Screen
If you are stuck at the VZW screen then you have only flashed one of the two essential parts. You need both (ROM and RADIO) to make it work. 3.16+ ROM will not work with the old radio. You need 3.27 radio.
Use the camera+power+soft reset and you can flash the one (new radio or new ROM) that you are missing.
See dcd's thread about the 2.3.2 rom. He has added a HUGE new disclaimer.
http://forum.xda-developers.com/showpost.php?p=1952956&postcount=1
Well nothing really worked so i used a sd card to flash back to the stock verizon ROM, i then attempted it again and got it all working!!!
Evening all,
I have been advised to post here on XDA from Android Forums. This is a copy of my initial post on there to explain the background to my issue.....
Hi there,
I have HTC Desire from O2 and after 12 hours of online searching and tweaking I'm hoping someone may be able to help.
I received the OTA upgrade yesterday which I accepted because I thought O2 might have it sorted by now. Obviously not. Anyway update ran with no interruption but then rebooted to a frozen O2 screen.
I searched the net and eventually found the guide to update the phone using the RUU Rom. I followed this to the letter and the installer for the RUU wouldnt't open. I then realised that Google Chrome hadn't fully downloaded the file (113mb not 171mb). I then used a download manager to ensure I had the full file. It then ran and seemed to be working... until 80% in when I get ERROR 110 File Open.... please use a complete RUU. I downloaded it several more times in various ways but still same result. By this point my phone was pretty much bricked.
I had black screen with silver HTC logo in the middle and 4 exclamation marks in the corners.... this remained whilst the phone was plugged in and the buttons in any combination did nothing. When i removed the USB cable i got a white boot screen with RUU highlighted in orange and again.... buttons do nothing. Every time I ran the RUU file it brought up a green bar as if it was making progress but then errors at the same point every time. (Error 110 use complete RUU... file seems to be complete now at 171mb)
I tried it on two computers, one win7 and the other vista. The vista machine doesn't even see the phone, it gives a USB error before the update begins.
At 2am I used the SDK download and typed the following at command prompt.... "fastboot oem boot".... phone instantly boots into O2 Froyo and works fine. If i then unplug the phone, turn it off and on again.... i get the black HTC screen again, back to square one.
At the moment I have fastbooted it so its working and have used the goldcard tool to obtain the CID and created the .img file.
I don't know what to do from here!!.... the update obviously hasn't FULLY worked but it must have completed enough for the thing to fastboot and seems to have full functionality (calls, wireless, network etc)
I don't really want to void the warranty but O2's only option is to send it off for 14 days to have an engineer tell me its buggered and send a replacement.
Any advice is appreciated.
Rich.
A couple of helpful guys on there have tried to advise me but without success. They suggested rooting etc but here is my problem.....
At the moment the phone seems to be working fine with Froyo... but the only way I can get my phone to start up is by plugging in and running "fastboot oem boot" from command prompt. If my phone is powered off and I turn it on in the normal way, I get the black screen with silver 'HTC' and triangles in 4 corners and all buttons do nothing!
I have tried fastboot command whilst holding down the volume keys etc and it just boots normally. Obviously something isn't right and I can't let my battery run down otherwise its useless until I can fastboot it again.
So this is preventing me from accessing any of the menu's required in the flash/root tutorials.
Can anyone help or do I just need to ensure I don't run the battery down?!?
Thanks in advance
Rich
if you have a goldcard already, have you tried flashing a diffrent ruu from fastboot? maybe just a generic htc one rather than the o2 one?
Hi,
Thanks for your reply.
Could you advise me which RUU would be the best to use?
I have looked through the list on shipped-roms website but apart from the obvious O2 ones, I don't understand which ones are which!
Thanks
Rich
Hi Rich,
I have exactly the same problem. Have you got any feedback about whether you have solved this issue?
Thanks!
Kelk
Edit:
I think I may have got it sorted. Downgrade to 2.1 as per:
hxxp://forum.xda-developers.com/showthread.php?t=768256
(replace xx to tt in link above)
Hi there,
I haven't solved my issue yet. At the moment I am using my phone on 2.2 but trying not let the battery run flat (I have to use fastboot from command prompt to get my phone to boot up)
Did the tutorial above work for you?
My issue is getting a working goldcard. I'm not sure whether mine has worked succesfully because when i've tried running the RUU of either the unbranded froyo update or even the O2 original, i get and error message and it doesn't work.
I followed the goldcard creation tutorial but I still get the CID error when trying to run the various RUU files.
I hope I can sort this soon because i've been close to throwing my phone out of the window several times!!
Cheers
Rich
Hi Rich,
Yes, the above tutorial worked for me. I think this is because it downgrades to a former version of HBOOT.
rich0684 said:
Hi there,
I haven't solved my issue yet. At the moment I am using my phone on 2.2 but trying not let the battery run flat (I have to use fastboot from command prompt to get my phone to boot up)
Did the tutorial above work for you?
My issue is getting a working goldcard. I'm not sure whether mine has worked succesfully because when i've tried running the RUU of either the unbranded froyo update or even the O2 original, i get and error message and it doesn't work.
I followed the goldcard creation tutorial but I still get the CID error when trying to run the various RUU files.
I hope I can sort this soon because i've been close to throwing my phone out of the window several times!!
Cheers
Rich
Click to expand...
Click to collapse
Use Goldcard + your shipped o2 ROM (ROM that came originally with ur phone 1st time). you can get the rom from HTC official website. enter your Serial Number t download (i recommend using Mozilla built in download manager, coz Google Chrome always give me Corrupted Download when downloading Large files)
Ok, so before the general populace of the forum, looks over this post thinking it's some noob who cant read through the forums to solve there own problem, i would like to say thanks in advance to anyone who can seriously provide some help.
Problem is as follows:::
1,)Phone is working fine using mini-winmo+cyan droid
2,) -PROBLEM- My android stops working, so now im stuck using a lite version of winmo
3,) Tried formatting the sdcard with the lite version winmo built in sdcard formatter, doesnt solve anything, dont exactly know what i was trying to solve with this step.
4,) I decide to get a nice fancy version of winmo, figured it would be as easy as just flashing it once n done.
5,)Decided on going with Ozrom, looked the best at the time.
6,) Run the ruucustom as admin, everything goes fine.
7,) -PROBLEM- after flashing the first boot leaves me stuck on the bootscreen.
So after all that i took the advice and tried to get back to the stock Tmous ROM, but as im typing this im still stuck on the Stick together screen, and also just for a control group i downloaded the latest HD2 cell winmo rom release, and that left me hanging on there version of the boot screen.
Same problem, different roms.. stuck on the loading/boot screen.
But, with the stock rom after playing around with removing the battery, simcard,sdcard and what have you i got the stock rom to boot!!!! I was so excited, i skipped the "How to use the on screen keyboard" tut and was typing in my email info when the phone reset on its own and all my hopes went down the drain... hopefully i will get some help on the issue, and like i said previously in the first paragraph i appreciate any and all help.
thanks.
---UPDATE---
Phone is on and working, intermittently.
When i plug the phone into the charger and wait for the amber light, it will boot up and actually enter into windows, now heres the kicker, removing the charger and using the phone will result in the phone turning off and restarting itself, hanging on the stick together screen.
Removing the battery, and replacing the battery after i push all the buttons, the same way you would power cycle a TV remote, and then connecting it to a charger is the only way ive been able to maintain the operation of the device.
Any ideas?
Try doing task29 reinstall winmo Rom of choosing.. see if that helps.. also I flash everything from bootloader. Also check battery pins make sure they aren't bent..
Sent from my Mytouch HD2
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
She lives!!!
Okay, I'm not actually sure if the problem is solved but I'm back in WinMo 6.5 for the time being.
Since it had been off for a few hours I tried my luck again, plugged it into the wall and saw that it was stuck in the boot loop again. But I got distracted and left it, and when I came back it was on the orange WinMo setup screen.
Not sure what happened to make it go from not even getting power from the battery to working normally. But I see now my radio version is 2.05 which is massively old, I'm going to try and upgrade that first and see... hopefully it won't go back to being dead the moment I power down.
Shawn_230 said:
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
Click to expand...
Click to collapse
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
germotlp said:
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
Click to expand...
Click to collapse
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
This is driving me crazy now...
I managed to flash HSPL 2.08, and then MAGLDR 1.3, and then CWM recovery on top.
But this still seems bricked to me, still needs external power to turn on and I can't actually flash a working ROM... flashing a ROM via USB gives connection error and flashing via SD card goes fine but gets stuck in a boot loop.
What can I do at this point short of tossing the phone? I've tried stock 1.48, stock 1.66, a bunch of radios from 2.05 to 2.15... everything.
I am doing some research but the only results I find are T-Mo HD2s being bricked by the wrong radio. I have an original HD2 and I never flashed a radio intended for another HD2 model, so how is my phone so bricked all of a sudden?
All the threads I've found say if you can get into the bootloader then there's some hope but I doubt it because I can't successfully flash anything with it. I don't even know how I managed to get back into WinMo briefly last night... think my HD2 is probably just toast.
Okay, I finally solved my problems for sure - bent charging leads in the battery compartment!
Anyone having boot issues, take out your battery and look at the metal leads and you will probably find them bent out of shape. They are incredibly flexible, so just make them straight again and it will work. I assume it cuts external power briefly right before booting into WinMo, which is why it was rebooting constantly.
So I suppose for me this was a huge case of confusion, I got all confused with bootloaders and MAGLDRs when the problem wasn't even software related.
Shawn_230 said:
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
Click to expand...
Click to collapse
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
germotlp said:
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
Click to expand...
Click to collapse
Which model HD2 do you have?
Find and download the stock ROM from this thread, get 1.66 since it will work with HSPL2 which is the latest HSPL that will work with MAGLDR (for Android and WinPhone7).
You can flash that through SD card and it will go back to total stock, including stock SPL. I assume you know how to pull the .nbh file from the ROM you download, so just rename to LEOIMG.nbh and put it on your SD card.
Go into the tri-color screen and it should flash fine and give you factory reset. This is where it wasn't working for me, but not because I had flashed the wrong ROM or something but because I had messed up the charging leads in the back while popping the battery in and out to reboot as I was flashing.
Man I downloaded 1.66 last nite and tried to flash back to winmo from android and its toast. Not sure what went wrong. Oh well.
Sent from my HTC Sensation 4G using XDA App
In my attempt to root my phone, I have caused some major issues.
Specs:
Mytouch 3G (I guess 1.2 since it has the 3.5mm jack)
Current:
S-on
HBoot-1.76.007 (SAPP31000)
CPLD-13
Radio-2.22.23.02
I know I flashed the incorrect stuff from what I found in my research. I cannot use Fastboot because it does not allow remote. No recovery options
I tried following a direction to root, but the sapping file was on megaupload which is not there anymore, so I searched for another from a differant site. The whole issue is I kept getting the incorrect ones, so this happened.
The last one was way off, as you can tell from the above info. I believe I found a correct one, but a new issue arose. When trying to load it, it stay's on "Unzipping" for system. In this particular img, it is the first to be done. I thought it was a currupted file, so I got another from a different source. Same issue. Seems to do that with any I try, including those I got from this site. I am Guessing the incorrect version that got installed.
Only options I have is "Fastboot" and "Simlock". no recovery. The OS will not load and cannot do the home+power boot to get into recovery.
I have been trying to locate how to flash one item at a time from the goldcard I made, but with no luck, most of the links I find seem to be dead, or lacking in the detail I need.
Right now, my phone is useless, and any help would be most appreciated.
While I want to keep this thread open until it's fixed, I suppose the first question is "how to I flash the correct SLP from an SD card without anything else?"