I rooted my phone and installed FreeGee to install the TWRP bootloader. Followed all the instructions, but now every time I power on the phont it goes to recovery mode and I can't get out. Even if I reboot it always goes to recovery. It says this: Android system recovery <3e>
I tried restore using LGNPST but it still only boots into this screen. I can't get back into Android. Help please
davelee1054 said:
I rooted my phone and installed FreeGee to install the TWRP bootloader. Followed all the instructions, but now every time I power on the phont it goes to recovery mode and I can't get out. Even if I reboot it always goes to recovery. It says this: Android system recovery <3e>
I tried restore using LGNPST but it still only boots into this screen. I can't get back into Android. Help please
Click to expand...
Click to collapse
I had this same issue last night. I ended up using LGNPST on the entire 800MB firmware .bin for 4.1.2 in order to get back to it. I lost all my apps and whatnot, but I thought it was worth it to have my phone be a phone again.
The issue is the reboot to recovery flag is set in your misc.
Run these commands from an adb shell to clear it:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/data/media/misc-bad-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
bump can someone help me out with this i cant even select anything
So I was trying to flash my recovery using dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p5
I now know it was dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Problem is that now the power button doesn't do anything. I can't turn it on, can't access recovery, or download. Odin does not recognize the device either.
What should I do?
R50731205 said:
So I was trying to flash my recovery using dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p5
I now know it was dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Problem is that now the power button doesn't do anything. I can't turn it on, can't access recovery, or download. Odin does not recognize the device either.
What should I do?
Click to expand...
Click to collapse
What you have done is cooked your bootloader. The mmcblkop5 block is sopposed to have an aboot.img file there. Since you cant access recovery or download you will likely need to attempt ADB. I do not have the best knowledge of ADB, but this is the road you should be looking down. That is if you haven't completely bricked it. Your other option may be jtag.
These following threads will probably be of interest to you. There are reports of this working so you may want to follow their instruction.
http://forum.xda-developers.com/showthread.php?t=2345860
http://forum.xda-developers.com/showthread.php?p=43724690
I'm not sure what to do for ADB, nor jtag. I don't even know what they are. I looked at the two links you provided, one I tried but it didn't do anything. The other wasn't applicable.
My phone is non-responsive to pressing the power button, it can't access download or recovery mode, which means odin couldn't have recognized it.
Can you expand on ADB or jtag?
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
We I accept the update to lollipop my phone restart and now is dead...
My phone was a twrp recovery but can't access now... No download mode works...
No screen turn on...
Only my Pc recognize on hardware QHSUSB_BULK
LG TOOLS not reconigce....
Please and help to resurrection my phone...
celtichazard said:
We I accept the update to lollipop my phone restart and now is dead...
My phone was a twrp recovery but can't access now... No download mode works...
No screen turn on...
Only my Pc recognize on hardware QHSUSB_BULK
LG TOOLS not reconigce....
Please and help to resurrection my phone...
Click to expand...
Click to collapse
You can never take an OTA update with a custom recovery. See this thread http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 it may help.
acefsw said:
You can never take an OTA update with a custom recovery. See this thread http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 it may help.
Click to expand...
Click to collapse
My phones don't enter in to download mode screen is turned of all the time
celtichazard said:
My phones don't enter in to download mode screen is turned of all the time
Click to expand...
Click to collapse
its bricked, you have to do some research on what you can do......if anything
never take an OTA if you are not 100% stock
decaturbob said:
its bricked, you have to do some research on what you can do......if anything
never take an OTA if you are not 100% stock
Click to expand...
Click to collapse
all ready do a research all day and no luck to fix
So when the phone is off and you hold the volume up button and plug in the usb it won't go into download mode?
vel0city said:
So when the phone is off and you hold the volume up button and plug in the usb it won't go into download mode?
Click to expand...
Click to collapse
Yeah, I'd at least try a battery pull, have all the drivers/downloads etc. ready for TOT. make sure the usb is plugged in to computer side on a usb 2.0 port, then attempt volume up/plug usb into phone.
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
TheCoutures said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
His screen doesn't turn on, so no TWRP access. He needs download mode or likely a jtag if he can't get that. Battery pull might help or be absolutely useless, especially since his computer is just recognizing the qualcomm chip
Here's some research links celtichazard https://www.google.com/search?q=QHS...458045j0j0&sourceid=chrome&es_sm=122&ie=UTF-8 don't give shady strangers money to unbrick
---------- Post added at 12:35 AM ---------- Previous post was at 12:20 AM ----------
Read this http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853
TheCoutures said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
Sorry but the phone dot turn the screen thanks
celtichazard said:
Sorry but the phone dot turn the screen thanks
Click to expand...
Click to collapse
Read the links posted above, especially the 2nd one. Also, https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/ is for a one + one phone, not ours, but explains some of what it takes to restore the files for the chipset
acefsw said:
Read the links posted above, especially the 2nd one. Also, https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/ is for a one + one phone, not ours, but explains some of what it takes to restore the files for the chipset
Click to expand...
Click to collapse
Thanks dude but the only problem is I cant find the right driver to make it work
this is my device manager detect whe I plug the phone
Thanks TC the fix worked. Thought I had OTA disabeled
So, I was performing the root process, and on step 3 I accidentally pasted the H810PR instead on H810ATT. Phone will not boot, but I can enter Download mode.
The problem is that when I'm using the Send_Command, the commands do not work. Sometimes I will get a very long pause after the DD command (I let it run overnight - doesn't work), or I get an immediate #. I've tried using the "id" command as well and nothing ever returns.
I have the original system.img on the phone as well as the rooted one. I just can't get the phone to run the dd command. When I type LEAVE, the phone restarts so I know it is communicating.
Any thoughts?