yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] noSuchThingAs2:
Well, I bricked my G1 today after a day of ownership. My goal was get the Rosie rom installed, so I started learning from the "informative threads" sticky. I think my problem was the original SPL I installed, but maybe someone else can shed some light on what went wrong. First I rooted my phone using the main root thread. That worked fine so it was suggested I install an updated SPL (the root thread suggests this). At this point I didn't realize that some SPLs are newer than others. So, I installed the hard SPL listed in both the root thread and the SPL thread. Then I attempted to upgrade to the rosie ROM (the newest one on the ROM page) - this failed. After searching on the error message I discovered that I'd installed an old SPL and this was the issue with that ROM (why isn't the SPL thread up to date?). So, I saw that I needed to install a new SPL, and that the new SPL required a new radio update as well. I installed the radio update and when I restarted the phone I got some strange icon of an arrow going into a chip - this is where my heart sank ;) I let that sit for awhile, then rebooted to finish the update by installing the latest SPL from google code. I installed the SPL then rebooted. Now my phone is stuck on the G1 screen. Ah well. What I did learn was that just because a thread is stickied under "informative" does not mean it's up to date. In fact, both the "how to root" and "update your spl" threads reference old software. It would be great to get these updated with a safe method to get any G1 up to date with the latest firmware. I do appreciate what you all put into this site, and the info has been great. You gotta break a few eggs... ;)
[G1 Android Development] JackD3ath:
The SPL thread is as it should be, the "new" SPL you are referring to is Haykuro's SPL, which makes your phone use the hardware more efficiently in order to install the larger roms. This is not a standard upgrade path, unless you are looking to install Hero ROMs or the other devices to G1. I am on the HardSPL not the Haykuro or "Danger" SPL.
[G1 Android Development] skweints:
Any updates? I'm anxiously awaiting to see what you come up with. :-) I'm in tears having been stuck with downgrading to my BlackBerry Pearl. LOL... and I thought that phone was the **** when I got it! Psssshhh.
[G1 Android Development] clockedtouch:
I have a G1 with broken screen that works perfectly fine if someone is looking to bring a phone back to life of just use i as is for dev or every day use

mdotcassidy@gmail for details
[G1 Android Development] skesseks:
:)

Please Keep It On Topic

:)
[G1 Android Development] naria01:
Ok you mentioned you are using cyanogens newer rom. Did you install the HTC build first? If you don't it will hang on the g1 screen. I would advise you check his wiki site, it has even more detailed instructions to this. If it still doesn't work download another rom and see if the other rom works. I usually keep every rom I download in the root of my sd card, and use install any zip from sd when in recovery. Hope this helps
[G1 Android Development] Rafi_:
Yes it definitely helped, I was tired and frustrated last night...When i woke up this morning I re-re-read the wiki. I should have done that before i posted here. I think also I read to many other "solutions" which caused me to throw in the proverbial towel prematurely. BTW Thanks for the quick response.
[G1 Android Development] lbcoder:
The SPL thread is FULLY up to date.

The newest/best SPL is the ENGINEERING SPL in that spl thread.

It is the most functional stock SPL available.

There is none better.

There are two HACKED spls... "HARDSPL", which is a modified engineering SPL that really doesn't offer ANY benefits over the engineering SPL, and the DEATHSPL, which is responsible for needlessly turning good phones into bricks.

There is NO NEED for the DEATHSPL. The ONLY thing you accomplish with it is that you risk killing your device... as you managed to accomplish (predictably). Even those ROMs that purport to require the DEATHSPL *do not* since it doesn't actually do anything except change the partition boundaries.... well how about you just MOVE SOME FILES AROUND to where they fit? The overall space remains THE SAME.
[G1 Android Development] raptoro07:
So you do not need the "death spl" to install a hero rom? I thought it was necessary.
[G1 Android Development] peshal:
This link seems to have the required document MSM7200. But in order to download it requires VIP membership which is $25 a month...

http://en.pudn.com/downloads149/doc/project/detail643560_en.html

Give it a try if u belive in something is better than nothing...

And this site seems to have lots of other important documents and files too...

I wish this is the correct file. It has been 2 weeks my g1 been bricked.

I apologize if it is the wrong file. Just tryin to help...
[G1 Android Development] chevycowboyusa:
Has anyone seen this document?

The Mobile Station Modem (MSM) MSM7200A chipset and system softwaresolution

http://www.datasheetpro.com/node/50270
[G1 Android Development] hilaireg:
Forum rules, please read!

There seems to be a significant amount of animosity of late in the Android related forums. I'm not certain as to why this is, nor do I want to hear any reason for justification; what I do know is that it is

unacceptable

.

XDA is about bringing together folks who have similar passions about mobile technology. As the forum is accessed worldwide, you will encounter all types of folks from different walks of life; some of these folks will be extremely technical, others not. In all cases, it is the responsibility of all members to remain respectful of one another. We all have different opinions, we do not all have the same level of knowledge, and some folks are looking to feel like they are learning while trying to contribute.

Show maturity and professionalism by responding with helpful and constructive information. There is absolutely no reason to respond in a rude tone or to make someone feel stupid ... it is not constructive and serves no purpose.

I would remind members that the best moderation is self-moderation.

Forum rules, please read!

http://xdaforums.com/announcement.php?f=263
[G1 Android Development] lbcoder:
Thanks boss.

Much nicer :D
[G1 Android Development] ReverseEngineered:
Cataloging what we know

Hey Binary,

I know the primary JTAG seems to be disabled and the secondary is troublesome, but could you post the pinouts for these anyway? If nothing else, it allows others (myself included) to do some experimenting with it.

Thanks.
[G1 Android Development] o7hafiz:
my fone is bricked... it frozz on "openbox and an arrow pointing at the phone" screen..

accidently i was upgrading HTC Hero Radio on my rooted g1.. =/ im trying the blue light thing.. but how do i "Put battery back in and boot into SPL" boot into spl? im new at this...

please help me....
[G1 Android Development] ReverseEngineered:
Unfortunately, the blue light thing is little more than a curiosity. It hasn't proven to provide an alternative way to flash the ROM.

If you can get into the SPL (with the power off, hold the Home key and press Power), you will be able to recover, but if not, you're as good as bricked, and so far there is no fix.
[G1 Android Development] LeonardoFloripa:
Not so fast, some news...

R3nrut got some fresh information on this issue...
[G1 Android Development] skweints:
Seems like anytime someone starts to make some progress, they fall into the black abyss. I'm beginning to doubt that a JTAG solution (or any type of solution) will be made available anytime this decade, if at all.
[G1 Android Development] stolen_pillow:
this might help

After I first started tinkering with my phone a couple of my friends wanted me to root/upgrade theirs. One worked fine (radio, hard spl) the other got bricked by the spl. He just took it to the local T-Mobile store, told them that he received an update, showed them that it wouldn't get past the G1 screen. They just gave him a new phone. No questions, no charge. Pretty sure he had insurance on it but it might be worth a try for some of you out there.
[G1 Android Development] dfw2k7:
Same for me. I bought mine off of craigslist and and when i bricked it using the haykuro spl they replaced it. (of course they dont know what happened)
[G1 Android Development] BinaryDroid:
Posted the jtag points in a new thread. aux will we posted once I take some pictures and label them be warned, their litterally impossible to get too.
[G1 Android Development] pixel21:
Question: how much did it cost you to send your G1 to HTC to fix? And how long? What's the right address or phone number to call to organise this?

-Eitan
[G1 Android Development] shaji007:
urggh i handed mine into t-mobile no insurance told them it was caused by an update which was "true" :P

and then t-mobile repair station sends it back saying its water damaged!!

how much of a BULL is that
[G1 Android Development] lbcoder:
They might be getting wise to this and just playing stupid.

Technically, they need to prove that the problem you are sending it in for is related to the water.

You could get threatening (that you will unleash some lawyers) and ultimately they would have to actually prove the problem with it, but if they go and do that, they will prove that you were trying to install unsupported SPL and you'll get hit with THEIR legal bills.

In other words... sucks to be you. You're going to have to wait for this: http://xdaforums.com/showthread.php?t=591048&page=4
[G1 Android Development] Arich0908:
I wanted to make a post regarding being stuck in the tri color screen (bootloader) while flashing Rc29.

This happen to me also .

I was stuck like chuck. Couldnt figure out why.

I then went and grabbed a friends Micro Sd card 1gb. I had a Micro Sd card that is 8gb Hc .

For some reason I wont read my Sd 8gb HC card?

I loaded Dreaimg.nhb into the 1gb card . Boom after 10 tries with the 8gb it took it right away.

I needed to flash again tried my card again same ****. The 1gb still had the files on there I needed . Took it again no problem.

I couldnt even root because it couldnt find the file. All this changed just because I switched my SD card. I know its a good card also because I just bought the thing. Maybe the phone has a problem reading files from SD HC type cards like some other machines.

good luck hope I helped some one.
[G1 Android Development] lbcoder:
Unfortunately, this is not applicable. If you were able to get to the tricolor screen, then the IPL->SPL handoff was working perfectly. In other words, it wasn't bricked.
[G1 Android Development] dwsco:
Is it possible?

This link on ebay says they can fix this issue...

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=180452322298&ssPageName=ADME:X:RTQ:US:1123

I emailed and confirmed that (they say) they can fix a device that is stuck in G1 screen, no camera+power, no home+power etc functionality.

Guy's got 426 feedback and 100% positive so not a scammer (one would assume)

I guess the question is whether it's worth $95 + shipping to get it fixed but the real point is, if it can be done by these guys there must be a solution right?

Maybe it's just mobo replacement but it's cheaper than HTC I think?
[G1 Android Development] akapoor:
History:	1 sold

That too to a person with 3 feedback.
[G1 Android Development] lbcoder:
For $95, that would definitely be a mainboard swap.

A programming solution should be more like $20.
[G1 Android Development] cybik:
Latest and weirdest brick on the front:

I was doing a "complete from-base restore" of sorts with a newly-acquired HTC Rogers Dream. Flashed AmonRa's latest for the Rogers phone. Updated the phone by Amon's recovery menu to the DRC base, then Cyanogen 4.2.13, then the EBI1 patch.

And then it flashed a RADIO. Automagically. I swear to (insert deity here) I didn't want to flash the fscker.

And now I have a brick.

After 1 day of usage on the Bell network (yes, i unlocked the little thing). One Day. Egads.

Is there any sort of medical, chirurgical, computer-based or even freakin VOODOO ressucitation method? Or should I call it quits because I put the Bell logo at boot and now I can't go to a Rogers store with a straight face?

Notes:

- No fastboot (i SO wish)

- No Recov (d'uh and ergh)

- No funny plug-usb-push-camera-and-then-put-battery-and-you-may-get-a-weird-fastboot-mode too. i wished i got that one working.

- Blue mode works... :(

ed: seems I isolated what bricked it: amonra's toolchain flashed the radio.img inside the "base system" file, thus bricking the phone. Now i am totally and thouroughly fscked.

Any idea or magic to suggest?
[G1 Android Development] nToxEk8d:
FWIW, I am in the same boat. I did exactly as you did. I have flashed it a million times without issues then... I guess I will put it aside and look for a replacement for now.
[G1 Android Development] captinamerica:
Hello,

I just read through this whole thread :) I unfortunalty just bricked a friends phone :( Flashed radio first but it was no compatable with the SPL I flashed after and now the phone is stuck at G1 screen. No recovery no nothing. She has the phone right now, but im going to work on it tomorrow. A few thoughts/ questions. Does starting the phone in safe mode do anything (Menu + Power)? If I swaped out the mothe board on the inside with a stock phone wouldn't that just bring it back to OEM? The track ball + pwoer def does something as mentioned but I have nothing so far. I'm going to instal ADB tomorow and see if that will do anything while having the phone conected to the computer. Any help would be appreciated :)
[G1 Android Development] R3nrut:
The only way to restore the original device is by pushing a binary format of the spl to the devive via jtag. As it has been discussed throughly on this thread it is near impossible to use a jtag interface on the retail boards because the primary jtag has a fuse blown to disable that path. The secondary jtag path was looked at and resolved that it is nearly impossible to hard wire the interface directly to the contact points based on where they are on the board. I supplied information on this subject at my site. To my knowledge no one found another solution. Best bet is to salvage the hardware and make some money off parts or buy a damaged device and repair it with your bricked device.
[G1 Android Development] SilentTweak:
+1, same thing happened to me... At best I can get a Blue Light and Rogers screen at the same time lol
[G1 Android Development] scholbert:
Hey R3nrut,

how are you?

Seems you stopped your experiments on JTAG...

I'm sorry to say that, but you're wrong :p

JTAG access on HTC Dream is confirmed on primary port.

http://xdaforums.com/showpost.php?p=5237673&postcount=61

Did some more investigation using the debugger and it is working very well in ARM9 mode :D

Anyway this won't help anyone right now, because the software to rewrite parts of NAND is missing.

But in theory... :rolleyes:

Best regards,

scholbert
[G1 Android Development] Electroboy:
ORT JTAG Support fully unbricking HTC Dream !

Best Regards

Oz
[G1 Android Development] Kutttt:
Thank you for being so helpful Brotha Lynch
[G1 Android Development] ThaiHeart:
Any good news on bricked?

Hi everyone, I just got my phone (G1) bricked today with my fool experimental by the death SPL. Gosh....I hope that R3nrut will find out the way to fix it. I love this phone so much and replacing the mainboard is not easy for me since I'm in Thailand where I found out it's pretty hard to find any cracked one.

Please....my hope is on you guys.

Best regards,
[G1 Android Development] M..N:
http://xdaforums.com/showthread.php?t=591048 read this
[G1 Android Development] ThaiHeart:
Thanks M..N It's very helpful to me. I hope that I will understand all and find the way to revive it.

Best regards,
[G1 Android Development] pziv2:
My G1 is not booting up. Its stuck at a black screen. I'm running stock Android 1.6 (unrooted). Please help
[G1 Android Development] HEARTBREAKER123:
I was trying to load the Cyanogen mod, when I flashed death spl before updating my radio to 2.x (It was 2.x before the RC29 downgrade, I guess the downgrade must have brought it to 1.x)

Any ideas?
[G1 Android Development] bestrafer:
you downgraded radio to 1.x... with RC29 downgrade
[G1 Android Development] hoting:
blue led @@

Hi, I also have this problem. I am not sure how to tell if the trackball is stuck. I did not push the trackball but everytime I power on my dev phone, the blue led lights up and gives me a blank screen.

How did you get your trackball to un-stuck and get the phone to work ?

Thanks in advance.
[G1 Android Development] bestrafer:
Does anyone have a Schematics Diagram for G1?

(which could be used as a guide in troubleshooting or fault finding in hardware problem Issues)

(sorry for cross-posting)
[G1 Android Development] a1t:
Brick

So I tried:

NewCupcake, original frosting and after the update, it was stuck at the 'android' bootscreen frozen.

I took the bat out and tried another proven jf1.5 build and it said that it was a "bad" update.zip.

this i have confirmed to work several times as I am always trying new builds.

I tried a couple of Hayk build and the same. So, I decided to try the DREAIMG and it says it filas at the RADIO.

Now, everytime I turn on phone (which I cant now because it for some reason drains the battery in 20 min - from full) it goes to the OG red green blue white screen - I believe it is the fastboot screen from RC29.

Please help. Any direction would be greatly appreciated.

#MORE INFO BELOW

DREA100 PVT 32B RUUNBH

HBOOT-0.95.0000

CPLD-4

RADIO-2.22.19.26I

Sep 2 2008

#The above is the red, green, blue, and white screen

Bootloader -

Recovery -

Boot -

Splash1 -

system -

Userdata -

Radio_V2 -

Update In Progress...

Then it reads:

DREAMINM.nbh - FAIL #in red

Bootloader -

Recovery -

Boot -

Splash1 -

system -

Userdata -

Radio_V2 -

Update Terminate #in red

UPDATE FAIL #in red

This used to actually tell me where it failed. Now it does not?! It fails at the Radio_V2
[G1 Android Development] alapapa:
I would try applying the HardSPL since it sounds like you have the original SPL -- then hopefully you ought to be able to apply the RC29

let us know if it works

EDIT: hrm...it sounds like your recovery image might be kaput too :-/
[G1 Android Development] theslam08:
People need to be careful, it seems like more and more bricks are showing up all of a sudden....not good...

This is a DEVELOPERS FORUM!!!! Things are in development, so people need to be reading and be cautious a whole lot more than an official forum...ayayaya
[G1 Android Development] LucidREM:
so if you can get to the colored screen it is not "bricked" .. as stated by others i believe .. just flash the nbh file .. make sure always verify the MD5 etc .. some files don't download completely and you must be sure the file is complete and without errors before trying to flash to the phone
[G1 Android Development] a1t:
Tech think tank (for possible solutions)

To be quite frank, I thought this was a forum for those that may have made a mistake and are looking for those that are willing to help, not to be told to be careful. It seems like some are very kind in replying and offering help while others are just creating wasted space.

If stuff happens, you can either help or not. If not, then please, leave it alone.
[G1 Android Development] DionS:
Tried the goldcard idea, didn't work out (It's for the stuck at splash screen problem, right?)

You meant the goldcard as in a goldcard you create over here?
[G1 Android Development] sir*mez:
yea i tried that yesterday and it didnt work for me.
[G1 Android Development] SolemnWishing:
received email back from HTC, they refused to provide any information whatsoever.
[G1 Android Development] LucidREM:
G1 Brick

G1 Brick

ok .. well i thought it was funny
[G1 Android Development] andonnguyen:
Your nbh file is named incorrectly. It should be DREAIMG.nbh and not DREAMINM.nbh Try renaming and flashing again at the bootscreen. Also, have you tried booting into SAFE MODE? You can do so by simply turning off the phone, hold down MENU and turn the phone back on. Keep on holding MENU until the phone fully boots up. You will see the words SAFE MODE in the bottom left corner of your screen.
[G1 Android Development] jjcd51590:
just an idea

i remeber someone a while back discovered if you hold power and tracball a blue light comes on did anyone find out what this was for? maybe you can adb idk just a thought
[G1 Android Development] Valicore:
I see haykuro twitted to try holding volume-down and power at the same time and report back what happens. Maybeeee?
[G1 Android Development] a1t:
Follow up to come

Sorry about that. It does reaf DREAIMG.nbh. When I turn on the phone, it will load to the og spl. I tried holding menu but even after a long hold (1 minute) it detects the nbh and wait to either start the update or cancel the update image.

As it used to show it fialing at the radio, and I have confirmed the integrity of the .nbh, I will try to load the SPL and report back. I will follow up tomorrow.

I hope my troubleshooting helps someone else.

I dont have a card reader so I have to wait to get to work tomorrow to try.

Thanks all!
[G1 Android Development] kylebrodeur:
what does this do actually?
[G1 Android Development] sir*mez:
well i got my replacement phone from the one that got bricked. I want to try the new H-Special SPL again but im more nerveous now that i got a brick before. I want to do it a third time for trial and error.
[G1 Android Development] jjcd51590:
ummm

im not sure but this is for brainstorming, right, but i cant remember what its for just that i proved that there is a blue led in there maybe its a loader of some sort no idea but its gotta be there for a reason
[G1 Android Development] LucidREM:
try the HardSPL?

$su

#cd /sdcard

#mv update.zip update_old.zip

#wget http://files.lucidrem.us/jf/ROOT/SPL_HARD/update.zip

this might work for you
[G1 Android Development] theslam08:
lol I would leave it alone dude, you got lucky and got another phone. Take the worst possibility and theoretically put it into play: It happens again. What would you do? There is no fix yet.

Its only for space, nothing else. If you are really edgy and really want to try it again anyway, check the board type, DVT or PVT, it seems to make a difference. Though I would still leave it alone, do the other hacks, just nothing to do with "not at tested spl as the main ones" SPL. I would just flash the stickied post "Engineering SPL". That will do everything you want, just normal space. And make sure to eject the SD card after its transfered, do not just unplug it.
[G1 Android Development] sir*mez:
lol... i already did everything else to it. i already put hardSPL on it tho. im still speculating whether to do it or not. btw its a pvt board.
[G1 Android Development] crazythunder:
i'd do it,lol. and you know you will. we're obsessed with stuff like this. gotta have it just right or we go nuts. plus, apparently you'll need it for the hero rom if we get it.
[G1 Android Development] crazythunder:
you live on the edge. as we all do.:D
[G1 Android Development] theslam08:
Glad you can finally move on :).

It really must be the board type. He should put that in his topic so people can know prior.

Congrats, now to find a fix for the others...hmmm

I wonder if there is a way to debug exactly what is happening when the power button is pushed, if somehow that information could be used to reverse something or change something while its booting. ...thats painful, this is not a simple problems, like others have stated, its like the bios on a computer has been fried with the wrong bios, now the mobo is junk. Err...
[G1 Android Development] SolemnWishing:
I would just like to add, I checked my phone, I am also a PVT, and I was able to flash the SPL successfully. I think we are on to something here.
[G1 Android Development] crazythunder:
with a pc bios, at least you can hotflash it if you have a spare\equal chip handy. this is much harder to fix apparently. ps...please send me all your "junk" mobo's! jk