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

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?

Related

[Q] I might have bricked my TF101G finally - Please help!

OK. This is an older TF101G, which was running ICS, but needed to go back to stock.
My first mistake was to follow a thread which installed the stock WW HC image, but with an US stock recovery. There, I could not get updates.
I tried to fix this by rooting this monster with nachoroot. I rooted successfully. My second mistake was to use RomManager to install CWM. Though it says it has the right image, this does not work. You can boot into it, but it cannot mount the sdcard, nor can it install any zip. The machine still boots into ICS.
To recover from this, I did my third mistake. I followed an advice to insert a blob from this web page with dd to mmcblk0p4. The blob is the boot blob from CM9.1. However, now this boot blob cannot start the ICS system. It hangs at the boot logo. I can still boot into CWM, however.
To recover from this, I tried booting as far as it goes, and starting adb shell. The screen is showing a boot logo of the Transformer at that time. But the su command now longer works and hangs the shell. This beats me. Otherwise I would have tried the blob from the ICS version I installed.
Is there any way to get out of this mess?
Update:
I tried re-rooting with nachoroot. But trying to push nachoroot.bin to /data/local fails because of "permission denied". Pushing to /mnt/sdcard works. But I am not permitted to chmod to 777 there.
I solved this for the moment
Sorry, I solved it myself. Glad to see that I am still faster than the people here
I followed an advice in a posting to install the universal drivers on Windows. Simply download the drivers and updated the device drives in the hardware manager. Then I boot into CWM. There adb shell magically goes to a root shell. Probably because I rooted the phone before. Then I used dd to push the blob of the original android firmware to mmcblk0p4. The device now reboots into HC!
It remains to find out how to get a working CWM recovery to this device, so I can put an ICS ROM on it.
mga010 said:
Sorry, I solved it myself. Glad to see that I am still faster than the people here
I followed an advice in a posting to install the universal drivers on Windows. Simply download the drivers and updated the device drives in the hardware manager. Then I boot into CWM. There adb shell magically goes to a root shell. Probably because I rooted the phone before. Then I used dd to push the blob of the original android firmware to mmcblk0p4. The device now reboots into ICS!
It remains to find out how to get a working CWM recovery to this device.
Click to expand...
Click to collapse
Use PERI.
It will push a working CWM via ADB.
Works with the TF101g
Be advised the version it uses only seers the internal storage to flash ROMs.
frederuco said:
Use PERI.
It will push a working CWM via ADB.
Works with the TF101g
Be advised the version it uses only seers the internal storage to flash ROMs.
Click to expand...
Click to collapse
Yeah, thanks, I used this tool to flash a working recovery when I was on ICS.
Now I am on rooted HC and a useless CWM. I could use the recoveryblob in the PERI tool and do the same dd trick I did with the boot blob. But I want to make sure this recovery will cooperate with my HC system. At least there should be a way to revert.
I don't see why it wouldn't work with HC.
Experience?
frederuco said:
I don't see why it wouldn't work with HC.
Click to expand...
Click to collapse
There are users which report on the PERI thread about problems with HC.
No Ideas
So nobody knows how to update my Transformer? The remaining problem is that I have HC (stock) running with a disfunctional CWM recovery.
Maybe I will live with it for a while and open a new thread later.
Solved, I hope!
Ok. I solved this too. I found TWPR 2.2 on the net and took the recoveryblob out of it. Then copied this to /dev/block/mmcblk0p4 with
dd if=recoveryblob of=/dev/block/mmcblk0p4
Reboot, and got my new recovery. I hope I can install and decent ROM now.

[Q] Botched TWRP upgrade, now lost root access

While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Tunameltsalad said:
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Click to expand...
Click to collapse
Can you use fastboot to reflash the stock ROM?

[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....

[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.

[Completed] LG G2, Stuck in TWRP bootloop! - Please help.

Hi,
So it alll started when I installed CM13 Nightly on my G2, (at this time, it wasnt rooted and no custom recovery) i then decided to update to the next version of the nightly which caused everything to crash.
So I used the LG Flash Tool, and went back to stock which worked absolutely fine. Then I decided to use ioroot and re-root my device which always went fine. Next, I installed the twrp manager, which installed an old version for my G2. I had G apps 5.1 and resurrection remix rom, in my downloads folder. I then went to recovery, wiped my device, (apart from internal storage) and then tried to install the rom. I forgot to download the bootstack and the new version of twrp. I then accidentally wiped internal storage, which has stopped adb sideload from working. I have tried re using the LG Flash tool to go back to stock, but it always skips system, data, cache etc. and when the phone boots, I am back in TWRP with no OS. Please Help. Thanks..
My Soloution
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.
after that, you can use the lg flash tool, and go back to stock
Hello,
Glad, you yourself found out the solution.
Thread closed!
-Vatsal

Categories

Resources