Related
Hey guys, I really need your help here.
I was trying to flash my mate's phone with the newest MIUI today, but it wouldn't work because the SD card wouldn't mount.
Now when he got this phone, it was already rooted. No idea how they rooted it, but there were a few Chinese apps on there. I got my phone (Samsung Captivate) from the same people, and there were also a few random apps on there, but I managed to flash a new ROM on that. It got to the point where I was un-rooting and rooting it over and over again, until I found a Clockwork Mod that worked on the Defy. It mounted the SD card fine, and then it installed the ROM using the "install from zip from sd card" function or something like it. It went fine, said it finished and it didn't lose power half way through the install. Rebooted the phone, and now it's stuck on the "M" Motorola logo. Went to go flash with sbf, and then it came up saying that the battery was too low so it wouldn't program. Well ****.
Tried the Mcgyver mod where you just splice a USB in between the battery and the phone, but that didn't work. I'm hoping that it will just charge from USB while the phone is off? I've read somewhere that it won't charge while it's off, but the LED is white (I think that indicates that it's charging). Occasionally the "M" logo comes on, but it goes away and starts "charging" again. It won't take to the wall charger for some reason, just doesn't want to charge D:
I've been at this for 8ish hours now, does anyone have any advice? Anything at all will be greatly appreciated.
Thanks,
Justin
How long have you been trying to charge it? That's normal behavior for the phone to show the Moto logo and go to battery charging animation when the phone is off. You should be able to power it on if it is plugged in though.
Are you in the boot loader when you try to flash the SBF? Reboot the phone and hold the volume key up to get to the bootloader. Use RSD lite to flash the SBF. I'm sure you've already looked at http://forum.xda-developers.com/showthread.php?t=966537. It's very helpful.
Good luck!
After flashing the new firm , try to make a WIPE before you install the zip !!
Worked for me!!
this should go to the development sector
youll find your answer there under "bricked phone"
usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
kasalamite said:
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
Click to expand...
Click to collapse
srry posted last night but would not show the thread... so i figured i couldn't so i tried to post in an existing thread. now i dont know how to delete that other one...
FIXED
well never mind the fact that i loaded a plethora of info onto this post and nothing.
but besides that i got it working. in the disaster recovery tut it only lists using the ruu through a flash... never stating that you can just run the file directly and not go in %temp% and get the rom.zip(excepting for the recovery_signed.img). simply find your version of the ruu that you need, flash back to the stock recovery image (within the rom.zip) relock bootloader place device in fastboot and run from pc.
the only hard part is getting it to charge... dont know how mines took charge but i pluged it into the sockets @ my school (long story read this thread: http://forum.xda-developers.com/showpost.php?p=26156147&postcount=20).
when i pluged it in the light went solid red instantly no blinking. after about an hour of charge i pressed the power button and it went to the splash screen (still was on a older CWM which doesn't support charging) left it at the splash screen for the remainder of the class (about another hour) unplugged entered bootloader.
@ this point i had no security warning under relocked. but i used the power down option, took it home and tried to unlock/flash to the latest version of CWM so i could charge. it worked without a hinge.
anyone know why it took charge on an older CWM?
note i got the phone back up and running and the first thing i did was make a nandroid back up
hi i dont have an answer to your question but i have a question to your answer am curently suffering the same problem i can flash the stock cwm because of low battery, and i know when in boot mode it doesnt charge so i rebooted the phone it took me to the htc logo and its displaying a solid red light does this mean its charging or what (the boot loader is re-locked so i can flash stock cwm but cant due to low charge)
Noob badly. But I think it should be charging. Could b wrong. Leave it there for a couple of hours and try again. Mayb fixed. Give it time and try again.
Sent from my HTC One X using XDA
Same thing is happening to my phone. and its bootloader is locked and cannot be unlocked because of the charging. its usb debugging wasnt turned on either before it went down.
Please help anyone?
Guys I have Htc One X. I rooted it then I thought to install a custom rom (resurrection remix) and gapps. so when I was in the CWM recovery I installed the mod while it was installing it said error no file contents but it installed successfully anyway. after that I installed Gapps but it got an error and said Installation aborted. I then started panicking and I tried to restore the backup but nothing happened, then I re-locked the bootloader with battery below 30% then I used the batch file to charge it then I unlocked it again. Now I want to download a stock rom I tried 2 one was a newer version than what my phone actually is and the other one was a lower version than what my phone actually is. I then tried alooooooooooot to search for the appropriate one for my phone but I didn't find it so I thought to continue with installing custom rom anyway but the problem is that I need to get the new mod zip file and new gapps zip file into my phones sdcard but I can't do that/I don't know how. My phone isn't recognized by my pc ( I can't browse it's files) and I tried using adb in command prompt which is very complicated for me however I searched on the internet and tried to do the same but then it says "adb server is out of date killing" then I found one adbFix.exe that said that the adb in HTC sync manager folder is causing a conflict but then the Fix file said that its ok and no problems are there. Now I need to put custom rom and gapps zip files to my phone's sdcard but I can't. Please I would be very grateful to anyone who would help me and guide me and If I'm posting in the wrong forum or thread then please forgive me for this is my first time I made an account on XDA and my first ever comment/
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
Ive just encountered the same problem. Were u able to find a solution?
Shahin7631 said:
Ive just encountered the same problem. Were u able to find a solution?
Click to expand...
Click to collapse
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Dennis_Arlo said:
Hi Guys,
've flash my Samsung Galaxy Note 2 N7100 to 4.4.2 KitKat it was successful, but after a few days my note 2 keeps auto shutting down randomly and sometimes I can't turn it on from sleep. I thought I've just missed something when flashing to 4.4.2 KitKat, what I did was to re-flash it and check if I've missed something but not. After I re-flash it, I've encountered this problem. I'm stuck at boot loop, I've done the Wipe process it was successful, but it didn't fix the problem, what I've noticed is when it's NOT charging or plug to PC it is stuck at boot loop, but when I plugged it to PC or charge it it continues loading the KitKat, sometimes prompting that it's not charging.
I'm wondering what could be the problem here. I've google any possible problem, I can't find any similar problem to mine. Can anyone help?
I'm still try any possible way to fix... HELP!
Click to expand...
Click to collapse
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
anish100 said:
I had a similar problem with my note 2 N7100.
It used to reboot every 30 minutes.
The best solution was to reinstall the firmware using ODIN.
First you need to download the firmware from sammobile and put the phone in download mode and install it.
Hope this solution helps you too.
Click to expand...
Click to collapse
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
GStriker said:
Thank you anish. I already tried this solution (with stock firmware and Cyanogenmod 10.3 &11) but it didn't work for me
The phone boot only happens when I unplug the USB cable and launch an app. If I do nothing after unplugging the cable the phone don't boot immediatly.
Click to expand...
Click to collapse
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
GStriker said:
I exactly encounter the same issue on my Note II. It seems that the automatic reboot (then the boot loop) when the phone is unplugged is generated with apps (or system) using internet connection or the camera.
Please help ! :crying:
Click to expand...
Click to collapse
Ive literally tried everything .even repartioned the phone . it works fine in recovery and download mode but as soon as i want too boot to android unplugged it restarts . when plugged it has no problem
Funny thing. I have a factory Sprint Note 2 with the latest kitkat updat and I am experiencing the same problem. Phone has not been rooted or messed with. If anybody come across a solution let me know. I booted the phone and unplugged the power button to verify and it does the same thing. Only stays on when in airplane mode or charging.
One more thing. I tried somewhat to do what was posted above about performance / cpu power. I put the phone in powersave mode and checked limit cpu and is is fully operation. problem gone. If I turn power save mode off I'm back to square one.
To late. Took a picture by mistake and phone jumped into boot loop.
i have GT-N7100 and same problem phone is stuck on boot loop when unpluged
---------- Post added at 04:22 PM ---------- Previous post was at 03:24 PM ----------
i just tought maybe it needs new battery. cause before i unpluged it it showed 67% then bootlooped 2x then i pluged back in and it shows me only 5%. i think its battery cause it cant dishcharge in 1 or 2min
My initial problems were that it would drop signal and show an x with no bars intermittently. then i started having problems anytime the phone demanded use. Picture, internet, video. tried a few things listed above. Still would go into a boot loop when not plugged in. Battery would charge normally and show it percentage like normal. It would reach 100% with no difference in charge time. When battery saver is on it would not have a problem unless I use an app that demands more cpu usage, network connection, battery consumption. Put a new battery and problem is gone. some people say the battery show swelling but my battery looks identical to the new one. no swelling and it is not deformed in any way.
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Shahin7631 said:
It also solves the problem for me ...but i dont know what to do after the restart ...have u found a permenant solution
Click to expand...
Click to collapse
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
dcmobiletech said:
I was thinking. If you flashed with a bad battery whats there to keep it from affecting the flash / update. The stock system doesn"t allow an update unless the battery is charged. It doesn't know if the battery is faulty. Try to reflash after a new battery has been reinstalled and charged to full. It's just a thought.
Click to expand...
Click to collapse
Ive tried already with another battery ....its a very strange situation while everything works fine in download or recovery mode when its unplugged ...i have ordered a third party battery to see if it'll make a difference or not ....i'll keep u updated tomorrow
GStriker said:
Hi guys ! I finally found a temporary work around to avoid automatic reboot. After multiple tests I noticed that the issue seems to come from CPU usage.My phone never went to deep sleep and often stayed around 1600MHz.
The work around was to go to Preferences > Performances > Processor/CPU > Strategy select "userspace" . The CPU goes down to 800MHz but I don't have any more automatic reboot when the USB cable is unplugged.
After reboot the boot loop is still there (so I need to put back in the USB cable to boot normally). I was wondering if the boot loop comes from the boot.img file...
Click to expand...
Click to collapse
Where is the Preferences section? I am unable to find that on my Note 2 settings.
Experienced the same thing and this is the first time I had this. I was playing a game after I fully charged my battery and suddenly it turns off. So I waited for it to turn on where I noticed that it keeps on turning on and off and stuck on the " Samsung Galaxy Note 2" logo screen. Then I tried several things like clearing the cache and dalvik but it just do the same thing. I re-flashed the 4.4 ROM that I was using but sadly it does the same thing. I then noticed that if I plug in the charger it works normally and does not boot loop. And as soon as I remove the charger it will keep on restarting on and off on that screen. I was thinking that it might be a hardware failure or the battery itself. So I went to recovery mode and unplugged the charger, it stays on. Went to download mode without the charger and it stays on. Freakin' weird. I am about to flash a different ROM and will wipe everything and see what happens...
Fully charged the battery to 100%, unplugged the charger and it started to boot loop again. I allowed it to boot loop once and immediately went to recovery mode and saw that my fully charged battery went down to 3%. Tried different ROMS (Omega, DN3, and Phoenix), I still have this issue. Now can use my Note2 as long as the charger is plugged in...
Change your battery and solve the problem ?
Sent from my GT-N7100 using XDA Free mobile app
I did. Case closed!
red_hanks said:
I did. Case closed!
Click to expand...
Click to collapse
is it working fine after battery change? does it still get stuck in boot loop? mobile networks?
It works perfectly !
I'm having a weird problem. Yesterday I was using my phone as I normally do-- texting, playing simple puzzle games, etc.-- when I noticed the battery was at about 2%. I wasn't very concerned so I tried to send one last text before it died. Shortly afterward it died with the usual "Powering Down" alert. I thought absolutely nothing of it and once I had access to a charger, I did what I normally do: I turn on my phone, wait for it to get past the LG splash screen, and I plug it in once it gets to the boot animation. I do this so my phone will turn on instead of going into charge only mode. Also, like usual, my phone's screen dimmed seconds after the boot animation began (I assume from my automatic light sensor settings), and I could feel it vibrating a little (also something it typically does upon boot).
However this is as far as it got. I was very confused when about an hour later, the phone still hadn't completed boot. I removed the battery, inserted it again, and tried once more telling myself that I would wait as long as I could instead of just an hour. Booting the second time gave me identical results-- everything is normal (light sensor response and vibration indicating the phone is powering on) yet it gets stuck. The only difference is that this time I got to see the entire bootloop.
After the boot animation screen has run for a while, I get the usual "Android is starting.... Optimizing app ## of ##" (#= actual numbers). Once it finishes, instead of booting my phone, it begins the boot animation again. If left alone it will cycle between the boot animation and the "Android is Starting" screen indefinitely.
TL;DR:
1. ) Caught in bootloop between boot animation screen and "Android is Starting... Optimizing app ## of ##" screen.
2. ) The screen still dims and there are little vibrations that usually tell me the phone is about to turn on.
I have tried:
- a hard reset- this yields only a slightly stronger vibration and it starts the bootloop again.
- Download mode- this does the same as the hard reset
- Removing battery for a while- no results
- Full charge to completely dead to full charge again on charge only mode- no results
I am running CM13 Nightlies from late February (not completely sure which exact date). Which I flashed without issue about a month ago. I do have Xposed and run various modules, but I was using nothing at the time and hadn't for about a month. My computer recognizes my phone as an LG G3 Device, but refuses to access any files.
Any help would be greatly appreciated!!
Phone not starting.
First remove phone battery, insert it again, do not start phone. Connect your phone to original charger and charge it, while charging with the charger start your phone. Your phone should start if yes/no report me immediately. Your phone battery is failing to start your phone (Due to Low Voltage in battery). Replace with original battery.
jit1108 said:
First remove phone battery, insert it again, do not start phone. Connect your phone to original charger and charge it, while charging with the charger start your phone. Your phone should start if yes/no report me immediately. Your phone battery is failing to start your phone (Due to Low Voltage in battery). Replace with original battery.
Click to expand...
Click to collapse
Alright, I removed the battery, reinserted it (without turning the phone on) plugged it into the wall charger (seeing the charge only battery animation), and attempted to turn it on. Whenever I try to turn my phone on after plugging it in, I get the LG splash screen followed by the battery charging animation. It never reaches the boot animation. I'll let it charge for a while and try again.
Thank you for the advice!
Okay, I let the phone charge completely and attempted to turn it on whilst plugged into the wall charger again. Unfortunately I had the same issue. The phone shows the LG splash screen and then the battery charging animation again-- no boot animation.
musiceas66 said:
Okay, I let the phone charge completely and attempted to turn it on whilst plugged into the wall charger again. Unfortunately I had the same issue. The phone shows the LG splash screen and then the battery charging animation again-- no boot animation.
Click to expand...
Click to collapse
just start with a full reflash , if it doesnt boot up its simply broken
Jhinta said:
just start with a full reflash , if it doesnt boot up its simply broken
Click to expand...
Click to collapse
Yeah, I'm trying to avoid a full reflash/data wipe. Since I haven't messed around with any Xposed modules or root apps, I also haven't backed up anything for quite a while. No abnormal apps were running before the battery died, which leads me to believe this can be solved somehow without a full wipe.
Also, I tried to use my boyfriend's battery to boot up my phone. I thought it might be a bad battery-- as some people on-line have mentioned. Unfortunately, it still refused to boot and it produced the same bootloop.
You see , if and not and this and that dont help . te only way to save files is to get acces by recovery or boot, you cant boot but possible you have recovery so start saving your files you need. when you have or dont have your files . you stil need your system to boot for that to happen, it needs to work. so flashing a default rom with wipe sould work if it doesnt you flash original if that doesnt work its dead
Verstuurd vanaf mijn LG-D855 met Tapatalk
I think I forgot to mention, I cannot access recovery mode. I have the latest TWRP installed, but attempting to boot into recovery gives me the same results-- endless bootanimation/ "Android is Starting" bootloop.
So no acces at all . so what do you do ? Read above! Anyway good luck
Verstuurd vanaf mijn LG-D855 met Tapatalk
Solved
I fixed my problem. It turns out I was being an idiot and got the method of entering recovery mode on the LG G3 confused with my Samsung tablet. I should be able to fix the bootloop on my own now. Thanks everyone for your help! Cheers to idiocy.
Hey, I have the exact same issue right now. Did you solve your problem, and how? I tried removing the battery and charging with original charger to 100%. I connected it to my PC, went into Download mode and clicked "Restore Upgrade Errors" in LG PC Suite. It successfully flashed the firmware update, then it said "Android is starting.... Optimizing app ## of ##". But after that it restarted into bootlop again. Also I noticed that sometimes it vibrates, and my LED (light sensor) doesn't light up anymore.
Any advice? I haven't tried replacing the battery yet.
simon710 said:
Hey, I have the exact same issue right now. Did you solve your problem, and how? I tried removing the battery and charging with original charger to 100%. I connected it to my PC, went into Download mode and clicked "Restore Upgrade Errors" in LG PC Suite. It successfully flashed the firmware update, then it said "Android is starting.... Optimizing app ## of ##". But after that it restarted into bootlop again. Also I noticed that sometimes it vibrates, and my LED (light sensor) doesn't light up anymore.
Any advice? I haven't tried replacing the battery yet.
Click to expand...
Click to collapse
Hi i have the same problem with my lg g3 d855, after a reflash hi is start and do android optimazig after the tel is start and do this over and over. help please
Hi, the solution that worked for me was to
1. install drivers
2.install LGUP
3.flash "LGD855P_D855P10a_04" - found here https://drive.google.com/file/d/18tlmVNK_ba0jIapJy-Sz5wamxbIXh8xH/view
I have this problem for quite a while now. I had Lineage OS installed in my phone for about 6 months and suddenly , one day when I tried booting into it , it failed. The HTC logo appeared but then the phone shut down , it would boot if I plug the charger in. I took it to HTC service center , to get it checked. They told that it might be caused by faulty battery. I took it to a shop nearby to get the battery replaced , but replacing the battery did not work. The shopman told me that the phone is rooted , and they told me that they will lock it. After they did , now I am unable to boot at all. I unlocked the bootloader again , and when I try to open recovery (TWRP) it just shutsdown again. I will get the battery charging screen. If I press the lock screen , I can see a bit of twrp but I'm unable to operate it. I then flashed CWM , it works , but I have no idea what to do next. I only had TWRP backups , which unfortunately do not work any longer.
I have a5_dwg.
parik27 said:
I have this problem for quite a while now. I had Lineage OS installed in my phone for about 6 months and suddenly , one day when I tried booting into it , it failed. The HTC logo appeared but then the phone shut down , it would boot if I plug the charger in. I took it to HTC service center , to get it checked. They told that it might be caused by faulty battery. I took it to a shop nearby to get the battery replaced , but replacing the battery did not work. The shopman told me that the phone is rooted , and they told me that they will lock it. After they did , now I am unable to boot at all. I unlocked the bootloader again , and when I try to open recovery (TWRP) it just shutsdown again. I will get the battery charging screen. If I press the lock screen , I can see a bit of twrp but I'm unable to operate it. I then flashed CWM , it works , but I have no idea what to do next. I only had TWRP backups , which unfortunately do not work any longer.
I have a5_dwg.
Click to expand...
Click to collapse
try to install twrp 3.0.0, probably from adb shell over the USB cable, in cwm recovery.
that should sort it out. hopefully. then you can try restoring a backup and see if switching the battery actually made any difference or not.
Unable to boot into phone
I have the same problem with me but i have twrp installed(3.0.0) and stock rom and bootloader unlocked. When i install lineage os in it it boots but only when charger is connected whereas when i restore my stock rom back up it couldn't boot into it reboots again and again...
I have a5_dwg.
Vibhor verma said:
I have the same problem with me but i have twrp installed(3.0.0) and stock rom and bootloader unlocked. When i install lineage os in it it boots but only when charger is connected whereas when i restore my stock rom back up it couldn't boot into it reboots again and again...
I have a5_dwg.
Click to expand...
Click to collapse
Try wiping data with the stock backup to see if it'll boot. I had an evo3d with some internal glitch that would from time to time bootloop stock until I wiped data then it would start up again.
Sounds like your battery might be weak, ROMs like to shut down if they think the battery is too low.
Having the same problem right now, confused whether I should replace the battery or not, right now plugged into a charger, phone is fully charged nd removing the charger phone turns off.