Slowly learning - TWRP update and fast boot to system boot loop - AT&T LG G3

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.

Related

[Q] Clockwork Recovery problem

First.. I want to say hello and that i've been reading around these forums for quite a while since I got my Droid about a year ago. I haven't posted anything till now.. but that's only because everyone else usually get's the answers typed faster than me. lol
On to the problem... I think I screwed up. I JUST bought this thing today. I got a little too excited about getting this tablet rooted and might have jumped the gun a little. I used the apk that has been around to root. No problems there. I got ROM Manager loaded... and I ended up flashing the newest recovery from there before realizing that everyone else says to use something else.
So... at this point, i'm unable to reboot into recovery at all. It starts up, acts like it's about to, and then just reboots again into the OS instead. Is there a way to fix this and get it on the correct recovery image or have I totally screwed myself over? Maybe through ADB? I can only tolerate this horrid TnT OS for so long. Took me 20 minutes to get it to update without a FC... Browser, weather, calendar, and a bunch of other stuff FC on me when I tried starting.. Fortunately, those issues are less frequent with the update, but still not working keeping.
I need some "stock(CyanogenMod)" Froyo goodness.. lol I can't have my year and a half old phone outclass this tablet for too long. If anyone can offer any help on this, I would greatly appreciate it.
The good news is you are still booting into the OS, so I doubt you've screwed anything up too bad. Most likely Clockwork Mod just never flashed so you are still running with the gimpy stock recovery and it's puking on the update.zip file you have on your internal sd card for some reason.
First suggestion is get a copy of Clockwork Mod 0.8 and try installing it. The instructions here are geared toward installing from an external from an external MicroSD card: http://forum.xda-developers.com/showthread.php?t=865245 I am not certain why they say that's the only way to do it, since I never did it that way.
I just downloaded this: http://www.mediafire.com/?dvleg4oatkfxm7w and stuck the update.zip and recovery folder into my /sdcard directory, then turned my tablet off, then held down Vol+ and turned it back on. Clockwork Mod should install itself and boots into Clockwork Mod, and that was that.
I never used ROM Manager at all on my G Tablet, so I can't speak to doing anything that way, but I would stick with the tried and true methods at least until you have Clockwork Mod running.
If that fails and you really can't get any recovery working, maybe something did get botched and you might need to use nvflash to fix it, but I doubt it.
Once you get Clockwork Mod running properly, just copy over the update.zip for TNT Lite or Vegan ROM, flash, and wipe data, then you should be good to go.
Worked perfectly and entirely from the tablet! I installed CM6.1 and I'm a bit upset at the lack way it looks, but then, its packed for smaller screens, so I understand. Thank you for the quick reply. I'm off to try TnT Lite now.

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

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

Galaxy S6 (SM-G920W8, BELL) has bricked and I need help.

Ok, I've been here on XDA for almost a year and until now I haven't had a problem I couldn't handle.
My Galaxy S6 (5.0.2) has been rooted since October 2015, it was May when I decided to Unroot and restore as a normal phone (I use Snapchat quite often and can't be used on a rooted phone). So July 9th, I decided that it was time for me to Root my phone again, and I did. I booted into TWRP and I'm sure everyone knows how long it takes to boot it into Recovery and back into normal mode, so I went deeper and tried switching where the USB is routed (or whatever). I switched it from (Guessing the name) NXT24 to USB-OTG (Which I've used to copy files to and from my laptop to the TWRP Boot which were mainly backups and ZIP Files.
Anyway, I've tried flashing 5.0.2, 5.1.1, and 6.0.2. I've pretty much exhausted all possible fixes and I need help. I've switched to the Moto G4 and Motorola is just... not good.. anyway, I would really appreciate any and all help you provide, thank you!
SiPhone1997 said:
Ok, I've been here on XDA for almost a year and until now I haven't had a problem I couldn't handle.
My Galaxy S6 (5.0.2) has been rooted since October 2015, it was May when I decided to Unroot and restore as a normal phone (I use Snapchat quite often and can't be used on a rooted phone). So July 9th, I decided that it was time for me to Root my phone again, and I did. I booted into TWRP and I'm sure everyone knows how long it takes to boot it into Recovery and back into normal mode, so I went deeper and tried switching where the USB is routed (or whatever). I switched it from (Guessing the name) NXT24 to USB-OTG (Which I've used to copy files to and from my laptop to the TWRP Boot which were mainly backups and ZIP Files.
Anyway, I've tried flashing 5.0.2, 5.1.1, and 6.0.2. I've pretty much exhausted all possible fixes and I need help. I've switched to the Moto G4 and Motorola is just... not good.. anyway, I would really appreciate any and all help you provide, thank you!
Click to expand...
Click to collapse
Stumbled upon this searching another thingy. How are You flashing the ROMs? Used Odin in fastboot with Stock ROM to start over?

Cleaning everything and starting over.

So...
When i got my phone i didnt even bother putting in the latest miui, i just flashed the latest CM13.1 and started working with it,
Since i got 2 phones, one for me and one for my brother, i used mine as a testbed while i did everything "by the book" for my brothers.
the thing is that now im getting bad battery life and overheating and i notice that even when doing a factory reset some stuff (like i have the keyboard in 3 different languages) gets carried over.
So how do i "clean house" and start over, a sterilization that would leave the phone totaly empty (with exception of recovery offcource, would like to be able to load a new rom) ?
Then again if i have to sideload a new recovery from adb/fastboot it wouldnt be the end of the world.
Have you tried in recovery to "format system"?
I think that it is one of the best ways to clean your phone, even if the deepest would be doing all the possible wipe in TWRP menu.
will try.

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