Related
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.
Reading the "How to root" thread here. I've rooted a few G1's and a MT3G in the past.
Anyways. I downgraded to RC29, downloaded Amon's recovery and Hard SPL.
Did the whole Telnetd, downloaded telnet from market and mount remount, flash yadda yadda as per stated.
Rebooted and applied the Hard SPL.
After that finished I rebooted and it just hangs on the G1 screen, Home/Power does nothing. Camera/Power does nothing. Trackball/Power just lights the LED up blue.
Will it live the rest of it's life as a door stop?
not being able to boot into anything is a brick but there have been many threads about people who have somehow reversed their brick so just search this forum and see if anything happends who knows it could happen. otherwise its a really shiny paper weight
Bummer. I'll search around a bit more and see if there might be a thread I missed. I don't want to dig into it and do the whole jtag crap since there is still a warranty on the phone.
This is the "How-to" thread I followed and has worked on every G1 I have rooted til this phone which is a brand new one from Tmo.
http://forum.xda-developers.com/showthread.php?t=442480
Searching more I have read about people not flashing a radio before the SPL and caused a brick. If that is true why doesn't it state this as a necessary step?
Flashing the Radio before the SPL is needed for DangerSPL (although I seem to recall a thread debating that - http://forum.xda-developers.com/showthread.php?t=655097 ), I didnt think it was needed for HardSPL, it sounds like a brick unfortunatly, but I am no expert.
It is thought that its safer to flash the SPL and radio ect via fastboot (see link above) , not that it helps to much now, but that is an old guide, it should be updated though
Yep. From what I have gathered is if you can't get into recovery (home+power) or fastboot (camera+power) and it hangs on the G1 boot screen. It's a brick.
-RotorDemon- said:
Yep. From what I have gathered is if you can't get into recovery (home+power) or fastboot (camera+power) and it hangs on the G1 boot screen. It's a brick.
Click to expand...
Click to collapse
its not a brick unless it doesn't turn on at all (depending on how you define the word "brick")
exact same thing happened to one of the G1 replacements my friend got sent to him...we sent it back and they sent him a new one
Nah it's not bricked, the HSpl isn't compatible with your ROM, try flashing he ROM again, or faulty ROM this happens a lot.
Howto fix:
1. Backup any files on your SD card that are valuable to you (you can copy them to your PC's hard drive)
2. Format your SD card to FAT32 ( put your SD in your PC)
Windows: Right-click on SD icon and select format
3. Download the RC29 / RC7 dreaimg.nbh file (don't rename it or your phone won't recognize it):
RC29 (US): http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
RC7(Europe):http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
4. Put the file you just downloaded onto your freshly formatted SD card (make sure it is named DREAIMG.nbh, the rc7 file downloads with .NBH which is wrong)
5. Turn your phone off.
6. Hold down the Camera button, and press the Power button until the bootloader starts.
Note: On some G1s it may require pressing the action button (trackball), while on others it may require pressing the power button.
7. Follow the on-screen instructions to flash the image.
8. When it's done, press the trackball.
9. Press the Call, Menu, and Power buttons at the same time to reboot. You may need to unplug your phone for this to work.
10. And you're done, your phone is in Manufacture default-settings.
If you want to flash a ROM follow a guide (start from the beginning)
Tell me if it worked or didn't worked!
Source: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
what tally said....
but on the one i described, just to let you know, i flashed the rc29 dreaimg.nbh like 15 times, it would never get off the G1 boot screen
tnpapadakos said:
what tally said....
but on the one i described, just to let you know, i flashed the rc29 dreaimg.nbh like 15 times, it would never get off the G1 boot screen
Click to expand...
Click to collapse
Try flashing the ROM again if you can go to the bootloader(Rainbow) screen try this:
1. take out the SD card
2. download this file ,open the folder and paste the dreaming.NBH file to the root of your SD card(use your pc or another phone to past this on your SD card).
2. you should get a gray screen once the card in placed back into the phone
3. then press power to start update
4. once the update is complete press the track ball then the rainbow(bootloader) screen should come back up,
5. pull out the battery and there you go your phone should work again
Note: If it didn't updated turn of your phone and turn it on by pressing (& holding) Power+Camera button.
Tell me if it worked
Lol, for some reason it double posted my previous post sorry.
He says in the first post Camera / Power dosent load the bootloader
vixsandlee said:
he says in the first post camera / power dosent load the bootloader
Click to expand...
Click to collapse
send it back
vixsandlee said:
He says in the first post Camera / Power dosent load the bootloader
Click to expand...
Click to collapse
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.
tally114 said:
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.
Click to expand...
Click to collapse
Interesting, I didnt know that.
Thanks for the info.
tally114 said:
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.
Click to expand...
Click to collapse
Doesn't work either. Connected, disconnected, SD card in or out, SIM card in or out and any combination of that.
Logcat just sits and says "Waiting for device" while the phone just hangs on the G1 screen. So unless there is a different way to get into the bootloader besides using Camera+Power I'd like to know.
Camera+Power and Home+Power are unresponsive.
Well... it sounds like you've got yourself a fancy plastic brick, just remember for next time
1. Downgrade
2. Radio
3. Spl
-------------------------------------
Sent via the XDA Tapatalk App
I bought a Rogers HTC Magic for a pretty cheap price. It had The Rogers 1.5 Sense UI update on it. I decided I wanted to root it and load other ROMs, etc. So I read that the easiest method was to use Universal Androot to root it, and ROM Manager (from the Market) to flash the appropriate recovery image.
So, I installed both apps. I first ran Universal Androot and rooted. I confirmed root through ADB and also Super User permissions. I then restarted the phone just for peace of mind. After the restart, I ran ROM Manager. It automatically popped up and asked me if I was running an Ion/My Touch or an HTC Magic. I selected HTC Magic, because that's what this is. So then it flashed the recovery image and restarted the phone. When it restarted it went to the Rogers boot screen for a few seconds, and then started a loop of restarts. That's all it does now. It shows the Rogers screen for a few seconds, goes black and reboots over and over. I have tried booting into HBOOT, Fastboot, and into recovery. I cannot boot into any of them. One thing I did notice is that when I'm pressing any of the combinations (volume down + power, home + power, menu + power) for a very brief half a second right before the phone restarts, the bottom of the screen says "ClockwordMod ..." where ... is the version of the image (I'm at work without the phone, so I don't recall the exact number there).
So, is this thing officially a paperweight now, or is there some sort of hope?
Thanks.
Paul
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
adrift02 said:
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
Click to expand...
Click to collapse
Okay. That's weird. I mean, my phone is a Magic so choosing the option for the Magic instead of the Ion/MyTouch seemed to make sense.
Anyway, I cannot get anywhere. Holding vol+ and power does nothing, neither does home and power or back and power. Are there any other tricks to getting anywhere beyond this endless restart loop?
Thanks.
Starting to think I'm screwed.
PaulieORF said:
Starting to think I'm screwed.
Click to expand...
Click to collapse
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
ezterry said:
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
Click to expand...
Click to collapse
Thanks for the reply!
Right, I cannot get into fastboot or hboot. I'll try running the battery down when I get home today. Interesting idea.
Unfortunately running the battery dead with restarts didn't do the trick.
Any idea if there's any place I can send it to who has the smarts to jtag recover this thing?
Thanks.
me too
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
tmokeith said:
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
Click to expand...
Click to collapse
I don't think it's the same thing.
I rooted, loaded ROM Manager and installed the recovery. I was never even able to get into recovery in order to try to load any ROMs.
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
nate_benji said:
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
The phone does not identify itself to the computer, so this doesn't work.
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
nate_benji said:
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Oh yes. I've gone crazy trying every key combination with every combination of taking battery out, plugging it in, USB cable attached, detached, etc.
The phone never identifies itself as a piece of hardware to the computer in the 5 seconds between reboots.
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
naparstekk said:
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
Click to expand...
Click to collapse
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
I wasn't able to get hboot or fastboot. I pluged off and on the battery in the exact moment when the Logo came out after restarting. The logo was on the screen for the whole time, even while battery plugged off. I guess, i've done it so quickly that phone didn't switched off.
I think i was holding the power+home or power+back buttons all the time.
Can't really rember the exact way, sorry.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
Try removing the SD card and booting if its not restarting due to the wrong radio too soon that may help.. if you get into android restore the SD card and run the exploid process I posted a bit back for rogers magics, or the older goldcard method.
I've played around with taking the battery out and putting it right back in at all different times during the booting and can't get the phone to behave any differently. Iv'e tried it with SD card in and SD card out, USB cable in and USB cable out. I can't get anywhere.
I did notice that the phone does show up as an Android device for a second when it's booting. Tried to catch it in adb but no luck.
Starting to think this thing is shot. Any other ideas?
Just so everyone can see what's happening, I recorded a video and uploaded it. Linked below:
http://www.youtube.com/watch?v=hPoxMzm0MVU&hd=1
try to hold and KEEP holding the back + power... Not volume down!
Don't push and release like you did in the video.
I don't know if the phone is bricked, i sure hope not.
I had cm7 final running just fine. I was installing a kernel from clockwork recovery, and i followed the instructions. It installed, i told it to reboot the phone, it came to the cm7 blue booting screen. it kept repeating that for over 20 minutes. at that point i pulled the battery and replaced it. then i think it was stuck at the tmobile splash screen for a while. i was able to reboot and get to recovery mode again, i wiped cache and tried to install the kernel again, this time got an error. now it went to tmo splash screen and froze there for a while. after another battery pull, nothing will display on the screen and i cannot access recovery mode (i try by holding volume down, then holding power button). the ONLY thing that does happen is that the lcd backlight will stay on until i pull the battery. i plugged into pc without the battery, lcd lights up, but its not recognized by windows or adb.
I'd be grateful for any possible help or ideas, thanks in advance.
Could you give more info on Rom recovery kernel you were attempting etc?
Sent from my HTC Glaciee using XDA Premium App
Jay10826 said:
I don't know if the phone is bricked, i sure hope not.
I had cm7 final running just fine. I was installing a kernel from clockwork recovery, and i followed the instructions. It installed, i told it to reboot the phone, it came to the cm7 blue booting screen. it kept repeating that for over 20 minutes. at that point i pulled the battery and replaced it. then i think it was stuck at the tmobile splash screen for a while. i was able to reboot and get to recovery mode again, i wiped cache and tried to install the kernel again, this time got an error. now it went to tmo splash screen and froze there for a while. after another battery pull, nothing will display on the screen and i cannot access recovery mode (i try by holding volume down, then holding power button). the ONLY thing that does happen is that the lcd backlight will stay on until i pull the battery. i plugged into pc without the battery, lcd lights up, but its not recognized by windows or adb.
I'd be grateful for any possible help or ideas, thanks in advance.
Click to expand...
Click to collapse
Um sorry to say but your screwed. Sounds like a true brick to me
Sent from my HTC Glacier using XDA Premium App
Can you boot into the bootloader? Which one is installed? How can we help if we have no idea what's installed on your phone? There could be hope if you can boot into the bootloader and have the engineering SPL installed.
Also, what kernel were you trying to install?
TeeJay3800 said:
Can you boot into the bootloader? Which one is installed? How can we help if we have no idea what's installed on your phone? There could be hope if you can boot into the bootloader and have the engineering SPL installed.
Also, what kernel were you trying to install?
Click to expand...
Click to collapse
He already stated that he could not boot into h boot
Sent from my HTC Glacier using XDA Premium App
mark manning said:
He already stated that he could not boot into h boot
Click to expand...
Click to collapse
He did? I only saw that he could not boot into recovery. I was thinking if his recovery is screwed up, he could still use fastboot to flash a new recovery and then be able to wipe and start over. If he can't get into the bootloader or recovery, then yeah, it's the dreaded B word.
I'd really like to know what kernel he was trying to flash.
TeeJay3800 said:
I'd really like to know what kernel he was trying to flash.
Click to expand...
Click to collapse
Me too......
TeeJay3800 said:
I'd really like to know what kernel he was trying to flash.
Click to expand...
Click to collapse
First thing I asked.. still no reply kinda sucks when they can't help by responding so we can help them..
Sent from my HTC Glaciee using XDA Premium App
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Jay10826 said:
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Click to expand...
Click to collapse
Unfortunatly its the same procedure, hold volume down and power on. So if when u do that nothing happens and adb doesn't work your phone is done.
Sent from my HTC Glacier using XDA Premium App
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Jay10826 said:
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Click to expand...
Click to collapse
I'm not sure what the exact status of your phone is, but usually flashing a kernel does not brick the phone. If anything the ROM won't run right or there will be other problems, but never do they prevent the phone from booting into recovery (the recovery partition uses a completely different kernel). When you try turning it on again, don't bother trying to let it boot normally. Hold down power and volume down and see if you can get into recovery. Then run all three wipe options and flash a new ROM.
Jay10826 said:
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Click to expand...
Click to collapse
It's happened to me before where I thought I had completely bricked the phone. It crashed in CM7 RC2 when I tried to mess with the DSP settings. After that, I went through the same situation as you. I got tired of it, left it charging overnight while it was stuck on the splash screen. The next morning, it was on like nothing happened. I'm thinking it just needed to sort itself out. Not really a fix or suggestion, but at least an indication that there is hope.
Nah, its dead man. Not on its entirety but virtually. I know that JTAG could be an option albeit, im not sure.
I can assure you though that there must be something extra u must have missed that caused this, did you play with radio's or SPL's? Cause that is how i bricked a magic lol
blah
mine bricked on restoring. got to the point of not responding to anything - power button and even charge indicator no longer worked.
sorry to hear OP. it's bricked.
Jay10826 said:
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Click to expand...
Click to collapse
By saying that you used the visionary app to obtain root, is that all you did? Then installed rom manager and etc etc etc? Did you go through the full root method to get S=OFF as well?
Well previous to using visionary...i was trying another method to root using the terminal, but it wasn't working, so then i found visionary and used that. I never interacted with the phone using adb, if it matters. If i never really had s=off, could this be why this whole thing happened?
Jay10826 said:
If i never really had s=off, could this be why this whole thing happened?
Click to expand...
Click to collapse
Yes it probably is
Sent from my HTC Glaciee using XDA Premium App
Jay10826 said:
Well previous to using visionary...i was trying another method to root using the terminal, but it wasn't working, so then i found visionary and used that. I never interacted with the phone using adb, if it matters. If i never really had s=off, could this be why this whole thing happened?
Click to expand...
Click to collapse
Not really, if you were able to run a custom ROM with no problems before then you were rooted properly. Somwhere after you must have gone wrong, not sure where
blah
Ok so my phone booted up into the bootloader the other day and the the volume keys and power keys arent working. I cant get adb to connect to it either. When the battery is real low and i boot into hboot it gives me a low battery voltage warning and says press power to continue and it actually works.. but when im at the hboot or fastboot screens nothing works. Anyone know of a solution? Thanks
Daryl Keith said:
Ok so my phone booted up into the bootloader the other day and the the volume keys and power keys arent working. I cant get adb to connect to it either. When the battery is real low and i boot into hboot it gives me a low battery voltage warning and says press power to continue and it actually works.. but when im at the hboot or fastboot screens nothing works. Anyone know of a solution? Thanks
Click to expand...
Click to collapse
Is your bootloader s-off or s-on? If it's s-off try putting an ruu as a pc10img.zip on your sdcard and flashing it through bootloader. You'll have to reroot and possibly get s-off again so use a 2.2 ruu
Sent from my HTC Vision using XDA App
could it be that somehow your trackpad is stuck?
I am s-off sorry i didnt mention that. I flashed a pc10img and everything worked but when i rebooted it it still loads to the bootloader and the keys dont work. Im thinking it maybe the trackpad is stuck but how would i be able to check that?
If you are rooted you most likely have clockworkmod recovery? Have you tried to boot into there and flash a clean rom?
Sent from my HTC Vision using XDA Premium App
i cant boot into anything else but the bootloader and when in there the buttons arent working. Is there another way to boot into recovery?
You need adb. I'm not saying it will work but its worth a shot. If you don't know adb the is a guide in the dev section.
If you can get adb connected to your device after you adb shell into phone you can run "adb reboot recovery". Hopefully that works, but if not I'm at a loss
Sent from my HTC Vision using XDA Premium App
Daryl Keith said:
i cant boot into anything else but the bootloader and when in there the buttons arent working. Is there another way to boot into recovery?
Click to expand...
Click to collapse
Try removing your SD card, then see if you can get to recovery through the BL.
I cant get adb to connect.. after i enter "adb devices" it lists nothing. I can get my hd2 to connect not problem. I tryed PDAnet to see if it was a prob with the driver but at the end it says failed to handshake with device. i also have htc sync installed. I tried to boot it with the sd card removed but to no avail, same thing happens. I think its wierd that i was able to flash an RUU and the power button worked to select stuff but once its back in the regular bootloader screen nothing responds.
Update!! Ok so i flashed the RUU found at this link http://forum.xda-developers.com/showthread.php?t=912399&page=4. I figured it would be safer because i was already rooted and had s-off. This rom flashed fine and then when i plugged my phone in while it was off it turned on and booted to clockwork recovery. once i booted it up though it turns out my track pad wont select anything. It will move around the screen but when you click it does nothing.
Daryl Keith said:
Update!! Ok so i flashed the RUU found at this link http://forum.xda-developers.com/showthread.php?t=912399&page=4. I figured it would be safer because i was already rooted and had s-off. This rom flashed fine and then when i plugged my phone in while it was off it turned on and booted to clockwork recovery. once i booted it up though it turns out my track pad wont select anything. It will move around the screen but when you click it does nothing.
Click to expand...
Click to collapse
Sounds like your trackpad is indeed stuck. I would get the phone replaced if possible
Sent from my HTC Vision using XDA App