Correct me if i'm wrong.. but I did a "adb reboot recovery" to do a hard reset on the phone... this is the screen I was presented with. All it says is "No Comment"...
Related
I have seen some people suffering this issue like I did before and Other guys just offering the advice of " Use LG flash tools to flash to stock"
Yes, it could solve the problem. But it takes so much effort and hustle to fix such a easy issues.
There is always a easy way to solve a problem. Keep reading.
This method should work for LG Optimus G Pro using the same recovery. Like E980, E985, E986. I only try this on my phone (AT&T E980)
Issue:
Your phone keep boot into CWM or TWRP all the time, no mater what you did- factory reset, wipe system, install new rom. It just keep going into recovery all the time.
What might cause this:
You install recovery in your phone and when you are in stock rom, you accidently hit "check update" and " install update".
You might not remmeber you did that , and the system just pop up showing " update available", and you click it....That is how the nightmare starts.
How to fix
If you are using CWM, try this method: http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70 But I personally like the TWRP method below ( just flash TWRP over CWM and use the TWRP method bellow)
remember hit thanks to @chappatti
Following these steps:
1.a. If you are stuck on CWM OR TWRP boot loop DO NOT DO ANYTHING YET to the phone or anything. All you need to do is delete the "fota" file. keep reading
1.b. YOU MUST HAVE ADB INSTALLED AND WORKING.
1.c. Open cmd prompt as admin and run "adb devices". If you get
"List of devices attached
XXXXXXXX recovery" GO TO STEP 7.
If you HAVE adb installed and get no device output....continue from 2.
Otherwise, INSTALL ADB.
2. With the phone in CWM plug it into the computer.
3. Your computer MAY not see the phone. i.e you will get the ping noise for USB cnnection, but if you look under
COntrolPanel>>>>DeviceManager you will see a yellow exclamation mark. The next part I figured by trial and error.
If your phone is seen properly go to step 5.
4. If 3: although I installed the drivers again, if you had the phone working on adb before try this step:
4.b. Press and hold the Volume DOWN (volume decrease) button and hold the power button.
NOTE: I am not 1000% whether volume up or down did it. Try each one.
HOLD until the phone goes off and reboots. After the LG logo release the power. You will see black and white text as the phone tries to go into factory reset. It will ask if you want to factory reset...... SAY NO by pressing volume down button. During reboot my computer saw my phone and installed the driver. Phone was still on CWM recovery now.
4.c. If 4.b. did not work reinstall following drivers (attached rar): I do not know which worked, if any
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.1 0.1
minimal_adb_fastboot_v1.1.3_setup
UniversalAdbDriverSetup
LGPCSuite_Setup
http://www.mediafire.com/download/1j...nd STUFF.rar
5. These steps I got from this forum post here: I DO NOT CLAIM ANY CREDIT http://forums.androidcentral.com/t-l...ot-loop-2.html
6. Open cmd promt as administrator.
7. Run "adb devices"
You will get
"List of devices attached
XXXXXXXX recovery" Now you are good to proceed
Enter the following one by one
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
it will say xxxx info in and out or soemthing each time.
Type "exit" to leave adb shell.
Then "adb reboot". This will reboot your phone and all is great !!
If you are using TWRP, or the method above did not work for you, flash TWRP as your recovery, then using this TWRP method.
remember to hit thanks to @thecubed here is the post: http://forum.xda-developers.com/showthread.php?t=2451696
you can simply use TWRP's awesome "terminal command" option to run the following code
go to "Advance" " Terminal Command", select the current folder( root folder), and type the following code:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
I took no credit for these method, they are work of other XDA members.
Hit thanks if any of us help you solve your problem.
This is VERY good work! THANK YOU!
Sent from my LG-D415 using XDA Free mobile app
Hello Forum!
Sorry for my English.
My Chinese Nokia N1 is bricked.
Why bricked:
After change file build.prop extracted from file uploaded by XDA user (I can't find a thread), my tablet only boot to screen "Powered by Android".
Nokia can't do power off. Allways reboot after many seconds hold power key.
Next what I do:
ADB working, but i dont have permission to change this file (i have backup build.prop).
I do all (IMO) to change permission to /system (read-only):
- mount -o rw,remount ...
- adb remount
etc.
Don't work power button and volume down.
And I have an idea ...
I run script to root Nokia from XDA.
Look great.
From recovery menu I mount /system to read-write.
After adb shell and mount command i see /system is read-write, but any changes/copy file = operation not permitted.
I try (of course after su).
- busybox mount -o rw,remount ...
- busybox chmod 777 /system
still "operation not permitted"
I'm disappointed.
And I run system/factory reset from recovery menu after run root script.
Now:
- still boot to screen "powered by android"
- adb not working, I don't have device ADB in Windows device manager
- power and volume up give me device: moorefield in windows device manager
- downloaded "Intel Phone Flash Tool Lite", and I see my Nokia after power & volume UP is connected in this software.
What next, what I need for unbrick? If they can...
Please help.
what's your current version?
Xkernels said:
what's your current version?
Click to expand...
Click to collapse
A5CN51C
you're better than me, my device can not even enter recovery mode, it keeps on turning and turning around after Powered by Android animation
Still needs help. I donate if my problem resolved.
Mine was stuck at "power by android" screen, it keeps looping to that screen.
Took me a few days of trying different things, I found the tablet was showing up on "adb devices" when it boots to "power by android" screen.
It shows up after maybe 30sec - 1min after you get to that screen.
When you run this command "adb devices"
If your device shows up.
You can run "adb reboot bootloader" or "adb reboot recovery"
If you device doesn't show up, you will have run "adb kill-server", otherwise it will never show up.
then run " adb devices" again.
Try a few time, if this works, you're in luck.
After you get into the bootloader, you can get into recovery mode, and use sideload to flash a full image.
http://forum.xda-developers.com/nokia-n1/general/nokia-n1-chinese-version-5-1-1-update-t3183529
Pick a full size image newer or the same to your current version.
adb sideload image_filename
kourcomp said:
Mine was stuck at "power by android" screen, it keeps looping to that screen.
Took me a few days of trying different things, I found the tablet was showing up on "adb devices" when it boots to "power by android" screen.
It shows up after maybe 30sec - 1min after you get to that screen.
When you run this command "adb devices"
If your device shows up.
You can run "adb reboot bootloader" or "adb reboot recovery"
If you device doesn't show up, you will have run "adb kill-server", otherwise it will never show up.
then run " adb devices" again.
Try a few time, if this works, you're in luck.
After you get into the bootloader, you can get into recovery mode, and use sideload to flash a full image.
http://forum.xda-developers.com/nokia-n1/general/nokia-n1-chinese-version-5-1-1-update-t3183529
Pick a full size image newer or the same to your current version.
adb sideload image_filename
Click to expand...
Click to collapse
Thanks You for answer.
I do a lot reboot after system/factory reset from recovery menu, and i never got adb device in windows device manager.
Without this device I do not have the ability to gain access to the adb device.
Hello everyone.
i have a problem with installing the ROM. Actually, i installed the rom before. But today, i just want a new installation. So i earlier flashed "TWRP - 2.8.5.1 BIG" recovery.
Today, i wanted to reinstall "CM12 -20150214" (android 5.0.2) rom to my telephone since when the phone is opened, i got "Trebuchet stopped" error all the time.
So reinstalling the rom, I followed the steps:
* wipe -> format data
* reboot into recovery
* Mount -> first "disable mtp", then "enable mtp". Then copy the rom_file.zip & gapps.zip to internal storage
* wipe -> factory reset
* install -> i chose the romfile.zip
* reboot into bootloader (in this part, i got an error on my win7 as "driver could not be installed")
HERE, THE PROBLEM OCCURS: i want to flash boot.img by opening cmd with "fastboot flash boot boot.img" command. But i just see a message "WAITING FOR DEVICE". and i can not flash the boot.img file.
in this step, on my phone screen i see, "fastboot usb" but vol up or vol down buttons does not work. when i put off my cable, i see " fastboot", and vol up or vol down buttons start to function. and when i put it on again, i see "fastboot usb" & all buttons dont work again.
i checked over internet, found many things about "adb driver fixes", but nothing work.
i am not sure that i enabled "usb debugging" earlier than the process. i just do not remember. problem occurs because of this?
By the way, in computer, device manager, i see two unknown things. inside the other devices, i see "Fastboot" & "unknown device". But i can not update the drivers. i show the adb tools folder, but does not work. i uninstalled and reinstall the drivers, but still did not work for me.
What should i do to fix it? Any idea?
i hope, the phone is not a brick now i try to give every hint. i hope, someone can help me.
problem solved
When i installed HTC drivers, problem is solved.
But now, i get "unfortunately, Google play services has stopped" prompt all the time.
any idea?
So I booted in recovery mod and had this image on the display for almost a second and then disappeared. It happens every time I enter in recovery mode.
Any idea what's up with this?
Normal, pretty sure they all do it, when they boot into recovery they look for update.zip initially and don't find it
Think I've seen it saying "Update not found" or something along those lines, nothing to worry about
Please tell me...
The device will simply boot into TWRP at normal startup (as if you were pressing the key combo or issued "adb reboot recovery" in a shell)