Database Info

[Q] LG G2 stuck in boot loop

I just got the international LG G2 D802 model. I installed the KitKat 4.4.2 update, rooted, and then installed TWRP. Everything was fine, but I noticed there was another OTA update available, and when I tried to install that my phone got stuck in a boot loop.
I was able to restore it using the the following command:
dd if=/dev/zero/ of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero/ of=/dev/block/platform/msm_sdcc.1/by-name/misc
That brought it back to stock, and thinking everything was ok, I tried to update again. Now the above commands will not work, possibly because I hadn't rooted and turned on USB debugging yet. When I select reboot from the TWRP menu, I get a message asking if I want to root with SuperuserUS, but it doesn't work.
I've tried everything, including all the LG flash tools, and nothing works.Because I've got the international version, but I'm with Telus, I can't find/select the proper stock ROM.
I'm really hoping I can avoid a $600 brick.

[Q] AT&T's 6-11-14 FOTA crashed my rooted D800

I need help to restore my phone to functioning. It only boots into TWRP.
Before the ATT FOTA, the phone was running stock OTA KitKat 4.4.2 with latest kernel. It was rooted with ioroot 2.5. I also installed TWRP 2.7.0 to evaluate custom ROMs. I had done a nandroid a month back, but I can't recover it in TWRP as it's not listed. TWRP indicates I may have lost root access and tries to reinstall SU to no avail. I did a wipe of everything but data, so there is no SU to run.
I've got my computer setup with ADB 1.0.32, but I'm not able to get the LG unified USB driver to work. This has halted me as I hoped to push a ROM onto the phone.
Please help!

I have the same problem with my phone any help much appreciated. Except I have a backup nandroid and the process went thru but my phone only boots into twrp. I've tried factory reset and reinstalling my custom ROM and again my phone just reboots into twrp
Sent from my XT1028 using XDA Premium 4 mobile app

Salguod said:
I need help to restore my phone to functioning. It only boots into TWRP.
Before the ATT FOTA, the phone was running stock OTA KitKat 4.4.2 with latest kernel. It was rooted with ioroot 2.5. I also installed TWRP 2.7.0 to evaluate custom ROMs. I had done a nandroid a month back, but I can't recover it in TWRP as it's not listed. TWRP indicates I may have lost root access and tries to reinstall SU to no avail. I did a wipe of everything but data, so there is no SU to run.
I've got my computer setup with ADB 1.0.32, but I'm not able to get the LG unified USB driver to work. This has halted me as I hoped to push a ROM onto the phone.
Please help!
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/showthread.php?t=2451696

The above thread is how I got mine to boot again but it became unrooted so I flashed latest supersu 2.0 in recovery. I'm pretty sure everything is back to normal again.

More help needed...
DvineLord said:
The above thread is how I got mine to boot again but it became unrooted so I flashed latest supersu 2.0 in recovery. I'm pretty sure everything is back to normal again.
Click to expand...
Click to collapse
I followed the thread and I used the TWRP command line to run:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Below is the output:
Updating partition details…
Full SELinux support is present.
/ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd: writing ‘/dev/block/platform/msm_sdcc.1/by-name/fota’: No space left on device
65537+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied,
1.813425 seconds, 17.6MB/s
The phone is still stuck in a boot loop and loading TWRP. Any recommendations?

Salguod said:
I followed the thread and I used the TWRP command line to run:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Below is the output:
Updating partition details…
Full SELinux support is present.
/ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd: writing ‘/dev/block/platform/msm_sdcc.1/by-name/fota’: No space left on device
65537+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied,
1.813425 seconds, 17.6MB/s
The phone is still stuck in a boot loop and loading TWRP. Any recommendations?
Click to expand...
Click to collapse
Try restoring your nandroid now. If you wiped everything except data as you indicated in your OP, then you currently have no system installed.
Sent from my LG-D800 using Tapatalk

What do i need to freeze or uninstall to prevent this from happening again?

[Q] HELP! I'm stuck in recovery

I just upgraded to the latest firmware last night using this method
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
I installed latest TWRP straight from their website and then flashed adrenaline 2.0
http://forum.xda-developers.com/ver...ent/rom5-0-1sense-6-0adrenaline02-06-t3023868
That was last night. This morning I decided that the smart thing to do now that my phone was up and running was to make a backup. I rebooted to recovery, and lo and behold TWRP disappeared. I rebooted to system and went into terminal emulator and installed TWRP again and rebooted to recovery, made a backup, and tried rebooting to system. It rebooted to recovery. I shut my phone (holding power and volume up) and tried turning it back on again, and it went to recovery. I went into fastboot and hit reboot from there, and it went into recovery. I restored the backup I had made minutes before and hit reboot system, and it rebooted recovery.
What is happening?

pie_are_squared said:
I just upgraded to the latest firmware last night using this method
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
I installed latest TWRP straight from their website and then flashed adrenaline 2.0
http://forum.xda-developers.com/ver...ent/rom5-0-1sense-6-0adrenaline02-06-t3023868
That was last night. This morning I decided that the smart thing to do now that my phone was up and running was to make a backup. I rebooted to recovery, and lo and behold TWRP disappeared. I rebooted to system and went into terminal emulator and installed TWRP again and rebooted to recovery, made a backup, and tried rebooting to system. It rebooted to recovery. I shut my phone (holding power and volume up) and tried turning it back on again, and it went to recovery. I went into fastboot and hit reboot from there, and it went into recovery. I restored the backup I had made minutes before and hit reboot system, and it rebooted recovery.
What is happening?
Click to expand...
Click to collapse
OK, I found out what (I think) happened and here is my solution for the next poor bastard who makes the same mistake.
When I installed TWRP I followed their instructions which was to load an adb shell and type the following
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p44
however here was the problem, in the latest update the partitions were changed so mmcblk0p44 (which I'm guessing was recovery in days of old) is now boot and mmcblk0p45 is recovery. When I followed TWRP's directions, I think I basically put the recovery in the boot which was why when I tried booting up it always went to recovery.
Moral of the story put the twrp.img in mmcblk0p45 not in mmcblk0p44
source for the partition change is the second comment on this thread:
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
P.S. If anyone knows any of the people at TWRP ask them to change it their instructions

pie_are_squared said:
OK, I found out what (I think) happened and here is my solution for the next poor bastard who makes the same mistake.
When I installed TWRP I followed their instructions which was to load an adb shell and type the following
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p44
however here was the problem, in the latest update the partitions were changed so mmcblk0p44 (which I'm guessing was recovery in days of old) is now boot and mmcblk0p45 is recovery. When I followed TWRP's directions, I think I basically put the recovery in the boot which was why when I tried booting up it always went to recovery.
Moral of the story put the twrp.img in mmcblk0p45 not in mmcblk0p44
source for the partition change is the second comment on this thread:
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
P.S. If anyone knows any of the people at TWRP ask them to change it their instructions
Click to expand...
Click to collapse
It might be that way but when TWRP first came out for our phone they had the same mistake in the instructions then and forever went by without it being changed. Might be it still hasn't been changed. I don't know. That said, it's best to flash it using fastboot. In my opinion anyway. It's never failed me.

Definitely did slide down (or up) one. Anything from where VZW_quality went in on down increased by one....
and agreed with you.. no one should be flashing any img using terminal and DD commands from within the rom anymore....

Flash recovery not working!

Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.

angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose

I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers

did not work for me anywhere to be found stock 4.4.2 recovery img for 926?

[Q] LG G3 is constantly rebooting into TWRP, can't get a normal boot

Guys I'm freaking out, I installed TWRP while on 4.4.2 and then later tried to install the OTA Lollipop update. My phone rebooted into TWRP, and now it won't stop. Even normal reboot option continues to reboot it into TWRP.
I tried flashing another ROM, I tried factory resetting from the TWRP menu, I tried rebooting to recovery then rebooting normally, nothing is working.
Please, what can I do?

MaliciousBanjo said:
Guys I'm freaking out, I installed TWRP while on 4.4.2 and then later tried to install the OTA Lollipop update. My phone rebooted into TWRP, and now it won't stop. Even normal reboot option continues to reboot it into TWRP.
I tried flashing another ROM, I tried factory resetting from the TWRP menu, I tried rebooting to recovery then rebooting normally, nothing is working.
Please, what can I do?
Click to expand...
Click to collapse
So your completely formatting system and then flashing a custom rom? That should fix it if not just follow my back to stock guide.
Sent from my iPhone using Tapatalk

I found your back to stock guide, you're sure it will work? I'm trembling in anticipation here because the .TOT file is going to take 5-6 hours to download, and I've got work really early in the morning. If it doesn't work I have no idea what I'm going to do.

http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/. link to unbrick.
or try this. i just had bootloop and nothing worked except this
Found this on AndroidCentral: Saved my life – it got my phone back to original. Hope this helps others.
*****************************************************************************************************************
What worked for me was from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.

I was able to fix the phone a few nights ago; I was on the road and never had a decent internet connection to update.
The return to stock method ended up working. Although, the process failed about six times before finally going through.