On ICS leak #1 I went to downgrade ro 2.3.6 using RSD Lite (done many times before, no problem) and the flashing starting perfeclty fine as usual. However I didn't realize that the battery level was on the borderline of being considered "low", so although it was high enough at the beginning, it must have crossed the threshold during flashing and it FAILED right in the middle of the process, mid-flash.
Now I can only turn the phone on into fastboot, and of course the battery can't be charged in this mode, so I can neither recharge the battery nor re-flash anything in this state, so it would seem that I'm stuck.
Do I have any options?
EDIT: Well, I just noticed the "Bricked" sticky thread and so will try to move this question over there... which means I suppose this thread can be deleted...
Related
Alright, well my phone won't turn on at all, as if there were no battery in or something, this is the result of several stupid things i did to it. It began with a not so stupid thing, i flash some new roms on it, was trying out a few, then eventually put stock back on and applied voodoo lag fix. well then i had some issues with haptic feedback so via odin i flashed stock back on it, without disabling lag fix or doing anything first. Well that wasn't such a huge problem as i could still get into recovery and all and so i assumed that it could be fixed somehow. Well after a few hours i got impatient and did something that i don't understand at all, but it resulting in my phone being in the stat it is right now. i download the file "s1_odin_20100512.pit" then i opened odin and put it in the PIT section. I checked Re-partition, Auto Reboot, and F. Reset Time. I hid start, the phone took it, odin showed success, only the phone hasn't done anything since shutting down. Please help me, and I really appreciate any taking the time to think about this.
[Edit]: Okay i think it might be more helpful to just as "Is there anyway to go from no software on the phone at all to put software on it?" I think this is basically the only it could be fixed since there's no way to access it to re flash the kernel, rom, etc.
Does the phone energize if it's plugged in to A/C? Despite the battery...
no
no, the phone doesn't do anything, although i do believe that it is charging because the battery warms up, im weary to leave it on the charger though because idk if it will overcharge without active software. But to be clear, it has the same issue when plugged in as when a only battery, it does nothing what so ever no matter what i do. Thanks for the reply btw.
did anyone get this figured out?? please let me know!!! I am having the same problem; it won't even show charging... and i can't go into download mode for Odin
I've searched the forums and have not seen anything quite like my problem, so if I missed an important thread, I'm sorry.
Over the weekend, I plugged my Captivate (using a stock battery) into the official Samsung charger and overnight my roommate semi-dislodged the charger. When I woke up and grabbed my phone it only registered a few hours of charging yet still had almost full battery. Upon rebooting the phone, I was sent into a bootloop. Not at the ROM, not at the Kernel, not even at the bootloader. It goes so far as to show the white loading ring at the center of the screen which never moves. At one point, a thin pink line appears halfway through the screen as it shuts down and reboots, never making it any farther. If I plug the phone in, it will boot normally though it does not accurately report battery levels or charging.
Other oddities: after 5 minutes of a phone call, the phone hard crashes. Not FC's, but just goes black. Upon a reboot, I get stuck into the same boot loop. If I plug the phone into the wall charger without a battery, it will go into the turned-off charging animation and show a 100% charged battery. Furthermore, my other roommate has a brand new i9000 so I tried that battery (again, stock Samsung) and it continues in the same bootloop. I have tried flashing other ROMS and going back to stock, but that does not seem to help.
Other info: I was running OneCosmic's ICS 3.1 with no overclock and light undervolting at the time. It was perfectly stable for the few days until the charger dislodged. I am also out of warranty and am not eligible for a hardware upgrade so repairing my Captivate would be ideal. I also have a usb jig if that is of any use to this scenario.
Has anyone experienced anything remotely like this? If not, what debugging steps should I attempt?
What I would suggest is using one of the ODIN one clicks and flash back to stock
Sent from my SGH-I897 using xda premium
I've flashed back to Rogers 2.2 stock. Doesn't help. It actually made it harder for me to get the phone started though I have yet to make a phone call from it.
Have you had the phone for less than a year? if so call at&t(or rogers) and they'll replace it for you.
then try factory reset
then try using odin or rom manager to flash back to stock
When all else fails, flash to cm7. that will completely wipe everything and start from scratch.
if that STILL dost work.... than you can be sure that its a hardware problem :/ theres nothing you can do except replace and sell for for parts.. sorry
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Skoffer said:
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Click to expand...
Click to collapse
I have exactly the same problem, I did the reset of the battery stats and still not working.
Did you solve the problem?
thanks
Martin
Thanks to everyone for their suggestions, however, no amount of battery calibration could get it to work. Furthermore, a bad flash has made the situation even worse. Now Im bootlooping even when plugged in and when unplugged my jig is of no help. I have declared my Captivate dead.
Best of luck toominds, if you get it to work, let me know. I'd love to have a spare phone sitting around.
Hi all, I have a Lenovo A1107 tablet running stock ICS. It began powering down when it reached <50% or so and gradually climbed the % scale to the point where now it is does it at 98% and while plugged in. I have searched for hours and tried few troubleshoots (cleaning up system resources such as apps, home screens etc..., factory reset, airplane mode) but no luck finding a fix.
This problem has become seriously annoying and I just can't seem to narrow down what the problem is. Does anyone have any ideas? Thanks much!
Well, after thinking about it more I realized that the problem seems to be that for some reason or other the system isn't registering the device getting charged, even though the battery indicator says it is charged (90%, 98%, or whatever). The reason it got progressively worse (first starting at @50%, then at 80% and so on) was because even though the battery was getting charged the system was being told that it hadn't. That is why eventually it would power down almost as soon as it turned on, just like it would if the battery were completely dead. The reason I know that is not completely dead and not the battery indicator that is in error is because I could boot into recovery mode and stay in that for well over an hour, despite the fact even that the device will not boot into recovery mode if it is <30% or whatever.
So, I guess the best question would be.......what part of the system communicates between it and the battery? The part that says "no/low power so shut down"?
All moot now as I just took the tablet back and got a different one. Thread closed.
I am hoping someone can help me here.
My notepro was working fine, except for the screen flicker issue. I wanted to root it in order to adjust voltage and a few other things to try and prevent the flicker.
I was able to install TWRP, and SU and verified it was now rooted. I then went and tried to install a custom ROM http://forum.xda-developers.com/gal...-civzp900lollipop-5-0-2-aroma-12-jul-t3155589
Everything seemed to install fine, the kernel, ROM, all that. However, when I restarted the device, i got stuck on the bootloader with the seanandroid red warning message. It would not load past this. So, i wiped and reinstalled everything several times over, and still no fix. I searched online and found a zip you could flash to fix the booting issue, but no help. I wiped everything except the extsd and reinstalled ROM and everything. Now TWRP says no OS and I am still stuck on the bootloader screen. i cannot do anything at this point.
After a bit it started flashing and flashing faster and faster. This was after sitting with the bootloader screen showing for a while. I assume battery ran out, but every time I tried to charge it, it either tries to show the battery charging from the off screen, but just gets frozen, and then starts to flash again.
I am letting it sit right now. I am thinking the temp or voltage spiked due to low battery power, but I am not sure.
Can anyone offer some advice?
I am thinking at this point it might be the motherboard.
After it started flashing, it would get so bad that the screen would fade out and then back in. Now, it wont do anything, and wont even indicate charging. Sometimes it did, but would just show the battery icon with a loading circle in the middle and never actually show it charging. now its just dead.
There is no way that rooting and installing a rom could have done this. i am thinking it is a hardware issue.
My choice now is to part out the pieces that work and scrap the mobo or to replace the mobo
Have you opened it up and taken a look at the battery connector to see if resoldering would help?
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Sent from my SM-P900 using Tapatalk
batt connector seems fine. It seems that if I let the device sit for a white it will spark a little life and then die off again. Its rather odd.
disconnected the battery and plugged it in. was able to boot into recovery temporarily. however, it only works for a few min. tried to flash stock kernel and it had an issue, reloaded twrp itself and then would not read anything on the extsd and died.
i was to flash stock, but the stock file I have is .zip and odin will not recognize it to flash in download mode.
Ive rooted and flashed many devices before, but its been a long while since I did. A year at least, and not on this device.
At this point I am assuming that the mobo is the issue, but I am not sure. It was having the screen flicker issue before, which seemed to be heat or voltage related.
If I cannot fix this, i will likely just sell it off for parts. The screen, batt, all that should be fine otherwise.
ok so im working on a nexus 5. i was already all too aware of the potential power button issue so that was the 1st thing i checked out, ive cleaned it twice now and made dbl damn sure i can feel it both click in and click out when being pressed.
on top of that i can boot into twrp both temp boot and flashing recovery for it. it does not cut off when in twrp (as i imagine it would if it were the power button being stuck)
previously i could not boot into twrp or flash anything at all so i ordered and installed a breand new battery.. now i can flash twrp via fastboot (progress right?)
however when it is powered off, on teh charger it shows the battery full with lightening bolt, then that fades and is replaced with a hollow battery being filled, then goes black and starts over... leading me to believe its not taking any charge in..
ive tried stock 7.1.1, stock 7.0.1, stock 6.0.1, cyanogenmod 14 and even ran the NRT by Wugs... i have wiped everything, i formatted data and made sure the partition was correct pre-flashing by running NRT to return stock values n such, i have also tried different approachs to flashing. fastboot flash system, adb sideload, twrp install zip and NRT...
with my small (yet excessive) experience so far with android im led to believe this is being caused by some sort of conflict inside the system memory, it almost has a rythym to when it cuts off, like when it hits block such n such it goes "OUCH DAMMIT" and retreats for safety (powering off)
you'll have to forgive me for starting a new thread, the only info i can find pertains to the power button which i am fairly confident it is NOT, and after hours of searching tonight alone im really not for diffing thru every thread, i did however do a quick search prior to posting....
Where did you get the battery? Tried different USB cables and chargers? The phone boots and runs properly on stock?
I had a similar problem. I talked to LG customer support and they were aware of this issue and suggested that the whole logic board needs to be replaced. Apparently this is common with LG devices.
A workaround that worked for me is to turn off the phone for 1 day (let it cool down), clean flash whatever rom you like, then flash ElementalX kernel with the CPU under-clocked to minimum.
I have tried various ports and cords, battery from a top seller on ebay (checked reviews prior) and I cannot boot into stock Android either... During my extensive tweaking of the device last night I relocked the bootloader while returning to complete stock... After doing such I later tried some thing I saw suggested on the forums, removal of the power button.. so I desoldered it.. didn't change anything so it's def not the button... However now I cannot click the screen to confirm unlocking the BL again so I'm close to boned as far as flashing options ATM... Lol fail...
If it is a motherboard problem, and it sounds like it is, the cheapest solution may be to buy a used Nexus 5 with smashed screen and working motherboard. Swapping the motherboards is quite simple.
That's probably gonna happen, I don't see many other viable options .... It's not my phone so imma be putting money into someone else's to save face. U don't get a broke device back from me
Thanks guys