hi
i flashed my htc dream with the new rogers rom update. i then rooted it using the 1-click-method, and confirmed by running "adb root". I then flashed hardspl and now when i reboot i am stuck at the rogers boot-up screen. trying to boot with camera+power, home+power or back+power has no effect. i have to pull the battery to turn it off. also, when plugged in with usb there is no response.
bricked or something else i can do?
if you have no access to spl or recovery then it is indeed a brick.
Fingerlickin said:
if you have no access to spl or recovery then it is indeed a brick.
Click to expand...
Click to collapse
thanks for your response. i read in your sticky that after spl upgrade it can take up to 15 minutes to boot, so now i am waiting and hoping, somehow it will come back to life (about 5 mins left)
update: 15 minutes gone by and still stuck
it will take up to 15 mins to do a normal boot but not if you hold camera+power. holding camera sends you straight to the spl. If it doesn't do that then there's nothing you can do. Can you provide a link to the spl you downloaded?
Fingerlickin said:
it will take up to 15 mins to do a normal boot but not if you hold camera+power. holding camera sends you straight to the spl. If it doesn't do that then there's nothing you can do. Can you provide a link to the spl you downloaded?
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream_Bootloader
http://forum.xda-developers.com/attachment.php?attachmentid=142426&d=1230965195
did you flash the recovery first?
Fingerlickin said:
did you flash the recovery first?
Click to expand...
Click to collapse
yes i think i did, through that 1-click app
hmm I've never used the one-click app nor have I even looked into what it does. David1171 can probably help us there. He should be on in a little bit.
Fingerlickin said:
hmm I've never used the one-click app nor have I even looked into what it does. David1171 can probably help us there. He should be on in a little bit.
Click to expand...
Click to collapse
ok thanks for your help
I guess I should mention, we are waiting for david1171 to determine how your phone got bricked so it doesn't happen again. The phone is actually a brick if Home+Power or Camera+Power doesn't work.
Fingerlickin said:
I guess I should mention, we are waiting for david1171 to determine how your phone got bricked so it doesn't happen again. The phone is actually a brick if Home+Power or Camera+Power doesn't work.
Click to expand...
Click to collapse
ok so it probably cant be fixed then. i will try and return it to Rogers hopefully they will replace it.
that new Rogers rom had a new radio version. im new to android so i guess this is a lesson learned the hard way.
Same thing here.
I think I'm in the same boat as you. Waiting on the Rogers splash screen with nothing happening. Still have access to the home/power command to access recovery mode but can't do much past that. Any help would be appreciated.
Thanks!
hjlow said:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream_Bootloader
http://forum.xda-developers.com/attachment.php?attachmentid=142426&d=1230965195
Click to expand...
Click to collapse
is this spl the same as 1.33.2005? before i try and screw another phone up
hjlow said:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream_Bootloader
http://forum.xda-developers.com/attachment.php?attachmentid=142426&d=1230965195
Click to expand...
Click to collapse
i just realised this is known as hard-spl and is not the same as the 2005 spl, so i might have flashed the wrong spl the first time? can anyone conform before I try 2005 from haykuro's thread?
hjlow said:
i just realised this is known as hard-spl and is not the same as the 2005 spl, so i might have flashed the wrong spl the first time? can anyone conform before I try 2005 from haykuro's thread?
Click to expand...
Click to collapse
hard spl is not the same as the 2005 spl. you need the haykuro spl.
make sure you read the thread "rogers, heres your real root"
that way you get a better understanding of the phone. it seems as though rogers and the g1 are 2 completely different animals
EDIT: heres another link also
http://forum.xda-developers.com/showthread.php?t=558301
Related
So I've been running Cyanogen's latest for quite a while now, with no problems that aren't systematic to whatever version he's just come out with. I decided to try something else just for fun, so I tried flashing JAC's and Drizzy's Hero ROMs. And yes, I flashed the correct radio and spl prior to the ROM flash.
For some reason, neither will work. They both come up with some kind of error at a certain line, either 80 or 59, I believe. So, I restore my backup to Cyanogen, and I'm back in business no problem.
Anyone care to hazard a guess as to what's going on? Thanks.
nspbass
I had that issue before. Here is what I did:
Wipe + repartition(dont forget you need 3)
reupdate SPL -> used the OTA, the the hardSPL
that worked for me, give it a try and good luck
Yeah I would just say wipe everything, make sure you use parted to split your sdcard which should be class6 into fat32/ext2or3/linux-swap.
You need Haykuro's special SPL. If you don't have it you will get that error every time.
shaolinx said:
I had that issue before. Here is what I did:
Wipe + repartition(dont forget you need 3)
reupdate SPL -> used the OTA, the the hardSPL
that worked for me, give it a try and good luck
Click to expand...
Click to collapse
Diceman4 said:
You need Haykuro's special SPL. If you don't have it you will get that error every time.
Click to expand...
Click to collapse
Exactly, so how the hell did Shaolinx flash it with HardSPL?
AdrianK said:
Exactly, so how the hell did Shaolinx flash it with HardSPL?
Click to expand...
Click to collapse
I'm sure he's mistaken.
And to the OP can you tell us what spl you have (cam + power).
Here's what it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I assumed the HBOOT to refer to the SPL, which obviously isn't correct. So, I reflashed the SPL.
I think I did a bad thing. Phone won't boot to anything past the initial G1 screen. I thought this was only an issue if I had the incorrect radio. Thoughts?
nspbass
nspbass said:
Here's what it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I assumed the HBOOT to refer to the SPL, which obviously isn't correct. So, I reflashed the SPL.
I think I did a bad thing. Phone won't boot to anything past the initial G1 screen. I thought this was only an issue if I had the incorrect radio. Thoughts?
nspbass
Click to expand...
Click to collapse
I hate to break the news to you but that is not the correct radio...the newest radio is 2.22.19.26I
Looks like its time to call TMO and put on your lying cap...
Also just because it says HBOOT does not mean that it is Haykuros SPL. THe special SPL is 1.33.2005
nspbass said:
Here's what it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I assumed the HBOOT to refer to the SPL, which obviously isn't correct. So, I reflashed the SPL.
I think I did a bad thing. Phone won't boot to anything past the initial G1 screen. I thought this was only an issue if I had the incorrect radio. Thoughts?
nspbass
Click to expand...
Click to collapse
and you have the wrong radio since the new one is 2.22.19.26I
Diceman4 with your slightly faster connection
but basically tell them your got an update or something, and that when the phone rebooted that it would not pass the g1 screen. also make sure you sound as clueless as to what root or flashing or anything technical is.
Ok, before this was a problem, I downloaded and flashed the radio, then the SPL. Clearly, they didn't take for some reason.
Now, my question is this: what do I do now? I'm looking in the bricked phone threads, but I haven't found an answer yet. Any help? Thanks.
nspbass
david1171 said:
Diceman4 with your slightly faster connection
but basically tell them your got an update or something, and that when the phone rebooted that it would not pass the g1 screen. also make sure you sound as clueless as to what root or flashing or anything technical is.
Click to expand...
Click to collapse
I wouldnt even say you got an update, I would just say that the phone restarted on its own one day and then just froze at the G1 screen. Be sure to not use any terms like "flash" "bricked" "boot loop" or anything that makes it look like you know anything at all about phone hacking. David is right just make yourself sound as clueless as possible.
nspbass said:
Ok, before this was a problem, I downloaded and flashed the radio, then the SPL. Clearly, they didn't take for some reason.
Now, my question is this: what do I do now? I'm looking in the bricked phone threads, but I haven't found an answer yet. Any help? Thanks.
nspbass
Click to expand...
Click to collapse
There is no way to fix it, the board needs to be replaced. You need to call t-mobile, follow mine and David's instructions and try to get a new one under warrantee
nspbass said:
Ok, before this was a problem, I downloaded and flashed the radio, then the SPL. Clearly, they didn't take for some reason.
Now, my question is this: what do I do now? I'm looking in the bricked phone threads, but I haven't found an answer yet. Any help? Thanks.
nspbass
Click to expand...
Click to collapse
i assume you have a cyanogen recovery image with the trackball feature? if so, for the radio and spl flashes you have to do the keyboard commands to make it work, you can't use the trackball or recovery console to reboot. so you can't boot into recovery or bootloader? if you can't, you have a brick
Diceman4 said:
I wouldnt even say you got an update, I would just say that the phone restarted on its own one day and then just froze at the G1 screen. Be sure to not use any terms like "flash" "bricked" "boot loop" or anything that makes it look like you know anything at all about phone hacking. David is right just make yourself sound as clueless as possible.
Click to expand...
Click to collapse
Done! Should have the replacement by Tuesday. I'm a tard.
nspbass
shaolinx said:
I had that issue before. Here is what I did:
Wipe + repartition(dont forget you need 3)
reupdate SPL -> used the OTA, the the hardSPL
that worked for me, give it a try and good luck
Click to expand...
Click to collapse
You know that you can't install hero with hard spl right? For someone who has a site dedicated to Android you don't seem to have your **** straight - no offense. And he could have bricked his phone if he tried to do H's danger spl without having the correct radio. Be careful when you give advice, we don't need to HELP people brick there G1's.
Haha, that's what I get for assuming he had the right spl and radio when he said he did. But if you are getting G1 screen you aren't bricked, if you can get into bootloader(camera+power) you should be able to flash your way back in time then forward again. I guess it doesn't matter if you're already getting it replaced but I got my friends back when his was only loading to G1, a true brick wont turn on at all no matter what you press.
JoshHart said:
But if you are getting G1 screen you aren't bricked..
Click to expand...
Click to collapse
If you do brick you will get the G1 splash screen, just nothing else..
Huh, well I guess my friend got lucky that wasn't his problem. Learn something new every day.
JoshHart said:
Haha, that's what I get for assuming he had the right spl and radio when he said he did. But if you are getting G1 screen you aren't bricked, if you can get into bootloader(camera+power) you should be able to flash your way back in time then forward again. I guess it doesn't matter if you're already getting it replaced but I got my friends back when his was only loading to G1, a true brick wont turn on at all no matter what you press.
Click to expand...
Click to collapse
Check the brick threads and you will see that just cause you have the G1 screen doesn't mean you don't have a brick. Flashing the SPL before the Radio will brick your G1 and you will be stuck at the loading screen. That is really the only true bricks we are aware of yet, maybe your friend found another way to brick but if you do some studying you will see what I'm talking about.
I was running Super D 1.2, flashed to 1.4 earlier this week with no problems. Went to flash to 1.5.1 last night and had an issue.
When I rooted I used hardSPL and didn't touch the radio. To flash super D 1.5.1 I needed to get Haykuro's radio and Danger SPL.
I wasn't aware I needed the new radio first and that's where the problem started.
I put danger SPL and super D on my card, booted up in recovery (amon_ra's), did a nan backup, flashed danger, then tried to flash 1.5.1 and got this error:
e: can't symlink /system/xbin/bb/[
e: failure at line 59:
symlink /system/xbin/busybox SYSTEM:xbin/bb/[
Installation aborted
After I got the error, I hit reboot so I could put 2.22.19.26i radio on my phone, and bam, stuck on G1 splash screen no matter how I try to boot up.
It's my fault for not checking the radio, This is my second time flashing a new rom (I rooted my G1 a few weeks ago)
I took my sd out and put it on my comp, so I have access to my sd thru my comp. Is there anything I can put on there to try and boot up in recovery and fix this? I have a nan back up from last week and last night before I flashed anything.
thanks in advance
Like all the other post say, flash the radio before the spl. If you failed to read the instructions and can not boot into recovery or fastboot, you have a brick.
evilkorn said:
Like all the other post say, flash the radio before the spl. If you failed to read the instructions and can not boot into recovery or fastboot, you have a brick.
Click to expand...
Click to collapse
Just in time to get a nexus too. Yay, for timing!
hi,im new to this, so bear with me.if you had already updated your radio and spl before then you shouldnt do it again.i might be wrong,but once its updated you dont have to do it again.
fabman33 said:
hi,im new to this, so bear with me.if you had already updated your radio and spl before then you shouldnt do it again.i might be wrong,but once its updated you dont have to do it again.
Click to expand...
Click to collapse
No, you shouldn't have to, but did you check before (can't check now)? There have also been cases where you got a bad download or it didn't work right, this also causes bricks. And please don't be a jerk and blame haykuro for this, I know some people have
I guess I failed to follow instructions lol ...
So I can't put a previous rom or anything on my sd from my comp to try and boot into recovery?
fabman33 said:
,but once its updated you dont have to do it again.
Click to expand...
Click to collapse
http://bit.ly/5V0VMB
t0nnn said:
I guess I failed to follow instructions lol ...
So I can't put a previous rom or anything on my sd from my comp to try and boot into recovery?
Click to expand...
Click to collapse
Can you boot into recovery now?
Nah every time I try I just get stuck on the G1 screen
t0nnn said:
Nah every time I try I just get stuck on the G1 screen
Click to expand...
Click to collapse
Well, enjoy your brick. You can replace the mobo, or break into htc and take the machine they used to originally put android on it, connect it to your phone's jtag's and watch the magic. Of course the second option comes with heavy fines, lawsuits, and jail time. Or you could buy a new phone
Nice, i'm an idiot.
Can I send it to HTC to get fixed?
t0nnn said:
Nice, i'm an idiot.
Can I send it to HTC to get fixed?
Click to expand...
Click to collapse
No you can't, you broke the warranty by rooting in the first place :/
So, buy a new phone
bah! ...this sucks.
It be nice if they offered a service to fix them, for a charge of course.
Before I rooted I sent the phone to them to get some minor stuff fixed under warranty (which it was), but to be covered under warranty they said they had to make sure the damage wasn't user caused and the phone didn't have any aftermarket roms on it.
Guess i'll be shopping for a new one
t0nnn said:
bah! ...this sucks.
It be nice if they offered a service to fix them, for a charge of course.
Before I rooted I sent the phone to them to get some minor stuff fixed under warranty (which it was), but to be covered under warranty they said they had to make sure the damage wasn't user caused and the phone didn't have any aftermarket roms on it.
Guess i'll be shopping for a new one
Click to expand...
Click to collapse
No they do offer it for a charge, a $400 one
what? Do they cup the balls and give you a milkshake for that too?
t0nnn said:
what? Do they cup the balls and give you a milkshake for that too?
Click to expand...
Click to collapse
No they send you a new phone
t0nnn said:
what? Do they cup the balls and give you a milkshake for that too?
Click to expand...
Click to collapse
On special occasions they do.
So you have a bricked phone! Care to donate it to the 'i wanna play with the motherboard' charity? Lol
just a stab in the dark, can you get into recovery with the USB cable connected / or a wall charger plugged in? (Hold home and long press power)
How long should I hold it? I just tried connecting via usb and home+power for about a minute with no luck.
Should it be home+power, but only hold power for a while? And how long?
Started to root the phone went back to 1.5, worked fine, applied FlashRec.apk and Amon Ra’s Recovery Image installed all that correctly worked fine. Went to install a new radio and spl and applied spl and when i go to start the phone it gets stuck at the G1 boot screen. Tried to book into recovery mode nothing happens , tried to hard & soft reset nothing happens. Phone just stays stuck at the G1 left it on for an hour and still nothing. Please help in any way or ask for more info if need.
Thanks in advance.
if you flashed the danger spl before flashing the new radio, your phone got permanent brick and cannot be solved without JTAG or changing the motherboard.
OK- I have the same problem, except I flashed the wrong radio.
(I thought I needed to update it for a different ROM, but.)
No fastboot, no recovery-- If I hold down the trackball, the screen wont come on, but the blue LED does. Is that useful to me at all??
Can JTAG help me? or is there another way?
I was reading about mtty-- but i'm not sure if that'll work for my G1.
Anything to unbrick this--- I really need my phone for finals week which started to-day.
JTAG is your only option.
techn0crat said:
Can JTAG help me?
Click to expand...
Click to collapse
Yes
techn0crat said:
or is there another way?
Click to expand...
Click to collapse
No.. at least none known yet
techn0crat said:
I was reading about mtty-- but i'm not sure if that'll work for my G1.
Click to expand...
Click to collapse
MTTY is just a program to talk to the serial port; it is actually part of the JTAG solution as well .. but as mentioned it will not help you at this point in time.
techn0crat said:
Anything to unbrick this--- I really need my phone for finals week which started to-day.
Click to expand...
Click to collapse
JTAG.. but unless you live near me or one of the very very few others who are set up for jtag hacks.. and that person is confident enough not to make the main board of the phone one big solder blob [I am but I'm not sure if some of the others I've heard poke JTAG are as confident].. it will take you a large chunk of time to learn what is needed to make it work.. or longer than the finals in the mail.
Thus I recommend.. get a cheap phone at the stand at the mall.. and pass your finals before worrying about the brick.
Since everyone who has caused a brick has either (1) not properly followed the directions and warnings.. or (2) did something in haste missing an important step; it will be no good to race it together during finals.
this dream was sent to my friend as a replacement
never used
he gave it to me sayingit wont boot
it gets into fastboot
it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
so i formatted his sdcard, got the DREAIMG.nbh put it on his sdcard, entered into fastboot, and it ran the install (rainbow screen) nothing was happening from there before i copied the DREAIMG.nbh to it, so at least this installed successfully)
then i rebooted (call-menu-power at same time) and still stuck at G1 screen after twenty minutes...whats happening here, anybody?
tnpapadakos said:
then i rebooted (call-menu-power at same time) and still stuck at G1 screen after twenty minutes...whats happening here, anybody?
Click to expand...
Click to collapse
Odd, the nbh files usually flash a full system.. thus while they might leave you with a rom you don't wish to have they usually will boot afterwards. You did let it fully flash all the partitions correct?
What nbh did you find/flash?
And. Can you still enter the spl or recovery.
ezterry said:
Odd, the nbh files usually flash a full system.. thus while they might leave you with a rom you don't wish to have they usually will boot afterwards. You did let it fully flash all the partitions correct?
What nbh did you find/flash?
And. Can you still enter the spl or recovery.
Click to expand...
Click to collapse
RC29 from the cm wiki, flashed successfully, nothing but fastboot screen, no boot, no recovery boot
weird
tnpapadakos said:
RC29 from the cm wiki, flashed successfully, nothing but fastboot screen, no boot, no recovery boot
weird
Click to expand...
Click to collapse
lol, wtf? wait... don't some phones need a goldcard for this?
r3s-rt said:
lol, wtf? wait... don't some phones need a goldcard for this?
Click to expand...
Click to collapse
yeah i dont know, all i know is i can ONLY getinto the bootloader, which is the ORIGINAL bootloader (0.95.0000)
what can i do with this thing?
what do i flash to it (cause it aint the RC29 DREAIMG.nbh)?
i refuse to lose
well only bootloader means nothing. you cold be getting a bad .nbh and the recovery partition could have something nasty on it. both of those not working doesn't automatically make it a brick. a working bootloader says everything is ok.
set up fastboot and fastboot a new recovery image.
then see if your recovery works. next time i don't respond, feel free to pm me again, lol. i really have a hard time keeping up with where i post.
of course: you can also fastboot a new spl:
http://code.google.com/p/android-roms/downloads/list?q=label:SPL
I recommend:
EngBootloader_v2_NoSigCheck.zip
That way you don't have to mess with that nasty danger spl and then you actually will be bricked.
hi,
my friend tried to root his g1 and somehow he got it stuck on the bootloader screen. It just stays there and does nothing.
I have no clue what to do and he let me have the phone.
I was just wondering if someone can tell me what to put onto my sd card to get it up and running. thanks so much!
hi there hope this helps follow this guide and it will help. hope all goes well.
http://forum.xda-developers.com/showthread.php?t=463779
Thank you, i will check it out.
your welcome. anymore help just ask. there's a lot of people here on XDA that would be gladly to help out. Some of them have great experience with the G1 and many others android phones. if that file don't work for you, this one will truly work its the one i use if i get into any trouble like your self, i been there. sometimes its stays on booting and this don't work i use this one.
http://www.megaupload.com/?d=EMY1HIVU and just follow the same direction as the last site i gave you.
For some reason i cant get into boot loader mode... any ideas?
did you press camera button and power button just like that. fist step camera button second step power button at same time. but before you do this phone needs to be off to get into boot loader mode. you need to place the image on the root of the sdcard thats in no folder at all, in the root of the sdcard.
What i did is i pulled out the battery, put the sd card in and then put the battery back in. Next I held down the camera key and then I pushed the power button. I have not let go.
sould i let go next time?
this is what you suppost to follow http://www.youtube.com/watch?v=ckbsFRnVciE . tell me something can your phone power on the g1 boot screen. can you tried for me power and home and tell me what you see. thanks.
It will not do anything. it is just stuck on the g1 screen.
I asked my friend what he used and he said Anon recovery rom and hard spl
probably the phone is bricked. write every single step you remember you took on trying to root your phone maybe i can get something out from there. its hard to brick one of this phones. to use amon recovery and hard spl your phone need to be downgraded with rc29 by using the file in the website i posted.
rhonal89 said:
probably the phone is bricked. write every single step you remember you took on trying to root your phone maybe i can get something out from there. its hard to brick one of this phones. to use amon recovery and hard spl your phone need to be downgraded with rc29 by using the file in the website i posted.
Click to expand...
Click to collapse
He said he did not downgrade it. he went straight to the spl and this is what happened.
he needed to downgrade the phone from stock before doing those steps. it aint that easy. probably he bricked the phone somehow.
enferrari said:
He said he did not downgrade it. he went straight to the spl and this is what happened.
Click to expand...
Click to collapse
He could not have flashed the spl straight onto a stock phone.. He's leaving something out, probably in the full knowledge that he did something stupid.
Anyway, if you can't get into bootloader with cam+power of recovery with home+power, it's a brick. JTAG it if you're comfortable with that or if not, sell it to someone who is.
then mines possibly bricked! maaan this is such BS. i accidentally installed the wrong recovery image, then figured I redo everything again. I got it working again, downgraded to RC29 and flashed Amon Ra 1.7.0 image. After that I got too excited, I went straight ahead and flashed hard spl and complete Eclair rom right away. Then poof, stuck on g1 screen. Still is now, possibly brick right?
iLOSER said:
then mines possibly bricked! maaan this is such BS. i accidentally installed the wrong recovery image, then figured I redo everything again. I got it working again, downgraded to RC29 and flashed Amon Ra 1.7.0 image. After that I got too excited, I went straight ahead and flashed hard spl and complete Eclair rom right away. Then poof, stuck on g1 screen. Still is now, possibly brick right?
Click to expand...
Click to collapse
HardSPL should not cause a brick with the RC29 radio, unless you are mistaking HardSPL 10.95.3000 for DeathSPL 1.33.2005.. which did you flash?
goldenarmZ said:
HardSPL should not cause a brick with the RC29 radio, unless you are mistaking HardSPL 10.95.3000 for DeathSPL 1.33.2005.. which did you flash?
Click to expand...
Click to collapse
I flashed with hardSPL. but isnt the steps i did correct? or did i skipped something? i haven't root my phone since last summer. so my brain was kinda fuzzy when i reroot my phone.
iLOSER said:
I flashed with hardSPL. but isnt the steps i did correct? or did i skipped something? i haven't root my phone since last summer. so my brain was kinda fuzzy when i reroot my phone.
Click to expand...
Click to collapse
You should've updated the radio before trying to run eclair, but that wouldn't cause a brick. Can't you get to recovery or bootloader?
goldenarmZ said:
You should've updated the radio before trying to run eclair, but that wouldn't cause a brick. Can't you get to recovery or bootloader?
Click to expand...
Click to collapse
Before this happen I can, but now I'm stuck on the g1 screen. I left it on all night and nothing. I still can't get into recovery nor bootloader. Any other suggestions? So tired too of staying up all night reading trying to figure this out
I received a G1 from a friend, this isn't actually the first G1 i've rooted. I have one of my own, and I have done about 3 others without any problems what so ever.
I'm not exactly sure what went wrong. I had flashed the recovery, following the cyanogen wiki, and when I got to the flashing the Hard SPL part, i flashed it, (and the radio) and i restarted, and thats it. It just stays at the G1 screen.
No combination of keys work. Home + Power. Camera + Power. Nada.
From most of the threads I've found, I can almost say its a brick, but I just wanted to double check that theres nothing I can do (ADB?).
Thanks!
red.Wood said:
I received a G1 from a friend, this isn't actually the first G1 i've rooted. I have one of my own, and I have done about 3 others without any problems what so ever.
I'm not exactly sure what went wrong. I had flashed the recovery, following the cyanogen wiki, and when I got to the flashing the Hard SPL part, i flashed it, (and the radio) and i restarted, and thats it. It just stays at the G1 screen.
No combination of keys work. Home + Power. Camera + Power. Nada.
From most of the threads I've found, I can almost say its a brick, but I just wanted to double check that theres nothing I can do (ADB?).
Thanks!
Click to expand...
Click to collapse
I know how frustrated you must be that actually happend to me before idk if the same thing caused it but try to do the whole process all over if that doesnt work i sudgest looking for how to unbrick your phone
jamal717 said:
I know how frustrated you must be that actually happend to me before idk if the same thing caused it but try to do the whole process all over if that doesnt work i sudgest looking for how to unbrick your phone
Click to expand...
Click to collapse
Did you even understand what happened? How's and what is he supposed to do over again if he can't get into bootloader or recovery?
OP, Sorry to say, you have a brick.
borodin1 said:
Did you even understand what happened? How's and what is he supposed to do over again if he can't get into bootloader or recovery?
OP, Sorry to say, you have a brick.
Click to expand...
Click to collapse
looks like i've done similar to the OP --> flashed a non EBI1/32A radio.
Now it just hangs on the HTC Dream splash screen.
Yeah, looks like were **** out luck lol. I ended up buying a Magic Slide. Whats weird is that i flashed the radio B4 the spl.
red.Wood said:
Yeah, looks like were **** out luck lol. I ended up buying a Magic Slide. Whats weird is that i flashed the radio B4 the spl.
Click to expand...
Click to collapse
sent it back to the SP with a story of how during the flash the computer crashed. here's to hoping.
got the phone back after being charged about $25 to repair.
anyway this time i read the instructions properly. left the radio on 3.22.20.17 and then installed the one click root and flashrec apps. I then rooted the phone, download Anon-RA's recovery image with flashrec. I then followed the cyanogen wiki and froyo is now running on it.
red.Wood said:
I received a G1 from a friend, this isn't actually the first G1 i've rooted. I have one of my own, and I have done about 3 others without any problems what so ever.
I'm not exactly sure what went wrong. I had flashed the recovery, following the cyanogen wiki, and when I got to the flashing the Hard SPL part, i flashed it, (and the radio) and i restarted, and thats it. It just stays at the G1 screen.
No combination of keys work. Home + Power. Camera + Power. Nada.
From most of the threads I've found, I can almost say its a brick, but I just wanted to double check that theres nothing I can do (ADB?).
Thanks!
Click to expand...
Click to collapse
borodin1 said:
Did you even understand what happened? How's and what is he supposed to do over again if he can't get into bootloader or recovery?
OP, Sorry to say, you have a brick.
Click to expand...
Click to collapse
It definitely sounds like you have a hard brick. I think the only way to fix your phone is to JTAG JTAG it. Which I have no idea how that works or how to reload the software on your phone.
Go to this thread, this explains all:
http://forum.xda-developers.com/showthread.php?t=591048