I was trying to flash the rotary dialer zip from customer recovery and its not there anymore. I press home+power and I go to what appears to be the stock recovery screen. The only options I see are to perform a factory reset. Its a white screen with the little green android at the bottom.
The only change I have done recently is install Freshs Kitchen. The only thing I did was attempt to remove one of the Sprint apps (NFL Football) from my phone but that removal failed.
Does Fresh's Kitchen do anything to the custom recovery image?
Would pushing the recovery image again via adb command have any negative effects on my phone?
Edit* Its working now. Is there anyway to delete this thread to prevent clutter?
Quis89 said:
I was trying to flash the rotary dialer zip from customer recovery and its not there anymore. I press home+power and I go to what appears to be the stock recovery screen. The only options I see are to perform a factory reset. Its a white screen with the little green android at the bottom.
The only change I have done recently is install Freshs Kitchen. The only thing I did was attempt to remove one of the Sprint apps (NFL Football) from my phone but that removal failed.
Does Fresh's Kitchen do anything to the custom recovery image?
Would pushing the recovery image again via adb command have any negative effects on my phone?
Click to expand...
Click to collapse
Not sure what happened, but you can simply flash recovery image 1.6.2 again. Instructions here >> http://forum.xda-developers.com/showthread.php?t=583291
Hmmm...Idk what happened. I pulled my battery (for the 3rd time) tried it again and it worked. I guess I was pressing the buttons incorrectly......................3 times, lol.
Oh well. Its working now.
Thanks.
that happened to me once too.
i just reflashed it though
i reccomend flashrec, install it right from your phone!
Quis89 said:
Hmmm...Idk what happened. I pulled my battery (for the 3rd time) tried it again and it worked. I guess I was pressing the buttons incorrectly......................3 times, lol.
Oh well. Its working now.
Thanks.
Click to expand...
Click to collapse
If you have issues again you can send the phone to custom recovery (as long as it is still there) by typing:
Code:
adb reboot recovery
As the title indicates, I soft-bricked my G2 via bad rom flash (wrong version of CM)
This post will be my outline of how I got my phone out of this mess and operating perfectly.
I foolishly made the mistake of not making a backup so as a result, I have scoured numerous forums and pushed my google-fu to it's limits. Biggest tip I can advise (as if it needs to be said again) is to backup before you do any flashing. If things go south though, here's what happened to me and how I fixed it all.
I rooted and installed TWRP 2.6.3.2 then did full wipe and flashed the wrong G2 version of CM from the internal storage. Rebooted and got the "udc_start()" message of sadness.
Hard reset the device by doing the power button/volume down thing which involves the following:
fully black screen except for tiny little message saying something like UDC_Start() and some other jibberish. Basically it doesn't do anything.
Hold down the power button for about 12~15 seconds. After 10 seconds the phone display will shut off and the LG logo will pop back up. KEEP HOLDING THE POWER BUTTON DOWN.
The screen will shut off again.
Now holding the volume down button, press and hold it and the power button together until the LG logo comes up again.
Release the buttons and then quickly hold down the power button again until you get a device reset screen.
hit the power button to confirm and it will load up TWRP.
I was relieved to be back in recovery but it dawned on me that the wrong version of CM is the only rom I had on my phone. Performing a factory reset does not fix the issue.. just kicks me back to that UDC error.
Next level googling engaged. I had the CORRECT ROM and a couple others for my device downloaded but I had to somehow get them onto the internal storage so that I could flash them.
HOWEVER, I also discovered in the hellfire rom thread, there are issues with TWRP version 2.6.3.2 flashing roms and that flashing the PHILZ recovery from within TWRP (just like flashing a new rom) to replace TWRP would work. I didn't want to take any chances so I got that zip file from here.
http://forum.xda-developers.com/showthread.php?t=2201860
To get these zip files onto the device, ADB push command was the trick.
I grabbed this (if the link is broken, google search for ADB fast boot zip)
http://d-h.st/iqA
And extracted the files to a folder on the desktop.
Next, after reading through some ADB push threads, I copied the zip files into the ADB folder on the desktop and then in windows explorer, hover the mouse over that ADB folder and then shift + right click the folder and in the pop up menu, select "Open command prompt window here"
it's efficiency - not laziness
then with the phone connected via usb cable to the computer, in that prompt type this
adb push ROMNAME.zip /sdcard/
After a short wait, it showed a couple hundred megs worth of a file was transferred. I repeated the command again with the PHILZ recovery zip name and again, it showed completing the transfer.
Time to get to work.
From TWRP, I went to flash a zip, pointed to the PHILZ zip file and successfully flashed that, went back to the main menu and then told it to reboot back into recovery.
I was greeted with the snazzy PHILZ recovery interface.
I then told it to do a wipe for a new ROM install and then after that completed, went to flash a zip, pointed it to the correct version of CM this time and flash was successful.
Crossed my fingers and rebooted the device and SUCCESS! Up and running perfectly.
hopefully this helps those who find themselves in the unfortunate soft brick scenario or something similar that I was in.
Great stuff. I'm sure this saved a couple of lives. Comment bump for ya.
Sent from my LG-D802 using Tapatalk
Just got a new phone from warranty to replace old one with digitizer problems.
So basically I rooted and then I installed TWRP via AutoRec, then was in TWRP and wanted to upgrade TWRP to the blastorgator thermal helping version and put recovery.img on /sdcard/ and went to the end of step 3 on a guide for flashing twrp on phonearena (stupid I know), I can probably PM guide if requested but can't post in this thread due to postcount.
After going into fastboot, the phone would go to a black screen while still backlit, and the notification LED's would alternate between green and blue. Couldn't go to regular OS at this point, but while in adb shell I could run adb reboot recovery and go back to TWRP. I figured maybe I did something wrong somehow with system and wiped all the stuff available in TWRP (dalvik, system, sdcard, cache) and then installed Cloudy G2 3.3 from TWRP's install menu, the little gui to install came up and it ran the commands and then prompted to reboot iirc, and then it went to a black screen, no notification LEDs on.
If I hold down power and lower volume, LG splash screen comes on and goes back to the normal black screen with backlight.
If I connect the phone to usb, windows gets spammed with a ton of "You must partition this drive to do anything with it G:/" all the way through the alphabet. adb devices is blank, commands don't run.
At this point I rebooted back into TWRP and formatted the phone, and then pushed Cloudy.zip back onto it and tried to install again. Same **** when it reboots after installation (with the black backlit screen and the disk formatting in windows).
So thats a no-dice. Can still reliably get into TWRP however.
Is there anything I can do?
I know about the no recovery mode fix, but I don't have the binned version of my rom. I have an identical phone with an identical rom (ie the digitizer problem one), could I in theory pull the binned version off that phone and use it to fix this one? Or something else I can do?
Yesterday I accidentally installed the OTA update. I got stuck in TWRP and flashed a new ROM. Phone booted up fine, but now I have no cellular signal, nothing that uses video or sound works. Camera doesn't work, flashlight doesn't work.
I tried several different ROMS and nothing changes. Even the system sounds, ringtones and so on do not work. Anyone have any idea what I can do? Thanks
boot into fastboot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase misc
fastboot erase fota
fastboot erase boot
then pull battery and reboot into twrp by holding power and vol down, when lg logo appears then click the power button and re-hold it down to get into twrp.
once in twrp, check and see if system is mounted, if it wont let you mount, go to wipe and wipe everything (not ur sd of course)
System, cache, dalvik, data, internal, everything... the fastboot should have already done this but let twrp do it too..
once done, use the format option and format data also, some of these may error thats okay, just keep going..
once done reflash the full rom that matches your device.. let it flash and reboot and do its thing. this should fix the issues...
once it boots you may need to let it activate, or re-activate.
Only other suggestion would be if you have a twrp backup and you backed up your efs, its time to restore it also and see if the NV files have been damaged.
I've tried installing several different roms available on xda but that didn't resolve the issue. My phone remains in a boot loop state. Is there a way I can return to stock without compromising my ability to use the current root exploits?
Might help to know what you've got currently, are you able to get to recovery at all, etc?
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
My Solution
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
lanyueng said:
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
Click to expand...
Click to collapse
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
jluca98 said:
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
Click to expand...
Click to collapse
This isn't working for me. Keeps rebooting to TWRP.
I get FAILED (remote: unknown command) with every adb command
Any ideas?
Drkphnxs2k said:
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
Click to expand...
Click to collapse
Don't use Easy Recowvery. Do it manually from the original thread. You can also google it for some sites that have cleaned the instructions up for easier reading.
I just did a H918 10d like this.
Hi, I don't have enough posts to ask this in the actual DirtySanta thread.
I meticulously followed the steps in the DirtySanta thread making sure I had all the correct software, all the pre-requisites, all files in my ADB folder (except SuperSU zip, which is on the SD card on the phone). Suffice it to say that I did all the steps exactly as written in the guide. I was prompted when to run the next batch files each time, etc. Entered the proper commands in the terminal utility, and so on. Everything as written.
After clicking on step3.bat, the phone immediately rebooted to a Fastboot screen. In the meantime, the batch files disappeared off my desktop.
So, for the past 15 minutes or so the phone has been sitting on Fastboot and vibrating away.
Here's what I see in the small Fastboot screen:
Fastboot Mode (in red)
stuff like Product_name, Variant, HW_Version, etc. up until it says LOCK_STATE.
Ok, after all of that basic stuff, it says:
[1090]
[1140] Fastboot mode started
[1670] fastboot: processing commands
[17600] usb_read() transaction failed; txn_status= -1
[17650] usb_read: DONE: ERROR len=64
[1700] fastboot: oops!
[17750] fastboot: processing commands
And that's where it sits, doing seemingly nothing and vibrating away.
Can anyone assist?
Try a different usb port. then rerun step 3.
me2151 said:
Try a different usb port. then rerun step 3.
Click to expand...
Click to collapse
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Heyitsrick said:
Will do...was just thinking of doing that since it said "usb read error". Will report back.
Click to expand...
Click to collapse
First off, a big thanks for helping me.
Update: OK, changing the USB port worked I re-ran Step3.bat. I have made it through getting to TWRP, and have done these steps:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
So, with that all complete, it's rebooted to a Verizon screen (horizontal progress dots) and a low buzzing.
I did try what you mentioned in the guide to get over the wait time by pulling the battery, reinserting with vol down key pressed and re-attaching the USB to flash boot2.img via fastboot, but it didn't get back to fastboot after the battery/voldown/usb. It went back to the same Verizon screen after the obligatory "Corrupt" screen came on.
Can I assume that I can wait this out for 20 minutes, or did I miss something in how to interrupt this waiting period for first setup? I do want to (and know I have to) flash boot2.img.
EDIT: wasn't holding vol key down long enough to get into fastboot. Doh. Just flashed boot2.img and rebooted.
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Heyitsrick said:
Looks like I made it! It's at the "Prepare your Phone Screen". Fingers crossed.
Click to expand...
Click to collapse
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
NegativeX said:
Are you still stuck?
I ran into this EXACT same issue on my brand new Verizon v20 on step 3 (both 13a and 12a firmware gave me this issue) and I had to figure out my own solution, even tho I read that 'dirty santa root' thread a thousand times front to back.... (no disrepsect to the OP/Devs of that thread btw!)
Anyways, below, is the link to my solution on my brand new Verizon v20, in case you're still stuck. I've actually reflashed (via LGUP) back to stock a couple times, then re-root/unlock to test out 13a and 12a firmwares to benchmark various battery life/performance markers for a tech site I write for. Ultimately, I have to go through the exact same steps everytime for my Verizon v20.
I know I wasn't too specific in my post below... but if you have any questions, don't hesitate to ask
https://forum.xda-developers.com/showpost.php?p=71371141&postcount=24
Click to expand...
Click to collapse
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
The first time I tried this, it booted up fine, but it went right back to the Logo screen. Doh! I figured perhaps I wasn't waiting long enough with the Volume Down button so I tried it again. What happened the first time when it rebooted to the Logo screen is I released the Volume Down button the moment the phone started to turn on (you feel the vibration). That's when it booted back to the Logo. This second time, I removed the battery again while it was on that never-ending Logo screen to power it off and disconnected the USB cable again. I put the battery back in, then with the Volume Down button pressed down, I reconnected the USB cable. The difference this time is that I did not release the Volume Down button this time UNTIL I saw it was in the Fastboot screen and not the Verizon Logo.
So, at this point the phone was on the Fastboot screen and I saw it was it was ready to go, so I initiated the ADB command to flash boot2.img. It went through its paces and once it got back to the ADB command prompt, I did an ADB Fastboot Reboot command. It rebooted, first with the obligatory corrupt warning, then the Verizon Logo and progress dots, but then after a short while I got the "Hello" screen in red and I knew it was actually going to finish. Whew! Relief! At that point I was eventually at the phone's setup screen for a new user, and I finished setting up the phone, reinstalling apps, etc.
One caveat in this: I don't know why, but even though I had gone through all the steps in "4" section of the instructions, when I checked Root, I wasn't rooted! Huh?
In other words, I had already gone through this part:
Verizon(VS995) and ATT(H910):
4.1) Flash SuperSU.zip
4.2) Go back to Main-menu > Wipe > [Format Data] > Type ?Yes?
4.3) Go back to Wipe > Advanced > Check Dalvik, Data and Cache > Slide to wipe
4.4) Go back to Main-menu > Reboot > System
Click to expand...
Click to collapse
After setting up the phone and reinstalling my apps, I opened up the SuperSU app, and it said there was no executable installed. In other words, it didn't recognize that I had flashed it in step 4.1. Perhaps flashing boot2.img overwrote that? Not sure, but at this point, I set about to figure out how to boot into TWRP Recovery on the phone (not fastboot) to flash it from there (again).
It took me a while to find the instructions on how to boot into TWRP, lol, and it's a little unnerving that before it boots to TWRPyou are warned that all your data is going to be overwritten before you can boot to it, but it did get me back into TWRP. Once in TWRP, I re-flashed Supersu-blahblah.zip and rebooted via the system reboot. (did not wipe any caches again, though).
After reboot, I checked root again, and this time after a bit SuperSu brought up the permissions screen for the Root app that I had to allow, and it brought back a successful Root message.
I then set about to do what I really wanted to do with root - bypass the Verizon entitlement check for hotspot usage, and got that working fine.
All in all, I have to say this was the diciest rooting I've ever had to go through. I guess that's because of Nougat and that there can't be (at least not yet) a "one-click" root. But man, was I worried when I was at the point where I first posted in this thread. I bought this phone as a "new-resale" (never used) phone from Swappa.com for $450, so if I bricked it, I was out of luck. But it seems to be ok now.
Heyitsrick said:
I read your "fix" post to see exactly where you got stuck, as I got stuck first due to the USB port not being able to work correctly and had to switch USB ports on my pc before I could re-run step3.bat.
I see now that you're talking about the long Verizon logo screen with progress dots issue after rebooting post-running step3.bat that I ran into, as well.
OK, what worked for me was much easier in the end than what you did. After step3.bat and the reboot, it would just sit there on the Verizon logo with the progress dots, as you know. There is a notation on the first page of the DirtySanta thread that in order to get around this, unplug the USB cable and remove the battery.
This is the actual note from the DirtySanta thread for Verizon users with the long Logo screen issue:
Once I removed the battery and usb cable, the phone was completely off, of course. Then, I just needed to get it back into "fastboot" on the phone, itself, in order to flash boot2.img via ADB on the PC. When the phone was on the never-ending Logo screen with progress dots, I found that ADB could see the phone ok via the adb devices command, but if I tried to flash anything at that point, it would just say something like "pending", as if it were waiting for the device to be free to flash. So, that wasn't going to work, obviously. I needed the phone to be in the flashboot screen, not the logo screen. I did a ctrl-c to cancel out of the adb flash command, and then set out to pull the battery/usb cable and then reconnect the battery, and while holding the Vol Down button reinserting the USB cable.
Click to expand...
Click to collapse
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
NegativeX said:
I saw that 'fix' and it never worked for me at the point in the rooting process I was in... sadly. You have to be able to even get to TWRP, do the SU install then format/wipe, then you can flash the boot2.img to speed up the booting process. In my case, I was never able to even get to TWRP. Trying to flash boot2.img before being able to get to TWRP, would soft brick my phone with the 'password' screen on bootup and I was never able to get around it, requiring me to LGUP back to stock and try again. Luckily I was able to still figure it out.
As you said, definitely the 'diceist' rooting process I've ever encountered... and I've been rooting phones since the original Motorola Droid 1/Milestone phone. Good times tho! Haha
Click to expand...
Click to collapse
Late response - sorry.
There must be something we each did differently, as we both have the same phones, same carrier, same software revision (13a). I was able to get to TWRP via the button method on the phone. Didn't use ADB for that. I was presented with an ominous white screen about all files will be wiped/deleted, but when accepting that (and hoping for the best, lol), it just went to TWRP. So, again...something or some step(s) must be done differently to get to that point on your end from what I did.
I'm guessing you're through with doing the flashing on this thing, so this is all moot now.
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
kratos380 said:
Hey guys i actually was having the same issues as you were now however after the SU install the wipe etc i reboot to TWRP no matter what i do even when i restart through bootloader or take the battery off it keeps booting to the same place instead to the verizon wizard help please
Click to expand...
Click to collapse
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
me2151 said:
Called a twrp loop. Easy fix. Been posted a lot. Look around for it
Click to expand...
Click to collapse
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
kratos380 said:
I have been looking for 2 days haha literally have like 30 tabs open shifting through i dont know what to do next, i backed up wiped my cache data etc installed SU which had no problems wiped again/ rebooted system and back to twrp, i read that you might need to flash a system.img but i dont know where to find one, would appreciate the help kind sir
Click to expand...
Click to collapse
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
me2151 said:
Look at team digitals ROM thread. Stockish one. Look at post 3. If you still can't find it I'll quote it directly later. I'm busy right now
Click to expand...
Click to collapse
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
kratos380 said:
Couldnt find it sorry im new to this forum please link it when you are free thanks again for the help much appreciated
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70393155&postcount=3
Sorry for the constant posts but i followed the steps on that thread, deleted the misc/fota files and it stopped it going to twrp and booted to the lg logo with the black screen, i waited there for about 2-3 hours to no avail rebooted into bootloader tried the fastboot img 2 and the same thing happened it was just stuck at the lg logo now when it boots to the fastboot screen however adb doesnt recognize the device anymore but fastboot does. Is it time to kdz and start over ?