[Q] Trouble with Lg G2 after flashing recovery. Please help. - Android Q&A, Help & Troubleshooting

I've searched these forums for over an hour now and I can't seem to find a solution to my problem. I had the stock 24A software and I rooted it using ioroot and everything went fine. I then wanted to flash a custom recovery, so I used the steps found on Droid News. It gives a link to an app that you install and it's supposed to flash the recovery.
Once it tried to reboot, I ended up with a white screen that shows a dew lines of text (I attached a picture).
If I try to go into download mode, it will flash for a quick second and then go right back to the white screen. I can't seem to get into the recovery either. The website that gave the instructions for flashing TWRP talked about a similar error on Sprint phones and the cure was to flash the kernel again, but I'm not really sure how. The phone will respond to commands in fastboot, i.e fastboot reboot, but it just goes to the same screen again.
Please help, I'm a little stuck. Can I use fastboot to flash the kernel, if so, how?

Related

[Q] TWRP Recovery - Black screen then boots system

I have a slight problem with my phone right now. I got the great idea to try and build a rom just for myself in kitchen based off the Telus 1.15.661.11 base. Everything appeared to work correctly, I got my rom flashed and working fine, haven't had any problems with it besides a FC issue with the HTC Sense input but i just uninstalled it as i use swiftkey anyways.
The problem is I can no longer access TWRP, I can get into the bootloader fine just when i select recovery it shows the TWRP logo then goes to a black screen and then proceeds to boot into the system. I have no idea how to fix it and but here's what I've tried so fair:
-Reflashing the recovery via fastboot
-Flashing a rom via fastboot (Can't be done gives me some remote denied error, i assumed because its still s-on?)
-Reflashing boot.img via fastboot (Figured it was worth a attempt?)
-Trying to reboot into recovery (Same thing happened, went from black screen to boot. Also i should note I could not get the phone to reboot via adb but could via the cwm rom manager (I just used it to reboot nothing else))
-Factory Reset from bootloader (didn't appear to do anything)
The one thing I have not tried is an RUU, however this was because first off i had difficultly locating one (I had the link somewhere but lost it) and second I don't think there is one for Telus (Although i would assume an ATT one would work?). Also ill try to locate the rom that i flashed, and maybe someone would be able to look at it and see what went wrong. Any help/ideas would be greatly appreciated to try and help restore my recovery.
EDIT: So i ran the ATT RUU and it failed towards the end of the process and I went through the recovery process. Then i re locked and unlocked my bootloader and after that i went to reboot into recovery and it works again. So im not sure what happened but if anyone has some insight it would be nice to know for the future.

[Q] HELP! - Bootlooping - Need Assistance

I tried to install CWM recovery by flashing the zip file in TWRP. It seemed to have flashed fine, but I cannot get into recovery now. When I try, the screen "flashes" and "flickers" a few times before going black. I've used odin to install the .tar file that I originally used to root the device and in goes through the process just fine. However, when I pull the battery and try to go into android stock recovery, it does the same thing ("flashes & flickers and then goes black"). When I try to boot the phone as normal (not into recovery) it boot loops between the blue samsung swirl and the verizon 4g logo.
I was on cleanrom 4.7 if that helps at all. I would greatly appreciate anyones assistance concerning this matter.
Edit: Found a .tar file for TWRP and was able to load it through ODIN. Once into TWRP I was able to restore a backup I made earlier today. Thought I would edit the post in case someone ran across the same problem.
Romans8vs1 said:
I tried to install CWM recovery by flashing the zip file in TWRP. It seemed to have flashed fine, but I cannot get into recovery now. When I try, the screen "flashes" and "flickers" a few times before going black. I've used odin to install the .tar file that I originally used to root the device and in goes through the process just fine. However, when I pull the battery and try to go into android stock recovery, it does the same thing ("flashes & flickers and then goes black"). When I try to boot the phone as normal (not into recovery) it boot loops between the blue samsung swirl and the verizon 4g logo.
I was on cleanrom 4.7 if that helps at all. I would greatly appreciate anyones assistance concerning this matter.
Edit: Found a .tar file for TWRP and was able to load it through ODIN. Once into TWRP I was able to restore a backup I made earlier today. Thought I would edit the post in case someone ran across the same problem.
Click to expand...
Click to collapse
My first time through a bootloop I ran into the same issue and had the same fix.

Need Some Help!

So I'd been having some problems lately with my phone hanging on the Samsung screen on boot. Been running CM11 1/1/2014 nightly most recently. Decided to try using TWRP instead of CWM. That didn't seem to help my issue, so I tried installing CWM again. I used an app called Recovery Tools to download the touch version of CWM. After it said it installed, I tried to boot into recovery and got the error "Unauthorized software found. Please contact Verizon." (paraphrased a little).
Doing some research it looks like that error typically comes up when the bootloader is locked. Now, obviously I had my bootloader unlocked (well, Loki'd) because I was running CM11. Any help fixing this? I'm able to bypass the warning screen on boot if I hold down vol up + power like I'm going into download mode, but then hit vol down to cancel to boot up the phone. Once booted everything is ok, but any reboot just brings that up again. Using ROM manager to flash CWM recovery seems to work ok and it says its installed, but same issue. So does trying to flash TWRP from Goo.
If I were to run this tool that I used to root and loki before (http://forum.xda-developers.com/showthread.php?t=2301720) to install a recovery, would I be able to get everything going again? I think that somehow the recovery I installed wasn't Loki'd, although I picked the right one for my device.
Thank you in advance for any replies.
The fix I found was by pure dumb luck. I ended up trying to flash a recovery with Odin. Odin failed but reboot back into the os. I then used the twrp manager app from the playstore (mainly because goomanager wasn't downloading the recovery at the time) to flash the latest twrp recovery and all was good. Even though Odin failed at flashing the recovery I still think it helped somehow. I haven't thought much about why but I might have to now.
Sent from my SCH-I545 using Tapatalk
You could probably try using ODIN to get back to stock MDK and then Re-Root and install a recovery after.
Edit: And then flash CM11 again.
Sent from my SCH-I545 using Tapatalk
Will this one-click stock ROM work?
http://www.rwilco12.com/downloads.p... S4 (Verizon) (SCH-I545)/Stock ROMs/One-Click
or, which of the files on this page are what I would want? (about 1/3 of the way down for SCH-I545)
http://www.droidviews.com/how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models/
I was actually able to reflash TWRP w/ their app from the Play Store. Still get a lot of boot hangs on the Samsung logo though. Seemed to happen less with CWM, but now I'm too scared to try to install a different recovery. I appreciate all your help guys.

[Q] Loop when trying to get into Recovery

Hey guys so this is the first time I try to throw a new Rom on my one ever since I got it last year and threw SuperUser on it (this is the thread I used, yes I am on a Mac http://forum.xda-developers.com/showthread.php?t=2245782) . Tonight I was able to start the install for ViperOne (http://forum.xda-developers.com/showthread.php?t=2345410) and everything was going good until the end, got a message saying there was a problem w/ installation 7 and to keep the log. Than I got a message saying that I may have lost root access and if I wanted Clockwork to fix it, I selected yes. And now I am on an ongoing loop. I get the green HTC logo saying "entering recovery" on top and than the recover flashes and goes back to HTC screen with the text "This build is for development purposes only..." and starts all over again. I am able to get into HBOOT and the top says ****Tampered**** ***Unlocked*** S-ON. I tried going thru the original thread and everything but I am stuck. Can't get into recover or anything.
Like I said earler, this is my second time doing this so I didn't clear anything prior to starting the ViperOne flash, I wasn't sure if I needed to. Anybody ever have this problem before? Or can someone help me out please?
I appreciate any help guys!
GCRamiro said:
Hey guys so this is the first time I try to throw a new Rom on my one ever since I got it last year and threw SuperUser on it (this is the thread I used, yes I am on a Mac http://forum.xda-developers.com/showthread.php?t=2245782) . Tonight I was able to start the install for ViperOne (http://forum.xda-developers.com/showthread.php?t=2345410) and everything was going good until the end, got a message saying there was a problem w/ installation 7 and to keep the log. Than I got a message saying that I may have lost root access and if I wanted Clockwork to fix it, I selected yes. And now I am on an ongoing loop. I get the green HTC logo saying "entering recovery" on top and than the recover flashes and goes back to HTC screen with the text "This build is for development purposes only..." and starts all over again. I am able to get into HBOOT and the top says ****Tampered**** ***Unlocked*** S-ON. I tried going thru the original thread and everything but I am stuck. Can't get into recover or anything.
Like I said earler, this is my second time doing this so I didn't clear anything prior to starting the ViperOne flash, I wasn't sure if I needed to. Anybody ever have this problem before? Or can someone help me out please?
I appreciate any help guys!
Click to expand...
Click to collapse
You need to update your custom recovery to TWRP 2.6.3.3 then flash your rom
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
clsA said:
You need to update your custom recovery to TWRP 2.6.3.3 then flash your rom
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks! I'll start right on it.
I was able to flash twrp but I don't have an option for erase cache. I selected reboot bootloader tried to go into the recovery but it flashes a bit than goes back into the loop.
So I was able to clear the cache and everything, I just now need to find a way to get the zip on the phone. For some reason I can't see it anymore. Could it be because I flashed it once already?
And I was able to install the Rom succesfully! Thanks for the help. I learned how to push the rom in tonight and got it going. Now I'm having a problem with the Viper One rom. Have any of you guys used the rom? I go thru everything, flash successfully but after I go thru all the steps for the setup, I get a mesage saying "Unfortunately Setup has stopped" and my only option is to hit Ok. Once I do that I go to a black screen and thats it. I tried to reboot the phone but it stays on the Viper One logo for 10 minutes now.

Stuck in bootloop

I have a SGP311 and started to root by following the guide at http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377. Works prefectly! Unlocked using the guide at http://wiki.cyanogenmod.org/w/Install_for_pollux_windy which also worked.
But once I flashed the boot.img it start bootlooping. The option "backup and restore" isn't visable in the recovery mode. I can't find install from zip either. I can install from external storage, but that doesn't work either.
I managed to get in to the tablet again by replacing the boot.img to another boot.img, but that doesn't help me to get CyanogenMod 12 though.
I'm new to this, so I might have made something wrong here, please tell me if so
I have a little problem of my own also when I try to unlock the bootloader following the Sony web page everything looks ok but when I boot the tab it's stuck in a bootloop at the xperia logo.....
i had the same issue, once i tried to flash the boot.img from the cyanogen site, it stopped working and went into a boot loop. Here is how I fixed it.
Hold Power + Volume Up until the LED light flashes 3 times in a row. this does a hardware reset and shuts down the tablet.
THen from there i basically just went through the flashing process again to restore it. That brought it back for me.
I think the reason is that the boot.img on the cyanogen website is expecting the stop kernel, but when we flash it using that guide, it is using the FOTA kernel. So it gets tripped up some how. I am still looking around on how to get around it.
skift said:
i had the same issue, once i tried to flash the boot.img from the cyanogen site, it stopped working and went into a boot loop. Here is how I fixed it.
Hold Power + Volume Up until the LED light flashes 3 times in a row. this does a hardware reset and shuts down the tablet.
THen from there i basically just went through the flashing process again to restore it. That brought it back for me.
I think the reason is that the boot.img on the cyanogen website is expecting the stop kernel, but when we flash it using that guide, it is using the FOTA kernel. So it gets tripped up some how. I am still looking around on how to get around it.
Click to expand...
Click to collapse
it seems that you just haven't unlocked you bootloader or using boot.img with broken recovery.
The bootloader was unlocked fine. Went through Sony to get the code and unlock it. I was even able to flash Previously using flashtool. I re ran the flashing to get back to where I was and tried it again and it seemed to work. The only way I could reboot was to hold power and volume up till I got the 3 flashing lights. Then I could get into recovery.

Categories

Resources