I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Dileter said:
I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Click to expand...
Click to collapse
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
Yes I am rooted and I tried flashing this ROM http://forum.xda-developers.com/lg-g5/development/unofficial-cyanogenmod-14-1-lg-g5-h850-t3494001
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
I also dont really care if I lose photos or anything I already got all of them saved on my pc before I even started rooting the damn thing. I do need to ask tho how do you dirty flash and Do i just flash twrp normally since im already in it or ??? As I said im rlly new to this
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
DidierMoulin said:
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
Click to expand...
Click to collapse
Okay thanks a lot I will see if Any of it helps.
Please report.
DidierMoulin said:
Please report.
Click to expand...
Click to collapse
UPDATE I fixed it I just downgraded to the 2nd to lates version of twrp and it booted normally. Now I regret flashing the pixel one XDD If you have any idea for a good custom rom tell me Thanks for the help it actually helped a lot gave me the idea to downgrade the twrp recovery.
What you mean by pixel one xxd?
DidierMoulin said:
What you mean by pixel one xxd?
Click to expand...
Click to collapse
Its a 7.1.1 android rom from the google pixel
Dileter said:
Its a 7.1.1 android rom from the google pixel
Click to expand...
Click to collapse
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Pphish20 said:
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Click to expand...
Click to collapse
What he asked [emoji32]
It's happened to me too! Like three times lol. Just use UpperCut / LG UP to flash the latest nougat rom. That will fix the issue. You will need to re-root after that. There are instructions in this forum that tell how to do all of that. Good luck
Well and don't flash a ROM which is not for your device...
Related
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Please give more details on how you flash it.
Enviado do meu GT-I9305 utilizando o Tapatalk now Free
nikolav75 said:
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Click to expand...
Click to collapse
!!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!!
nikolav75 said:
Hi, all!
I have that annoying problem with all the 4.3 ROM I've tried with no exception. Everything is fine until the first reboot. Then it's stuck on the first Galaxy SIII boot logo. I'm using TWRP - the latest version if it matters.
I always wipe everything first.
Click to expand...
Click to collapse
If you did all required wipes and followed the instructions did you try a different recovery? I read in the SB thread for example of people having issues with TWRP
Sent from my Nexus 7 (2013)
I am sorry for the wrong section. May I ask some to move it to Q&A?
I always wipe data, cash, dalvik cash, system. Then install the ROM and gapps...
After the restart I set up the google account and etc. And after the first restart the phone freezes. That's all.
I'll try with different recovery.
PS. I've just tried CWM recovery 6.0.3.3. and Omega AOSP v9. Still the same.
Try cwm 6.0.3.6 and after you install the rom and after its set up go to recovery and factory reset
nikolav75 said:
I am sorry for the wrong section. May I ask some to move it to Q&A?
I always wipe data, cash, dalvik cash, system. Then install the ROM and gapps...
After the restart I set up the google account and etc. And after the first restart the phone freezes. That's all.
I'll try with different recovery.
PS. I've just tried CWM recovery 6.0.3.3. and Omega AOSP v9. Still the same.
Click to expand...
Click to collapse
That's strange, I run Philz recovery and every 4.3 flash till now went through without issue.
Sent from my GT-I9300 using xda app-developers app
I tried all the recoveries I could find. Including Philz. Still the same.
And something else strange. I installed CWM, CWM, touch and Philz and with them I made backups. After restoration of the backup the phone freezes. I also tried to install Omega 49 and the installation goes OK, but freezes before the first start-up.
The only solution was to install manually TWRP (Odin) to restore some of my old backups. I'm beginning to think that there is something wrong with my phone. It's black if it is important.
Suggest total wipe of phone install your stock rom and test
Hi,
I just want to say I'm also having the same problem.
Started using TWRP with full wipe, same issue on 4.3 and no issues on 4.2.
On latest CWM same problem and 4.2 wont even pass the first boot on Samsung logo.
Also had to use Odin to get back on TWRP and flash a 4.2 rom again.
Anyway there is one more thing I would like to try but haven't had the chance to do so, is installing the latest modem and ril. But I'm kind skeptic about that currently because there is also some risks and my S3 is my daily driver.
Don't change the ril on any custom as you stand a big chance of breaking the calls and Tex's. Modem yes but not ril. Do change to cwm and retry.
andrewwright said:
Don't change the ril on any custom as you stand a big chance of breaking the calls and Tex's. Modem yes but not ril. Do change to cwm and retry.
Click to expand...
Click to collapse
Thanks for the info, I was planning to read more about it before I would make an attempt. BTW already tried CWM that only made things worse, couldn't flash any rom without getting stuck on samsung screen.
bla166 said:
Thanks for the info, I was planning to read more about it before I would make an attempt. BTW already tried CWM that only made things worse, couldn't flash any rom without getting stuck on samsung screen.
Click to expand...
Click to collapse
You are doing a full wipe?. System and data is the main thing to wipe not just factory reset. So go into mounts and storage and format data,system and cache there then flash the rom /gapps.
andrewwright said:
You are doing a full wipe?. System and data is the main thing to wipe not just factory reset. So go into mounts and storage and format data,system and cache there then flash the rom /gapps.
Click to expand...
Click to collapse
yes tried that, also used the mega wipe zip thing
Start fresh and flash stock with Odin then try again after you root and install cwm.
andrewwright said:
Start fresh and flash stock with Odin then try again after you root and install cwm.
Click to expand...
Click to collapse
Tried to go stock and flashed a 4.3 rom again that fixed my problem. =)
Thanks! :good:
I'll try it too. And one stupid question. Where do I find a stock ROM? I never did it before
nikolav75 said:
I'll try it too. And one stupid question. Where do I find a stock ROM? I never did it before
Click to expand...
Click to collapse
http://www.sammobile.com/
Thank you!
But nothing helped. I flashed a stock ROM, with Odin. First I tried with TWRP, and the second time (again after flashing stock) with CWM recovery. I tried two 4.3 ROMs. They both can't boot after the first reboot.
nikolav75 said:
Thank you!
But nothing helped. I flashed a stock ROM, with Odin. First I tried with TWRP, and the second time (again after flashing stock) with CWM recovery. I tried two 4.3 ROMs. They both can't boot after the first reboot.
Click to expand...
Click to collapse
Hi, I think I did the following steps to get it working on my device.
1. Flash stock with odin
2. Hard reset
3. Boot up and finish first run menus
4. Flash twrp with odin
5. Format data with twrp
6. Flash 4.3 rom
Hi Guys,
Need some help here. Got a weird problem with my OpX. I have a habit of trying each and every rom on our forum. So, as usually after trying a rom for a day or two I used to revert back to my fav rom. So, I'm familiar with all those flashing stuffs. The problem right now is that I'm not able to boot into any 6.0.1 Rom that I flash. No matter what I do it doesn't boot, just stuck at bootloop. I'm just tired trying out each and every rom out on the developer's section. Wiped completely, even tried downloading the rom multiple times. Tried all type of flashing, like with gapps, without gapps, with gapps, with SU. Tried all possible combination just to end in vain . None of the rom boot into HS, it's just stuck in the bootloop .
However, I've no problem in flashing OOS, H2OS, Color OS, Cm12.1 rom. It flashes without any issues and works fine.
Any help would be appreciated. Thanks in advance
Did you perform a full wipe ( sys/data/cache) when you changed android version (5.1 --> 6.0.1)
Nexx_ said:
Did you perform a full wipe ( sys/data/cache) when you changed android version (5.1 --> 6.0.1)
Click to expand...
Click to collapse
Yes, I even wiped the internal.
Anyone?
prarun2030 said:
Anyone?
Click to expand...
Click to collapse
Maybe you're using F2FS ?
Nexx_ said:
Maybe you're using F2FS ?
Click to expand...
Click to collapse
No bro, not using it. Did a dirty flash over OOS 5.1.1 by wiping data alone and it booted up. Still it doesn't boot if i do a complete wipe..
Flash this recovery on the community build: http://forum.xda-developers.com/devdb/project/dl/?id=20236
And then flash the super SU file via recovery:
https://www.androidfilehost.com/?fid=24591000424944601
Let me know if this works or you need any help ?
Did any1 tried??
Sent from my ONE E1003 using XDA-Developers mobile app
From other posts in other topics it seams that it's the only twrp version that installs OOS 3.1.1
Sent from my ONE E1001
trendchanger said:
Did any1 tried??
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried, and I can confirm it worked.
The only thing is that I can't get xposed installer to work properly. When I install it (v86 sdk23 arm) , every time that I tap on recent apps button, system ui crashes, so, I flashes the Uninstaller zip, and everything went well. But I miss xposed, if anybody has a solution, I would appreciate it
yes this is working
Jab_ said:
I tried, and I can confirm it worked.
The only thing is that I can't get xposed installer to work properly. When I install it (v86 sdk23 arm) , every time that I tap on recent apps button, system ui crashes, so, I flashes the Uninstaller zip, and everything went well. But I miss xposed, if anybody has a solution, I would appreciate it
Click to expand...
Click to collapse
Using the latest Blu spark twrp from his thread I flashed v86 sdk23 arm.zip and didn't have any issues on 3.1.1.
Exodusche said:
Using the latest Blu spark twrp from his thread I flashed v86 sdk23 arm.zip and didn't have any issues on 3.1.1.
Click to expand...
Click to collapse
Maybe the problem is not xposed itself, maybe the issue is related to an specific module. I'll try one by one tomorrow and see what happens, thank you!
Just delete the . rar part. This one worked for me I think your right though maybe bad file.
Exodusche said:
Just delete the . rar part. This one worked for me I think your right though maybe bad file.
Click to expand...
Click to collapse
I know what the problem was. My xposed zip was correct. As I thought, it was because of a module. "Android N-fy", in recents, I just had to uncheck quick switch and change no recent image and that was it. I don't know if that module is optimized for this oos especific build, because in settings of the phone, the module does not change as much as in lollipop oos. Thank you tho
I have latest official TWRP rn on OOS 2.2.2.. Should I just flash(dirty flash or clean flash after wiping) it normally? or revert to stock, flash the ROM and then use fastboot to flash recovery by bluspark?
Worked fine. Thanks OP.
bootloop when flashed supersu zip on oos 3.1.1 with twrp v41 recovery
i just saw that you have to use modified zip , so no other file to flash
thanks and sorry for not reading properly
TarushS said:
bootloop when flashed supersu zip on oos 3.1.1 with twrp v41 recovery
i just saw that you have to use modified zip , so no other file to flash
thanks and sorry for not reading properly
Click to expand...
Click to collapse
Oh lol, glad this helped
StraightEdgeKid said:
Worked fine. Thanks OP.
Click to expand...
Click to collapse
Np?
Sachin7843 said:
I have latest official TWRP rn on OOS 2.2.2.. Should I just flash(dirty flash or clean flash after wiping) it normally? or revert to stock, flash the ROM and then use fastboot to flash recovery by bluspark?
Click to expand...
Click to collapse
What exactly are you looking to do?
marwan2704 said:
What exactly are you looking to do?
Click to expand...
Click to collapse
I want to get OOS 3.1.1 and also be able to revert back to OOS 2.2.2 if I experience any bugs or don't like it so, I want to know when should I flash TWRP by bluspark?
Sachin7843 said:
I want to get OOS 3.1.1 and also be able to revert back to OOS 2.2.2 if I experience any bugs or don't like it so, I want to know when should I flash TWRP by bluspark?
Click to expand...
Click to collapse
Make sure you have both .zip files on your phone, clean flash 3.1.1 then boot it up. If you don't like it, you can go back to 2.2.2 via stock recovery anytime. You don't even need twrp unless you want to root, install Xposed or backup.
might be a bit off-topic but...
i was coming from sultans cm13 build - flashed stock recovery - wiped system - installed the community build.
So far so good
System works fine, but wifi drains system like hell (37% usage)
So i installed bluespark twrp and wanted to wipe cache & dalvik/art at once
-> initially i got an error -> "can´t mount /cache - invalid argument" (or so) - tried only to wipe cache and then it worked on the 3rd attempt...
But - after restarting only 12 Apps are "optimized", altough i have 100+ apps installed.... so i expect some filesystem/partition issue
Did you ever have this behaviour ?
I´m thinking about to do a full wipe in twrp and reinstall the community build -> other suggestions ?
error23 said:
i was coming from sultans cm13 build - flashed stock recovery - wiped system - installed the community build.
So far so good
System works fine, but wifi drains system like hell (37% usage)
So i installed bluespark twrp and wanted to wipe cache & dalvik/art at once
-> initially i got an error -> "can´t mount /cache - invalid argument" (or so) - tried only to wipe cache and then it worked on the 3rd attempt...
But - after restarting only 12 Apps are "optimized", altough i have 100+ apps installed.... so i expect some filesystem/partition issue
Did you ever have this behaviour ?
I´m thinking about to do a full wipe in twrp and reinstall the community build -> other suggestions ?
Click to expand...
Click to collapse
Sounds like you forgot to wipe data. Wipe system, data, cache and just flash 3.1.1. As for wifi drain it's not real and happens when you have wifi scanning on under location. Turn it off, reset network settings under backup/reset. Now reboot and should be gone. Turning off and rebooting might be enough but doesn't hurt to add network reset. Next cycle after reboot and full charge should be clean.
Exodusche said:
As for wifi drain it's not real and happens when you have wifi scanning on under location. Turn it off, reset network settings under backup/reset. Now reboot and should be gone. Turning off and rebooting might be enough but doesn't hurt to add network reset. Next cycle after reboot and full charge should be clean.
Click to expand...
Click to collapse
It's not the place, but I can confirm that it didn't work for me. I still have the drain from time to time.
And if I don't have the Wifi drain I have a service Google Play service drain (33% for today's charge for example...).
And sometimes, I even had the wifi drain with Wifi completly switched off...
Hello guys, i have a problem, i tried to install RR 5.7.4 via TWRP ZCX, but the first boot asks me for a password
PS: I tried flashing RR while i was in MIUI 8 global stable
Factory reset in TWRP.
using TWRP filemanager go to /data/system
Delete all .key files and also delete locksettings.db file.
Reboot enjoy
Guys, my TWRP ZCX crashed, it is stuck on its logo
theoneofgod said:
Factory reset in TWRP.
Click to expand...
Click to collapse
HI, I am also facing same issue. For every boot I am being asked to draw the pattern. Factory reset in TWRP will not effect my current rom and data stuff ????
[email protected] said:
HI, I am also facing same issue. For every boot I am being asked to draw the pattern. Factory reset in TWRP will not effect my current rom and data stuff ????
Click to expand...
Click to collapse
Yes it will.
Do what's said here https://forum.xda-developers.com/showpost.php?p=70354200&postcount=3
theoneofgod said:
Yes it will.
Do what's said here https://forum.xda-developers.com/showpost.php?p=70354200&postcount=3
Click to expand...
Click to collapse
Thanks for the info
Can you explain what is this feature? because I didn't get this when i am in miui 8. But as soon as I flashed ZCX TWRP and installed RR I started getting this. Thanks in Advance
[email protected] said:
Thanks for the info
Can you explain what is this feature? because I didn't get this when i am in miui 8. But as soon as I flashed ZCX TWRP and installed RR I started getting this. Thanks in Advance
Click to expand...
Click to collapse
What he suggested will delete the lockscreen password/passcode etc so you can boot the phone without any prompts. You do this within TWRP.
theoneofgod said:
What he suggested will delete the lockscreen password/passcode etc so you can boot the phone without any prompts. You do this within TWRP.
Click to expand...
Click to collapse
Many thanks guys..You are quite supportive :angel:
[email protected] said:
Thanks for the info
Can you explain what is this feature? because I didn't get this when i am in miui 8. But as soon as I flashed ZCX TWRP and installed RR I started getting this. Thanks in Advance
Click to expand...
Click to collapse
this is because force encryption of internal storage. do a factory reset in twrp after flashing lazy flasher. and if its stuck on twrp boot logo thn u have to flash latest fastboot dev rom through miflash. thn unlock bootloader thn flash twrp thn flash lazy flasher thn factry reset. .
hope it helps
smustafasms said:
this is because force encryption of internal storage. do a factory reset in twrp after flashing lazy flasher. and if its stuck on twrp boot logo thn u have to flash latest fastboot dev rom through miflash. thn unlock bootloader thn flash twrp thn flash lazy flasher thn factry reset. .
hope it helps
Click to expand...
Click to collapse
oh in that case, should I have to factory reset everytime I flash a rom through my TWRP? I use ZCX TWRP, so Lazy flasher is not required after rom flashing right?
you just need it once . to decrypt your storage
[email protected] said:
oh in that case, should I have to factory reset everytime I flash a rom through my TWRP? I use ZCX TWRP, so Lazy flasher is not required after rom flashing right?
Click to expand...
Click to collapse
In the information about the ZCX TWRP I found below:
ZCX TWRP : http://forum.xda-developers.com/redm...persu-t3462448
- Based on official TWRP 3.0.2-0
- Patches boot.img automatically (Removes dm-verity flag)
- Disables forced encryption
Should I have to tweak anything in TWRP settings to remove this dm-verify flag everytime?
[email protected] said:
In the information about the ZCX TWRP I found below:
ZCX TWRP : http://forum.xda-developers.com/redm...persu-t3462448
- Based on official TWRP 3.0.2-0
- Patches boot.img automatically (Removes dm-verity flag)
- Disables forced encryption
Should I have to tweak anything in TWRP settings to remove this dm-verify flag everytime?
Click to expand...
Click to collapse
no ,but you should flash lazy flasher once . to decrypt ur internal storage. dm-verity flag does nothing to decrypt storage
smustafasms said:
no ,but you should flash lazy flasher once . to decrypt ur internal storage. dm-verity flag does nothing to decrypt storage
Click to expand...
Click to collapse
Thank you very much :angel:
gulshanstrider said:
using TWRP filemanager go to /data/system
Delete all .key files and also delete locksettings.db file.
Reboot enjoy
Click to expand...
Click to collapse
I tried it. Earlier i did not have any issue even if i install custom rom on my Redmi note 3. But today i thought of trying Pure Nexus *Substratum* rom. And on the first boot it asked me to enter password. though i have never kept password for my mobile, i tried all the passwords that i remember, which didnt solve my issue. then saw ur reply and tried it, and still it didnt work for me. Any other way?:crying:
AnilLonely said:
I tried it. Earlier i did not have any issue even if i install custom rom on my Redmi note 3. But today i thought of trying Pure Nexus *Substratum* rom. And on the first boot it asked me to enter password. though i have never kept password for my mobile, i tried all the passwords that i remember, which didnt solve my issue. then saw ur reply and tried it, and still it didnt work for me. Any other way?:crying:
Click to expand...
Click to collapse
Are you coming from MIUI? If so then MIUI encrypts the data partition, hence the new ROM asking for a password.
Before you install the ROM, you must "format data" on wipe in TWRP, this is different from wipe data.
Note that this will delete all your data obviously.
kimxk said:
Are you coming from MIUI? If so then MIUI encrypts the data partition, hence the new ROM asking for a password.
Before you install the ROM, you must "format data" on wipe in TWRP, this is different from wipe data.
Note that this will delete all your data obviously.
Click to expand...
Click to collapse
Yes i am coming from MIUI. I had done that But no use. Tried what ever that has been discussed in the following thread as well, but that also did not work for me.
http://en.miui.com/thread-324522-1-1.html
Posted a thread on MIUI forum as well. Waiting for some sort of help. Earlier i was able to install Custom Rom's without any issue, (though i am coming from MIUI), but now what ever may be the rom that i am trying to flash, the first boot is asking me for password. Unable to understand what is the issue.
AnilLonely said:
Yes i am coming from MIUI. I had done that But no use. Tried what ever that has been discussed in the following thread as well, but that also did not work for me.
http://en.miui.com/thread-324522-1-1.html
Posted a thread on MIUI forum as well. Waiting for some sort of help. Earlier i was able to install Custom Rom's without any issue, (though i am coming from MIUI), but now what ever may be the rom that i am trying to flash, the first boot is asking me for password. Unable to understand what is the issue.
Click to expand...
Click to collapse
Are you sure that you used "format data"?
Wipe data doesn't remove the encryption.
See this page for an image:
http://xiaomitips.com/media/2016/07/Format-Data-TWRP.png
kimxk said:
Are you sure that you used "format data"?
Wipe data doesn't remove the encryption.
See this page for an image:
http://xiaomitips.com/media/2016/07/Format-Data-TWRP.png
Click to expand...
Click to collapse
Perfect. Worked bro. Thanks a lot for the help. I was wiping cache,and internal storage. Now only came to know this. :highfive:
Typical disclaimer, etc etc.
You nuke your phone, I'm not paying for it
Thanks to @zefie for converting the kdz to a zip.
The zip
The anti-root removal
I flashed the zip in TWRP, rebooted to the OS, and was unrooted.
Reboot into the bootloader, and flashed TWRP.
Rebooted into recovery, flashed the lucye anti root removal, then rebooted into recovery again, and flashed Magisk.
Phone has been fine since Thursday.
Did you flash this dirty or clean?
I flashed it. Works GREAT. Dirty flashed.
Here's what I did...
-Flashed this zip
-Flashed Eliminator74 twrp image https://forum.xda-developers.com/lg-g6/development/twrp-t3828254 (you'll need to change from .zip to .img in TWRP)
-Rebooted to recovery
-Flashed antiroot removal zip
-rebooted to recovery
-Flashed magisk
-rebooted to system
-be patient
Can you please post a link to eliminator74 twrp build? I'm not sure if I have that one...
Link to his thread
jjohn7293 said:
Can you please post a link to eliminator74 twrp build? I'm not sure if I have that one...
Click to expand...
Click to collapse
Here's a link to his thread https://forum.xda-developers.com/lg-g6/development/twrp-t3828254
monark88 said:
I flashed it. Works GREAT. Dirty flashed.
Here's what I did...
-Flashed this zip
-Flashed Eliminator74 twrp image https://forum.xda-developers.com/lg-g6/development/twrp-t3828254 (you'll need to change from .zip to .img in TWRP)
-Rebooted to recovery
-Flashed antiroot removal zip
-rebooted to recovery
-Flashed magisk
-rebooted to system
-be patient
Click to expand...
Click to collapse
Dirty from 21B worked fine for me
Dirty flash from 20A worked perfectly.
FYI: This ROM has the recovery image removed, so if you already have TWRP, flashing this won't remove TWRP. No need to reinstall TWRP.
I actually started having bad idle drain. Flashed LOS for now, will go back to stock soon. If anyone else notices idle drain, please do let us know.
Thank you!
Only wiped caches
Dirty flashed over 20A
Reboot to recovery
Flashed anti root removal tool
Reboot to recovery
Flashed Magisk 17.3
Wiped caches again
Reboot to system
Showed Android is updating screen
All is well so far!
Still running 17A [rooted]... think dirty flashing this will be alright? Been looking for a good time to update.
Coming from 20A, battery life has been about the same- maybe even a bit better. All's well.
MetalMan2 said:
Still running 17A [rooted]... think dirty flashing this will be alright? Been looking for a good time to update.
Click to expand...
Click to collapse
Go for it. Be sure to install Magisk for root. SuperSU (if you happen to be using it) doesn't work anymore.
gl;hf
BeardKing said:
Coming from 20A, battery life has been about the same- maybe even a bit better. All's well.
Go for it. Be sure to install Magisk for root. SuperSU (if you happen to be using it) doesn't work anymore.
gl;hf
Click to expand...
Click to collapse
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
MetalMan2 said:
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
Click to expand...
Click to collapse
Good to hear. :good:
US997 14a to 21c (Keeping Root)
I'm using the US997 still on 14a (rooted, TWRP installed) would I need to (CLEAN) flash up to 17a and then the 21c? After that flash the anti-root and flash an updated version of Magisk? (currently stuck on v16.4) Can't find my stock boot image to update. Only got the phone back in October and stopped all updates before I unlocked the bootloaded, installed TWRP and used Magisk to get root. I had a hard time finding a version of TWRP with a kernel that worked for my phone (Melina v3.2.1-0) would I have to update that also? Was waiting to see the highest update I could get without losing root. Anyone done this? Any help would be greatly appreciated.
My wife and I both have G6 phones. On mine, I dirty flashed this over 20A with absolutely no problem. My sequence was: flash Eliminator74 TWRP, reboot to recovery, flash 21C zip, reboot to recovery, flash lucye anti-root, reboot to recovery, flash Magisk, wipe cache and Dalvik, reboot to system. I'm guessing I really didn't need those extra reboots but it felt safer. Phone is perfectly stable.
On my wife's phone it was another matter. Her data partition was encrypted, due to the phone having been reimaged by LG during warranty repair. I'd rooted it but never decrypted it. None of the default ways to decrypt it worked, so I was forced to format /data. I thought that would do it, but the resulting installation was unstable, and wouldn't get through setup successfully without continually looping, freezing, and returning to start. Finally I realized it was probably flashing over the LG factory image that caused the problem. I wiped /system and started over, and had much better results.
LPMatt said:
Thank you!
Only wiped caches
Dirty flashed over 20A
Reboot to recovery
Flashed anti root removal tool
Reboot to recovery
Flashed Magisk 17.3
Wiped caches again
Reboot to system
Showed Android is updating screen
All is well so far!
Click to expand...
Click to collapse
MetalMan2 said:
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
Click to expand...
Click to collapse
So I tried this coming from 17A.
When I reboot to recovery on the first go I have the Oreo bootloader screen and it goes into the white reset menu. All encryption is enabled again.
I have to fastboot bootloader, install TWRP recovery, wipe/format and then restore my 17A to recover the phone.
What steps did you take MetalMan2?
Malezar said:
So I tried this coming from 17A.
When I reboot to recovery on the first go I have the Oreo bootloader screen and it goes into the white reset menu. All encryption is enabled again.
I have to fastboot bootloader, install TWRP recovery, wipe/format and then restore my 17A to recover the phone.
What steps did you take MetalMan2?
Click to expand...
Click to collapse
This probably won't help, but are you using this version of TWRP?
BeardKing said:
This probably won't help, but are you using this version of TWRP?
Click to expand...
Click to collapse
Yep. Just downgraded the bootloader back to 17a through it.
Malezar said:
What steps did you take MetalMan2?
Click to expand...
Click to collapse
I exactly followed LPMatt's list which you quoted.
Still no problems. Pretty sure the battery life is less than 17A, but I think we all know that and for me it's "good enough".
How to remove root checker?