Related
Hi guys,
three days ago I installed Darkyrom HD on my mates Galaxy S2, everything went smooth. But 10 minutes ago he called and said that the phone woudn't turn on!
He says he can't get response out of it. No recovery or hard reset with nor without battery in.
Don't hope it's perma bricked and it seems weird that it suddenly wont turn on.
Any ideas/help?
Thanks a lot.
At the same time press volume up + home button + power on to enter CWM.
Is his battery charged?
Prozel said:
Hi guys,
three days ago I installed Darkyrom HD on my mates Galaxy S2, everything went smooth. But 10 minutes ago he called and said that the phone woudn't turn on!
He says he can't get response out of it. No recovery or hard reset with nor without battery in.
Don't hope it's perma bricked and it seems weird that it suddenly wont turn on.
Any ideas/help?
Thanks a lot.
Click to expand...
Click to collapse
Does it get a response if holding down the power button for 8-10 sec? This will essentially reboot the phone regardless of what state it is in. If your buddy's been hit with the "sleep of death", this will boot the phone. Though I think this is a low probability if he tried pulling battery and putting it back.
Does it get a response if plugging it into the AC adapter? On the off chance the battery is completely dead. I'd like to think he tried this, though.
Has he tried another battery? Could be the battery lost the ability to hold a charge. Not common, but not unheard of either.
Doesn't seem to help. But I've told to let it charge the night and try again.
Any particular this happens? Seems random that it suddenly wont turn on.
Prozel said:
Doesn't seem to help. But I've told to let it charge the night and try again.
Any particular this happens? Seems random that it suddenly wont turn on.
Click to expand...
Click to collapse
Any particular reason? Sure. Most often, because the user installs something or flashes something they are not supposed to, to their phone. Or dropped it in water.
ctomgee said:
Any particular reason? Sure. Most often, because the user installs something or flashes something they are not supposed to, to their phone. Or dropped it in water.
Click to expand...
Click to collapse
This is what I did:
- Flashede an insecure kernel
- Rootede and installed busybox
- Downloaded Darky's OTA
- Downloaded og installed his kernel (SuperCore)
- Bootede in CWM and installed his ROM
Prozel said:
This is what I did:
- Flashede an insecure kernel
- Rootede and installed busybox
- Downloaded Darky's OTA
- Downloaded og installed his kernel (SuperCore)
- Bootede in CWM and installed his ROM
Click to expand...
Click to collapse
I wasn't trying to say YOU installed or flashed something. Maybe he did. Can I assume the phone was working when you gave it back to him? And that it was working fine for the three days after? Or was the phone in YOUR possession until he called you today?
I haven't had phone since i installed it. But I honestly don't think i he flashed anything.
He went out to jog - phone worked (listening to music)
He came home and placed the phone on the table - Phone worked
He did some exercises and when he came back - phone all black, can't get any response
Prozel said:
I haven't had phone since i installed it. But I honestly don't think i he flashed anything.
He went out to jog - phone worked (listening to music)
He came home and placed the phone on the table - Phone worked
He did some exercises and when he came back - phone all black, can't get any response
Click to expand...
Click to collapse
You said he tried a battery pull? And no response after replacing battery?
Sure his battery is just not dead, bit odd if it had been working and suddenly this happens.
Most cases an app or something can cause the phone to restart, or freezes, usually a hard reset solves this by holding down the power button for about 10 seconds.
Or entering recovery mode, or download mode just to ensure they are working.
Make sure he can charge the battery.
If all fails you may need to try a jig.
Sent from my GT-I9100 using Tapatalk
No response afer he pulled the battery.
Prozel said:
No response afer he pulled the battery.
Click to expand...
Click to collapse
Hmm. Try a different battery. If that doesn't work, warranty time.
Sent from my GT-I9100 using XDA App
We are trying to get another battery. In the meantime I've ordered a USB Jig that hopefully will turn the beast on!
Prozel said:
We are trying to get another battery. In the meantime I've ordered a USB Jig that hopefully will turn the beast on!
Click to expand...
Click to collapse
If not you will need to reflash to stock rom as warranty void with root or custom rom ..
JTag may be your next step .
jje
try to get into download mode (vol. down, home and standby button) then you can flash a firmware
Sent from my GT-I9100 using XDA App
Judaas said:
try to get into download mode (vol. down, home and standby button) then you can flash a firmware
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
READ the post please before answering .
We are trying to get another battery. In the meantime I've ordered a USB Jig that hopefully will turn the beast on!
jje
It wasn't the battery. But we've found someone that can repair it for 25 pounds + shipping. So if the USB jig doesn't work, it's going to them!
Hi guys,
Very confused here!
I was running the latest AOKP Hydrogen rom and one of the latest Siyah kernels...
I recently moved onto the S3, so I was basically prepping my S2 to be sold. What happened was as follows:
I had my S2 connected to my PC to get some data off of it;
I went into the factory reset menu and it froze so I unplugged the USB cable (I assume it was waiting for the SD card to become available.
It displays the "settings is not responding. Would you like to close?" message, but I clicked wait and it seemed to work fine as I'd disconnected the USB cable;
At this point the battery was at about 19%;
I clicked factory reset with wipe SD card;
After a few minutes I check the phone and it's completely blank. I figure it's doing something and can't turn the screen on so I leave it for a few more minutes;
Eventually I grow concerned and assume the phone has crashed, so I hold down the power button to do a hard reset.
After this the phone does not turn on.
It does the following:
If I try to turn it on it displays the SGS2 logo (with the yellow triangle) for a few seconds and then turns off.
If I connect it to the power it displays the loading screen of the battery charge app for a few seconds and then turns off.
Sometimes if I mash the buttons it will flash on and off with a pure white screen until I hold the power button and turn it off.
Any ideas, guys?
My only idea is that something crazy has happened with the battery as I did swap my extended battery with my girlfriend's normal battery last night. As I work in a phone shop, I'll charge up the battery in another phone to make sure it has power.
But I know the battery has power, and the phone it doing exactly the same thing with my old 1650mah battery (which may or may not have power in it).
Any ideas? I was going to be selling it for around £200, so it was gonna really take the load of my shiny, new S3! 0_o
SirCanealot said:
Hi guys,
Very confused here!
I was running the latest AOKP Hydrogen rom and one of the latest Siyah kernels...
I recently moved onto the S3, so I was basically prepping my S2 to be sold. What happened was as follows:
I had my S2 connected to my PC to get some data off of it;
I went into the factory reset menu and it froze so I unplugged the USB cable (I assume it was waiting for the SD card to become available.
It displays the "settings is not responding. Would you like to close?" message, but I clicked wait and it seemed to work fine as I'd disconnected the USB cable;
At this point the battery was at about 19%;
I clicked factory reset with wipe SD card;
After a few minutes I check the phone and it's completely blank. I figure it's doing something and can't turn the screen on so I leave it for a few more minutes;
Eventually I grow concerned and assume the phone has crashed, so I hold down the power button to do a hard reset.
After this the phone does not turn on.
It does the following:
If I try to turn it on it displays the SGS2 logo (with the yellow triangle) for a few seconds and then turns off.
If I connect it to the power it displays the loading screen of the battery charge app for a few seconds and then turns off.
Sometimes if I mash the buttons it will flash on and off with a pure white screen until I hold the power button and turn it off.
Any ideas, guys?
My only idea is that something crazy has happened with the battery as I did swap my extended battery with my girlfriend's normal battery last night. As I work in a phone shop, I'll charge up the battery in another phone to make sure it has power.
But I know the battery has power, and the phone it doing exactly the same thing with my old 1650mah battery (which may or may not have power in it).
Any ideas? I was going to be selling it for around £200, so it was gonna really take the load of my shiny, new S3! 0_o
Click to expand...
Click to collapse
If it was bricked it wouldnt turn on even a bit. Just charge it or try changing the battery.
coolstorybro_123 said:
If it was bricked it wouldnt turn on even a bit. Just charge it or try changing the battery.
Click to expand...
Click to collapse
If I try to charge it it displays the SGS2 charging screen for a few seconds and then switcher straight off.
I just got into work and tried my colleagues 2000mah battery which had 32% in it. Exactly the same problem. WTF????
Thanks
Edit: FYI, it turns off before entering download mode or recovery. WTF????
Maybe you hit this ?
VAXXi said:
Maybe you hit this ?
Click to expand...
Click to collapse
That's just what I was thinking, actually
I couldn't find a description of what actually happens when this brick happens. The page doesn't really say... Does anywhere say?
Edit: I swear I didn't even flash the Siyah RC6 that was known to brick the phones either... -_-;;
Thanks!
It's not just a specific kernel, more are actually faulty. The whole story is here.
SirCanealot said:
Hi guys,
Very confused here!
I was running the latest AOKP Hydrogen rom and one of the latest Siyah kernels...
I recently moved onto the S3, so I was basically prepping my S2 to be sold. What happened was as follows:
I had my S2 connected to my PC to get some data off of it;
I went into the factory reset menu and it froze so I unplugged the USB cable (I assume it was waiting for the SD card to become available.
It displays the "settings is not responding. Would you like to close?" message, but I clicked wait and it seemed to work fine as I'd disconnected the USB cable;
At this point the battery was at about 19%;
I clicked factory reset with wipe SD card;
After a few minutes I check the phone and it's completely blank. I figure it's doing something and can't turn the screen on so I leave it for a few more minutes;
Eventually I grow concerned and assume the phone has crashed, so I hold down the power button to do a hard reset.
After this the phone does not turn on.
It does the following:
If I try to turn it on it displays the SGS2 logo (with the yellow triangle) for a few seconds and then turns off.
If I connect it to the power it displays the loading screen of the battery charge app for a few seconds and then turns off.
Sometimes if I mash the buttons it will flash on and off with a pure white screen until I hold the power button and turn it off.
Any ideas, guys?
My only idea is that something crazy has happened with the battery as I did swap my extended battery with my girlfriend's normal battery last night. As I work in a phone shop, I'll charge up the battery in another phone to make sure it has power.
But I know the battery has power, and the phone it doing exactly the same thing with my old 1650mah battery (which may or may not have power in it).
Any ideas? I was going to be selling it for around £200, so it was gonna really take the load of my shiny, new S3! 0_o
Click to expand...
Click to collapse
your phone is ok as far as it shows u the s2 logo
you have 2 things to do , try to go to recovery or download mode and formate data/factory reset then flash another rom , btw what kernel u used before your phone go to this situation ? if you were using stable kernel "cm,neak,fluxi,syah stable" so you are safe from hardbrick bug , and the hard brick bug is done only if you have faulty kernel and wibed your data through recovery , and this isn't your situation , so don't be afraid
evaworld said:
your phone is ok as far as it shows u the s2 logo
you have 2 things to do , try to go to recovery or download mode and formate data/factory reset then flash another rom , btw what kernel u used before your phone go to this situation ? if you were using stable kernel "cm,neak,fluxi,syah stable" so you are safe from hardbrick bug , and the hard brick bug is done only if you have faulty kernel and wibed your data through recovery , and this isn't your situation , so don't be afraid
Click to expand...
Click to collapse
Thanks for saying, but I can't get into recovery or download. The phone switches off before then!
That's what's so confusing! xD
Thanks
With a known good batter try hard resetting to download mode 2x in a row.. Hold the button config to get into download mode.. Hold it through two restarts.. Might work.
Sent from my GT-I9100 using xda premium
I've nuked mine a few times with buggy kernels, sounds like a similar situation. I got my device back by flashing CM9 resurrection, then flashing Siyah, and finally from CWM flashing an ICS-based stock ROM.
I'd suggest taking a backup of your efs unless you're selling it with stock.
Sent from my GT-I9100 using XDA
SirCanealot said:
Hi guys,
Very confused here!
I was running the latest AOKP Hydrogen rom and one of the latest Siyah kernels...
I recently moved onto the S3, so I was basically prepping my S2 to be sold. What happened was as follows:
I had my S2 connected to my PC to get some data off of it;
I went into the factory reset menu and it froze so I unplugged the USB cable (I assume it was waiting for the SD card to become available.
It displays the "settings is not responding. Would you like to close?" message, but I clicked wait and it seemed to work fine as I'd disconnected the USB cable;
At this point the battery was at about 19%;
I clicked factory reset with wipe SD card;
After a few minutes I check the phone and it's completely blank. I figure it's doing something and can't turn the screen on so I leave it for a few more minutes;
Eventually I grow concerned and assume the phone has crashed, so I hold down the power button to do a hard reset.
After this the phone does not turn on.
It does the following:
If I try to turn it on it displays the SGS2 logo (with the yellow triangle) for a few seconds and then turns off.
If I connect it to the power it displays the loading screen of the battery charge app for a few seconds and then turns off.
Sometimes if I mash the buttons it will flash on and off with a pure white screen until I hold the power button and turn it off.
Any ideas, guys?
My only idea is that something crazy has happened with the battery as I did swap my extended battery with my girlfriend's normal battery last night. As I work in a phone shop, I'll charge up the battery in another phone to make sure it has power.
But I know the battery has power, and the phone it doing exactly the same thing with my old 1650mah battery (which may or may not have power in it).
Any ideas? I was going to be selling it for around £200, so it was gonna really take the load of my shiny, new S3! 0_o
Click to expand...
Click to collapse
i am having exactly the same problem.i did a factory reset after flashing siyah kernel (SiyahKernel v3.3.1) on Resurrection remix v2.2.let me know if you guys find any solutions
JIG
try to use a download mode JIG.
I'm not sure if a link will violate xda-rules....
google it
dont worry
if you boot up and are getting the sg2 logo then you have not bricked you phone.
to fix simply download a .tar version of any rom and run odin to pda reinstall if you wanted to you could go the whole hog and reflash a fresh cf-kernal (rooted or stock) and then flash fresh firmware. just remember to get the kernal that originally matches the (ithink) your correct baseband ie xxki4
there should be no worries aslong as you dont pull the plug.
could have had a worse error saying installation incomplete please use kies then you would have to had taken battry out reinserted and hoped the three butn combo for rec. mode worked happened to me awhile back lol
hope i helped you
ps never read your post fully just skimmd the jist of it although the above should be applicable
also try resetting your battry stats in cwm
finally fixed
thanks for the help everyone.i have fixed it now.it seems like the problem was with the updated version of siyah kernel .i managed to put the phone in download mode.(kept the phone on the charger for a while. than, i don't know some how when i tried to go to download mode it did).and flashed siyah kanel v3.2.6.4 via odin
Hi All,
I have a Samsung GT-I9100 phone which in it's current state, no matter what button is pushed or combination is pushed together will show nothing.
Situation of death:
6.30am - on charge, working fine - Take off charge put in pocket
6.50am - take out of pocket, phone sitting on the Galaxy loading screen. Attempt turning phone off then on and gets to same point and sits there.
7.30am - pull battery off, leave for an hour
8.30am - Put battery in, same result. Find post here which recommends clear data/factory reset. Put phone into Recovery, select Clear data, reboot phone, same situation. Put phone back into recovery, select factory reset. Starts clearing, sits on this screen for about 15 min before screen turns off. leave for 10 min, nothing happened so pushed power button and nothing happened, attempted recovery mode and download mode button combination - still nothing. Removed battery for 30 min, back in and same thing.
Now stuck with my phone which will do absolutely nothing. Any suggestions would be much appreciated. From what I read a USB Jig may be appropriate so will look into a bit of shopping soon.
What ROM were you on?
Don't say 4.0.4.
Sent from the little guy
gastonw said:
What ROM were you on?
Don't say 4.0.4.
Sent from the little guy
Click to expand...
Click to collapse
Ok, I won't say it....
Instead I will say 4.1.2 I believe. I was running the latest that had been provided to me via Kies (not been using a custom rom for a long time)
Jig more than likely won't work (0.0000000000001% chance of working), but try it any way. Service centre.
MistahBungle said:
Jig more than likely won't work (0.0000000000001% chance of working), but try it any way. Service centre.
Click to expand...
Click to collapse
Took it to where I brought it, and they told me $100 min for repairs which isn't fun but I guess it's that point
Yep unfortunately that's how these things work. Look, if you can get a jig, try it. You may be one of those lucky people. But at least now you know what you're up for.
Well, thanks for the replies, sent it in and been told Mobo problems, and will cost more to replace than to buy a new phone... YAY....
Flashing going fine, but just have a bit of an annoying problem. To boot into ODIN or Recovery, I have to keep trying and trying before it sticks and finally gets into what I want.
Right now I'm trying to get into recovery. Phone is off, I hold VolUp and the Power button. The phone buzzes and starts to turn on. However, sometimes it just shuts right back down. Other times, the Samsung logo appears with "loading recovery" in the top left, I release the buttons only to have it shut down again. Very rarely, I can get into Recovery or ODIN.
Anyone know why this or how to solve this?
Thanks!
dj_blueshift said:
Flashing going fine, but just have a bit of an annoying problem. To boot into ODIN or Recovery, I have to keep trying and trying before it sticks and finally gets into what I want.
Right now I'm trying to get into recovery. Phone is off, I hold VolUp and the Power button. The phone buzzes and starts to turn on. However, sometimes it just shuts right back down. Other times, the Samsung logo appears with "loading recovery" in the top left, I release the buttons only to have it shut down again. Very rarely, I can get into Recovery or ODIN.
Anyone know why this or how to solve this?
Thanks!
Click to expand...
Click to collapse
That sounds odd... especially since at that point the phone is not booted so it's down at the hardware level. Maybe defective?
mwm523 said:
That sounds odd... especially since at that point the phone is not booted so it's down at the hardware level. Maybe defective?
Click to expand...
Click to collapse
not sure, but got a ROM loaded up so i can just reboot into recovery. problem solved!
I had this same problem...I couldn't really figure out what was wrong but I too just use the boot to recovery option in the 4-way reboot menu. It'd be kinda nice to figure out what was wrong, though.
just found another issue. after my battery dies, i need to let it charge for 10-15 minutes before i can power it on.
my previous phone seemed to have a tiny bit "of reserve" to let you boot up and at least be functional while you were charging.
is this just a HW limitation on the S4 or is something up?
dj_blueshift said:
just found another issue. after my battery dies, i need to let it charge for 10-15 minutes before i can power it on.
my previous phone seemed to have a tiny bit "of reserve" to let you boot up and at least be functional while you were charging.
is this just a HW limitation on the S4 or is something up?
Click to expand...
Click to collapse
Usually you can wait a few minutes and charge it. That's how it was on the S3. I haven't let me phone die completely yet because the battery life is so good it lasts all day o when I go to bed it charges on my bedside and doubles as my wake up alarm as well as my medication alarms.
DarkMenace said:
Usually you can wait a few minutes and charge it. That's how it was on the S3. I haven't let me phone die completely yet because the battery life is so good it lasts all day o when I go to bed it charges on my bedside and doubles as my wake up alarm as well as my medication alarms.
Click to expand...
Click to collapse
Sounds good. I just picked up one of those "lipstick" portable chargers as well, so will probably keep that on me at all times.
Hi!
I've been having a little trouble with my Motorola Photon 4G this past week. So far it wasn't that bad, but it got worse during the past couple days. I've had it for about 2 years, and have to wait until February to change it. (Note: it is not, nor has it ever been rooted)
It started by just freezing and restarting at random moments. Then I had to remove the battery to restart it when it froze, because the power button wouldn't respond. It started going on reboot loops, where it would freeze, I'd take out the battery, it'd restart, and go through the restart process over and over again until the battery died. I could still turn it on. After a couple days, the battery would drain extremely quickly, to the point where to actually be able to turn it on I'd have to remove the battery, plug the phone in until the "looking for battery" icon popped up, reinstall the battery, wait for it to charge, and then turn it on.
Now, no matter what I do, it will not turn on. If I plug it in a wall outlet, it
-With the battery installed --> LED turns green, nothing pops up, power button is not responsive
-Without the battery --> Nothing happens
If I plug it in the computer, the LED turns white, but the Dual Core screen doesn't pop up. When it rarely does, it freezes there.
I have tried the whole "hold power button and volume down" (Stuck in RSD mode or something like freezes on the screen), or "hold the power button and volume up" (Fastboot freezes on the screen), and the holding the two volume keys when the Dual Core screen pops up doesn't work either.
I can't get a new contract, since I am moving away in a couple months in another country, and an US phone would be useless.
Does anybody have a solution?
Elodieme said:
Hi!
I've been having a little trouble with my Motorola Photon 4G this past week. So far it wasn't that bad, but it got worse during the past couple days. I've had it for about 2 years, and have to wait until February to change it. (Note: it is not, nor has it ever been rooted)
It started by just freezing and restarting at random moments. Then I had to remove the battery to restart it when it froze, because the power button wouldn't respond. It started going on reboot loops, where it would freeze, I'd take out the battery, it'd restart, and go through the restart process over and over again until the battery died. I could still turn it on. After a couple days, the battery would drain extremely quickly, to the point where to actually be able to turn it on I'd have to remove the battery, plug the phone in until the "looking for battery" icon popped up, reinstall the battery, wait for it to charge, and then turn it on.
Now, no matter what I do, it will not turn on. If I plug it in a wall outlet, it
-With the battery installed --> LED turns green, nothing pops up, power button is not responsive
-Without the battery --> Nothing happens
If I plug it in the computer, the LED turns white, but the Dual Core screen doesn't pop up. When it rarely does, it freezes there.
I have tried the whole "hold power button and volume down" (Stuck in RSD mode or something like freezes on the screen), or "hold the power button and volume up" (Fastboot freezes on the screen), and the holding the two volume keys when the Dual Core screen pops up doesn't work either.
I can't get a new contract, since I am moving away in a couple months in another country, and an US phone would be useless.
Does anybody have a solution?
Click to expand...
Click to collapse
Try this:
1) Power down (if not already powered off);
2) Pull the battery out;
3) Plug power in *without* putting the battery in;
4) Boot the phone.
If it does not start, we'll have to go from there. If it does start, you need a new battery.
tdhite said:
Try this:
1) Power down (if not already powered off);
2) Pull the battery out;
3) Plug power in *without* putting the battery in;
4) Boot the phone.
If it does not start, we'll have to go from there. If it does start, you need a new battery.
Click to expand...
Click to collapse
The power button is unresponsive; the LED light turns green, but the Dual Core screen doesn't appear
Elodieme said:
The power button is unresponsive; the LED light turns green, but the Dual Core screen doesn't appear
Click to expand...
Click to collapse
The light is green because it's powered and the battery doesn't need charging (not in the device). At least we have that.
Ok, this will sound stupid, but let's give it a shot:
1) unplug power;
2) remove battery (if not still removed);
3) Let it sit for a while (10 minutes would be overkill, but what the heck);
4) plug power in (not battery -- leave that out);
5) Press and hold the power and volume-down buttons for a good long time -- get a motorola screen?
If we don't get the motorola screen, could be a couple things -- screen dead? Or hardware prob (maybe the power button is dirty -- push good and hard just to be sure).
tdhite said:
The light is green because it's powered and the battery doesn't need charging (not in the device). At least we have that.
Ok, this will sound stupid, but let's give it a shot:
1) unplug power;
2) remove battery (if not still removed);
3) Let it sit for a while (10 minutes would be overkill, but what the heck);
4) plug power in (not battery -- leave that out);
5) Press and hold the power and volume-down buttons for a good long time -- get a motorola screen?
If we don't get the motorola screen, could be a couple things -- screen dead? Or hardware prob (maybe the power button is dirty -- push good and hard just to be sure).
Click to expand...
Click to collapse
The Dual Core screen comes up, with "Fastboot" in the top left corner, but it freezes on that screen
Elodieme said:
The Dual Core screen comes up, with "Fastboot" in the top left corner, but it freezes on that screen
Click to expand...
Click to collapse
i had the same issue 2 weeks ago. you need to buy a new battery as the one your using is completely drained. after that... unbrick and you should be ok.
Jonathanlc2005 said:
i had the same issue 2 weeks ago. you need to buy a new battery as the one your using is completely drained. after that... unbrick and you should be ok.
Click to expand...
Click to collapse
Silly question, but I am a noob when it comes to phones. How do I do this? I never rooted my phone
Elodieme said:
Silly question, but I am a noob when it comes to phones. How do I do this? I never rooted my phone
Click to expand...
Click to collapse
your lucky im still on the site...
heres the link
http://forum.xda-developers.com/showthread.php?t=1798145
Jonathanlc2005 said:
your lucky im still on the site...
heres the link
http://forum.xda-developers.com/showthread.php?t=1798145
Click to expand...
Click to collapse
If I have any questions, can I ask you?
Elodieme said:
If I have any questions, can I ask you?
Click to expand...
Click to collapse
im not trying to say no to be mean... i just dont have that much experience to answer all your questions you may have. your best bet is to PM the OP of that thread
Jonathanlc2005 said:
im not trying to say no to be mean... i just dont have that much experience to answer all your questions you may have. your best bet is to PM the OP of that thread
Click to expand...
Click to collapse
Okay because I'm just going to have to have everything literally spelled out for me. I wasn't exaggerating when I said I was a noob haha
As I thought, battery shot. Confuses many. So, an unbrick might not be necessary. The battery just won't even pull up the bootloader.
If you get the new battery, and you never rooted, thus didn't load the clockwork recovery hack, it should charge, and then boot might be ok. We will see, but until you see no boot at all, unbrick is the last resort since it's a slog and you're not overly experienced.
I can help, but the OP on the unbrick thread is a great help in most cases.
tdhite said:
As I thought, battery shot. Confuses many. So, an ubrick might not be necessary. The battery just won't even pull up the bootloader.
If you get the new battery, and you never rooted, thus didn't load the clockwork recovery hack, it should charge, and then boot might be ok. We will see, but until you see no boot at all, until is the last resort since it's a slog abd you're not overly experienced.
I can help, but the OP on the unbrick thread is a great help in most cases.
Click to expand...
Click to collapse
Thanks. I ordered a new battery when it started happening, so it should be in soon
tdhite said:
As I thought, battery shot. Confuses many. So, an unbrick might not be necessary. The battery just won't even pull up the bootloader.
If you get the new battery, and you never rooted, thus didn't load the clockwork recovery hack, it should charge, and then boot might be ok. We will see, but until you see no boot at all, unbrick is the last resort since it's a slog and you're not overly experienced.
I can help, but the OP on the unbrick thread is a great help in most cases.
Click to expand...
Click to collapse
it didnt charge... i tried all ways and it didnt work. it only unbricked after i bought a new battery.
Elodieme said:
Thanks. I ordered a new battery when it started happening, so it should be in soon
Click to expand...
Click to collapse
No worries -- your duty (of course) is hit the Thanks button when folks help and we get somewhere. I also fixed a couple typos in my reply (typed on a phone, and naturally ends up imperfect. Just didn't want you confused. One way or another, you can get the phone back up and running.
---------- Post added at 04:06 PM ---------- Previous post was at 03:57 PM ----------
Jonathanlc2005 said:
it didnt charge... i tried all ways and it didnt work. it only unbricked after i bought a new battery.
Click to expand...
Click to collapse
Not quite sure what you're saying, but the new battery the OP in this thread purchased should charge fine unless something is really wrong (never rooted so never loaded any charge-precluding mods).
If you are saying that on your phone, with a new battery, you still had to unbrick it because it wouldn't charge ... hmmmm ... seems very strange. Even the clockwork recovery mod would come up and then allow rebooting normally.
We'll see when the new battery comes. Hopefully no unbrick work required, just a charge.
what i am saying is that when the phone is bricked.. i mean bricked... nothing works what so ever except rsd... then thats it... it will not charge the battery. if you have a dead battery then dont expect it to charge while rsd. i needs power on the battery to allow RSD because the computer doesnt flash when the battery is dead and doesnt flash without the battery.
thus... he needs a changed battery. you could buy a seperate charger if you like... but it is much more expensive then buying a battery
Ok, I see what you're saying.
Yes, if truly bricked, it's an unbrick operation. Smells bricked, but I find it plausible the OP gets a battery with enough charge to try a boot. It is concerning we couldn't get booted on power without battery, though. That should have worked. Do it all the time working on kernel modules.
Just saying don't unbrick until trying out the new battery, the former of which the OP could do on power alone.
To qualify so no confusion -- I reboot into recovery mod without battery merely by plugin in -- so I can flash over modules. I've never been able to boot in to the OS normally without the battery in, but we still should see the moto logo.
Sent from my HTCONE using xda app-developers app