I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app
lingarajug said:
I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I have more or less the same issue. Was with StockMod for D802 and received an official OTA and accepted and installed it. Now I'm stuck in bootloop. Unlike you, I can go into recovery (CWM not TWRP) BUT I can't seem to go into fastboot mode. When I hold the Volume Up and connect the phone through cable to my laptop, the phone boots but goes automatically into recovery mode. Did system wipe as well (which I shouldn't have) and at that point my phone has no OS to boot into so I used ADB to transfer CM 10.2 and GAPPS to my phone hoping that if I do it like I'm flashing a custom rom will help but unfortunately it didn't. I'm still stuck in bootloop and can't go into fastboot. help please...:crying:
Try a stock Rom and see if it helps.
Sent from my LG-D800 using xda app-developers app
Related
So I messed up my Nexus somehow. I was trying to install MIUI coming from Carbon ROM but something went wrong as it got stuck on the miui logo. So I rebooted to TWRP and restored my backup. So then I tried to install PA and then it just got stuck on the google logo. So i restored my backup again and tried again to no avail. Then after that I couldn't restore my backup ( I keep getting FAILED as soon as the data restore starts). I can boot to Recovery but I dunno what to do. I tried sideloading but that's not working. I tried the toolkit but everytime it tries to download the factory image it says 404. The phone charges and whatnot but I don't know what to do. I only have the PA rom on my phone and reinstalling it doesn't do anything. The only weird thing is that when I try to install the PA gapps I get a FAILED message. Any help would be appreciated
varem said:
So I messed up my Nexus somehow. I was trying to install MIUI coming from Carbon ROM but something went wrong as it got stuck on the miui logo. So I rebooted to TWRP and restored my backup. So then I tried to install PA and then it just got stuck on the google logo. So i restored my backup again and tried again to no avail. Then after that I couldn't restore my backup ( I keep getting FAILED as soon as the data restore starts). I can boot to Recovery but I dunno what to do. I tried sideloading but that's not working. I tried the toolkit but everytime it tries to download the factory image it says 404. The phone charges and whatnot but I don't know what to do. I only have the PA rom on my phone and reinstalling it doesn't do anything. The only weird thing is that when I try to install the PA gapps I get a FAILED message. Any help would be appreciated
Click to expand...
Click to collapse
Have you tried to install another rom on your nexus?
you can put it on with adb push command from recovery though a pc, and then wipe everything and try to install it.
Or you can download stock 4.2.2 rom here: http://forum.xda-developers.com/showthread.php?t=2147281
Here you can find your factory image directly from google: https://developers.google.com/android/nexus/images#occamjdq39
How do I adb push?
varem said:
How do I adb push?
Click to expand...
Click to collapse
you must enter into recovery, connect your phone to your pc with usb cable and then you should be able to see your device,
try
Code:
adb devices
on CMD and it can see your phone type
Code:
adb push **your-rom-from-computer** /sdcard/
then just install it from the recovery
When you say recovery do you mean the main menu? I'm using TWRP and when I'm on the main menu my PC doesnt read the device
http://forum.xda-developers.com/showthread.php?p=34674471
My bad I should have read.....you tried a tool kit already
Sent from my Nexus 4 using xda app-developers app
mmh i don't have twrp so i don't know, do you have the option to mount sdcard to usb?
varem said:
When you say recovery do you mean the main menu? I'm using TWRP and when I'm on the main menu my PC doesnt read the device
Click to expand...
Click to collapse
Ok, wait. I need some clarification. I'm going to try to be as simple as possible, to make sure we are on the same page. When you say your PC doesn't read the device, do you mean through adb or on Windows Explorer?
If you mean through Windows Explorer, then that is not where you need to be. You must get adb working as a bridge to your device. Use this sticky guide to get it set up. I would recommend reading that guide top to bottom anyway, it's extremely informative and new-user friendly. Anyway, the info you need is in the 'Setting up ADB for our device:' section.
If you have adb installed, you need to check to see if it recognizes your device. Do this by opening up cmd and navigating to the folder that adb.exe is located. After that, use 'adb devices' to see if adb recognizes your device. If so, move to the next paragraph. If not, your drivers aren't set up properly for recovery mode. Go into Device Manager on your computer and find your device (under something like 'Other devices', or 'Android device'). If you find it, then get these drivers and install them for the device. Do this by right-clicking, and selecting 'Update Driver Software...', 'Browse my computer for driver software', and browse to that folder. I may have missed a few steps on installing the drivers, it's been a while. If so, just search on how to do it, or post back here. I'm sure I can walk through it and get a more precise guide.
Assuming you have adb installed and it recognizes your device, you need to open up cmd and navigate to the folder that adb.exe is located. Then, use the adb push command as outlined above.
Download stock images from Google's website and flash it via fastboot. If you don't know how to do it then use a toolkit like WuguFresh to do it for you.
Sent from my Nexus 4
You can also use the toolkit for pushing a ROM in your SDcard, or backup your SD in your pc.
Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
The PC reads the device as it detects it but when I type in adb devices it doesnt show up. It only ever shows up when I enter the sideload menu in TWRP
atulalvenkar said:
Download stock images from Google's website and flash it via fastboot. If you don't know how to do it then use a toolkit like WuguFresh to do it for you.
Sent from my Nexus 4
Click to expand...
Click to collapse
Thanks man. This toolkit saved my nexus!
Sent from my Nexus 4 using xda premium
Hi,
I use F320L and I am under boot loop
I was planning to run the flash tool... but it needs download mode...
may be some partitions are messed up so that even I flash stock version, it never moves on to next step...
I've been searching Q&A thread and couldn't find suitable solution for me T_T ( there were similar situations but not exact same)
I've tried this one
http://forum.xda-developers.com/showthread.php?t=2477595
but my phone never goes to fastboot
and also I read this one
http://forum.xda-developers.com/showthread.php?t=2582142
however, I can't install ubuntu for that I am using my company's computer
one good thing is that I can use adb in the cwm
but I don't know what to do with it
may be my best chance is to restore download mode and repartition all of device via flash tool.
it would be very very helpful and thankful if someone gives me any idea....
urusaikara said:
Hi,
I use F320L and I am under boot loop
I was planning to run the flash tool... but it needs download mode...
may be some partitions are messed up so that even I flash stock version, it never moves on to next step...
I've been searching Q&A thread and couldn't find suitable solution for me T_T ( there were similar situations but not exact same)
I've tried this one
http://forum.xda-developers.com/showthread.php?t=2477595
but my phone never goes to fastboot
and also I read this one
http://forum.xda-developers.com/showthread.php?t=2582142
however, I can't install ubuntu for that I am using my company's computer
one good thing is that I can use adb in the cwm
but I don't know what to do with it
may be my best chance is to restore download mode and repartition all of device via flash tool.
it would be very very helpful and thankful if someone gives me any idea....
Click to expand...
Click to collapse
Since you can use adb it should be simple, download a rom i used cyanogen mod to recover mine http://download.cyanogenmod.org/
Make sure you have the adb drivers
open CMD on pc and sideload mode on CWM
enter the below commands one by one into cwm
"
cd \adb
adb kill-server
adb usb
adb devices
adb sideload zipname.zip
"
Cwm should then install the zip, wipe data/davlik/cach and reboot.
once you boot up again you should be able to turn it off and enter download mode
how to enter download mode
alex xander said:
Since you can use adb it should be simple, download a rom i used cyanogen mod to recover mine http://download.cyanogenmod.org/
Make sure you have the adb drivers
open CMD on pc and sideload mode on CWM
enter the below commands one by one into cwm
"
cd \adb
adb kill-server
adb usb
adb devices
adb sideload zipname.zip
"
Cwm should then install the zip, wipe data/davlik/cach and reboot.
once you boot up again you should be able to turn it off and enter download mode
how to enter download mode
Click to expand...
Click to collapse
thx for the tip!
I tried what yo wrote for me...
but it is not working.
actually the rom is installed but there is sth wrong with some partition I think
thx anyway, may be I should try to find another way
OK. I have spent the last 8 hours reading and trying my darnedest to get my phone up and running.
I wiped everything, and formatted data accidentally.
Now the phone wont mount the USB so I can put a ROM on it. I cannot get drivers to make either the skipsoft toolkit or the WugFresh tool kit to work.
I have read on ADB side loading, but cannot figure out how to get the phone to get recognized in order to connect with it. As it sets right now, I am stuck at the bootloader image, or TWRP recovery. No image on the phone, and I cant seem to get the drivers to allow my PC to see the phone. (Ive used WugFresh drivers, naked drivers)
Any help you guys can give me would be awesome.
Thank you
Mark
Hey there,
Our phones are MTP devices and because of that (I think) we can't mount them as a usb drive. But yea you can use adb sideload to get yourself up and running again.
For the drivers try this: http://forum.xda-developers.com/nexus-4/orig-development/toolkit-skipsoft-android-toolkit-nexus-t1995688
On your Phone:
1. Boot into TWRP,
2. Tap advanced,
3. Tap adb sideload,
4. Swipe to start sideload.
Once it says its waiting or something like that, it's ready to sideload from the PC.
On your PC:
Put the rom you wanna flash in the same folder as adb. So if adb is in C:\adb\ then put the file there.
In CMD type in adb sideload filename.zip (filename.zip is the name of your file you want to flash)
So an example would be:
Code:
c:\adb>adb sideload CARBON-JB-NIGHTLY-20131117-1149-mako.zip
It'll take a bit to transfer the file, but once it finishes you should be able to boot into the rom and use it normally again.
Hope it works for you, regards...
You can use Wugfresh to restore to stock and start over.
Dear people of xda,
Recenlty ive receive a FOTA update to my device which runs 4.2.2. Being stupid, i did the update although i had cwm recovery installed on my devices. Now my device keeps bootlooping into cwm without being able to do anything.
Ive read tons of threads talking about this issue but i still cant get my to boot normally.
Yingy in this thread http://forum.xda-developers.com/showthread.php?t=2563527 had the same problem but the only diffrence is my pc cant recognize my device in order to do the adb fix by thecubed.
Im plugging my G2 for the first time in this computer and that is why i think my pc is failing to install drivers. I downloaded and instellad latest driver although windows device manger shows error devices not detected and the end of the process.
In order to fix my phone i just need to make me pc recognize my phone in adb although phone was never plugged before to this pc so i think my G2 wont let it access. I tried installing universal driver such as Pdanet as offered in threat but still when i write adb devices in cmd i get device offline!
Download latest adb drviers, lates lg g2 driver, lg user support tool does not recognize plugged device as well. All me sdk manger tools are patched to latest version.
PLEASE ive tried anything possible. spend like 9 hours and still nothing. i would really appriciate your help.
Thanks.
Edit: here my problem with pdanet drivers, it asks me to allow pc usb debbuging as shown in screenshot below but icant do it since im stuck at cwm recovery!
Solved!
BOOM!! after 12 hours i FINALLY manged to solved this problem. Really simple actually lol.
If anyone come across the issue please do the following:
1. Go to clockwork recovery as always, go to install zip from sdcard, choose install zip from sideload.
2. Plug your phone to pc.
3. Run adb with lastest drivers and sdk tools.
4. At the adb folder press shift+right click and start cmd.
5. write adb devices it should show your device id like this (xxxxxxxxx sideload).
6.Download latest twrp recovery from here http://teamw.in/project/twrp2/197 and if you have open europe version G2 like me download latest version from here: http://techerrata.com/browse/twrp2/g2d802
7.put the zip file in the adb folder, do not unzip it.
8. write in cmd console adb sideload xxxx.zip (xxxx is the name of twrp file).
9. cwm will flash twrp recovery over cwm.
10. reboot in recovery in advanced options.
11. now you have twrp recovery.
12. follow this guide : http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
13. THATS IT!!!
finally after going through this mess, im never using cwm recovery again. twrp is the best
good luck everyone!
I really need help, I have tried the following, having TWRP V2.8.5.1 functioning and Fastboot also.
- Through TWRP, tried connecting the PC so I can Flash a ROM from there, but I can't seem to be able to connect the One to my PC so it will let me transfer files through cmd with adb push. My computer is a windows 10 OS with Samsung drivers and Android SDK full installed, still can't get it to work.
- Through Fastboot tried flashing cm-11-20141008-SNAPSHOT-M11-bacon.zip downloaded from Cyanogenmod page and using Oneplus One Toolkit 2.0, even though the Toolkit says the files are there, still phone continues to show 1+ logo and then rebooting.
Please I need some help.
Cheers. and thank you.
Why adb push when you can just copy the file over using a file manager (or a command prompt if you insist) and then flash from the internal storage?
I'm having the same issue but in my case I can boot into recovery or other stuff IF I HAVE THE USB PLUGGED IN
Maybe you can check and and let me know, if I found a solution I'll tell you, hoping the same from you please.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 this could help.