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
Related
heres the scenario i did, i basically did hard spl on my device, it rebooted itself and then nothing is happening further from there. Device boots up all i see is ROGERS and thats it. pressing power and camera button doesnt do anything, pressing power and home button also doesnt do anything. Please help.
did you put the 1.33.2005 spl from the rogers heres your real root thread of the hard spl floating around on all the other rooting threads?
yes thats true i used one of the hard spl from here....but im running out of luck....need assistance please
if your phone will not boot into either bootloader (camera and power) or recovery (home and power) then you have a brick, i hope your phone is still under warranty
I dont know if its still under warranty, coz i didnt get this phone from rogers, i bought it off from someone.......it was a brand new one....so im hoping for some good knews from somewere....
wordlife said:
I dont know if its still under warranty, coz i didnt get this phone from rogers, i bought it off from someone.......it was a brand new one....so im hoping for some good knews from somewere....
Click to expand...
Click to collapse
sorry... but it won't boot using those keypresses then it is a brick...
when you have it plugged up to a computer does it make any kind of sound when the boot screen is on?
it doesnt makes any sound, but somethings does comes in device manager but nothing is listed in there.....i have a feeling its bricked but hoping there should be some way to get in n fix this
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!
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
so i have a bricked tmobile g1 on my hands. my friend tried to flash haykuro's spl and did it wrong so now the phone is effed it does not say "tmobile G1" at the bootup screen, it says HTC and stays there. trying to get to bootloader and recovery mode is impossible because the phone will not go into those modes. the spl is a "danger spl". is there any possible way to fix this?
as of right now...no there is no way to fix this...
sorry
if ur phone is under warranty just call tmobile and say ur phone would not turn on after a backup app asked u to restart ur phone
worked for me with the same problem
flashed the spl before the radio and bricked. called them and told them an app caused it and got my device within a week :-D
Ask for a replacement, and lie about what happened
But yeah, your current G1 is bricked if you cannot access recovery or bootloader.
It's a bad sign that it says htc and not g1 on the boot screen. If they see that then they might charge you because it's obvious you flashed the wrong spl for the phone.
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