Database Develop

Question on Haykuro's SPL

i had CM 4.1.999 and i wanted to try out a hero rom so i decided to flash to the latest radio and spl. i flashed the radio succesfully, but when i flashed my spl (through CM 1.4 recovery), i got this error message saying the installation isnt complete.
"E:Multiple firmware images
E:cant store hboot image
E:failure ate line 1:
Installation aborted"
and idk if this helps but when i went into the bootloader it said i had the latest radio and spl, but in hboot it tried to run something (im not sure what) and it kept on saying "no image!"
any help would be greatly appreciated
and i did search before posting this and i couldnt find anything...
thanks once again
-ballerhaller

what does it say next to HBOOT in the bootloader?

No image! seems to be referring to not finding DREAIMG.nbh on the sdcard so you can just ignore that. And as long as it says HBOOT 1.33.2005 I would go ahead and try flashing a Hero ROM to see if it works cuz it can't hurt right? You already did the stuff that could potentially brick your phone.

B-man007 said:
what does it say next to HBOOT in the bootloader?
Click to expand...
Click to collapse
it says
1.33.2005 (Drea10000)
but whenever i push the camera button to go into hboot mode, it tries to load an image of the sd card and it says No Image!

one more thing, when my phone is off and plugged into the charger the LED light is red? could that mean anything?

Nah. Just restart into recovery. There's not much more you need to do in the Bootloader aside from using fastboot (via back button, the camera button is for flashing DREAIMG.nbh so that's why its saying "No Image!"

ok, it boots back into recovery after the spl is flashed, but at the bottom it says "Formatting CACHE:..." and the spl never finishes flashing because the installation cant be complete

ballerhaller said:
one more thing, when my phone is off and plugged into the charger the LED light is red? could that mean anything?
Click to expand...
Click to collapse
lol its red cause your battery is less than 90% charged and charging...
you already have the latest spl if it says 1.33.2005
just continue flashing the rom

..but is that possible if spl never finished flashing in recovery??

ballerhaller said:
..but is that possible if spl never finished flashing in recovery??
Click to expand...
Click to collapse
Like I said before, the easiest way to test if it worked is to flash a Hero ROM on there. If it was successful, then everything will be peachy; if it didn't work, then you'll get an error during the flash. Either way, I don't think you'll brick your phone.
Just make sure the error is an error that corresponds to not having the correct SPL vs not wiping your data partition or whatever.

ballerhaller said:
..but is that possible if spl never finished flashing in recovery??
Click to expand...
Click to collapse
i guess so..... i havent heard of it, but if it says 1.33.2005 in bootloader, then you have the haykuro spl
i searched your error and found people had that error but the spl installed fine anyway. go ahead and flash your rom and see if it throws any errors

thanks a lot guys, i went ahead and flashed the rom and got no error
thx for your time guys
and b-man, sorry, but i looked and i couldnt find another thread with a similar situation, i guess im blind? haha

ballerhaller said:
thanks a lot guys, i went ahead and flashed the rom and got no error
thx for your time guys
and b-man, sorry, but i looked and i couldnt find another thread with a similar situation, i guess im blind? haha
Click to expand...
Click to collapse
lol np it took me a while to find too, and it wasn't in a specific thead. it was in a thread for haykuros 6.0 rom which was one of the first roms that needed the new spl. people were discussing the spl flash on there and 2 people mentioned it and said everything worked fine

[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?

Please help ASAP

Hello everyone,
I have a rooted g1 and I was putting on the 2.1 rom on my phone. I was following a guys instruction off of youtube but it totally messed my phone up. Now its stuck on the pitcure with the open box pointing a yellow arrow on the phone right next to it(the update screen), what do I do??? Thanks for your help.

You dont even have root then...If it shows what i think your taking about....You should follow this simple enough my little brother(7yr) could master it:
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/

no i have root access i already had about 5 other roms on there but this guy said that you need a radio update sign. the guys site is http://www.youtube.com/watch?v=QfPI9Qdagd0&feature=related

Sagz326 said:
no i have root access i already had about 5 other roms on there but this guy said that you need a radio update sign. the guys site is http://www.youtube.com/watch?v=QfPI9Qdagd0&feature=related
Click to expand...
Click to collapse
If you had root why did you flash the radio again?
That gives bricks applying radio after having root is pointless.
What are you trying to do?

i dont know im a noob if you dont know by know. well is there anything i can do???

Sagz326 said:
i dont know im a noob if you dont know by know. well is there anything i can do???
Click to expand...
Click to collapse
Just tell me everything you did, step by step.

ok first i put both of his zip files on my sd card then turned off my phone and turned it on with the home key, then i backed up my phone, then a factory wipe/reset, then applied the radio update, then tried to apply the other zip file but couldnt, so i rebooted my phone and now im stuck

Sagz326 said:
ok first i put both of his zip files on my sd card then turned off my phone and turned it on with the home key, then i backed up my phone, then a factory wipe/reset, then applied the radio update, then tried to apply the other zip file but couldnt, so i rebooted my phone and now im stuck
Click to expand...
Click to collapse
radio and spl?'
But you have to have a custom recovery image before you can flash either of those.

i think it was just a radio but not sure. but i followed that guys video step by step and now im in this position

yeah i have amonra

Sagz326 said:
i think it was just a radio but not sure. but i followed that guys video step by step and now im in this position
Click to expand...
Click to collapse
Ahh you might brick, you seem to have flashed the Radio made for HTC hero not G1....Notice the title: "How to get Android 2.1 on HTC Hero"
To use Hero 2.1 on G1 it shows it here @ XDA, you only needed Haykuro SPL and the 26I radio/
If rec mode is working then you arent brick or if you can get into bootloader.

how do i get in rec mode or bootloader

Hold down home when turning on the phone=recovery
Hold down camera button while powering on= bootloader
If you can't get into either one of those, likely bricked. I know with WM devices flashing a radio for another phone is one of the fastest ways to brick your phone, Android seems to be much more forgiving, so hopefully you will be lucky and if recovery and bootloader don't work, you can possibly get ADB to work.

If you don't figure out how to do this BEFORE you do it, you will likely brick your phone, if not sooner, soon enough. Doing it along with a video isn't enough to make sure you won't brick your phone.
Read through the steps of rooting, flashing a basic, stock ROM, do that a time or two, and then get into the more up-to-date stuff.
Your method of going about a new task is going to... well, it isn't going to work, unless you are really, really lucky.

Problem: Stuck at G1 Screen

I was running Super D 1.2, flashed to 1.4 earlier this week with no problems. Went to flash to 1.5.1 last night and had an issue.
When I rooted I used hardSPL and didn't touch the radio. To flash super D 1.5.1 I needed to get Haykuro's radio and Danger SPL.
I wasn't aware I needed the new radio first and that's where the problem started.
I put danger SPL and super D on my card, booted up in recovery (amon_ra's), did a nan backup, flashed danger, then tried to flash 1.5.1 and got this error:
e: can't symlink /system/xbin/bb/[
e: failure at line 59:
symlink /system/xbin/busybox SYSTEM:xbin/bb/[
Installation aborted
After I got the error, I hit reboot so I could put 2.22.19.26i radio on my phone, and bam, stuck on G1 splash screen no matter how I try to boot up.
It's my fault for not checking the radio, This is my second time flashing a new rom (I rooted my G1 a few weeks ago)
I took my sd out and put it on my comp, so I have access to my sd thru my comp. Is there anything I can put on there to try and boot up in recovery and fix this? I have a nan back up from last week and last night before I flashed anything.
thanks in advance

Like all the other post say, flash the radio before the spl. If you failed to read the instructions and can not boot into recovery or fastboot, you have a brick.

evilkorn said:
Like all the other post say, flash the radio before the spl. If you failed to read the instructions and can not boot into recovery or fastboot, you have a brick.
Click to expand...
Click to collapse
Just in time to get a nexus too. Yay, for timing!

hi,im new to this, so bear with me.if you had already updated your radio and spl before then you shouldnt do it again.i might be wrong,but once its updated you dont have to do it again.

fabman33 said:
hi,im new to this, so bear with me.if you had already updated your radio and spl before then you shouldnt do it again.i might be wrong,but once its updated you dont have to do it again.
Click to expand...
Click to collapse
No, you shouldn't have to, but did you check before (can't check now)? There have also been cases where you got a bad download or it didn't work right, this also causes bricks. And please don't be a jerk and blame haykuro for this, I know some people have

I guess I failed to follow instructions lol ...
So I can't put a previous rom or anything on my sd from my comp to try and boot into recovery?

fabman33 said:
,but once its updated you dont have to do it again.
Click to expand...
Click to collapse
http://bit.ly/5V0VMB

t0nnn said:
I guess I failed to follow instructions lol ...
So I can't put a previous rom or anything on my sd from my comp to try and boot into recovery?
Click to expand...
Click to collapse
Can you boot into recovery now?

Nah every time I try I just get stuck on the G1 screen

t0nnn said:
Nah every time I try I just get stuck on the G1 screen
Click to expand...
Click to collapse
Well, enjoy your brick. You can replace the mobo, or break into htc and take the machine they used to originally put android on it, connect it to your phone's jtag's and watch the magic. Of course the second option comes with heavy fines, lawsuits, and jail time. Or you could buy a new phone

Nice, i'm an idiot.
Can I send it to HTC to get fixed?

t0nnn said:
Nice, i'm an idiot.
Can I send it to HTC to get fixed?
Click to expand...
Click to collapse
No you can't, you broke the warranty by rooting in the first place :/
So, buy a new phone

bah! ...this sucks.
It be nice if they offered a service to fix them, for a charge of course.
Before I rooted I sent the phone to them to get some minor stuff fixed under warranty (which it was), but to be covered under warranty they said they had to make sure the damage wasn't user caused and the phone didn't have any aftermarket roms on it.
Guess i'll be shopping for a new one

t0nnn said:
bah! ...this sucks.
It be nice if they offered a service to fix them, for a charge of course.
Before I rooted I sent the phone to them to get some minor stuff fixed under warranty (which it was), but to be covered under warranty they said they had to make sure the damage wasn't user caused and the phone didn't have any aftermarket roms on it.
Guess i'll be shopping for a new one
Click to expand...
Click to collapse
No they do offer it for a charge, a $400 one

what? Do they cup the balls and give you a milkshake for that too?

t0nnn said:
what? Do they cup the balls and give you a milkshake for that too?
Click to expand...
Click to collapse
No they send you a new phone

t0nnn said:
what? Do they cup the balls and give you a milkshake for that too?
Click to expand...
Click to collapse
On special occasions they do.

So you have a bricked phone! Care to donate it to the 'i wanna play with the motherboard' charity? Lol

just a stab in the dark, can you get into recovery with the USB cable connected / or a wall charger plugged in? (Hold home and long press power)

How long should I hold it? I just tried connecting via usb and home+power for about a minute with no luck.
Should it be home+power, but only hold power for a while? And how long?

plz help - Rom install - Failure at line.. Install aborted

I rooted my G1 last night and have yet been able to load a Rom on it.
my radio is 2.22.19261
and I do not know how to check what my spl is. also when I try to install the newest spl to make sure I have it Im not sure how to install it since when I boot up pressing home and power it goes to RA-dream-v1.5.2. not sure how to do the update from here.
The 3 Roms I have tried so far are:
-FastTest2.4.1
-SuperD193-blk-WGKv3beta
-MLIGN-HeroV3.3
fasttest and superD get failure at line 59
MLIGN-Hero gets failure at line 80
So is there something I'm missing somewhere and if its the spl can someone point me in the right direction to update it??
Im still researching, but a lil help would be apprieciated and amazing

It shows the SPL version in your first screenshot. The SPL you need to load the roms you listed is in my signature.
You should be able to flash the SPL without problems because you meet the radio requirement already.

thanks.. I was just logging in to say I already got it figured out..
I thought I still had to rename the spl as update and then get the phone to boot to it wick i couldnt figure out how to do after I rooted it.
I booting it to recovery and then choose to Flash zip from sdcard.. choosing the spl I loaded on the sdcard
Works great now.. im testing out FastTest2.4.1 right now
Thanks again

Help
I have the exact problem, the pic that this person has is the same thing that shows up on my phone! but it wont let me even get on my phone if i turn it goes directly to android system recovery.. ????????

samanthamaresh said:
I have the exact problem, the pic that this person has is the same thing that shows up on my phone! but it wont let me even get on my phone if i turn it goes directly to android system recovery.. ????????
Click to expand...
Click to collapse
I'm going to be nice this time but next time make sure you read on how to root your phone and install either HardSPL or EngSPL. Do not flash Haykuro's/Death/Danger because you'll likely brick your phone (since your first post has such an obvious answer)
http://forum.xda-developers.com/showthread.php?t=442480