Okay, so.. I'm trying to unlock the bootloader on my phone using Carlos' video (HERE: It's an amazing guide, check it out. All files are on his post. http://www.youtube.com/watch?v=WyNtFP_TkKc) Anyways, when I flash my KDZ it says my battery level is insufficient, please recharge and reconnect when charged or something like that. But the worst part is... My battery level is at 100%. I just did a factory reset, wiped cache partition and dalvik cache and it's still doing that. I wiped battery stats before (lol) hoping that would somehow do something. This is annoying me because I've flashed KDZ's to this phone around 10 times and now when I finally want to do something it stops working lmfao.
So in short, can anyone help me?
EDIT: Never mind lol. I just realized that there's no reason for me to flash a KDZ right now and that I'm happy on stock.
Ilxaot said:
Okay, so.. I'm trying to unlock the bootloader on my phone using Carlos' video (HERE: It's an amazing guide, check it out. All files are on his post. http://www.youtube.com/watch?v=WyNtFP_TkKc) Anyways, when I flash my KDZ it says my battery level is insufficient, please recharge and reconnect when charged or something like that. But the worst part is... My battery level is at 100%. I just did a factory reset, wiped cache partition and dalvik cache and it's still doing that. I wiped battery stats before (lol) hoping that would somehow do something. This is annoying me because I've flashed KDZ's to this phone around 10 times and now when I finally want to do something it stops working lmfao.
So in short, can anyone help me?
EDIT: Never mind lol. I just realized that there's no reason for me to flash a KDZ right now and that I'm happy on stock.
Click to expand...
Click to collapse
Keep the battery below 90% at least.
Sent from my LG-P769 using Tapatalk 4 Beta
Related
Maybe a stupid question, searched the forums and couldnt really find a solid answer. Just flashed the team whiskey Bionix Fusion 1.1 on my Samsung Vibrant, with great success. Everything is working fine except my battery life is not that great. It seems i am having the same issue i had before with the radio constantly searching/ transferring data. I fixed it by doing a factory reset and my battery life improved ten fold (and it was. My question is, Can i do a factory reset with a custom rom with no ill effects? Some have said it will end up in a constant boot loop. Others say it will be fine. I want a solid answer, before i try it. I am new to the whole rooting, custom rom thing. and really dont want to go through the whole odin thing, as i am not familiar with it yet.
Thanks IN advance for your help!!
I know when I did a factory reset on a custom rom I had to do it through cw recovery. I tried to do it twice through settings (just to see if it was a fluke or not) and was in a fc loop both times. So I think cw recovery is safe for a reset but doing it through settings is not. Maybe it was just my phone though
Sent from my SGH-T959 using XDA App
How do I do it through cw recovery? Open cwrecove and have it boot into recovery, then once in recovery do the factory reset. Our is there a different way..sorry for the stupid question just want to make sure I'm doing it right.
Yea there should be an option for a reset there
Sent from my SGH-T959 using XDA App
Great! I'll give it a shot. Thanks again for your help
Sent from my SGH-T959 using XDA App
sparkyj62 said:
Great! I'll give it a shot. Thanks again for your help
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Let me know how it goes.
Just curious about the results.
Although I've never did it for the Vibrant, its generally not a good idea (it completely bricked my last phone because I messed with the kernel and didn't understand what I was doing when I did a factory reset.) Just flash back to stock with ODIN instead.
sparkyj62 said:
Great! I'll give it a shot. Thanks again for your help
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Question. Did you wipe the battery stats as the instructions told you too?
Sent from my SGH-T959 using XDA App
ShinyBuddha said:
Question. Did you wipe the battery stats as the instructions told you too?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Nowhere in the instructions does it say wipe the battery stats.
i was having the battery issue before with stock everything, and wiped the battery stats with no luck. The only thing that worked was the factory reset
Did the factory reset through CW recovery, everything works well! Making sure everything works, and so far so good.
sparkyj62 said:
Nowhere in the instructions does it say wipe the battery stats.
i was having the battery issue before with stock everything, and wiped the battery stats with no luck. The only thing that worked was the factory reset
Did the factory reset through CW recovery, everything works well! Making sure everything works, and so far so good.
Click to expand...
Click to collapse
Ah, sorry. It was in the Install instructions for the regular Bionix (although it applies for Fusion too, I'll try and get Viral to change that). XDA Bionix link.
edit: Just got confirmation that it's always good to wipe the battery stats whenever you flash a new ROM.
~SB
ShinyBuddha said:
Ah, sorry. It was in the Install instructions for the regular Bionix (although it applies for Fusion too, I'll try and get Viral to change that). XDA Bionix link.
edit: Just got confirmation that it's always good to wipe the battery stats whenever you flash a new ROM.
~SB
Click to expand...
Click to collapse
Thanks, Ill definitley keep that in mind next i flash a rom.
Apparently the factory reset didnt work. It seemed as though it is back to doing the same thing as before (seems to constantly transferring data battery)
Battery life is horrible ( dropped 25% with in an hour) and the back of the phone is very warm to the touch.
will the Flashable JI2 Modem fix this issue? if not can i just reflash fusion or should i odin back to stock and then back to fusion.
One thing i did read after i flashed this rom was to pull sim and sd card before flashing (which i didnt do) Could this be the reason for the radio issues?
Thanks again for all of your help!
I bricked mine.
I downloaded a custom rom onto my Galaxy S GT-I9000, but I really didn't know what I was doing, so I did a factory reset via settings, I wanted to go back.
BUT:
It got bricked, it got stuck on the samsung galaxy s screen forever.
One explanation would be, that when installing a custom rom, it tells you to format all partitions on the device. So I guess that the backup of the stock rom, were gone, so it didn't have anything to restore to.
Hey guys... I am not new to using odin, flashing roms, pushing stuff to sd, etc, but I have ran into a problem recently that I can't seem to fix. It doesn't matter what rom I flash and use, I keep getting random shutdowns on my phone, especially after it gets below 20%. Other people using the same roms do not have this trouble.
That being said, most of the time, I odin back to Froyo before flashing a new rom (and yes, I wait about 15 minutes without touching the phone after each flash, do factory reset/wipe, wipe dalvic cache, fix permissions, etc). The Froyo files I use are Eugene's 512.pit file and the JK2.tar file. I finally got to wondering if there was more of a problem with the base files I'm using, so then flashed the listed files using odin (which is what I use to "start fresh" before each new rom) and found out that I am still getting random shutdowns!
I really am not sure what to do... do I need to completely blow everything away (as in doing something that will erase everything - music, photos, etc. which normally doesn't happen), unroot, re-root, and take it from there? Am I using old files that are known not to work so well anymore? Any suggestions?
Try fixing permissions in CWM the wipe dalvac and cache. If that doesn't work try factory reset
Sent from my SGH-T959 using xda premium
i have done all that you listed... do it every time after i flash a new rom but it still shuts down...
When is the last time you calibrated the battery?
I remember someone else having g this issue and its related to the battery percentage. As if the phone thinks its at dead battery when its not.
Sent from my SGH-T959 using xda premium
well, i don't do the full calibration i don't think... what i do is: after i flash a new rom, i charge it all the way up, plug and unplug it a few times to make sure it stays at 100%, then (while it is still plugged in) i reboot into recovery and wipe the battery stats. most of the time that's it, i don't let it charge all the way to 0% and then charge all the way back up again.
but i don't think that's the problem because even when the battery says it is still at 50-75% i still have the problem... albeit not as often.
i'm thinking of usin odin to go back to the un-rooted stock and see if that fixes it... from there i can re-root and flash the rom i want.
Let me know if that works, im interested to see if it works! Good luck.
Sent from my SGH-T959 using xda premium
don't if it will help, but try odening back to jfd. I never odin back to froyo always jfd when I want a fresh start. Try running jfd and see if it still reboots. If so then your phone is defective. Also a while back I remember this happening on simply honey and other gb roms. I forgot what the fix was though.
thanks guys... am in the process of going back to jfd now, sure hope that works! i followed sn15's guide on this and actually reformatted both internal and external card as well to wipe everything. i will keep you all posted if it works...
Could it be a hardware issue? How 'bout on stock, does it still do it? Do you have a case on the phone that it might be pushing the power button down that its causing a forced shutdown? Is the power button getting stuck somehow? Have you tried cleaning the hell out of the contacts (battery & phone) and made sure that the contacts are in fact making a good contact? Luck homie.
Yeah definitely give JFD a shot. Root and reflash. I only really ever use Eugene's JK2 if my partitions get mess up or something. If it's still doing it after that then it could be a hardware issue like someone else said.
just wanted to give an update...
after i flashed JFD my phone was still randomly shutting down some, so i decided to give the battery a shot (as was mentioned above) just to see if that was indeed the issue. i switched batteries from the extended battery i was using back to the stock battery. i reconditioned it in JFD following s15n's advise. i have not had any more issues after this! i believe this worked... thanks for all the advise and help.
I have JXD s7100B with Android 2.3.4. After rooting it and killing cell apps (and all unnecessary apps) it's battery lasted about 4 hours and it was OK. I used Battery Calibration from Google Play to try and get some more and after that it started acting weird: It could not boot (it would loop the bott screen) unless it's on the charger. After it boots it would drain the battery in less than 20 minutes! When I try to charge it it would charge to full in 10-15 minutes but when I disconect the chatrger, it will again last <20min.
After a few days it started acting normaly (booting and battery life) but few days after that it started the same again:cannot boot unless on charger and lasts <20min. I tried recalibrating battery again with Battery Calibration, reflashing firmware with custom rom and with original rom from the manifacturer - nothing. It still acts the same.
Once, while using bitrider's custom rom (I still can't use URL's ), I booted it and got black screen with no icons nor drawer (i guess launcher crashed) but with only the notification bar (battery level notification, working clock) and touch screen not working. I left it like that to see how the battery will work and it lasted normaly! After that I experimented with two original firmwares from the manifacturer and it drained battery fast like before. If I start JXD in restore mode battery lasts long there too.
So my guess is that battery is OK but software somewhere in Android is reading baterry level of 100% as 100% but of 97-98% as 15% and it forces power off although battery has juice to power the tablet. Is there an app that can tell to Android how to see battery or could I do it by editing the firmware somehow. Enything to make it work like it did.
Do you have a custom recovery? If so, I think there is some way to delete the battery configuration files from recovery. You charge the device until it says it's full, delete the files via recovery and then boot normally again. Then the OS will regenerate the files.
This is the same thing Battery Calibration should do, but maybe it's doing it wrong or something.
It could also be that you have some app that is draining the battery. This would explain why the battery lasts longer when no apps launch. Install BetterBatteryStats from the market to see if some app you have insalled is causing wakelocks (these drain your battery a lot). It is a paid app, but if it fixes your battery life, it's well worth it. You should probably try this before the other thing with the recovery.
Thanks for quick answer
SifJar said:
Do you have a custom recovery? If so, I think there is some way to delete the battery configuration files from recovery. You charge the device until it says it's full, delete the files via recovery and then boot normally again. Then the OS will regenerate the files.
This is the same thing Battery Calibration should do, but maybe it's doing it wrong or something.
Click to expand...
Click to collapse
Did that and nothing changed . I charged it to full and used Root explorer to delete batterystats.bin in /data/system and OS made another one but it did nothing.
SifJar said:
It could also be that you have some app that is draining the battery. This would explain why the battery lasts longer when no apps launch. Install BetterBatteryStats from the market to see if some app you have insalled is causing wakelocks (these drain your battery a lot). It is a paid app, but if it fixes your battery life, it's well worth it. You should probably try this before the other thing with the recovery.
Click to expand...
Click to collapse
Done (on your advice): nothing on the lists last longer than 20 seconds (I've just turned it on and let it drain). Application doesn't explains why I can't start it without charging it, why, when I deplet it, I only need to charge it 10-20minutes to full and why it happens on three diferent firmwares (Theoreticaly, maybe the same firmware - one on english, one on chinese and one made from chinese, but that chinese (original) worked normaly before Battery Calibration).
Well, apologies for making you waste money on that app when it didn't help then
Have you tried reinstalling stock ROM after doing a wipe in recovery first and just starting all over again?
SifJar said:
Well, apologies for making you waste money on that app when it didn't help then
Click to expand...
Click to collapse
No problem, we are trying to fix something more valuable here .
SifJar said:
Have you tried reinstalling stock ROM after doing a wipe in recovery first and just starting all over again?
Click to expand...
Click to collapse
I've reinstalled stock ROM a few times but I didn't do wipes. I just did it one after another. I'll do a "wipe data/factory reset" from recovery mode and then install stock ROM. I'll post here what happened.
scivias.a said:
I've reinstalled stock ROM a few times but I didn't do wipes. I just did it one after another. I'll do a "wipe data/factory reset" from recovery mode and then install stock ROM. I'll post here what happened.
Click to expand...
Click to collapse
That might be the problem then, I believe installing new ROMs without doing a "wipe data/factory reset" can sometimes cause issues.
Same . I've done data wipe/factory reset from recovery mode (it has nice "are you sure" screen 7 "No"s + 1 Yes + 3 "No"s) and then installed stock chinese ROM but again battery starts draining 3-4% per minute. Is there a partition in Android that doesn't get wiped with factory reset?
The system partition does not get formatted when performing a wipe "data/factory reset". Can you check to see if you can format the system partition in recovery?
That's an interesting information. I'll see if I could format it somehow. Options that I have in recovery are:
-reboot system now
-apply update from sdcard
-wipe data/factory reset
-wipe cache partition
-wipe media partition and
-reboot into factory test
Has anyone ported clockworkmod recovery for your device? If so, that recovery has the option to format system. Has someone created an all in one wipe that included formatting system for your device?
Sent from my SPH-D710 using xda premium
Any super wipe script should work
It sounds to me like your battery is actually faulty. Try another battery, or put yours in the freezer for about 30 min, then charge.
Sent from my PC36100 using xda premium
Fixed it!!!!
User named Friend on the apad forum posted that he found somewhere how to fix this issue and I tried it and fixed it. Thank you all who tried to help me - it is nice to see normal, helpfull people on the net. Thank you very much. Here's how I did it with the image for an easier orientation: goo.gl/XpC5I (can't post urls yet but this works. It leads to apad forum where it all started). All the best.
Glad you were able to fix it and good luck with your tablet. Hope everything goes well.
Sent from my Galaxy Nexus using xda premium
First off, hello to everyone.
I tried to root my S3 and messed it up. Now when I start my mobile, the samsung logo appears and nothing else.
Can anyone please help me sort this out? Maybe a way to flash or reset it?
Have been trying for a week now and getting nowhere.
Any help would be very appreciated.
Thank you.
If you can get to recovery, wipe cache and dalvik cache & reboot.
If you want to start again then reflash stock rom with ODIN. Then flash cf-root ver. 6.4 with ODIN. You now have stock, rooted rom....
ultramag69 said:
If you can get to recovery, wipe cache and dalvik cache & reboot.
If you want to start again then reflash stock rom with ODIN. Then flash cf-root ver. 6.4 with ODIN. You now have stock, rooted rom....
Click to expand...
Click to collapse
Thanks it worked. Still getting cell standy issue.
Don't worry about cell standby issue. Is just an error in reading actual usage.
Sent from my GT-I9300 using xda app-developers app
Arsaw said:
Don't worry about cell standby issue. Is just an error in reading actual usage.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Need to charge battery every 12 hours still, cell standby is at 56%?
limewithcoke said:
Need to charge battery every 12 hours still, cell standby is at 56%?
Click to expand...
Click to collapse
Cell standby issue is just because Samsung made a mistake in the way the stats are reported in the battery stats.
It thinks the draw is 35ma when in fact it is actually 3.5ma, it has no effect on the actual drain, just how its reported.
Also poor signal will increase cell standby battery drain.
Sent from my GT-I9300 using xda premium
limewithcoke said:
First off, hello to everyone.
I tried to root my S3 and messed it up. Now when I start my mobile, the samsung logo appears and nothing else.
Can anyone please help me sort this out? Maybe a way to flash or reset it?
Have been trying for a week now and getting nowhere.
Any help would be very appreciated.
Thank you.
Click to expand...
Click to collapse
I have similar problem with my s3. It keeps crashing after rooting. I have unrooted my phone in order to fix that out but no luck so far.
First I did use an Odin to download original android system onto my phone. When that didn't work, I used Kies and Emergency Firmware Recovery, unfortunately with no positive result.. Phone seems to be working quite fine until unexpected rebooting happens. On and on at least 20 times a day! That really pissing me off bcoz it happens in the middle of important chats or calls
Is it possible that I did something wrong while rooting and i've damaged my phone? Is there any way to figure out what had happened to my s3? perhaps so kind of diagnostic tools?
Your input would be greatly appreciated
I have done searching and reading but I just want to double check before I break something. Is it safe to flash EMG4 over the new 4.3 update without loosing IMEI? they both use the new format of reading the efs folder right? so it should be OK? And if it all goes wrong I can restore EMG4 efs backup or go back to 4.3 to restore IMEI?
well, from what i've read, it looks that it is the good solution.
i might try it later (when back from work )
if someone can confirm before i'd be grateful too.
I wanna know as well
Just do it, both EFS are compatible. Just your internal card won't bi at same mounting point (now is in /0 folder).
Sent from my GT-I9300 using XDA Premium 4 mobile app
You got it right, no problem ahead :good:
i did this went from BTU 4.3 to BTU MG4 and got a boot loop, only way to get back is to clear user data and cache wipe etc in recovery mode before you flash MG4.
I thought so but it is best to check first instead of just doing stuff and then trying to fix it after. To be fair 4.3 isn't working out too bad for me now. I tried to get away with just clearing cache but it was horrible. I got 8hrs battery life with light use:silly: and LAGS all over the place. So I drained the battery and left it out for 40 min, then fully charged while off then switched on and factory reset. I got 20hrs light/moderate use with WIFI always on after that. I will see how it goes but second battery cycle is looking OK so far......
flashbackvictim said:
I thought so but it is best to check first instead of just doing stuff and then trying to fix it after. To be fair 4.3 isn't working out too bad for me now. I tried to get away with just clearing cache but it was horrible. I got 8hrs battery life with light use:silly: and LAGS all over the place. So I drained the battery and left it out for 40 min, then fully charged while off then switched on and factory reset. I got 20hrs light/moderate use with WIFI always on after that. I will see how it goes but second battery cycle is looking OK so far......
Click to expand...
Click to collapse
In your custom recovery wipe the cache again but this time try wiping the dalvik cache aswell.