Database Develop

HELP!!! Stuck at Boot Screen. NEED SD IMAGE FILE

Hope you guys can help me out. I disassembled my Cingular 8125 to try and improve the earpiece speaker. I put the device back together and turned it on and it sticks on the boot screen.
When I try to do a hard reset, I get to the point where I have to press send (green button), but then displays the following for a second and then goes back and freezes on the boot loader screen:
format FAT partition
format is complete
I've read some stuff about being able to recover from this using the SD card, but I'm not sure how to do it. If it is possible to recover from SD card, can someone please upload the appropriate files to the ftp site?
Please HELP!!! My ROM versions are below:
IPL: 2.16
SPL: 2.16
GSM: 02.07.10
OS: 2.16.9.1
Thanks!!!

Update:
I'm able to get to the mutli-colored screen by holding the Camera Button prior to starting the Wizard back on. I plug in my USB to my computer, but my computer says "USB Device Not Recognized". How can I get a new ROM on to my device? I tried running the ROMUpdateUtility.exe from a ROM, but it obviously wouldn't work because my computer doesn't see my phone. Please help!!
Thanks!!

Update #2:
When connected to the computer, I got to device manager and see an unknown device under USB. I uninstall the device and do a scan for hardware changes. This finds the phone, but it still shows up as an unknown device. It does say that device is ready to use, but when i try to run the ROM update utility, it still cannot find my phone.
Do I need special USB drivers for the phone to be recognized?
Please guys, any help would be greatly appreciated!
Thanks!!!

you shouldnt need any special driver for your computer to connect to Wizard.
did you install ActiveSync at all ? perhaps its using the driver from that installation....
What OS are you using ?

Yes, I've previously installed ActiveSync 4.1. I am using Windows XP. Would it help to try to uninstall/reinstall ActiveSync? I may give that a try. Will keep you posted. Any other suggestions?
EDIT:
Just tried to uninstall/reinstall ActiveSync and it still says USB device not recognized

it looks like a dead ROM, hope it has nothing to do with the hardware.
Anyway, you try looking through this forum, there are some people who've got stuck on the boot screen, and did a flash (via the bootloader screen, e.g. the multi colour one) on the ROM and seems to fix the problem. Probably you want to put this option last. Mean while, wait for others to repsond, and you may well start looking on how to flash the ROM from bootloader screen.

hanmin said:
it looks like a dead ROM, hope it has nothing to do with the hardware.
Anyway, you try looking through this forum, there are some people who've got stuck on the boot screen, and did a flash (via the bootloader screen, e.g. the multi colour one) on the ROM and seems to fix the problem. Probably you want to put this option last. Mean while, wait for others to repsond, and you may well start looking on how to flash the ROM from bootloader screen.
Click to expand...
Click to collapse
Thanks for responding. I'm ok with having to reflash, but the problem is that my computer doesn't seem to recognize my device when i'm at the multi color screen.
Isn't there a backup battery in these devices? I had my Wizard disassembled for 4 hours. I guess the backup battery could have died during this span, but even if it did, what implications would that have?

You still have hope
Get it to the bootloader screen. Connect via USB to your PC (make sure you have active sycn installed) and run an RUU to replace your ROM. I had to do this after trying to downgrade to the original Cingular ROM on my 8125. Scared the S*!T out of me when it hung on the Splash screen and wouldn't load. I thought it was toast but using the Bootloader and an RUU it put it back to normal again.
It won't look like the PC is recognizing the device but it will as long as its in Bootloader.
Let us know if you get it fixed.

Re: You still have hope
hellomoto_25 said:
Get it to the bootloader screen. Connect via USB to your PC (make sure you have active sycn installed) and run an RUU to replace your ROM. I had to do this after trying to downgrade to the original Cingular ROM on my 8125. Scared the S*!T out of me when it hung on the Splash screen and wouldn't load. I thought it was toast but using the Bootloader and an RUU it put it back to normal again.
It won't look like the PC is recognizing the device but it will as long as its in Bootloader.
Let us know if you get it fixed.
Click to expand...
Click to collapse
Thanks for the reply. The problem is that when I plug the device into my computer, I get a USB device not recognized error. I try to proceed with ROMUpdateUtility.exe anyways, and get this error:
"The update utility cannot connect to your PDA phone..."
Seems like updating via USB is not going to work for me. Can I write a backup to the SD card from the PC, put the SD card in the phone, and then boot from there? I've read some posts along these lines, but detailed steps would be very helpful. THANKS!!!

You need an SD card dump image.
This is NOT a file in the sense of a file on the SD card. Its a RAW image. You need someone who has dumped their firmware in that fashion to send you the SD image.
You then write it onto the SD card using something like "psdwrite" (which will, by the way, DESTROY the filesystem on the SD card - don't have anything on there you care about!) and then insert it into the phone with the power off. Hold the CAMERA button and turn it on; when it asks if you want to restore the image, hit VOICE.
Note that for 1.x IPLs/SPLs the backlight will be OFF during this procedure, so you have to pay attention and/or have a good flashlight handy.

Genesis3 said:
You need an SD card dump image.
This is NOT a file in the sense of a file on the SD card. Its a RAW image. You need someone who has dumped their firmware in that fashion to send you the SD image.
You then write it onto the SD card using something like "psdwrite" (which will, by the way, DESTROY the filesystem on the SD card - don't have anything on there you care about!) and then insert it into the phone with the power off. Hold the CAMERA button and turn it on; when it asks if you want to restore the image, hit VOICE.
Note that for 1.x IPLs/SPLs the backlight will be OFF during this procedure, so you have to pay attention and/or have a good flashlight handy.
Click to expand...
Click to collapse
Genesis3,
Thanks for your wonderful insight. I really appreciate your help.
Now can someone help me with getting an SD image? What constitutes an image file? Is it simply the .nbf file? Do I just use psdwrite and copy the nbf file onto the card? Is there something on the FTP site I can use? My configuration as mentioned in the original post is:
IPL: 2.16
SPL: 2.16
GSM: 02.07.10
OS: 2.16.9.1

I had a similar problem and reflashing the rom using the usb is possible. Don't use a flasing utility, though.
Find a self contained rom upgrade from the FTP. As long as you see USB on the bottom left side of your screen, it should work. After that, reflash with whatever rom you want. Hope it works. Nothing worse than an the feeling you have holding an expensive paper waight.

wireless_one said:
I had a similar problem and reflashing the rom using the usb is possible. Don't use a flasing utility, though.
Find a self contained rom upgrade from the FTP. As long as you see USB on the bottom left side of your screen, it should work. After that, reflash with whatever rom you want. Hope it works. Nothing worse than an the feeling you have holding an expensive paper waight.
Click to expand...
Click to collapse
Thanks for the reply. I'm not sure what you mean by "self contained rom". In the past, I've used K-JAM_WWE_216901_2169101_020710_ship.zip from the FTP site, and ran the ROMUpdateUtility.exe without any problem. Now, since I cannot make a connection to the computer via USB, I am unable to run ROMUpdateUtility.exe. Is there an alternative "self contained" file I can use that will work in spite of the unknown USB device message?
Thanks in advance...

try to DL this file: RUU_Prodigy_1060701_101_11310_QTEK_WWE_Ship.exe. Its on the FTP. Follow this link:
http://wiki.xda-developers.com/index.php?pagename=BA_FTP_Site
click on the FTP Root link, navigate here:
ftp://ftp.xda-developers.com/Wizard/Roms/Qtek/ and download the file. Put the phone in bootloader, attach to PC (make sure the phone has USB shown in the bottom left corner, and run the file.
Ignore any references to ActiveSync or any connections period. Just run it all the way through the installation process. When all is done, you can upgrade, down grade, etc using the appropriate method (I use aWizard) Let me know if this helps.
Wireless One

wireless_one said:
try to DL this file: RUU_Prodigy_1060701_101_11310_QTEK_WWE_Ship.exe. Its on the FTP. Follow this link:
http://wiki.xda-developers.com/index.php?pagename=BA_FTP_Site
click on the FTP Root link, navigate here:
ftp://ftp.xda-developers.com/Wizard/Roms/Qtek/ and download the file. Put the phone in bootloader, attach to PC (make sure the phone has USB shown in the bottom left corner, and run the file.
Ignore any references to ActiveSync or any connections period. Just run it all the way through the installation process. When all is done, you can upgrade, down grade, etc using the appropriate method (I use aWizard) Let me know if this helps.
Wireless One
Click to expand...
Click to collapse
Thanks for your reply. I've tried the course of action that you've suggested, but i cannot get through the installation process because of inadequate connectivity between the phone and my PC. I see the USB in the bottom left hand corner, plug into the PC, and immediately see a USB Unknown device error. I ignore that and try to run the ROM anyways and it fails and I get an Update Error:
"The Update Utility cannot connect to your PDA Phone. Please check that your USB/cradle is connected..."
That's why I think I got to go the SD card route, so anyone with an image file that i can put on my SD card, I really could use the help!

It is NOT a NBF file.
The problem with the 8125 is that if you are somehow not CID unlocked the wrong SD image will actually hurt you more than it helps.
You need to find someone with a Cingular 8125 SD image - I have one for the T-Mobile MDA but not for the Cingular "as-shipped" ROM.

Genesis3 said:
It is NOT a NBF file.
The problem with the 8125 is that if you are somehow not CID unlocked the wrong SD image will actually hurt you more than it helps.
You need to find someone with a Cingular 8125 SD image - I have one for the T-Mobile MDA but not for the Cingular "as-shipped" ROM.
Click to expand...
Click to collapse
Genesis3,
Thanks for confirming it's not a NBF file. I had previously CID unlocked using awizard and then installed a newer IMATE ROM:
IPL: 2.16
SPL: 2.16
GSM: 02.07.10
OS: 2.16.9.1
I did not install the IMATE Extended ROM or Cingular customizations after upgrading to the IMATE ROM. Do I still need a Cingular 8125 SD image, since i've already upgraded my ROM, or do I now need an IMATE SD image to match my current configuration? Or does the type of image file really not matter?
Thanks in advance!

I really hate to beg, but I am desparately seeking an SD image file backup. I'm going out of town in a couple of days, and would love to have a working wizard for my trip.
Can any one of you kind souls please upload your SD image file backup to the FTP site? It really is my last ditch effort before having to send the phone back.
I truly appreciate all the help and all the responses I have received to date.
THANKS!!!

sunil23 said:
I really hate to beg, but I am desparately seeking an SD image file backup. I'm going out of town in a couple of days, and would love to have a working wizard for my trip.
Can any one of you kind souls please upload your SD image file backup to the FTP site? It really is my last ditch effort before having to send the phone back.
I truly appreciate all the help and all the responses I have received to date.
THANKS!!!
Click to expand...
Click to collapse
Sunil,
i apologize for not responding your PM sooner but wasnt available due to travel plans.
I am trying to upload the files to the Upload folder now and i iwll let you know when i am done.
Thanks

getting permission denied when i tried to upload the documents.
is there another password i should be using besides xda/xda ?

Is it bricked? (Upgrade ROM error)

(I'm not 100% sure this is the correct forum, but since it is very ROM related it didn't feel all wrong to put it in here...)
Hi guys. After som serious flashing of cooked ROMs I decided for some unknown reason that I should try to restore a stock ROM. Now, being very tired as I was, i completely forgott that its probably a good idea to flash a new Stock ROM on the unit BEFORE flashing it with a signed SPL....so I just flashed the Signed SPL to the device. That in it self seem to have gone ok, because when I start the unit it say "SPL-1.15.0000". Problem is though that it also says "Upgrade ROM error, please try again"
Now, what should I do? Have tried put both signed and unsigned SPLs on the storage card and started up via the volume down/pwr button thingy, but that does not seem to do anything. I have also tried to attach the unit to a USB port when in tricolor mode ("USB" shows up on the screen) and tried the CustomRUU program. It finds the device and starts to "upgrade" (grey screen on the device with 0%) but then it just doesnt seem to get any further...
As the device was working fine with a custom ROM before I started all this, I suspect that the main problem proably is that I now have a Standard SPL with a cooked ROM, and that they collide sort of. I, as well as the Blackstone, is now stuck and I am all out of ideas what to do? Have also tried Hard and Soft resets, but that doesnt seem to change anything.
Help!

try removing the SD Card and put the phone into bootloader mode and re-flash the stock ROM! if this doesn't work ... still with the SD Card removed try flashing to USPL and flash the stock ROM again!
hope this helps

You can try USPL on your HD and flash a custom or stock ROM with it.

PapaDocta said:
try removing the SD Card and put the phone into bootloader mode and re-flash the stock ROM! if this doesn't work ... still with the SD Card removed try flashing to USPL and flash the stock ROM again!
hope this helps
Click to expand...
Click to collapse
Thanks for the feedback!
Just be be sure, "into bootloader mode" is when you start the device holding down volume down and powerkey until you see the tricolor screen? Then that is probably what I have tried to do for a while now without success (total success that is, I do get into the tricolored screen)). Or maybe I am doing something wrong, could you perhaps point to a detailed explaination besides the one in "HardSPL" thread?
USPL I havnt tried, will do that! Is it still so that trying to do USPL on Vista is asking for trouble?
I read somewhere that Stock ROMs should only be flashed from internal storage, not SD cards, is that true? If so, how do I go about accessing that storage now when it doesnt show up in the file explorer on my PC (PC recognizes it as USB device, "HTC Sync" but I get no file access to it).

improwise said:
Thanks for the feedback!
Just be be sure, "into bootloader mode" is when you start the device holding down volume down and powerkey until you see the tricolor screen? Then that is probably what I have tried to do for a while now without success. Or maybe I am doing something wrong, could you perhaps point to a detailed explaination besides the one in "HardSPL" thread?
USPL I havnt tried, will do that! Is it still so that trying to do USPL on Vista is asking for trouble?
Click to expand...
Click to collapse
just do uspl it will work

improwise said:
Thanks for the feedback!
Just be be sure, "into bootloader mode" is when you start the device holding down volume down and powerkey until you see the tricolor screen? Then that is probably what I have tried to do for a while now without success (total success that is, I do get into the tricolored screen)). Or maybe I am doing something wrong, could you perhaps point to a detailed explaination besides the one in "HardSPL" thread?
USPL I havnt tried, will do that! Is it still so that trying to do USPL on Vista is asking for trouble?
I read somewhere that Stock ROMs should only be flashed from internal storage, not SD cards, is that true? If so, how do I go about accessing that storage now when it doesnt show up in the file explorer on my PC (PC recognizes it as USB device, "HTC Sync" but I get no file access to it).
Click to expand...
Click to collapse
bootloader mode is when you power off the device and hold the volume button down and press power till you get the tricolor screen...
so here is what you need to do .
1. remove the sd card
2. go into the tricolor mode connect your device to the pc and make sure it says (USB) at the bottom
3. run the stock shipped exe from you pc
if that didn't work then you should try the USPL version.. and there is a guide if you are using vista.. i just tried and worked fine.. here it is
http://forum.xda-developers.com/showpost.php?p=3331078&postcount=153
and the reason i'm asking you to remove the sd card because if you have a rom (blacimg.nbh) it won't let you do anything it will try to flash from the sd card and right now you don't want to do that.
and you shouldn't put any rom into the internal storage of the phone..

PapaDocta said:
and you shouldn't put any rom into the internal storage of the phone..
Click to expand...
Click to collapse
What happens if you do that? will it try and flash over the flash? Proper *&@! it up?

nicelad_uk said:
What happens if you do that? will it try and flash over the flash? Proper *&@! it up?
Click to expand...
Click to collapse
i don't think anything would happen... the file will get deleted when you flash as the rest of the files in the internal memory

Thank you everyone! The USPL thing solved it, when I did it from a XP machine! The once bricked Blackstone is not alive an kicking again!
About USPL, I saw the workaround for Vista, but downgrading a few components to make it work just doesn't seem like a safe way to do it. And I cant help but to think that it might have unwanted side affects, ie affecting system stability. But maybe I am wrong?

Going back to shipped ROM without bricking?
Hi,
After reading this thread I am now a bit worried and, as a newbie, would appreciate maybe a "simple" answer to my question.
I''ve been experimenting with various cooked ROMs after following the guide in the WIKI for installing HardSPL and then putting the ROM file (BLACKIMG.nbh) on my SD card and installing it using the power on + volume down button method.
However, I now want to revert back to the original "shipped" ROM, which I have downloaded from the list of shipped ROMs via the WIKI (I downloaded the one which closely matched what was originally on my HD - as I didn't know how to backup the actual ROM on my HD at the time).
So, my question:
How should I put the downloaded original/shipped ROM:
RUU_BlackStone_HTC_WWE_1.14.405.3_Radio_52.49a.25.26_1.09.25.14_Ship.exe
into my HD without bricking it?! Do I just run it on my PC with ActiveSync enabled or do I need to do something to remove the HardSPL or something first?
Sorry if this has been answered previously but I get confused when a thread just makes loads of references to SPLthis and SPLthat etc.!

if you have the HardSPL already installed on your phone then you don't need to do anything more.. just connect your phone to the pc and let it sync (activesync enabled) and flash to any shipped rom you want by simply running the exe file..

PapaDocta said:
if you have the HardSPL already installed on your phone then you don't need to do anything more.. just connect your phone to the pc and let it sync (activesync enabled) and flash to any shipped rom you want by simply running the exe file..
Click to expand...
Click to collapse
Brilliant! Thanks for the simple answer Worked no problem!

Stuck With 1.14, No USB Support

Hi guys! Need some help, my device is stuck with HardSPL 1.14 because my USB Port on the phone is broken. Any method yet that i can use to flash a 1.56 ROM or upgrade to 1.56 HSPL only using SD Card Method??
Many Thanks!!

MarcWhittle said:
Hi guys! Need some help, my device is stuck with HardSPL 1.14 because my USB Port on the phone is broken. Any method yet that i can use to flash a 1.56 ROM or upgrade to 1.56 HSPL only using SD Card Method??
Many Thanks!!
Click to expand...
Click to collapse
is it 1.14.olinex or 1.14.00000

sorry, 1.14 Olinex

If i'm correct you should be able to flash the hspl by using the SD Card method.
I've have not tested this but they way i'd go would be as follows:
-download HSPLWrapper_Blackstone_156OliNex.exe from this forum
-run the exe in a seperate folder, it will extract it's content to run.
-look inside the folder and see the extracted files, keep the app open for now.
-copy RUU_Signed.nbh from the folder and place in another folder.
-close the app, the extracted files should be removed by it then.
-go to the new folder where you copied RUU_Signed.nbh and rename it to BLACIMG.nbh
-copy BLACIMG.nbh to your phone's SD Card
-enter the bootloader on your phone and it should launch the option the flash as it detects the BLACIMG.nbh
-finish flashing as usual and say some prayers while you reboot your phone
All theoretical here so i'd highly advise to read up in the dummy's thread about hspl/uspl when unsure or unfamiliar with it.
gl

righ, getting somewhere!!! did this method and it worked, now when i go into bootlaoder it says my SPL is 1.56 but it also always says 'Upgrade ROM Code Error Please Try Again' on the bootloader in the middle of the screen?

Not sure what that could be as im no spl expert but might be that the app that does it via usb actually crashes the bootloader to be able to load non htc spl. Since you cant run the app you can flash but generate the error cause it doesnt accept the non htc spl.
There is however also the following mentioned in the dummy's thread:
# Hard reset afterwards. Once or twice- up to you. Twice has been recommended. Turn off your phone. I personally do it right after flashing completes and I see the "Smart Mobility" screen. I just yank the battery out instead of waiting for it to boot up all the way and go through customization process just to hard reset Hold the volume down button and volume up button while you press the power on button. You should see a message saying "This operation will delete all your personal data, and reset all settings to the manufacturer default settings. Press VolUp to restore manufacturer defaults, or press other keys to cancel." Do exactly what it says...
# You are done!
Click to expand...
Click to collapse
Dont know if you did that already but if not give it go, keep in mind the bold part tho before you loose data.
ill have a look if i can find something, tho can never hurt to look for yourself ofcourse, let us know if you make some progression.

Perhaps this will help, from http://forum.xda-developers.com/showthread.php?t=431217
Anyone having problems with the device entering SSPL automatically, please copy SSPL-Manual-TouchHD.exe from SSPL-Manual-TouchHD.zip attachment to the device and run it. then once the screen is sayingn 1.07.OliNex, run RUU manually. i.e. you launch the Hard-SPL RUU (HardSPLWrapper_Blackstone.exe) on the PC and flash.
*important*: make sure that the USB cable is plugged in and device is synced to Windows Mobile even if doing manual SSPL method.
Click to expand...
Click to collapse
dunno if that last note is an option due to the broken port, but sounds like a good option if you ignore the on pc part. Else perhaps going back to a stock spl would be an option.

MarcWhittle said:
righ, getting somewhere!!! did this method and it worked, now when i go into bootlaoder it says my SPL is 1.56 but it also always says 'Upgrade ROM Code Error Please Try Again' on the bootloader in the middle of the screen?
Click to expand...
Click to collapse
if it says 1.56.olinex then choose the rom u want to flash
then rename the .nbh file dnloaded from the rom cooker to BLACIMG.NBH
place this file in the root of ur sd card.
now insert the sd card nd go to the bootloader.
follow onscreen instructions...

OK, after using the method suggested in post 3 i have managed to get OlinexHSPL 1.56 on it. I then installed Mary One v0.03 using SD card method. It all went AMAZING!!! Thanks doods!! I got my baby back!! Dont need to risk returning it to HTC Repairs now with dodgy spl and rom!!! YAY!!!

MarcWhittle said:
OK, after using the method suggested in post 3 i have managed to get OlinexHSPL 1.56 on it. I then installed Mary One v0.03 using SD card method. It all went AMAZING!!! Thanks doods!! I got my baby back!! Dont need to risk returning it to HTC Repairs now with dodgy spl and rom!!! YAY!!!
Click to expand...
Click to collapse
glad u made it..

Good to hear its fixed, enjoy your device again

Nice work guys, another happy customer.
Thread closed

Returning device to T-mobile for repair (still rooted)

My phone will not boot, after g1 logo and boot image goes to a black screen. in recovery it wont reognice i have an sd card inserted..
Right my question, since i cant unroot (without the use of an sd card) i will have to send it to tmobile to be repaired whilst still rooted. Has this been done before? will they just laugh at me and tell me to jog on.. or is there a chance they will still fix?
Thanks guys

You have a couple of options:
1) Send it in as-is (If you're freaking crazy)
2) Brick the thing (Pro choice FTW )
3) See if the bootloader will recognize the sdcard. Problem is, even if it does, you can't downgrade with 1.33.2005 (it will insta-brick). And as you can't flash the SPL via adb or fastboot, this is more just me rambling than an viable answer.
My suggestion is brick it (if the bootloader will accept the card) and tell tmo an OTA update did it.
EDIT: Just realized I assumed you had 1.33.2005 SPL (Seem to remember a thread about flashing it, might not have been by you though...). If you have stock or hardspl then downgrading shouldn't (again, shouldn't) brick on dowgrade.

yep i have 1.33.2005 SPL.. think im going to have to go with brick'me option.
whats the best/easiest way to go about it? i have zero experience with fastboot and adb.. :/
thanks for your time

To brick, grab the RC7 NBH and put it on your SD card as DREAIMG.nbh. Boot in to the SPL (power+camera) and follow the instructions to flash. If it doesn't reocgnize the SD card then you could try flashing the old radio via fastboot.

Well if you're able to put a rom on the sdcard and run the update.zip then why not just try to flash a rom first?
Also, you can ADB a recovery into the phone... that will fix your recovery, i'm assuming you have the newest radio since you have the danger spl.
so you have newest radio and danger SPL already....
just ADB a recovery into the phone and that will hopefully get your SDCard recognized... once that's done, just put a rom in the sdcard and flash it
worst case: as long as you have insurance... tmobile doesn't care that you rooted or modded your G1 (As long as you didn't actually open up the phone and depending on the insurance you have... as long as it's not wet.

so when you choose zip from recovery, it wont show any of the roms/themes you have saved on your sd card?
surely there is something that can be done to save the phone here?
I would post this in the brick think-tank thread.
worst case: as long as you have insurance... tmobile doesn't care that you rooted or modded your G1 (As long as you didn't actually open up the phone and depending on the insurance you have... as long as it's not wet.
Click to expand...
Click to collapse
WHAT??????????

[HELP] I think I bricked my Rogers Dream!

i was following this guide here http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod and everything seemed to go smoothly. i verified the md5 thing and it matched and everything. my sd card is fat32 for the record. i got to where it was flashing the spl. the screen stayed saying it was flashing for a really long time and half way through the device rebooted itself. It was plugged into its charger and I was not touching it. It just rebooted prematurely before the spl had been flashed. now when I boot up it doesnt bring up android or anything!
i bought this phone second hand and unlocked it, im using it with telus. If its bricked can i send it anywhere to get fixed?
edit: not sure if it means anything but it said HBOOT was 0009 not 0010. apparently 0010 was perfect spl or something like that. im not sure if this matters but its just something i noticed.

ddd67 said:
It just rebooted prematurely before the spl had been flashed. now when I boot up it doesnt bring up android or anything!
i bought this phone second hand and unlocked it, im using it with telus. If its bricked can i send it anywhere to get fixed?
edit: not sure if it means anything but it said HBOOT was 0009 not 0010. apparently 0010 was perfect spl or something like that. im not sure if this matters but its just something i noticed.
Click to expand...
Click to collapse
So can you get into recovery or fastboot?

Ace42 said:
So can you get into recovery or fastboot?
Click to expand...
Click to collapse
No, it doesn't do anything.

can anyone help PLEASE

If you interrupted the spl flash (why would you do that btw?!) and you cant enter recovery or bootloader, you're bricked.

ddd67 said:
No, it doesn't do anything.
Click to expand...
Click to collapse
Which spl were you flashing? Did you flash a radio first?
Not being an ass, but you do know how to enter these modes, right.
Fastboot= camera+power held down
Recovery= home+power held down
If it is indeed bricked, there are very few solutions. Only working one is replacing board at the moment. There is other ways trying to be had in development forum as we speak. Don't start a new theard, but search and read thoses, maybe something can help you/help them.

goldenarmZ said:
If you interrupted the spl flash (why would you do that btw?!) and you cant enter recovery or bootloader, you're bricked.
Click to expand...
Click to collapse
That's the thing, I didn't interrupt the flash. I thought that if I checked the md5 hash that it would work perfectly. I didnt know it could fail without me doing anything.
fastludeh22 said:
Which spl were you flashing? Did you flash a radio first?
Not being an ass, but you do know how to enter these modes, right.
Fastboot= camera+power held down
Recovery= home+power held down
If it is indeed bricked, there are very few solutions. Only working one is replacing board at the moment. There is other ways trying to be had in development forum as we speak. Don't start a new theard, but search and read thoses, maybe something can help you/help them.
Click to expand...
Click to collapse
Can I send the phone anywhere and get it fixed?
goldenarmZ said:
If you interrupted the spl flash (why would you do that btw?!) and you cant enter recovery or bootloader, you're bricked.
Click to expand...
Click to collapse
I followed this guide:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
My dream is a rogers one, so I assume its EBl1, I haven't done anything to it besides follow that guide.
1. I got my 2GB memory card and formatted it to FAT32 on my computer.
2. I put spl-1332005.zip on the card (I kept it as a zip)
3. I downloaded this file: signed-dream_devphone_userdebug-img-14721.zip
4. I opened that file I downloaded and copied system.img to my memory card.
5. I downloaded update-cm-4.2.x-signed.zip and bc-4.2.x-ebi1-signed.zip on my SD cards root.
6. I installed zinx recovery flasher and cm-recovery-1.4 32A flashed onto my phone (now that I think about it I didnt check to see if my phones 32A. I don't know where to do that)
7. I booted into cyanogenmod screen.
8. I flashed the SPL, it didn't get interrupted and I thought all went right, but I guess not.
That is everything I did. did I do something wrong?

ddd67 said:
That's the thing, I didn't interrupt the flash. I thought that if I checked the md5 hash that it would work perfectly. I didnt know it could fail without me doing anything.
Can I send the phone anywhere and get it fixed?
I followed this guide:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
My dream is a rogers one, so I assume its EBl1, I haven't done anything to it besides follow that guide.
1. I got my 2GB memory card and formatted it to FAT32 on my computer.
2. I put spl-1332005.zip on the card (I kept it as a zip)
3. I downloaded this file: signed-dream_devphone_userdebug-img-14721.zip
4. I opened that file I downloaded and copied system.img to my memory card.
5. I downloaded update-cm-4.2.x-signed.zip and bc-4.2.x-ebi1-signed.zip on my SD cards root.
6. I installed zinx recovery flasher and cm-recovery-1.4 32A flashed onto my phone (now that I think about it I didnt check to see if my phones 32A. I don't know where to do that)
7. I booted into cyanogenmod screen.
8. I flashed the SPL, it didn't get interrupted and I thought all went right, but I guess not.
That is everything I did. did I do something wrong?
Click to expand...
Click to collapse
It looks as if you didn't flash the radio first. the 26I radio, that is

Oh man, which part of the guide shows me how to flash the radio?

ddd67 said:
Oh man, which part of the guide shows me how to flash the radio?
Click to expand...
Click to collapse
If you flashed the spl already, it is too late. The radio NEEDS to be flashed first

@ people telling him to flash the radio, if you're following that guide, you don't flash the radio, you leave it as is.
He did nothing wrong, he just got ****ed up by pure chance, though if he were reading the guide closely he would realize that he wasn't supposed to put system.img on his SD card.

That SPL is safe on all Rogers dreams.. either you were spectacularly unlucky with a bad flash, or it isn't actually bricked.. Remove the battery, hold the camera button, replace the battery and power on.. anything?

goldenarmZ said:
That SPL is safe on all Rogers dreams.. either you were spectacularly unlucky with a bad flash, or it isn't actually bricked.. Remove the battery, hold the camera button, replace the battery and power on.. anything?
Click to expand...
Click to collapse
No dice. I didn't think it was possible for it to just brick on its own accord

AHH!
So I followed the turorial on updating the rogers HTC Dream to a T. I successfully changed the SPL to 1.33.2005 but the "system.img" file is no longers available on the HTC developer website. I tried using the system.img file from the Google I/O page (from the HTC developer website) but was left with a phone that pretty much was an HTC version of the iPod touch with no phone-related-applications working. does anyone have a backup of that system.img file for android 1.6 for the Htc DREAM??
Thanx
Meldon

@meldonlobo, are you looking for this?
http://forum.xda-developers.com/showthread.php?t=593626

I thought this was 100% safe. what happened?

my radio version was 3.22.20.17 and HBOOT-1.33.0009 (DREA21000). my friend told me to post that because it might help. Is that radio right for following the guide?? It also says 32B not A. The tutorial mentions something about 32A. Is that why?
i remember that if i went to recovery mode when it was stock it showd an exclamation mark

Please can someone tell?