My Salutations, I am asking a question in regards to a serious bootloop I have managed to pull myself into.
Most bootloops I usually just enter CWM and flash another rom or restore. This problem however is much more serious.
Every time I attempt to enter CWM it goes directly to download mode. It's as if CWM doesn't exist on my phone anymore or something.
Download mode is the only thing I can access. I have tried multiple attempts to enter any other recovery mode but they all end up getting me to download mode.
This isn't the only problem. I thought this wouldn't be a big deal until I realized my PC can't recognize my phone at all anymore. Even before I got into the bootloop, my phone would only charge but any other recognition from the PC was absent. I have all the correct drivers installed including numerous attempts at re-installing, re-configuring, and restarting my PC.
I think I may have reached an irrecoverable error.
Any ideas would be much appreciated. Thanks.
FYI, The ROM I flashed when my Phone started acting like a bundle of ninnyhammerness was AOKP milestone 6. It's not the ROMs fault of course, seeing as how this ROM is very good. I also had the Darkside kernel. This is when I couldn't manually enter CWM. In stead, I had to let the phone boot up and utilizing the power menu, restart in recovery mode. I thought this was strange at first. I then wiped, and decided to flash the 20th Nightly of AOKP Jellybean just to try it. It booted fine, but then when I had to restart to enter CWM again I chose to flash another Darkside kernel. After this, my phone went into a bootloop. That is where everything else fell apart.
Sounds like either the recovery isn't sitting in the system correctly or its gone. When your phone is in download mode you said that you can't connect to pc. Are you running odin as admin and/or connecting the device to pc previous to putting the battery back?
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
Yes I did run Odin as an administrator. I also tried connecting the device prior to putting the battery in, and also after.
I had this sort of problem yesterday (I installed a port of CWMR and it had some bugs which lead to it formatting the disk and then freezing and a reboot wouldn't allow me to install a rom...) anyways
1) Go to http://www.samsung.com/us/support/owners/product/SGH-T989ZKBTMB? and download the drivers for the phone. This will allow windows to recognize the phone, without the phone having to communicate to the computer.
2) Download Odin v 1.85 (that's what I used anyways)
3) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1481141 It'll give you a workable CWMR to allow a format and installation of a rom to stop the boot loop
Those three steps should solve the problem, it did for me at least.
Hope that helps!
kmcclry said:
I had this sort of problem yesterday (I installed a port of CWMR and it had some bugs which lead to it formatting the disk and then freezing and a reboot wouldn't allow me to install a rom...) anyways
1) Go to http://www.samsung.com/us/support/owners/product/SGH-T989ZKBTMB? and download the drivers for the phone. This will allow windows to recognize the phone, without the phone having to communicate to the computer.
2) Download Odin v 1.85 (that's what I used anyways)
3) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1481141 It'll give you a workable CWMR to allow a format and installation of a rom to stop the boot loop
Those three steps should solve the problem, it did for me at least.
Hope that helps!
Click to expand...
Click to collapse
Thanks but, it still hasn't worked. It keep saying "USB device not recognized, Device driver software was not successfully installed."
I was able to fix it. If anyone else encounters this lethal, and pretentious conflict again... I resolved the problem by repeatedly spamming the power button on my computer, unplugging the cable repeatedly and letting my phone sit without the battery inside of it for 24 hours until my PC finally recognized the device.
i3lackDawn said:
I was able to fix it. If anyone else encounters this lethal, and pretentious conflict again... I resolved the problem by repeatedly spamming the power button on my computer, unplugging the cable repeatedly and letting my phone sit without the battery inside of it for 24 hours until my PC finally recognized the device.
Click to expand...
Click to collapse
also it may be because of a faulty data cable !
Hi,
Summary: Was running Cyanogenmod 10.2.0 and tried to update to 10.2.1. Phone won't boot. Using CWM recovery 6.0.4.3. Factory Reset reports that it can't mount / clear /data (due to encryption?). Can get phone into CWM recovery and Download mode. Haven't been able to successfully connect to PC (ADB or Odin) even though I have samsung drivers.
I do have an unencrypted SD card in the phone so my normal way of flashing is to connect SD card to PC, download, then in CWM recovery to install ZIP from SD card.
Looking to get into any good state - Cyanogenmod 10.2.1, or 10.2.0, or heck go back to stock.
**** I think the answer might be use ODIN and flash back to stock, I see some guides but haven't been able to get ODIN to "see" my phone *****
Details
I had downloaded Cyanogenmod update to phone using "About this phone" menu and when I tried to "Install it" from that window the machine booted into recovery, immediately failed, and rebooted. The phone is encrypted (work requires this) and I discovered Cyanogenmod saves the download to encrypted phone storage and CWM recovery doesn't support encryption.
Downloaded 10.2.1 to my SD card and flashed it. (no back-up, no wiping of cache). Installed successfully, reboot asked me for my encryption password, Android optimized apps, rebooted, encryption password, then blue spinner spins forever.
From here I started my troubleshooting:
- I flashed back to 10.2.0 then flashed Gapps again, no change.
- Reading about boot.img I installed ADB and SDK Manager and tried connecting and flashing boot.img. ADB devices shows up empty. I have installed Samsung drivers.
- Researching going back to Stock points me to installed Triangle to reset my custom ROM count - but I can't boot.
Thanks in advance.
Matt
[Solved] This is for anyone who happens to read this wondering if their phone is screwed. Relax! If you can get into Download mode and Odin can see your phone, you'll be o.k.
Turns out the machine and cable you use do matter. I tried for days connecting using my MAC running Windows 7 Virtual Machine. Once I switched to my Win7 laptop and used the original Samsung cable things starting working out more smoothly.
Steps:
1) Get Odin (mine was 3.09) and run as admin. If you see an error in Korean it's because you have to unzip the entire Odin folder.
2) Get stock firmware for t-mobile. There's only 1 firmware file, I didn't need a PIT nor a specific recovery step. The t-mobile firmware includes everything I needed. Flashing failed in Odin saying Complete Write failure. This had me stumped for hours and hours. When I switched to stock cable and Win7 laptop it succeeded. I never had to check Nand erase all or repartitian (almost did in desparation though). Flash took about 10 minutes but eventually PASSED.
3) However, when it rebooted it asked for encryption key and my old one didn't work. Turns out their are more steps. This scared me.
4) Reboot into recovery (up, home, power) which gave a bunch of scary error messages. Actually those listed at the bottom in http://forum.xda-developers.com/showthread.php?t=1840030.
5) Factory Reset then Wipe Cache
6) Reboot
Now I'm back at stock and breathing a sigh of relief. Unclear if I'll ROM back to Cyanogenmod.
I spent hours and hours reading discussions and going down one dead end after another. I'd say it was like looking for a needle in a haystack but it was the complete opposite. It was like looking for a specific needle in a sea of needles. Every search query yielding tantilizing results and a plethora of step by step guides that ultimately didn't work. A very frustrating experience all around. Good luck to anyone who reads this.
Hi Matt
Similar thing happened to me last night. I am/was using Omni-Nightly build. I plugged it in to the charger before bed, and it rebooted, saying upon reboot - "Encryption Failed" and saying the only way to recover would be to wipe the machine and start again, it then rebooted and all I get is the Samsung boot screen.
Tried rebooting, wiping, everything, Odin, Android Toolkit, nothing works. It shows up on my Linux PCs but not accessible, but not windows at all.
Hi guys, so my problem is I was installing a new rom on my rooted D855. everything was going along fine but then the process stalled. I left it running for 15 - 20 minutes but it was still on 33%. I tried holding the power button in desperation which shut the thing down. Now when I try to factory reset it goes to the prompt screen, I answer yes, then it asks me to confirm. from there however it goes to LG splash screen and eventually a black screen with Fastboot mode started. -reset- portcharge -reset- portcharge fastboot: processing commands in the top left corner. That's it.. If I try download mode it goes to the download screen and then to the black screen as described above.
Sounds pretty ordinary but if there is an answer out there I am sure one of you guys will know it.
TIA
i had some similar other issue and the only way i got out of it, is by using the lg flashtool 2014 and the KDZ file appropriate to your version
there is a thread with a step by step instructions.
you launch the flashtool, then insert the kdz file (original stock rom) then you put your phone into download mode (making sure in windows/controlpanel/devicemanager/ports - comp port 41 for the device driver)
you press volume up and plug it into the pc, the pc sees the phone and it starts reflashing the custom rom to your cell.
i presume that as soon as your download mode is working by flashing whatever command is corrupt and makes your phone black should be bypassed by then
i hope it helps - look for the thread how to flash the lg
Thanks I'll give it a shot. Not sure device manager is seeing it properly. I'll have a play and see. Thanks again for the reply
O.K here's the thing, my phone is seen in device manager as a Samsung Android Phone. Under the details tab it shows it connected via USB Modem Phone ADB Port. There is no option to change the port to 41. Anybody who can help I would be very grateful......
Hi everyone, today my Elephone p8000 with stock rom (no root nor recovery installed) proposed me an OTA update, and I did it.
After installing the update the phone is stuck at the boot animation logo. If I boot in factory mode (volume down + power button) I am presented with a bunch of options in Chinese, which I don't understand. If I go in recovery mode (volume down + power button) it says "no command".
What can I do? What are my options? Is it bricked?
Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.
kevvyboy said:
Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.
Click to expand...
Click to collapse
Damn. I had huge problems with the flash tool in the past (I don't have a Windows PC) and the idea of spending the weekend trying to get the damn thing work is not a fun one.
Got this issue too this morning on way to work, I guess my phones useless today until I get home to try and flash it.
seem to be able to get to the boot select screen but nothing is different anyway, also managed to get into a "PCBA" mode that did a load of tests to the phone but thats it.
it now just died, not powering on, think its bricked :crying:
skea said:
it now just died, not powering on, think its bricked :crying:
Click to expand...
Click to collapse
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
pitrus- said:
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
thanks it was out of power lol
I just had the same problem. Did you solved it?
Like, exactly the same... Crazy
Another one
My p8000 also in bootloop after ota update. Only have an old vista PC w8ll dust it off tonight and see what happens
mines doing the same i thought it was too good to be true and it was lol
Cannot get pc (win 10) to install all the drivers, PC cannot see the phone so unable to run flash tool.
Suggestions? I presume the ROM cannot be flashed through the recovery (standard)?
EDIT: Driver package installed by disabling 'driver verification' setting in Windows. Phone only recognised as a MTP USB Device in devide manager, and flash tool does not seem to want to do anything. Might try this on a Win 7 laptop tomorrow. HJow you guys getting on with this?
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
pitrus- said:
download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.
same issue
Hi everyone!
I've got the same issue: I allowed the OTA update to 20151105 firmware release from previous version (20150725), after the upgrade, the phone keeps in a bootloop with a new colored Elephone logo.
I can't find a valid set of drivers, I tried a lot over the night, but windows don't recognize the phone.
PLEASE some kind soul could link a valid driver package to use SP tool ?
thanks a lot in advance!
mr..speed said:
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.
Click to expand...
Click to collapse
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
pretty much did the same thing and it worked!! Cheers!! (also had the rage and it took ages to find english on the tool lol :laugh: )
when you get the android with the "no command" message, let go of the volume and power buttons. Then hold the POWER BUTTON for 1-2 seconds and TAP VOLUME UP while still holding the power button. this will open the recovery options
omg!!
disabling the Windows install signed drivers only setting!!
i thought we wouldnt have to do things like this since Windows 95
Lol
Worked for me
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
What if no Windows?
Edit: Never mind, I got myself a windows computer and succeeded. Thanks for all the orientation!
Hi all,
Thanks a lot for posting a solution to this problem so quickly. I am affected by the same issue. Looking to buy some LSD to better enjoy the psychtrip my phone seems to be stuck in. Also looking to fix the phone.
Unfortunately, I'm running Ubuntu 14.04 LTS. I did find a guide to use the flash tool on Ubuntu, but my phone does not seem to connect. I'm guessing this has something to do with that pack of drivers 2.0, for which I have no equivalent. I would really appreciate any ideas!
I might end up returning my phone to Amazon, though. It's only been a few days since I've had it, and you can imagine that although I was really liking it, I'm beginning to change my mind.
Your advice?
EDIT: I am getting the following error message:
BROM ERROR: S_COM_PORT_OPEN_FAIL (1013)
[COM]: Failed to open COM port.
[HINT]:
I did some googling, but didn't find anything worth mentioning.
yslsl said:
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
Click to expand...
Click to collapse
Ahh good stuff. Connect phone last after hitting download - thanks for the heads up. Got my wife's p8000 today so will be doing some flashing later.
Cheers!
So after accidently wiping everything I had on both SD and Internal memory trying to make a custom rom work, I was stuck with a phone that only has TWRP on it, basically. Now after I've been through this guide TO THE LETTER: http://www.droidviews.com/install-stock-android-marshmallow-lg-g3-d855-using-twrp-recovery/ I can see it installed an OS but I cant seem to get my phone to load it! SO then I tried entering recovery mode and getting back to default, it didn't change anything, so I tried installing Zoe rom (https://forum.xda-developers.com/lg-g3/development/zoe-rom-v1-0-mm-6-0-stock-v30a-d855-t3402087) and It STILL ONLY LOADS TWRP even though the installation seemed to be successful!
So what do I need to do? Just flat out delete TWRP? or what? Pleas advise as I'm desperate. If needs be, redirect me to how to just completely reinstall everything from scratch to 6.0 or 7.0 (preferably). I was on 4.x.x for ages and I just wanted to update, instead destroyed my phone. Sigh.
UPDATE: Another thing I've tried is to flash it with KDZ file from the PC. I can see the phone, I can transfer files to it, but windows DOES NOT recognize in the device manage so when I tried to use the flash tool, after clicking "Start" it pops a new window which gets to 60% and then stops saying the phone is not connected to the pc.
Malkishua said:
So after accidently wiping everything I had on both SD and Internal memory trying to make a custom rom work, I was stuck with a phone that only has TWRP on it, basically. Now after I've been through this guide TO THE LETTER: http://www.droidviews.com/install-stock-android-marshmallow-lg-g3-d855-using-twrp-recovery/ I can see it installed an OS but I cant seem to get my phone to load it! SO then I tried entering recovery mode and getting back to default, it didn't change anything, so I tried installing Zoe rom (https://forum.xda-developers.com/lg-g3/development/zoe-rom-v1-0-mm-6-0-stock-v30a-d855-t3402087) and It STILL ONLY LOADS TWRP even though the installation seemed to be successful!
So what do I need to do? Just flat out delete TWRP? or what? Pleas advise as I'm desperate. If needs be, redirect me to how to just completely reinstall everything from scratch to 6.0 or 7.0 (preferably). I was on 4.x.x for ages and I just wanted to update, instead destroyed my phone. Sigh.
UPDATE: Another thing I've tried is to flash it with KDZ file from the PC. I can see the phone, I can transfer files to it, but windows DOES NOT recognize in the device manage so when I tried to use the flash tool, after clicking "Start" it pops a new window which gets to 60% and then stops saying the phone is not connected to the pc.
Click to expand...
Click to collapse
I just got over something like this this morning. First, you need to ensure you have the LG Universal drivers installed for your phone. Get them here.
Next, reboot your machine.
After this, I made sure the PC recognized all 3 modes of my phone, TWRP mode (boot to TWRP, connect), Download Mode (boot to download mode with cable) and, at least in my case, the flashing lights mode (shows up as QHUD Bulk or something).
After that, I ran the KDZ restore program successfully.
Good luck and let me know how it goes.