I recently tried to flash my US T-Moble Phone Edition with the SER 1.1. Since my model number was different then the rom I couldn't use the Program A method and had to use the ROM Image Tool. The tool worked great for downloading my old backup ROM off of my card... but every time I tried to write the new SER 1.1 to the card, it gave a can't open physical device error???
After much interigation on these forums and my setup... I downloaded to source to try to see if the mistake was simple. After fixing several typos which prevented it from compiling (not sure why the source link points to something that wouldn't compile) if found a funcitonal typo which was causeing the problem.
In the call to the WriteImage function in RawDiskDlg.cpp the device index is was specified by 'dip->Id', this is not the actual index of the device and should be 'dip->index' as in the ReadImage calls.
After this fix, I was able to recompile and use the app to put the rom on my flash... then upgrade my Tmobile and everything seems to work perfect (thanks guys).
I really do appeciate the work you guys are doing... and can't wait till 2003 comes out!!!
- T.J.
I dont suppose there is any chance that you could send me the recompiled file so that I could try it.
Many thanks BORIS
Or to me too
We would greatly appreciate it!!!
Here's a link to the exe...
http://givemebeer.com:8080/warez/XDA/xdarit.exe
Hi folks, i'm looking for 2 days a way to solve my DHD problem:
It can't boot anymore. It pop up the "htc quietly brilliant" screen, play the boot sound and, start this step again, and again, and again...
So I'm googling a LOT about how to solve this, if exist a way to restore the original rom. Because i'm thinking that was the problem, my original rom is gone.
That happens when i try to install 3 softwares from appbrain, my device got freeze and i hit the power button to reset. So, after that, my device is gone.
So i came here, to ask you folks: There is a way to recover the original rom ? Without send to warranty (because it spend something like 1 month here).
I'm not a mobile hacker or something, i'm just trying to be happy with my device.
Thanks a lot and sorry for my poor english!!
Perhaps try booting to the bootloader, by holding Power + Volume down button. From there, you should be able to do a factory reset, which may or may not fix your problem. Worth a shot at least, imo
And if it does not work when you do a factory reset, you can use a rom.zip from HTC RUU to restore your phone.
Now the important thing is to know which HTC rom you are running. If it is unbranded, 1.72.405.3 is a sure shot. Download the RUU.exe from Stock roms thread in android development subforum, and run it. When the window pops up, open run prompt, and type: "%TEMP%". Then search for rom.zip, copy it to your desktop, rename it to PD98IMG.zip and put it to your SD card (I hope that you have a card reader). Then just reboot to bootloader as tmh described, and watch the magic happen
Then if your phone is branded, you can still use the same technique to make PD98IMG.zip, but you have to get the RUU that matches your branding. There are lots of RUUs in android development subforum, just search.
Hi guys,
thanks a lot for quik reply!
I perform the procedure indicated by tmh, but without lucky ;\
I think it is unbranded. I buy it at Portugal and i'm using at Brazil right now.
I'll perform your tip jkoljo.
I'll post a repply to let people know if it works or not.
Thanks a lot!!
Hope the advice the last guy gave helps , a factory re set may work fine and fix the issue. Iv had 3 dhd since the day of release , the second one I had wouldn't switch on, had it replaced by Vodafone . Not sure weather or not they will give you a new one . Hope u get it fixed
Sent from my Desire HD using XDA App
I'm not sure if i got cover from warranty.
Right now, my "PROOF OF PURCHASE" is at europe, and i'm at america, so i must get this work again by myself, or pay (some expensive value, i think) for htc support.
I found those ROM version:
RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed.exe 04-Jan-2011 12:41 285M Windows executable file
RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed.exe
but i'm not sure about "WWE". What it means?
dogasantos said:
I'm not sure if i got cover from warranty.
Right now, my "PROOF OF PURCHASE" is at europe, and i'm at america, so i must get this work again by myself, or pay (some expensive value, i think) for htc support.
I found those ROM version:
RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed.exe 04-Jan-2011 12:41 285M Windows executable file
RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed.exe
but i'm not sure about "WWE". What it means?
Click to expand...
Click to collapse
the different is just the radio version. just try flash one of them and see if that work.
WWE means World Wide English, which is an international release
Any one of those RUUs you linked is ok, as hedayat7 already said.
WWE is World wide English...so both are english Roms...try the RUU flash, it should work like a dream....
jkoljo said:
Download the RUU.exe from Stock roms thread in android development subforum, and run it.
Click to expand...
Click to collapse
Sorry ask for your help again, but at Official thread (thread number 841207) for DHD files, both 1.72.405.3 links are broken.
So i search for another thread, and found another one, but when i run the .exe, it ask for a USB connection to device, so it appears wrong.
Could you gimme a hand to find the correct file?
PS: I can help with a web hosting to all correct files.
You probably found the correct RUU, now proceed to %TEMP% and copy rom.zip to desktop.
You can find RUUs here: http://xdafil.es/index.php?path=DesireHD/RUU/
I am not completely sure if those zip files are actual rom.zips, you can check that. Open up the zip, and if it has a long list of hboot, system, android-info.txt etc, then it is rom.zip and you can just go ahead and rename it to PD98IMG.zip.
jkoljo said:
You probably found the correct RUU, now proceed to %TEMP% and copy rom.zip to desktop.
You can find RUUs here: ...
I am not completely sure if those zip files are actual rom.zips, you can check that. Open up the zip, and if it has a long list of hboot, system, android-info.txt etc, then it is rom.zip and you can just go ahead and rename it to PD98IMG.zip.
Click to expand...
Click to collapse
But i did that.
The "1.72.405.3" files at this URL are broken (Or need password to access it, because "You don't have permission to access" message pop up).
When i run the RRU i got two screens, first i must accept a advice, the second one ask if I have a USB connection to my device. Even when i proceed to next step, i got no .zip file on my %TEMP%.
Im lost because of that lol
UPDATE: OK I FOUND IT! haha ty
Thanks a lot my friends,
but it doesn't work.
I perform the process for 2 different roms, and it doesn't work.
Still can't boot.
I'll sent for warranty and wait a loooong time..
But thanks a lot for help me with this!!
Ok, then there is something wrong in the device itself. You have to send it to a service center.
Sent from my Desire HD using Tapatalk
Hi again,
i keep a little hope that i can restore my phone, so i found a possible solution:
OTA update.
At "showthread.php?t=667728&page=2", i found a guy with the same problem i think, here is the quote:
Kinma said:
I had the same problem last week.
I suspected it had to do with the EXT3 partition.
Solved it by first flashing the OTA 2.2 ROM (for rooted users) as this does not use the EXT3. Then used Rom manager to recreate the EXT3.
Now all ROMs that use the EXT3 run fine!
Click to expand...
Click to collapse
(thanks Kinma for the feedback)
So, i start a search for OTA update file here, and found at "showthread.php?t=885996".
But when i choose "Apply sdcard:update.zip", i got INVALID OPERATION.
Someone have a tip for me about this?
Thanks (its very sad, but i must keep hope).
dogasantos said:
(thanks Kinma for the feedback)
Click to expand...
Click to collapse
You are welcome.
What happened was that after a reboot of the phone the phone started rebooting in the boot sequence, i.e. a boot loop.
I tried a lot of things and nothing worked.
Finally I suspected that the problem might be with the SD card. I had a backup, so I had no problem doing a factory reset.
Then I booted the phone without the SD card.
The phone booted fine.
That way I was certain that the problem was with the SD card.
I had 2 partitions on the SD card, an EXT3 part and the rest was a normal Fat part.
I could still read the card, so I made a backup of all the data on the card.
Then I reformatted the card using windows.
The phone booted fine with an empty, reformatted, SD card.
Since I use Apps 2 SD, I had to recreate the EXT3 partition.
If your rom does not use this, you do not have to do this.
After recreating the EXT partition, put back all files that I want on my SD card.
My advice would be to do a factory reset and after that boot the phone without the SD card.
If the phone boots, you know the problem is with the card.
Hope that helps; good luck!
dogasantos said:
Sorry ask for your help again, but at Official thread (thread number 841207) for DHD files, both 1.72.405.3 links are broken.
So i search for another thread, and found another one, but when i run the .exe, it ask for a USB connection to device, so it appears wrong.
Could you gimme a hand to find the correct file?
PS: I can help with a web hosting to all correct files.
Click to expand...
Click to collapse
Here, use this link:
http://forum.xda-developers.com/archive/index.php/t-899564.html
From "football" post copy and paste his link, the download would start immediately..
Hi folks,
boot without the SD card, doesn't work =(
I'm really without luck with this.
I do:
- Factory reset
- Clear cache and userdata
- Boot without SD or/and SIM cards
- Reflash RUU WWE 1.72.405.3 Radio 26.04.02.17_M2
- Reflash RRU WWE 1.72.405.3 Radio 26.04.02.17_M2 SF
- erase all SD
One show was use OTA update.zip, but at this step i got "invalid operation"
SO, nothing works!
Well, it appears a lost battle =\
thanks folks for all help.
Yeah, there must be something wrong in your device itself, for example a motherboard fault. Send it back to HTC.
yukinok25 said:
Here, use this link:
http://forum.xda-developers.com/archive/index.php/t-899564.html
From "football" post copy and paste his link, the download would start immediately..
Click to expand...
Click to collapse
Hi,
I found the information extremely useful. Big Thanks
GRuti
Finally went and made the beginnings of a general flashing guide that should eventually cover the basics of everything streak related.
forum.xda-developers.com/wiki/index.php?title=Dell_Streak/Flashing_Guide
For the time being I ask that noone directly adds to the list and instead gives me the details to add myself. As it's a wiki I cannot force anyone to do this but i WILL edit it to match the phrasing or possibly remove it if it's redundant.
It is intentionally not excessively verbose/detailed as too much additional detail is only needed if you're completely new to flashing/messing with software.
It doesnt handhold your way though flashing stuff, if you dont know how to use the command line you should NOT be flashing roms as when you brick you only have your self to blame for not having the needed prereq ability pc wise.
It also only covers windows as I only work/dev on windows, if anyone on *nix/osx wants to give me the OS specific details i'll go ahead and add it
It's also missing most of the details on how to use QDL tool as i've never used it or needed it. I need someone to add/help me add the details in the same guide style without handholding users though using it
It's also very generic as installing most roms dont have specific requirements to them (excluding setting up SD's install.txt which is it's own thing)
it does NOT and will not cover using automated tools such as Gingerbreak or mutlirecovery flasher as automated tools ultimately mean that you do not wish to read the instructions on how to do it properly. (on the streak at least) (no offense to respective makers)
edit: it should also NEVER contain links to the forum and especially "read this post to do xxx" stuff, it should be more or less self contained except with regards to downloading files, which should either be direct links (preferably not on a filesharing site like multishare/etc) or links to another section of the wiki containing links
I know there's a couple users about with compiled guides but I cant recall who/which offhand as I dont need them myself. I'd like your input whoever you are
Great job!
Sent from my Inspire 4g using XDA Premium App
I have added some comments on the talk/discussion page on the wiki. If there is any specific topic you need help on in the wiki let me know.
TheManii said:
Finally went and made the beginnings of a general flashing guide that should eventually cover the basics of everything streak related.
forum.xda-developers.com/wiki/index.php?title=Dell_Streak/Flashing_Guide
For the time being I ask that noone directly adds to the list and instead gives me the details to add myself. As it's a wiki I cannot force anyone to do this but i WILL edit it to match the phrasing or possibly remove it if it's redundant.
It is intentionally not excessively verbose/detailed as too much additional detail is only needed if you're completely new to flashing/messing with software.
It doesnt handhold your way though flashing stuff, if you dont know how to use the command line you should NOT be flashing roms as when you brick you only have your self to blame for not having the needed prereq ability pc wise.
It also only covers windows as I only work/dev on windows, if anyone on *nix/osx wants to give me the OS specific details i'll go ahead and add it
It's also missing most of the details on how to use QDL tool as i've never used it or needed it. I need someone to add/help me add the details in the same guide style without handholding users though using it
It's also very generic as installing most roms dont have specific requirements to them (excluding setting up SD's install.txt which is it's own thing)
it does NOT and will not cover using automated tools such as Gingerbreak or mutlirecovery flasher as automated tools ultimately mean that you do not wish to read the instructions on how to do it properly. (on the streak at least) (no offense to respective makers)
edit: it should also NEVER contain links to the forum and especially "read this post to do xxx" stuff, it should be more or less self contained except with regards to downloading files, which should either be direct links (preferably not on a filesharing site like multishare/etc) or links to another section of the wiki containing links
I know there's a couple users about with compiled guides but I cant recall who/which offhand as I dont need them myself. I'd like your input whoever you are
Click to expand...
Click to collapse
Thanx!
I had a problem with Zune update of samsung focus i917and tried to restore as suggested. I got a bricked phone. I need to try downloading the following file: i917-Focus-firmware-UCJK2-ATT-USA.exe to try and get the phone to be updated and functioning, but I cannot find the file anywhere. XDA has some links for the file, but they have been hijacked by B...S websites. Does anyone know where to find the file? I have searched, but have gotten a bunch of websites that want you to download a bunch of crappy software, but never provide the actual file.
Bill
Please see my post here. I've just tested both mediafire and digzip (you just need to wait 30).
If you use the MediaFire links, be sure to download BOTH parts of the ROM you want. I had to break them into two pieces due to the limitations of MediaFire. Then Run the First part to extract the ROM files. Also, you may need the Samsung Drivers if you have not installed them previously. It is also included in that link.
Hi all,
I was following the "main thread" a while ago before these phones had their own section, but hadn't checked for updates since early to mid January (before the bootloader was unlocked). Now I see that it's unlocked, there is unfortunately no support for the Canadian (Bell) variant, the E617G.
I extracted the bootloader from my wife's phone and did a binary comprison to the various unlocked bootloaders for the E610, 612 and 615 and it's almost identical byte for byte to the E610. Aside from the edited messages and the tail end of the files where the checks appear to be located, there is one location (byte 0xB476) that is different.
I'm not really experienced in this sort of work, but could that one byte be what's causing the random reboots for the E617 variants? Before I try truncating the file I extracted to removed what appears to be the secure checks and flashing it, does anybody have any other reasons why the E617 has been "left out in the cold"?
I've attached some screenshots of the comparison to the E610 emmc_appsboot.bin
First Difference
Differences in Messages
Apparent Secure Checks?
In the 3rd screenshot, you can see in the E610 file, after 0x40F07 the file is blank, but in mine the file continues on (it's 4MB of null padding by the looks of it).
Skellums said:
Hi all,
I was following the "main thread" a while ago before these phones had their own section, but hadn't checked for updates since early to mid January (before the bootloader was unlocked). Now I see that it's unlocked, there is unfortunately no support for the Canadian (Bell) variant, the E617G.
I extracted the bootloader from my wife's phone and did a binary comprison to the various unlocked bootloaders for the E610, 612 and 615 and it's almost identical byte for byte to the E610. Aside from the edited messages and the tail end of the files where the checks appear to be located, there is one location (byte 0xB476) that is different.
I'm not really experienced in this sort of work, but could that one byte be what's causing the random reboots for the E617 variants? Before I try truncating the file I extracted to removed what appears to be the secure checks and flashing it, does anybody have any other reasons why the E617 has been "left out in the cold"?
I've attached some screenshots of the comparison to the E610 emmc_appsboot.bin
First Difference
Differences in Messages
Apparent Secure Checks?
In the 3rd screenshot, you can see in the E610 file, after 0x40F07 the file is blank, but in mine the file continues on (it's 4MB of null padding by the looks of it).
Click to expand...
Click to collapse
Hey, I have the E617-G too and I'm looking for a way to unlock the bootloader. have you made any progress on doing it? I would forever be in debt to you if you did hahahahh!
KingDaedrix said:
Hey, I have the E617-G too and I'm looking for a way to unlock the bootloader. have you made any progress on doing it? I would forever be in debt to you if you did hahahahh!
Click to expand...
Click to collapse
Sorry for the lack of reply, I've been busy for the past few weeks!
I went ahead and truncated the backup I made, and changed the one byte that was different... So far I haven't had any problems. I was able to flash the recovery image and make a CWM backup.
I made a few other slight modifications (changed the messages in the file, from "Russia" to "Canada" ), but other than that the files are identical.
I've attached my modified file if you want to give it a go. The instructions are the same as the other unlock instructions here.
Make sure you don't skip making a backup just in case!!!
As usual with things of this nature: I claim no resposibility for any damage to your phone, loss of data, etc!! Flash at your own risk!
All credit to the original devs of the unlock, fix is the same, just different source files were used.
Skellums said:
Sorry for the lack of reply, I've been busy for the past few weeks!
I went ahead and truncated the backup I made, and changed the one byte that was different... So far I haven't had any problems. I was able to flash the recovery image and make a CWM backup.
I made a few other slight modifications (changed the messages in the file, from "Russia" to "Canada" ), but other than that the files are identical.
I've attached my modified file if you want to give it a go. The instructions are the same as the other unlock instructions here.
Make sure you don't skip making a backup just in case!!!
As usual with things of this nature: I claim no resposibility for any damage to your phone, loss of data, etc!! Flash at your own risk!
Click to expand...
Click to collapse
thanks a lot! I was looking to put a Windows Phone 7 ROM on it, is that possible? Sorry, I'm kind of a noob with phones, more into building computers and such.
KingDaedrix said:
thanks a lot! I was looking to put a Windows Phone 7 ROM on it, is that possible? Sorry, I'm kind of a noob with phones, more into building computers and such.
Click to expand...
Click to collapse
Unfortunately no. Windows Phone 7 is not open source so there is no easy/legal way to port the OS over. There are launchers that have been made so the Android interface mimics Windows Phone 7, but it's still Android running under the hood.
Help!
Skellums said:
Sorry for the lack of reply, I've been busy for the past few weeks!
I went ahead and truncated the backup I made, and changed the one byte that was different... So far I haven't had any problems. I was able to flash the recovery image and make a CWM backup.
I made a few other slight modifications (changed the messages in the file, from "Russia" to "Canada" ), but other than that the files are identical.
I've attached my modified file if you want to give it a go. The instructions are the same as the other unlock instructions here.
Make sure you don't skip making a backup just in case!!!
As usual with things of this nature: I claim no resposibility for any damage to your phone, loss of data, etc!! Flash at your own risk!
Click to expand...
Click to collapse
I have followed the instruction you posted but i still cant boot into recovery. I have used adb command reboot bootloader and it gets stuck on a black and white screen tht says fastboot processing.
I am not sure if there something wrong with my device.
Thanks!
Me again, just replying to confirm that following the steps posted I successfully unlocked the bootloader of the phone. Not very much use however as there is very few ROMs for the model. Thanks a lot though OP!
I also successfully unlocked the bootloader using your binary. Thank you!
I wrote an article here on getting it all running with CM10.1 on the L5 E617G!