Related
Hey guys i've a problem with my x10
So one night i was playing with it than the other day the phone would start
so i thought yeah right might be the battery or something. i took it to my friends x10 it was with 87% charged so i exclude this
Than i tried to flash with flashtool a new kernel and i get stuck at 9% or 15% depending on the kernel i use.
With SEUS it starts to repair but it says. No new updates avaiable after a few moments.
Some information regarding my phone
Unlocked Bootloader
FXP KERNEL
MM TEAM MIUI V4
The phone vibrate but doesn't start or load the kernel.
What do i do?!
Srry for my bad english
Thx in advance
Usrle flashtool to reflash kernel or firmware.
already did but i get stuck at 9% or 15% flashing the kernel
I'm downloading a full generic rom x10a
having similar problem
Hi, I had similar problem as well
X10i running FXP CM7 suddenly just wont boot n charge after I turn off the phone
it wont boot after flashing anything (firm or kernel) except the official firm
now that I end up with a cap R bootloader but flashtool claim that bootloader is rooted
do I still keep the bootloader unlock?
i guess you have a locked bootloader since the original firmware is loading just fine even tho rooting has nothing to do with the bootloader it self. i'm only guessing.
I'm stuck at. Flashing Loader
I bricked my phone last week and it got stuck in a boot loop.
I downloaded the x10a generic Stock ROM and flashed it via Flashtool and it worked like a charm.
Hope this helps.
[XBOCT]™ said:
I bricked my phone last week and it got stuck in a boot loop.
I downloaded the x10a generic Stock ROM and flashed it via Flashtool and it worked like a charm.
Hope this helps.
Click to expand...
Click to collapse
But that way you weren't at a brick point.
You get brick when u get those 3 blink red LED and the phone doesn't do anything
By the fact that your phone were able to load the kernel. i guess
same problem repeat
Hi, just confirm that the bootloader remain unlock as long as the flashtool claim its ROOTED
had you try other than official 2.3.3 ftf?
because I just got the same unable to boot problem repeated again
this time cant get boot on even stock 2.3.3 firm
but I was able to boot up and charge on 2.1, then get root, recovery and kernel (w/o unlock bootloader again) and go straight to custom ROM with no problem
mooving said:
Hi, just confirm that the bootloader remain unlock as long as the flashtool claim its ROOTED
had you try other than official 2.3.3 ftf?
because I just got the same unable to boot problem repeated again
this time cant get boot on even stock 2.3.3 firm
but I was able to boot up and charge on 2.1, then get root, recovery and kernel (w/o unlock bootloader again) and go straight to custom ROM with no problem
Click to expand...
Click to collapse
i'm using
X10a_2.1update1_r2.1.A.0.435_Generic.ftf
And it get stuck at Flashing loader
Idk but i can "read" the kernel when i dump the propriets but i can't "right" when i try to flash something
Anyone?
guys?
you said your phone is "bricked"
I'm not sure if you know what that means.
If you say you've bricked your phone then no one can help you.
A brick is a brick. It doesn't matter if it weighs a few kgs or a few hundred grams. A brick can't receive phone calls.
And your phone isn't even a normal brick... You wrote that it's "really bricked"
Are you building a house anytime soon?
LJE said:
you said your phone is "bricked"
I'm not sure if you know what that means.
If you say you've bricked your phone then no one can help you.
A brick is a brick. It doesn't matter if it weighs a few kgs or a few hundred grams. A brick can't receive phone calls.
And your phone isn't even a normal brick... You wrote that it's "really bricked"
Are you building a house anytime soon?
Click to expand...
Click to collapse
maybe i'm wrong idk maybe is a soft brick. thats why i'm asking for some help.
almomdegal said:
But that way you weren't at a brick point.
You get brick when u get those 3 blink red LED and the phone doesn't do anything
By the fact that your phone were able to load the kernel. i guess
Click to expand...
Click to collapse
The red led blinking rapidly three times means the battery is "out of juice".
I've said it earlier: Several X10 devices have reached an age, where battery failures are fairly common due to charge cycles and/or age. Specially if one got it just after the launch.
Anyhow, what you can do, is let the device charge "blindly" for a while, and a while I mean for half an hour to a few hours. Then it should, out of the blue, jump into "active" charging (With the battery screen showing offline charging)
If this doesn't happen you might have to charge the battery externally.
...or even replace the battery.
-"Why?", one might ask.
Reason is that the flash mode only works with a charged battery.
If it empty, it won't engage the flash mode at all. Stupid design, yes, but that is how it is.
Worst thing is, that the battery does deplete/discharge while in flashing mode. That is why it's so important it's fully charged and fully working, before one engages in flashing activities.
See this post for more information about this: http://forum.xda-developers.com/showthread.php?t=1642154
Try wotanserver's flashtool...
http://www.wotanserver.com/en/
Good luck
SysGhost said:
The red led blinking rapidly three times means the battery is "out of juice".
I've said it earlier: Several X10 devices have reached an age, where battery failures are fairly common due to charge cycles and/or age. Specially if one got it just after the launch.
Anyhow, what you can do, is let the device charge "blindly" for a while, and a while I mean for half an hour to a few hours. Then it should, out of the blue, jump into "active" charging (With the battery screen showing offline charging)
If this doesn't happen you might have to charge the battery externally.
...or even replace the battery.
-"Why?", one might ask.
Reason is that the flash mode only works with a charged battery.
If it empty, it won't engage the flash mode at all. Stupid design, yes, but that is how it is.
Worst thing is, that the battery does deplete/discharge while in flashing mode. That is why it's so important it's fully charged and fully working, before one engages in flashing activities.
See this post for more information about this: http://forum.xda-developers.com/showthread.php?t=1642154
Click to expand...
Click to collapse
Didn't work, i even use my friends battery to flash it and it didn't work
almomdegal said:
Didn't work, i even use my friends battery to flash it and it didn't work
Click to expand...
Click to collapse
Well, if the battery issue was fixed, and you're sure the battery is fully charged, then try this: (Quoting from my other post)
I've charged/replaced the battery, and are having trouble with starting up. Earlier flash failed. Now what?
Don't worry. It's pretty darn hard to truly brick this device. Even if the screen remains black, there's still hope.
Once that the battery issue has been dealt with, you can move on:
Download the latest Flashtool and the proper global firmware (FTF-file) for your device from here:
http://forum.xda-developers.com/show...ight=flashtool
1: Extract/Install the Flashtool to a folder of your liking.
2: Copy the ftf-file to the "firmware" folder in the Flashtool folder you just created above.
3: Start Flashtool. Click the Bolt icon (flash). A Window appear. There, choose "flashmode". Cllick OK.
4: A new window appears. In the list on the left, choose the Generic firmware you downloaded and copied into the "firmware" folder. Should have a similar name as the file itself. (Or manually open the ftf-file from the "..." icon on the top right.)
5: Hit "OK. Follow the instructions you get on the screen:
1 - Unplug the device.
2 - Power off the device. (Unplug and replug the battery to be sure it really off, and not stuck in black screen)
3 - Press the "back" putton, and hold it down while performing the next task.
4 - Plug the device into the computers USB.
Click to expand...
Click to collapse
Forced flashing should now start.
Click to expand...
Click to collapse
time to accept the fact that it is really brick
Hi @almomdegal,
if you try flash using another full charge batt n its not work, I think this forum is no longer works for u anymore.
I own a faulty X10 as well, random shut down (no warning at all) then wont boot n charge
reflash it, revive for few days and dead again, and reflash....
now it is really dead, no problem appears and it show flash successful and it just wont boot or charge but vibrate non stop
I just send the phone to service center and the board need to be replace
so its time to send to the real professional to solve it, coz this problem ain't software downloaded from internet can solve anymore
mooving said:
Hi @almomdegal,
if you try flash using another full charge batt n its not work, I think this forum is no longer works for u anymore.
I own a faulty X10 as well, random shut down (no warning at all) then wont boot n charge
reflash it, revive for few days and dead again, and reflash....
now it is really dead, no problem appears and it show flash successful and it just wont boot or charge but vibrate non stop
I just send the phone to service center and the board need to be replace
so its time to send to the real professional to solve it, coz this problem ain't software downloaded from internet can solve anymore
Click to expand...
Click to collapse
yeah i guess so.
I just needed this closure i'll send it to service today
Morning everyone
i have tried to search the forums with a similar problem, but i couldnt find a solution to this.
NOTE; If there is, please provide a link to the post, i'll appreciate that.
So this is what happened :
i flashed the phone with custom rom ( MiniCM9/JB/ICS) successfully..but after finding that the camera didnt work with one of the roms ICS i think, i reverted back to the original e10i kernel.
the problem with this is that PC Companion couldnt update my phone, as it didnt recognise it, it only said SONY/SONY ERICSSON phone..apart from that, the battery seems to have died out, i tried charging it on the wall plug but it would boot up and display the SONY ERICSSON logo and after a few seconds, restart. it doesnt seem to charge the phone but rather gives it a 'boost' to boot up. it does the same thing when plugged in the laptop. Now, the baterry seems to have been depleted completely as the red led flashes while still connected in flash mode.
I expected a big battery icon to display when i charged it on the wall plug but i got the boot logo...and restarts..SEUS said i have the latest software..PC companion couldnt ''repair'' it because the battery would run out while still connected in flashmode.
Please assist me in anyway.
thanks
AGAIN : if there is a problem somewhere in the forums PLEASE direct me to it, i dont wanna cause any spam on the forums.
Thank you
hands360 said:
Morning everyone
i have tried to search the forums with a similar problem, but i couldnt find a solution to this.
i flashed the phone with custom rom ( MiniCM9/JB/ICS) successfully..but after finding that the camera didnt work with one of the roms ICS i think, i reverted back to the original e10i kernel.
I expected a big battery icon to display when i charged it on the wall plug but i got the boot logo...and restarts..SEUS said i have the latest software..PC companion couldnt ''repair'' it because the battery would run out while still connected in flashmode.
Click to expand...
Click to collapse
Your main problem is that you still have the custom ROM although you're back on stock kernel. Try to flash this with flashtool.
downloading
SmG67 said:
Your main problem is that you still have the custom ROM although you're back on stock kernel. Try to flash this with flashtool.
Click to expand...
Click to collapse
Thanks bro..i'm downloading it now will try it after an hour or so..have to go to a friends house for a laptop..thanks to lighting storm. Anyway i'll keep you updated with the process.
After doing so can i flash custom rom?(i'd like to think so, just confirming to ease my conscience lol) and currently which is the most stable rom between the aforementioned roms? Just looking for your opinion.
Thanks again.
hands360 said:
Thanks bro..i'm downloading it now will try it after an hour or so..have to go to a friends house for a laptop..thanks to lighting storm. Anyway i'll keep you updated with the process.
After doing so can i flash custom rom?(i'd like to think so, just confirming to ease my conscience lol) and currently which is the most stable rom between the aforementioned roms? Just looking for your opinion.
Thanks again.
Click to expand...
Click to collapse
Yes, your bootloader will remain unlocked, so you will be able to flash custom kernels and roms, no problem.
They are working on a fix for the camera, and the first one updated will be MiniCM9 i think, but for now MiniCM7 (or other gingerbread based roms) remains the best performing option for our phones.
fail
SmG67 said:
Yes, your bootloader will remain unlocked, so you will be able to flash custom kernels and roms, no problem.
They are working on a fix for the camera, and the first one updated will be MiniCM9 i think, but for now MiniCM7 (or other gingerbread based roms) remains the best performing option for our phones.
Click to expand...
Click to collapse
Smg, i tell you, Yesterday was not my xperias day. My data bundles depleted while it had gone 80% (i think) into the download, i then recharged for another 100MB unfortunately i was using my ageing 6730c on Opera mini n the download couldnt resume! So i'd like to know, how big is the file itself because when it started, it said 114MB it reached that size and kept on going till 188MB i guess that's how much bundles i had. Anyway will try to get a wifi hotspot.
I think i'll go with the MiniCM7 for now till further development is made for these ROMS. A very big up to the developers.
Till i get that file! Later
hands360 said:
Smg, i tell you, Yesterday was not my xperias day. My data bundles depleted while it had gone 80% (i think) into the download, i then recharged for another 100MB unfortunately i was using my ageing 6730c on Opera mini n the download couldnt resume! So i'd like to know, how big is the file itself because when it started, it said 114MB it reached that size and kept on going till 188MB i guess that's how much bundles i had. Anyway will try to get a wifi hotspot.
I think i'll go with the MiniCM7 for now till further development is made for these ROMS. A very big up to the developers.
Till i get that file! Later
Click to expand...
Click to collapse
Yes, sorry about that.. it's the original SE stock 2.1 firmware and it comes in at about 210mb, although the site keeps saying differently, i don't know why it does that. You need to flash it with flashtool.
success
hey bro....guess what..it worked. I ended up downloading the file via a blackberry lol anyway it was 210MB...215 in fact..anyway my phone is fixed and ready for customisation. A very big Thank u man. I'm just waiting for it to fully charge because it was completely drained i was lucky it survived the original stock flashing.
Thanks for the time and energy you put in. I really appreciate it. Cant wait to get my Samsung Galaxy Gio lol i know its a bit old now but it hasn't seen the 'other side' of the grass.
i am suffering from a strange problme...dunno whether its rom or kernel related
i am on odexed xxlsj using philz kernel
whenever i reboot my phone after flashing something from cwm, by battery percentage goes down by about 20%
it happens only once in one charge cycle
if my charge was at 54% before flashing the file,after rebooting it goes down to about 30-35%
y is this happening???any help pl
tried to search,but couldnt get satisfactory answer
also ENTROPY,elite recognized dev , said that resetting battery stats is useless in our beloved s2 i9100
Thats a common issue.
If your rom support Siyah kernal ( most probably it will) then flash it & install extweak from Play store.
And then reset Battery Chip and put your phone to sleep it will go back to normal.
Btw don't worry that 20% will give you same time uptime as 54%
bluepratham said:
i am suffering from a strange problme...dunno whether its rom or kernel related
i am on odexed xxlsj using philz kernel
whenever i reboot my phone after flashing something from cwm, by battery percentage goes down by about 20%
it happens only once in one charge cycle
if my charge was at 54% before flashing the file,after rebooting it goes down to about 30-35%
y is this happening???any help pl
tried to search,but couldnt get satisfactory answer
also ENTROPY,elite recognized dev , said that resetting battery stats is useless in our beloved s2 i9100
Click to expand...
Click to collapse
Maybe try to charge to 100%, then turn of your phone, remove your battery for about a minute and then boot again. It's supposed to work Let me know
Chairmansaab said:
Thats a common issue.
If your rom support Siyah kernal ( most probably it will) then flash it & install extweak from Play store.
And then reset Battery Chip and put your phone to sleep it will go back to normal.
Btw don't worry that 20% will give you same time uptime as 54%
Click to expand...
Click to collapse
He's on LSJ, so Siyah doesn't work
Sent from the Matrix
That is normal, when you flash something, the battery will go down about that.
Once developers are able to do some battery tweaks, it will be less but for now, you will need to live with a 20 % battery reduction when flashing something.
I noticed that after removin battery while phone is on, on LS8 and LSD Roms.. the phone doesn't boot anymore unless you do a full data wipe !!! I could reproduce it on different custom Roms... didn't test stock yet.. Any comments ??
I did face this issue once. Since then i have not tested it again.
I also got that,when i removed my battery it doesnt boot anymore. Sometimes it crash when its on and reboot automatically. All i can see after reboot is black screen past the Samsung i9100 and the traingle.
(sorry for bad english)
First, here is android development forum, not discussion
Second, there are several threads in general which discuss about bootloop problem on xxls8 and xxlsd
You are right.. didn't see that thread on general section.. Please close it ...
Today I had same problem: remove battery without shutdown first = bootloop on XXLSD neatrom lite 14.1.
FIX
- Reboot recovery
- Wipe Cache
- Wipe Dalvik Cache
- Reboot
fatjoez said:
Today I had same problem: remove battery without shutdown first = bootloop on XXLSD neatrom lite 14.1.
FIX
- Reboot recovery
- Wipe Cache
- Wipe Dalvik Cache
- Reboot
Click to expand...
Click to collapse
Didnt work, must be a different problem... after get the batt off when phone is still on i still got a boot hang!
Why are you guys pulling your battery out?
Sent from the little guy
gastonw said:
Why are you guys pulling your battery out?
Sent from the little guy
Click to expand...
Click to collapse
We take the battery off just to check if we still got the bug and we get stuck in the boot. Why?
Because it can happen in a lot of different situations that you cannot control and i can just tell you a few... Phone drops and battery jumps, battery gets drain forcing the phone to shut down without having time for a proper shuting down, freeze by any aplication or anormal situation that can only be solved be removing battery, the need of switching batteries in case you have 2 or more( some ppl got this boot hang by changing batt even when phone is shut down), etc, etc....
BTW fatjoez afterall ur procedure solved my issue, it just took more time than normal to boot, but i wasnt stuck afterall
Thank you very much! I could not reproduce the boot hang issue anymore after do what you said...
guimar4es said:
We take the battery off just to check if we still got the bug and we get stuck in the boot. Why?
Because it can happen in a lot of different situations that you cannot control and i can just tell you a few... Phone drops and battery jumps, battery gets drain forcing the phone to shut down without having time for a proper shuting down, freeze by any aplication or anormal situation that can only be solved be removing battery, the need of switching batteries in case you have 2 or more( some ppl got this boot hang by changing batt even when phone is shut down), etc, etc....
BTW fatjoez afterall ur procedure solved my issue, it just took more time than normal to boot, but i wasnt stuck afterall
Thank you very much! I could not reproduce the boot hang issue anymore after do what you said...
Click to expand...
Click to collapse
Heard about bootloops but thought nuke script sorted it out.
Now, I don't wanna know If my device will bootloop....when it does I'd know how to fix it.
Sent from the little guy
fix
when you get a bootloop hold power button until the phone restarts and you will solve the problem without doing anything
gastonw said:
Why are you guys pulling your battery out?
Sent from the little guy
Click to expand...
Click to collapse
if you need to change sim cards or micro sd cards, the battery must be pulled
Okay, I've been driving myself crazy trying to find the answer to this little bootloop, and have been all over the place. So I apologize in advance if there is an elusive thread answer to this somewhere...
Here goes:
I downloaded and installed (properly) the [ [ROM] CM9 (ICS) for the Galaxy Player 5.0 USA ] by JackpotClavin. Now normally I would post my issue there, but due to me being a new member, it isn't allowed as you all know. So please bear with me.
Everything works fantastic, until I plug it in when the device is off. Then the screen and buttons light up, it shows the busy signal asterik, and gets to where it would NORMALLY show the battery next, but powers down. Now if I do something that stops the boot loop here (can't remember what right now; no internet at home) then when I plug it in, it actually boots up. But as soon as I unplug it, it kills itself as if it had no battery.
But if I plug in the device when it is already on, then it charges like normal. So I am REALLY confused here.
I already un-bricked it by myself at home when I did something dumb during the ROM restore (CWM). Set it back to stock, and it ran fine. As soon as I switch to the ICS ROM, issues
Now I did a little searching, and in the boot.log it references a "charging_mode_booting" I followed the file path, and found no file there. Now I am aware that I have little (none ) experience in android until now, so that may be normal. I would post the exact log here, but since the device is bootlooping as I type, this will have to wait until I get home again and can troubleshoot
Anyways, I hope I'm not wasting your time. Hope you can help me solve this!
Thank you for your time
N7_X
Samsung Galaxy Player 5.0 (US)
Are you charging your device (while it's shut off) via laptop, console, desktop, or anything else besides a wall charger?
Look under your /system/media
There should be a bunch of battery charging files. If they aren't there, find the files from another ROM and move it there.
Sent from my YP-G70 using xda app-developers app
Jistropy said:
Are you charging your device (while it's shut off) via laptop, console, desktop, or anything else besides a wall charger?
Click to expand...
Click to collapse
Ah thanks mate, that's what I did to get it to boot up while plugged in. Then it has the error here that if I unplug it, whole device shuts off as if the power was the only power source, but will reboot from the battery if I turn it back on.
iurnait said:
Look under your /system/media
There should be a bunch of battery charging files. If they aren't there, find the files from another ROM and move it there.
Click to expand...
Click to collapse
Good idea, I'll get right on it and see if I have any progress.
Thank you both, cheers!
EDIT: Just looked into my system/media folder, and have all "battery_charging_#" 5-100.
Also:
chargingwarning.qmg
Disconnected.qmg
LMprec_508.emd
PFFprec_600.emd
And of course the boot animation and folders
Strange boot loop too with YP-G70
iurnait said:
Look under your /system/media
There should be a bunch of battery charging files. If they aren't there, find the files from another ROM and move it there.
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
Hello everyone ,
first thank you for all your developments.
Secondly, excuse my English but I'm Portuguese.
I spent a lot of time to read all the topics related to this problem, and I have too with my Intl Player.
Since I installed the rj 's custom kernel (r14) if my player is turned off, as I branch as a wall charger or on USB in my MacBookPro , I boot loop load as described above.
So I installed a file explorer that allowed me to see that I had none of the files in the directory system / media.
Ok, I installed adb and fastboot on my Mac , and successful (despite the write permissions only one I managed to get around) to copy the files I found there.
I was sure now it was going to fix my problem, but unfortunately, I have always this kind of boot loop charge if my player is turned off.
Apart from that , everything seems to work well , I do not even know if this is really a problem , I did not let my battery run down lest I get stuck . As long as the player stays on, no worries, battery charging well. Of course I did all the basic wipe's (data/factory, cache, dalvik cache, battery stats).
Sorry for the long post, but I wanted to give as much information .
If someone has an idea of where it may come again, or at least tell me if it's serious in case my battery is fully discharged .
Thank you ! :good:
Edit : actualy I have installed the [ROM][4.3][YP-G70]CyanogenMod 10.2 - M1 Release whith the KKernel R2.1 by KOala888 (My YP-G70 run super fast...).
ToniOsX said:
Hello everyone ,
first thank you for all your developments.
Secondly, excuse my English but I'm Portuguese.
I spent a lot of time to read all the topics related to this problem, and I have too with my Intl Player.
Since I installed the rj 's custom kernel (r14) if my player is turned off, as I branch as a wall charger or on USB in my MacBookPro , I boot loop load as described above.
So I installed a file explorer that allowed me to see that I had none of the files in the directory system / media.
Ok, I installed adb and fastboot on my Mac , and successful (despite the write permissions only one I managed to get around) to copy the files I found there.
I was sure now it was going to fix my problem, but unfortunately, I have always this kind of boot loop charge if my player is turned off.
Apart from that , everything seems to work well , I do not even know if this is really a problem , I did not let my battery run down lest I get stuck . As long as the player stays on, no worries, battery charging well. Of course I did all the basic wipe's (data/factory, cache, dalvik cache, battery stats).
Sorry for the long post, but I wanted to give as much information .
If someone has an idea of where it may come again, or at least tell me if it's serious in case my battery is fully discharged .
Thank you ! :good:
Edit : actualy I have installed the [ROM][4.3][YP-G70]CyanogenMod 10.2 - M1 Release whith the KKernel R2.1 by KOala888 (My YP-G70 run super fast...).
Click to expand...
Click to collapse
The charging mode bootloop has been a problem since the first gingerbread custom kernels and has been a problem up until KitKat. It is solved in KitKat. There is no fixing this problem in pre-KitKat custom roms without recompiling the kernel.
Here is information about the fix:
https://github.com/Meticulus/nutell...mmit/2f7c4affa392c9d0603c23cd3a007ed91dfe62f0
I have answered this question before. Getting tired of explaining it.
Strange boot loop too with YP-G70
Meticulus said:
The charging mode bootloop has been a problem since the first gingerbread custom kernels and has been a problem up until KitKat. It is solved in KitKat. There is no fixing this problem in pre-KitKat custom roms without recompiling the kernel.
Here is information about the fix:
....
I have answered this question before. Getting tired of explaining it.
Click to expand...
Click to collapse
Thanks for your answer. I understand you be tired of answering this problem ... But everything I 've read (and I read for hours and hours , really), I thought it only happened when a USB connection to a computer, not to a wall charging.
If it's just a minor bug and I can use my YP-G70 like that, it's going well, I 'm just afraid to let the battery get to the end and did not do anything. (I also read an old post that says let the battery get to 5% and then moving into CWM mode, and let it discharge completely before reconnecting to a wall charger)...
Last question, is there an kitkat "light" version of that will go as fast as the YP-G70 I installed (4.3) ?, because really outside this bug, all is so good and speed all I 'm doing it (basic use) is really fast.
Strange boot loop too with YP-G70 (4.3)
So I try to install a kitkat to see if the speed is correct.
Thank you again. :angel:
ToniOsX said:
Thanks for your answer. I understand you be tired of answering this problem ... But everything I 've read (and I read for hours and hours , really), I thought it only happened when a USB connection to a computer, not to a wall charging.
If it's just a minor bug and I can use my YP-G70 like that, it's going well, I 'm just afraid to let the battery get to the end and did not do anything. (I also read an old post that says let the battery get to 5% and then moving into CWM mode, and let it discharge completely before reconnecting to a wall charger)...
Last question, is there an kitkat "light" version of that will go as fast as the YP-G70 I installed (4.3) ?, because really outside this bug, all is so good and speed all I 'm doing it (basic use) is really fast.
Click to expand...
Click to collapse
When I was running pre-KitKat ROMs, I let the battery drain completely a few times. It does charge, when it is bootlooping. I let it bootloop for a while, say 10 mins or so and then disconnected it and started it up. Then plugged it back in and let it charge the rest of the way...
:good:
Strange boot loop too with YP-G70 (4.3) --> 4.4
Meticulus said:
When I was running pre-KitKat ROMs, I let the battery drain completely a few times. It does charge, when it is bootlooping. I let it bootloop for a while, say 10 mins or so and then disconnected it and started it up. Then plugged it back in and let it charge the rest of the way...
:good:
Click to expand...
Click to collapse
Well, I installed a Kitkat's ROM ,apart from the start a little longer, everything seems to work well. (Perhaps the least stable wireless)...
I'll try to use it like that a few days and I'll see.
Thank you again. :good: