cannot flash from bootloader *error* - Touch Diamond, MDA Compact IV ROM Development

Good morning everybody,
I had yesterday a great review of many posts and threads about flashing and I did it before, but now I have some problems and I hope you can help me.
With mtty 1.42 I have deleted all datas from my device (HTC TD1) and after that my device is in bootload. There is because of deleting no ROM installed. In the bootload it is displayed that HSPL is installed and when I connect my device to my PC the status from serial to USB switchs, so my device is successfully conntected to my PC.
When I start flashing the original HTC ROM (this is an exe data), in some cases the flashing does not start and the error 260 and 264 occur or the flashing display appears and it stopps flashing at 0 % with the error code 262 Update error.
What do I wrong? Is it possible to flash only from the bootload with no ROM on the device?
Thanks for your help!
Cheers, Daniel

Related

FLASH disaster

I was becoming an expert in flashing...but the cable became undone during a flash :-(
Now it restarts to a blank screen with R1.50.08.11 / G32.83.7020 etc. but goes no further.
Computer no longer sees device.
Used hard keys to go into bootlocker. (IPL 0.50 / SPL- 1.07.000)
My VISTA :-( computer sees device.
Then try RUU, but this gives a 270 error.
Tried moving to XP, but the computer does not install the software for the USB port, so now the RUU gives 200 error. Arrgh.
Question: How to update from a very corrupted ROM? Or where can I find the drivers for the USB port, for XP. and if I do can I do the update from the hard bootlocker?
Any help really appreciated!
MS
Update
Found USB drivers for Windows XP
But getting identical problem as with Vista :-(
Device not seen unless in bootlocker mode.
RUU starts and after 1% quits with 270 error - image file corrupt.
Tried RUU a hard SPL (olipro) but same 270 error occured.
Help still needed...
MS
I think you have to flash original HTC rom prio to try other roms
i got a similar problem here, my vista can find trinity only when it is in bootloader mode.
my experience is that connect tinity to vista when it is in bootlader mode, then i can flash a new rom.
after that tinity can sync with vista only via bluetooth.
for your case, maybe you really need restore your trinity to official rom first.
sailer1983 said:
i got a similar problem here, my vista can find trinity only when it is in bootloader mode.
my experience is that connect tinity to vista when it is in bootlader mode, then i can flash a new rom.
after that tinity can sync with vista only via bluetooth.
for your case, maybe you really need restore your trinity to official rom first.
Click to expand...
Click to collapse
Maybe helps:
http://trinityguides.info/index.php?option=com_content&task=view&id=20&Itemid=66
The trinity upgrade guide does not help here.
I can connect to device I have sorted out all the VISTA and XP issues.
The problem is at 1% status the 270 error occurs.
The telephone is actuall a Swisscom 1510. Original ROM was lost in first flashing, have searched but not found official update.
Is there a mini-ROM or a windows WM5 lite ROM which may overwrite what happens while still using the hard bootloader?
MS
Use SD card method.
See wiki page.
Bye
Hi,
...or .... MTTY Procedure....
BYE, Bobo
Tried SD card method - nothing happens. Just sits in Bootloader :-(
Try this procedure
In windows Vista use the attached driver in order to recognize your Device.
If your device is already recognized from windows vista replace the drivers with the drivers in the zip drive.
You have to use the drivers in the attached file not the windows default drivers VERY IMPORTANT!!!
After your Windows vista recognized your device try to flash it
Cheers
Thanks for all the help....but still I am having no success.
The HTC trinity is recognised in both Vista and XP when I use bootloader. (ie HTC USB SYNCH in device manager. Without boot loader the device is more or less dead.
I tried the SD crard trick - nothing happens.
Tried mtty.exe - just get cannot open USB port (on both VISTA and XP).
Nevertheless, the bootloader sees the USB port and the RUU goes to 1% then stops so some communication is happening.
Any other ideas?
MS
The final and, j' m sure, the definitive solution:
Try this one http://forum.xda-developers.com/showthread.php?t=308691&highlight=stack+in+bootloader
Just before I try splxploit, as a note I got this out of mtty
Cmd>info 8
Block 0x0(0) is Reversed block
...
Block 0xC(12) is Reversed block
Block 0x335(821) is BAD block !!!
Seems my problem must be here. Is there another fix besides splxploit?
MS
Install Olipro hardspl 1.20.
Bye
Dear, carefully look that thread again. Stack overflow for Trinity.
It's all my advise. I think you don't do right "Stack method" to get out your problem.
Best regard.(rest calm and do it again).
Uhm, try to download some rom again? and try Rom NVID (no vendor ID) for example. ???
Quick update...
Tried SD card - get 00068002 loading .... then goes to IPL0.5 SPL 1.07
mtty info 8 shows bad blocks
task 2a doesn't clear bad blocks because of CID lock
Tried various hard-SPL OLIPRO 1.2 1.3 etc, to unlock CID - to no avail.
Can the CID not be unlocked through mtty?
MS
ManStan said:
Quick update...
Tried SD card - get 00068002 loading .... then goes to IPL0.5 SPL 1.07
mtty info 8 shows bad blocks
task 2a doesn't clear bad blocks because of CID lock
Tried various hard-SPL OLIPRO 1.2 1.3 etc, to unlock CID - to no avail.
Can the CID not be unlocked through mtty?
MS
Click to expand...
Click to collapse
So you haven't yet tried splxploit?
END of STORY
YESSS!
POF you are a genius - Splxpoilt worked a dream.
Had to run unbrick.bat once. Hit soft reset, and run again as explained in the readme.
This got a good SPL on the machine - then a standard RUU worked a dream.
At the same time I got the SD card update working too...
OK, OK, so I should have tried splxpoit earlier. But I think I had to do the rest first to understand what was going on.
Strange thing is if I look at my machine again under mtty, there is still the Bad block (821). Who cares, I am unbricked!!!
By the way, this board is just completely amazing.
THANKS TO ALL....
i have the same problem
could you help me . how did you repair your spv?

Flash error 262 Diamond

Hi,
I updated with success few time ROM usually Duttys 1.7 - 1.8 , i have installed HardSPL 1.4 Olinex yesterday i tried flash Duttys 1.9 its stop on 53 % and show flash error 262 IU 634 after that time i cannot flash any rom the stop on 58 84 % like TOR, PANOSHA, Please help !
Best Regards
Muzzzik77
This is error 262:
Q: During the upgrade, the progress bar is moving. If the error message (ERROR [262] :UPDATE ERROR) appears, what should I do?
A: This may occur when the connection is lost, without power supply, computer host is down, or due to other unexpected cases. You will see that there’s still one progress bar displayed on the device but it is not moving any more. The device cannot get into the Wince screen, so you cannot connect with ActiveSync. This problem usually can be recovered. You just need to follow the instructions in the error message box, reset the device, and run RUU again. RUU will re-flash the whole image again.
Note: You should remove the battery and reset the Mobile Device.
What you can do is reset the device with volume down key pressed. You will enter the bootloader. Check that at the bottom of the screen it says USB and not SERIAL.
If so, unplug the USB cable till it shows USB. Then flash it again. Maybe you should flash a stock HTC ROM first.
Good luck...
Muzzik77 said:
Hi,
I updated with success few time ROM usually Duttys 1.7 - 1.8 , i have installed HardSPL 1.4 Olinex yesterday i tried flash Duttys 1.9 its stop on 53 % and show flash error 262 IU 634 after that time i cannot flash any rom the stop on 58 84 % like TOR, PANOSHA, Please help !
Best Regards
Muzzzik77
Click to expand...
Click to collapse
try to flash an original rom signed like:
RUU_Diamond_HTC_Europe_1.93.401.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe
and remove the cover from the back of your device and keep it cooled with something(a vent or something)
is probbably that you have a power management issue on you device
if you got warranty u should take it to the shop with an original rom
i had the same ..
I used Hardspl a few weeks ago.
After 3 retry´s to flash the new WM6.5 HTC ROM,
i installed Hardspl relocker and rebooted it...
It came up like you bought it.. like a fresh install ...
after all the settigns i tried to flash the new rom again and.... bingo
where can i find the hardspl relocker??

Updating HTC Diamond Pro

Hi,
I have bought an MDA Compact IV and i'm trying to install a different ROM on this.
So far I have flashed the SPL to : SPL-1.90.Olinex (as verifyed in the boot loader) and I'm trying to flash an rom image, it aborts with an 244 error.
I have tried to flash other SPL's but they don't work with an 244 error (device not compatible). The Device is already Sim-Lock free.
Olinex means that I flashed the SPL correctly right? What can I do to resolve the 244 error?
244 error
LaurensBER said:
Hi,
I have bought an MDA Compact IV and i'm trying to install a different ROM on this.
So far I have flashed the SPL to : SPL-1.90.Olinex (as verifyed in the boot loader) and I'm trying to flash an rom image, it aborts with an 244 error.
I have tried to flash other SPL's but they don't work with an 244 error (device not compatible). The Device is already Sim-Lock free.
Olinex means that I flashed the SPL correctly right? What can I do to resolve the 244 error?
Click to expand...
Click to collapse
This is my first post, but to save you time reading and searching different forums; (Thats all I have been doing the last few months), here are some questions and things you should do first. I have already flashed my device successfully about 30 times.
1. Your device is GSM and not CDMA? If it's GSM I can help if not I'm sorry, I blank out here.
2. Which ROM you're trying to install? Coocked ROMs need specific Hard SPL. Chech the chief's recommendation for that. Stock ROMs are OK with your SPL.
3. Prepare your PC: Not to complicate things you need a PC running XP (English version,RUU seems to have a problem with other languages) with service pack 2 and netframework 3.5 instaled, you can get the .NET file from the Microsoft site for free. Do not use USB Hubs, plug your phone directly to your PC. Disable hibernation and all unwated programmes running in the background and do'nt launch any programmes during the upgrade process.
4. Prepare your Phone: Install Cert_SPCS (search the forum), its a cab file that modifies security policies in the registry. Install netframework compact 3.5 on your phone, get it from the Microsoft site: plug in your phone, sync it and run the compact from your PC. Watch for prompts on your phone screen and accept them. Remmember to install the above in the device memmory and not the device storage.
5. Run your preferred RUU. Problems still? let me know, will be glad to help.

Connection Type has been changed to Serial in Bootloader

Dear Sirs;
I've done Hard Spl unsigned olinex 1.93 before and flashed various Cooked ROM befor (the last one was Diaduit 1.6.7). I decided to back to the original ROM, so connected the Diamond to computer and run the original ROM software (RUU_Diamond_HTC_WWE-ME_2.03.456.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe). everything was ok and the bar went to 100% BUT then Diamond hanged in Bootloader and "connection error" appeared in RUU screen. I flashed the diamond from internal memory by Diaduit "diamimg.nbh" file which I've placed there before but connection type has been changed from "USB" to "Serial" in Bootloader and I can't flash the mobile by PC anymore.
I will be rally apprecialed if you help to to change the "Serial" to "USB" in Bootloader.
Best Regards
Try following the steps in This Thread to ensure you have the right drivers for the connection on your computer.
If you have bad blocks in the onboard memory this should sort it out and then you can re-flash from internal storage.
MarkG
Let me correct the description. After complete the flash (by original ROM) in boot loader this message appears "Upgrade ROM code error. Please Try again" and in RUU screen (in PC) correction error appears.
I'm going to try MTTY.
Solved! It seems the problem related to the ROM (which I've downloaded from HTC site directly and installed successfully before!!?!) I tried another original ROM (RUU_Diamond_HTC_ARA_2.03.415.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe) and diamond flashed successfully!

Can't get into my HTC Desire

I flashed the Cyanogen Mod 7 onto the phone about 3 months ago, and today tried a different ROM as my girlfriend's O2 card (It's a UK Orange phone) wouldn't work in it, and the SIM unlock code which I paid for wasn't working - the guy I bought the code from said it's probably ROM-related.
I've tried flashing a LeeDroid ROM, and an INSERTCOIN ROM but neither work. With Leedroid I get bootloops, and with the other it gets to a colourful background but nothing else on screen and no other buttons do anything.
I've gone into bootloader mode and tried just running an exe file (for example an HTC_WWE_BRAVO_date_version number_etc from the laptop with the phone connected via USB, but this doesn't work either.
At my wit's end now as I think I've bricked the phone...
Can anyone help at all?
Why does flashing ruu not work?
ur supposed to be in fastboot. not hboot when trying to restore using ruu
Thanks for the tip -
I get as far as an updating signature message for about 10 seconds, then it crashes out with:
ERROR [131]: CUSTOMER ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
This problem is easy to fix. Create goldcard with linux, put this in your desire and then flash ruu again:
http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html
I managed to successfully create a goldcard, but upon flashing the RUU .exe file, it gets to the 'updating signature' part (before the percentage completion bar has even started) and then crashes out with the following message:
Error [132] SIGNARURE (sic) ERROR
Please try to flash again with a different ROM update utility (or words to that effect).
EDIT: Now working. Thanks MatDroid!!

Categories

Resources