yeah, im a dummy. i know. so when i told the phone to update it rebooted to the twrp recovery and stopped because twrp is a straaaaaaaaaanger. first it must have wiped or something though, because reboot brought twrp back up. wipe, restore, reboot, twrp. ok, wiped, flashed different rom and gapps, reboot, twrp. apparently twrp is the only thing on the phone? ive never pulled such a boner so im stuck as to what to do. every thread about restoring stock is full of links to 404s and other files that are no longer there. anyone have any ideas?
Just looked it up everything is there to use the lg flashtool and all files to return to zva stock.
i used the dev/zero fota/misc fix. after starting this thread i found a thread making this one redundant but OPs cant delete the P i guess. if a mod wants to delete this thread, i wouldnt be mad at them haha.
Related
I updated using this guide:
http://www.droidviews.com/update-att-lg-g2-to-android-4-4-2-kitkat-without-losing-root-and-twrp/
All was well until I got a message for the OTA update mentioned in the post below and allowed it. I know, stupid.
http://forum.xda-developers.com/showthread.php?t=2672931&highlight=update&page=9
So now my phone just boots into TWRP recovery and nothing seems to get me out of it. I've cleared the cache, I've wiped the phone, I've reinstalled the Zip. Everything just reboots me into TWRP. Is there a way out of this without flashing back to stock?
Trying to figure this out first off here's the details of the device in question.
Sgh-i377m Canadian koodo. Running stock ROM L 5.0.1
I've rooted with cf-autoroot and then flashified to Philz 6.14 I think. Just because I've never tried it. Then rebooted wiped cache/davlik then rebooted and flashified to the latest twrp 2.8.6 with f2fs support from the optimized 9105 cyanogen mod 12 thread. Everything was solid. I upgraded root to the beta copy in chainfire's supersu thread.
I rebooted several times and was fine. I went to bed and I woke up with my phone unrooted and factory reset asking me to start from the beginning of setting up my phone. So incredibly angry I didn't believe the situation and I setup the phone over again. Then rebooted into recovery and sure as fart that you shouldn't of trusted it was the factory oem recovery. So I attempted to root again and was successful and then upgraded the phone to what flashify lists as the latest twrp for the jfltecan as 2.8.4 and then upgraded to 2.8.6 f2fs from the thread mentioned earlier and sure enough not even 20 min later after I got out of the shower it factory reset itself and installed the factory oem recovery. I made sure this time software update was disabled and rooted again. I flashified to 2.8.4 only as per flashify reporting is the latest and everything seemed fine so I thought maybe the recovery being for the 9105 as the problem. I went to eat and the problem happened again. Am I the only one experiencing this?
Am I doing something wrong ? someone please help.
Signed sincerely,
Getting pissed off of flashing the same damn thing over and over.
Thank u.
900A, AT&T, WAS 4.4.4. I rooted my phone with towelroot by downgrading via ODIN then reflashing 4.4.4. I've had the phone for a year and wanted to experiment with some custom roms--specifically Twi5ted Lollipop. The version I found last night was V3. Anyways I followed the instructions of installing safestrap then attempting to create a partition to host the mod. Every time I tried to boot the partition I would wait 12 minutes with nothing but a black screen (I presume a bootloop.) After reading some posts here I found it requires a clean flash--not a dirty flash. So I used safestrap to backup, then I wiped it and installed the mod. Nothing--still black screen. I then attempted to restore the backup I saved--fails every time.
At this point being the noob I am, I started to get very concerned. I went into advanced wipe and for some reason selected 'system' and wiped it. After a reboot, it shows the Samsung logo, goes blank, vibrates then goes back to the Samsung logo. I went into the standard bootloader and attempted to restore to factory settings but there is nothing to restore of course cause I wiped everything.
I'm currently at work bored as heck cause my phone is wiped. I can still go into download mode thankfully. Should I have no problems flashing stock via ODIN when I get home on my lunch break? Which stock firmware should I flash for this phone?
Thanks!
http://forum.xda-developers.com/galaxy-s5/help
yes, wrong section, but hopefully the post is moved soon.
since you have a G900A, make sure you only flash an older 4.4.2 firmware, so you can still root. the newer 5.0 firmwares are currently unrootable.
Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.
I was running CM 14.0 with TWRP. I did a OTA download through CM Updater to 14.1 nightly. The phone rebooted to recovery and nothing happened. I manually found the OTA under sdcard/cmupdater and flashed the file. Now, whenever i try to boot the phone, it keeps going into recovery. I tried restoring nandroid backup, wiping everything and installing the older cm14.0 zip and nothing worked, phone keeps going into recovery, what can I do, please help!!
I think there are few users reported same issue before.
Try to check the ROM thread. If Im not mistaken, the solution has been posted there.
Hope this help. Good luck
Sent from my Nexus 4
Sorry, I panicked and didnt look through the forums thoroughly before posting. I managed to boot my phone up by flashing factory images and going back to stock. Afterwards, I tried to install the CM 14.0 again (StephanMC's build) which was working fine before I tried the update process. TWRP throws error 7 when I try to flash it. I looked around and found that the problem can be fixed by editing the Meta-INF, but I did not have this problem before, did I mess something up in the factory image flash process?
Would it be wise to go ahead and force install the ROM by editing the zip?