Just a little bug report:
When the battery is totally empty and the phone connects to power the phone will boot - but usually does not have enough power to boot completely to the O/S. Hence there is a vicious circle of starting and failing.
Once I am fully in the O/S I simply switch the phone off.
My suggestion:
Don't have the phone boot automatically when connected to power when it's totally off (and not in stand-by)
Otherwise a really good ROM. But please also add Nokia Drive 3.0 (which I installed manually)
1. Your posing in the wrong section.
2. Nokia drive 3.0 Does not need to be In the rom taking up space. Because you can install it from the marketplace as you have described.
3. This is the case for any Custom HD2 rom. not just this rom.
4. Another solution is to simply boot to mangler1.3 and let your phone charge a little bit. Before launching the OS and fully Utilizing all hardware.
5. Buy a new 2600 extended battery.
6. Don't let your phone die.
7. Nothing you say is a bug in Pdaimatejam / OS 7.10.8862.144. This is simply the case.
and why new topic? you can post already in Pdaimatejam ROM topic
http://forum.xda-developers.com/showthread.php?t=1356833
or here
http://forum.xda-developers.com/showthread.php?t=2159490
and why you need ND manually install? better is to have fresh, clean from Marketplace to receive updates...
minidisco said:
Just a little bug report:
When the battery is totally empty and the phone connects to power the phone will boot - but usually does not have enough power to boot completely to the O/S. Hence there is a vicious circle of starting and failing.
Once I am fully in the O/S I simply switch the phone off.
My suggestion:
Don't have the phone boot automatically when connected to power when it's totally off (and not in stand-by)
Otherwise a really good ROM. But please also add Nokia Drive 3.0 (which I installed manually)
Click to expand...
Click to collapse
rom booting automatically, is because of the you have WP7 on HD2 which is not a native windows phone device, you should have installed MAGLDR, the famous bootloader created by the genius COTULLA, which, in his thread stated "*Fixed Power-Off-Cable-Plug-Stop. Phone now detects this situation and reboots. Battery controller inside LEO needs runtime control during charge, it implemented in OS."
magldr used to hang when connected, so reboot while connected to a charger is a workaround. somebody didn't read enough before posting
gilbert32 said:
rom booting automatically, is because of the you have WP7 on HD2 which is not a native windows phone device, you should have installed MAGLDR, the famous bootloader created by the genius COTULLA, which, in his thread stated "*Fixed Power-Off-Cable-Plug-Stop. Phone now detects this situation and reboots. Battery controller inside LEO needs runtime control during charge, it implemented in OS."
magldr used to hang when connected, so reboot while connected to a charger is a workaround. somebody didn't read enough before posting
Click to expand...
Click to collapse
booting when charger plugged is a security feature of windows phone ... every windows phone has it .. i think so ..
sathara said:
booting when charger plugged is a security feature of windows phone ... every windows phone has it .. i think so ..
Click to expand...
Click to collapse
and a bootloader (magldr) bug. it doesn't have offmode charging so it boots. also happens if android is installed on nand instead of wp
Related
First of all sorry for my english not good.
Start : with my HD2 have brick after task29 and not success to flash new ROM I'm take USB. cable out and try to open my HD2 in to boot loader by put volum down + power bottom but screen not show any image or 3 color my phone it only long vibration pull battery out waiting 30 minute and put battery in and try to open my phone to boot loader but is same only long vibration.
Now : can not do any think with it when try to plug power in my phone is auto startup and long vibration.
I'm search on google and in this forum not have some one face problem same as me please help me to fix this.
Any body please help me, I'm love it because now we can run both WM. and Android
Upppp waiting for your help
Did you try a long press of the reset-button?
You could try to put the original Stock Image from HTC onto the root-folder of your SD-Card, rename it to LEOIMG.nbh and Push Vol up + Vol down during start and follow the on-screen instructions if it works.
Otherwise use Search-Function in the forum.
ı have jtag HTC for samsung and HTC devices if u want send for repair to me..
www.sevgigsm.net/forum
admin..
I use ORT
Did you check to make sure your radio version was correct before flashing? This is probably the number one reason for bricking.
Check this thread it may help you if you did the flash properly:
http://forum.xda-developers.com/showthread.php?t=668347
i got same problem now...
no screen, no boot, vol down+ power oso same
no screen just a long vibration
anybody help?
I am using the correct radio so don't tell me I am using a wrong radio or something, I have been flashing for 4 months so I know EXACTLY how to flash.
now i can neither get into tri-color or hard reset so don't tell me to flash or smth like that, just tell me how to recover properly
Don't tell us to use search or something because seems like only 2 of us is encountering this problem in the internet
I'm exactly the same problem as TS coz it juz auto go vibrate when plug in battery
This problem actually started when I flash ROM halfway, it stucked and failed...
the device is already HSPL-ed!!!!
but why the F it cannot get into tri-color bootscreen now?
Also, I have to state that my device already got several problems before, my device was very hard to bootup as it will always stuck at HTC screen w/o red version number at bottom left corner, must keep on removing and reinstall battery and reboot until it can boot, not an issue with rom/radio/sim/sd as I tried flash proper rom and radio and remove sd and SIM.
my device also seems like got problem at the gps chip, because when using it for a few minutes, it will lost signal and never reconnects unless i soft reset, after use gps the device will also use battery VERY FAST(-100mA in standby, from -4mA).
now i cannot flash to stock completely, how do I get warranty it?
at the long vibrate, when i plug in to my pc, it will keep on got usb connected and disconnected sound
and dont know what device is connected as not shown in found new hardware and device manager
I also have been searching all possible keywords about what me and TS encountered but all linked to completely UNRELATED results(like search for long vibrations only link to people asking how to make vibration long and 1st result is this thread)
bountygiver said:
This problem actually started when I flash ROM halfway, it stucked and failed...
the device is already HSPL-ed!!!!
but why the F it cannot get into tri-color bootscreen now?
Also, I have to state that my device already got several problems before, my device was very hard to bootup as it will always stuck at HTC screen w/o red version number at bottom left corner, must keep on removing and reinstall battery and reboot until it can boot, not an issue with rom/radio/sim/sd as I tried flash proper rom and radio and remove sd and SIM.
my device also seems like got problem at the gps chip, because when using it for a few minutes, it will lost signal and never reconnects unless i soft reset, after use gps the device will also use battery VERY FAST(-100mA in standby, from -4mA).
now i cannot flash to stock completely, how do I get warranty it?
Click to expand...
Click to collapse
Silly question, but are you holding (and keep on holding) the Volume-Down button while you press the power button?
of course YES
i told you i have been flashing for so long
Leo from T-Mobile. Hi! I've got same problem. After flashing new (next) rom phone definetely died. Phohe is currently simfree and with HSPL. Only one reaction is short vibration after press power button. I searched everywhere. My phone has no bootloader but system see him as Qualcom CDMA Technologies MSM. Thats all, any ideas? Please and thanks for advice.
czaruch said:
Thats all, any ideas?
Click to expand...
Click to collapse
Yes, you flashed a non tmous stock rom that included a ..51.. radio and it destroyed your phone.
What rom? exact filename please.
thank you so much.
I bricked a Leo with the .51 radio. I think I read that is a European or otherwise foreign radio. Since your ROM has Euro in the name.......
czaruch said:
ROM_Leo_HTC_WWE_EastEurope_1-66.
Click to expand...
Click to collapse
The full filename for that rom is
RUU_Leo_HTC_WWE_EastEurope_1.66.479.2_Radio_CRC_Si gned_15.32.50.07U_2.07.51.22_2_Ship.exe
it comes with a version x.xx.51.x radio, and they do Not work on tmous (t mobile us) phones. They kill them
Your phone is dead, sorry. No known fix.
warranty or repair (or JTAG if you are brave and have the money)
a friend of mine bricked his phone. he then tried to microwave it, but that didn't work after that he took a power wire from an old computer, cut it and connected it directly to the phone's parts where the battery would go...this completely f-ed his phone up (he also used a lighter to fake a powersurge of the battery). Then he called htc and a few weeks later he got a new hd2!
GOOD LUCK
lol, he doesnt need to do any of that, its allready as dead as it can be. Loads of epople have had them replaced under warranty with this kind of brick. It wont start, so htc/tmo cant see that its been hacked.
Hi! I understand and realy sad. Somebody know where could I fix it in UK? And how much for this pleasure. Thanks.
i would contact htc, see what they have to say. (dont say you flashed it, it just stopped working")
I have tried everything on this forum and everything people have contributed to me. Now I'm in an endless circle of downloading this and flashing that. Nothing seems to work anymore. My damn phone gets stuck on the boot screen and vibrates a few times and just stays there. I'll give it one more shot before I'll run over it with my car or attach some fireworks to it, something in that nature.
I tried using task29.exe, but it always results in Error 290. I'm pretty sure I'm using 2.08 HPSL and Radio Leo 2.15.50.14.
I faced that you discribing... when I bricked my OMNIA i900!
There're nothing wrong with Leo - it's STILL one of the VERY best smartphone on the market!
And, I never had problems with flashing, except that moment with my old OMNIA, when I was hurry to flash one rom and I f*cked up big time... and bricked my phone.
Don't know what happen to you - you don't writting DETAILS.
But, I'm strongly recomending you to try and re-DOWNLOAD every file/app you need to flashing roms, re-install everything in your PC, try again the task29.exe (if your phones has nothing wrong, the task29.exe SHOULD be working, by all means) and re-try to flash a rom - I'm strongly recomending, to try "ENERGY" roms. The "Yank" lad (chef) rocks!
Flash through SD card stock ROM.
art0605 said:
My damn phone gets stuck on the boot screen and vibrates a few times and just stays there.
Click to expand...
Click to collapse
I think your phone cpu is getting loose from its socket, have a read here http://forum.xda-developers.com/showthread.php?t=982454
Its not easy to fix tho.
Did you use Android ROMs with MAGLDR? Chances are that your device is bricked.
hi
i would suggest to download and install this toolkit found here
http://forum.xda-developers.com/showthread.php?t=1090783
this will allow you to task 29, install hspl, as well as install windows ruu.exe roms
it also alows you to download the drivers needed for your phone which is what i expect is your issue without having any real details
hope this helps
Have you tried flashing a rom through the bootloader by holding down volume down then turning the phone on? Barring a hardware fault, as long as you still have HSPL and can get to the tricolored boot screen your phone should be recoverable.
i think it might be hardware probleme ...not all phones are compatible with android ...mine works perfect on wm but ...when using android and no matter what's the rom i installed ...i always have a hight battery drain ...and i have always to wait 2 mn after turning off the phone if i want to turn it on ...otherwise i stuch on android logo and i cant boot android from sd card...i tried everything ...without success ...
the boot probleme and the hight battery drain doesnt exist on wm ...so i guess not all phones r made to work with android ...since htc make phones by lots ...so might buy one with hardware probleme like mine ...
i'm sure if u tried to install android in another phone u wont have any probleme.
i wrote this reply using wm ...i install it back to sell it tomorrow ...just do like me
instead of destroying it, give it away to some developer. sometimes things starts disliking you. than nothing works. so give it away. where do u stay?
I have the same problem. I finally found an easy fix. Take out the battery for 2-3 hours and put it back in. It almost always comes back to life with no loss of data. Good Luck.
Hi all.
I have been using HD2 for while not.. few days back it started to overheat and freeze. so I tried to update radio drivers. Radio driver installation goes up to 96% and then freeze (2.15.50.14 and 2.14.50.*). If I just let it boot it get stuck just before the red text shows (radio drivers versions and so on) it also makes 6 or 7 vibration as it gets stuck..
I have can go to bootload mode with no problems.. but not further.. i have tried few radios with no luck..
Phone has HSPL 2.08, Energy rom latest, and it use to have 2.07.50.27_2
Its T-mobile USA model.
any ideas.. what do I do.. what do 7 vibration represent? Is main board busted?
Did you use MAGLDR (and Android for that matter)?
If yes, chances are high that your device is bricked, unfortunately.
According to another forum, a technician found some high probability that MAGLDR could cause a permanent memory damage if used with Android. He was not able to fix it even with his special tools - the clear sign for that problem is the 7-times vibration when turning on the device.
Sorry, mate. Looks bad. Maybe try to send it to a service center?
tictac0566 said:
Did you use MAGLDR (and Android for that matter)?
Click to expand...
Click to collapse
nop.. win 6.5 only.. energy rom....
should I try MAGLDR?
found this..
http://forum.xda-developers.com/showthread.php?t=982454
and
http://forum.xda-developers.com/showpost.php?p=10066913&postcount=10
Try chilling the phone in plastic bag in fridge, have. Nbh ready to flash from SD as soon as u take it out, , if it works, then its definitely a thermal problem.
My apologies if this post is already started elsewhere (please guide me there if you can), but it seem the search is not possible today...
I rooted my brand new Vodafone Smart 2 and in order to free some memory I was moving some files from internal to SD card. Noticing a folder in the root called custpack (and thinking it was the specific folder Vodafone used for its teaking) I wanted to play around with it on my computer, but instead of copying it to SD card, I MOVED it... :0 At the first command the screen turned gray and the phone froze. I can turn it off now only by removing the battery. When it starts it can't go pass the android logo (boot image) and the screen turns gray. I know that Power button and Volume Down yield to Recovery menu, but my ROM is branded Vodafone Albania and they have removed that option. All I get is the option for factory reset (or I think that is what "All you data will be lost, Yes/No" means). Accepting that does restart the phone but still the same logo and gray screen afterwards.
Unfortunately, I can't install from SD due to this branded Vodafone AL ROM I have, and adb device command at the command prompt (DOS) does not recognize the phone (it did recognize before as I have the drivers loaded and Android SDK Tools).
Can someone help me either bringing the Recovery option to install from SD so I can try a complete flash of the original, or if there is any way I can have the adb recognise the device, or if there is any other way. I found a user here (Voda_Smart_2) that seemed to have the same problem and someone had said could help but only through PM. I tried to reply the thread so I could present my case, but as a newly registered I was not allowed to post on developers forums.
PLEASE HELP ME - For someone who uses a low-end phone like Vodafone Smart II option to buy a new one after ruining a new one is not possible....
Don
Go to
roeddie.blogspot.com
Ota update 3
U will find there The Solution !
Enjoy
Sent from my Vodafone Smart II using Tapatalk 2
Do you still have the problem?
I can help you if you need because I had the same problem before.
i have this problem with vodafone smart 2, it is stuck at boot logo ( the green android robot), how can i fix it?
when i try to connect him to pc, the pc doesn't detect him anymore and when i plug in the charger remain stucked at android logo too without showing the battery status charging.
this happend after i tried to flash recovery on it.
phenomenalxp said:
Go to
roeddie.blogspot.com
Ota update 3
U will find there The Solution !
Enjoy
Sent from my Vodafone Smart II using Tapatalk 2
Click to expand...
Click to collapse
Thank you for interest and concern for my situation! I know very well roeddie custom rom for VS2. I have actually installed version 0.9.1 as well as version 0.9.9 to some friends. I have the undestanding that the AIO he uses requires that the phone be recognized by the PC (adb devices does not list anything in my case). However, I'll give it a try and let this forum know if roeddie AIO flasher (OTA update 3) does install without the need for PC to recognize the android phone.
Thanks,
Don
jiandroid said:
Do you still have the problem?
I can help you if you need because I had the same problem before.
Click to expand...
Click to collapse
Yes, I still have a problem with my VS2/V860 - stuck at boot logo without fastboot. I can't seem to find a way how to get it recognized. Can you help me? It would be really helpful since now my brother has the same problem after trying to flash latest roeddie mod (June 1, 2013).
Don
jiandroid said:
Do you still have the problem?
I can help you if you need because I had the same problem before.
Click to expand...
Click to collapse
I've got that problem too, can anyone help us please?
Recovery
U need full recovery
http://forum.xda-developers.com/showpost.php?p=40506492&postcount=2
Fastboot mode not recognized by computer...
atha959 said:
U need full recovery
http://forum.xda-developers.com/showpost.php?p=40506492&postcount=2
Click to expand...
Click to collapse
Thanks for your consideration! My problem is that my phone is not recognized in fastboot mode by the computer. I have installed Android SDK and updated regularly. Without fastboot (see bullet no. four following your link) I can not do anything Alberto96 suggest.
Any other insight?
Don
i ve got the same problem with my V860.....does anyone know a way to de-brick our phone?
or anyone found out something???
tnx in advance!
Vodafone Smart 2 device can't start code 10 error
I have the same problem any help..?
dead battery is the answer
well guys if anyone of you still use this device; a possible fault that causes infinite boot logo screen is dead battery. Actually the controller board of the battery gets shorted causing a stable 1.7v output instead of 3.8~4.2v and refuses to charge even pushing power to it from an external power supply. Thats why the phone stucks on logo; it is the same reaction to connecting the phone to the charger without a battery... what you have to do is to find a used or a new battery (if it's still worth to do so...)
dizzytransistor said:
well guys if anyone of you still use this device; a possible fault that causes infinite boot logo screen is dead battery. Actually the controller board of the battery gets shorted causing a stable 1.7v output instead of 3.8~4.2v and refuses to charge even pushing power to it from an external power supply. Thats why the phone stucks on logo; it is the same reaction to connecting the phone to the charger without a battery... what you have to do is to find a used or a new battery (if it's still worth to do so...)
Click to expand...
Click to collapse
Thanks for the suggestion! It is not a problem of battery, as I have tried with two other batteries from friends' V860. Plus, if it is a board circuit then it does not matter if the we change the battery, unless with 'board' you mean the way batteries are connected inside the battery pack.
Thanks once again! Your answer is much appreciated! Keep them coming if you think about something else. I still have this phone, just for because I like to know what was the problem or how to overcomes such situations in the future.
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: