Database Info

Need some advice to fix phone

Thank you in advance for any help!
So I flashed my phone (with the newest RomEo ROM) and everything installed correctly. After install phone starts up and I calibrate my stylus. It then proceeds to install some stuff automatically and reboots on its own. Everything is still great. On restart I'm asked for my sim so I turn off the phone, throw the sim in, and then.....NOTHING. Phone will not turn on or respond to anything. Any advice?

Did you hard reset after flashin the rom? (when you got to the calibrate stylus screen)

Damn. Forgot. Any solution?

Im not sure, Ive heard that if you can get to the bootloader screen your ok. I would suggest just trying to flash again.

First, thanks for your input thusfar.
I would try to flash again but the phone is dead. It doesn't turn on at all and it doesn't sync with the computer. Hell, it doesn't even charge. I just bought the phone from AT&T the other day so I guess I'll walk in and tell them it died and see if they give me a new one, unless I can fix this thing tonight.

i dont know if this would be a problem but do you have HARDSPL on it? and maybe you just have a bad battery. Might want to test that first before taking it to the store and them getting it to work and then see the new ROM and void the warranty.

Im new to all of this so I dont know what advice to give. Did you pust in the Roms thread?
Since you have flashed a new Rom your carrier may not give you a refund.
You did flash GSM rom to a GSM phone and not to a CDMA one right?

he flashed the right rom because Romeos does not have a CDMA rom. I just hope he had hard spl. I mean i dont know what would happen if he flashed a rom and did not have hard spl. I dont know if it would even let him flash the new rom with out hard spl. So that is one possible reason i can think or his battery might have just given out. Since he says nothing turns on and it does not charge.

I do have hardSPL. I check and double checked that everything was the right version and everything was compatible. I'm hoping it's the battery but it's so weird if that is the case because I just got the phone a few days ago! Well, I guess I'll roll the dice and take the phone in and try to get a replacement for either the battery or phone.
Thanks for the input everyone.

If is was the battery, though, shouldn't the phone still boot up when it is connected to the power, even if the battery is dead? If you take the battery out of your phone and connect it to the power, does it still startup?

Nevermind. I took the sim out (again -- for the 10th time) and played with the battery prongs and, thank god, it worked. Thanks one last time for all the input and concern.

awesome! glad to hear it was just a battery problem

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.

My Phone Keeps Restarting Help.

I was carrying my phone and i dropped it, and now it won't turn on. Well i plug it to my computer and then i pressed the on button and it turns on but it gets to windows screen and reboots and does this over and over. BUT if i unplug it doesnt turn on anymore.
I've flashed it a couple of time but the last time i flashed it was back to the stock alltel rom because I wanted picture messages to come through.
I've reflashed it again and it goes through but when you unplug it. It turns off again.

So, when did you drop it? Like, right after you flashed a gsm rom onto a cdma phone (or vice-versa, not sure what alltel is, though I suspect it's cdma). Is dropping the phone even relevant to the story, or is flashing the cause of the re-boot cycles? You need to be a little more clear. By that, I mean, what did you do immediately before the re-booting started? Flash, or drop?
I suspect you need to go back to the stock rom and you'll be good to go. If dropping is the cause, go back to stock, and if it's still broken, send it in for repairs/warranty/insurance or whatever.

Farmer Ted said:
So, when did you drop it? Like, right after you flashed a gsm rom onto a cdma phone (or vice-versa, not sure what alltel is, though I suspect it's cdma). Is dropping the phone even relevant to the story, or is flashing the cause of the re-boot cycles? You need to be a little more clear. By that, I mean, what did you do immediately before the re-booting started? Flash, or drop?
I suspect you need to go back to the stock rom and you'll be good to go. If dropping is the cause, go back to stock, and if it's still broken, send it in for repairs/warranty/insurance or whatever.
Click to expand...
Click to collapse
Yup, Alltel IS CDMA.....

If it works while connected to the computer then you might have broken the battery-phone connection...or who knows. I'd definitely send it back if it is tstill in warranty.
Good luck.

Okay, i flashed it like 6 hours earlier to droping it, no i don't have warranty on it.
so i flashed it with back to the stock rom
then i dropped it 6 hours later and it keeps rebooting only when i have it plugged in but it wont turn on without it being plug.

You haven't answered whether or not you flashed a GSM ROM to your CDMA phone.
Can you see physical damage?

Oh, idk why but i typed something wrong, i've had this rom forum.ppcgeeks.com/showthread.php?t=42741 the alltel one since yesterday, and i dropped it today, After i dropped it put the battery back on but it didn't start up so i pluged it to my comp and it started up so i did hard reset while i had it plugged up to the computer and it didn't fix it.
*NOTE it can only start up (well try to start up but reboots) when i have the cord pluged up as soon as i take it out it wont start at all.*
So, i figured since it will only start up when i have a power source and reboots it might have a booting problem. So i reflashed it with the same rom i posted a link to..
I still have the same problem
Also i have no warranty bought phone from a friend.
*Also no damage just battery poped out when it got dropped*

Morbis0688 said:
Oh, idk why but i typed something wrong, i've had this rom forum.ppcgeeks.com/showthread.php?t=42741 the alltel one since yesterday, and i dropped it today, After i dropped it put the battery back on but it didn't start up so i pluged it to my comp and it started up so i did hard reset while i had it plugged up to the computer and it didn't fix it.
*NOTE it can only start up (well try to start up but reboots) when i have the cord pluged up as soon as i take it out it wont start at all.*
So, i figured since it will only start up when i have a power source and reboots it might have a booting problem. So i reflashed it with the same rom i posted a link to..
I still have the same problem
Also i have no warranty bought phone from a friend.
*Also no damage just battery poped out when it got dropped*
Click to expand...
Click to collapse
So before you dropped it it was working fine on the stock Alltel ROM?
If that's the case, its probably physical damage, although the constant restarts would indicate a software issue.
Make sure your battery is getting a good connection.
It may just be a damaged battery.

Yes, it was working fine, I got a spare battery at home so i'm gonna try that, but ya the restarting make me think a software problem cause its getting power really from the computer port.

[Q] Nexus S (i9023) won't start. Need help

Let me try to explain as comprehensively as possible what happened before I couldn't start my Nexus S again.
Until yesterday, I was running an older CM9 Nightly, together with the Matrix CFS kernel (18.0) and an older reloadedICS mod. Everything was running fine. Well, except for the fact that every time I rebooted, it took 2 or 3 times before it actually started. So 2 or 3 times, while rebooting, my Nexus S rebooted again, or just crashed so that I'd have to pull out the battery. But when my Nexus S finally started, it worked fine. I still had the occasional crash, but everything worked.
Yesterday, I decided it was time for a new nightly. So I downloaded the CM9 nightly from 7 april, the latest gapps, the newest matrix CFS kernel (18.5), and the Reloaded ICS 1.9b2 mod. Before I flashed everything, I wiped cache/dalvik cache, as always. I did flash everything at the same time though.
I didn't like the new icons in the statusbar from the latest Reloaded ICS mod, so I downloaded a different version of the Reloaded ICS 1.9b2 mod that someone had uploaded, with the different icons. That also worked fine. Every icon changed, except for the battery icon.
I used my Nexus S for the day. I listened music, browsed the web, whatsapped with some people... It worked fine. Then I went and watched some TV. After that I went to bed, and I noticed the battery of my Nexus S was empty. Since I wanted to check my mail/facebook before I went to sleep, I put my Nexus S in the charger. I started it, that worked fine. It said the battery had 0% on the statusbar, and because of the new battery icon from the Reloaded ICS mod, you can't see anymore if your Nexus S is charging. But it started, so I guess that's what counts.
So I started facebook (in the browser). Halfway loading, my Nexus S crashed. I experienced crashes before, certainly with CM9 nightlies, so I wasn't really surprised. I pulled out the battery, because the power button wasn't working (again, wasn't surprised, that's normal with that kind of crash).
And that's when things went wrong. My Nexus S wouldn't start again. I tried starting it in fastboot mode. Didn't work.... I put it in the charger for the night, but the charge icon (the white battery icon) didn't show up on the screen. And the next day (today), it still didn't start. I know someone who also has a Nexus S, so I tried his battery. Didn't work. I tried his charger. Didn't work. But when he tried MY battery and charger in HIS Nexus S, it DID work! Well, except for the fact that his Nexus S is still trying to boot up, after half an hour...
So that's two Nexus S's dead. One that won't even charge anymore. The other at least shows signs of life. I have no idea how this is possible. Clearly it has something to do with pulling out batteries, since his Nexus S wouldn't start anymore after he pulled out the battery when it was still turned on, and my Nexus S wouldn't start anymore after I pulled out the battery when it crashed.
By the way, my friend's Nexus S is not rooted. He is using stock ICS.
Thanks a lot in advance!
Edit; i also noticed that my battery was going down exceptionally quick after the 7 april nightly. I don't know if this is relevant.

Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?

Harbb said:
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Click to expand...
Click to collapse
Thanks for your help! I'm going to try that.
Yes, his phone can enter bootloader.
I've found some other people on the internet with the same problem as me. First there were problems with rebooting (it would only start after the second or third try). Then the battery drained exceptionally quick. And then, no signs of life at all... http://groups.google.com/a/googlepr...gory-topic/mobile/android-devices/06zm2LENFpc

Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.

Harbb said:
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Click to expand...
Click to collapse
My friend can't get into recovery anymore... It shows the green android icon for a flash of a second, and then it shuts down... But at least he can get into bootloader mode... I guess that's something.
I guess it has something to do with my battery, since that is what killed my friends Nexus S. I don't think my problem will ever be fixed though. That ubuntu app is worth a shot, but for that I need a computer that can run ubuntu and windows, and I don't think I have that.
I've also found this: http://mobiletechvideos.mybigcommerce.com/nexus-s-jtag-brick-repair/. Is that worth a shot? I'm willing to pay that kind of money for it. I do a lot of things myself without having too much knowledge, but this goes a little too far...

I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.

Harbb said:
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Click to expand...
Click to collapse
That tip with the bright lamp really worked! Thanks for that! But the first time he didn't do the factory reset yet, and now he can't even see the recovery menu (not even with a bright lamp), just the exclamation mark...

He needs to press Power + Vol. Up while he can see the exclamation mark. This will exit the splash screen and enter the actual recovery menu.

Thanks! But the factory reset didn't work, unfortunately... He is still stuck in boot...

As a matter of fact, oldblue has written up good instructions to get the phone to factory-stock state and fastboot flashable images. These should overwrite everything that should be overwrited on the phone and throw stock google stuff on there. Definitely something to try out, i would be doing this beyond anything else.
Note that it requires unlocking (and relocking later) the bootloader, and this will also erase all data on the phone and internal sdcard.

My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!

Happy to help and best of luck. Definitely use AdamOutler's app to the best of it's ability, it can do damn near anything. There is one more thing to try on top of this too if nothing goes to plan but it could be a potential sacrifice (minor hardware mod). Let's just hope this works.
The fastboot images would be, theoretically, a more perfect way to return to stock, so if this is possible to fix by software alone you'd be hard at work trying to find a better alternative. Maybe your phone is recoverable after all.

Androyed said:
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Click to expand...
Click to collapse
No dont try the ubuntu tool unless it doesnt turn on, you cant boot into bootloader or you cant turn it on, and you see nothing on the screen.
---
die tool is voor echte gebrickte nexussen.. gebruik die aleen als je dus niks meer ermee kan, zoals dat hij nieteens in de bootloader kan booten. (dat was met demijne gebeurd).
succes , als je vragen hebt PM me maar.

Same Problem?
Hey guys, i have a Nexus S (never rooted or anything). I received the update notice for ICS so i duly updated. Right after, my phone was bricked. Doesn't turn on / respond to anything.
I ran the UnbrickableRessurector by Adam and I can get Fastboot Mode to show up this way. I was really hoping that i don't have to unlock it or anything as i don't want to void warranty.
Any thoughts? I tried selecting 'recovery' after which the screen goes dark. Shining a bright light on the display doesn't help - really can't make out anything. Do i have a different problem?
Thanks!

[Q] May Have Bricked...

Forgive me if I'm missing something obvious; this is the first time I've rooted, so I'm still a bit new to all of this (though I have been reading around for weeks now).
So I just received my One X back from HTC today (needed to be fixed, don't ask), and, seeing that 2.20 had finally been rooted, got right to work in unlocking the bootloader. An hour later, I had CM10 flashed, installed, and running great (including separately flashing the boot.img). Installed most of my old apps, configured settings, everything was working great (tested calls, texts, HSPA+, and wifi). While I was setting a new voicemail message through AT&T Visual Voicemail, I started talking to a friend of mine (not on the phone), and the phone went to sleep. No big deal, I figured. However, I can't get the screen to turn back on now, and I'm a bit concerned. I don't think the phone's off, because it won't boot into bootloader (nothing happens when I press the power or the volume keys, no matter how long I hold for), and nothing happens when I plug into my computer either (the LED charging light doesn't even change). The only strange thing I can think of that could have caused this is that I had originally installed AOKP Milestone before going to CM10, and though I did a factory reset and reflashed boot.img before installing CM10, I didn't do a complete system wipe.
Does anybody have any idea what's going on? I sincerely hope I haven't bricked my phone... I'm going to try plugging it into a wall outlet for a little while and see if that makes a difference. Thanks in advance for any help!

So it just rebooted itself... I don't think I had anything to do with it; I'm pretty sure I wasn't pressing anything at the time. So at the very least, I have a working phone; however, I'd like to figure out what happened so that I can prevent it from happening again, particularly at a time where I actually need to call someone. Anybody have any idea what could have happened?

i heard VVM has problems with aosp roms.

Visual voicemail is getting trouble.. at the same time, it sounds like a good case of the sleep of death.. I tend to keep mine over clocked with a minimum of at least the 500's.
Sent from my One X using Tapatalk 2

InflatedTitan said:
Visual voicemail is getting trouble.. at the same time, it sounds like a good case of the sleep of death.. I tend to keep mine over clocked with a minimum of at least the 500's.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
How would overclocking help with this problem? Sorry for cluelessness, I'm just really new to this stuff.

flash the roms stock kernel

Sort of the same issue
My phone has been completely black for about 3 hours now. when i hold the power button none of the lights flash. I rooted my phone today and installed CM10 but it didn't work right so i decided to try another one. I used icecoldjelly and later found out that it was only for the international version. i tried to reboot my phone through TWRP and now it won't turn on. at all so i can't do anything with it. when it's plugged into my computer and i hold the power button, I hear the connect, then disconnect sound repeatedly until i let go. but there is no response on the phone.:crying:
help please. this is an expensive paperweight that i have here.

cakeballs said:
My phone has been completely black for about 3 hours now. when i hold the power button none of the lights flash. I rooted my phone today and installed CM10 but it didn't work right so i decided to try another one. I used icecoldjelly and later found out that it was only for the international version. i tried to reboot my phone through TWRP and now it won't turn on. at all so i can't do anything with it. when it's plugged into my computer and i hold the power button, I hear the connect, then disconnect sound repeatedly until i let go. but there is no response on the phone.:crying:
help please. this is an expensive paperweight that i have here.
Click to expand...
Click to collapse
Lucky for us, absolutegrim wrote a guide on how to unbrick. Head over to the general section and look for the "unbricking Evita" thread, it may be down a few pages.

Ice Cold Jelly strikes again....
cakeballs said:
My phone has been completely black for about 3 hours now. when i hold the power button none of the lights flash. I rooted my phone today and installed CM10 but it didn't work right so i decided to try another one. I used icecoldjelly and later found out that it was only for the international version. i tried to reboot my phone through TWRP and now it won't turn on. at all so i can't do anything with it. when it's plugged into my computer and i hold the power button, I hear the connect, then disconnect sound repeatedly until i let go. but there is no response on the phone.:crying:
help please. this is an expensive paperweight that i have here.
Click to expand...
Click to collapse
bricked it is but hopefully not permanently see here http://forum.xda-developers.com/showthread.php?t=1966850

Ouch
cakeballs said:
My phone has been completely black for about 3 hours now. when i hold the power button none of the lights flash. I rooted my phone today and installed CM10 but it didn't work right so i decided to try another one. I used icecoldjelly and later found out that it was only for the international version. i tried to reboot my phone through TWRP and now it won't turn on. at all so i can't do anything with it. when it's plugged into my computer and i hold the power button, I hear the connect, then disconnect sound repeatedly until i let go. but there is no response on the phone.:crying:
help please. this is an expensive paperweight that i have here.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1966850

Right now, there isn't a fix for an ICJ brick. Absolutelygrim makes note of this on the last page of the thread. He is working like a mad man to get it.
I hate to be blunt, but read the threads carefully, pay attention to some of the posters signatures. There are multiple threads and multiple people who have links in their signatures to those threads(see mine). Just check back to the unbrick evita thread frequently. It will get fixed. I turned my phone over to grim and let hum brick it on purpose to downgrade my Hboot. So the method that's posted in the thread, works... Just not for ICJ, yet.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

Unless I get ahold of a bricked phone.. Then I can bring a JTAG into this.. Neither my method or yarr's method will work for an ICJ flash on 2.20..
We are probably 5 feet away from a brick wall while traveling at 80 mph.. That's the best way to put it, we are almost out of ideas

absolutelygrim said:
Unless I get ahold of a bricked phone.. Then I can bring a JTAG into this.. Neither my method or yarr's method will work for an ICJ flash on 2.20..
We are probably 5 feet away from a brick wall while traveling at 80 mph.. That's the best way to put it, we are almost out of ideas
Click to expand...
Click to collapse
It's really looking like JTAG will be the only option, and even then it still might not work...
Sent from my HTC One XL cellular device over clocked to 1.9Ghz