Related
My device: XDA O2, with wallaby boot loader 5.17
Tried to flash RSUv1.15(GPRS_421_ENG_O2) into it. Update froze at either 48% or 53%. Tried it 10 times over, while waiting infinitely but the device just auto-booted itself after each froze. Deleted the autorun files from the startup director on the XDA. After which it did not try the update at bootup anymore. Instead the device is now dead :
On boot it just gives a white screen and everything fails / nothing can be done. The device cannot be connected through USB, and nothing on either SD card of MM card will install.
I tried to flash wallaby-patch-tool.nb2 to fix the key problem with 5.17 bootloader but as GSM fails at the bootloader: it just ignores the disk. I tried the patch tool on a SD card and on two other MM cards it does not work on any of them: as the damn bootloader checks GSM first (and gives GSM ERROR)
Also since the device is trashed it does not apper to load its battery, I assume it must be quite dead soon. (is there any way to load a battery on a software-trashed XDA O2??)
I have another fully working XDA O2 at my disposal. That machine is running older version of CE, GSM and 5.15 Bootloader. I tried flashing the OS from that device to the SD card, succeeded in getting it there - but the broken device will not flash itself from the SD card since it has "wrong key", and the patch tool fails to work because the GSM fails before it even checks any cards in 5.17..
The GSM cannot be copied to the SD card from the working device, because copying the GSM requires connecting something called RS232 and running some program nobody has heard of..
Is there anything I can do? I even tried copying the 5.15 bootloader from the working device to SD, and flashing that to the 5.17 broken device: no success, since it fails the GSM at bootloader startup, and the card has "wrong key" anyways.
How can I recover from this?
When you do reply, please reply in full generously abundant and exquisite detail. I am unable to follow instructions such as "just do this and that" if you do give instructions please be very detailed: tell me where to load the files (paste the links) and preferably go step by step through the process.
I have noticed that some other people have this exact same problem. If you give good enough guidance maybe we can create a help file to address this same problem in the future as well.
Thank you in advance!
A further problem with the other XDA
A further problem emerged with the other XDA:
- now it only boots to bootloader, and refuses to power up properly
pressing the power button does nothing. Soft reseting does nothing. Hard reseting does nothing. The only thing that seems to work is pressing the powerbutton+softreseting at the same time == entering the bootloader mode. There the machine passes all tests and seems to be fully functional. however refuses to power up.
I tought maybe the SIM slot is improperly closed, tried closing it better, and manually pressing the switch inside - doesn't work either.
Also tired inserting, taking out, and reinserting the XDA to the cradle, with either the power button pressed at the same time or not (this seems to work sometimes when the XDA O2 in unresponsive) but that doesn't work either.
What to do? how can the device be powered up?
Still stuck with this same situation
Hi all,
I'm still stuck with this same situation. So far nobody has even tried offering any help to me. What can I do? Do you think I should just give up and toss the damn device to the nearest body of water I can see, or what?
look for "repair.zip" in the forum, for some people this helped.
XDA developer Itsme said:
look for "repair.zip" in the forum, for some people this helped.
Click to expand...
Click to collapse
Tried that. That doesn't work since that repair requires that the device works as far as the today screen - my device dies out well before that. As described above it dies right in the start: just frozes up and displays a white screen with a blue bar in top, and after that does nothing, runs nothing, reacts to nothing, etc..
Any other ideas?
After experimenting on an SX56 with a dead Radio Stack, I finally understood the cause of the 1% error, and have a veredict:
IT IS BECAUSE AT THE MOMENT IT WANTS TO FLASH, THE PHONE CAN'T TURN THE RADIO STACK PART ON, SO IT SIMPLY CAN'T FLASH BECAUSE IT HAS NO ACCESS TO THE FLASH CHIP.
I am not saying anything new, I am just confirming it.
I tried to attack the GSM part with a GSM-ROM inside an SD. I did a normal CE+BOOT backup, analysed the dump, replaced the CE-ROM Image it saved with a GSM-ROM image, and modified the SD so when I go into the bootloader it says CARD TYPE: GSM ROM, PRESS ACTION TO DOWNLOAD.
When I press action it says "Please wait for downloading" and after a second the message goes blank, then after 13 more seconds it says "GSM turn on FAIL, PRESS ACTION TO EXIT". It is the same it takes to the normal RSUpgrade.exe program to say "Flash failed, press OK to reboot".
So that's it. If you manage to trash the radio stack entirely (so it shows R and nothing else when it boots), the phone will only be recoverable by reflashing by hardware PERIOD.
Now a question, does anyone know which is the flash chip in the Wallaby? I can't recognize it on the motherboard...
nobody knows???
Maybe this helps.....
http://wiki.xda-developers.com/index.php?pagename=WallabyJTAG
Stefan
No, because the GSM part can't be flashed via JTAG with that info. There are some people who can do it, but they don't share the info on how to do it.
Marton
rre
"I tried to attack the GSM part with a GSM-ROM inside an SD. "
pls sent the "GSM-ROM file" to me thanks!! ([email protected])
hello, I am a new here. and my Elf got a serious problem, I don't know what to do. About 5 days before, my elf fall into water, and I send it to repair. When I got it back, the repairman said your software maybe broke, so he advice me to flash the phone again, and I never done it before. so I try it myself today. now, this phone cannot boot the system, it enter a page tell you startup failed cause suddenly loss power and let me press ok to continue, but when i press ok, it turn off automaticlly.
There is some imformation below:
my CID is not cracked yet.
IPL:2.24.0002
SPL:2.24.0000
I can enter bootloader and connect to USB
I make a goldencard already and it's seems working, mtty shows:
Unlimited time!
g_cKeyCardSecurityLevel = 0
I tried so many different roms and they are all stop flashing at 2%
So, now I don't know what should or can I do?
plzzzzz, i don't have spare mobile to use, thx a lot for help.
I am sorry something forgot to post
Device ID : ELF010052
CID : DOPOD601
I can't find my rom in here so I try goldencard and try to match the Device ID and also doesn't work.
Hi
First go to the stickies and find how to Cid unlock, then you can flash any rom, provided there's no physical damage to the device.
Good luck
first try a hard-reset
Hello mates,
My i-mate Jasjar doesn't start any longer. Here's how I got here. I tried to flash my jasjar with Crossbow ROM using ROMUpgradeUt.exe but it didn't do anything. So I went into the Country_ID_Error folder on the computer and executed MaUpgradeUt_noID.exe. My jasjar froze after this and everytime I restarted it just hung on the bootscreen that says i-mate.
So I tried using mamaich method using mtty and now I can't even get to the i-mate bootscreen. So nothing just happens when I try to power up the phone (I'm sure the battery isn't dead).
All I can do is just enter the bootloader mode. That is the only thing that I can do that I know.
Please suggest something. I'm lifeless without the i-mate.
Thanks and regards,
Aditya More.
i had this same issue, i task28?'d my device, whatever command that resets the flash structure, then booted into bootloader, and flashed this file:
http://rs507.rapidshare.com/files/184081773/JASJAR_WWE_11353_137_10301.zip
that should fix you up real good, hopefully.
Well thanks a lot. But it doesn't help. It gives me a connection error when everything is fine. USB is connected, ActiveSync USB connection is disallowed.
I forgot to mention, that when I task 28'd my device, nothing showed on the device. It just showed USB at the top and v2.01 at the bottom for ever, which means the task 28 wasn't probably successful or I ain't sure what.
Yeah, I had to ask you how if the above given file will work if the phone is in bootloader mode.
To fill you on more details, my phone somehow strangely starts. I'll explain how.
When the phone is switched off, and when I press the reset button, nothing actually happens, no activities can be observed.
When the phone is switched off and I connect it to the computer via USB, it shows the charging light. Now when I press the reset button with the phone connected to the USB, the charging light goes off and the USB detection sound sounds on the computer and the computer shows "USB Device not recognized". This means the phone started.
But strangely in both the above cases, none of the two lights on the phone indicate anything and display of the phone shows absolutely nothing.
The only thing I can do with the phone now is enter bootloader.
Also, since I compromised so much, is it possible that I can still flash it with WM6? Because going back to WM5 will make me feel miserable.
Thanks.
@cheapusenet:
I tried flashing with that file. It flashed successfully, but the screen is all smudged. I soft reseted the phone too (using reset+two soft keys) but it keeps displaying that same smudged screen.
Good news is it did something.
Bad new is that it didn't make the mate work.
Please help. I'm dying without the phone.
Thanks and best regards,
Aditya More.
is it possible you can get a picture of what screen its showing? I THINK it happened on mine as well, did you let it sit for 10 or so minutes? if i recall the bootscreen was all corrupted but it started into WM5 just fine.
and regarding wm6, i'd attempt to get the device working before you try and get fancy. is the device cid unlocked? mine was and thats what was causing the issues.
Originally Posted by mamaich
if you can enter bootloader - use "task 28 55aa", this would restore DOC to its original layout.
If you cannot - contact service center.
if you didnt run that exact command, it's probably a good idea.
and you could try reflashing that stock imate rom?
This is all that happens.. I have waited for 5 minutes. I'll wait for 20 minutes now.
i waited for 30 minutes.. no go..
yap it did that EXACT same thing to mine.
reflash it, i think that fixed mine.
if that doesnt work, attempt flashing some custom roms.
is it CID unlocked?
i flashed it twice.. no go..
what's CID unlocked?
CID
Read the Wiki on my sig link
cid unlock allows flashing of roms that don't match your device branding.
i don't remember what brought me back from that, i may have flashed a custom rom with the imate cid settings in it? i don't remember.
i'll post a rom that i think may have helped in a few hours, I have slow upload speed. until then, just keep tinkering.
also, you should only be flashing nk.nbf. not the ms, or radio nbfs.
http://milfweed.info/UNI_AKU3_2_WWE_IVAN_beta_4_extrom_public.rar
try that rom.
hey man.. Flashed the rom with Ranju's ROM of WM6.1.. it worked.. But I can get the phone to be turned on. i mean device turns on but I can't make or receive calls or text. Let me check the thread of that rom. Thanks a ton for your support. Really appreciate it.
Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?
SS and HX in the bootloader screen just means Samsung or Hynix, , two chip providers HTC uses. They do the same thing, and you can forget about that for now, you have much bigger issues than one chipset being slightly better than the other.
The pink on black screen is a splashscreen, anyone recognise it? winmo? android?
The HTC website started dropping support pages for the HD2 a month or two ago, , looks like its ancient history as far as HTC are concerned.
Qualcomm MSM,,, this is a bad sign, , it is what the bare chipset presents itself to the usb connection as when there is no controlling bootloader. (This is what tmous users get when they radio brick their phones). Quite an odd symptom to see in a phone that powers on.
From the various power / boot symptoms, it sounds likely that one or more of the following are true
1 - the battery may be low on charge, and if magldr is installed the battery wont charge until android is running (which of course it cant) so you NEED to get magldr off ASAP (if in fact it flashed)
2 - the radio may be corrupted, which usually manifests itself as flashes failing at 8 - 10%, or radio flashes never completing.
3 - The phone may be one of the unlucky ones that has/is cooked/cooking itself. have a read on the 'freezer trick' where you cool the phone down for a while in a bag in the freezer, then quickly flash from sd as soon as you take it out, so the chips don't overheat before its done. If this turns out to work, then the phone has hardware issues.
4 - The bootloader itself may be corrupt, but only slightly (just theorising now) or the NAND memory where the bootloader is stored could be starting to degrade.
Recommended way forward.
Assuming you have access to a card reader,,,
send me your IMEI and an email address, and ill generate you a Goldcard.img,
follow THIS to make teh goldcard and place on that goldcard the RUU_Signed.nbh (renamed to leoimg.nbh) extracted from, , lets go for the WWE 3.14 rom from HERE (Lotta junk in that folder, scroll way down towards the bottom, look for filename as below)
id go for
RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.zip
down towards the bottom.
(Thats assuming you want english? theres probably a DE one if you prefer)
SO, id try flash that from the goldcard, and report back.
(Note i'll be on and off all day, so don't expect an immediate response to your IMEI, cheers, oh and the .img when i send it will most likely get spam foldered, so dont miss it!)
I created a goldcard myself and tried the image inside "RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2. 15.50.14_LEO_S_Ship.zip".
While flashing it showed me "RSA Fail" on "Radio_v2".
Any ideas? I'll try other ROMs till someone answers
Thanks,
iCEQB
EDIT1:
Trying "GER" Roms:
1 test) HTC_HD2_RUU_Leo_HTC_GER_1.66.407.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe - "RSA-Fail" on "Radio_v2"
Ahh radio fail, bad news. I've seen it cured once or twice, by flashing the phones original rom, but I suspect those were exceptions.
I've also seen failed flashes take when you well chill in the freezer (card sim and battery out while it chills) and quickly flash on removal.
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.
samsamuel said:
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.
Click to expand...
Click to collapse
Yeah I used the wp7 config. Is it bad? I mean, the goldcard works right?
test 2) RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe - "RSA-Fail" on "Radio_v2"
I'm out of ideas guys ... will wait for you to create me a winmo goldcard image and try them again.
Last resort is the freezer trick. Or any other ideas on how to progress from here?
Regards,
iCEQB
EDIT: BTW, does HSPL need to be deinstalled for these goldcard actions?
Ohhh hang on, that img i sent wont work, silly me, its not the imei I need, its the Cid (unique serial, uid, goes by a few names) of the SD card. See the howto I linked ya for how to find it.(really easy if you have access to any other winmo phone, not so easy otherwise.)
Just shows how long its been since I thought about goldcards.
Sorry.
Which branded phone is this?
Brother even I have same type of logo when phone starts (pink colour circle)
Even my phone is bricked but I can install wp7 or android (only no network problem)
Can u guide me how did u solve this issue pls
Thanks & Regards
SE_iCEQB said:
Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?
Click to expand...
Click to collapse
Do a jtag on it it will fix everything i think
Sent from my Nexus 7 using xda premium