Database Develop

Problem just arrived

I was trying to load up my gf's G1 and I had a cyans newest rom and pretty much all was working good. Now my friend decided to try the boot screen flasher to load a custom boot image and well it was not working so he said that it was the SPL and I told him that not to worry about it...But he did it anyway and now when the phone loads it stays on the G1 screen. I tried to load into recovery (home+power) to see if I could nandroid but no dice. Any Ideas...I would like this to work by time she gets home as I am creating a playboy theme for her phone.
P.S. I decided to let my friend know not to touch my phones by a nice punch in the arm
P.P.S. I know I should search for this but I am time crunching thanks to my friend and need to get this working again for her ASAP

I would give him a little more than a punch.... if he flashed the SPL
and you cant get to the SPL (Cam+Power) or recovery (Home+Power)
then your phone is bricked....
just so you know... the boot screen flasher has two options..one for the standard/engineering/hardspl and another for the haykuro SPL

Yeah When I do camera power I still get the G1 screen

Sorry but this is a brick. Not fixable.
Try not to actually kill your friend, but he definitely deserves a serious beating.
There is one thing that's worked on a few magics/sapphires, but I don't think anyone's had it work on a g1.. you might as well give it a try since it's literally your only shot: You need to have fastboot drivers already installed and working on your pc and a copy of the engineering or hardspl.. plug your phone in by usb but don't switch it on and execute this command:
Code:
fastboot flash hboot hboot.img
You should get the message "Waiting for device...", now hold [camera] power the phone on and hope. If it doesnt work, try pulling and reinserting the battery a few times. The idea is to get fastboot to recognise the phone before it trips up and start the flash, but as I said I don't know if this has ever worked on a g1. It has been reported that this is more likely to work with linux than windows as it reacts to usb devices much more quickly.

goldenarmZ said:
Sorry but this is a brick. Not fixable.
Try not to actually kill your friend, but he definitely deserves a serious beating.
There is one thing that's worked on a few magics/sapphires, but I don't think anyone's had it work on a g1.. you might as well give it a try since it's literally your only shot: You need to have fastboot drivers already installed and working on your pc and a copy of the haykuro spl.. plug your phone in by usb but don't switch it on and execute this command:
Code:
fastboot flash hboot hboot.img
You should get the message "Waiting for device...", now hold [camera] power the phone on and hope. If it doesnt work, try pulling and reinserting the battery a few times. The idea is to get fastboot to recognise the phone before it trips up and start the flash, but as I said I don't know if this has ever worked on a g1. It has been reported that this is more likely to work with linux than windows as it reacts to usb devices much more quickly.
Click to expand...
Click to collapse
fastboot only works in the spl though. the radio never calls the spl if the radios outdated.
also, why would you want to send haykuros spl back on the phone, when thats what caused it to brick in the first place.
can you link me to where the magic people got it to work? because i doubt their brick is the same as this

B-man007 said:
fastboot only works in the spl though. the radio never calls the spl if the radios outdated.
also, why would you want to send haykuros spl back on the phone, when thats what caused it to brick in the first place.
can you link me to where the magic people got it to work? because i doubt their brick is the same as this
Click to expand...
Click to collapse
to the first part of your statement: thats our best guess but noone REALLY knows, so if you dont want off the wall, maybe fix your phone solutions, then go else where
and i do agree that using HARDSPL versus haykuro would prolly be better idea, but its worth a shot nonetheless, depends all on where the fastboot code exisits and where exactly the phones hang, if you have some specific details that the rest of us are missing then do SHARE
and from what ive heard you'll need to be running linux for the reasons above (windows being slow as balls to do anything, and "security" {hostility} protocols applied to the usb bus)

B-man007 said:
fastboot only works in the spl though. the radio never calls the spl if the radios outdated.
also, why would you want to send haykuros spl back on the phone, when thats what caused it to brick in the first place.
can you link me to where the magic people got it to work? because i doubt their brick is the same as this
Click to expand...
Click to collapse
That's what I thought til I saw this thread too, but the magics were spl bricks or I wouldn't have even posted it You're right tho, I meant to recommend hardspl, not haykuro's.. slip of the fingers. I've edited the post.
I'll try to find the magic thread again.. I can't quite remember where it was though..

ESKIMOn00b said:
to the first part of your statement: thats our best guess but noone REALLY knows, so if you dont want off the wall, maybe fix your phone solutions, then go else where
and i do agree that using HARDSPL versus haykuro would prolly be better idea, but its worth a shot nonetheless, depends all on where the fastboot code exisits and where exactly the phones hang, if you have some specific details that the rest of us are missing then do SHARE
and from what ive heard you'll need to be running linux for the reasons above (windows being slow as balls to do anything, and "security" {hostility} protocols applied to the usb bus)
Click to expand...
Click to collapse
what do you mean by no one already knows? We do know. i dont think youve been following xda very closely.
read the the threads that relate to the spl because all that info is already shared. Heres the summary
IPL>SPL>Android
when the link from IPL>SPL is broken.... there is nothing
Fastboot is on the SPL.
Its not "the rest of us" that don't know this....its just you
@Golden
Im surprised that hasnt been looked at yet. However..the spl bricks are probably very different from the ones on the G1
reason being is that Magic users are using Magic radios and Magic SPLs
These G1 bricks are from using G1 Radio and ported Magic SPL's
Technically, any magic radio should be compatible any magic spl
their bricks would easier to fix as the proper software is probably still on there while g1 may or may not recognize the software such as the magic spl

Somebody please help me with fastboot

I seem to be getting no where and am reaching out for a little help. I am using XP system and trying to fastboot my g1 and mytouch 3g. I am running Cyan 4.2.4, and I am trying to figure out how yo get fastboot working. I found the guide to help, but the new SDK doesnt come with the usb drivers.
I am trying to flash custom splash screens.
How can I get my MT3g and G1 fastboot ready?

spazoid said:
I seem to be getting no where and am reaching out for a little help. I am using XP system and trying to fastboot my g1 and mytouch 3g. I am running Cyan 4.2.4, and I am trying to figure out how yo get fastboot working. I found the guide to help, but the new SDK doesnt come with the usb drivers.
I am trying to flash custom splash screens.
How can I get my MT3g and G1 fastboot ready?
Click to expand...
Click to collapse
Well first of all you need an SPL which is fastboot enabled, be it HardSPL, Engeneering, or 1.33.2005 (AKA Haykuro, Danger, blah blah).
If you're having trouble with your current drivers try these.

How do I go aboput getting those installed?
And if I change the spl is there a way to revert back to stock? ie 1.33.0006

spazoid said:
How do I go aboput getting those installed?
And if I change the spl is there a way to revert back to stock? ie 1.33.0006
Click to expand...
Click to collapse
Drivers or SPLs?
SPL: It's just a regular update that you flash. For the G1 I reccomend 1.33.2005, just make sure you have the .26i radio first. If you don't it will brick, also boot in to reocvery to check you have a PVT board first.
Drivers: Once you get the phone in to fastboot via the SPL, windows should tell you that new hardware has been connected, from there choose to install from a certain location and select the drivers I linked to earlier.

For the MT3G, look for AmonRA's posting of which SPL's to use in the sapphire section.

I still don't get it though....can u help me

need help fellas... i made a mistake n cant fix it?

i was rooting a friends g1, i missed a step n tried flashing a rom without having the danger spl installed first, i cant get into my spl menu by holding camera and power nor can i get into my recovery nor can i get into adb... my phone turns on and stays at the g1 logo... any advice?

bricked.. look in the development section for un-bricking guides... although it'll cost some money i think.. i'll look for one myself and post back with a link
edit: http://forum.xda-developers.com/showthread.php?t=576628&highlight=brick
or
http://forum.xda-developers.com/showthread.php?t=591048
maybe those could help... Good luck!

madunix said:
i was rooting a friends g1, i missed a step n tried flashing a rom without having the danger spl installed first, i cant get into my spl menu by holding camera and power nor can i get into my recovery nor can i get into adb... my phone turns on and stays at the g1 logo... any advice?
Click to expand...
Click to collapse
that is why i dont screw around with other peoples phones LOL

i just checked my sdcard that was in the phone, the update.zip file is the danger spl. im guessing i flashed that? but i dont get why that would brick anything.. the phone was rooted... but i had the factory recovery where u see that pic in the middle, i hit alt w? or alt s i forget what the instructions were i was following. soo its a brick huh? no way of getting through this one?

madunix said:
i just checked my sdcard that was in the phone, the update.zip file is the danger spl. im guessing i flashed that? but i dont get why that would brick anything.. the phone was rooted... but i had the factory recovery where u see that pic in the middle, i hit alt w? or alt s i forget what the instructions were i was following. soo its a brick huh? no way of getting through this one?
Click to expand...
Click to collapse
Just because the phone is rooted doesn't mean it is magical and can't be bricked. You have to have the latest radio before you can flash the danger SPL. Depending on which method you used(likely RC29 method) that radio would not be anywhere close to what is needed. And, yes, once you flash the danger SPL without the newest radio, you have a brick and no way getting back from it.
Hopefully your friend is understanding and it isn't a major disaster getting a replacement G1 for him.

Flash Danger SPL without Latest Radio = Bricked.
I hope that your friend can get a replacement without much complications, because that one is screwed.

You could give him your phone...

the phone already had the newest radio installed... it was a brand new G1.. =X did i still have to flash it with the radio on this forums?

madunix said:
the phone already had the newest radio installed... it was a brand new G1.. =X did i still have to flash it with the radio on this forums?
Click to expand...
Click to collapse
Most likely yes usually when something is brand new it was manufactured months ago. Its unlikely that it included the proper radio. try blaming your friend lol good luck!

madunix said:
the phone already had the newest radio installed... it was a brand new G1.. =X did i still have to flash it with the radio on this forums?
Click to expand...
Click to collapse
Brand new or not, most every root method has you downgrade to RC29, which takes you back to a radio that is about a year old now.

G1 stuck at G1 screen

Started to root the phone went back to 1.5, worked fine, applied FlashRec.apk and Amon Ra’s Recovery Image installed all that correctly worked fine. Went to install a new radio and spl and applied spl and when i go to start the phone it gets stuck at the G1 boot screen. Tried to book into recovery mode nothing happens , tried to hard & soft reset nothing happens. Phone just stays stuck at the G1 left it on for an hour and still nothing. Please help in any way or ask for more info if need.
Thanks in advance.

if you flashed the danger spl before flashing the new radio, your phone got permanent brick and cannot be solved without JTAG or changing the motherboard.

OK- I have the same problem, except I flashed the wrong radio.
(I thought I needed to update it for a different ROM, but.)
No fastboot, no recovery-- If I hold down the trackball, the screen wont come on, but the blue LED does. Is that useful to me at all??
Can JTAG help me? or is there another way?
I was reading about mtty-- but i'm not sure if that'll work for my G1.
Anything to unbrick this--- I really need my phone for finals week which started to-day.

JTAG is your only option.

techn0crat said:
Can JTAG help me?
Click to expand...
Click to collapse
Yes
techn0crat said:
or is there another way?
Click to expand...
Click to collapse
No.. at least none known yet
techn0crat said:
I was reading about mtty-- but i'm not sure if that'll work for my G1.
Click to expand...
Click to collapse
MTTY is just a program to talk to the serial port; it is actually part of the JTAG solution as well .. but as mentioned it will not help you at this point in time.
techn0crat said:
Anything to unbrick this--- I really need my phone for finals week which started to-day.
Click to expand...
Click to collapse
JTAG.. but unless you live near me or one of the very very few others who are set up for jtag hacks.. and that person is confident enough not to make the main board of the phone one big solder blob [I am but I'm not sure if some of the others I've heard poke JTAG are as confident].. it will take you a large chunk of time to learn what is needed to make it work.. or longer than the finals in the mail.
Thus I recommend.. get a cheap phone at the stand at the mall.. and pass your finals before worrying about the brick.
Since everyone who has caused a brick has either (1) not properly followed the directions and warnings.. or (2) did something in haste missing an important step; it will be no good to race it together during finals.

this dream was sent to my friend as a replacement
never used
he gave it to me sayingit wont boot
it gets into fastboot
it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
so i formatted his sdcard, got the DREAIMG.nbh put it on his sdcard, entered into fastboot, and it ran the install (rainbow screen) nothing was happening from there before i copied the DREAIMG.nbh to it, so at least this installed successfully)
then i rebooted (call-menu-power at same time) and still stuck at G1 screen after twenty minutes...whats happening here, anybody?

tnpapadakos said:
then i rebooted (call-menu-power at same time) and still stuck at G1 screen after twenty minutes...whats happening here, anybody?
Click to expand...
Click to collapse
Odd, the nbh files usually flash a full system.. thus while they might leave you with a rom you don't wish to have they usually will boot afterwards. You did let it fully flash all the partitions correct?
What nbh did you find/flash?
And. Can you still enter the spl or recovery.

ezterry said:
Odd, the nbh files usually flash a full system.. thus while they might leave you with a rom you don't wish to have they usually will boot afterwards. You did let it fully flash all the partitions correct?
What nbh did you find/flash?
And. Can you still enter the spl or recovery.
Click to expand...
Click to collapse
RC29 from the cm wiki, flashed successfully, nothing but fastboot screen, no boot, no recovery boot
weird

tnpapadakos said:
RC29 from the cm wiki, flashed successfully, nothing but fastboot screen, no boot, no recovery boot
weird
Click to expand...
Click to collapse
lol, wtf? wait... don't some phones need a goldcard for this?

r3s-rt said:
lol, wtf? wait... don't some phones need a goldcard for this?
Click to expand...
Click to collapse
yeah i dont know, all i know is i can ONLY getinto the bootloader, which is the ORIGINAL bootloader (0.95.0000)
what can i do with this thing?
what do i flash to it (cause it aint the RC29 DREAIMG.nbh)?
i refuse to lose

well only bootloader means nothing. you cold be getting a bad .nbh and the recovery partition could have something nasty on it. both of those not working doesn't automatically make it a brick. a working bootloader says everything is ok.
set up fastboot and fastboot a new recovery image.
then see if your recovery works. next time i don't respond, feel free to pm me again, lol. i really have a hard time keeping up with where i post.
of course: you can also fastboot a new spl:
http://code.google.com/p/android-roms/downloads/list?q=label:SPL
I recommend:
EngBootloader_v2_NoSigCheck.zip
That way you don't have to mess with that nasty danger spl and then you actually will be bricked.

[Q] Its bricked right?

hey.
Im almost sure i just bricked my g1, just need to be sure.
I was running Death SPL and the last official radio, and had gsm\umts network connection problems.
Decided to upgrade the radio to the last one that came out recently, i did, the problem seem to be better but it got worse in time.
downgraded the radio, and tried around 15 different roms, all tries with the same outcome.
so after a lot of trial and error, i decided to get back to one the the first radios available, but i was afraid it would brick my phone so i read carefully about it
I had a realy hard time finding something but i everntually came across a couple threads that stated that it was ok to flash any radio, as long as the SPL was flashed first...
after reading that i downloaded a 1xxx radio and flashed via recovery...
result: stuck in the G1 screen...
My question: phone in the crapper right?
thanks for reading guys

mordockcs said:
i everntually came across a couple threads that stated that it was ok to flash any radio, as long as the SPL was flashed first...
Click to expand...
Click to collapse
No, what they said is that it is OK to flash anything as long as you use FASTBOOT INSTEAD OF RECOVERY, and that FULL FASTBOOT (with this ability) depended on having a 1.33.2xxx SPL.
With an SPL and RADIO that are incompatible with each other, it is impossible to successfully boot the kernel. Following a flash-hboot or flash-radio, the system is set (via writing the command field in the MISC partition) to boot-recovery. When in boot-recovery, the phone IGNORES all user inputs. The incompatible radio/spl fails to boot-recovery, and you're bricked.
USING FASTBOOT INSTEAD prevents the misc partition from being set to boot-recovery by writing the SPL or RADIO directly. As a result, when you reboot, though it still won't be able to boot a kernel, IT WILL RESPOND TO USER INPUTS and bring you into FASTBOOT mode... from where it is possible to, again, flash radio or spl.
Your failure is a result of failure to read properly.
SPL/radio compatibility:
0.95.xxxx, 1.33.x003: compatible with 1.x or 2.x radios.
1.33.xxxx (except 1.33.x003): compatible with 2.x or 3.x radios.
No exceptions.
I always suggest using the 1.33.2003 SPL since DREAM should always use either a 1.x or 2.x radio (except robbers in canada, because they are bastards, but you can load those with a 2.x radio just fine). 1.33.2003 is the strongest engineering SPL available, and fully compatible with the proper radios. There is NO ADVANTAGE to any other SPL -- no, you don't need to change your SPL to reallocate storage space.... in fact, limiting yourself to SPL changes to do this will tend to waste a lot more space (15 MB more available than 1.33.2005 gives you).

lbcoder said:
Your failure is a result of failure to read properly.
Click to expand...
Click to collapse
no its not...im pretty sure about what i read...if i stumble on the thread again ill PM you to prove it.
i already have a touch HD on the way so no harm done, i wish this was all the harm in our world...
but anyway now that its dead...lets fix it!
is there a way around it? i hear about jtaging a lot but i have never seen a tutorial on the web...
any insight on that would be delightful...seriously
but hey lbcoder thanks for enlightening me i appreciate it, i really do...thanks man