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...
Related
Hi,
I was running BeanStalk-4.4.270 03/18/14 by zymphad. Im not sure what the kernel was.
I tried flashing the ROM by ronasimi in this thread.
The ROM that i picked was cm-11-20140817-UNOFFICIAL-geeb & the kernel was gbx-kernel-lights-CM11.0-CAF.zip. Apart from this i picked the Google Stock package of PA GApps from here.
For flashing i did the following :-
1. backed up all my apps using TB from BeanStalk.
2. loaded the ROM, the kernel & GApps zip files into a folder on my sdcard.
3. rebooted into recovery(TWRP 2.6.xx), backed up my original ROM and lined up all the three flashable zips and flashed them. (The flash was successful)
4. Then i rebooted into system. But after reaching the home screen, i was getting errors "Unfortunately, the process com.android.systemui has stopped" & "Unfortunately, the process com.android.phone has stopped". I remembered it might be because i forgot to wipe dalvik & cache.
5. I again rebooted into recovery, wiped dalvik & system cache and tried booting into system. It was still giving the same issues.
6. I tried restoring my old ROM's backup. Surprisingly even that wouldn't solve the issue.
7. So i again flashed the CM11 ROMs. But this time, the boot process is getting stuck at the boot animation.
My Qs are as follows:-
1. Did i miss anything or do something that is not recommended (or maybe even dangerous)?
2. What should be my next step in resolving this issue?
Any help appreciated.
gautam_k said:
Hi,
I was running BeanStalk-4.4.270 03/18/14 by zymphad. Im not sure what the kernel was.
I tried flashing the ROM by ronasimi in this thread.
The ROM that i picked was cm-11-20140817-UNOFFICIAL-geeb & the kernel was gbx-kernel-lights-CM11.0-CAF.zip. Apart from this i picked the Google Stock package of PA GApps from here.
For flashing i did the following :-
1. backed up all my apps using TB from BeanStalk.
2. loaded the ROM, the kernel & GApps zip files into a folder on my sdcard.
3. rebooted into recovery(TWRP 2.6.xx), backed up my original ROM and lined up all the three flashable zips and flashed them. (The flash was successful)
4. Then i rebooted into system. But after reaching the home screen, i was getting errors "Unfortunately, the process com.android.systemui has stopped" & "Unfortunately, the process com.android.phone has stopped". I remembered it might be because i forgot to wipe dalvik & cache.
5. I again rebooted into recovery, wiped dalvik & system cache and tried booting into system. It was still giving the same issues.
6. I tried restoring my old ROM's backup. Surprisingly even that wouldn't solve the issue.
7. So i again flashed the CM11 ROMs. But this time, the boot process is getting stuck at the boot animation.
My Qs are as follows:-
1. Did i miss anything or do something that is not recommended (or maybe even dangerous)?
2. What should be my next step in resolving this issue?
Any help appreciated.
Click to expand...
Click to collapse
Flash TWRP 2.7.1 or Philz's touch CWM
than do a clean install
Wipe data and Format system
Flash any ROM (here CM 11 ) and Gapps
Flash proper kernel ( for CM 11 old Gprij-X kernel or neighborhood kernel)
Wipe cache and delvick cache
reboot profit
For more info :
ShoaibAhmed said:
Flash TWRP 2.7.1 or Philz's touch CWM
than do a clean install
Wipe data and Format system
Flash any ROM (here CM 11 ) and Gapps
Flash proper kernel ( for CM 11 old Gprij-X kernel or neighborhood kernel)
Wipe cache and delvick cache
reboot profit
For more info :
Click to expand...
Click to collapse
I tried flashing using TWRP but the flash failed. then I saw the video and thought of giving philz touch cwm a try. it worked like a charm. Thanks a lot for the help. For kernel I flashed gprojx-kernel-lights-CM11.0-CAF-20140414.zip. Everything seems to be working now. Only thing is that I can't seem to turn off NFC. Every time I deselect the check box, go somewhere else and come back, the NFC check box is already checked.
Any tips on that? It's eating up my battery
gautam_k said:
I tried flashing using TWRP but the flash failed. then I saw the video and thought of giving philz touch cwm a try. it worked like a charm. Thanks a lot for the help. For kernel I flashed gprojx-kernel-lights-CM11.0-CAF-20140414.zip. Everything seems to be working now. Only thing is that I can't seem to turn off NFC. Every time I deselect the check box, go somewhere else and come back, the NFC check box is already checked.
Any tips on that? It's eating up my battery
Click to expand...
Click to collapse
Reboot once and then try to turn off NFC , it will work.
ShoaibAhmed said:
Reboot once and then try to turn off NFC , it will work.
Click to expand...
Click to collapse
Awesome! Thanks a lot man.
One last Q p)- I spent almost 30mins combing through settings but I couldn't find a 3G/2G switch. Is it hidden somewhere or it doesn't exist yet in CM11?
gautam_k said:
Awesome! Thanks a lot man.
One last Q p)- I spent almost 30mins combing through settings but I couldn't find a 3G/2G switch. Is it hidden somewhere or it doesn't exist yet in CM11?
Click to expand...
Click to collapse
Settings--->Mobile networks--->Prefered network type--> change it from "LTE" to 2G/3G
ShoaibAhmed said:
Settings--->Mobile networks--->Prefered network type--> change it from "LTE" to 2G/3G
Click to expand...
Click to collapse
i am actually looking for a shortcut for the same in notification draweer or quick settings pulldown...apologies for not making it clear before.
gautam_k said:
i am actually looking for a shortcut for the same in notification draweer or quick settings pulldown...apologies for not making it clear before.
Click to expand...
Click to collapse
Found the shortcut in Settings> Notification Drawer> Quick settings panel> Tiles & layout> Network mode
For some reason i was thinking that this will lead me to the GSM/WCDMA switch.
Ok , Im running CM 13 i9300 and it worked so well except the camera. I always got the error "Can't connect to camera" . So I was trying to fix that problem and I found couple of solution . The solution need an app that requires SuperSU permission . And It was kinda weird because there's no "permission asking" popup from SuperSU. So I open SuperSU and it told me to update SuperSU binary file. So I tried to update it and it failed. So I tried to update it manually but I found other thing which is to flash the latest version of SuperSU direct from chainfire website. I deleted the old SuperSU (The one that needs to be updated) and I flashed the new SuperSU zip and wipe dalvik cache through my TWRP Recovery and then I reboot my phone . And got stuck at the Cyanogenmod Logo . So what should I do to get my phone back to normal ? I mean back to CM13 and everything I have before. PLS HELP
Note : actually , after I flashed CM 13 . I dont have the SuperSU in my apps . So I manually downloaded it from the playstore . It's weird because it should automatically be there .
Isn't root access found under developer settings?
audit13 said:
Isn't root access found under developer settings?
Click to expand...
Click to collapse
I seriously dunno about the root access at the developer settings . Now my phone is soft bricked and I'm gonna lose all of my data. Any clue on how to reflash the CM13 without deleting my stuff?(factory reset)
p/s : Yes , It's in the Developer settings
Boot into TWRP and reflash the same version of CM that was on the phone before it soft-bricked.
audit13 said:
Boot into TWRP and reflash the same version of CM that was on the phone before it soft-bricked.
Click to expand...
Click to collapse
Should I clear data , wipe cache and dalvik , factory reset all that or just go to TWRP and just flash
You could just flash over the existing ROM without wiping. If it doesn't boot, wipe cache. If it still doesn't boot, wipe data and cache.
audit13 said:
You could just flash over the existing ROM without wiping. If it doesn't boot, wipe cache. If it still doesn't boot, wipe data and cache.
Click to expand...
Click to collapse
Ok sir , new problem .. So I uses CM13 Nightlies , And I dont remember which version. Can I use latest version of CM13 Nightlies?
Yes, try the latest nightly.
audit13 said:
Yes, try the latest nightly.
Click to expand...
Click to collapse
Man It worked , seriously thank you man :good: :good: :good:
Glad to hear you solved the problem. We're all here to help and learn from each other.
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...
I am on miui 8.1.4.0 rooted rn3p. So my question is can i use dual boot patcher and dual boot lineage os 14.1
Anyone ??
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots, go back into TWRP and check your log again.
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
Thanks buddy trying it now
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
One more thing its a bit off topic but still i am using radon kernel and i am seeing that when i sweep on the black screen it unlocks how to turn this off as its consuming a lot of battery
Androbots said:
One more thing its a bit off topic but still i am using radon kernel and i am seeing that when i sweep on the black screen it unlocks how to turn this off as its consuming a lot of battery
Click to expand...
Click to collapse
Umm... not sure what you're talking about. Maybe DT2W? I tried out Radon, but I haven't tried that feature. I think you just need to reflash Radon and choose default options. If that doesn't work for you, just reflash MIUI, it will get rid of Radon.
Filip013 said:
OK. I'll try to help. Boot into TWRP and press the button on the bottom left (four lines). This will open TWRP log. If you see something like "attempting to decrypt with default password" it means your data is encrypted. An alternative solution is to flash TWRP by dadi11 and see if it asks you for password.
How to decrypt? You must format data in TWRP. This will wipe your /data and the entire internal storage so make sure you make a backup on your SD card or PC. Then boot into TWRP, select Wipe menu and press Format data. After this, immediately flash either SuperSU or Magisk or Lazy flasher (which ever one of the three you like) and only then reboot. Once the system boots go back into TWRP and check your log again.
Click to expand...
Click to collapse
Filip013 said:
Umm... not sure what you're talking about. Maybe DT2W? I tried our Radon, but I haven't tried that feature. I think you just need to reflash Radon and choose default options. If that doesn't work for you, just reflash MIUI, it will get rid of Radon.
Click to expand...
Click to collapse
Yes d2tw I was talking about that only and now i have disabled it using kernel audiutor as it was consumping a lot of abttery thanks anyway
Androbots said:
Yes d2tw I was talking about that only and now i have disabled it using kernel audiutor as it was consumping a lot of abttery thanks anyway
Click to expand...
Click to collapse
OK. Let me know if you manage to get DBP to work.
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Yup
Edit: i forgot that i checked twrp log (my bad)unfortunately it is encrypted so can't use dbp as of now but next month i might factory reset on miui and then use super su to stop encryption. Hope it works...
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Ok so here is what i got in the results of this experiment :
I was able to patch minz1 lineage os and gapps pico 7.0 and then booted to zcx and flashed both files i removed the fingerprint and any kind security measures on miui and i flashed both files and it was successful!!!
But now i am not able to boot to either miui or lineage os!!!
Conclusion: DO NOT TRY THIS!!!
Androbots said:
Ok so here is what i got in the results of this experiment :
I was able to patch minz1 lineage os and gapps pico 7.0 and then booted to zcx and flashed both files i removed the fingerprint and any kind security measures on miui and i flashed both files and it was successful!!!
But now i am not able to boot to either miui or lineage os!!!
Conclusion: DO NOT TRY THIS!!!
Click to expand...
Click to collapse
Weird... It seems to me that you are still encrypted. Have you tried flashing DualBootUtilities and switching to MIUI that way? It is possible that you messed up your primary ROM boot image, I think that happened to me once. Whatever the case, reflashing MIUI should allow you to boot into MIUI.
---------- Post added at 04:08 PM ---------- Previous post was at 04:03 PM ----------
Androbots said:
Yup
Edit: i forgot that i checked twrp log (my bad)unfortunately it is encrypted so can't use dbp as of now but next month i might factory reset on miui and then use super su to stop encryption. Hope it works...
Click to expand...
Click to collapse
I didn't see this post until now. Well, of course you can't use DBP when you're encrypted. If you want to try DPB, you have to format data.
Filip013 said:
Weird... It seems to me that you are still encrypted. Have you tried flashing DualBootUtilities and switching to MIUI that way? It is possible that you messed up your primary ROM boot image, I think that happened to me once. Whatever the case, reflashing MIUI should allow you to boot into MIUI.
Click to expand...
Click to collapse
Flashing back miui kicked me out of the situation and btw i backed up the boot.img as well as tried switching roms none worked and also it was glitching zcx a bit.
Its quite irritating seeing xiaomi and miui enforcing so many security measures a bad day for people who like to customize things a lot!
Androbots said:
Flashing back miui kicked me out of the situation and btw i backed up the boot.img as well as tried switching roms none worked and also it was glitching zcx a bit.
Its quite irritating seeing xiaomi and miui enforcing so many security measures a bad day for people who like to customize things a lot!
Click to expand...
Click to collapse
OK. Good to know that at least you have a working system now. I only experienced issues with booting MIUI after I flashed a custom kernel on MIUI and forgot to update the kernel in DBP app, but like we established flashing MIUI solves the problem.
But again, there's no use in experimenting with DBP until you format data. So please report back when you get around to doing that.
As for Xiaomi policies, I don't know the details, but I don't think it's their fault. It seems that Google can be very strict when certifying devices and allowing the OEMs to include Gapps. Google forces OEMs to ship phones with locked bootloaders and forced encryption.
Filip013 said:
OK. Good to know that at least you have a working system now. I only experienced issues with booting MIUI after I flashed a custom kernel on MIUI and forgot to update the kernel in DBP app, but like we established flashing MIUI solves the problem.
But again, there's no use in experimenting with DBP until you format data. So please report back when you get around to doing that.
As for Xiaomi policies, I don't know the details, but I don't think it's their fault. It seems that Google can be very strict when certifying devices and allowing the OEMs to include Gapps. Google forces OEMs to ship phones with locked bootloaders and forced encryption.
Click to expand...
Click to collapse
Anyways I will be resting my device next month maybe and then I can try and let u know
Filip013 said:
OK. Let me know if you manage to get DBP to work.
Click to expand...
Click to collapse
Ok so i installed epic rim today and i erased data 3times here are results:
Data erase#1 reboot recovery data is is still encrypted
Installing epic rim did not help either flashed super su 3 times still data is encrypted!!!!
What to do???
Androbots said:
Ok so i installed epic rim today and i erased data 3times here are results:
Data erase#1 reboot recovery data is is still encrypted
Installing epic rim did not help either flashed super su 3 times still data is encrypted!!!!
What to do???
Click to expand...
Click to collapse
The order of steps is very important.
1st step: Boot to recovery.
2nd step: Format data (not wipe and I don't know what you mean by erase).
3rd step: Flash ROM (Epic ROM should be good, but it also works for Global Stable and others).
4th step: Flash SuperSU.
5th step: Reboot system.
Filip013 said:
The order of steps is very important.
1st step: Boot to recovery.
2nd step: Format data (not wipe and I don't know what you mean by erase).
3rd step: Flash ROM (Epic ROM should be good, but it also works for Global Stable and others).
4th step: Flash SuperSU.
5th step: Reboot system.
Click to expand...
Click to collapse
Gotcha that means in wipe section i have to go to format data right??
Androbots said:
Gotcha that means in wipe section i have to go to format data right??
Click to expand...
Click to collapse
Yes. Good luck.
Filip013 said:
Yes. Good luck.
Click to expand...
Click to collapse
See I have setup everything on epic rom deleting everything again will be tough I will try it next month when I am bored with epic rom
Androbots said:
See I have setup everything on epic rom deleting everything again will be tough I will try it next month when I am bored with epic rom
Click to expand...
Click to collapse
LOL. Fine. Next month then.
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?