yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] micahmills:
I KNOW HOW TO UNBRICK YOUR PHONES!!!!!!!!!

Lol ... so just like everyone else on this thread... I tried to go to the 1.5 rom and didn't update from 29 to 33 so my phone bricked and got stuck on the t-mobile G1 screen..... so today i went to the t-mobile store in the mall and i said to the lady... "can you help me? when i try to turn my phone on it just does this... (showed her how it is stuck on g1 screen).." she says "well lets see what we can do." (she calls tech support and they try to walk her through doing a factory reset) when it doesn't work she asks (repeating from the tech lady on the other end) "did you root your phone?" and then I gave her a confused look like she just said something vulgar. (laughs inside) she then tells the guy "he says no." Then she hands me the phone so the tech lady can go about mailing me a new phone no questions asked and free of charge. Except for the 19$ for 3 day shipping. :) Its that simple guys!!!!!!

Peter from family guy... "Just lie to her, It's ok to lie to women, they're not people like us!" :D
[G1 Android Development] tanksta:
the motherboard swap worked.. it turns out i didn't wait long enough for the phone to boot so it seemed like it was bricked but it booted after a little while and my g1 is out of its coma.

anyone here need a bricked mobo to help with finding a solution?
[G1 Android Development] R3nrut:
Yeah all you have to do is use an exacto-knife on the void seal, just carefully slide the razor under the sticker and presto your warranty is most likely still valid. :)
[G1 Android Development] stuff:
Yeah and if you get unlucky, they will determine it has been rooted, and they will charge you a fee for the new phone.
[G1 Android Development] Skuggi:
just a heads up. I thought my phone got bricked last night. I've lost ADB to my phone some how so I started reflashing, going from a nandroid backup everything i could think of.

Then the phone started hanging on the G1 screen after a flash, literally from 11:30pm to 12:45am when I went to sleep. I just let it be figuring it could be bricked and I would deal with it in the morning. I woke up this morning and the thing booted in finally and is now working just fine.

Just thought to check the log. Latest log activity started around 3am and ended at 5am.

Not sure if this will help anyone or anything. But try just leaving it on and plugged in.
[G1 Android Development] scholbert:
EDIT:

O.K. i see, my post seemed a bit to humorous.

I decided to edit it and delete some lines of it, to prevent a start up of another discussion about brick or no brick or other stupid things.

Anyway some parts should be taken for serious:

The discussion about bricks will help to figure out what a true brick is, but won't lead to any solution, i suppose.

The following "solutions" won't help to find a practicable way to unbrick the G1:

- Hey, i unbricked my device by using the service of the manufacturer.

- I unbricked mine by swapping the mainboard.

- You won't believe it, but i unbricked my phone with buying a new one :rolleyes:

scholbert
[G1 Android Development] Fallen Spartan:
MOD EDIT

ok guys, lets leave the childish behaviour in the playground and get back on topic. Any further childish behaviour, insults etc will result in me closing this thread
[G1 Android Development] Dave RL:
I'm assuming that adb is not working on these G1's?

I did a quick test on my G1 and at the latter end of the T-mobile boot screen you can run adb.

-I guess if fastboot doesn't work then adb won't
[G1 Android Development] ESKIMOn00b:
if im not mistaken you can only adb from splash2 forward, originally the g1 comes with nothing in splash2 but you know what im talking about if you flashed your own boot imgs, i cant adb from splash1 loop, but i have before from splash2 (on old spl since new one does not have splash2 only splash1) so my guess is that you wouldnt be able to adb on the new spl till you hit where splash2 would normally come in the boot process
[G1 Android Development] SolemnWishing:
ADB will not work, as you said, it has to be at splash2. One problem, the new 1.5 firmwares completely wipe out the splash2 partition, splash2 no longer exists.
[G1 Android Development] theslam08:
Yeh, I noticed the same (figured I would check anyway for curiosity). It does work close to the end of that first splash screen (3-4 seconds before it changes to the android screen).

I believe not everyones phones doesnt have a screen...I thought I read people just never got PASSED the g1 screen. Maybe after waiting 1-2 minutes on that screen, the adb might work.

There isnt enough 'trial and error' support for this phone yet as like other phones that are older...like older phones you could do test pins, shorting them forcing the bootloader up, but thats all untested waters which sucks, but this is how everything starts, problems arise and people figure out solutions. I wouldnt give up hope yet, almost always there are ways to bring back to life, just need to know exactly what...
[G1 Android Development] SolemnWishing:
I think we need to find out how these firmwares are installed onto these phones in the first place, from the moment they were created. I assume the G1 does not support a boot-from-SD option?
[G1 Android Development] sir*mez:
i tried to use the goldcard method. But in order to create a goldcard it needs the phone to go into fastboot, which it cant.
[G1 Android Development] SolemnWishing:
No, that is not what I mean. Though probably unlikely, I mean like booting up your computer directly from a CD. Its just, a computer has the BIOS built in, and if you mess up the BIOS (which is like what we have done on these G1s) then you are well... you are screwed. However, how do you get this BIOS or SPL on the phone in the FIRST place, I mean when the phone is first manufactured. Do they somehow burn the image in place, or what?
[G1 Android Development] Dave RL:
I was doing some digging and found this from the early discussions between JF and others back in November:

Is this the case that it boots the radio bootloader first? if so this might be another in-road (or deadend)
[G1 Android Development] SolemnWishing:
It doesn't boot anything... just hangs on the Tmobile screen. Holding the camera button, etc or any other procedures will not work.

Anyhow, I just dropped HTC a support email concerning this, I will see what they have to say.
[G1 Android Development] ivanmmj:
Oh, you can't even CREATE the goldcard. I thought you could (using a Windows Mobile phone) but couldn't get the G1 to use the Goldcard.

Does anyone with a bricked G1 have both their G1 and a Windows Mobile phone?
[G1 Android Development] ESKIMOn00b:
he missspoke (mistyped) to get the phone to USE the gold card the phone has to be in FASTBOOT
[G1 Android Development] gochiefs:
french rru

Quite a few threads back someone posted a link to the french rru (ruu?) Update that u run from windows. Probably wont work but worth a shot
[G1 Android Development] Dave RL:
Bootloader with the back button instead of camera?
[G1 Android Development] djdeviance:
While holding back and power would be a plausible solution it should still bring forth the same outcome of holding the cam + power correct? If one method of booting is the same as the other you should come to the same conclusion. If only there was a way to reflash the old engineering SPL through the p/c or possibly a hardboot from SD like I've done on my T-Mobile Wing.
[G1 Android Development] im.l0ltn:
Just a note or reminder, but remember to update your adb driver after installing the new SPL. It might be out of date. Your computer won't be able to read your phone for adb or fastboot if the driver is out of date.
[G1 Android Development] djdeviance:
Word. Good call. Make sure drivers are updated as stated in other threads.
[G1 Android Development] Dave RL:
djdeviance, yea, you are probably right and I thought about this before posting and fully expected to see the same result as the camera button. I have seen stranger things work before though ;)

The google groups discussion (http://groups.google.com/group/android-platform/browse_thread/thread/f03730e25cc3fe55?fwc=1&pli=1) also has this:
[G1 Android Development] shaneaus:
I doesn't sound like this will be of any help for the specific issues that ya'll are trying to figure out. But, just in case....

If you installed the new SPL put out by Haykuro he put out an update on his Twitter with the following about 3 hrs ago:

"anyone with a 'bricked' device (with new SPL): press VOLUME DOWN+POWER... report back please"

Seems that the newer SPL has some additional key press functions. I know this won't help resolve the core issue of being able to install bootloader from the beginning. But, maybe it will help troubleshoot some of the other issues?

Also, you might contact Haykuro with a PM and see if he knows anyone that might have some insight. After all he is getting the leaked ROMs from somewhere!

"The idea of selecting VOL DWN and PWR at the same time comes from other HTC devices which use this to get to the boot loader screen. Most common on devices with Windows Mobile. It has been tried and has yielded no results. Thanks for the info though."

Sorry, it didn't yield anything new. I thought I read this post all the way through. Sorry, if I missed that it had already been tried. Best luck and I'm very interested in what ya'll find out!
[G1 Android Development] d474rpr:
The idea of selecting VOL DWN and PWR at the same time comes from other HTC devices which use this to get to the boot loader screen. Most common on devices with Windows Mobile. It has been tried and has yielded no results. Thanks for the info though.
[G1 Android Development] d474rpr:
I have access to whatever Windows Mobile device you can think of... but I was able to make the goldcard using ubuntu on my netbook... so yea... ???
[G1 Android Development] tabasco122:
im kind of disappointed, i figured there would be a resolution to this by now. guess ill have to just get a new phone from tmo :-(
[G1 Android Development] youneek:
Did you "brick" your phone and now it's stuck on the g1 logo? Read this: http://xdaforums.com/showthread.php?t=548759
[G1 Android Development] shaji007:
anyone got a solution to bricks yet?
[G1 Android Development] miketaylor00:
Yes. Flash the latest radio BEFORE you flash the SPL.
[G1 Android Development] lbcoder:
Now there's someone who doesn't read the question he's answering.

The question was regarding returning an ALREADY-BRICKED device to working status, NOT in preventing a working device from becoming bricked.
[G1 Android Development] Geniusdog254:
And theres someone who obviously doesn't understand a sarcastic comment in response to someone who obviously hasn't read the thread at all and just popped in and asked a stupid question expecting a normal answer :eek: :rolleyes:
[G1 Android Development] clefky10:
haha i agree
[G1 Android Development] G_won:
Well i screwed up on a G1 but explained to the good folks in T-Mobile that my phone "just suddenly screwed up" but of course I arfed up on the SPL install. Actually I made sure to do the Radio first and foremost but afterwards I tried doing the ROM before the SPL and was getting a "Error on line 58" or something to that effect, kept getting error even when I installed the SPL and soon ran into the white font "T-Mobile G1" screen of death.

I'm thinking it was that and/OR the fact that i probably didn't have a PVT board. So while I'm contemplating on trying this again with replacement G1 by my side I just figured I throw in my two cents and suggest that for all builds that requires the SPL & ROM to PLEASE specify how risky they are especially when one doesn't have a PVT board e.g. MVT board G1s shouldn't be surprised @ unrecoverable bricks
[G1 Android Development] lbcoder:
Text doesn't transmit sarcasm.

And btw: if it was sarcasm, then he was just being an a$$hole, and for that, there is no excuse.
[G1 Android Development] DirectMatrix:
Clearly some of the previous posters haven't been reading up on their "coding for forums". There are specific tags for specific responses.

Sarcasm is fairly self explanatory, to convey sarcasm simply place sarcastic text within the proper tags such as:

[SARCASM] clearly you didn't read the rules :) [/SARCASM]

:D

Then there is my personal favorite which I actually think I may have pioneered. The rant tag

[RANT] I am so tired of people not reading the tutorials![/RANT]
[G1 Android Development] cthuga:
TMO 12 month warranty

[update: I see someone already posted this. sorry for the duplication]

This information would've helped me when I bricked my G1 and read this thread - though I know its not a technical solution it might help others.

I brought my bricked G1 to TMO Store and played dumb while the sales person called TMO tech support. After they "of course" were unable to fix it with the "master" reset, they gave me a new (refurbished?) G1, which I updated proper that evening. I was ecstatic that they replaced it using the 12 month warranty.

"Phones are generally considered to be defective and covered under warranty if the phone has stopped properly functioning due to no fault of the user. For example, a software malfunction would typically be considered a defect of the phone."

So as long as your G1 is still in good condition, TMO may replace it since there is no way for them to tell if your G1 was bricked during the latest OTA update.
[G1 Android Development] b_ron_:
Unbricked my phone (from hard brick) and here's how

Unbrick Trick:

My case may be unique, but I hope it helps someone. See background below. I believe I read in one of the "bricked" threads linked in the thread "***Informative Links***..." [Thanks, alapapa] that switching from cupcake builds to hero builds can cause bricks due to something being added to the swap file or sdcard. I swapped out my phone's 8gb sdcard with a 2 gb sdcard from my canon camera, and BINGO, I had access to recovery screen [Thanks, Cyanogen and JF]. I plan to wipe 8gb sdcard and partition again and stick with either the hero build or the cupcake build.

Background:

Rooted phone. No problems.

Flashed radio (2.22.19.26I). No problem.

Flashed SPL (1.33.2005). No problem. [Thanks, Haykuro]

Flashed CyanogenMod (v3.6.8.1). No problem. [Thanks, Cyanogen]

Partitioned sdcard. No problem. [Thanks, 51dusty]

Wiped. No problems.

Flashed Drizzy Drake Rogers' Personal V3. No problem. [Thanks, Drizzy]

Wiped. No problems.

Flashed back to CyanogenMod (v3.6.8.1).

Upgraded to CyanogenMod (v4.0.2).

Moved zip files of v3.6.8.1, Personal V3, v4.0.2 to folder named "zips" on my sdcard to switch between the three builds.

Toggled with wifi settings while in v4.0.2...

...Hard BRICK.

-no LEDs

-no response from camera+power, menu+power, home+power, (-)volume+power. nothing.

-no response after taking out sdcard, simcard, battery or any combination of the three.

-no response after replacing sdcard with a sdcard from another non-g1 phone (although I did get to recovery screen when I used a sdcard from a camera).
[G1 Android Development] kiiiiiid:
Is there finally a solution for bricked by SPL?

I bricked my G1 by updating the SPL before Radio.

I haven't access to t-mobile to change it with the new one.

Is there a real solution to unbrick it?
[G1 Android Development] crpercodani:
Sorry to say but no your are screwed, I hate to sound mean but you really should of made sure you had the correct radio first. Only thing, and I have no idea if they will do this but try to call HTC or contact them and see if they offer any kind of warranty replacement since the phone is less then a year old. Did you buy it from ebay or something or did you purchase it from your carrier? If you did the second then you might be able to have them replace it.
[G1 Android Development] crpercodani:
Then you didn't have a bricked G1, just a malfunctioning SD card. The only way to truly brick the G1 itself is to update the SPL before radio OR using a radio meant for another device.
[G1 Android Development] b_ron_:
Well, if it wasn't hard bricked then it had all the symptoms (and agonies) of being hard bricked--my G1 would not turn on at all. No responses from any input.

Nonetheless, I would have to agree that what I did would definitely

not

work for someone who flashed the SPL before the radio OR flashed the wrong radio.
[G1 Android Development] crpercodani:
-no response after replacing sdcard with a sdcard from another non-g1 phone (although I did get to recovery screen when I used a sdcard from a camera).

That shows right there that it was a faulty sd card. If you had a brick, from any method (be it Radio errors or someting else) the your phone would not be usable unless JTAG'ed, which from what I know is not availible or known how to do yet with the G1. I am sure it sucked balls though and felt like it was bricked.
[G1 Android Development] jtoyz2:
i flash in the right order with radio first but when i flash spl i did not do a format i just update now its stuck is mine brick

thanks
[G1 Android Development] joelikesramen:
So I'm pretty sure my phone is bricked. When I say pretty sure, I mean 100% sure. I was trying to un-root my phone, and I used the incorrect bootloader. When it was trying to flash the new one, it rebooted, showed a logo, and shut off. Nothing I have tried can get it to turn back on.

Any help would be great, even though I'm sure I'm done. Do you think T-Mobile would be able to replace my phone?

I'm using a myTouch, by the way.

Today has just been insane..
[G1 Android Development] arprice67:
noob

i have a bricked phone that i sent to a local repair shop. after a week he has told me he can read the bootloader and is going to work on it futher over the next couple of days. does the fact that he can read the bootloader help anyone?
[G1 Android Development] mr502:
Maybe a starting point

my contribution to the think tank.....

http://xdaforums.com/archive/index.php/t-487945.html

since the radio loads first and then...

This looks like a good starting point for "talking" to the radio bootloader . i dont have a bricked device but , as a shot in the dark , does the "blue light" mode allow mtty.exe to connect to a bricked phone? Has anyone tried this at all yet. If so, could directly enter a command to force to radio to pass the load to WHATEVER SPL is present . or to load up the dream diagnostic image.

It looks like other HTC forums have relied heavily on mtty or putty to bring their "bricked" phones back from the grave. especially with the help of gsleon3
[G1 Android Development] dr.frankinfurter:
How is the JTAG cable solution coming along?
[G1 Android Development] shaolinx:
I was just wondering, has anyone been able to UN-brick their phone?:confused:
[G1 Android Development] Boomer1721:
just flash rc29 and re-root thats it n try again
[G1 Android Development] Shane2:
Does anyone know if future radio updates are likely to also brick the device, and also, is it possible to fall back to Hard SPL without needing a wipe?
[G1 Android Development] Boomer1721:
who need an iphone when u have a g1....when ur g1 breaks and the iphone iz da last phone on earth
[G1 Android Development] Shane2:
Y cnt u uze engerlish lyk bruv innit

Seriously though, this thread is for serious problems, don't troll it.

Oh and FYI my phone has never broken ;)
[G1 Android Development] jaekim708:
So i got a new G1 after the previous one never got signal (took it to a shop and they sent me a replacement)

i downgraded to rc 29

rooted/put cm recovery 1.4 in

the most recent radio was already installed (62.50S.20.17H_2.22.19.26I)

flashed haykuro's spl.

then, as usual, it says "press home+back" to reboot.

so i did.

however, the phone is stuck at the white G1 screen. I tried to do reboot with home+power, and with camera+power, but both of those went to the G1 screen and stopped.

I can't see what's going on (adb logcat simply says -waiting for device-. is there another command?)

so should i wait on the screen, or did i make a mistake. If so, then where did i go wrong and how should i have done it?

edit: sorry - wasn't aware that downgrading takes the radio down also. how do you delete a post...
[G1 Android Development] kiiiiiid:
I have found some things

http://r3nrut.com/?p=1

any one have idea?
[G1 Android Development] etjazz001:
looking for jtag test-points

I will apologise if this post is not relevant to the argument.

Looking for a MSM72k datasheet I've found this file shared by fastludeh22 in xda-dev forum, it contains a qualcomm presentation where are explained the two JTAG ports present in MSM7200A. One is GPIO programmed and one is dedicated.

I suppose it isn't very usefull in a dense wafer as the dream borad but it's better than nothing.

I read that JTAG port must be activated by 4 pins selecting correct mode.

the file is here:

http://www.box.net/shared/etsai78xa2

found in post:

http://xdaforums.com/showthread.php?t=454842
[G1 Android Development] stuff:
That is a fella that has been helping us the most with this project.

I hope he gets it to work :)
[G1 Android Development] dman977:
Don't count JTAG out yet

So why is r3nrut saying JTAG is a bust when he never got to try it? He just ruined his MoBo and called it a bust. That is a failed attempt, not a reason to say that JTAG will not work.
[G1 Android Development] stanley.zhang:
G1 Mistake to upgrade HTC Hero Radio 63.18.55.06EU_6.35.06.18, change brick, a very painful！
[G1 Android Development] etjazz001:
JTAG finder

A possible simple interface to look for the correct test-points should be this porting to arduino of the jtag finder:

http://hackerspace.be/arduino-jtag-finder-workshop

if the phone goes to JTAG mode!
[G1 Android Development] etjazz001:
more on strange "blue led mode"

in any htc blue led mode is done by pressing "power + wheel" but I think it is not a SPL feature but an hardware mode.

Ideed you can run both blue led and SPL with this procedure:

If the power supply is plugged in the phone charging battery and you unplug and replug also battery with wheel pressed the phone power up and go to blue led mode, now unplug battery and plug it again.

If you also plug the power supply to charge battery with wheel pressed it show the blue led for half a second..

May blue led is JTAG mode activation? or a Radio emission test? or something that do nothing??

But it uses lot of battery power to do noting!

good luck!
[G1 Android Development] etjazz001:
mode pins

For n3nrut:

if you damaged the board why you don't consider toremove the cpu from the board and find out with a multimeter if the mode pins are located somewhere?
[G1 Android Development] arbab01:
Soft brick

i was recently trying to put a new update on my phone i believe it was spl.signed and after doing so when i restarted my phone it just froze at the t mobile g1 screen. i have tried to take out the battery and press home and screen. and it takes me to the triangle and exclamation mark. When i do Alt W (data wipe) it goes through the process but still does not go past the t mobile loading screen on reboot. i can also get to this white page with 3 androids on a skate board. the page reveals the following info:

dream ptvt 32B ENG S-OFF

hboot-1.33 2--5 (drea10000)

cpld-4

radio-2.22.19, 261

apr 20 2009, 15:30:43

please help me fix my phone thanks
[G1 Android Development] nasman1993:
Wipe then reflash.
[G1 Android Development] Geniusdog254:
etjazz001: That is a very interesting discovery.

To elaborate on what he said, you can get into SPL while in Blue Light mode:

Power into blue light while on battery

Plug into pc & pull battery, blue light will stay lit

Put battery back in and boot into SPL

I can't try this on a bricked device as I don't have one, but another interesting thing is that you can follow the same procedure, but try to boot into normal mode. Here is where it gets somewhat strange.

It will begin to boot into regular mode while in blue led mode as well. But, after the first few seconds (about 10 seconds I think) on the T-mobile G1/Rogers/Android (depending on your model) the blue light will go off & the phone will boot normally.