Related
Hey guys, i just went from davidukes custom rom to a stock rom because i need to send phone into HTC, but now that i downgraded, the colors on the screen are all messed up, can someone please help me
This happens to me after I upgraded my radio. Press the power button once (sleep mode) and then press it to turn on the screen and see whether it helps. For me that's the way (the color returns to normal) and I will have to live with it everytime it is soft-reset/rebooted.
elite-fusion said:
Hey guys, i just went from davidukes custom rom to a stock rom because i need to send phone into HTC, but now that i downgraded, the colors on the screen are all messed up, can someone please help me
Click to expand...
Click to collapse
you need to follow the guide to restore your stock SPL. if it's a UK HD, i believe it SPL 1.14. anyway, click the "Restore Stock SPL" link in my signature for instructions.
@exlixx - what you describe is NOT normal. based on your description of the problem, seems you didn't upgrade your SPL; especially if you're using one of the new ROMs. if this is the case, check out the "Fix Greenscreens" guide to correct your problem.
how would i know which one i need, i bought it in USA and it came with an English rom so i would need WWE, but there are several ones...
RUU_BlackStone_HKCSL_WWE_1.57.831.1_Radio_52.64.25.34_1.14.25.24_Ship.exe
RUU_BlackStone_HKCSL_WWE_1.19.831.0_Radio_52.49a.25.26_1.09.25.14_Ship.exe
RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.3 4_1.13.25.24_Ship.exe
RUU_BlackStone_HTC_WWE-AFK_1.14.421.5_Radio_52.49a.25.26_1.09.25.14_Ship.exe
RUU_BlackStone_HTC_WWE_1.14.405.3_Radio_52.49a.25.26_1.09.25.14_Ship.exe
RUU_BlackStone_HTC_WWE_1.14.405.0_Radio_52.49a.25.26_1.09.25.14_Ship.exe
all of these could be possibilities but... i dont know wat HKCSL means so maybe thats an abriviation for a country therefore i wouldnt need it, same goes for AFK... not sure which one i need even from the regular ones, my serial number is HT916KD***87 maybe you guys can tell me by my serial number
because right now i downloaded and have installed this one
http://www.filestube.com/b8b2b346f76b05d203e9,g/HTC-Stock-ROM-BLACKSTONE-1-14-401-3-22273-WWE.html
but my screen is still messed up, and i already installed Restore_Stock_SPL_114_2.zip as well
just do some research using the model number (on the retail box), goto HTC's website and try to download a ROM using your serial number. did you buy from a retailer or person? is the model number T8282 or T8285? if you go into bootloader mode and and if you see BLAC100 it's a UK version, BLAC120 it's a Telstra HD. UK=1.14 SPL and Telstra =1.15 SPL. i suggest retracing your steps to ensure you didn't miss anything, e.g., doing something out of order. good luck!
exlixx said:
This happens to me after I upgraded my radio. Press the power button once (sleep mode) and then press it to turn on the screen and see whether it helps. For me that's the way (the color returns to normal) and I will have to live with it everytime it is soft-reset/rebooted.
Click to expand...
Click to collapse
U dont have to live with it.
Upgrade ur spl and Rom and ull be fine..
it happens to most of the people who flash their device..
elite-fusion said:
how would i know which one i need, i bought it in USA and it came with an English rom so i would need WWE, but there are several ones...
RUU_BlackStone_HKCSL_WWE_1.57.831.1_Radio_52.64.25.34_1.14.25.24_Ship.exe
RUU_BlackStone_HKCSL_WWE_1.19.831.0_Radio_52.49a.25.26_1.09.25.14_Ship.exe
RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.3 4_1.13.25.24_Ship.exe
RUU_BlackStone_HTC_WWE-AFK_1.14.421.5_Radio_52.49a.25.26_1.09.25.14_Ship.exe
RUU_BlackStone_HTC_WWE_1.14.405.3_Radio_52.49a.25.26_1.09.25.14_Ship.exe
RUU_BlackStone_HTC_WWE_1.14.405.0_Radio_52.49a.25.26_1.09.25.14_Ship.exe
all of these could be possibilities but... i dont know wat HKCSL means so maybe thats an abriviation for a country therefore i wouldnt need it, same goes for AFK... not sure which one i need even from the regular ones, my serial number is HT916KD***87 maybe you guys can tell me by my serial number
because right now i downloaded and have installed this one
http://www.filestube.com/b8b2b346f76b05d203e9,g/HTC-Stock-ROM-BLACKSTONE-1-14-401-3-22273-WWE.html
but my screen is still messed up, and i already installed Restore_Stock_SPL_114_2.zip as well
Click to expand...
Click to collapse
May be u downgraded to the wrong stock SPL.
if u dont know do a hit and trial of all spl's starting from 1.14.00000.
Some one will surely work fine for u..
Do we really need another thread for this. Been discussed on many forums before. Just requires research. Use links provided by Cortez.i and post your queries within that thread. Abide by forum rules.
Check your SPL, what rom are you using. According to flashing guide do you have correct SPL for rom your using? If not you will experience this discolourization. Already a section on this in the wiki.
Thread closed
Hello everyone,
I have a rooted g1 and I was putting on the 2.1 rom on my phone. I was following a guys instruction off of youtube but it totally messed my phone up. Now its stuck on the pitcure with the open box pointing a yellow arrow on the phone right next to it(the update screen), what do I do??? Thanks for your help.
You dont even have root then...If it shows what i think your taking about....You should follow this simple enough my little brother(7yr) could master it:
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
no i have root access i already had about 5 other roms on there but this guy said that you need a radio update sign. the guys site is http://www.youtube.com/watch?v=QfPI9Qdagd0&feature=related
Sagz326 said:
no i have root access i already had about 5 other roms on there but this guy said that you need a radio update sign. the guys site is http://www.youtube.com/watch?v=QfPI9Qdagd0&feature=related
Click to expand...
Click to collapse
If you had root why did you flash the radio again?
That gives bricks applying radio after having root is pointless.
What are you trying to do?
i dont know im a noob if you dont know by know. well is there anything i can do???
Sagz326 said:
i dont know im a noob if you dont know by know. well is there anything i can do???
Click to expand...
Click to collapse
Just tell me everything you did, step by step.
ok first i put both of his zip files on my sd card then turned off my phone and turned it on with the home key, then i backed up my phone, then a factory wipe/reset, then applied the radio update, then tried to apply the other zip file but couldnt, so i rebooted my phone and now im stuck
Sagz326 said:
ok first i put both of his zip files on my sd card then turned off my phone and turned it on with the home key, then i backed up my phone, then a factory wipe/reset, then applied the radio update, then tried to apply the other zip file but couldnt, so i rebooted my phone and now im stuck
Click to expand...
Click to collapse
radio and spl?'
But you have to have a custom recovery image before you can flash either of those.
i think it was just a radio but not sure. but i followed that guys video step by step and now im in this position
yeah i have amonra
Sagz326 said:
i think it was just a radio but not sure. but i followed that guys video step by step and now im in this position
Click to expand...
Click to collapse
Ahh you might brick, you seem to have flashed the Radio made for HTC hero not G1....Notice the title: "How to get Android 2.1 on HTC Hero"
To use Hero 2.1 on G1 it shows it here @ XDA, you only needed Haykuro SPL and the 26I radio/
If rec mode is working then you arent brick or if you can get into bootloader.
how do i get in rec mode or bootloader
Hold down home when turning on the phone=recovery
Hold down camera button while powering on= bootloader
If you can't get into either one of those, likely bricked. I know with WM devices flashing a radio for another phone is one of the fastest ways to brick your phone, Android seems to be much more forgiving, so hopefully you will be lucky and if recovery and bootloader don't work, you can possibly get ADB to work.
If you don't figure out how to do this BEFORE you do it, you will likely brick your phone, if not sooner, soon enough. Doing it along with a video isn't enough to make sure you won't brick your phone.
Read through the steps of rooting, flashing a basic, stock ROM, do that a time or two, and then get into the more up-to-date stuff.
Your method of going about a new task is going to... well, it isn't going to work, unless you are really, really lucky.
ill try many ways to root my g1 dmd64 1.6 and no way
it wont to down grade on 1.5
any helps is wellcome
dzevadnp said:
ill try many ways to root my g1 dmd64 1.6 and no way
it wont to down grade on 1.5
any helps is wellcome
Click to expand...
Click to collapse
You will get more helps from the QA section.
When you report a problem being as detailed as possible will only help.
it wont to down grade on 1.5
Click to expand...
Click to collapse
Is it not taking the .nbh file? Did it error out? If so what was the error?
nolimit78
i got when try to flash nbh file NOT ALOW some numbers 000..
dzevad
by the way il try many metods from xda dev. and theunlockr and nothing
dzevadnp said:
by the way il try many metods from xda dev. and theunlockr and nothing
Click to expand...
Click to collapse
You you have the right DreaIMG.nbh file? RC7 is Europe RC29 is US.
no limit
I tried both, still nothing. I get the same message not alow
Where did your device originally come from? The error is related to the nbh file not being compatible. You can Google for this and find lots of discussion about that error message. If it is not US or UK it may take some special steps. There is a process involving a "gold card" that may be what you need.
I am also having this issue. it is a USA Tmo G1 with the DMD64 1.6 update. mine flashes a screen that says "no img file then gets stuck on a 3 colored screen with the radio info. any ideas?
SOLVED
problem solved with goldcard from theunlockr guide
the_Guchi said:
I am also having this issue. it is a USA Tmo G1 with the DMD64 1.6 update. mine flashes a screen that says "no img file then gets stuck on a 3 colored screen with the radio info. any ideas?
Click to expand...
Click to collapse
Make sure the card is formatted fat32 and the DreaIMG.nbh is the only file on the card.
dzevadnp said:
problem solved with goldcard from theunlockr guide
Click to expand...
Click to collapse
I've searched there website for this information, can you post a link to some good instructions or possibly write your own? I wanna root my new DMD64 G1 I just received.
Oh god if there wasn't a way to re-root I would be so mad... man I'm an idiot for unrooting lol. Effing 2.0 >.<
prince.siraj said:
Oh god if there wasn't a way to re-root I would be so mad... man I'm an idiot for unrooting lol. Effing 2.0 >.<
Click to expand...
Click to collapse
anybody got any idea?
create godcard by this guide
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
them put on it by mem card adapter or reader rc29nbh or 7 nomether what g1 wil recive evrything from goldcard
turn of your phone
put goldcard with nbh file in phone
then turn on by holding camera buton and end key until bootloader screen turns on
hit end key to start update. DO NOT INTERUPT PROCES
once it is done hit trackball to rstart phone
now you are on stock version rc29 or7
now you can root by this easy guide
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
sorry for bad english
i hope this will help
I have firmware 1.6 build number DMD64, how would I go about rooting my g1?
i need help with the rainbow screen
my phone is stuck on the rainbow screen i take out the battery and put it back in and it automaticaly turns on and jusmps to the rainbow screen can anyone help me?
(Not Allowed)
Having same issue (Not Allowed)
Will try Goldcard method...
Note - I previously had installed Android 2.2 on this G1 then went back to 1.6 as it was performing ok but slowly....
Was about to try it again but had updated my firmware to DMD64 then I was getting (Not Allowed)
I'll let you know how I get on with GoldCard...
My phone runs fine but can't root it at all with the desktop program and androot 1.6 it says it roots it but then open rom manager and it tells me dont have super user permissions.
i used universal androot and it worked without the hassle of trensfering files to your sd.
Hi everyone really sorry for opening a new thread for a G1 brick.
My G1 has stuck at the T-Mobile screen and on pressing Camera+Power i cant get into fastboot to restore using the .nbh file.
I am not able to get into recovery using power+home key also.
There has to be a way to get my dream back....
please please please help
JTAG or go for a replacement. I'm guessing it's a DangerSPL brick, right?
Danger SPL
Yes dude....
i have done this so many time.....
this time i forgot to update the radio first and this is stuck....
Someone should have a solution for this....
I read many thread which say use it as a paperweight...
I am not loosing hope....
XDA Member will have some solution.....
Maybe you should try to keep current on developments.
There is NOT A SINGLE REASON to use the deathspl.
As for your "poll"... what do you expect to learn from something like this? Do you realize that any numbers you get will be completely MEANINGLESS?
lbcoder said:
Maybe you should try to keep current on developments.
There is NOT A SINGLE REASON to use the deathspl.
As for your "poll"... what do you expect to learn from something like this? Do you realize that any numbers you get will be completely MEANINGLESS?
Click to expand...
Click to collapse
By adding the poll I am just trying to avoid post which says hey even i have the same problem.
I was upgrading to cm 5 which needs deathspl.
chinmayfun said:
I was upgrading to cm 5 which needs deathspl.
Click to expand...
Click to collapse
Aaaaannnnnd.... it doesn't need it
http://forum.xda-developers.com/showthread.php?t=704560
lbcoder said:
There is NOT A SINGLE REASON to use the deathspl.
Click to expand...
Click to collapse
Sure there is as its one if the few full engineering spls. And I don't think your latest development will ever be quite as user friendly (however some more configuration it will be very close)
The real user friendly fix/patch for 1.33.2005 (those that know what they are doing can decide if any benifit of the spl exists) is an assertion statement in the recovery script to check the radio version is not one of the two common 1.x ones.
(the evil patch is to make the assertion somehow also autoinstall the lattest Rogers e911 patched rom if the user has the 1.x radio. Because atm the rogers rom appears to be very safe from the user messing up the boot chain.. actually we may need to "perfect" the spl a bit more I think it will let us erase hboot)
I am still a newb to the android scene - and do believe I as well made the same mistake - and have bricked my G1.
If eveything I've read is accurate, I can purchase a donor phone - broken screen, or other issues - so long as the mother board is still good.
Swap out the new mother board for the bricked one, and have a working phone again - right ?
Have an opportunity on a donor phone - have no issues pulling phones apart, and putting them back together
But just want to make sure I understand the basics
Thanks in advance for any replies
Motherboard only option ?
Is replacing the motherboard the only option left ?
I am not sure i would be able to do that
Worst day of my life i screwed up big time
Any help is appreciated.
Some tool to recover back to original.
I can understand there is no way to repair as I am not able to get into recovery nor fastboot so cant adb also...
youtube
i checked the below video bt this is kinda a complicated and nt a solution for me
chinmayfun said:
i checked the below video bt this is kinda a complicated and nt a solution for me
Click to expand...
Click to collapse
There is no tool to get it back except by the options listed above. If you are not going to switch the mobos in the G1 then you won't be able to do the other option either. There is no software that can bring your G1 back after a deathspl.
protomanez said:
There is no tool to get it back except by the options listed above. If you are not going to switch the mobos in the G1 then you won't be able to do the other option either. There is no software that can bring your G1 back after a deathspl.
Click to expand...
Click to collapse
Thanks....
i will have to plan out on buying a new android....
had waited for a long time to get tht android phone from a friend in usa....
now there are many android phones available in india.... will have to start saving some money.... cant live without an android....
hey,
i had the same prob.
only thing,
mine bricke in cause of a radio update,
i tried all which was in my head,
and all i can do
but after some nights spending to my phone i found this:
i copied my nand backup to root of sd,
and connected it to pc
first he told me, device not known
so i tried to boot the modified recovery,
and *tada* i was in recovery mode,
plz try and tell me if it fix your problem,
for mine it did
best regards,
psycho
Mine is also due to radio update dude, before flashing spl the radio has to be flashed i and forgot to do that.
Will try out your suggestion, just hoping that it work and my g1 is back to life.
Ne ways appreciate your suggestion.
Please let me know if you were able to get into recovery mode prior to putting the files on the sd card.
And if you could tell me the list of files (if u had nething other then the nand update) which you put on the sd card, i can replicate the exact process.
Thanks,
Chinmay
Hope
Is there any hope to get the G1 back to life from the Death SPL Brick ?
You should read instructions carefully man. Its not that hard. You should always verify that you have a compatible radio before flashing DangerSPL.
There is a method to recover your device and it involves a lot of time and patience. Google "JTAG".
Sent from my HTC Dream using XDA App
"JTAG".
me too, my G1 Bricked (Not able to fastboot). but i wanna know if the JTAG method work 100%.please.
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 )