[Completed] LG G2 Boots into TWRP Every Time I try to boot after Update - XDA Assist

Alright, so before I say anything, I have not visited this site nor have I conducted any business with roms, TWRP, etc in the past year let's say. I used to be an avid visitor, flashing a bunch of roms, but was tired of the amounts of bugs and problems that I found. So I restored my back to stock on my G2 from TWRP. Been using it for about 1 year now, just so I didn't have to deal with problems... until now.
So a few days ago I saw an update in my notifications, but for the love of God I cannot remember what it said. All I know was that it needed to update something about the phone, not for example an app. Today I decided just to update it, and suddenly the phone rebooted into TWRP. I thought that was weird so I rebooted it again, and back into TWRP I was. I tried restoring some old backups to see if they would maybe boot into it, but once again it keeps bringing me to TWRP. Now I am stuck in a position where I am unable to use my phone and am not sure what to do next. I haven't visited these forums in a while either so Im not sure where to post this xD.
Honestly if someone can suggest something or help me in any way, it is appreciated. If there is anything I can do to help, just say the word.
I am using the Canadian Variant of the LG G2, from wind. I believe it is a D801 but not an actual D801, as I remember being told to only flash D803 roms as it was basically a D803. Not sure if that helps. Im planning on getting a new phone so I just need this one to hang on a little bit longer.

Thread closed / Duplicate

Related

How to Restore from Latest S3 Nightly?

EDIT: 12/23/2012 3:19AM.. Doing a little research I figured out what the issue was. Used Brian Gove's Guide
[How To] Reset your phone in order to return to Verizon(Updated 12/11/2012)
From Step 5 Onwords and everything works great.
.. I am still stumped on exactly what happen. I am almost positive it was because of the new file structure..
Just Proves that with a little patience and smarts anyone can use the resourced and tools here to solve their own android problems without bothering anyone haha.
Thank you all for your articles and Merry Xmas / Happy Holidays to Everyone!!
now.. I gotta unlock my boot loader and start all over..
Soft Brick.....
I was looking around and I cant seem to find a post that really solves my problem.
I have a Verizon S3 that I rooted and flashed to CyanogenMod Nightly build and everything was working great.
I used Rom Manager Premium and it updated me to update to CMW 6023. I went ahead and updated.
I saw that there was an update for my Daily As well 12/22/12 so I went ahead and used Rom Manager to download it and install it for me like It did with my last 16 Roms. That Rom had some strange things going on so I flashed to an older rom 12/20/12 and that rom was buggy as well.
Finally I decided that I should just stop with the Daily's and use the stable. When I loaded the Stable things started to still act strange. Mostly the Keyboard would not work and keep crashing. I decided then to just reload my original backup from Verizon.
Before I went in to recovery i took a look at my files and backed everything up. However then I noticed something that was not there before, a folder /0 with most of my main files inside.
I went into CWM v6.0.2.3. and tried to do a restore to my original nandroid backup from verizon but it looks like it failed.
It Says "Error While Restoring System" and kicked me back to CWM
Now when I reboot all I see is the White "Samsung Galaxy s3"
Did I Screw the pooch on this? Kinda nervous haha.
I am Posiive its a Soft Brik and hoping there is a way to fix it.
I can however get to Download mode. If anyone knows a great guide to help me reflash with Odin that would be fantastic.
thanks guys, been a long time reader and this is the first problem I have really had.
I apologize if this has already been over in a post.
Just a quick step breakdown would be great. I am really hoping that I didnt brick my phone.
Thanks for the help and Merry Christmas / Happy Holidays to everyone.

Slowly learning - TWRP update and fast boot to system boot loop

It's been about 4-5 months now since getting a G3. Nice phone. I also picked up a few OPO's along the way. Rooting, custom rom, etc.
Today, while messing about with my G3, one of my daughters came into talk about what to wear at their next big date. Some distraction later I came back to my phone, thinking it was my OnePlus, and I installed TWRP manager, to update from 2.8.0.0; I forgot I had my G3 in my hand and updated for the OPO to 2.8.1.
The phone rebooted into ADP and and would not boot into recovery. It would go into system after taking out the battery.
Some months ago this would have thrown me for a loop too. But with the bit of knowledge I've picked up from the many folks here, it seems a little problem. I copied over a TWRP img to the internal SD card, rebooted to system, and Flasified TWRP. Lastly restored my most recent backup, from this afternoon.
Sure, I could have done the same through ADP commands, but this was the most 'visually' simple.
Awesome.
Thanks of the many who have helped me learn at this site.

[Completed] Formatting Samsung S3 Problem

Hey, so basically I'm in a situation where I have no idea what to do.
I recently just got a new phone, and am going to give my Samsung Galaxy S3, SGH-T999V model - from Wind Mobile to my Dad. Basically, when I first got the phone - a couple months after, I decided to try Rooting it, and I did, successfully. Since I didn't really know what to do with my rooted phone, I decided to unroot it - then tried rooting it again some months later, but it didn't work successfully. Basically my phone wasn't rooted, but I had the "Team-Win" recovery on it.
I wanted to bring my phone back to it's original state - and have the stock recovery on it. After some Googling, my solution seemed to be to flash the stock rom for the SGH-T999V model onto my phone using Odin. And I did that - and it worked successfully. But I still couldn't check for OTA updates or anything, it said my phone had still been modified in an unauthorized way.
Now that I need to give the phone to my Dad, I have to format the device and erase everything. This is where my problem starts. When I try to format it (using the Stock recovery), I see a bunch of error messages, with the Android logo falling down in a kind of dead way. I reboot my device, and nothing changes.
It still has all my data, and everything on it.
Sorry if this is the wrong area to post this (I'm relatively new to the forum), and if my problem doesn't make much sense - I've tried being as detailed as possible. Could anyone help?
Hi, thank you for using XDA Assist. Flashing the stock firmware should show you to get ota's. This should have everything you need,http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125. Also, you can ask further questions here,http://forum.xda-developers.com/galaxy-s3/help/help-thread-galaxy-s3-question-t2690307
Thread closed

Null IMEI/Baseband

Hey guys, so I'm pretty new to all this, I wanted to root my Galaxy S6 - SM-G920F - to be able to play pokemon from home... yes, that sad. So I started reading XDA like my brother recommended and "learnt" how to root my phone. In the beggining when i was installing SuperSU I had some problems and my phone went into bootloop, but it was because of my cable, I then reflashed it with another cable and it fixed the bootloop issue. I went on to install TWRP and that's when mistakes started happening. First of all, I forgot to back up my phone, including the EFS which, after reading countless posts, I understood is what gives the phone the IMEI code.
I tried installing the standard Xposed on Galaxy S6 (only later on i learnt you must use Wanam on samsungs from S6 and above) and my phone went into bootloop, with out knowing what to do (i tried the uninstall zip but it was failing to install from twrp...), very stupidly, i deleted my System folder... After much more reading, i tried using KIES3 and Smart switch to recover, but they always ask for the stupid recovery code,which I don't have, when i tried the upgrade and initialization option... I tried costum roms and a ****load of stuff. Custom Roms would usually work, my phone would turn on and that's when i noticed my SIM wasn't beeing recognized. (later on i also found out i didn't have IMEI) tried flashing the appropriate MODEM for my galaxy but it all failed. I don't remenber all the stuff I did tbh... I tried the tyrannus ROM and XtreStoLite Universal Deodexed Mod Edition ROM, and tried flashing the MODEM that comes with the last mentioned ROM and yeah, probably just useless attempts that wouldn't fix the problem in the first place. Then i tried flashing Stock, from Sammobile: I bought my phone at the Portuguese vodafone, so G920FXXS3DPF5_G920FVFG3DPC1_TCL (marshmallow) with Odin but it would always fail. Then i read something about splitting the folder in 5 and flashing 1 by 1 and it would work until the Hidden zip, which would always fail. I tried not flashing Hidden and my phone turned on and I went back to stock although, still with out IMEI or baseband. Then after more reading, i found out the best solution would be giving it to a store.
So i just rooted, twrp and did what i wanted to do in the first place. With the correct Wanam Xposed this time (later on i found a way to hack pokemon with out root... sucks :v) and i managed this time.
Yesterday i went to the stored and today the guy told me to go get it, with high hopes i went there, to find out he couldn't fix the problem... He tried Octobox to rewrite the IMEI from the one in the back of phone, but he says it failed. So now I really don't know what to do. The guy went on holidays and told me to go back there when he comes back, we wants to try to downgrade to lollipop and try to fix it from there (he said he has more tools available to work with). It could work, Galaxy S6 just got marshmallow 1/2 months ago officially, and i bought the phone in october of last year, so maybe with the ROM it came with, I really don't know.
At this point I'm just looking for suggestions. I'll be paying attention to the forum and try to reply to all the questions you might have to my best. Thank you all for your time and patience!
:EDIT: so... another major mistake i guess, I found out today, by asking my parents where they got the phone, that the phone wasn't actually purchased in vodafone, the phone was bought in a Samsung store, so it is unblocked. So most likely I've been flashing the wrong stock rom all along. Could you guys guide me in the right direction from here?
What would be the appropriate ROM for the unblocked? vodafone portugal is TCL, optimus is OPT and MEO is MEO. There is another one under the name TPH, would that be the appropriate one?
Solved
Okay... using the correct stock rom fixed all my problems... sorry for wasting your time guys! TPH was the right one
Where did you find your roms?

Need, my device keeps encrypting itself!

I've only had this phone for a few weeks, bought new from Target. It is a US BLN-L24. It originally was running Marshmallow but I updated it to Nougat via the official updater (BLN-L24C567B360).
The first time I got this issue was when I rooted the stock ROM with Magisk. I later installed Apps2SD Pro (for linking apps to 2nd partition on SD card). It mounted this partition, I rebooted, the device then asks for a PIN# which I didnt have and never set. Afterwards I rebooted to @OldDroid's TWRP, it couldnt mount data partition, some error about not being able to find the crypto footer. I then used the dload method to rollback to MM, then updated to Nougat again, and rerooted, this time with systemless SuperSU instead..
Then eventually everything went fine for awhile, but it happened again. So I decided to try a custom Nougat ROM. I went with Resurrection Remix 7.1.2. And then.....it happened again. This time I had rooted with Magisk. I tried yet again, but with SuperSU. And yet again with Phh's Superuser.
I've also tried AOKP, AOSPA, LineageOS, OctN, all Nougat, the issue returns with all of them.
So, no matter what root solution I use, the encryption issue eventually returns. Magisk, SuperSU, and Phh are all supposed to disable data partition encryption. But it seems they aren't.
What I've tried so far:
1. 3 different root solutions, same results
2. Formatting data and wiping all partitions in TWRP immediately before installing a ROM zip, which is supposed to remove the encryption
3. A custom kernel (CycloX)
4. Formatting my MicroSD, as exFAT, every time I check it for errors in Windows 10 corruption is found and repaired, but it always returns. I had initially thought that the encryption might be related to the SD
It has happened numerous times, on different ROMs including stock, and MM/Nougat, and with different root solutions. I know when it happens, I get stuck on the boot logo forever. TWRP reports that data can't be mounted. At one point my phone randomly rebooted into eRecovery and I was shown a message stating that data partition was corrupted. Sometimes it happens as little as 15 mins after booting into a freshly installed ROM, sometimes it takes a few days, but it always comes back no matter what. So far several dozen times.
I'm at a loss as to what is the cause. It could be a hardware defect, a firmware defect/bug, or something I'm doing wrong/missing. So I really have to ask if others are experiencing this too, and what you did to resolve it, I'm sure I'm not the only one. Please provided detailed steps. This is driving me crazy. I bought the 6X to replace my Samsung Note 4 which recently died after 3 years of loyal service. I'm liking this phone alot, it's very powerful, but this is killing me.
If anyone can help then I would greatly appreciate it. If I can't get this resolved then I'll just sell the phone on Craigslist after returning it to stock.
Thanks!
C'mon guys, really need some help here. I know I can't be the only one with the encryption issue, since the 6X is encrypted by default.
AnonVendetta said:
C'mon guys, really need some help here. I know I can't be the only one with the encryption issue, since the 6X is encrypted by default.
Click to expand...
Click to collapse
Actually I think you are the only one with this issue. Flashing Magisk alone will remove auto-encryption. But then you already flashed custom roms.
After 4 more days of testing, I still haven't been able to find a solution. The issue has been less frequent ever since I started using the stock charging brick that came with the phone, before I was using a slightly larger LG brick, I thought it would charge faster. But maybe it was supplying too much power, which partly explains why the phone would sometimes act erratically on the battery charging screen while turned off.
But it's not solved, sometimes I still can't boot, it just gets stuck on the ROM boot logo, makes no difference whether it's stock or custom ROM. I can get past the "your device is unlocked" part though.
I no longer think encryption is the biggest part of the issue, I think the /data partition is getting corrupted. This partition uses the F2FS filesystem by default. The last few times I got stuck I booted into TWRP. But instead of doing a factory reset, I used the repair filesystem option on /data, TWRP says it repaired, then the ROM boots fine. But the problem always comes back. It seems to happen most frequently when I completely power off the device then turn it back on, but not every time.
Today I called Huawei customer service and explained, though I didn't mention TWRP, root, etc. They want me to follow up on an email by sending pics of the phone, then mail it to them so they can diagnose and fix the issue. I just restored the stock MM firmware and made sure the bootloader was locked. It was just placed it in the mail, so I'll wait until I get it back then test further to see if this happens again.
AnonVendetta said:
After 4 more days of testing, I still haven't been able to find a solution. The issue has been less frequent ever since I started using the stock charging brick that came with the phone, before I was using a slightly larger LG brick, I thought it would charge faster. But maybe it was supplying too much power, which partly explains why the phone would sometimes act erratically on the battery charging screen while turned off.
But it's not solved, sometimes I still can't boot, it just gets stuck on the ROM boot logo, makes no difference whether it's stock or custom ROM. I can get past the "your device is unlocked" part though.
I no longer think encryption is the biggest part of the issue, I think the /data partition is getting corrupted. This partition uses the F2FS filesystem by default. The last few times I got stuck I booted into TWRP. But instead of doing a factory reset, I used the repair filesystem option on /data, TWRP says it repaired, then the ROM boots fine. But the problem always comes back. It seems to happen most frequently when I completely power off the device then turn it back on, but not every time.
Today I called Huawei customer service and explained, though I didn't mention TWRP, root, etc. They want me to follow up on an email by sending pics of the phone, then mail it to them so they can diagnose and fix the issue. I just restored the stock MM firmware and made sure the bootloader was locked. It was just placed it in the mail, so I'll wait until I get it back then test further to see if this happens again.
Click to expand...
Click to collapse
Hello, can you help me? I have the same model BLN-L24C567B360. I got this phone today and updated today as well right out of the box. My problem is that I installed TWRP 3.1.1.0 Berlin version for this phone and it doesn't work at all. Now I have my phone working ROM but with no recovery option. Can you give me a link with the files I need? I was thinking on putting back the original recovery.img file back but unfortunately I never thought on doing a backup of it. I read on the top that you have all original stock files. Thanks
@jaimejdv: Are you having the same encryption/corruption of the data partition that I'm getting? Because if not then you should start your own topic.
If you have installed the correct TWRP by OldDroid, via fastboot, then there is no reason it shouldn't be working. Instructions are available in other topics, I won't list them here.
There are some Marshmallow downgrade files on Huawei's website, go search for them and follow the instructions in the PDF they provide.
And BTW, I really don't appreciate you trying to hijack my topic. I understand you need help, but I posted this topic because I'm specifically having trouble with encryption/corruption. This isn't meant to be a generalized help thread.
Right now Huawei has my phone, I'm waiting on them to fix and return it so I can do more testing. If it doesn't work as expected, I'll be selling it on Craigslist.
AnonVendetta said:
@jaimejdv: Are you having the same encryption/corruption of the data partition that I'm getting? Because if not then you should start your own topic.
If you have installed the correct TWRP by OldDroid, via fastboot, then there is no reason it shouldn't be working. Instructions are available in other topics, I won't list them here.
There are some Marshmallow downgrade files on Huawei's website, go search for them and follow the instructions in the PDF they provide.
And BTW, I really don't appreciate you trying to hijack my topic. I understand you need help, but I posted this topic because I'm specifically having trouble with encryption/corruption. This isn't meant to be a generalized help thread.
Right now Huawei has my phone, I'm waiting on them to fix and return it so I can do more testing. If it doesn't work as expected, I'll be selling it on Craigslist.
Click to expand...
Click to collapse
You can stop crying now, I won't be using your "topic" anymore. I just replied to you asking for files that you already have.
And BTW, I don't need them anymore but thanks anyways.
Yoooooo did Huawei do anything yet?
I just got the phone back in the mail this morning from Huawei, after waiting about 3 weeks. And.....THEY DIDN'T EVEN FIX IT!!! They sent it back unrepaired, with a note saying it wouldn't be fixed because their technician found water damage. But I'd say that's just a generic canned excuse to not fix it. I bought this phone very recently from Target, I never exposed it to liquids at all. I'm very careful with my phones, I have 3 old ones for over 5 years and they still look good and work fine. I don't do stupid crap like using my phone in the rain, dropping in sink, etc.
So, I unlocked the bootloader, flashed TWRP, then installed Resurrection Remix and Magisk. I did no other changes whatsoever. And sure enough, within 6 hours it was just hanging up forever on the boot logo. I went back into TWRP and got the same error about the data partition not having a crypto footer. I can repair the partition in TWRP without factory resetting, and the issue goes away for awhile, but eventually returns.
At this point I'm really angry, having spent around $230 for this phone. So I'm just going to reflash it to stock firmware and sell it on Craigslist at a loss. I don't think I'll ever buy a Huawei phone again, not just because of this phone, but also because their customer service is crap and can barely speak English, as well as their failure to honor the warranty.
I don't know what phone I'll get next, I'll probably shell out for a new ZTE Axon 7 on Amazon, with a warranty. Which also has the added advantage of having better specs than the 6X.
Oh well, life moves on.....
AnonVendetta said:
I just got the phone back in the mail this morning from Huawei, after waiting about 3 weeks. And.....THEY DIDN'T EVEN FIX IT!!! They sent it back unrepaired, with a note saying it wouldn't be fixed because their technician found water damage. But I'd say that's just a generic canned excuse to not fix it. I bought this phone very recently from Target, I never exposed it to liquids at all. I'm very careful with my phones, I have 3 old ones for over 5 years and they still look good and work fine. I don't do stupid crap like using my phone in the rain, dropping in sink, etc.
So, I unlocked the bootloader, flashed TWRP, then installed Resurrection Remix and Magisk. I did no other changes whatsoever. And sure enough, within 6 hours it was just hanging up forever on the boot logo. I went back into TWRP and got the same error about the data partition not having a crypto footer. I can repair the partition in TWRP without factory resetting, and the issue goes away for awhile, but eventually returns.
At this point I'm really angry, having spent around $230 for this phone. So I'm just going to reflash it to stock firmware and sell it on Craigslist at a loss. I don't think I'll ever buy a Huawei phone again, not just because of this phone, but also because their customer service is crap and can barely speak English, as well as their failure to honor the warranty.
I don't know what phone I'll get next, I'll probably shell out for a new ZTE Axon 7 on Amazon, with a warranty. Which also has the added advantage of having better specs than the 6X.
Oh well, life moves on.....
Click to expand...
Click to collapse
Sorry to hear you had such a bad experience with them. Pretty crappy that they used a lame excuse like water damage to deny responsibility in fixing the issue.
I agree with you, I will never buy Huawei again. The phone itself is great but the audio is so so bad Im trying to sell mine at a loss as well but no ones calling so Im tinkering with it again. I would be absolutely livid if I spent the money on one of the flagship Huawei phones. Oh well live and learn I guess, at least the 5T comes out sometime next month.

Categories

Resources