Database Users

Possible unbrick method

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?

So... I think I just bricked a G1. You tell me.

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

Is my HTC Magic totally bricked?

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.

People with hardware locked vibrants..

What can we do? I dont want to mess with anything again because i know if anything goes wrong i cant get in to download mode.. But i too want to flash the new roms and gps fixes. Is there anyway to make the hardware buttons unlocked?

Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.

You can root using clockworks and run some of the patch through clockworks too. Try not to use odin unless you really know what you're doing. A lot have odin hang on them. Other than that, you can flash rom using clockworks.
Sent from my SGH-T959 using XDA App

jonathan3579 said:
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
Click to expand...
Click to collapse
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*

TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.

glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
exactly my point. this is what happened to me. but think about this lets say i flash a rom right and you know how sometimes it hangs on the vibrant screen and just stays there. and in order to get it back i am going have to use odin. which i cant.......... so i think i wont mess with anything anymore. Rather just wait for official 2.2 ota update.

Chief Geek said:
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
Click to expand...
Click to collapse
Take it back and do a warranty exchange cause the buttons arent working correctly.

I've never tried it because I could never get Kies to connect to my phone, but isn't there a way to update firmware through Kies? I know the i9000 guys use Kies to upgrade, but I think that's only to get drivers and the updates though. I wish Samsung had a better interface than Odin to flash firmware. It's absolute garbage.

Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????

glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
This is how I got out of "phone to pc"
get into download mode (i went through it manually, as in plug in the phone, and pressing the volume buttons together at the same time)
Connected to ODIN, and by perfect accident, I clicked on "start" without placing ANY files in ANY spots.
This is what I thought "OMG $h!t" Well my phone was already bricked enough, so i just let it run its course through ODIN. My phone magically rebooted, and it booted into the ROM i had installed before I got the "phone to pc" problem.

Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA

demo23019 said:
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
Click to expand...
Click to collapse
The disadvantage is that it is harder (maybe impossible in some situations?) to get into the Download mode if something goes wrong during a ROM update. You can still load custom ROMS but if something goes wrong, you might not be able to get to Download mode to be able to fix it.
I had the phone ! PC screen on mine when I first tried to unsuccessfully flash Vibrant8. Luckily, my Vibrant doesn't seem to be hardware locked and I was able to get back into Download mode and re-flash it with Odin.

I'm able to access download mode with volume keys and i can access recovery mode so i guess im ok
also date on box is 8/27/10

How do you know whether you have a hardware locked Vibrant or not?

No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene

eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I trust what you're saying.. but is there any way to test that out without having an already bricked phone? I want to make sure I can recover my phone before flashing your Vibrant hybrid ROM. So after Step 6 do you get the download mode screen? Or does ODIN now show a COM port and it works, even without the little digger guy?

eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).

johnny12times said:
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
Click to expand...
Click to collapse
Download Mode is controlled by SBL, so if they truly changed anything that would be the cause.
I would think you could target redbend to update the SBL or even boot.bin bml /stl location.. I've not tried this, nor do I need too.. Just tossing options out there for people to try & don't mind risking a brick..
If you can get the SBL / Boot.bin for the Stock to flash via redbend, then this will solve the HW locks.. Now, Regarding my Phone, I can still get into Download Mode however, only by doing the USB trick &/or ADB reboot download.
I can not get into recovery unless I use clockwork Manager or ADB into
By the way, this is not a Hardware Lock issue as the thread states.. Not being able to get into download Mode like described, is a zImage issue & not the SBL / BOOT.bin
just as a FYI.
~Eugene

Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
Click to expand...
Click to collapse
Its happening because you ran a full titanium backup including system data. Yeah, dont do that. Reflash, then reinstall user apps with data, and pick and choose the system ones that are obvious (mms, bluetooth settings, wireless settings, etc.) Then reboot for changes to take effect. When in doubt, dont restore.
Good luck. Although you won't need it if you do what I just told you.
Sent from my SGH-T959 using Tapatalk

Just to share...
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I had the phone!computer bricked Vibrant, and just got my replacement from Asurion (in fact, of the phones in front of me are from Asurion since my original got stolen 2days after it came out ).
On phone1: The original TMO date is 8/12/2010, while the Asurion date is 8/19/2010. Also the ID is GJ/HLP. This one was HW Locked.
On phone2: The original TMO date is 9/2/2010, while the Asurion date is 9/10/2010. Also the ID is SM/HLP. This one doesn't seem to be HW Loocked, I can get into recovery easily, DL Mode ... not so much . Booting with vol+&- gets me into recovery, but booting with just vol- does nothing ...
Any thoughts?

[Q] First blue screen, now boot loop.

Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.

Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?

Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.

Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]

I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.

PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)

Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)

Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.

just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..

Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.

hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!

Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started

i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off

astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??

Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little

U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App

all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^

How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link

Looks like you are not having much luck. Did you try to factory reset?

astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much