Database Develop

Did I brick my phone?!

Im using Rogers HTC Dream
I flashed the ADP1 Radio 2.22.19.16i from the Developer HTC website
My SPL is 1.33.0010
Then when i reboot the phone it stuck @splash screen showing "ROGERS"
And i cannot go to the SPL Screen or Recovery?
Is it broken? I only know if flash the SPL will break the phone, so the radio does?

Can you reboot by holding Green + Red + Menu? If you remove and put the battery back in, and hold Camera + Power, does anything come up? Can take a few seconds...
If anything comes up, things can be fixed and you should be fine.

No...
It doesnt work to me...
Cannot reboot use Call+MENU+Hang
Real Brick?!

well if you cant get in recover or anything sounds like it is.hold home plus power to see if it will go in recovery or not if you can get it there it's not bricked but if not thn yep it's bricked.if so call rodgers or who ever your service provider is and go that route .just say it's mess up .

this is really messed up because i started with same rogers htc dream as you and first tried to flash spl and got a brick. you tried radio first and got a brick. what are we supposed to do? can radio and spl be flashed at the same time?

this brick is caused by flashing the wrong radio on the wrong phone...... radios are just capable of bricking phones as the SPL.....
also, the radio may be incompatible with your spl
not sure 100% its a brick, maybe there is a solution. but im 90% sure its bricked if you cant access anything. try letting it sit on tht screen for a few minutes, it may take time to update

dev phone

been having some real trouble with my uk spec g1, ive experimented with it quite alot, ran jakrom, the dude, jesusfreke, and settled on cyanogen, i dont think ive ever gone about flashing it all properly, so my phone threw a fit and now after a hard reset it comes up with the google sign in droid and it says dev phone underneath?!?
i think i also lost root as i no longer have spare parts and no superuser permissions,
i tried to root again with a down grade to ukrc7, when i try to enter the bootloader it comes up with the skateboarding droids, says no images found and go's back to the droid skateboarding again, then i cant do anything with the device!!
help appreciated!!

tobirichmond said:
been having some real trouble with my uk spec g1, ive experimented with it quite alot, ran jakrom, the dude, jesusfreke, and settled on cyanogen, i dont think ive ever gone about flashing it all properly, so my phone threw a fit and now after a hard reset it comes up with the google sign in droid and it says dev phone underneath?!?
i think i also lost root as i no longer have spare parts and no superuser permissions,
i tried to root again with a down grade to ukrc7, when i try to enter the bootloader it comes up with the skateboarding droids, says no images found and go's back to the droid skateboarding again, then i cant do anything with the device!!
help appreciated!!
Click to expand...
Click to collapse
Could you explain a little better? So your phone is a UK G1, with 1.33.2005 SPL and you were running a Cyanogen Mod ROM, and then something weird happened?
If you're on 1.33.2005 SPL then it's a good thing your phone didn't take the NBH, your phone would have bricked. 1.33.2005 requires the 26i radio which gets downraded when reverting to RC7.

AdrianK said:
Could you explain a little better? So your phone is a UK G1, with 1.33.2005 SPL and you were running a Cyanogen Mod ROM, and then something weird happened?
If you're on 1.33.2005 SPL then it's a good thing your phone didn't take the NBH, your phone would have bricked. 1.33.2005 requires the 26i radio which gets downraded when reverting to RC7.
Click to expand...
Click to collapse
Its safe to Downgrade with the RC29 image as it replaces the radio AND the spl
Can you provide more details on the issue? How it happened/what you were doing?

one problem to another
Right, I've wiped my phone, formatted the sdcard so that all is on it is the files needed to update to cm!
The phone is running perfectly like a stock handset, but it won't let me root, when I type into telnet the code to apply the cm recovery image I get an mtd error, but it is still followed by the two ##

Have you tried using the root.apk app that helps to flash it? Search for it and maybe it can help you out

what is haykuro SPL and danger spl? please help

hi guys
i have been having truoble installing other roms im using cyanogen rom with hard spl but i cant flash another rom when i do it stucks on tmobile g1 boot screen i tryed installing death spl but still it stucks on g1 boot screen then i had to restore my phone and it works please guys help me how to fix this and i want to know what is haykuro SPL and death spl and danger spl? and is haykuro SPL and danger spl the same if not were can i find them ?

Before you do anything else, read this tutorial very carefully.
http://forum.xda-developers.com/showthread.php?t=625886
Make sure that your phone has the PVT board and not a DVT board.
You can check by going into fastboot and make sure that it reads DREAM PVT 32B ENG S-OFF on the first line.
Then you upgrade the radio first AND THEN you flash the Danger SPL.
Just make sure that you read that tutorial very carefully and know what you are doing or else you might just end up with a paperweight.

cg87 said:
Before you do anything else, read this tutorial very carefully.
http://forum.xda-developers.com/showthread.php?t=625886
Make sure that your phone has the PVT board and not a DVT board.
You can check by going into fastboot and make sure that it reads DREAM PVT 32B ENG S-OFF on the first line.
Then you upgrade the radio first AND THEN you flash the Danger SPL.
Just make sure that you read that tutorial very carefully and know what you are doing or else you might just end up with a paperweight.
Click to expand...
Click to collapse
thanks i will read this and try and see if this works or not i will reply here back

hi i did what in the tuturial said an when i Flashed the Radio "ota-radio-2_22_19_26I.zip know my g1 wont even boot when i press the power button nothing happens it does not even start please help me i dont know whats wrong?

Try removing the battery and then put it back in and see if it turns on. Then see if you can get into recovery mode. BTW, what recovery are you using right now?

cg87 said:
Try removing the battery and then put it back in and see if it turns on. Then see if you can get into recovery mode. BTW, what recovery are you using right now?
Click to expand...
Click to collapse
i tryed everything removing the battery and putting it back on nothing works just dead it does not do anything when i try to press the power button im using cyanogen 1.4 recovery but whats the point of it if the phone is not powering on?

loveispoison said:
i tryed everything removing the battery and putting it back on nothing works just dead it does not do anything when i try to press the power button im using cyanogen 1.4 recovery but whats the point of it if the phone is not powering on?
Click to expand...
Click to collapse
Did you check to see if you phone has a PVT board? Did you install the radio first and then install the SPL? If you did it the other way around, then will will have a brick.
Is the phone not powering on after you flash the radio or after you flash the spl?

yes i know the phone has pvt and i checked it and i installed the radio first i did not had the chance to install the spl and after rebooted into recovery i pulled the battery out and after that it did not power on

That's weird because the radio should not have bricked your phone. Since you were able to boot the phone after you flashed the radio, it couldn't have been the radio either. Why did you pull the battery when you were in recovery?

What was your battery level before you flashed? If it ran out during the installation, then you have a brick. Try charging it some and see if it turns on.

cg87 said:
That's weird because the radio should not have bricked your phone. Since you were able to boot the phone after you flashed the radio, it couldn't have been the radio either. Why did you pull the battery when you were in recovery?
Click to expand...
Click to collapse
well the flashing was complete and i rebooted the phone and it went back into recovery and i removed the battery i tought i will boot into the phone instead of recovery
mejorguille said:
What was your battery level before you flashed? If it ran out during the installation, then you have a brick. Try charging it some and see if it turns on.
Click to expand...
Click to collapse
battery level wa less but the flashing went ok it happend after flashing it i tryed another battery but same nothing happens

IIRC when flashing a radio, the phone will reboot itself during the process then carry on flashing.. you didn't pull your battery then did you..?

goldenarmZ said:
IIRC when flashing a radio, the phone will reboot itself during the process then carry on flashing.. you didn't pull your battery then did you..?
Click to expand...
Click to collapse
when i flshashed the radio then i rebooted the phone and it rebooted into recovery then i pulled the battery out as soon as i saw the recovery mode

loveispoison said:
when i flshashed the radio then i rebooted the phone and it rebooted into recovery then i pulled the battery out as soon as i saw the recovery mode
Click to expand...
Click to collapse
Are you sure it was the recovery screen? Did it have all the text options? The radio flashing screen looks similar.. If you pulled it out there, you're bricked.

I am pretty familiar with the guide that you said you followed. I dont remember seeing the part in it that says "pull the battery"...
UPDATE: After this persons unfortunate experience I have updated the guide to actually tell you not to pull the battery at any point during the installation process. I know its common sense but this thread goes to show that unless you tell someone not to do something they may think that its ok.

goldenarmZ said:
Are you sure it was the recovery screen? Did it have all the text options? The radio flashing screen looks similar.. If you pulled it out there, you're bricked.
Click to expand...
Click to collapse
im sure it said flashing complete then rebooted it and i pulled the battery out anyways doesnt matter know bcoz there was guarantee on my phone so i took it back to them and told them when i woke up in the morning the phone was like this and i got my money back and i bought an iphone 3gs thank you for your help
Joe333x said:
I am pretty familiar with the guide that you said you followed. I dont remember seeing the part in it that says "pull the battery"...
UPDATE: After this persons unfortunate experience I have updated the guide to actually tell you not to pull the battery at any point during the installation process. I know its common sense but this thread goes to show that unless you tell someone not to do something they may think that its ok.
Click to expand...
Click to collapse
thanks for your help

loveispoison said:
im sure it said flashing complete then rebooted it and i pulled the battery out anyways doesnt matter know bcoz there was guarantee on my phone so i took it back to them and told them when i woke up in the morning the phone was like this and i got my money back and i bought an iphone 3gs thank you for your help
Click to expand...
Click to collapse
After you flash the radio it tells you to reboot and it reboots and then finishes installing the radio. Then it reboots to recovery. You must have pulled the battery before the radio finished installing.

my brick ?

no adb and no fastboot on pc
i can go into recovery but when phone boots it goes straight to tri color screen a.k.a bootloader with serial0
i tried downgrading it shows down grade on bootloader but not booting to rom what am i not doing

any suggestions

mods close thread solved by reflashing org.spl

ok it happen again and this time flashing stock spl is not working any help any one

Well it's very probable that by flashing your stock spl that youre now running a perfected spl which won't let you get any further, If you do manage to get back into the rom adb erase and flash a new recovery and spl because it sounds as if your recovery is fried. If you want help from others it would be a good idea to include rom, spl, radio, recovery that you're running so we can better assist you. every combination is different and often it's something as simple as a radio/rom mismatch or an overclocking issue

ok im at complete stock everything

rooted or unrooted?
one second thought.. try downgrading and re-rooting your phone via old school rc29 rom versions..
something has obviously gone awry. lets see if flashing an older rom will get you into the phone and then you can flash a new recovery, spl and radio from there.
http://forum.xda-developers.com/showthread.php?t=442480&page=35
Sometimes you just gotta redo everything because of software mismatches and extra crap in your phone that isn't supposed to be there.

i had bought the phone like that stuck on bootloader i fixed it after i tried to flash the org. spl it didnt flash but after reset it booted fine after rooting and using the danger spl and cannon complete eclair my carmera went bugging so i decide to downgrade and reroot i flashed the rc29 but it went back to the first problem again

all eclair roms have problems with cameras.. but this sounds more like there's just something not right.. could be anything from your radio to your recovery.. Full wipe and restart the process I no longer have a g1 but im pretty sure if i downgraded from 2.1 to rc29 my phone would act screwy too.

i did the full wipe formated sd cards i am at a brick wall with out a brick

thatruth132 said:
i did the full wipe formated sd cards i am at a brick wall with out a brick
Click to expand...
Click to collapse
set up sdk/adb and see if your phone is being found or not with the command
Code:
/cd
cd AndroidSDK/tools/
adb devices

i have adb installed correct its not picking up in adb at all no fastboot of course

I don't know i maybe wrong but think you should start all over again
downgrading to v1.0
although i am not that experience
please wait for someone how know

nothing i try is catching

still needing help

And we still don't know what you have installed..
1) make sure your phone is off: boot into the spl by turning on the phone while holding down camera.. tell us all the text on that screen
2) power off your phone again and enter recovery (power on holding home) if it loads do you see any version info? Or just an icon in the center of the screen.. if it dosent load tell us that
3) can you boot into a system (in your case I assume not but if others are reading) tell us the build number and rom if possible in about phone. If it wont boot tell us that.
4) Last what carrier and country is the phone originally from. (This changes what "stock" is)
With all of this information we can find the correct path to solve any issues.. usually without resorting to jtag.

DREA 100 PVT 32B
HBOOT 0.95.0000
CPLD 4
Rado 2.22.19.26I
Sep 2 2008
At this point, I searched around again for 30 minutes or so, and saw the stuck camera button problem and took off the back battery case and performed a restart and still went straight to the SPL with almost no delay. The camera button depresses properly and doesnt seem to be stuck.
After all this, I figured I should just start off fresh, so I flashed the DREAM.nbh for RC29 that is listed everywhere in order to get root. On restart, I held down the camera button, and the white screen comes up to ask if I want to boot image.
I do, and everything goes off without a hitch, I press action key to restart and end up at the SPL screen again, this time, my radio is down to v1.2 instead of v2.2 so I know I changed something. I have done this update twice just to make sure everything is going right but I am still stuck at SPL.
Sorry for the extensive post, but as you can see, I did a bit of trouble shooting before I posted this.
1 did that
2 did that regular recovery
3 can not boot into system on 1.5 cupcake signed-kila-ota-148830.de6a94ca.zip
4 tmobile usa

anything i know its not bricked

OK you have rc29 installed. That is the original android with 1x radio. So software wise you are fine. (Ie not bricked)
The problem is you need to enter normal boot and are always entering the spl instead?
My guess is the camera button is stuck..
The real button is surface mounted on the main board what you press is a user friendly piece of plastic on top of that, attatched to the phone's cover.
If you have any warranty get T-Mobile to take a look.. Otherwise you can try opening it and cleaning it out.

i tired that and i actually switched the mother boards and check the buttons and nothing is stuck when i update to rc29 it lets me when i update to cupcake it lets me the text even changes on bootloader but not actual boot

Hard Bricked my G1. Any way to unbrick it?

Hi everybody,
I was trying to load the cyanogen mod to my G1
Had Android 1.6 and Radio 2.22.23.02
I downgraded to RC29 successfully
Rooted my phone
Loaded recovery-RA-dream-v1.7.0.img. Flashed successfully
Then started following instructions below:
wiki . cyanogenmod / index.php / DangerSPL_and_CM_5_for_Dream
I got stuck in step 6
It is probably because downgrading to RC29 also downgraded my radio version. I did not check the radio version again after I downgraded
Using danger.spl bricked the phone
I searched online and found some solutions with JTAG, but I am in Turkey and do not have access to purchasing these from ebay or the know-how to apply them (as you can tell from my mistake above!)
1) I found the below solution, but not sure if it will work:
code . google / p / android-roms / wiki / Unbrick
They say it will only work if you have soft-bricked your G1. I'm not sure
2) Others say I need to call T-mobile Customer care (where I purchased the phne from), but that was about a year and a half ago. How long is the warranty on the G1? 1 year or 2 years?
3) And yet others say use it paper-weight
Should I go for option 3?
What do you think?

Wiki Instructions
What is DangerSPL?
This SPL is actually a port of the Magic/MT3G (Sapphire)'s SPL to the Dream/G1. Called danger because not only does it wipe your data in the repartition process (data can be restored with Nandroid restore after flashing DangerSPL), it has a chance of bricking your phone if you would ever choose to downgrade the radio after flashing it (see below for compatible radios). Never flash a 1.x, 4.x, or 6.x radio with DangerSpl
It is not required for CyanogenMod versions 4.X (CM4) and below, but required for the CM5 series on the G1/Dream.
Why is it required for the CM5 series on G1/Dream?
The G1/Dream's /system partition was originally created to take ROMs up to 64MB. The CM5 series for the G1 & Magic/MT3G is currently too big to fit on this partition.
Why don't Magic/MT3G users have to apply it?
The Magic/MT3G (Sapphire)'s /system is set to take ROMs up to 96MB by default, so no SPL change is needed.
Is it dangerous?
While the method of applying it has been perfected over the course of its use, any modification of SPL/Radio/ROM carries with it an inherent risk. That being said, if you pay attention, follow instructions, and plan your approach, it is actually an easy process.
How do I check if I already have DangerSPL?
Boot into fastboot mode by turning the phone on while holding the camera button and pushing the power button. The second line contains your SPL version. If it ends in 2005 (eg 1.33.2005) then you have DangerSPL installed already. The line with RADIO tells the radio version, which is important if you don't have DangerSPL. To leave fastboot mode, press MENU+SEND+END at the same time.
Installation
Warnings
Make sure that you have a full battery during the steps below and at no point remove power from the device (i.e. no battery pulls!). See the first two bullets in troubleshooting regarding battery use after flashing CM5 and fixes for higher-than-expected battery drain.
There has been some development/debate over DVT/PVT and bricks. Optional reading (but still recommended): XDA forum
Prerequisites
A rooted G1/Dream
A compatible radio (IMPORTANT: If you just rooted, the RC29/RC7 install includes a 1.x radio and you MUST install one of the 2.x radios below before DangerSPL)
2.22.23.02 seems to get more bars for T-Mobile US customers, though non-US users might have better luck with 2.22.19.26i.
(HardSPL/Engineering Spl Users) Radio installations can be had by fastboot flash radio radio.img after extracting radio.img from the .zip
Either of the following radio versions is acceptable.
Radio 2.22.19.26I
Radio 2.22.23.02 (G1)
Rogers Dream users: A 3.X radio is Danger compatible (eg 3.22.26.17)
Failure to meet the Prerequisites WILL result in a BRICK!
Files required
Danger Spl
gapps-ds-ERE36B-signed.zip, Mirror1
Latest CM5 for Dream/Sapphire
ONLY Roger's Dream users: EBI1 kernel for 5.0.x
Steps
It has been brought up that Clockwork Recovery struggles with this guide, so Amon_ra is v1.7.0 recommended. If you have CM or older recovery, upgrade to Amon_Ra first.
Please if you need to diverge from these steps for any reason start over from step 1 when you return.
Boot into Fastboot (Power on the phone holding the camera button) This will either show a screen with dancing androids or a "rainbow" splash. Here you will find the hboot/radio version:
radio 1.x: You will need to upgrade this to a 2.x radio before running this process.. please upgrade and re-do this step (Ie. verify you see the updated radio in fastboot before continuing)
radio 2.x: You may press MENU+SEND+END at the same time and proceed (unless hboot-1.33.2005 is installed; indicating you already have dangerSPL)
radio 3.x: You may press MENU+SEND+END at the same time and proceed (unless hboot-1.33.2005 is installed; indicating you already have dangerSPL)
Copy DangerSPL (spl-signed.zip), CM 5.0.x, and gapps-ds-ERE36B (& Ebi1 port if required) to the root of your sdcard.
Reboot/Boot into your custom recovery by holding down the 'home' key before the G1 splash appears.
Make a Nandroid Backup (ext not required) (recommended for upgrading users, not required for freshly-rooted users)
Flash DangerSPL (spl-signed.zip). It will install and then ask you to reboot to finish the installation
Reboot as prompted at the bottom of the screen. This will finish installing DangerSPL and reboot back into recovery so you can flash your ROM.
Once back into recovery Wipe Data/Factory Reset
Flash CM 5.0.x THEN gapps-ds-ERE36B (& Ebi1 port if required); then reboot (Boot may take longer than normal)
Login to Android/Google as per usual
If you want to restore the nandroid backup (to attempt an unrecommended no-wipe upgrade between CM4.2 and CM5)
[Optional] Reboot to recovery, and issue a Nandroid Restore, then follow the regular instructions .
This command will attempt to restore user data.
Restoring will also restore your previous Firmware, so you have to follow the instructions to get 5.0.x again
Note: If this causes undesired consequences (ie bootloops, FC's, etc) then run Fix Permissions/'Fix UID Mismatches'.
***************************************
Instructions for the 'soft-brick' (I think)
How to Un-Brick Your Phone
(Method 1)
Ok so you're trying to put this really cool new custom ROM on your phone and then suddenly, your phone won't start up…well my friends, you have got yourself a bricked phone. The thing you worry about the entire time you're rooting, and flashing your phone, has now become reality. Well, fear no more, for I, CTDroidBeast have found a way to unbrick your device!
It's really easy. It's actually easier then rooting your phone, believe it or not.
Ok, you will need a new SD card, because I bet if you use the one out of your device your computer will not be able to read it. But if it does then HEY, you're in luck. You don't have to spend your money on a new SD card.
So let's get started.
Step 1: Turning Off Your Phone
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to take out the battery.
Step 2: Preparing Our SD card
Take out your SD card and put it into an SD card reader or some type of other adapter so that we can view it from our computer. If you cannot view the SD card on your computer then you're going to need a new SD card.
Download DREAIMG-RC29.zip and unzip the file.
Reformat the SD card to FAT32 and copy the DREAIMG.nbh onto it.
Safely eject the SD card.
Put the SD card into your device.
Step 3: Wipe The Phone
Hold home and press the power button.
When you see the image of an ! mark, open your keyboard and press Alt + L if you cannot see any command options.
Do a factory reset by pressing Alt + W or just using the trackball.
When the reset is done, go ahead and hold the camera button and select the reboot system now option with your trackball.
Step 4: Flashing The Phone
Once the grey screen pops up (or the white screen if your phone was rooted with JesusFreke) it will ask you to hit a button to start installing the image…press that button. DO NOT DO ANYTHING TO STOP THIS PROCCESS. It will take about 8-12 minutes.
When the image has completed the installation (it will say completed), go ahead and press the green, red, and menu buttons at the same time. The phone will reboot.
And your done! Your phone is now unbricked!.

Please help!

YOU FAILED.
If you don't take the time to read and learn what you are doing, why should anyone take the time to help you?
WHY would you EVER install RC29? IDIOTIC MOVE!
WHY would you EVER install deathSPL? IDIOTIC MOVE!
I say you deserve what you got.

lbcoder said:
YOU FAILED.
If you don't take the time to read and learn what you are doing, why should anyone take the time to help you?
WHY would you EVER install RC29? IDIOTIC MOVE!
WHY would you EVER install deathSPL? IDIOTIC MOVE!
I say you deserve what you got.
Click to expand...
Click to collapse
I was just following the Wiki instructions ( Full Update Guide - G1/Dream Firmware to CyanogenMod ) here:
My radio before downgrading was 2.x, so I assumed it would still be the same after the RC29 downgrade, but it turns out the downgrade also dongrades the radio to 1.x
therefore death spl bricked the phone
I should have checked the radio version for a 2nd time before flashing death spl
Is there any way to fix this now??

HEARTBREAKER123 said:
I was just following the Wiki instructions ( Full Update Guide - G1/Dream Firmware to CyanogenMod )
Click to expand...
Click to collapse
You did not follow the instructions.
You deliberately skipped step one on the danger spl instructions. Put there so that those who didn't realize the radio had become downgraded didn't do what you just did. You also ignored the warnings on that page that rc29 installs the 1.x radio.
HEARTBREAKER123 said:
Is there any way to fix this now??
Click to expand...
Click to collapse
What part of not having the right radio will brick your device wasn't understood..
by all means hope your recovery is messed up and that you have access to fastboot when you attatch a USB wire.
Otherwise there is jtag. .. bit more complex than flash spl-signed.zip after being 100% sure a 2.x radio is installed however..
Another option is replace it.. some have found replacing the main board + daughter board of a working phone in bad cosmetic shape (screen cracked) a cheap alternative here than a brand new dream. Still requires reading the service manual to properly disassemble what you need without having a bit of a mess.. particularly if you skip a step.
My recommended solution is to find a phone you can deal with stock firmware buy it and sell the rest of your dream as is.. you want root you need to understand the instructions not just follow them.

Alright, well I think he got the point - he should have followed instruction better
I'll keep it as straight forward as possible, no there is not a way you can unbrick your phone without the JTAG tools. T-Mobile's warranty is only one year, afterwards they will not replace your device for any reason.
The soft brick solution you posted will not work, because you have a hard brick.
I believe you only have a couple of solutions.
a) Get a new G1
b) Buy an old G1, preferably one with a broken screen so its cheaper, and place the motherboard of that G1 into your current one
c) Work with some members of XDA and see if you can work out an arrangement to get you the JTAG tools, though this is unlikely to work and difficult to do.
I'm sorry that you have broken your G1, it's a terrible feeling to break your phone in this way where everything is physically still perfect. I believe your best bets are probably solution "a" or "b", you can shop around locally and see if you can find anything
Best of luck.

Thanks for the help.
I think I will try and get another G1 to see if I can replace the motherboards

HEARTBREAKER123 said:
Thanks for the help.
I think I will try and get another G1 to see if I can replace the motherboards
Click to expand...
Click to collapse
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.

lbcoder said:
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
Click to expand...
Click to collapse
Like the OP said, he lives in Turkey and is unable to purchase these items on eBay.

SolemnWishing said:
Like the OP said, he lives in Turkey and is unable to purchase these items on eBay.
Click to expand...
Click to collapse
Turkey is NOT a back-woods country and there ARE LOTS of sources besides ebay. In fact, ebay is the LAST place you should look for electronic components.
I GUARANTEE that the required components can be purchased in STORES all over the place in Turkey.

lbcoder said:
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
Click to expand...
Click to collapse
$2? I thought Jtag cost like 70 bucks

racerxgt said:
$2? I thought Jtag cost like 70 bucks
Click to expand...
Click to collapse
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Being more careful this time, I went through the wiki steps and installed CM 5.0.8 and gapps-ds-ERE36B-signed
Yaay!
But then I noticed that CM6 was out, and that it had flash, so why wait, right?
I flashed CM6 with no problems, rebooted the phone, logged in, everything seemed OK, except that I didn't have google apps
So I flashed gapps-mdpi-FRF91-signed.zip and... I wasn't able to log on to google!
You know the menu that asks you to sign in to your google account at the beginning
It says "touch the android to begin"... And when I touched the android, it wouldn't ask for my username and password.. Right click would go into 'Wireless Settings', and I was able to successfully define an APN and get a 3G connection, however, even after all that, and when the phone had reception,
touching the android would make the android change color, but it wouldn't let me go to the next step!
So I decided to flash the previous google apps
Now the phone does not boot in normal mode
I can access the bootloader and the fastboot menu (both Camera+Power and Home+Power work fine), but I am not sure how to fix the problem I have
I tried downgrading to Android 1.5 and starting over, but when I go into the bootloader menu, I see 3 androids with skateboards and the following options:
CAMERA_STEP2 : Hboot mode
SEND: Reset device (Doesn't reset, it just reboots when you try)
ACTION: Restart to hboot
MENU: Power down
And when you are in hboot mode, you can't click anything
How can I revert to CM 5.0.8??
Also, is it normal for the new gapps to cause this type of an error?

HEARTBREAKER123 said:
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Being more careful this time, I went through the wiki steps and installed CM 5.0.8 and gapps-ds-ERE36B-signed
Yaay!
But then I noticed that CM6 was out, and that it had flash, so why wait, right?
I flashed CM6 with no problems, rebooted the phone, logged in, everything seemed OK, except that I didn't have google apps
So I flashed gapps-mdpi-FRF91-signed.zip and... I wasn't able to log on to google!
You know the menu that asks you to sign in to your google account at the beginning
It says "touch the android to begin"... And when I touched the android, it wouldn't ask for my username and password.. Right click would go into 'Wireless Settings', and I was able to successfully define an APN and get a 3G connection, however, even after all that, and when the phone had reception,
touching the android would make the android change color, but it wouldn't let me go to the next step!
So I decided to flash the previous google apps
Now the phone does not boot in normal mode
I can access the bootloader and the fastboot menu (both Camera+Power and Home+Power work fine), but I am not sure how to fix the problem I have
I tried downgrading to Android 1.5 and starting over, but when I go into the bootloader menu, I see 3 androids with skateboards and the following options:
CAMERA_STEP2 : Hboot mode
SEND: Reset device (Doesn't reset, it just reboots when you try)
ACTION: Restart to hboot
MENU: Power down
And when you are in hboot mode, you can't click anything
How can I revert to CM 5.0.8??
Also, is it normal for the new gapps to cause this type of an error?
Click to expand...
Click to collapse
*FACEPALM*

goldenarmZ said:
*FACEPALM*
Click to expand...
Click to collapse
Don't facepalm just yet
I managed to go back to 5.0.8 after doing everything from scratch
I guess I will use it like that for a while until CM6 / google apps stabilizes

HEARTBREAKER123 said:
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Click to expand...
Click to collapse
I bricked my G1 as well, but I'm not in the US
Do you have an idea what the JTAG adapter looked like ?

wow you guys sound mean to the poor guy when he was just making a newbie mistake. i remember when i was making all of those mistakes...hell im still making those mistakes and even thou i have gotten my fone to freeze on the g1 logo or even just go into a constant reboot im glad iv been able to fix the problem everytime and still dont know what im doing im just learning. but hey isnt that procedure that you have up there an unrooting procedure???? and for those getting the wrong gappss try downloading the tiny mdpi on the dream that one worked for me, the mdpi didnt work at all till i tried that one got it from the cyanogenmod site. by the way i gotta say thanks to all the devs, which i had a brain like yals id love to join in on developing but im kinda an idiot here lol

spike210 said:
wow you guys sound mean to the poor guy when he was just making a newbie mistake. i remember when i was making all of those mistakes...hell im still making those mistakes and even thou i have gotten my fone to freeze on the g1 logo or even just go into a constant reboot im glad iv been able to fix the problem everytime and still dont know what im doing im just learning. but hey isnt that procedure that you have up there an unrooting procedure???? and for those getting the wrong gappss try downloading the tiny mdpi on the dream that one worked for me, the mdpi didnt work at all till i tried that one got it from the cyanogenmod site. by the way i gotta say thanks to all the devs, which i had a brain like yals id love to join in on developing but im kinda an idiot here lol
Click to expand...
Click to collapse
bigest mistake evar was probably buyng tha damn mobo ...you see i have 3 HTC's 1 HTC Dream that work's just fine , 2 T Mobile G1 that it's a piece of **** ( it got's nothing in comon with HTC dream it's just a cheap crap copy of the original ) and 3 it's a HTC with Win Mobile wich i think it's by far the most stable mobile operating sistem for now , all of you will say that it does not work like that , but think about this .... how manny win mobo's hawe ever been bricked?! and how manny android mobos are there bricking every day ? your android will brick eventualy ... oh yeah and i am selling 2 HTC dream Black and white
Thumb's upp if you are born in the rong generation )