Database Develop

Flash Only Gets to 1%

Hello xda
I've been following the flashing guide for my p3600i, but have hit a snag.
After flashing HardSPL 3.20 and the current radio ROM, I can't flash any cooked ROM's. Attempting to flash any ROM results in error code 270 after 1% and reboots the phone. I still have access to the original OS after it boots back up. I'm attempting this on Vista using the XP drivers for HTC USB Sync.
Any ideas?
Edit: I've read that I need to modify HTC p3600 based ROM's to work on the p3600i, but this information isn't listed in the stickied guide. Is this still accurate, and if it is, can someone point me in the right direction on how to do this?

The guides are up-to-date and have worked for many people.
Have you tried to boot to the tri-colour screen by holding down the power button, camera button and pressing in the bottom soft reset button all at the same time?
Do that and confirm you have Olipro's HardSPL installed properly.
EDIT: I think I know what your problem might be. When you flash a ROM, IGNORE THE DIRECTIONS ON THE PROGRAM YOU RUN.
Do this, AND ONLY THIS don't do anything else.
Enter the tri-colour flash screen manually on your phone (holding down the 3 buttons). when you get this screen, connect the phone to your computer. Confirm you see the phone display Olipro's HardSPL 3.20 as installed, and at the bottom once connected to the PC, USB as the connection.
From there, run the upgrade program to flash the ROM. Ignore the instructions on the screen and keep clicking continue.
That might be why youre having the problem - you need to ALREADY be in the tri-colour bootscreen before running the flashing program.
Good luck!

Ok, I definately need to patch p3600 ROM's to work on my p3600i. I've patched Mary's 3.7 Lite and that seems to have installed and booted, so I'm away.
Edit: I can confirm I was following the guide precisely, but it's a guide for Trinity P3600, not for P3600i. It doesn't mention the required patching (it really should). I can also confirm I have the correct HardSPL installed and it seems to working now. Someone needs to add a note for P3600i users to that sticky.

You don't need to patch anything.
There is a sticky in the upgrading section for P3600i ROMs that have been tested and are working. Use those and you won't have any issues (Y)
I just had a look and at the end the ROM Collection thread is mentioned. You obviously didn't read to the end.

TheGuitarPlayer said:
Hello xda
I've been following the flashing guide for my p3600i, but have hit a snag.
After flashing HardSPL 3.20 and the current radio ROM, I can't flash any cooked ROM's. Attempting to flash any ROM results in error code 270 after 1% and reboots the phone. I still have access to the original OS after it boots back up. I'm attempting this on Vista using the XP drivers for HTC USB Sync.
Any ideas?
Edit: I've read that I need to modify HTC p3600 based ROM's to work on the p3600i, but this information isn't listed in the stickied guide. Is this still accurate, and if it is, can someone point me in the right direction on how to do this?
Click to expand...
Click to collapse
I have EXACTLY the same problem as you.
Also I extracted the official ROM into a folder, then extract the cooked ROM 6.1 and get the .nbf (ROM only) file into the official extract folder and tried to flash. At this point the error says: error: NAND 128 is on this rom where the target (which is p3600i) is NAND 256.
so the structure of NAND is different that's why got error.
I saw the correction is to change 400 to 401 in the name of the os file and bake again. This may help but I don't know how to do it yet...

vnt said:
I saw the correction is to change 400 to 401 in the name of the os file and bake again. This may help but I don't know how to do it yet...
Click to expand...
Click to collapse
Um retard did you read what I wrote? You DON'T need to patch anything. Follow the flashing instructions, and IF you read them to the end you'll see it point to the ROM Collection link for the P3600i. For the ROMs linked to in this thread there is no flashing required - they're already done.

Don't call him a retard. I certainly read to the end and but Mediafire was down last night and I had to get the Mary 3.7 Lite ROM from the original Mary's 3.7 thread. This is why I had to patch them manually. The thread doesn't mention that the linked to ROM's are different then those in the original thread about each ROM, hence this is where I went wrong. If I had know the mediafire linked ROM's were different then the ones in each individual thread, I would have waited until mediafire was back up.

New in flashing cooked roms - HELP

I will do it for the first time - Dutty's 1.8 ROM. I don't know the tools etc,...
Can someone help me how to do it and how to save original rom.
Thanks
Dave

Surfer_D said:
I will do it for the first time - Dutty's 1.8 ROM. I don't know the tools etc,...
Can someone help me how to do it and how to save original rom.
Thanks
Dave
Click to expand...
Click to collapse
Well first i dont really know how to save the original ROM but don't worry. The most of the original ROMs are available at the blackstoneWIKI so you can check if your version is listed before flashing.
When it comes to the flashing itself it's really easy. First of all download USPL from this site. Then you download the ROM you want to flash with. If the ROM is named nbhsigned.nbh you will want to change this to BLACIMG.nbh and if it's already named BLACIMG.nbh just leave it like that. Then you copy BLACIMG.nbh to the root of your storage card (the main folder). Then you go to activesync->connection settings->disable USB connections.
Now turn the phone off and remove your storage card. Enter bootloader mode by pressing PowerON and volDOWN simultaneously. When your in bootloader mode wait for the text "serial" at the bottom to change to USB. When it says USB you insert your storage card. After that you run blac_uspl in the USPL folder you downloaded. The phone will now restart and come back in USPL bootloader mode. USPL will update and recognize BLACIMG.nbh in your storage card and it will ask if you want to update. Press yes and your good to go.
You should backup all your important files before flashing and remember this way of flashing isn't 100% secure and I can't assure you that you're phone won't break, but following these steps closely really should narrow down the risks with flashing by alot.
Hope this helped you!

Thank you! This helped me too Can i do it with Windows 7?

Thanks friend, I tried it but I'm having a little difficulties When I use the tool I et an error message about USB - it can't find the phone.
Any ideas?
I did as you wrote and it worked till I used the EXE tool. There nothing happenes. I downloaded the latest version, but I0m using Vista. Acording to post where I downloaded it it should work on Vista.
Thanks for everything
Dave

First dump your rom using the method described here:
http://forum.xda-developers.com/showthread.php?t=427507
After that's done flash HardSPL described here:
http://forum.xda-developers.com/showthread.php?t=431217
A littlebit of reading wouldn't hurd you I think.
Also in Dutty's thread the procedure is well described how to flash so why open a new thread?
Surfer_D said:
Thanks friend, I tried it but I'm having a little difficulties When I use the tool I et an error message about USB - it can't find the phone.
Any ideas?
I did as you wrote and it worked till I used the EXE tool. There nothing happenes. I downloaded the latest version, but I0m using Vista. Acording to post where I downloaded it it should work on Vista.
Thanks for everything
Dave
Click to expand...
Click to collapse

Thanks Leo for the step by step
@OP, please read/search the sticky posts, wiki, ROM thread (and the rest of the forum if need be ) before starting a new thread.
Thread closed as per forum guidelines,
Dave

Problem flashing rom

Hi,
Although this is my first post, I have been lurking for many years.
I have successfully flashed a Kaiser and a Diamond in the past so I feel reasonably confident.
However, I am having real problems with my blackstone. I have followed the instructions until point 5, when I enter bootloader it is showing 1.14000 etc - I then try to follow the rest of the instructions. It will go into the rom updater utility, the screen will go grey and show 0% but then nothing happens and I eventually have to go into recovery.
Any ideas?
Thanks
Caroline

cazlol said:
Hi,
Although this is my first post, I have been lurking for many years.
I have successfully flashed a Kaiser and a Diamond in the past so I feel reasonably confident.
However, I am having real problems with my blackstone. I have followed the instructions until point 5, when I enter bootloader it is showing 1.14000 etc - I then try to follow the rest of the instructions. It will go into the rom updater utility, the screen will go grey and show 0% but then nothing happens and I eventually have to go into recovery.
Any ideas?
Thanks
Caroline
Click to expand...
Click to collapse
Sounds like you haven't installed either HSPL or USPL before trying to flash rom.
I'd recommend going down the HSPL route. (Latest HSPL can be found in my signature). Once downloaded flash to phone then you are ready to flash to cooked roms

Hi,
Thanks for replying. I just tried that and have the same problem.
What have I done wrong??
Caroline

cazlol said:
Hi,
Thanks for replying. I just tried that and have the same problem.
What have I done wrong??
Caroline
Click to expand...
Click to collapse
Go into bootloader. If it says 1.14.0000 you are ready to go to step (5c). When you connect usb cable to pc does the text at bottom change from 'serial' to 'USB'?
Possible problems could be:
1. You haven't disabled anti-virus
2. Drivers on you pc need updated. Download step (1g) and go to (0).
If USPL is successful it should state SPL v 1.15.USPL in bootloader. If HSPL is successful it should state SPL v 1.15 OliNex

Hi,
Well after much swearing at both computer and phone, I managed to get the drivers updated. Many thanks Spartan, it seems that this was the problem as I am flashing Dutty's ROM right now.
Thanks for your help.
Caroline

cazlol said:
Hi,
Well after much swearing at both computer and phone, I managed to get the drivers updated. Many thanks Spartan, it seems that this was the problem as I am flashing Dutty's ROM right now.
Thanks for your help.
Caroline
Click to expand...
Click to collapse
No prob's, just glad you got it sorted

Potentially Broken T.HD - Need help!

Hi All,
I have used the search function - but ended up getting confused.
I have a Touch HD that I bought in January of this year (2009) from Mobiles.co.uk (Carphone Warehouse) and is on the O2 network (UK).
I have been using Dutty's ROMs (both 6.1 and 6.5) for months now - and have always used USPL when flashing, using the SD card method.
Over the past 3 days, my HD has been playing up.
When it started, I was using Dutty's R7. The radio was 1.14.something.something. The device was working perfectly, and I was really happy with the ROM and the way the phone was working. I had installed NO other applications with the exception of a different taskbar and obviously SDKCerts.cab
First of all, HTC Sense stopped working - it would cycle between "Loading HTC Sense" and "Tap here to launch HTC Sense"
Then, when rebooting the device, it just hung on the "Smart Mobility" screen. I left it in case it just needed a while to boot, but nothing.
I had no other option than to hard reset.
It worked OK for a few hours, but then HTC Sense started to crash again. So I flashed a new ROM - Lost in Asia or whatever it is called.
Same symptoms.
I flashed Dutty's R7 back and also the new 1.17 radio.
No joy.
The phone also hangs for ages on the Smart Mobility screen - perhaps a full minute where as before, it used to be no more than 15 seconds or so.
The following is displayed on the "Smart Mobility Screen"
1.17.25.09
52.69.25.37H
1.59.Dutty
The bootloader screen (before running USPL) shows the following:
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) V6
So the question I'm asking - is... Is my phone suffering some kind of hardware malfunction, or is this a known and fixable fault that I somehow have caused?
If the phone looks like it is malfunctioning, how would I go about returning it to stock so that the CPWH repair centre do not know it's had an unofficial ROM installed?
I'd like to add that whilst I'm very PC literate, I'm no programmer and a lot of the stuff here is alien to me hence my confusion - I just know how to flash a new ROM etc.
Thanks to anyone that takes the time to help me - I'd be really thankful to anyone that helps me sort this - be it tell me how to fix the device, or tells me to take it back!
Thanks in advance & Regards,
Chris.

Will D/L and flash Dutty's R0 Holy Grail ROM and see if that makes a difference...

If you've been using uspl than it will still be the stock spl and thus you could try to load the stock rom from htc.com specially designed for the touch hd(blackstone). I've read and heard from a lot of people that after flashing several roms and even hard resetting afterwards, some bits and pieces stay behind and flashing an original stock rom will undo this. I don't think it's a radio issue. And another big thing if you use dutty R7 that's a 1.56+ rom so you should have the right uspl olinex software to load these roms, if you used older software then problems with colouring and other things will appear.

a1gp said:
If you've been using uspl than it will still be the stock spl and thus you could try to load the stock rom from htc.com specially designed for the touch hd(blackstone). I've read and heard from a lot of people that after flashing several roms and even hard resetting afterwards, some bits and pieces stay behind and flashing an original stock rom will undo this. I don't think it's a radio issue. And another big thing if you use dutty R7 that's a 1.56+ rom so you should have the right uspl olinex software to load these roms, if you used older software then problems with colouring and other things will appear.
Click to expand...
Click to collapse
Thanks for the quick reply.
So is it perhaps better to revert to the original ROM before flashing a cooked ROM? I always Hard Reset twice after flashing as understand this helps.
OK - so the 1.56+ situation - I was under the impression that using the latest USPL (2.5) when flashing was OK? I have never had the colour problem... but perhaps if I'm flashing wrong then these problems could be to do with this?
Thanks again...
Chris

The Sense Manila has known bug that you need to press home to load it (sometimes).
For you case, I would suggest you to clean up your SD Card.
there may be several file that cause your system to freeze.
So, format your SD, hard reset.. and cross fingers.

Yes, It is better to revert to the original rom once in a while before flashing a new rom, if u used the latest uspl and the colours are ok, then you've done that right and it will probably be bits and pieces of old flashed roms floating around on the device.
Best to revert to stock rom and hard reset twice.
Afterwards flash the rom u want. If everything works again. U could hspl instead of uspl, hspl is more stable if u ask me. And you can go back to stock spl if you have waranty issues. there's a tut on that to in the rom section.

mcdull said:
The Sense Manila has known bug that you need to press home to load it (sometimes).
For you case, I would suggest you to clean up your SD Card.
there may be several file that cause your system to freeze.
So, format your SD, hard reset.. and cross fingers.
Click to expand...
Click to collapse
I forgot to mention - that was one of the things I did. Previously, I had loads of email folders from all the ROM installs.
Now I have a folder containing the useful CAB files that I need, and the ROM image file. Thats it.
It's only a 1gb card as my 8gb card gave up the ghost.
Thanks for the suggestion though and my apologies for not mentioning this in the initial post.
From reading the Dummies guide, am I right in thinking that in order to use a 1.55+ ROM (such as Dutty's Holy Grail R0) I only need to run USPL and then flash (as opposed to flash a newer SPL) as my stock SPL is already 1.54?

a1gp said:
Yes, It is better to revert to the original rom once in a while before flashing a new rom, if u used the latest uspl and the colours are ok, then you've done that right and it will probably be bits and pieces of old flashed roms floating around on the device.
Best to revert to stock rom and hard reset twice.
Afterwards flash the rom u want. If everything works again. U could hspl instead of uspl, hspl is more stable if u ask me. And you can go back to stock spl if you have waranty issues. there's a tut on that to in the rom section.
Click to expand...
Click to collapse
Thanks for this - I didnt realise the device would retain bits and bobs, and you may well be right in that things are getting corrupted in there!
Which is the best stock ROM to flash - is there a link to one? I looked on the Wiki and there seem to be loads... which will work on a UK T8282?!
Thanks again!
Chris

constablechris said:
I forgot to mention - that was one of the things I did. Previously, I had loads of email folders from all the ROM installs.
Now I have a folder containing the useful CAB files that I need, and the ROM image file. Thats it.
It's only a 1gb card as my 8gb card gave up the ghost.
Thanks for the suggestion though and my apologies for not mentioning this in the initial post.
From reading the Dummies guide, am I right in thinking that in order to use a 1.55+ ROM (such as Dutty's Holy Grail R0) I only need to run USPL and then flash (as opposed to flash a newer SPL) as my stock SPL is already 1.54?
Click to expand...
Click to collapse
what do you mean hang for age?
1 minute is nothing if it turns out boot up.
There are chances that the nand flash needs to refresh and wasted some times. But it won't be forever.

constablechris said:
Thanks for this - I didnt realise the device would retain bits and bobs, and you may well be right in that things are getting corrupted in there!
Which is the best stock ROM to flash - is there a link to one? I looked on the Wiki and there seem to be loads... which will work on a UK T8282?!
Thanks again!
Chris
Click to expand...
Click to collapse
there's an original rom on htc.com for blackstone just use that one.
hope it will turn out right for you

I thought I'm the only one who had this problem. Last Sunday my blackstone started to freeze on the smart mobility screen too. I flash 3 different roms because I thought its an rom issue with no luck. On Monday it even managed to hardreset itself after I waited for about 15 min in the smart mobility screen.
After that I flashed a stock rom and it seem to be fine by now.
But now I will flash a custom again, the stock one is so 6.1

Another scream for help...

Hi,
I have my HD from march and being interested in WM6.5 and disappointed by HTC because they do not release an upgrade I decided to try some cooked roms.
I used USPL so that I can keep my original SPL.
I tried:
* Duttys WM6.5 Sense 2.1 Holy Grail
* Duttys WM6.5 Leo Holy Grail
* Topix HD
From the first boot I have noisy screen image with 4 colours or something .... but after entering in sleep mode and restore it recovers to normal "true color" until I reset the device. I can live with that but the real issue is that I cannot start my phone using the original radio neither with the latest versions I found for HTC HD. No error there, it simply stays off after I confirm that I want to enable the phone.
Also the device is hanging for very long time now and then and I have exactly the same problem/behaviour with all the above roms. I tried some fixes found in the forum but nothing works and I did not found anybody with the same weird behaviour.
I wand to recover my stock firmware but I found that even I brought mine from Romania it has a Czech S/N and HTC does not provide a stock ROM for this "v1.56.402 - Czech republic - not supported".
What can I do. do you guys know if I can get the original firmware from somewhere?
Thanks.

Obviously you havent bothered to read anything let alone the guidelines of starting new threads.
The answers are in the forum I suggest you take time to read and start by reading the forum guidelines and the sticky threads.
If you dont understand what you're doing then stick to a stock ROM until you do or you might brick your phone.

You say that you used uspl. Are you sure that it was successful as the symptoms you describe are typical when you have the incorrect spl for the rom you are using. After using uspl, what spl is showing in the bootloader screen?
Follow the steps in the Dummies Guide to Flashing and your problems should be sorted out.
If you still have further questions, post them in that thread as the mods will close this one as soon as they come across it (as explained by homer285)

you're ok as long as you can still go to bootloader mode, then go back to the uspl 2.5 guide here, FOLLOW INSTRUCTIONS STEP BY STEP
http://forum.xda-developers.com/showthread.php?t=505377
and here
http://forum.xda-developers.com/showthread.php?t=462347
format your sd card using fat32 (full format) (if you are a frequent flasher I suggest you get a small capacity sd card – 1Gb - and devote this only for flashing)
rename the RUU_signed.nbh to BLACIMG.nbh and pair this with ROMUpdateUtility -(application file) OR BlackstoneRUUWrapper (whichever the ROM cook presents) copy these TWO files in your formatted sd card.
then using Digital Outcast's USPL GUI: look here
http://forum.xda-developers.com/showthread.php?t=508361
if you're using Vista see this to update your sync driver
http://www.modaco.com/content/windo...u-on-vista-it-can-be-done-the-ultimate-guide/
flash the ROM.
I hope I make the above clear to you.

suggestion: Read the howtos!
If I was you I would do like this:
- flash hspl.
- flash latest radio from memorystick
- flash any 23xxx-rom from memstick (miri or phamQ can I recommend).
Cant understand why you are doing it the complicated way... there are ways to recover to original-spl if needed. This is the easyest way to flash 6.5 and it is almost fail-safe.
good luck!

brumbrum said:
suggestion: Read the howtos!
If I was you I would do like this:
- flash hspl.
- flash latest radio from memorystick
- flash any 23xxx-rom from memstick (miri or phamQ can I recommend).
Cant understand why you are doing it the complicated way... there are ways to recover to original-spl if needed. This is the easyest way to do it and it is almost fail-safe.
good luck!
Click to expand...
Click to collapse
dont add to the confusion, he is already using USPL, the SAFEST METHOD as stated by Dutty Throy, he even advocates this in all of his cooked ROMs
all he needs to do is to redo the steps again as i posted above.

Sorry for my panic post
Yes, after 8 hours of trying stuff I did not read post guide-lines but I searched all the internet and xda forums, tried all the dumb fixes for my weird behaviours without any success.
I am sure that my original rom it is not available and I call for help from people that have Czech S/N English version to extract the flash and the radio if it is no so complicated or if they have it as backup.
Actually I read every "flashing for dummies" posts and only when I thought I got everything I started to flash it.
I used the latest 2.5 USPL, the GUI one and also the command line from the cmd prompt so I saw all the output lines and there was no error at all. It is clear that the device was successfully flashed and I respected all the version requirements stated in description of the packages. The problem comes from some sort of incompatibility. The versions at boot is the right one.
The only wrong thing I did was after seeing USPL 2.5 coloured boot loader I go on with the tutorial which said to read on screen RUU instructions which said to connect with activesync and I did as they said and restart the device, cradle and continue flashing in which case the original SPL started and I got a flashing error on the desktop client but after restarting the device everything run normally with the stock firmware and I think I have a good understanding on how it work and I can say that that error does not hurt a bit.
I finally succeed, in the morning, to flash 6.1 vanilla topaz and almost everything works except the GPS module and I am investigating this issue.
It is clear that you cannot help me an my device issue related to WM6.5 roms are unique and I will investigate this on my own.
Sorry to everybody, again, for my wrong located post and have a nice day.