Related
Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks
What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.
You didn't unzip them did you?
You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery
I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?
Hello. Sorry for my english. I want flash my phone via rootjoy to Arcatarc's MIUmIZERO and i only can see miui logo. next i want back to stock rom from needrom via sp flash tool, i followed instructions and i stop, when red status back not change for 20 minutes. and i can't charge my phone, can't conected to pc, can't turn on, looks like dead. How unbrick my phone? please help
problem solved
how did you solve it? please let me know as i am in the same boat
If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.
it is dead . the phone wont turn on . the pc wont recognise it anymore , it was fine ... untill i tried to flash stock through sp flash tool .
i was running antarcts emui,.... tried flashing using the method on umi digi forum : http://umidigi.com/forums/topic/how-to-restore-rom-version-3-03-2/ ... preloader was unticked, and when i tried firmware uopgrade option...nothing happened, and the phone was dead after that.
thepopos said:
If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.
Click to expand...
Click to collapse
I managed to make it boot.
The problem is I have twrp and some chinese recovery . And I cant go back to stock.
Fastboot cant flash recovery for some reason ... so I can go back to rootjoy.
use adb side load an try to flash a working rom, the original one from umi website or emui.
can you get in recovery mode? volume (+ or - try both) and power button for some seconds
if yes go adb side load, (check google) and transfer an original rom, then flash it again in the recovery
My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?
Pospa420 said:
My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?
Click to expand...
Click to collapse
If the system is unstable with popups etc or with damaged partitions you can get past that with TWRP.
Boot into recovery Wipe/Advanced Wipe. Then after that is completed, without rebooting, Format Data. That should sort out your partitions.
Then Install ROM from the recovery. It will need to be on the device. If your new ROM is not already there plug in a USB lead and transfer the zip file from your pc.
If you want to re-install your backup, do that instead.
If that doesn't work Backup in TWRP, even though there is no system. Then copy your Nandroid backup (must have been made via TWRP) and paste into the same folder as the Backup you just made, overwriting if asked.
I have had to do all this myself!
Good luck
Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.
It looks like memory become write-protected...
YrP said:
Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.
Click to expand...
Click to collapse
Hi
Did you Advance Wipe and Format Data?
I found that worked.
Alternatively, you could use Rootjoy to put just about any ROM on. CM 12.1 works ok.
Once you have a stable installation, install a custom recovery like TWRP 2.8.7 from Needrom. I used Mobileuncle, an app from the Playstore. However, I looked just now and it doesn't seem to be available.
I have tried Rashr, but couldn't get it to work.
Once you have it all stable you can flash the ROM you really want via TWRP.
Good luck
Advance Wipe and Format Data or flashing new stable ROM via TWRP did not work for me. The same result- unable to mount /system.
Rootjoy and Mobileuncle could be used if phone is working. My phone works in recovery mode only.
I tried to flash different recoveries but did not find the way to do this. As I wrote, Sp Flash Tool, Fastboot and Adb Sideload did not make any changes to my recovery. I think, flash new recovery will help if I found the way)
Or if I discover the method to test and\or repair /system partition from PC
But thank you for answer)
@YrP
Rootjoy works from your pc
Yes, Rootjoy- works)
But for establish connection phone must work too.
And not in recovery mode.
@YrP
I have already done all this with my daughter's Zero.
However, it's in bits at the moment while we wait for a part from China. So I can't go through the process with you live, step by step.
I am in the UK.
If you send the phone to me I will try and fix it for you.
PM me if you want to go ahead and I will let you have my address.
I am in Ukraine, it is too far from UK)
I will keep trying to find the way to fix it by myself.
But thank you very much for your attention and advices.
@YrP
I have got my daughter's phone back together and fixed (mostly).
Did you manage to get your Zero going?
Sent from my Nexus 4 using XDA-Developers mobile app
@goldbear
My UMI is still bricked(
It is flash memory problem, I think.
I am trying to find the tool to remap internal memory, to move SYSTEM part to other physical place. But did not find it yet.
What was your way?
Zero stutters, processes crash or the phone will not boot into System
Have you already tried a Factory Reset or re-installed the ROM?
What can you do?
You could try the following. However, if your phone blows up, orders a takeaway or elopes with your girl-friend, please don’t blame me.
1. Provided you already have TWRP custom recovery installed and your phone is powered down boot into Recovery: hold the volume down and power buttons until the Zero logo appears then let go
2. Select Wipe/Advanced and select Dalvik Cache, System, Cache and Data. Slide to execute
3. Select Format Data/ type yes and slide to execute
4. Reboot into Recovery without installing a new ROM
5. Select Backup, choose SD card rather than internal storage and give the file a memorable title like Blank Backup and date. Select Boot, Logo, Recovery and Uboot. Slide to execute
6. The next step requires you to have a Nandroid backup made via TWRP already made of a stable ROM. If it isn’t stable or you don’t have one I have attached a clean backup below. It’s derived from Cyanogen Mod 12.1. This is based on Lollipop 5.1, with Gapps and rooted. I have found this to work. As the title of the file suggests, it’s a factory reset, ie no personal data included. Download it to your pc unzip and save it.
7. Connect your phone to your pc via USB cable and open Windows Explorer
8. Find your stable backup or the one below and drill down until you see the folder with 15 files, starting with data.info and ending with uboot.emmc.win. Select all and Copy.
9. Open another window and find the TWRP folder on the SC card of your phone. Drill down to the same folder containing similar files as to step 8 above. Click in folder and Paste. When prompted select Copy and Replace, all and Ok
10. If your pc doesn’t show your phone and the SD card, in recovery select Mount and USB storage.
11. In Recovery select Restore and the Blank Backup (or whatever file name you gave it, now populated with usable ‘data’). Slide to execute
12. Give it time to load and boot up
13. You should be good to go!
If you don’t like CM 12.1 installing a new Launcher from the Playstore, like Cheetah will make it run smoother. Everything after that is down to you.
Of course, you could flash another ROM via TWRP
The backup below was made via TWRP 2.8.6. This is also attached below. You can install this via a previous version of TWRP as an image. Unzip it first.
Assuming this doesn’t wreck your phone and you like the guide please click Thanks below.
https://drive.google.com/file/d/0ByoLjFrSKxLwc01UUWZBZEQtbWs/view?usp=sharing
https://drive.google.com/file/d/0ByoLjFrSKxLweGhqNGJuVGV1a0U/view?usp=sharing
HI all,
I've come from flashing Samsung S4's for years but after trying to flash an update I got the boot screen and nothing happens.
Here's the situation.
I had originally installed PureNexus, rooted, unlocked the boot loader and probably turned off USB ADB settings (and I don't typically want an alert when plugging in the USB cable) as I usually transfer media and ROM's to the download folder for future flashing.
I saw that 6.01 was released and saw that the bootloader and radio were updated. So I tried to flash those before updating with PureNexus 6.01.
I did a nandroid backup before I did this, knowing something might go wrong.
I think my camera wasn't working so I tried a nandroid recovery to get it back.
Unfortunately I didn't read about the password encryption bug which TWRP had as I did the restore in my car and didn't have internet as it was free down time. When it was completed, I got the failed password issue. So I decided just to format everything. I used TWRP and formatted everything including the vendor partition. Of course, I forgot it would delete the Nandroid, too. I'm too used to having a spare external SD card to store all of the Nandroids on.
Anyway after that I can only get to TWRP.
I've tried installing the original 6.0 ROM, PureNexus ROM through TWRP with the appropriate ZIP files. It says it's completed, no errors but just the boot screen.
I've tried restoring through ADB with Windows 10 and through the USB. I don't get to an ADB selection on the bootloader, but can get to the ADB sideload throught TWRP. The problem is when I tried to restore through ADB nothing happens as it says "waiting" when I use fastboot flash-all. ADB devices does give me an ID when I do ADB so it is connecting. However, I believe ADB is waiting for the USB-ADB to be turned on which I can't do because I can't get to the OS system partition.
I've tried using several of the Skip Soft Toolkit and again, it waits and says closed.
I'm assuming that USB-ADB is closed and not turned on. I don't know why TWRP can't overwrite the system partitions if I try to flash, unless it's still encrypted but shouldn't be as I formatted everything, except for the boot loader and that is unlocked as I get the screen that I should lock the bootloader because the OS can't tell if it is corrupted.
Any ideas? I can only think if someone sends me a Nandroid of a configuration that may flash it back to a level I can get into Android and then get back to USB ADB and do a clean install with fastboot flash-all.
Please help!! Thanks in advance for your suggestions. I hope I gave you enough information to help me out.
Update. I apparently found a way. Luckily TWRP has a Flash image feature as well as flashing the vendor image. Flashed PureNexus 6.01 and PureNexus Gapps and thank goodness that worked! No idea why ADB was not flashing except for the configuration for USB ADB was turned off on the ROM originally.
I was in the middle of a restore in twrp and the phone shut off in the middle of the restore (while restoring recovery), and had such, my android system will no longer boot, nor can I get into recovery. It simply goes into fastboot mode and that's all. Is there a way to flash twrp (Archlinux?) using fastboot/adb?
Thank you in advance!
533y4 said:
I was in the middle of a restore in twrp and the phone shut off in the middle of the restore (while restoring recovery), and had such, my android system will no longer boot, nor can I get into recovery. It simply goes into fastboot mode and that's all. Is there a way to flash twrp (Archlinux?) using fastboot/adb?
Thank you in advance!
Click to expand...
Click to collapse
Depends on what variant you have. If its a dirtysanta one while in fastboot do
Code:
fastboot flash recovery (twrpimgnamehere).img
and it will install the twrp image you have downloaded. If you are on TMO you need to revert to stock using a KDZ and then re root.
Fastboot commands aren't working on the H918? My model... -_-
What's the difference between recowvery and dirtysanta?
OK. So let me ask this then. If fastboot commands don't seem to do much on the H918, then how does one go about backing up the internal storage before being formatted? Is there like a dd command to copy everything over? Or will the phone still attach storage to the PC when attached, even in fastboot?
In other words, how can I backup my internal storage before reseting to stock?
533y4 said:
Fastboot commands aren't working on the H918? My model... -_-
What's the difference between recowvery and dirtysanta?
Click to expand...
Click to collapse
The difference between recowvery and dirtysanta is multiple things. One thing is the fact that recovery goes after the recovery directly and dirtysanta replaces the bootloader itself. IF you use dirtysanta on a H918 you WILL BRICK. non recoverable. Dirtysantas boatloader is a debug bootloader that has full access to the phone. H918 bootloader only has limited commands available.
The other difference is how the methods goes about actually doing everything. Jcadduonos recowvery attacks recovery uses scripts to start a factory recovery installer/updater but makes it install a temp root instead of a recovery then the device has access to fully install a twrp image. Dirtysanta skips that and attacks the bootloader directly by replacing a higher level function of the phone temporarily that has access to the phones bootloader(for some unknown reason) and replaces it with the debug one. Once the debug one is in the device is able to be rooted like any other device with an unlocked bootloader since it has full access.
533y4 said:
OK. So let me ask this then. If fastboot commands don't seem to do much on the H918, then how does one go about backing up the internal storage before being formatted? Is there like a dd command to copy everything over? Or will the phone still attach storage to the PC when attached, even in fastboot?
In other words, how can I backup my internal storage before reseting to stock?
Click to expand...
Click to collapse
You don't. you can copy everything manually but If you backup the data partition(which has your internal storage inside) it will not be usable on the device after you root. If you do manage to back it up then restore it afterward since the device itself is normally encrypted and is now decrypted the settings and stuff will cause crashes and force closes.
me2151 said:
The difference between recowvery and dirtysanta is multiple things. One thing is the fact that recovery goes after the recovery directly and dirtysanta replaces the bootloader itself. IF you use dirtysanta on a H918 you WILL BRICK. non recoverable. Dirtysantas boatloader is a debug bootloader that has full access to the phone. H918 bootloader only has limited commands available.
The other difference is how the methods goes about actually doing everything. Jcadduonos recowvery attacks recovery uses scripts to start a factory recovery installer/updater but makes it install a temp root instead of a recovery then the device has access to fully install a twrp image. Dirtysanta skips that and attacks the bootloader directly by replacing a higher level function of the phone temporarily that has access to the phones bootloader(for some unknown reason) and replaces it with the debug one. Once the debug one is in the device is able to be rooted like any other device with an unlocked bootloader since it has full access.
You don't. you can copy everything manually but If you backup the data partition(which has your internal storage inside) it will not be usable on the device after you root. If you do manage to back it up then restore it afterward since the device itself is normally encrypted and is now decrypted the settings and stuff will cause crashes and force closes.
Click to expand...
Click to collapse
Very interesting how different the two are and how they work. Very interesting indeed.
As for the data partition, mine is already decrypted as is (was rooted already and tried to install a cm rom to test; ended up glitches during restore). But I have no intentions on restoring an backups. I simply want my photos, saves, books, etc off the actual internal SD storage (not my external SD card, obviously).
My question here I guess is, will the internal storage mount while in fastboot mode the same as if the phone was on normal (adds a new drive (win)/mtp link (unix))?
I just want to copy and paste all the files off the internal storage on to my unix desktop. Then format the whole phone and start fresh again.
*bump*
I have tried to access the SD card while in fastboot mode. Absolutely nothing I do can make the PC see the internal storage on my V20. I have some files for my job on my internal SD card (NOT my external SD card, but the actual built in storage), that I absolutely, positively cannot afford to loose. These files are for my job. If I loose these files, I will loose my job.
Please, can someone tell me how to access the SD card in fastboot mode? It's really really important.
If anyone, at all, has any clue or any ideas on how to access the internal storage or how to restore my v20 without a full reset, then please please please help. Hell, I'll even be willing to donate some money to whoever can figure this out for me. Seriously, it's really that important that I get my files off the internal storage.
Thanks to anyone who can help.
P.s. I have access to Windows and Linux computers.
533y4 said:
*bump*
I have tried to access the SD card while in fastboot mode. Absolutely nothing I do can make the PC see the internal storage on my V20. I have some files for my job on my internal SD card (NOT my external SD card, but the actual built in storage), that I absolutely, positively cannot afford to loose. These files are for my job. If I loose these files, I will loose my job.
Please, can someone tell me how to access the SD card in fastboot mode? It's really really important.
If anyone, at all, has any clue or any ideas on how to access the internal storage or how to restore my v20 without a full reset, then please please please help. Hell, I'll even be willing to donate some money to whoever can figure this out for me. Seriously, it's really that important that I get my files off the internal storage.
Thanks to anyone who can help.
P.s. I have access to Windows and Linux computers.
Click to expand...
Click to collapse
can you let it boot up and will it just hang on the lg logo or is it rebooting into fastboot?
really my only advice would be try letting it hang on lg logo and see if adb is present, furthermore you can get a adb always moded boot.img and push that to the phone using fastboot then see if adb is a option.
If so you can do the adb commands to pull the userdata portion off the device the same way the system dumps are done i believe, but the sad fact is its probably all currupted anyway from your restore you were trying.
The other option is push recovery again to device, and then try a dirty flash of the stock rom, in hopes it can get the system partition back up and running,
furthermore, worst case wipe all and flash the rom, once its back up and running, download diskdigger from playstore and see if it can recovery the deleted stuff, or try the phonedoctor program for windows that runs against your internals and trys to recocvery stuff..
The biggest question is why were you flashing your device without saving stuff thats "soooo important and can cost you your job" ? seems like a oversight on your part really, and a lesson learned. Backup work stuff always, and dont play with roms during work days lol, not to be mean but really, why risk your job and lively hood over some unsaved stuff?
I did actually have a back up on my S6, which I dropped and broke a mere hour before this. So it's not at all an oversight. There were backups in place. And it won't boot at all or I'd had been able to get adb Atleast. ADB won't see the v20 and I tried to flash recovery using fastboot flash recovery recovery.img command. It says unknown.
How can one going about flashing such a boot.img in the H918? Where can one find such things? I assume you mean a kernel of some sort, right?
I truly appreciate the reply. Has I said, it's not like I didn't have backups. I did. It really is an issue of bad luck. : (
i tried this it worked https://forum.xda-developers.com/v20/help/lg-v20-access-to-fastboot-t3557328
Have you tried power on and volume down to go through the factory reset screens.
A bunch of us had this problem and it was because an update downloaded on it's own and the bootloader snoops it out and forces recovery to boot.
Just do the volume down + power button - as soon as you see the lg logo release power only then immediately re-press power and continue holding power and volume down until the factory reset screen pops up. Select yes and yes, (don't worry - if you have twrp recovery it can't reset). It will boot you into TWRP and I'm pretty sure it will delete the update files in fota folder.
In TWRP select reboot - system and it should boot normally like nothing happened.
Due to dirty flashing and flashing a rom with the wrong kernel, my phone goes into a logo boot loop. I had cleared my internal storage after flashing since i thot flashing had succeeded. Now, I can only access twrp. I formatted the internal storage, i cant access adb. My pc doesnt recognize the phone at all. My kernal is NoKernal, i cleared everything including system, and twrp doesn't recognize my usb either. Please help me! Thanks a lot in advance!
-Danny
Try to check whether fastboot is working, check with a different usb cable. Once you can access adb, you can sideload any rom you want.
No, fastboot isn't working either. I switched the phone onto fastboot mode, but nothing showed up when i used 'fastboot devices'.