Related
I have the Rogers HTC Dream which I bricked this morning.
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
1) Take out the battery and unplug the USB cable and wait 20 seconds
2) plug in the USB cable
3) The second you insert the battery your phone will automatically turn itself on. Therefore hold the camera button down while putting in the battery.
4) The phone should start up (again a black screen + Rogers logo) and you should see a red box in the top left corner saying "FAST USB"
5) The phone appears frozen, but now you can use ADP to send it a recovery.img.
Code:
fastboot boot recovery.img
For me I installed the recovery.img from "Haykuro's initial root kit" available in step 4 of this guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
6) After the fastboot command is finished your phone should automatically reset, and enter the Cyanogen recovery menu.
7) Now install the custom ROM as before
EDIT: After following these steps, I can now start my phone using CAMERA + POWER to get into the fastboot menu just like before I bricked my phone.
EDIT #2: I am currently running my phone with the cyanogen 4.1.999 ROM, so everything worked out for me in the end. I should probably mention that I did not "brick" my phone by flashing a new SPL while still running an older radio.img, so Im not sure how far this method will get some of you.
I'm afraid that your device was NOT BRICKED. You just had an incompatible or defective system image and didn't know how to use the bootloader.
THIS WILL NOT WORK on a device that is actually bricked.
martin_secretary said:
I have the Rogers HTC Dream which I bricked this morning.
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
1) Take out the battery and unplug the USB cable and wait 20 seconds
2) plug in the USB cable
3) The second you insert the battery your phone will automatically turn itself on. Therefore hold the camera button down while putting in the battery.
4) The phone should start up and you should see a red box in the top left corner saying "FAST USB"
5) The phone appears frozen, but now you can use ADP to send it a recovery.img.
Code:
fastboot boot recovery.img
For me I installed the recovery.img from "Haykuro's initial root kit" available in step 4 of this guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
6) After the fastboot command is finished your phone should automatically reset, and enter the Cyanogen recovery menu.
7)????
I am stuck here, Im still not sure how to proceed to fix my phone, but I know this will help others get to this point, and maybe someone with more expertise can point out where to move on from here.
EDIT: After following these steps, I can now start my phone using CAMERA + POWER to get into the fastboot menu just like before I bricked my phone.
Click to expand...
Click to collapse
Perhaps you are right and it was not "truly bricked", but it was in a state where home+power and camera+power did nothing.
Anyone on these forums that would describe this problem would automatically be told they have a new paperweight. Im sure many people just have the same problem as me.
From a POWEROFF state, press and hole HOME (for recovery) or BACK (for fastboot), then press the power button while continuing to hold the HOME or BACK button. That is all there is to it. No magic.
lbcoder said:
I'm afraid that your device was NOT BRICKED. You just had an incompatible or defective system image and didn't know how to use the bootloader.
THIS WILL NOT WORK on a device that is actually bricked.
Click to expand...
Click to collapse
have you personally tried this?
lbcoder said:
From a POWEROFF state, press and hole HOME (for recovery) or BACK (for fastboot), then press the power button while continuing to hold the HOME or BACK button. That is all there is to it. No magic.
Click to expand...
Click to collapse
No, that is not magic, but what is really impressive is that in the original post it is stated that
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
Click to expand...
Click to collapse
, and if the OP was actually able to find a way around this, it is the first time I have heard. Since registering, I have read numerous posts on XDA stating that if you cannot get to recovery by home+power and cannot get to fastboot via home+camera, then your phone is "probably bricked". I have yet to read one post with a solution to this situation (not to say they do not exist, just that they are not easy to find if they do exist). I think the OP found something that could be quite useful for many people that find themselves in this situation (such as after flashing the wrong radio for hero).
Now having said that, I must also say that your phone was not bricked. If it were bricked, you could not have made it this far. Thus, it either the case that this was a fluke, or the (quite wonderful, but usually with a low probability) case that you stumbled upon something new, and the concept of a "bricked G1" will need to be redefined.
We need more people in this situation to try this method, that will be the only way to really know what this is.
cloverdale said:
No, that is not magic, but what is really impressive is that in the original post it is stated that , and if the OP was actually able to find a way around this, it is the first time I have heard. Since registering, I have read numerous posts on XDA stating that if you cannot get to recovery by home+power and cannot get to fastboot via home+camera, then your phone is "probably bricked". I have yet to read one post with a solution to this situation (not to say they do not exist, just that they are not easy to find if they do exist). I think the OP found something that could be quite useful for many people that find themselves in this situation (such as after flashing the wrong radio for hero).
Now having said that, I must also say that your phone was not bricked. If it were bricked, you could not have made it this far. Thus, it either the case that this was a fluke, or the (quite wonderful, but usually with a low probability) case that you stumbled upon something new, and the concept of a "bricked G1" will need to be redefined.
We need more people in this situation to try this method, that will be the only way to really know what this is.
Click to expand...
Click to collapse
As I said, from a POWER OFF STATE.
And no, you do NOT hold home+power, you hold HOME, then PRESS AND RELEASE power while continuing to hold HOME.
He didn't get by anything. He simply didn't push the buttons properly (i.e. pressed them *too late* or while the device was STILL POWERED ON.
lbcoder said:
As I said, from a POWER OFF STATE.
And no, you do NOT hold home+power, you hold HOME, then PRESS AND RELEASE power while continuing to hold HOME.
He didn't get by anything. He simply didn't push the buttons properly (i.e. pressed them *too late* or while the device was STILL POWERED ON.
Click to expand...
Click to collapse
Why are you so sure about yourself about what buttons I pressed? I booted into recovery mode and fastboot mode MANY times before I "bricked" my phone, so i know how to press the buttons....
yo lbcoder i hold home+power at the same time for a LONG time and it still goes to recovery. Same with camera + power. As long as you hold home before you hold/press power you're good to go. We need more people to tryout this method.
I wonder why lbcoder is so sure of what hes saying....hes been wrong a lot of times in his previous postings...
I got a solution for this. How bout the OP or someone else actually brick there phone and try this method. If they get it back working then hey theres a solution but if not then you know it really wasn't a brick. So who wants a brick.
Plus I would like to know what was the initial problem to make the OP think he had a brick.
B-man007 said:
I wonder why lbcoder is so sure of what hes saying....hes been wrong a lot of times in his previous postings...
Click to expand...
Click to collapse
If you're going to make such an absurd statement, you better damn well be prepared to back it up.
But since you can't, I hereby nullify your statement and reserve the right to do so for anything you ever state.
@martin:
How can I be sure? Because after you tried several times it eventually worked. You didn't do anything differently the last time except pull the battery, which will have no effect except that you can be certain that you are starting from a fully powered off state. That being the difference proves that one of the following things happened on every one of your previous attempts;
1) You pushed the button too late in the boot sequence (everybody's done this a few times, sometimes several times in a row),
2) The device was never actually powered off. Yes, it can have the appearance of being off without actually being off.
As for other's trying this with their bricks, certainly it might help a very few people out, but no, this is not a magical fix for an IPL CRASH. If the SPL is simply not compatible with the IPL, then no matter what you try, the IPL will never be able to start the SPL. And yes, you MUST start the SPL since that is where the bootloader is, and the home or back or no button signals the bootloader on which way to boot (multiboot). It can go into fastboot (payload within SPL), recovery (recovery partition), normal (boot partition), etc.
lbcoder said:
If you're going to make such an absurd statement, you better damn well be prepared to back it up.
But since you can't, I hereby nullify your statement and reserve the right to do so for anything you ever state.
@martin:
How can I be sure? Because after you tried several times it eventually worked. You didn't do anything differently the last time except pull the battery, which will have no effect except that you can be certain that you are starting from a fully powered off state. That being the difference proves that one of the following things happened on every one of your previous attempts;
1) You pushed the button too late in the boot sequence (everybody's done this a few times, sometimes several times in a row),
2) The device was never actually powered off. Yes, it can have the appearance of being off without actually being off.
As for other's trying this with their bricks, certainly it might help a very few people out, but no, this is not a magical fix for an IPL CRASH. If the SPL is simply not compatible with the IPL, then no matter what you try, the IPL will never be able to start the SPL. And yes, you MUST start the SPL since that is where the bootloader is, and the home or back or no button signals the bootloader on which way to boot (multiboot). It can go into fastboot (payload within SPL), recovery (recovery partition), normal (boot partition), etc.
Click to expand...
Click to collapse
I've updated my post to state that I did not brick my phone by using an incompatible SPL. However I am saying my phone was in the state where I could not access fast boot or recovery mode.
Look through this thread: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
and see how many people say they can't access fastboot or recovery anymore....this is the same guide I followed and screwed up my phone. There is more than one way to brick your phone, and I think I found a way to unbrick it in this special case.
martin_secretary said:
I've updated my post to state that I did not brick my phone by using an incompatible SPL. However I am saying my phone was in the state where I could not access fast boot or recovery mode.
Look through this thread: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
and see how many people say they can't access fastboot or recovery anymore....this is the same guide I followed and screwed up my phone. There is more than one way to brick your phone, and I think I found a way to unbrick it in this special case.
Click to expand...
Click to collapse
Do you have any idea what proportion of "users" can't even press the "enter" button when told to?
And FYI: that thread talks about installing the deathspl (the one that usually makes your phone into a paperweight). Regardless of their statement that it is compatible, it is actually quite unknown/undocumented and therefore compatibility with it is NEVER certain.
The fact that you only THOUGHT you bricked your phone means that you are lucky. Lots of people have ACTUALLY bricked with that SPL.
lbcoder said:
If you're going to make such an absurd statement, you better damn well be prepared to back it up.
But since you can't, I hereby nullify your statement and reserve the right to do so for anything you ever state.
Click to expand...
Click to collapse
lbcoder said:
Why the app? winanything will BSOD just by looking at it.
Click to expand...
Click to collapse
I'm looking at windows right now...and it didnt bluescreen.....
Do you have any idea what proportion of "users" can't even press the "enter" button when told to?
Click to expand...
Click to collapse
Look at how many people use a rooted G1, then look at how many can't..... its a very low proportion. Just because you see some posts in which people complain about not being able to use their phone doesnt make it an accurate representation of "users"
Code:
The fact that you only THOUGHT you bricked your phone means that you are lucky. Lots of people have ACTUALLY bricked with that SPL.
ok, first off....hes using a rogers phones. The buttons are much easier to press than the g1. I highly doubt he would have messed up that many times. And if he couldn't access the SPL or Recovery, its effectively a brick for him. What does it matter how it happened if it did happen. a bad ipl/spl flash is not the only way to brick a phone (though its the most common and most documented) There are many factors to this "brick" that you may or may not know about
why the heck are you sitting here and arguing the definition of a brick. Hes trying to help people who have messed up their phone and giving them one more solution to try to fix their phone before spending money on replacing it. If it doesnt work, so be it. if it worked for even one person, its officially worthwhile for the post to be there.
there is no need to sit there criticizing someone whos trying to help by repeatedly posting the same thing over and over there. I think that your judging him because of his low post count. Martin has greater than adequate knowledge of the dream. but you wouldnt know that because anyone that doesn't have a post count > 100 "can't even press the 'enter' button when told to"
martin_secretary said:
I have the Rogers HTC Dream which I bricked this morning.
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
1) Take out the battery and unplug the USB cable and wait 20 seconds
2) plug in the USB cable
3) The second you insert the battery your phone will automatically turn itself on. Therefore hold the camera button down while putting in the battery.
4) The phone should start up (again a black screen + Rogers logo) and you should see a red box in the top left corner saying "FAST USB"
5) The phone appears frozen, but now you can use ADP to send it a recovery.img.
Code:
fastboot boot recovery.img
For me I installed the recovery.img from "Haykuro's initial root kit" available in step 4 of this guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
6) After the fastboot command is finished your phone should automatically reset, and enter the Cyanogen recovery menu.
7) Now install the custom ROM as before
EDIT: After following these steps, I can now start my phone using CAMERA + POWER to get into the fastboot menu just like before I bricked my phone.
EDIT #2: I am currently running my phone with the cyanogen 4.1.999 ROM, so everything worked out for me in the end. I should probably mention that I did not "brick" my phone by flashing a new SPL while still running an older radio.img, so Im not sure how far this method will get some of you.
Click to expand...
Click to collapse
i have G1 its stck on G1 screen ... i try to do as you did but wont work at all ???
i cant boot or flashe from sd card ...
any help ?
B-man007 said:
I'm looking at windows right now...and it didnt bluescreen.....
Click to expand...
Click to collapse
Are you so absolutely dense that you don't know what a JOKE is?
Look at how many people use a rooted G1, then look at how many can't..... its a very low proportion. Just because you see some posts in which people complain about not being able to use their phone doesnt make it an accurate representation of "users"
Click to expand...
Click to collapse
I'm talking about users IN GENERAL. I.e. forget about phones, forget about root. Most users are (from the programmer's perspective) absolute MORONS who are barely able to breath on their own. Give a "rooted" phone to a NORMAL user (i.e. a teenage girl), do you expect them to be able to get anything extra out of it? How about trying to talk an average (that's *AVERAGE*, not a geek) teenage girl through the process of rooting her phone? You think that will go well? Definitely not.
ok, first off....hes using a rogers phones. The buttons are much easier to press than the g1.
Click to expand...
Click to collapse
That is absolutely not relevant in any way. If he is pressing the buttons WITH THE THING POWERED ON, then it won't work, regardless of how "easy" the buttons are to press.
I highly doubt he would have messed up that many times.
Click to expand...
Click to collapse
You are therefore judging him to be of equal technical aptitude to yourself. What do you base this on? The first rule of anything technical is to assume that your end users are complete morons. If they aren't, then so much the better, but you can't make that assumption.
And if he couldn't access the SPL or Recovery, its effectively a brick for him. What does it matter how it happened if it did happen. a bad ipl/spl flash is not the only way to brick a phone (though its the most common and most documented) There are many factors to this "brick" that you may or may not know about
Click to expand...
Click to collapse
Fact: If the device is not physically damaged, contains a compatible and valid IPL and a compatible and valid SPL, then it *must* boot up to SPL *as long as the correct procedure is followed*.
The ONLY possible ways to make the device non-functional beyond the possibility of correcting using standard procedure is to have physical damage, corrupt or incompatible IPL, or corrupt or incompatible SPL. There are no other possibilities.
why the heck are you sitting here and arguing the definition of a brick. Hes trying to help people who have messed up their phone and giving them one more solution to try to fix their phone before spending money on replacing it. If it doesnt work, so be it. if it worked for even one person, its officially worthwhile for the post to be there.
Click to expand...
Click to collapse
No, he is not providing any information that is not already available for anyone to try. He did nothing at all beyond standard procedure. In his first attempts, he clearly failed to follow standard procedure, in his final attempt, he successfully followed standard procedure and was able to access recovery. This thread is misleading as it offers a solution which, quite frankly, doesn't exist.
there is no need to sit there criticizing someone whos trying to help by repeatedly posting the same thing over and over there. I think that your judging him because of his low post count.
Click to expand...
Click to collapse
I post to correct. I post to inform against useless information.
Martin has greater than adequate knowledge of the dream.
Click to expand...
Click to collapse
Again, not to put him down, but HOW DO YOU KNOW?
but you wouldnt know that because anyone that doesn't have a post count > 100 "can't even press the 'enter' button when told to"
Click to expand...
Click to collapse
Back to basics. You can absolutely NOT assume that everyone else knows what YOU know. You *MUST* assume that they know NOTHING.
Post count? Tell me where you got the impression that I even bothered to look at his post count. I don't care about post count. If the post makes sense and introduced NEW INFORMATION, then the author is making a worthy contribution. If they are just repeating the same crap that *everybody already knows*, then it is a worthless or potentially damaging contribution.
Duh, my phone don't work. I tried and tried and it didn't work. And then finally I followed the directions and it worked.
lbcoder: I am currently a software programmer working for the top 5 biggest tech companies in North America. I am also currently doing my masters in Computer Engineering. Every post of yours has hinted that you think I'm a moron, and you've been very insulting and unhelpful on this message board.
I've pointed out to you many times I did NOT brick my phone by flashing an incorrect SPL. Yes we get it, if an incorrect SPL has been flashed then there is probably no possible way to recover the phone.
However I'm saying that I bricked my phone some other way, and for some reason you wont get that into your head. Im beginning to wonder who the real "moron" is here.
This thread is meant to try and help people whose phones are in the same state mine was. You're just being an ass and hijacking this thread.
P.S. I bet B-man007 has his doubts about whether this method actually works. Yet hes taking a wait-and-see approach, not a calleveryoneamoroncuzIthinkimright approach.
iyass said:
i have G1 its stck on G1 screen ... i try to do as you did but wont work at all ???
i cant boot or flashe from sd card ...
any help ?
Click to expand...
Click to collapse
How did you brick your phone? What guide did you follow, and what step did it fail at?
Ok.. So a friend of mine suddenly got a triangle with the exclamation mark picture on his phone. That's all it boots up to. So, he took it to T-mobile, they told him it's FUBAR, and sold him a new phone.
The fact that the thing boots to a recovery mode tells me that there's SOME way to un-FUBAR this phone. My friend is too technologically inadiquate to attempt to do any modifying, so I'm going to assume he was at whatever firmware level would hve been blasted out to T-mobile as of last Friday 01/15/2010.
If I boot the phone normally, it gives me the TriAngle. I pop open the keyboard and hit alt-L and the I get the Android System Recovery menu. at the bottom I get "E:CAn't open /cache/recovery/command"
I've spent all day bouncing around this forum, and many like it, downloaded all sorts of G1 fimwares trying to go back to RC29, RC28, 30, 33.. gah! The latest one I'm trying to update to is "signed-kila-ota-116143-prereq.TC4-RC19+RC28+RC29.zip" Which i rename to update.zip . I hit alt-L, select 'update from SD card' It goes through:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update package....
Installation aborted.
That's it... no more log than that.
I've done the Alt-W, and Alt-S.. wiped cache partition. I think playing around with the recent firmwares might be fun, but I'd like to get this bad boy reset back to factory defaults. I've read the forums here on how to do that.. but all of the procedures fail.
I can get Windows 7 to recognize the phone, but I cannot access the sd card while it is in the phone. I've been transfering data to it by taking the sdcard out, and putting it into a known good SD card reader. I've formatted the sdcard to FAT16, and FAT32 quick and not quick.
Seriously.. why is this so complicated? Now I need some serious digging assistance. Is there an interface that will allow me to directly talk to this phone via the USB cable? How can I force an firmware onto it? Clearly something is functional, or I would get no I/O. How can I get this silly thing back to where it was? I know this thread seems like a redundant one, but as far as I can tell, its not. The typical procedures posted here don't seem to work, but I'll be happy to run through any steps y'all suggest. I'll resign that it's been bricked if that's really whats happened.. but I'm not ready to throw this unit away yet.
Ask questions.. let me answer them. I know this team can get this phone working again.
Thanks y'all.
--Rob aka The Austin Slacker.
Have you tried the RC29 DREAIMG.nbh file?
http://forum.xda-developers.com/showpost.php?p=4593084&postcount=1
Roadmasta01 said:
Have you tried the RC29 DREAIMG.nbh file?
http://forum.xda-developers.com/showpost.php?p=4593084&postcount=1
Click to expand...
Click to collapse
bingo !
sounds like your friend tried to flash something he shouldn't have. or messed around with stuff he shouldn't.
as far as taking it to the store, and accepting their suggestion to "GIVE US YOUR MONEY!" that was a mistake.
the phone is likely fine, and maybe you'll buy it from him for cheap, then fix, resell/use.
good luck, should be easy.
The "press camera and power to get to bootloader" procedure. I've tried holding the Camera while pressing power over and over and all I get is the triangle. However if I press power and the "back" button (swooping arrow to the left), I'll get the bars screen, and a Gray screen telling me to press send to restore.... Which is all good, but there's no progress or any thing to indicate that i've done something by pressing the send button.(based on cell phone standards, I'm assuming "send" is the green "call" button.
Is this normal?
No yeah.. he gave me the G1.. its mine. I just need to fix the little bugger.. .. well.. then laugh at him
Ok.. one more day (well ok.. couple hours) of fiddling with this thing, and i'm begining to wonder if Microsoft was involved. I'm not able to get this poor G1 to do anything new. I tried using a different SD card, hoping perhaps the one I got with it was bad... no dice. camera + power doesn't do anything useful.
I can connect it to the PC.. but i can't see the data card that way. adb devices reads no output, so its not correctly attaching to the PC (tried Windows 7 32bit, and Windows XP 64bit).. There's gotta be a good way to force a known good image onto this silly thing.
Is it probable that the internal memory has gotten corrupt somehow? I know someone out there's got the golden suggestion, please do tell if you do. I'd really like to use this phone.
--Rob
If you can get into fast boot (the tri color screen) there are ways to flash it... try getting into your tri color, then plugging in the USB cable and see if it switches from Serial 0 to USB at the bottom, if so you are golden to flash using the fast boot method.
There are guides around on how exactly to do that, as well a couple places that you can download the official RUU that will do all the hard work for you!
gah.. nothing doing. I can hit Back and Home, and end up with the tri-color screen for about 1/5th of a second, then a gray screen saying:
This operation will delete all your personal data, and reset all settings to manufacturer default. Press Send to restore manufacturer default, or press other keys to cancel.
At this point, the unit is dead. I can remove the battery, and continue on my little quest.. but hitting *any* key at all (including the Send key) will not produce any sort of output. I've tried pressing Send one time, then setting the phone down for a full hour (watched a netflix show) nothing. I can't power it off either w/o removing the battery.
I would throw in the towel.. but from all the research i've been doing, it seems as if this one is behaving in a manner in which other forum users havne't posted. Maybe by continuing to try options and post results, a positive outcome will come out, and someone else who has a G1 behaving this way will have an easier time.
... or y'all can tell me that its toast and to bugger off.. ha ha.. either way.. I continue to google. If you can think of anything, please toss it out.
OH!.. tried an RUU.. found one called. RhodiumSPLRelocker Looks promising.. but can't see the device when attached to the PC... yeah.. guess the phone has to have a functioning OS before that will happen...
You would want a Dream RUU... I looked around a bit and couldn't find one. Maybe someone has a quick link?
Double check that your SD card is formatted FAT32 and see if you can get ADB to see it when on that greay screen.
I've formatted the SD card in FAT32 multiple times.. I even questioned if my Windows 7 32bit would do it, and formatted it on a laptop running XP 64bit. adb doesn't seem to see it ever.
I don't get why I can't get it into fast boot. I've been looking on ebay for dream G1s with broken screens.. heh.. I guess i'm preparing for the worst. really sad, becasue this G1 was actually pretty well taken care of. My friend didn't do anything he shouldn't. HE woke up one morning and it was like this. He lives out in the country.. so he gets pretty spotty signal. I'm wondering if T-Mobile didn't push out an update, and it got interrupted by signal loss.
By the by... I've been doing all this work w/o a SIM card. Does that matter?
austinslacker said:
(based on cell phone standards, I'm assuming "send" is the green "call" button.
Click to expand...
Click to collapse
its not the green send button -- its the red end button
see below extracted from http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
Load the DreaIMG.nbh File
1. Download the Original DreaIMG.nbh file:
http://www.megaupload.com/?d=XXSQ0T7W
2. If the file downloaded above downloads as a .Zip file, please unzip it first then put the DreamIMG.nbh file that is inside on the SD card, NOT in any folder. (If you did Section I the phone is off still, take out the memory card, put it in the MicroSD adapter and plug it into your computer to transfer the file over, since your G1 won’t turn on right now if you did Section I above. Otherwise if you did not need to do Section I above, then you can just put it on the SD card normally using the usb cable and the phone).
3. Turn the phone off if it is on.
4. Turn on the phone by holding the Camera button and the End key until the bootloader screen turns on.
5. Hit the End key to start the update. DO NOT INTERUPT THIS PROCESS.
6. Once it is done, hit the trackball to restart the phone. You now are on the stock firmware RC29
austinslacker said:
The "press camera and power to get to bootloader" procedure. I've tried holding the Camera while pressing power over and over and all I get is the triangle. However if I press power and the "back" button (swooping arrow to the left), I'll get the bars screen, and a Gray screen telling me to press send to restore.... Which is all good, but there's no progress or any thing to indicate that i've done something by pressing the send button.(based on cell phone standards, I'm assuming "send" is the green "call" button.
Is this normal?
No yeah.. he gave me the G1.. its mine. I just need to fix the little bugger.. .. well.. then laugh at him
Click to expand...
Click to collapse
You mention that you can access fastboot by pressing the back button while turning it on, isn't that how the hero gets into fastboot? maybe your friend tried flashing a rom that was meant for the hero. if you have access to fastboot you should be able to flash a new image from there, just place the image file in the root of your card and follow the fastboot instructions
Also if fastboot isn't doing it for you have you tried adb? if you don't know what that is look it up I've seen a couple guides on how to do it and they are really detailed.
Im having the same problem, Im stuck in the recover triangle of death. Ive done the alt+w and reboot, the RC29 DREAIMG.nbh , the update.zip, camera+power, I cant get the gray screen to pop. Nothing, its brickkkkeeeddddd, FUBAR. There has got to be someway I can reload this G1. I wasnt trying to root it or anything. I was bowling and then it triangled on me. Anyone have any ideas at all on how to fix it?
Triangle of Death
I'm from Brazil, I can't take it to t-mobile to fix...
when i tried to root my G1 did the downgrade perfectly, the screen was just as it was suposed to be.
But in the recovery mode boot, appeared this triangle with an exclamation...
what do i do now???? help plz!
deftoneage12 said:
Im having the same problem, Im stuck in the recover triangle of death. Ive done the alt+w and reboot, the RC29 DREAIMG.nbh , the update.zip, camera+power, I cant get the gray screen to pop. Nothing, its brickkkkeeeddddd, FUBAR. There has got to be someway I can reload this G1. I wasnt trying to root it or anything. I was bowling and then it triangled on me. Anyone have any ideas at all on how to fix it?
Click to expand...
Click to collapse
Any one have any ideas? hell ill pay someone to fix it for me
The only idea I have is make'ing an goldcard so your sure your phone accepts the update (dreaimg)... other than that...
Sent from my HTC Dream G1 using the XDA mobile application powered by Tapatalk
Any chance the home button is stuck? I'm not 100%, but I think if you were to hold home, camera and power, the recovery would come out on top.
Home button is not stuck, and cant seem to figure out the CID of my SD card since my phone is unaccessable.
I have a N1 and its worked fine for a while then i noticed when i turned it on it just stays at the "X" boot up screen.. I have already tried to reset the phone, clear storage, reboot,, and nothing fixes it. What can i do.. i know there has to be a way to load software back onto it or fix whatever is wrong with this thing. please help and thanks for our time.
can you get into the bootloader menu? by holding trackball and power button?
if yes then follow
http://forum.xda-developers.com/showthread.php?t=623496
wow,, ive done some programming and flashing to phones before but trying to follow those instructions and make sense of it all, isnt working with me. Thanks for the advice but that thread doesnt help me to much. i tried downloading everything it says i need and i cant figure it out.
rustynuttz said:
I have a N1 and its worked fine for a while then i noticed when i turned it on it just stays at the "X" boot up screen.. I have already tried to reset the phone, clear storage, reboot,, and nothing fixes it. What can i do.. i know there has to be a way to load software back onto it or fix whatever is wrong with this thing. please help and thanks for our time.
Click to expand...
Click to collapse
another app2SD thing after flashing a new rom?
well then you know more then me. If you can get into bootloader you should be able to get into recovery mode. You can also toggle USB mode, so you can be connected to your comp. In that case you can push a recovery image.
http://forum.xda-developers.com/showthread.php?t=611829
you can also wipe
etc
its all in that thread or somewhere else on this forum
rustynuttz said:
I have a N1 and its worked fine for a while then i noticed when i turned it on it just stays at the "X" boot up screen.. I have already tried to reset the phone, clear storage, reboot,, and nothing fixes it. What can i do.. i know there has to be a way to load software back onto it or fix whatever is wrong with this thing. please help and thanks for our time.
Click to expand...
Click to collapse
Any updates? same thing happened to me.
If in doubt then reflash everything again;
boot
system
and recovery
and start afresh.
see thats the thing,, i can click recovery from the bootloader screen and nothing happens. It will restart and just sit on the same "X" screen. Its very simple to put a phone into a DFU mode or recovery mode for Iphones,Motorolas,blackberry,nokia,samsung,Lg, and a few more i cant think of at the moment. When these phones become corrupt ive learned how to whatever firmware or software i want on dumb thing.. But this HTC is giving me a hard time and i know its something simple.. Most phones have a desktop software that will allow you to mess with phones programming, Itune-iphone/Blackberry-BB desktop Manager/motorola-RSD lite....ect. BUt i cannot find anything really for the HTC or just this N1. A lot of these programs for other brands, once you plug your phone in, will notice that the phone is in a recovery state and offer to do an update or a restore. Now why doesnt the N1 or do they, does google offer something like evryone else does?
rustynuttz said:
see thats the thing,, i can click recovery from the bootloader screen and nothing happens. It will restart and just sit on the same "X" screen. Its very simple to put a phone into a DFU mode or recovery mode for Iphones,Motorolas,blackberry,nokia,samsung,Lg, and a few more i cant think of at the moment. When these phones become corrupt ive learned how to whatever firmware or software i want on dumb thing.. But this HTC is giving me a hard time and i know its something simple.. Most phones have a desktop software that will allow you to mess with phones programming, Itune-iphone/Blackberry-BB desktop Manager/motorola-RSD lite....ect. BUt i cannot find anything really for the HTC or just this N1. A lot of these programs for other brands, once you plug your phone in, will notice that the phone is in a recovery state and offer to do an update or a restore. Now why doesnt the N1 or do they, does google offer something like evryone else does?
Click to expand...
Click to collapse
hmmm I understand your frustration. What did you do before it got to the 'X' splash screen?
I'm assumimg you've tried to reflash a different ROM in recovery mode?
rustynuttz said:
Most phones have a desktop software that will allow you to mess with phones programming, Itune-iphone/Blackberry-BB desktop Manager/motorola-RSD lite....ect. BUt i cannot find anything really for the HTC or just this N1. A lot of these programs for other brands, once you plug your phone in, will notice that the phone is in a recovery state and offer to do an update or a restore. Now why doesnt the N1 or do they, does google offer something like evryone else does?
Click to expand...
Click to collapse
The SDK can do that
like the others said, try get into recovery and reflash everything
SDK? i just turned the phone on and its stuck on the "Splash" screen just a big ol "X". I press volume down and power and pull up the bootloader menus.. i scroll down to recovery and press enter. and it reboots and stays at the damn "x" screen again. I've chosen everyone of the options it offers in that menu and nothing changes.. You know how when u first open that menu it will scan the SD card? Well it shows up for a second then goes away, and in the split second the green lettering is on the screen i swear it says "no splash image" or something like that. UHHHHhhhg!
Hmm I forgot how to get to get to recovery using physical buttons, sth like: power + trackball, or volume down + trackball i guess, so try that
So it looks like your phone is not rooted and you don't have Amon_Ra recovery maybe you have not even turned on USB debugger? tough luck friend
All is not lost if you can get into fastboot mode trackball and power together then using adb reflash boot,system and recovery images.
Or call Customer Service and trade in for a new Nexus One
if not you have to download the SDK http://developer.android.com/sdk/index.html
find stock images and reflash like the above post said
duylong186 said:
Or call Customer Service and trade in for a new Nexus One
if not you have to download the SDK http://developer.android.com/sdk/index.html
find stock images and reflash like the above post said
Click to expand...
Click to collapse
agreed....if you haven't "unlocked" the bootloader then i wouldn't bother with any of the suggestions....Call customer care and get a new one before you un-lock it and this mysteriously happens again...THEN, you'll be S-O-L!!
EDIT: Then with the new one, follow all the threads for un-locking, flashing recovery, nand,flash cyan, flash gapps LALALA
DOUBLE EDIT: Althought it sounds all you've done is messed up the recovery image, which you could re-flash. Then you could get into recovery and flash Cyan, having a functioning phone again
Hi guys,
First off let me say that i have been*
googleing this for a couple of days and im not one who easily asks a question in a forum but this problem really bugs me...
I have a htc dream or a t- mobile g1 (call it whatever you want). I know this isn't the right place but i couldn't find any other place to ask...
When i press the power button of my devices i see the g1 logo followed by the android logo... Right after the android logo i should see the interface off my phone but it does not. All it is showing me is a black screen. The screen is turned on i can see the glow off it and know how the phone looks like turned off...
First thing i tried
Hard reset. I pressed the home button and the end button. After seeing the exlamation mark i hold alt and press L. Wipe everything (alt w, alt s) tried them all but after rebooting the phone... Black screen...
At this point im stuck because if a hard reset doesn't work then the phone is dead... I presumed but it turned out that i was wrong... If i can get in the bootloader or the rainbow colour *screen (camera + end) i should be able to get it working...
Second thing i tried is download all kinds off update.zip and tried them all and none of them worked... You would think that the update.zip provided by google (1.6) should work. Here's the strange part. It detects the update... Extracts the update... Verifies the update... And the moment it installs the update the installation gets aborted... No other warning
I have read about DREAIMG.nbh but that wont work for me because my sd card is not a gold card and i cant make it a gold card because i cant get in the freaking menu off my phone...
What happened to my phone? It belonged to my nephew of 14 and he wanted to update it to 2.2 without doing some research first so yeah i smacked his head...
Can someone help me with this?
Engin
enginsoysal said:
Hi guys,
First off let me say that i have been*
googleing this for a couple of days and im not one who easily asks a question in a forum but this problem really bugs me...
I have a htc dream or a t- mobile g1 (call it whatever you want). I know this isn't the right place but i couldn't find any other place to ask...
When i press the power button of my devices i see the g1 logo followed by the android logo... Right after the android logo i should see the interface off my phone but it does not. All it is showing me is a black screen. The screen is turned on i can see the glow off it and know how the phone looks like turned off...
First thing i tried
Hard reset. I pressed the home button and the end button. After seeing the exlamation mark i hold alt and press L. Wipe everything (alt w, alt s) tried them all but after rebooting the phone... Black screen...
At this point im stuck because if a hard reset doesn't work then the phone is dead... I presumed but it turned out that i was wrong... If i can get in the bootloader or the rainbow colour *screen (camera + end) i should be able to get it working...
Second thing i tried is download all kinds off update.zip and tried them all and none of them worked... You would think that the update.zip provided by google (1.6) should work. Here's the strange part. It detects the update... Extracts the update... Verifies the update... And the moment it installs the update the installation gets aborted... No other warning
I have read about DREAIMG.nbh but that wont work for me because my sd card is not a gold card and i cant make it a gold card because i cant get in the freaking menu off my phone...
What happened to my phone? It belonged to my nephew of 14 and he wanted to update it to 2.2 without doing some research first so yeah i smacked his head...
Can someone help me with this?
Engin
Click to expand...
Click to collapse
There's a G1 forum where you can ask.
Sent from my HTC Glacier using Tapatalk
This is HTC Magic forum.....
Can this please be moved to the correct place? Or do i need to create the same topic there?
so i have a stock rooted a500 i got yesterday new.
have a problem..
10 minutes ago i was setting a wallpaper to a picture of my car. i cropped and set..wallpaper stayed black, so i did it again, still black. so i tried a different picture.
Crash
restarted, now stuck at lock screen, lock button doesnt slide, once you shut screen off, wont turn back on. clock doesnt move either. help?
Snag a paperclip
Hit that reset button.
Failing that, i'm at a loss. Never had anything remotely similar happen.
entropy.of.avarice said:
Hit that reset button.
Failing that, i'm at a loss. Never had anything remotely similar happen.
Click to expand...
Click to collapse
niether have i, i have a custom evo. reset button only restarts it
i didnt flash recovery yet, though i can access the files via usb when its locked at lock screen, so im going to try adb push
Good move
Or you can always toss a full stock ROM image on microSD and flash without custom recovery.
entropy.of.avarice said:
Or you can always toss a full stock ROM image on microSD and flash without custom recovery.
Click to expand...
Click to collapse
ok, adb sees no devices, so ill have to do it that way
where can i find a stock full rom for USA? seems full package links are dead
skullzaflare said:
where can i find a stock full rom for USA? seems full package links are dead
Click to expand...
Click to collapse
Not sure - never done any full package flashes, only update packages. Pretty sure I've seen a bunch of them around these fourms.
Best of luck - hope you don't have a dead tab.
entropy.of.avarice said:
Not sure - never done any full package flashes, only update packages. Pretty sure I've seen a bunch of them around these fourms.
Best of luck - hope you don't have a dead tab.
Click to expand...
Click to collapse
so far it seems i do, tried a update, and still does the same thing
it would be fine if i didnt have a custom boost animation in the system/media
i still have 12 more days warrenty.
is there a way to delete it via computer?
not sure if anyone knew about the hard reset, i contacted acer and played dumb, though i told them what happened.
i was instructed to
Power down the device
hold Vol Up + Power for 3 sec
continue holding Vol up, and keep switch the screen lock back and forth until "erasing cache" comes up on the acer screen
at which point you stop and let it run its course.
said it would take 30 minutes. i fell asleep, 2hrs later i checked it, still same. recontacted acer, another tech said to do the default hard restart with the push pin
worked like a charm
in process of rooting, installing CWM and making backup lol
skullzaflare said:
not sure if anyone knew about the hard reset, i contacted acer and played dumb, though i told them what happened.
i was instructed to
Power down the device
hold Vol Up + Power for 3 sec
continue holding Vol up, and keep switch the screen lock back and forth until "erasing cache" comes up on the acer screen
at which point you stop and let it run its course.
said it would take 30 minutes. i fell asleep, 2hrs later i checked it, still same. recontacted acer, another tech said to do the default hard restart with the push pin
worked like a charm
in process of rooting, installing CWM and making backup lol
Click to expand...
Click to collapse
Hello ,
Did have the same problem and solved it by flashing the update.zip found on this site.
I've put it on the root of the SD card , push start and holding vol down , and then perform the update .
Can you explain me tough what you men by " do the default hard restart with the push pin " .
Thanks
BerreZ said:
Hello ,
Did have the same problem and solved it by flashing the update.zip found on this site.
I've put it on the root of the SD card , push start and holding vol down , and then perform the update .
Can you explain me tough what you men by " do the default hard restart with the push pin " .
Thanks
Click to expand...
Click to collapse
the reboot is for if it stops responding, like a reset button on a computer. its under the usb port
flashing any update zip didnt work for me
skullzaflare said:
flashing any update zip didnt work for me
Click to expand...
Click to collapse
Did you get it from a local retail location? If so, I would just march back there with my receipt and not give too many details - i was working on a picture and it broke and I have no idea what is wrong, etc - they should just give you a new one.
Have you tried clearing the cache? There is a combo with holding power / volume up when booting and using the rotation lock switch, not quite sure how it is done but i think you just hold both and flip the switch like mad - totally sure I have seen the process posted here somewhere.
If you got it via online order, you still should be able to just return it.
Or call acer - they might be able to work some magic.
Best of luck, hope you get it going or at least get a new one. Really sounds like you have a defective unit, I rooted mine the day after I bought it, have had it for nearly two months and multiple rootings/unrootings/rom flashes and have had no issues at all.