Database Develop

stuck on boot loop after 4.1.2 update

update wouldnt install the stock way so decided to force it with odin first it just failed in odin on the last step, so i found the cf auto root method ran that and now i cant even get back to download mode help!!! thanks.
edit was able to get back into download mode figured out i was pressing the button the wrong way. anyway tried reflashing the 4.1.2 build i found and after flashing it says "fail" at the modem stage, so i restarted download mode and flashed the cf auto root again, it started to "update apps for 4.1.2" and kept rebooting itself where it left off, now when booting it said "starting apps" and just reboot again and now just keeps rebooting.
any help would be greatly appreciated.

Have you done a reset since flashing?
Sent from my GT-N8000 using Tapatalk HD

RavenY2K3 said:
Have you done a reset since flashing?
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
What kind of reset? (cant factory reset dont have a recovery to do that with) i've tried taking battery out and putting it back in and it just boot loops after installing the cf autoroot file. so i than tried flashing the 4.1.2 file and it fails again, like a vicious cycle. downloading the stock image now i just want the camera to boot again i shouldnt have bothered with the update lol.
edit: installed stock image get same fail message at modem part, so ran the cf autoroot again it than restarted and "upgraded" all the apps went all the way through this to to finishing boot and now is boot looping again!!!!!!!!!! errrrrr i should have never even bothered with all this.

don't you have at least a stock recovery?
holding zoom+ while turning on my galaxy camera boots it into a simple recovery mode.
4th option is "wipe data/factory reset"
the stock recovery doesn't have as much options as cwm or twrp, but it's enough for a reset.
for recovery or download mode you always have to power down your camera completely, if quick startup is enabled it goes into standby instead so you may have to pull the battery first.

dragonfly1113 said:
What kind of reset? (cant factory reset dont have a recovery to do that with) i've tried taking battery out and putting it back in and it just boot loops after installing the cf autoroot file. so i than tried flashing the 4.1.2 file and it fails again, like a vicious cycle. downloading the stock image now i just want the camera to boot again i shouldnt have bothered with the update lol.
edit: installed stock image get same fail message at modem part, so ran the cf autoroot again it than restarted and "upgraded" all the apps went all the way through this to to finishing boot and now is boot looping again!!!!!!!!!! errrrrr i should have never even bothered with all this.
Click to expand...
Click to collapse
See here for details on how to enter recovery.
http://forum.xda-developers.com/showthread.php?t=2080675
Sent from my GT-N8000 using Tapatalk HD

RavenY2K3 said:
See here for details on how to enter recovery.
http://forum.xda-developers.com/showthread.php?t=2080675
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
Thanks so much worked at least it boots now i think ill just stick with 4.1.1 and a working device thanks for all your help.

[RESOLVED] Unlocked XT1058; Bootloop & Failed System Flash

Long story short: Phone won't boot past "Unlocked Bootloader" warning; Recoveries won't stick; Unknown Error & Freezing when trying to Flash System.img
I own an ATT Locked Moto X, but went ahead and unlocked it by purchasing the oem code. No issues there.
I decided to go ahead and try rooting it too, and was able to flash TWRP as my recovery. Still, everything seemed to be looking good, until I tried hard rebooting (to see if root would last). Upon rebooting, I could not get past the warning sign, notifying me that the bootloader was unlocked. I waited, and waited, and restarted again, but all progress stopped there. I would be the first to admit that whatever happened was probably my fault; perhaps I flashed some files in the wrong order, or entered a wrong command into fastboot. I don't know, and frankly don't care. My only question is how to get out of this mess and back to rooting, or at the very least, back to stock ROM now that I'm unlocked.
Booting into recovery only leads to the red triangle over an open android mascot, with the "Android Recovery" title. So clearly TWRP didn't stick; I tried reflashing, but nothing lasts past reboot. Then I tried flashing Philz Touch instead, which, upon exit, notified me that root was not enabled. So I rooted, rebooted, and was finally able to see Philz Tough again, even though I still can't boot normally. That time, both Philz Touch as well as root seemed to have stuck.
With that minor victory I downloaded the latest firmware for my model and tried to flash the components over, thinking I had somehow corrupted the existing OS files, but here's where it gets particularly frustrating. I am able to flash every file except for system.img, even though I am using moto-fastboot, which I understand is a common mistake. I get no specific error code, simply "Unknown Error," upon which the phone is frozen in fastboot. The phone remains unresponsive until I hard reboot [back into fastboot], and see that, once again, Recovery is back to stock. So now I'm baffled. I can't seem to find a way to flash the system file, factory resetting doesn't work, and my recoveries are constantly reverted back to stock. Does anyone have any advice, or suggestions for what I could try next?

You try RSD lite?
Sent from my XT1058 using xda app-developers app

southern87 said:
You try RSD lite?
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I was already downloading it just as I saw your post, as my last-ditch effort. It also failed, but it gave me "Unknown USB Error," which is all I needed, it seems. I tried a different USB slot on another side of the computer, and lo-and-behold, the flash finished.
I'm not sure what saddens me more, the fact that I pushed off making this post for hours, only to have the solution less than an hour after I do, or the fact that I never thought to try a different USB port... In any case, sorry for the uselessness of this post. I think I'll save rooting for another day though...

[Q] Bricked experts out there come hither

So i got a new lg g2 for verizon last week. ive had good experiences with cyanomod and other roms so i figured off the bat that i would install one of these. turns out they were alot more problems than it was worth. so i went back to stock rom and rooted. for some reason i took OTA. now phone is stuck in fastboot. so i went through this thread http://forum.xda-developers.com/showthread.php?t=2582142. so i got everything done and figured out (running live ubuntu so getting automount to stop was a challenge and then figuring out the new file paths). so now i reboot phone and try to get into twrp (from complete power off hold power button and volume down, release when logo shows and press again). so i get the "do you want factory reset" screen and i click yes, yes then it just goes into fast boot again. problem is now not even linux is reconizing the device. device doesnt go into twrp. cant get into download mode to reflash. all i got is "[16370]fastboot mode started [16420]udc_start() [16590]-reset- [1660]-portcharge- [16640] fastboot: processing commands.
do i have any hope? the phone is new from a third party so i dont think i have a chance to return to the seller, and im not sure if lg will take it either

added info
also, just read and possibly part of problem, twrp was 2.7.1.0, either way though im still stuck with it at this point

ok, so just a bit more info. now when the phone is plugged into windows 7 computer it automatically installed a driver "USB Movem Phone ADB port". so i figured id try to run adb devices and see if it showed, no luck. dont know if this puts me in a different situation or not...

Did you try via terminal $ reboot-bootloader you may be able to force into bootloader for adb sideload twrp 2.7.0.0
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
Adb and fastboot are two different programs. If your in fastboot mode computer won't recognize adb devices. While in fastboot mode, reboot-bootloader then see if you can get adb through toggling vol + or -
Sent from my VS980 4G using XDA Premium 4 mobile app

actually i just got a step farther.... now i have twrp installed and working (turns out version 2.7.1.0 and 2.7.0.0 both didnt work with my phone even though i specifically got the versions for my phone. now im using 2.6.3.2 in case anyone else is having issues).
so twrp is on the phone. by random luck i apparently had all the rom zips left on the SD card. so i was able to flash a known working rom (at least it was working well enough to get by...). so i flashed the rom and rebooted the phone. unfortunatly it went straight back into twrp. i dont know if there is a flag i havent set or what. i thought i saw a walkthrough about what to do at this point, so im still working on it and i will update if i can fix it... but as i stated right now have twrp 2.6.3.2 working, still no download mode apparently(ill mess with this more because originally this is how i was flashing back to stock when things went wrong), and even though twrp installed a known working rom its still booting straight into twrp (without the whole power and volume down seqeunce...)

Some ROMs won't work on 2.6.3.2
Sent from my VS980 4G using XDA Premium 4 mobile app

would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp

If recovery doesn't detect a compatible ROM it bootloops. That or corrupt download itself, make sure to verify md5s whenever possible.
Sent from my VS980 4G using XDA Premium 4 mobile app

YAY, got it mostly back kinda sorta. so i followed this http://forum.xda-developers.com/showthread.php?t=2451696 after getting back into twrp. i dont know what this did or if it helped. then i flashed a new rom (which i also by chance had on the SD already) i believe it was malladus 1.2.9 and it worked (except i didnt put gapps or anything so it was having a fit about play... now its restarted and i have download mode back so ill just flash the whole thing with the regular rom (the rom on this website might even be older than the phone, but for me it worked well...). here is that website i case anyone needs it http://www.lg-phones.org/guide-to-flash-restore-unbirck-verizon-lg-g2.html i will reflash and post results, hopefully a bone stock phone to start over with...

glenn3451 said:
would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp
Click to expand...
Click to collapse
As far as a straight to recovery, I haven't had that problem on my g2. On my tablet,I run multi ROM recovery and it will go straight to recovery if a ROM is not installed. I would think it would do the same on vs980 twrp.
Sent from my VS980 4G using XDA Premium 4 mobile app

btw thankyou for suggesting a different rom, wouldve probably been stuck for awhile without that advice. so flashed verizon stock firmware(which also deletes everything) and its 100% running with the exception of the activation (switched back to old phone while working on getting this guy running again). i feel like ive learned alot more than i ever wanted so ill stay subscribed to this thread and if anyone has similar issues when you post hopefully ill be able to help alittle... no promises though

Safestrap Safe System Not Active, Cant seem to get active

I dont know what to do. If I go to recovery from safestrap it just restarts normally. If I hold power and restart from recovery, it goes to stock recovery where update from ABD doesn’t let me explore my phone storage. Any idea? I tried SELinux already but it didn’t work. I'm on TMS 3.0 900a 5.0 and I'm trying obviously to have Safestrap as my default recovery and able to get to it without NCE Flashing
EDIT: I did the steps and NCE flasher again to reinstall the ROM to get to Safestrap recovery again and it says "ROM Slot: Stock" at the top in red. Would that be why? Should I change it to another slot?
EDIT 2: Reflashing ROM did not help, same position as before. Even though I let the boot animation go all the way without restarting. Even if I boot to recovery in Safestrap recovery after I NCE Flashed, it goes to stock recovery. Then when I rebooted it from there, I did see the screen where I choose safestrap recovery on the bottom left or continue on the bottom right, which otherwise is not there after I flash TMS3.0. However continuing gave a black screen.
Also fixed permissions in Safestrap recovery, didn't work.
EDIT 3: So my phone had soft bricked from flashing via flashfire, I had to get a VM and then odin and flash the OC4 to fix it. Then I saw an article going over safestrap install and saw the "not active" status is normal but obviously the lack of functionality isnt. So I guess my question is not how to get the active status but how do I get safestrap recovery to be functional? By functional I mean that recovery or continue screen on boot up and booting to recovery loading Safestrap.

And btw I see the little android error bot where he's opened and it has the red exclamation point above him right before it goes into recovery.

Go to hashcodes thread and try a different version... There is another 3.75 that has working rom slots. . That may work a little better. But safestrap is wonky on lollipop
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

tried going from slim to cm...

okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt

dorkydroid said:
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
Click to expand...
Click to collapse
try stock 5.1.2 firmware
otherwise there is no fix that I know of
Sent from my KFFOWI using XDA Labs

i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this

dorkydroid said:
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
Click to expand...
Click to collapse
I fear I'm in the same boat. Which version of flash fire were you using?
Any further progress?
Sent from my Nexus 7 using XDA-Developers mobile app