Database Users

[Guide] How to recover your semi-brick

YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html

[Q] Push /System to internal

Anyway to push this to internal memory?
I got /system damaged and phone is stuck in bootloop.
odin doesn't work as I am on MF3.
-----
SGH-I337
-----
Windows 7
OSX 10.9

pandaturtle64 said:
Anyway to push this to internal memory?
I got /system damaged and phone is stuck in bootloop.
odin doesn't work as I am on MF3.
-----
SGH-I337
-----
Windows 7
OSX 10.9
Click to expand...
Click to collapse
"Originally Posted by toastido View Post
I actually just did it and it did work. I used goo manager to try to write TWRP not thinking about MF3. Got a buddy who has a stock phone running MF3 (also an i337), temp pwnd it, pulled a dd of his recovery and dd'd it back to mine (rooted). I have a recovery again!
Here's the MF3 recovery image I used (attached and zipped to save space)
MD5 (recovery.img) = 8bb35b1bfbf01dfb83b30ffdbb243d87
On a stock device, enabled developer mode, adb, put in my sdcard with pwn on it, got root. Then did:
adb shell
$ /mnt/extSdCard/pwn
...
# dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
# exit
$ exit
adb pull /sdcard/recovery.img
*disconnected the donor phone*
adb push recovery.img /sdcard/
adb shell
$ su
# dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
# exit
$ exit
Rebooted phone with vol+/home/power and it booted into recovery mode, whereas before this would get it stuck in the ODIN download screen.
YMMV of course, but it DOES work!.
-toast"
You can try to use ADB only problem is idk if works in download mode or not.

[q] help help help

My gf is on the ls980 with sprint and she is rooted on the optimus rom. twrp 2.3.4. lokified. she took the sprint ota and now the phone only boots into recovery no matter what i do. restore or load a new rom wont work. Please help..

umm
you said TWRP 2.3.4 did you mean 2.6.3.4? i know TWRP 2.6.3.4 supports OTG cables. If you have an OTG cable you could put a rom on a flash drive and it and try to flash it.

jarhead0231 said:
My gf is on the ls980 with sprint and she is rooted on the optimus rom. twrp 2.3.4. lokified. she took the sprint ota and now the phone only boots into recovery no matter what i do. restore or load a new rom wont work. Please help..
Click to expand...
Click to collapse
Search and read: http://forum.xda-developers.com/showthread.php?t=2451696

Saving LG G2 after unwanted OTA caused boot loop
doktor buknasty said:
Search and read: http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
This works on International D802. I had stock rooted rom with CWM (6.0.4.4), Xposed ( G2 Xposed, G2 tweakbox, Advanced Power Settings, App Settings), Tasker w/ Secure Settings and whatnot. So I applied OTA. Not good for the phone and the Ingress Ressistance. I was stuck at LG screen for 2 sec, reboot, rinse and repeat. Download mode was no go. Luckily I was able to enter recovery mode. Tried to restore..no luck. And after staying up till 4AM (thanx to the xda forum). I tried G2 back to stock with kdz thread. Couldn't enter download mode. I changed few USB cables, three comps and voila it entered DL mode. Unfortunately that was on Linux box...so no LG flash tool. Arghhhhh.
Next step...Linux needed, no knowledge, just sensible use of copy/paste. Enter recovery, wipe everything you can. Reboot to recovery and yes, root please. Now you should have adb. Do the following (thank you thecube)
Code:
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
If you get any errors...don't worry. I managed to execute only line 2.
Reboot to recovery w/ root and again wipe everything (it worked for me, might not be needed), and copy/paste again.
Code:
adb shell
mount /data (disregard errors)
mkdir -p /data/media/0
exit (do not forget to exit shell)
adb push rom.zip /data/media/0
adb push rom.zip /data/media/0 ( where rom.zip is up to you..i used Black Pearl ROM)
Now watch that coursor. If it is not blinking...you are almost there. When push is completed, install rom. zip as usuall.

Franketo said:
This works on International D802. I had stock rooted rom with CWM (6.0.4.4), Xposed ( G2 Xposed, G2 tweakbox, Advanced Power Settings, App Settings), Tasker w/ Secure Settings and whatnot. So I applied OTA. Not good for the phone and the Ingress Ressistance. I was stuck at LG screen for 2 sec, reboot, rinse and repeat. Download mode was no go. Luckily I was able to enter recovery mode. Tried to restore..no luck. And after staying up till 4AM (thanx to the xda forum). I tried G2 back to stock with kdz thread. Couldn't enter download mode. I changed few USB cables, three comps and voila it entered DL mode. Unfortunately that was on Linux box...so no LG flash tool. Arghhhhh.
Next step...Linux needed, no knowledge, just sensible use of copy/paste. Enter recovery, wipe everything you can. Reboot to recovery and yes, root please. Now you should have adb. Do the following (thank you thecube)
Code:
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
If you get any errors...don't worry. I managed to execute only line 2.
Reboot to recovery w/ root and again wipe everything (it worked for me, might not be needed), and copy/paste again.
Code:
adb shell
mount /data (disregard errors)
mkdir -p /data/media/0
exit (do not forget to exit shell)
adb push rom.zip /data/media/0
adb push rom.zip /data/media/0 ( where rom.zip is up to you..i used Black Pearl ROM)
Now watch that coursor. If it is not blinking...you are almost there. When push is completed, install rom. zip as usuall.
Click to expand...
Click to collapse
DOES NOT WORK says adb not found.

jarhead0231 said:
DOES NOT WORK says adb not found.
Click to expand...
Click to collapse
Are you even on Linux? And have adb / Android sdk
Sent from my LG-D802

[Q] Is it possible to repair my installation post official updating?

So I did a number on my phone in a half asleep stupor I allowed an official update to go through while running a custom recovery and debloated kitkat. I can't believe I did this to myself. Is there anyway to repair the installation other than wiping the phone again? It was one of those mini updates, but now I boot straight to recovery instead of the operating system.

I am in the same boat you are man. I hit update now instead of later and the phone reboot into recovery and won't boot the ROM. I tried restoring a previous backup with no luck. I'm on a rooted stock ROM running twrp 2.7. Hope someone can shed some light on this.

I found an answer!
Gnex81 said:
I am in the same boat you are man. I hit update now instead of later and the phone reboot into recovery and won't boot the ROM. I tried restoring a previous backup with no luck. I'm on a rooted stock ROM running twrp 2.7. Hope someone can shed some light on this.
Click to expand...
Click to collapse
I found the answer in another thread after an exhaustive search. Serious thanks goes out to the user 6ril1
6ril1 said:
Have you typed the two commands in TWRP
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
and
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
?
Click to expand...
Click to collapse
Here is the thread:
[FIX] Installed TWRP and now you're stuck after OTA?
So here is what you do:
1) Boot into recovery (TWRP)
2) Go to Advanced and then Terminal Command
3) VERY CAREFULLY TYPE IN EXACTLY THIS:
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota" then RETURN
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc" then RETURN
Reboot and it should have fixed it up for you.

[Fix] Stuck at TWRPviaBump after installing 10L/any OTA?

all credits go to thecubed.
i feel sorry for the guy @ q&a section, that had the same experience . had to go through wipe.
will have to remember to update via lg pc suite now to retain apps etc. then just redo bump if ever. thanks autoprime,thecubed and the rest of the amazing devs.
http://forum.xda-developers.com/showthread.php?t=2451696
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
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
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
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!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse

http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
if that doesn't work, try autoprime's with added step for misc.
after that you can delete the files located at (using es file explorer) device>cache>fota
autoprime said:
LG G3 Stuck in Recovery Fix
Background
This thread is to help those who get stuck in custom recovery every time they try to boot into the rom.. usually after trying to take an OTA. Now that we're all rooted and unlocked this might be needed soon. Inspired by IOMonster's [FIX] Installed TWRP and now you're stuck after OTA? thread for the LG G2. Sometimes wiping FOTA was not enough and wiping the misc partition was also needed. But wiping the entire partition isn't the best idea. I've made a flashable zip to automate this process to properly fix being stuck in TWRP/CWM due to "stuck fota" or "stuck misc"​Fix
Flash LG_G3_Flash2FixStuckRecovery.zip to backup the current stuck fota/misc partitions and then fix them to allow proper booting.
Flashing LG_G3_Flash2FixStuckRecovery.zip creates a backup of your FOTA and Misc partitions in the /sdcard/FOTAnMisc_Backup/ folder.
1. Download the LG_G3_Flash2FixStuckRecovery.zip and place it on your phone. You can use TWRP's MTP feature to copy it from computer to phone, use OTG w/connected storage containing zip or use adb push to get the file onto your phone...
Code:
adb push LG_G3_Flash2FixStuckRecovery.zip /sdcard/
DOWNLOAD FROM CODEFIRE HERE
2. Flash LG_G3_Flash2FixStuckRecovery.zip in recovery or use adb commands below to fix boot issues..
Code:
adb shell
su
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 bs=256 count=1 conv=notrunc
reboot
If you are still booting into TWRP/CWM then you may have accidentally flashed the custom recovery img to the boot partition slot instead of the recovery partition slot. Reflash the rom in TWRP/CWM which should fix the boot.img... or download the required boot.img, place on root of internal storage ( /sdcard/ ) and flash the boot.img in TWRP/CWM...
Code:
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
reboot
Click to expand...
Click to collapse