Database Info

G1 is bricked!!!

after i attemped to upgrade my jf 1.41 rc 30 to jf 1.41 rc 33 my phone freeze and then i took out the battery, try to turn it on and it wont turn back on is there any way or any buttons i need to push to get this back on again? i'm desperate and dont want to wait for a g1 replacement which is coming next week please give me some advice on how to make my phone work again.

both CAMERA/POWER and HOME/POWER are not working?

yup both i tried nothing works

ariex said:
my phone freeze and then i took out the battery, try to turn it on and it wont turn back on.
Click to expand...
Click to collapse
Did you put the battery back in?

what do you think?

I upgraded from JF 1.41 RC30 with no problem, Radio and all, good luck!

ariex said:
what do you think?
Click to expand...
Click to collapse
So far you are the only person with this problem so we are running through the basics.
Did you get any errors or messages during the update? Did the phone run out of battery mid update? Did anything odd or unusual happen?

quick question in while in the topic, had he done a FULL nandroid backup and was able to atleast get to boot screen would he be able to restore his phone? just a quick questions because to this day i have no idea how the nandroid thing works i cant do it on my x64 vista either and dont see how it comes in handy lol. Sorry just trying to fig it out.

after i tried to install the radio update it showed some sort of chip with an arrow and then it froze for over 10 mins so i ended up taking out the battery

@zgjbeta Yes. If you can get to the blinkin android screen, your not really bricked. Nandroid would fix it right up.
If it wont even turn on, like your case. I dono what to tell you.
For starters, try to connect it to a wall outlet to make sure its not the battery.
Also tell us exactly what happened during the update process.
EDIT: I read your most recent post. That's strange because everyone gets the chip thing, you shouldve tried home + back or menu + green + red.
One of those wouldve most likely worked.
Good luck.
Also maybe try to take it out again and put it back in.

I had the chip and arrow after the radio update, I didn't take the battery out, started pressing random keys, lol... and then it went away and booted back to a JF recovery style screen. Pressed home + back and it rebooted to a stuck flashing android. Then did call+menu+end to reboot and it has worked fine ever since.
There is definitely something whacky going on...

yes i tried to do the home key plus end and camera plus end options while in that chip state but didnt do anything so i resolve to take out the battery and it wont turn on again. i also tried all the button reset combo nothing happens

If it wont even turn then there is really nothing that can be done. Another thing I would try is if you know someone else with a G1 try their battery.

ariex said:
after i tried to install the radio update it showed some sort of chip with an arrow and then it froze for over 10 mins so i ended up taking out the battery
Click to expand...
Click to collapse
Also try cleaning the battery contacts in the phone and on the battery. This happened to one of my dumbphones once - cleaned out the battery contacts and it worked again. Bizzare situation, simple solutions first.
You might've turned it off while it was writing a vital file. Thus your phone might be bricked.
Here's an idea - sent it back to T-Mobile/HTC - and I don't think they will notice you violated your warranty until it's too late (they have to fix your phone to find out) so you could just refuse to pay and have them send it back to you.

I too saw the chip with the arrow thing, so that makes 3 people in this thread. It happened when I did the radio update. Anyway, in my case, I held down the recovery mode keys for a while and it went to the menu. Then I just rebooted and everything was great. Glad I didn't take out the battery (I considered it).

I had the chip and just waited and it took care of itself. Just be patient people.

plug in the wall charger, wait 10 seconds, then hold the red power button for 3-5 seconds then release, it should turn on

i tried that didnt work anymore advice?

also is there any way to run diagnostics of this phone to pc to make it work?

If the phone won't turn on, go back to the T-Mobile store and ***** em out. Not much else to say if we can't even get power to it.

Partially Bricked Captivate

Hey guys, quick question. I've been scouring the forum here but haven't found a solution yet.
I was attempting to flash back to stock using Odin and my phone just kinda "hung up." Odin basically froze so I did a battery pull hoping that I'd be able to re-enter download mode and reflash to stock.
Now I'm getting a black screen with a phone, and exclamation point, and a computer icon every time i try to power on my phone.
I've tried every configuration of the 3 button combo to get back into download mode that I can think of but thus far nothing has helped.
I've read that this screen is a sign that you're only "partially bricked" but I cannot for the life of me get my phone to proceed past this screen in any way.
Can anyone help?

You need a Jig. This is how I fixed mine but they sell them on Ebay if you have the time to wait.
http://forum.xda-developers.com/showthread.php?t=841512&highlight=iGo

You try turning on odin, plug usb into computer and NOT the phone, Then while holding volume up/down plug usb into phone. That put my phone in download mode for me, it may take a few trys but hopefully you can get it to work

http://forum.xda-developers.com/showthread.php?t=775911
Follow this ^^

I've done that to my phone countless times. The first time, I was really freak out lol. I personally used this method its worked every time for me. It's difficult to get it to work the first time, but one you get the hang of it its not too bad, so don't get frustrated if you try it and it takes a few times. It's also the most cost effective. Instruction are there under the video.
http://www.youtube.com/watch?v=D0aoabVtPJ8

I appreciate the replies guys.
I was able to make my own Jig using a micro usb I had lying around and some resistors I bought this afternoon.
It's a hell of a relief to have my phone up and running and having only spent $4 to get it working again as opposed to the $125 AT&T would have charged me for the replacement.
Again, much thanks!

[Q] Hard Bricked?

Well, I was running the 2/10/2012 build of CM7 for about a week and a half, everything was silky smooth except for a few little hiccups until last night. My phone shut off and started boot looping. (SAMSUNG screen.... Off.... repeat). i figured it'd be fine, and just put it into download mode and i'd be fine. But no, it was different. As soon as i put the battery in, it instantly starts boot looping. no matter what i've tried it won't go... the only way i could get it into DL mode was using a custom jig i made with some resistors but even then, it shut off after about 3 seconds and then continued the boot loop routine. Seems like this thing is done for. i called AT&T and they're sending a new one, but do you guys think they'll find i had a custom rom on it? i took it to the store but naturally i knew more then the "helpful" sales rep. No one there could figure it out so i think ill be fine. Any thoughts??

devilsxcrunner15 said:
Well, I was running the 2/10/2012 build of CM7 for about a week and a half, everything was silky smooth except for a few little hiccups until last night. My phone shut off and started boot looping. (SAMSUNG screen.... Off.... repeat). i figured it'd be fine, and just put it into download mode and i'd be fine. But no, it was different. As soon as i put the battery in, it instantly starts boot looping. no matter what i've tried it won't go... the only way i could get it into DL mode was using a custom jig i made with some resistors but even then, it shut off after about 3 seconds and then continued the boot loop routine. Seems like this thing is done for. i called AT&T and they're sending a new one, but do you guys think they'll find i had a custom rom on it? i took it to the store but naturally i knew more then the "helpful" sales rep. No one there could figure it out so i think ill be fine. Any thoughts??
Click to expand...
Click to collapse
Runner,
Sounds like similar to a few other user.
Something to do with the power button stuck or bad board.
Search user garen21. Read his thread..a few pages back. Gl

thanks man, ill give it a look. It's really out of no where that this happened.

[Q] I Really Screwed Up This Time....Major Screw Up

Well, I'm sure you've probably guessed by the tone of the title, I bricked my 3G Xoom MZ600. Don't really wanna get too much in depth on how I did so.​ But I will say this: I rooted my Xoom a few weeks back, and everything was cool. For some reason, tonight, I decided I wanted to revert back to stock. This way I could do all OTA updates, and get myself off of Honeycomb, and back to ICS, and then see what I wanted to do from then on. Well, my dumbass, DID NOT have my battery fully charged, and I had this wild ass idea that if I had my charging cable plugged in, everything would be ok as far as being able to flash all necessary *.img files to revert back to Stock. So I flash the first *.img file which was the boot.img This went completely fine, which led me to believe that continuing on would be fine as well....Not the case. I proceeded to flash the system.img file, and that's where things took a turn for the worse. For some reason the system.img file would not flash to my Xoom through ADB (kept saying FAILED). So what do I do? I panic. I try several ADB Commands thinking that the Xoom had come Unmounted from my PC. After trying different commands, and reading a few things, I was somehow able to get the Xoom to respond, but not in a good way. I apparently hit a button combo that reset my Xoom, and then all it would do is stay stuck on the Motorola M Dual Core Boot Screen. So then I panic again. I then press Volume Up + Power and then Volume Down + Power to get back into Fastboot protocol. I then try to flash the *.img files again, thinking surely it had been enough time on the charger, so I should be able to flash all files now. Not the case. I honestly can't remember what happened exactly next, but my Xoom started saying RSD MODE 3. At this point I stopped panicking and started completely tripping (I've heard of the elusive RSD MODE, Never actually saw it though, until now). I do some research (Google is my Best Friend), but hey, I'm a dumbass, and I start trying to boot into recovery and what not (didn't happen by the way). Got the Xoom to reboot again, back into fastboot protocol again, thinking to myself, I'll try flashing the files one more time. It's GOT to work this time. So I flash the boot.img, success! I try to flash the system.img, FAILED! So now I'm thinking, well maybe I don't necessarily need to flash the System.img file, and instead I just continue on flashing the other *.img files (recovery.img, and userdata.img). By the way, not sure if I made this clear, I'm a F**KING dumbass!) Well, I then get the files flashed, minus the system.img, I then for some reason, think it is acceptable to go ahead and Lock the F**KING BOOTLOADER(before having successfully flashed the system.img file. Yea, I know what you're ALL thinking (What the HELL is WRONG with YOU!?!?!?!) So, guess what happens next? Can you guess? My Xoom stays stuck on the Moto Dual Core Boot Logo Screen, I reset once more using Volume Up + Power, then try to go into Recovery, only to be told (In Red Letters):
Failed to boot LNX 0x0004
Starting RSD mode 2
OneWire: Charger is connected...
Battery Charge Level: 60%
Danny Xoom by DannyShane, on Flickr
So now I'm not really sure what the hell to do. I keep giggling a little bit to myself, but that could just be the liquor I'm now consuming because I am completely devastated that I could actually be so F**KING STUPID to go and do this to myself. I am at a total loss for words to be spoken out loud, for I feel as though a person as dumb as I should not be allowed to talk for a significant amount of time.​
ANY, and I MEAN ANY, HELP would be GREATLY APPRECIATED. I have been looking at random stuff about RSD Mode and so on, on Google since this has happened, which was about 25 minutes ago now (currently 2:08am Sunday April 14th 2013). All I have seen so far, are some posts, and other random things about Soldering a USB cable (which I have no idea how to do BTW) And a person with as little brain power as myself, definitely does not need to be screwing around with a Handheld Metal Melting Device, to "FIX" his electronics. Someone please Help! PLEASE HELP PLEASE HELP. I am going to go drown my sorrows in a bottle of rum. We'll see what tomorrow has in store for DannyShane and his beloved Stingray Xoom, See you tomorrow XDA.
For the love of all that is holy.....Please HELP!:crying::laugh::silly:

there ya go
1:Type "Fastboot oem unlock" and Enter: It will say "Waiting for device"
3: Immediately press'n hold "Vol- and power", when the Dual core logo appears. You will need to hold them down for 10-20 sec
2:Reset the Xoom (Power and Vol+)
4: After 10-20 sec you will see that the fastboot command gets through and you can unlock the xoom with fastboot oem unlock (MZ604 US)

As I know the only way to get out of this is with a "Factory Cable" or something, I never ran to RSD 2 to tell you what it is. I found this cable on ebay, not sure but looks it can work for you http://www.ebay.com/itm/150CM-5-ft-...014771?pt=PDA_Accessories&hash=item3a7b234f33

@Extremetempz, first let me say THANK YOU for such a quick response. I did have a question though, about the order of which you put the instructions:
1:Type "Fastboot oem unlock" and Enter: It will say "Waiting for device"
3: Immediately press'n hold "Vol- and power", when the Dual core logo appears. You will need to hold them down for 10-20 sec
2:Reset the Xoom (Power and Vol+)
4: After 10-20 sec you will see that the fastboot command gets through and you can unlock the xoom with fastboot oem unlock (MZ604 US)
The question I have is, am I supposed to do step 3 before step 2? Or was the step that is labeled as step 3 actually supposed to be labeled step 2? I just want to make sure I have it correct. Thanks again.

@XxLordsxX, hello again! Let me also say THANK YOU for such a quick response as well. I too have been looking at the Pre-Made Brick Fix Cables, because I honestly think I would end up screwing something else up by trying to make one myself. Not really sure that it is possible to do any more screwing up to my Beloved Xoom, but I'm sure I could find a way, ha.
Anyway once again thank you for the Shared Link, if I can't my Xoom to do anything based upon what Extremetempz explained how to do, then I will definitely bee looking at purchasing the Pre-Made Brick Fix Cable. I just hope it doesn't come down to that. Wish me luck.

DannyShane said:
@Extremetempz, first let me say THANK YOU for such a quick response. I did have a question though, about the order of which you put the instructions:
1:Type "Fastboot oem unlock" and Enter: It will say "Waiting for device"
3: Immediately press'n hold "Vol- and power", when the Dual core logo appears. You will need to hold them down for 10-20 sec
2:Reset the Xoom (Power and Vol+)
4: After 10-20 sec you will see that the fastboot command gets through and you can unlock the xoom with fastboot oem unlock (MZ604 US)
The question I have is, am I supposed to do step 3 before step 2? Or was the step that is labeled as step 3 actually supposed to be labeled step 2? I just want to make sure I have it correct. Thanks again.
Click to expand...
Click to collapse
yeah do the 3rd before second I've had this problem before

If you come to have the RSD Mode 3 problem again, you can check the FAQ (which points to my solution to solve it) or the link on my signature . RSD Mode 3 is quite a common things to happen, and to not cause further problems remember to download another system.img, because it's clear that yours is corrupted!

Thanks goes to both
First, I wanna say Thanks to both of y'all
Now, to update y'all: Unfortunately XxLordxX the cable that you spoke of was not really an option for me, simply because, A.) I can't wait for the whole shipping time and such. B.) I don't have the $$$ to buy one if that was an option for me either. C.) I know that there has to be an easier/alternative way to go about fixing a completely Bricked Xoom. So as much as I do thank you for the input, these were not really feasible options for me seeing as how I use my Xoom on a constant daily basis, and I needed it back up and running immediately
And Extremetempz, I want to thank you for your input as well, because even though I couldn't get your method to actually do anything for me, it did get me to rethink my situation, take a deep breath, sit down, and start going back through everything I have learned, and everything I have taught myself about my Xoom, ADB, Fastboot, Android, and Patience. I would have to say that patience was the big factor in all of this. After trying your method with no success, unfortunately , I tried a few other things, button combos and what not. Unfortunately at this point the Xoom was completely unresponsive when it came to having it connected to my PC through USB. I kept getting a blank list of attached devices in ADB/Fastboot. I know it would seem that this would have to be a case of Drivers not being installed on my PC, but this was not the case. So after moving the folder that ADB/Fastboot was installed to around I was finally able to get my Xoom to register through Command Prompt(ADB/Fastboot). I wasn't ever able to get it to give me anything other than blank list of devices. So I took a shot in the dark, and decided to try and flash the *.img files......And so it worked!!!! Success! And I didn't even have to download any new *.img files. Because despite what XxLordxX recommended (about me needing to re-download the *.img files) they were actually all working files, and Ta-Da!!! I now have my Xoom back to Stock, and fully OTA'd and back on ICS (@ the moment ). We'll see how long it takes me to get something else going on it.
Once again, I wanna thank the both of you for helping me as much as y'all tried to. I will be keeping XDA posted on any new news that may happen in my Android Journey.
Thank you, and goodbye.

UM.....help !!!! Phone wont turn on after Re-Flashing JB 4.1.2 Stock in ODIN

So I've been v customizing friends and families S3's today even an old LG Revolution, And I finally got around to doing my dad's and was using going to use odin to just flash the stock image of JB 4.1.2 and then boom lol
Anyways, it said Successful and all that good stuff, unplugged it, and then restarted it but instead it just shut off. And it wont turn back on, But it still makes the notification sound on my laptop for when a device is plugged/unplugged from the USB, and it started installing the Android device drivers as well, so something in that phone still has to be alive.
Please tell me I can fix thi. When I show up at his his house later with a broken S3, he's gonna be so pissed, and I just got a new Note 3 and I really dont wanna have to give it to him as a replacement.

Just read this in a thread if ound on here while doing a search - And if it doesn't work you can force it into downoad mode by holding down the power. volume down and power key without the battery and then putting in a micro usb cord plugged into the computer. Then put in the battery. -
when i did that, the notification LED lit up RED, but I think i did something wrong after that. So I am thinikin this is fixable if I can just get into stock recovery and format/reset system and cache.

and apparently this guy had the same problem and fixed his - Update:
Josh over at MTVideos is the bomb. He was very professional and accommodating. They are typically a mail order operation but I was desperate and only a couple hours away, so he let me stop by. As soon as I showed up, he put down what he was working on and jumped into my phone. This was the first 32 Gb version he'd seen, so we were learning as we went. He explained everything he was doing as he went. First, try the dongle to get into download mode. No go. Next, hook up his JTAG equipment and dump a full backup, Justin Case .
Next, carefully write, address block by address block a known good 16 Gb bootloader and test. All the way up to 18 ( which, if you read the linked threads, was where I dd'd the recovery). Bingo. Once a known good recovery was put back in, it booted right up.
Factory data reset and we were off to the races.
Moral of the story: the recovery is very important. MD5 that ish before pushing.
I do still have one issue. When it boots, it tries to put me in Factory Mode, then FC's "factory mode" twice before letting me use my phone...
Again, a big thanks to Josh for helping me out. Those guys at Mobile Tech Videos really know their stuff and are good at what they do.

BackSeatSuicide said:
and apparently this guy had the same problem and fixed his - Update:
Josh over at MTVideos is the bomb. He was very professional and accommodating. They are typically a mail order operation but I was desperate and only a couple hours away, so he let me stop by. As soon as I showed up, he put down what he was working on and jumped into my phone. This was the first 32 Gb version he'd seen, so we were learning as we went. He explained everything he was doing as he went. First, try the dongle to get into download mode. No go. Next, hook up his JTAG equipment and dump a full backup, Justin Case .
Next, carefully write, address block by address block a known good 16 Gb bootloader and test. All the way up to 18 ( which, if you read the linked threads, was where I dd'd the recovery). Bingo. Once a known good recovery was put back in, it booted right up.
Factory data reset and we were off to the races.
Moral of the story: the recovery is very important. MD5 that ish before pushing.
I do still have one issue. When it boots, it tries to put me in Factory Mode, then FC's "factory mode" twice before letting me use my phone...
Again, a big thanks to Josh for helping me out. Those guys at Mobile Tech Videos really know their stuff and are good at what they do.
Click to expand...
Click to collapse
So yea. dont have Jtag equipment, but apparently this type of Hardbrick has been fixed without JTAG before. Tnere are a few threads/Guides on here. So I just gotta go find a bigger SD Card cause apparently you need a 16GB SD and I only have an 8 right now cause my 64GB got stolen. Other then that I got everything I need including a dual-boot installation of Linux. So as soon one of the Electronic stores around here opens I am going to get that card and hopefully make this thign work.....
I dont get what Happened. I flashed like 4 or 5 S3's yesterday, all of them were on 4.1.1 so I used to odin to flash them to 4.1.2, that file worked fine for all of them, including thw two of them that were Verizon, just like this one is. The phone has never been rooted or anytiing custom at all done to it. And it was not even 3months old. And my stepdad barely uses the thing. Just gonna be one of those days I can tell already.

BackSeatSuicide said:
So yea. dont have Jtag equipment, but apparently this type of Hardbrick has been fixed without JTAG before. Tnere are a few threads/Guides on here. So I just gotta go find a bigger SD Card cause apparently you need a 16GB SD and I only have an 8 right now cause my 64GB got stolen. Other then that I got everything I need including a dual-boot installation of Linux. So as soon one of the Electronic stores around here opens I am going to get that card and hopefully make this thign work.....
I dont get what Happened. I flashed like 4 or 5 S3's yesterday, all of them were on 4.1.1 so I used to odin to flash them to 4.1.2, that file worked fine for all of them, including thw two of them that were Verizon, just like this one is. The phone has never been rooted or anytiing custom at all done to it. And it was not even 3months old. And my stepdad barely uses the thing. Just gonna be one of those days I can tell already.
Click to expand...
Click to collapse
Have seen that happen when battery too low and messing with SD Card and recovery. Remove battery and sd card a few minutes. Replace battery only and plug into charger for at least 30 minutes. Unplug and Try to boot. If it boots. Power off and replace sim card. Reboot. Worth a shot.

I will try that
Sent Using My Galaxy Note 3

Yea that didn't work.
Sent Using My Galaxy Note 3