I have the Rogers HTC Dream and I was going to update the radio blah blah to the 2.22.19.26I one so I put the radio on the sd card and in preparation I was going to do nadriod. But I wasn't paying attention at all and flashed the radio instead (I am an idiot).
Now it is just stuck on the Rogers screen and holding the home button or the camera button doesn't do anything.
I am fooked arn't I
Any help?
Bricked....try looking into this....its cheapier than buying a new phone.
http://forum.xda-developers.com/showthread.php?t=576628
Im sorry for your phone...
Can you get into adb at all? I didn't do that exact issue, but one time I did something that screwed up some things, I couldn't boot the phone or get into recovery, but I was able to adb into it, reapply the recovery.img and then get into recovery to reflash a ROM and everything else.
Computer doesn't recognize the phone at all
I phoned and told them that the new update for the 911 fix bricked it. They said they will send me a new one and if there is no water or hardware damage it will be covered. It's not water damage and it's not hardware damage (it's software ) so I will see what happens.
They didn't mention anything about software and they might not check so I might get lucky.
so your comp doesn't recognize it in fastboot also?
i thought i was bricked till i realized that RA Recovery 1.5.2R didn't work when i downgraded my EBI1 radio to .26I one. had to load 1.5.2w/o R to make things work again.
then again, im all new at this stuff (just a few days). so i might not even know what the hell im doing.
yes your right that I would need a new recovery also but it is too late now as I can't get into fastboot or recovery and computer doesn't recognize my phone while it is stuck on the Rogers Logo.
I assume the new dream that they send will already have the new SPL, radio and rom so hopefully someone will be able to root the new "perfected" SPL by the time that I get it .
I saw in the Saphire section that you should beable to use a goldcard but I am not sure if that works for the Dream also... I guess I will find out once I get my new Dream.
Are you sure its not finished installing yet? It took two reboots and a few minutes to install the radio on my phone. I couldnt do anything and I was really scared, but then I just left it on and it finished on its own=p GL
Related
Hi two days ago i decided to put the jachero rom on my g1 and it said i had to update the radio so i did then put the latest spl so i did and after i renamed the spl to update.zip and applied it. my phone got bricked and i cant apply the dreaimg.nbh to wipe everything and cant go to recovery and i dont know if it will never work again?? please heelpppp!!! oh yyeah and im 13.
what do you mean brick? which radio did you install and which spl did you install after that?
does your phone turn on at all?
um
i put the radio 2.22.6i and idk about the spl and it just says tmobile g1
Alanrocks15 said:
Hi two days ago i decided to put the jachero rom on my g1 and it said i had to update the radio so i did then put the latest spl so i did and after i renamed the spl to update.zip and applied it. my phone got bricked and i cant apply the dreaimg.nbh to wipe everything and cant go to recovery and i dont know if it will never work again?? please heelpppp!!! oh yyeah and im 13.
Click to expand...
Click to collapse
it seems like you're pretty bricked.
Please give more information on your procedure.
If you cannot boot into recovery (home + power) or the bootloader (camera + power) then it is most likely bricked. If you have insurance, just tell T-Mobile that your phone told you that there was an update available, and when you clicked OK, the phone restarted and then you were stuck at the G1 screen.
um
well i dont know anything how to flash cyanogen
on the jachero page it said get the latest spl so i updated and after that canot go into recovery
so i only have warranty no insurance
Alanrocks15 said:
well i dont know anything how to flash cyanogen
on the jachero page it said get the latest spl so i updated and after that canot go into recovery
so i only have warranty no insurance
Click to expand...
Click to collapse
if you dont even know what your putting on your phone, you kinda deserved it...
Use your warranty, tell them there was an over the air update and ur phone ran out of battery in the middle of it.... and read up/think before doing something like that again...
theres really nothing you can do now. You need to give us more detailed procedures if you want a second opinion
well
i did know what to do but since i already have the latest radio then i just put the spl and if i get another g1 if i already have the hard spl do i need to put the latest because igot the hard spl from another forum but since the jachero page told me to update it i did that maybe i dont have the latest radio but no since anymore and thank you i will tell tmobile i got a ota but didnt the ota thing stop like 3 weeks ago i dont think they will believe me that i just got an ota barely
Alanrocks15 said:
i did know what to do but since i already have the latest radio then i just put the spl and if i get another g1 if i already have the hard spl do i need to put the latest because igot the hard spl from another forum but since the jachero page told me to update it i did that maybe i dont have the latest radio but no since anymore and thank you i will tell tmobile i got a ota but didnt the ota thing stop like 3 weeks ago i dont think they will believe me that i just got an ota barely
Click to expand...
Click to collapse
So? Just say that you had your phone off for a few weeks cuz you went on vacation and chose to bring another phone for safety's sake, and when you got back, you turned on the phone and presto! OTA update...
Alanrocks15 said:
i did know what to do but since i already have the latest radio then i just put the spl and if i get another g1 if i already have the hard spl do i need to put the latest because igot the hard spl from another forum but since the jachero page told me to update it i did that maybe i dont have the latest radio but no since anymore and thank you i will tell tmobile i got a ota but didnt the ota thing stop like 3 weeks ago i dont think they will believe me that i just got an ota barely
Click to expand...
Click to collapse
1) Use full stops, 'cos that's near impossible to read.
2) No, hard SPL will not work you need Haykuro's SPL.
3) Your phone will only have bricked it you had the old radio OR you did not have a PVT board. Did you look in the bootloader before you flashed the new one? I'm guessing not.
4) Luckily there was a security (I think it was security) update that was just released, so they shouldn't qustion it.
ok sorry
Ithink the warranty will cover it
I would go with the OTA story especially since there was just an OTA update released that has been pushed to phones over the last few days. I know a few people who also didn't read up before they started flashing and they too bricked their phones however, the OTA story worked most of the time. This is really your only choice seeing that you don't have insurance on the phone. Good luck
Just use the OTA story again lol
Tmobile wont hassle you too much about it.
Make sure you download the Radio that Haykuro provided, flash it, then boot into the bootloader to make sure it reads properly. Also verify that you have a PVT board.
Put the update.zip with the SPL on your phone AND VERIFY THE MD5 CHECKSUM (you should do it with the radio too actually)
and continue to follow the proper directions.
If you brick after following that, use the OTA story again but stick to HardSPL lol
what is checksum and pvt board?
Alanrocks15 said:
what is checksum and pvt board?
Click to expand...
Click to collapse
PVT board is the board that won't brick when flashed with the Danger SPL. Just another design. You can check your board revision by booting into bootloader (camera+power).
md5 checksum is a special key that is tied to the file that is generated based on that file. If the file that you downloaded is corrupt or different compared to the original file, the md5checksum will be different, letting you know that you need to re-download the file or risk a brick.
help help help help
please somwbody help please...my g1 t mobile freeze in g1 screen...i can't power+camera, power+volumen down, no bootloader screen nothing, only freeze in g1 tmobile screen...
when press action botton and power a blue led come on but nothing happend...
somebody can help me with any information
jtag pin outs...or somenthing to solve this problem..i come from panama
help help help help
please somebody help please...my g1 t mobile freeze in g1 screen...i can't power+camera, power+volumen down, no bootloader screen nothing, only freeze in g1 tmobile screen...
when press action botton and power a blue led come on but nothing happend...
somebody can help me with any information
jtag pin outs...or somenthing to solve this problem..i come from panama
jommega said:
please somebody help please...my g1 t mobile freeze in g1 screen...i can't power+camera, power+volumen down, no bootloader screen nothing, only freeze in g1 tmobile screen...
when press action botton and power a blue led come on but nothing happend...
somebody can help me with any information
jtag pin outs...or somenthing to solve this problem..i come from panama
Click to expand...
Click to collapse
nothing you can do. its bricked. call tmo or get it replaced by whatever warranty you have
well im getting a replacement g1 and i wanna root it again but i dont wanna brick it and theres a post that is here on xda and its called
"how to root, flash recovery cyanogen, parition sd to fat , ext2 and 3 , how to flash radio nd spl and install jachero"
is this a good post?
Thanks guys this helped a lot wow its been almost 2 years so yea thanks a lot guys
Sent from my SGH-T959 using XDA App
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?
If you can not get into recovery or bootloader, just set down, yell, smack yourself in your head and then take it back to the shop for another one cause you my friend BRICKED your phone. Another phone bites the dust, don't feel to bad I have done it before too
any idea how it happened? so i can avoid doing it again later?
Did you have a pvt board? If so then you are just a small statistical error. I have bricked a phohne before that have a pvt board, newest radio, all the requirements for it to work ,and the phone still bricked ,but it was around the release of cupcake so i told my friend to call tmobile and tell them he got an ota update and his phone wouldn't get passed the g1 screen, and they sent him another and the new spl flashed just fine on it
Not sure cause you said that the newest radio was already on there which would be the usual suspect, when you say it was already there do you mean before you downgraded to rc29 if so when you downgrade it also downgrades the radio and you have to flash it back on
not sure about the board - im assuming there's no way to check now?
and as long as you can "prove" (or lie, really) that the phone broke on its own, theres no limit as to how many replacements you can get, right?
...It downgrades the radio too?
well, theres my problem.
Anyway, thanks for the quick help guys
Yes it overwrites everything except a custom splash image but hey now you know, I would say that is what got you, when you get your new phone go into the bootloader and the first peice of info will say it is either a pvt or dvt board
If you just got your g1, chances are it did not ship with the latest update, none of the 3 I got like 2 months ago did so just say it was upgrading a ota update and froze and they will give you another one
So i had a blast last night at the party till i spilled beer on my phone......pulled out the batt and all that, few hours later after it dried out i powered it back up no problems but home home and green button aint working along with w e r 6 7 0 buttons so this morning i decided to do a system rest to see what it would do. So it did it took me into recovery only 1 problem i cant do anything since my home button isn't working....so i restarted and now i get a bootloop on the hero screen....
So i was wondering what to do now? i got insurance on the phone and i didn't spill that much beer on so i didn't flood the back where the white sticker is that changes color so will i able to exchange it as hardware defect so i dont have to pay deductible?
you should be able to get into recovery by running
adb shell reboot recovery
while the device is plugged in on USB, and you're in the SDK folder...
how do i brick it so it doesnt go past G1 screen i dont want them see Hero boot screen =/
Install RA-recovery 1.2.1 it uses call instead of home. To brick it flash an old radio over 1.33.2005 spl and you are good to go.
If you plan to blame a HW defect flash it back to stock, otherwise brick it & blame an OTA update.
gurnted said:
Install RA-recovery 1.2.1 it uses call instead of home. To brick it flash an old radio over 1.33.2005 spl and you are good to go.
If you plan to blame a HW defect flash it back to stock, otherwise brick it & blame an OTA update.
Click to expand...
Click to collapse
sweet but can u give me step by step direction cuz i cant get past hero screen cuz that's where its loops and i cant get into recovery, cuz that's where its loops...do i need to do adb or w/e its called? cuz i have no clue how to do it....
One thing you could do, is grab the RC29 US or RC7 UK update and place that on your SD cards root as DREAIMG.nbh. Boot in to the SPL (home+camera) and flash it. That update contains the 1.1 radio, the one which isn't compatible with 1.33.2005 SPL. As soon as it flashes the radio it should brick it.
Download the NBH
Place it on the root of you SD card as DREAIMG.nbh
boot in the the SPL (Power+Camera)
Flash it!
Hi,
I got a G1 Root/mod with DREAIMG-RC29, it was working with all functions, then I was trying to put SuperD 1.8
As did this:
1.Flash Radio (2.22.19.26I Baseband Version: 62.50S.20.17H_2.22.19.26I)
2.Flash SPL (1.33.2005)
agreed this tutorial forum.xda-developers.com/showthread.php?t=613809
3. Then I format my 8Gb midroSd as quoted in (androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/)
4. when I was flashing the new rom(SuperD18-blk), I did it as usual: change name from "SuperD18-blk.zip" to "update.zip", power off, power+home, alt+w, alt+s.
5. An error came up, something like error in line 59, something with E:/ bla bla, or something, i didn't read it 'cuz suddenly the phone restart itself.
After this I can't go to console or recovery mode.
I tried:
-Home+power to go to recovery mode.
-Home+camera button with RC29 on re-formated FAT32 SD card.
-Go to recovery trough abdshell, but my computer doesn't recognize the device so is not possible to get into the phone via PC.
Now the G1 is in the same situation: T-mobile G1 screen, so, I want to know if there is something that I can do to recover this or, maybe other way to roll back to RC29.
I'll appreciate any help, is sad to get stucked between the heaven and hell!!!!!!! The bad thing is that I don't got any log!!!
Cheers..... Alecks
Use fastboot with an old nandroid backup
RC29 includes an old radio image not compatible with 1.33.2005 SPL. If you had 1.33.2005 on the phone and reflashed RC29 when your update failed, the phone is most likely bricked.
dude most likely you are in deep dookey although there is probably still a chance if you can see the Tmobile G1 Screen.
dont be too scared just....dig a hole in the ground...just in case lol jk
Macrophage001 said:
dude most likely you are in deep dookey although there is probably still a chance if you can see the Tmobile G1 Screen.
dont be too scared just....dig a hole in the ground...just in case lol jk
Click to expand...
Click to collapse
Wrong, if all he can see is the G1 screen, he is bricked.
Welcome to the " I Bricked my G1 Club"
Say hello to your brand spanking new paper weight, pretty ain't it?
Tis a harsh world in which we live.
Seems to be a hopeless case!!!!
I will keep working on the G1, earning money for the nexus maybe!!!!
JAguirre1231 said:
Wrong, if all he can see is the G1 screen, he is bricked.
Click to expand...
Click to collapse
Is there any way to push the files into the phone with Eclipse? I got it even SDK, but I don't know how to do it exactly. The main issue is that the phone is not recognized by my PC currently, I think I have to perform some steps.. any idea?
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