Just thought I would tell everybody about my experience. Be careful when flashing ROMs. I was on marshmallow 3.1.1 xdabbebs. On a vs985 by the way. Anyway tried to Flash Jasmine 9.0 again with the 9.1 update...did everything correctly...wipe dalvik cache cache data system...then went on to Flash 35b bootstack...from there flashed Jasmine along with the update then the moderate debloat zip...after that did a factory reset...THEN when I went to reboot the screen was black...no logo no both in but odd thing was I could hear that it was booted...black screen of death...attempted to get into download mode to do a tot back to 10b not ring able to see anything on the phone...tried to Flash and failed every time. So...I tried the kdz method...numerous fails...for 20 minutes...out of nowhere phone vibrates and kicks on...I go to settings and somehow it took the 24b file...don't know how...anyways I tried to tot from there...to 10b...fail fail fail...then I tried the one click root method...nope didn't work...so I did king root...that worked...I then did the autorec twrp method...it flashed it...I then installed twrp manager to get the latest recovery...I flashed that...that seemed good...went to reboot to recovery...I got a security error message...I pulled battery and tried to reboot...same message every time...I then did the power and volume down and managed to get into recovery...thank God...LUCKILY I had a backup of xdabbeb 3.1.1 Rom...restored and I'm back up and running...lol...I think my Rom flashing days are over...lol...anyway...careful guys
matt1285 said:
Just thought I would tell everybody about my experience. Be careful when flashing ROMs. I was on marshmallow 3.1.1 xdabbebs. On a vs985 by the way. Anyway tried to Flash Jasmine 9.0 again with the 9.1 update...did everything correctly...wipe dalvik cache cache data system...then went on to Flash 35b bootstack...from there flashed Jasmine along with the update then the moderate debloat zip...after that did a factory reset...THEN when I went to reboot the screen was black...no logo no both in but odd thing was I could hear that it was booted...black screen of death...attempted to get into download mode to do a tot back to 10b not ring able to see anything on the phone...tried to Flash and failed every time. So...I tried the kdz method...numerous fails...for 20 minutes...out of nowhere phone vibrates and kicks on...I go to settings and somehow it took the 24b file...don't know how...anyways I tried to tot from there...to 10b...fail fail fail...then I tried the one click root method...nope didn't work...so I did king root...that worked...I then did the autorec twrp method...it flashed it...I then installed twrp manager to get the latest recovery...I flashed that...that seemed good...went to reboot to recovery...I got a security error message...I pulled battery and tried to reboot...same message every time...I then did the power and volume down and managed to get into recovery...thank God...LUCKILY I had a backup of xdabbeb 3.1.1 Rom...restored and I'm back up and running...lol...I think my Rom flashing days are over...lol...anyway...careful guys
Click to expand...
Click to collapse
After getting Secure boot error you could have flashed Mr.bump.
Related
So I was on a early January build of Mahdi Roms. I decided today to update it. I was told to wipe everything flash the radio zip, cloudy rom. let it boot up then flash the new mahdi rom.
However, im on twrp 2.6.3. and when i flashed the radio and flashed the stock rom it booted up into twrp instead. I tried wiping and reflashing but it failed. I tried to reboot but it said my device isnt rooted and need to install SU so i swiped to continue however my device froze on the LG logo for about 10+ minute. So here I am still with no working phone for about 2 hours
any idea as to what to do?
EDIT: Well it's not solved, but in the process of trying to fix it I soft-bricked it so I forced myself to have to tot back to 4.2.2 using this thread: http://forum.xda-developers.com/showthread.php?t=2687768 . Now I'm simply trying to get it to OTA back to D80020y (on Cricket... using a prepaid AT&T sim to try and force an OTA... no luck).
I'm sure I'll end up facepalming as I've gotta be missing something simple.
I was running stock D80020y, rooted with a few exposed tweaks - nothing major. I flashed TWRP using Autorec, did a full "nandroid", then proceeded to install Blisspop 3.3 by doing the following steps:
A full wipe
Flashing LP_30d loki'd bootstack (my hunch is this is the problem)
Flashing the rom + gapps
I had lots of issues with it not recognizing my sim card and acting as if I had no service, despite the APN settings looking accurate. So I got back into recovery (had to install/run autorec again as I couldn't get into it from the rom), restored my EFS just in case, then did a full wipe and restored the nandroid - all of it.
The first time it booted up, it went through the update of every app and just hung on "starting apps". I let it go for a good 10 minutes before rebooting and it just hung at the logo prior to full boot. I got back into recovery and restored again, but no luck - it just hangs every time.
Is the bootstack my problem? I REALLY don't want to have to flash back to stock via kdz or tot as I'm on cricket and won't be able to OTA back to D80020y. Any input is appreciated!
I have been using CM12.1 on an LG G2 D802 and decided to upgrade the device to CM 13 today. As the device was running the stock 4.4 ROM before I initially switched to CM 12.1, I figured it would already have the Kitkat bootloader installed and proceeded to download the latest CM 13 nightly from the CM page as well the stock OpenGapps package. I then booted into TWRP (v2.6.3.3), wiped system, dalvik, data and cache and then flashed the ROM and the Gapps package which worked just fine.
However, when I selected "reboot system", the screen went black. I turned the phone off by pressing the power button. turned it on again and found that the LG logo flashes up for less than 1 second, then the screen goes black again. Gladly, I am still able to boot into TWRP. I then searched the forums, decided to try the latest Lollipop bootstack from this thread and reflashed the ROM and the Gapps package, but the problem still persits.
I am now thinking if my seriously outdated TWRP version is causing the problem, but I hesitate to update that (as it is basically the only working thing on the phone right now) without making sure that it really could be the problem.
Do you have any tips for me what could be the problem and how I can fix the phone?
Thank you very much!
Any help is appreciated
lg g2 bricked
YassinTP said:
Any help is appreciated
Click to expand...
Click to collapse
bro does ur phone goes in download mode? if yes flash tot. if not i will solve ur issue through teamviewer. dont worry it will be solved.
YassinTP said:
Any help is appreciated
Click to expand...
Click to collapse
to boot into system you need hybrid bootstacks, and definitiverly need thermal twrp 2.8.7.3
you could either do both. download twrp and bootstaclks the hybrid ones.
first update twrp if you want. but i recomend as it has thermal to control heat during installations
once you in twrp. wipe all. then reboot into recovery from recovery.
flash hybrid bootstacks then again reboot into recovery from recovery, and when you in twrp flash rom it should boot.
just remeber to reboot into recovery each time you flash twrp ot hybrids to take effect.
I've decided to unlock bootloader, get a custom recovery and root my new LG G6 H870, so I've downloaded Melina TWRP v321 and Magisk v16.
Unlocking went well, then I downloaded drivers, unlocked debugging, "adb reboot bootloader" -> "fastboot flash recovery twrp.img" -> unplug usb -> boot into twrp by pressing volume down + power (with a tap) -> some weird screen about encryption popped up, but I clicked through -> and then I proceeded to install Magisk straight away, cause this guide said it'd not let TWRP stick if I didn't. After that I tried to boot into system and start the real fun. But it booted me back into TWRP. Again and again.
From there, I've tried Wipe -> Factory Reset, Wipe -> Advanced Wipe -> Repair File System for Data and System, Wipe -> Format Data, Advanced -> Fix Contents, but it all ends with twrp boot... I'm completly lost at this point. I've flashed/rooted a few phones before, but this one... it's a real nightmare.
I've also tried flashing a stock kdz (the filename is "H87011i_00_EEO_GB_OP_0108.kdz" for anyone wondering) through LGUP and redoing this stuff, but I end up with the same result. Please advise how to get it working.
Did you use uppercut when you flashed the kdz file? This is needed to successfully flash back to stock.
Seems it didn't work correctly.
basicreece said:
Did you use uppercut when you flashed the kdz file? This is needed to successfully flash back to stock.
Seems it didn't work correctly.
Click to expand...
Click to collapse
Yes, I did flash through Uppercut (v1).
Since this thread started I flashed it once again, but this time I tried installing official TWRP v321. There was no weird encryption screen, but there were a lot of msgs (when installing magisk or doing a backup, for example) about being unable to unmount /system because it was being used. I did manage to install Magisk though and boot up the phone, but then when I tried installing Xposed, the phone went into another weird loop... but this time, it would get stuck on LG screen and it'd start heating up very fast. It stops heating when I restart using volume down + power into recovery. But I'm once again stuck... this is incredibly annoying, are aall LG phones like that?
How you installing xposed?
Install it via magisk module.
I had no issue.
Unlocked BL
Flashed Zefie TWRP (most stable and backups work)
Flashed fulmics
Flashed Magisk
Wiped cache and dalvik.
Reboot.
Works fine and flashed this over 15 times now no issues ever.
basicreece said:
How you installing xposed?
Install it via magisk module.
I had no issue.
Unlocked BL
Flashed Zefie TWRP (most stable and backups work)
Flashed fulmics
Flashed Magisk
Wiped cache and dalvik.
Reboot.
Works fine and flashed this over 15 times now no issues ever.
Click to expand...
Click to collapse
Did you also have that weird encryption message when flashing Zefie TWRP? Could you be more specific about your way? As in, you wiped cache/dalvik only once or after every flash? Did you wipe anything else? And yeah, I've just downloaded Fulmics and I'm at the installation screen, but I clicked System Information and it says my Storage Size is 5417MB with 104MB free... it reads SDCard Size correctly though. Should I be worried?
Starting from fresh, out the box.
Unlocked bootloader.
Installed Zefie TWRP.
Then added fulmics zip to sdcard.
Flashed zip, followed on screen instructions.
Wiped dalvik and cache.
Rebooted.
Takes a few minutes.
Boots up and done.
Magisk was packed into fulmics when installed.
I do NOT touch xposed. Too many issues plus I need safetynet for Google pay.
Yeah, I pretty much flashed stock firmware back and then followed basicreece instructions, along with flashing Fulmics, but I've got the 'official' Twp (v321). And everything's working so far, but I didn't touch Xposed so far though since Fulmics had pretty much all I wanted from Xposed. Word of advice for future readers though: don't bother staying on stock, too many problems. Fulmics is basically stock, but with some really neat options, and a ton of bugs and problems less.
I am stuck at encryption failed when I flash stock oreo rom. I tried formatting data using twrp and flashed no encryption file as well but nothing works.:crying::crying::crying:
I just want to use the stock oreo rom again with root.
Pls help:crying:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
jl10101 said:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
Click to expand...
Click to collapse
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Deadmeat03 said:
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Click to expand...
Click to collapse
Odd. If I had to guess anything, it would be that not all the partitions were flashed when going from Nougat to Oreo.
I once flash a Nougat ROM from an Oreo ROM and I had the same encryption issue and lost everything.
That was the last time I would trust myself again and not do a backup.
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Prowler_gr said:
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Click to expand...
Click to collapse
I tried that as well. With stock recovery is says data is corrupted and doesn't do anything. I think it might be a problem with patched lg up because when i use normal lg up to flash oreo it works. But I cant root then.
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
In the same boat as OP
scottyrick said:
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
Click to expand...
Click to collapse
Hi
Looking for a way to keep TWRP and root ... any help appreciated
I've got a US996 with the same issue as the op. I have the latest TWRP 3.3.1-0. The phone was working fine until I upgraded twrp but I might have done a mistake resetting phone outside of twrp.
I can still get back into twrp but I haven't been able to install zip files without getting that decryption unsuccessful message when booting to system.
When getting back into TWRP using hardware buttons sometimes there is a prompt asking "keep system read only?" which I never chose and swipe to allow modification. I think this happens after
I pull the battery after getting the decryption unsuccessful message. There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
...but if my phone is a us996 and is still
unlocked, would it matter if I did select it? Wouldn't I be able to reinstall twrp using adb again on a computer after Oreo is reinstalled?
To do Prowler_gr's suggestion which guide do I follow (sounds like I should do the second option)
"Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track... "
1-[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix) to use lgup
or this guide
2-Ultimate guide to unbrick LG V20(Only Variants with .KDZ)[No OS Firmware Update Loop]
Thank you for any guidance on this...
There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
Click to expand...
Click to collapse
Don't blame me if this goes wrong but I'm pretty much 100% certain that you mush press the rest button. This has happened to me a few times I'm sure. You won't loose twrp. Whatever resetting goes on in the background I don't think it's an actual Factory Reset.
Edit: Just to be clear you taking about a white screen with I think in dark blue or black text ENCRYPTION UNSUCCESSFUL and something like "reset phone" option directly under it, on the upper half of the screen?
Hi ezzony
Yes you are thinking of the right decryption unsuccessful page. I get it when booting to system
after installing Oreo and magisk 19 and having wiped everything (format data too). I will get the exact wording of it tonight
Thanks!
downgrade twrp i has same prob twrp 3.3.1 gives issues
ghet2rockuu said:
downgrade twrp i has same prob twrp 3.3.1 gives issues
Click to expand...
Click to collapse
Hi ghet2rockuu
I downgraded twrp and that got it working Thank You! see also Phoenix591 thread [Recovery][Unofficial for the moment]TWRP 3.3.1-0 : 2019-05-17 #625
Thank You !