[Q] Restore on TWRP only leads to boot logo - G2 Q&A, Help & Troubleshooting

I flashed the Slim Bean Android 4.3 rom on my D801 to discover the rom was unrooted. When I went to restore the rooted stock, (rooted with IOroot), TWRP restored the rom but when I rebooted the phone would only show the LG logo (doesn't look like boot loop). My PC recognizes that the phone is plugged in. If I can't access the internal storage, how to I flash a working rom onto the phone? What have I done wrong?

Agayvoronski said:
I flashed the Slim Bean Android 4.3 rom on my D801 to discover the rom was unrooted. When I went to restore the rooted stock, (rooted with IOroot), TWRP restored the rom but when I rebooted the phone would only show the LG logo (doesn't look like boot loop). My PC recognizes that the phone is plugged in. If I can't access the internal storage, how to I flash a working rom onto the phone? What have I done wrong?
Click to expand...
Click to collapse
Wipe data/factory reset and reflash Slim Bean. Then download the root.zip and flash it. Now it's rooted.
SuperSU 1.69 https://www.google.com/url?sa=t&rct...=Tagov7Bq3zQLmXCTtqzDOQ&bvm=bv.56643336,d.b2I

Reply
Mandelbrot.Benoit said:
Wipe data/factory reset and reflash Slim Bean. Then download the root.zip and flash it. Now it's rooted
Click to expand...
Click to collapse
Thank you, but I have already tried to do that; the same thing happens. Is there any way that I can restore the factory rom without the use of TWRP? Because I think that the backups are the problem.

Sounds like you should just restore to stock via the LG flashtool.

Agayvoronski said:
I flashed the Slim Bean Android 4.3 rom on my D801 to discover the rom was unrooted. When I went to restore the rooted stock, (rooted with IOroot), TWRP restored the rom but when I rebooted the phone would only show the LG logo (doesn't look like boot loop). My PC recognizes that the phone is plugged in. If I can't access the internal storage, how to I flash a working rom onto the phone? What have I done wrong?
Click to expand...
Click to collapse
I had this happen too. I loaded CleanROM and it booted up without any issue.
In TWRP I selected all the advanced wipe options except for Internal Storage. Then I ran the install.
If you can't get to the OS, then you'll need to adb sideload the ROM. http://forum.xda-developers.com/showthread.php?t=2317986

Adam1203 said:
I had this happen too. I loaded CleanROM and it booted up without any issue.
In TWRP I selected all the advanced wipe options except for Internal Storage. Then I ran the install.
If you can't get to the OS, then you'll need to adb sideload the ROM.
Click to expand...
Click to collapse
Thank you, but I also tried to adb sideload. TWRP said "starting adb sideload" for about twenty minutes, and when I tried to load a rom it said the no devices were found.

It worked
simon_lefisch said:
Sounds like you should just restore to stock via the LG flashtool.
Click to expand...
Click to collapse
I looked it up and my phone is like new again! Thank you!

Agayvoronski said:
I looked it up and my phone is like new again! Thank you!
Click to expand...
Click to collapse
Glad you got it working! Nothing is as scary as bricking a brand new phone!

Related

[Q] Just got the 4.4 KRT16 OTA on my Nexus 4 and its been stuck on the boot screen

Hi,
My nexus 4 was perfectly running the 4.4 kitkat when all of a sudden I received an OTA for build KRT16S. After the installation my phone didn't boot up and it's been stuck on google page ever since.
Details:
Rooted
twrp recovery 2.6.3.3
ART runtime
Encrypted.
My phone restarted straight into twrp, I typed the encryp. password and it started to install the new update automatically and it said successful.
I restart and it gets stuck on google page.
Please help guys
Many Thanks
You probably have too many customizations and especially running custom recovery. OTA is meant for stock Android.
Do a factory reset in TWRP and see if it boot. Otherwise search for a stock KRT16S rom in the development section, and use the TWRP sideload feature to install it.
eksasol said:
You probably have too many customizations and especially running custom recovery. OTA is meant for stock Android.
Do a factory reset in TWRP and see if it boot. Otherwise search for a stock KRT16S rom in the development section, and use the TWRP sideload feature to install it.
Click to expand...
Click to collapse
Thanks eksasol, I had the stock Android installed on this nexus and I got the ROM straight from google.
I will try doing a factory reset or installing the ROM from sideload. but would any of these erase my data?
Pulse.1995 said:
Thanks eksasol, I had the stock Android installed on this nexus and I got the ROM straight from google.
I will try doing a factory reset or installing the ROM from sideload. but would any of these erase my data?
Click to expand...
Click to collapse
Doing factory reset in TWRP won't wipe your internal storage, but it will clear your installed apps and its data ofcourse. Just don't select to wipe internal storage in the advance wipe. Installing rom zips will not wipe your data either.
If you want to backup everything from your internal storage, just connect the phone while in TWRP, then type: adb pull /data/media/ C:\backup\
I wiped and installed a fresh copy at the end and its working now.
Thanks eksasol for your help.
How do i mark this thread as resolved?
Pulse.1995 said:
I wiped and installed a fresh copy at the end and its working now.
Thanks eksasol for your help.
How do i mark this thread as resolved?
Click to expand...
Click to collapse
Just edit your thread title and write SOLVED before the title.

[Q] Yellow Brick?

Just recently rooted my s4, was working fine or so I thought, went to flash NamelessROM, I don't think the rom is the issue, I had my s2 rooted and flashed on a weekly basis so I know about wiping, data cache, and dalvik, I flashed Rom then Gapps, and it was stuck on boot up, of course I made a nandroid and restored, but now I'm stuck on the yellow sprint screen, did my research and found it it's called a Yellow Brick, or referred to as. Found out a possible fix was downloading the kernel so I've chosen the Rooted NoData kernel to download and flash via odin. Is this what I should do or is there a better fix out there?
Sounds like you wiped everything. Can you boot into recovery?
Beezer80 said:
Sounds like you wiped everything. Can you boot into recovery?
Click to expand...
Click to collapse
Yes I can, and I tried to restore back from my nandroid which is how I'm stuck on yellow sprint screen now versus stuck on the boot for NamelessROM.
Do a factory reset in recovery and see if it boots.
That will wipe your accounts and what not but you can't boot anyway.
If it won't boot then you'll need to flash a ROM to get running. Do you still have the ROM you wish to flash on your SD card or internal storage?
Beezer80 said:
Do a factory reset in recovery and see if it boots.
That will wipe your accounts and what not but you can't boot anyway.
If it won't boot then you'll need to flash a ROM to get running. Do you still have the ROM you wish to flash on your SD card or internal storage?
Click to expand...
Click to collapse
Just got me stuck on NamelessROM boot up so I'm restoring off nandroid again. I think that flashing the kernel will fix it.
I'd get the ROM booting then play with the kernel. That's just me though.
Beezer80 said:
I'd get the ROM booting then play with the kernel. That's just me though.
Click to expand...
Click to collapse
trying that right now
JosephBallin said:
trying that right now
Click to expand...
Click to collapse
I'm trying to push a kernel through odin, I could possible try to find a way to put a kernel on my extsd and try and flash it through twrp? Would I just have to wipe cache and dalvik and flash? because when I try through odin it fails.
EDIT: I found a fix it involves unrooting most likely, but if I do I'll be back at VPUAMDC (Android 4.2.2) so could I still root with SafeRoot? Or what would be the way to root from that version?
Which firmware version did you root from? If it was MJA or MK2 you have to use one of those, you can't downgrade to MDC easily.

[Q] Soft brick after trying to flash resurrection

I have a G2 from Verizon (VS980).
It was running KitKat 4.4.2 stock rooted.
I run a Nandroid backup using TWRP.
I flashed the Resurrection Remix ROM.
On restart I entered a boot loop.
Turned off, rebooted into TWRP recovery, did a complete swipe (system, cache, dalvik and data).
Tried restoring from Nandroid backup and could not find any backup files (perhaps I don't know where to look but all folders appear empty).
Tried rebooting into download mode and got stuck at installing some drivers (could take 10 minutes) with nothing happening.
Screen says Rooted and I am guessing that could be the issue. I don't know how to proceed.
Can someone help please?
Download another 4.4.2 based ROM. I'm assuming you are attempting to flash a lollipop 5.0.2 ROM. Is that the case?
untamed1 said:
I have a G2 from Verizon (VS980).
It was running KitKat 4.4.2 stock rooted.
I run a Nandroid backup using TWRP.
I flashed the Resurrection Remix ROM.
On restart I entered a boot loop.
Turned off, rebooted into TWRP recovery, did a complete swipe (system, cache, dalvik and data).
Tried restoring from Nandroid backup and could not find any backup files (perhaps I don't know where to look but all folders appear empty).
Tried rebooting into download mode and got stuck at installing some drivers (could take 10 minutes) with nothing happening.
Screen says Rooted and I am guessing that could be the issue. I don't know how to proceed.
Can someone help please?
Click to expand...
Click to collapse
I ran in to that problem when trying to go from a G3 rom to Lollipop. My solution was this:
1. Boot in to TWRP
2. Plug phone in to computer (pc should recognize it; sometimes it wouldn't and I had to mount then unmount /system partition from TWRP
3. Drag and drop a Kit Kat based rom (and GAAPS if need be) from your computer on to the root of your device
4. Flash from there
Let me know if you have any issues with that. I did manage to lose everything saved on my device which led me to a valuable lesson learned, that being: once you back up the device in TWRP, be sure to transfer that backup to your PC in case you mistakenly wipe the device clean later.
RETRObruzzin said:
I ran in to that problem when trying to go from a G3 rom to Lollipop. My solution was this:
1. Boot in to TWRP
2. Plug phone in to computer (pc should recognize it; sometimes it wouldn't and I had to mount then unmount /system partition from TWRP
3. Drag and drop a Kit Kat based rom (and GAAPS if need be) from your computer on to the root of your device
4. Flash from there
Let me know if you have any issues with that. I did manage to lose everything saved on my device which led me to a valuable lesson learned, that being: once you back up the device in TWRP, be sure to transfer that backup to your PC in case you mistakenly wipe the device clean later.
Click to expand...
Click to collapse
Retobuzzing, thank you for the quick response. Thanks also for your last recommendation, gotta do that too next time.
I have actually found my solution reading in a post that I should try entering download mode by pressing both volume keys together while you connect the micro usb connector. That worked even though the screen gives you no feedback except for the led turning red (kind of scary at first :fingers-crossed.
After doing that I was able to follow the directions in the article titled: "How to unbrick LG G2 with stock firmware" at the Androidcure.com site.
The phone was restored to the original stock conditions and later I was able to update it to software version 26A.
Note to Forum Moderators: You can close this tread if desired. Thanks.
Yes I am!
Snuzzo said:
Download another 4.4.2 based ROM. I'm assuming you are attempting to flash a lollipop 5.0.2 ROM. Is that the case?
Click to expand...
Click to collapse
Your assumption is right on the money.:good:
Do you have a suggestion on a better lollipop ROM for the G2?
Any idea on could have caused the boot loop after flashing Resurrection remix?
untamed1 said:
Your assumption is right on the money.:good:
Do you have a suggestion on a better lollipop ROM for the G2?
Any idea on could have caused the boot loop after flashing Resurrection remix?
Click to expand...
Click to collapse
Only 1 assumption. Didnt downdate back to 12b bootloader/modem.

Phone only boots into TWRP

I decided today to try and root my phone and followed the steps on this tutorial: http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
I had unlocked my phone and installed the latest version of TWRP. Now I can only boot into TWRP and bootloader. My phone is not being picked up by my PC. I tried a factory reset and format of data on TWRP but my phone still only boots into TWRP.
Is my phone permanently bricked?
Any help will be greatly appreciated
I actually have just made some progress now. I've managed to get the phone connected to the computer by going into ADB sideload and installing the ADB drivers again on my computer.
Typing ADB devices in CMD now shows my device as connected.
Any advice on what I should do now?
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
theminikiller said:
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
Click to expand...
Click to collapse
Booting the phone normally loads it into TWRP. Booting the phone with the volume key pressed down loads the bootloader. I think I may have just wiped the OS present on the Phone.
I want my phone to be rooted running CyanogenMOD (phone is currently unrooted). Should I first install a stock rom then root by installing SuperSU and CyanogenMOD or can I just skip installing a stock rom and install SuperSU and CyanogenMOD?
Thanks for the help
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
theminikiller said:
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
Click to expand...
Click to collapse
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
umair_ said:
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
Click to expand...
Click to collapse
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
theminikiller said:
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
Click to expand...
Click to collapse
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
umair_ said:
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
Click to expand...
Click to collapse
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
theminikiller said:
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
I've managed to get it all working by first flashing the stock ROM and starting all over again.
Thanks for your help.
Is there a workaround to this other than flashing factory images...?
hwweiler said:
Is there a workaround to this other than flashing factory images...?
Click to expand...
Click to collapse
@hwweiler, No friend there is no other way.Please before do this as is one direction way take the pain to look on my post #180 on zaclmon's thread http://forum.xda-developers.com/nexus-4/orig-development/wip-aosp-7-0-nougat-t3448444/page18 and keep in mind that is impossible to return back on any nandroid backup u kept e.g to 5.1.1 or M furthermore its also impossible to flash any rom zip if u use this N (WIP) rom,the only way to have a workable phone again is to flash the stock rom from scratch.Exceperienced with and never again untill we have the appropriate solution..The twrp used and i still use on M is TWRP 3.0.2.0.The possibility to return on LP ffrom M and reverse still exists but not when u flash this rom.
Regards,Christos

TWRP Format Data Problem HELP!

Hi, i Accidentally used the "Format Data" instead Advanced Wipe on My D802 :/... There's a way to "Roll back" that.?
Still can go in TWRP Recovery (3.0.0), also i can install a Custom ROM but the Internal Storage Always says "-1Mb"... lol?
Also installed a ROM (CloudyG2) But when is booting in goes into the Fastboot Screen..! ADB is working Fine in Fastboot.!
Any help.?
I would try to flash the stock firmware (hopefully you are able to) before I do everything else now, then root+twrp and start over with flashing custom roms.
bigmike87 said:
I would try to flash the stock firmware (hopefully you are able to) before I do everything else now, then root+twrp and start over with flashing custom roms.
Click to expand...
Click to collapse
i Fixed it :victory: ..! Kinda doing that you said.! But i Installed The same Custom ROM Via ADB Sideload and it Worked, dont know how.!
Thanks!
Lucky you bricked my device half a year ago like that, congrats.

Categories

Resources