Related
PROBLEM SOLVED, THREAD CLOSED, THANKS FOR YOUR HELP
Hi guyz i'm stuck in a problem and may you can help me to get over it. I have Moto G 2015 (XT1550), before i was on stock and everything was working perfectly (including xposed and supersu). Then i moved to CyanogenMod 13.0 for my device. Now i want to flash stock again and i did it perfectly as well and it does boot up perfectly, but when i flash Supersu to root this time (I tried every supersu for marshmallow whether it is "2.67 or 2.71(latest)" it is not booting up, it freezes on logo.
1. I tried every version of TWRP for moto G
2. Tried every version of supersu
3. Without flashing supersu i boots up perfectly.
4. I can't provide log as phone is not booting up.
I'm attaching 3 screenshots, one of them is after flashing Stock firmware (of course through cmd method) and the another two after flashing cyanogenmod 13. There is difference between both images, please check them and try to provide me solution for it.
First two are after flashing cyanogenmod and last one is after flashing supersu on stock
Try BETA-SuperSU-v2.65.
lost101 said:
Try BETA-SuperSU-v2.65.
Click to expand...
Click to collapse
Tried didn't worked same problem stuck on logo, as you can see difference between both screenshots is, one is flashing "system mode" and the another one "system less mode" and in system less mode it is also flashing boot image.. Before it was fine, i don't know wtf is this.
Sent from my MotoG3 using XDA-Developers mobile app
@Chainfire please do have a look, it's a supersu problem.
Sent from my MotoG3 using XDA-Developers mobile app
@Aman Dewett - Are you doing a 'Factory data reset' in Android before flashing the firmware image? Just because Android loads does not mean everything is fine.
Aman Dewett said:
Tried didn't worked same problem stuck on logo, as you can see difference between both screenshots is, one is flashing "system mode" and the another one "system less mode" and in system less mode it is also flashing boot image.. Before it was fine, i don't know wtf is this.
Sent from my MotoG3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you try 2.62-3?
lost101 said:
@Aman Dewett - Are you doing a 'Factory data reset' in Android before flashing the firmware image? Just because Android loads does not mean everything is fine.
Click to expand...
Click to collapse
No, through twrp -> wipe-> advance, I remove OS totally. I mean wipe everything except otg and external sd card.
Sent from my MotoG3 using XDA-Developers mobile app
Aman Dewett said:
No, through twrp -> wipe-> advance, I remove OS totally. I mean wipe everything except otg and external sd card.
Click to expand...
Click to collapse
Don't ignore the instructions in the Factory Firmware flashing tutorial. This is the source of your problem.
You must do a 'Factory data reset' in Android or Stock Recovery prior to flashing.
lost101 said:
Don't ignore the instructions in the Factory Firmware flashing tutorial. This is the source of your problem.
You must do a 'Factory data reset' in Android or Stock Recovery prior to flashing.
Click to expand...
Click to collapse
I did factory reset as well bro and of course i flashed properly as instructed in "how to flash" thread by you.
That is the reason everything was working perfectly before and still i'm following the same process but this time after flashing supersu on stock it stuck on logo.
Sent from my MotoG3 using XDA-Developers mobile app
MrTooPhone said:
Did you try 2.62-3?
Click to expand...
Click to collapse
Yes
Sent from my MotoG3 using XDA-Developers mobile app
Aman Dewett said:
I did factory reset as well bro and of course i flashed properly as instructed in "how to flash" thread by you.
Click to expand...
Click to collapse
Please state clearly that you did a Factory data reset via Settings > Backup & reset.
lost101 said:
Please state clearly that you did a Factory data reset via Settings > Backup & reset.
Click to expand...
Click to collapse
No i did not performed "factory data reset" through backup & reset settings.
I format phone through twrp only..
At first i wiped it normally, then format it through advance wipe option and removed whole os from phone then flashed stock through CMD.
Sent from my MotoG3 using XDA-Developers mobile app
I cannot help you as you refuse to follow the instructions I have provided.
lost101 said:
I cannot help you as you refuse to follow the instructions I have provided.
Click to expand...
Click to collapse
Ok this time i will follow proper instruction likewise format phone through backup & reset option and then will open boot loader mode and flash the rom according to instruction (commands) provided. Let's see what will happen.
As of now SuperSU 2.62-3 is the only version that is not creating a problem. I too tried the latest versions from 2.67 to 2.71 but landed with my phone stuck at unlocked bootloader screen. Erasing cache and userdate is recommended as suggested by twrp.
lost101 said:
I cannot help you as you refuse to follow the instructions I have provided.
Click to expand...
Click to collapse
I did properly what you said, at first i "factory reset" through backup & reset option, then i open bootloader mode and flashed it according to given instructions. At the end after flashing supersu 2.65 stuck n logo. Same issue.
arunhebbare said:
As of now SuperSU 2.62-3 is the only version that is not creating a problem. I too tried the latest versions from 2.67 to 2.71 but landed with my phone stuck at unlocked bootloader screen. Erasing cache and userdate is recommended as suggested by twrp.
Click to expand...
Click to collapse
removed cache and user data as well bro didn't worked.
I faced the same problem on 6.0.1 only, and I tried every su version "UPDATE" "BETA", rooted with kingroot and unfortunately I lost my SIM card recognition!
Sent from my MotoG3 using Tapatalk
Aman Dewett said:
Hi guyz i'm stuck in a problem and may you can help me to get over it. I have Moto G 2015 (XT1550), before i was on stock and everything was working perfectly (including xposed and supersu). Then i moved to CyanogenMod 13.0 for my device. Now i want to flash stock again and i did it perfectly as well and it does boot up perfectly, but when i flash Supersu to root this time (I tried every supersu for marshmallow whether it is "2.67 or 2.71(latest)" it is not booting up, it freezes on logo.
1. I tried every version of TWRP for moto G
2. Tried every version of supersu
3. Without flashing supersu i boots up perfectly.
4. I can't provide log as phone is not booting up.
I'm attaching 3 screenshots, one of them is after flashing Stock firmware (of course through cmd method) and the another two after flashing cyanogenmod 13. There is difference between both images, please check them and try to provide me solution for it.
First two are after flashing cyanogenmod and last one is after flashing supersu on stock
Click to expand...
Click to collapse
If you and I are having the same device, and have followed the steps as given elsewhere, and I could root my phone without any problem I don't see any reason why you should not unless you are deviating or any other reason which you know or do not.... BTW it takes a long time to reboot the phone after flashing the 2.62-3. Are you falling short on patience?
arunhebbare said:
If you and I are having the same device, and have followed the steps as given elsewhere, and I could root my phone without any problem I don't see any reason why you should not unless you are deviating or any other reason which you know or do not.... BTW it takes a long time to reboot the phone after flashing the 2.62-3. Are you falling short on patience?
Click to expand...
Click to collapse
If you can read i mentioned in OP that phone gets freeze on logo, It is not going on booting stage.
Hello...
I am HTC ONE A9..
Nougat 7.0, European UHL..
S-off, SuperCID..
TWRP 3.0.3.2 beta Installed.. [TWRP 3.0.3 beta will work on Nougat only if you are S-OFF ]
Please Guide Me to root my phone.. thank you..
Should i flash UPDATE-SuperSU-v2.79-20161211114519 via TWRP?
flashing UPDATE-SuperSU-v2.76 resulted in Bootloops
Dr.Anshuman said:
Hello...
I am HTC ONE A9..
Nougat 7.0, European UHL..
S-off, SuperCID..
TWRP 3.0.3.2 beta Installed.. [TWRP 3.0.3 beta will work on Nougat only if you are S-OFF ]
Please Guide Me to root my phone.. thank you..
Should i flash UPDATE-SuperSU-v2.79-20161211114519 via TWRP?
flashing UPDATE-SuperSU-v2.76 resulted in Bootloops
Click to expand...
Click to collapse
SuperSU should work fine, it is supposed to loop 2-3 times, also, it is mandatory to wipe data via TWRP after install
How can i root my a9 with s-on and nougat ?
BigDiqSeitz said:
How can i root my a9 with s-on and nougat ?
Click to expand...
Click to collapse
Fastboot flash TWRP (one of the newer versions from the downloads tab in the thread, I used 3.0.3-4), make sure system is mounted read-only and use TWRP to flash Magisk. That's all I had to do.
JohnRogers23 said:
Fastboot flash TWRP (one of the newer versions from the downloads tab in the thread, I used 3.0.3-4), make sure system is mounted read-only and use TWRP to flash Magisk. That's all I had to do.
Click to expand...
Click to collapse
i`ve tried it like u said but after flashing twrp 3.03 i cant boot in it
[confirm] working on European & Us Unlocked/dev version on Nougat
BigDiqSeitz said:
i`ve tried it like u said but after flashing twrp 3.03 i cant boot in it
Click to expand...
Click to collapse
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3.. Reboot into system..
2 bootloops are common, do not give up for at least 3 bootloops..
It will take a long time to boot as you have done a factory reset..
So be patient and wait for at least half hour..
Dr.Anshuman said:
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3.. Reboot into system..
2 bootloops are common, do not give up for at least 3 bootloops..
It will take a long time to boot as you have done a factory reset..
So be patient and wait for at least half hour..
Click to expand...
Click to collapse
how can i backup my imp data ?
BigDiqSeitz said:
how can i backup my imp data ?
Click to expand...
Click to collapse
You can backup your data by burning your Phone at 400℃
Factory reset will wipe out your internal memory, keep a backup
Dr.Anshuman said:
You can backup your data by burning your Phone at 400℃
Factory reset will wipe out your internal memory, keep a backup
Click to expand...
Click to collapse
ahhhh i thought its a special kind of back up DD
Dr.Anshuman said:
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3.. Reboot into system..
2 bootloops are common, do not give up for at least 3 bootloops..
It will take a long time to boot as you have done a factory reset..
So be patient and wait for at least half hour..
Click to expand...
Click to collapse
I used the same versions of TWRP and SuperSU SR and get a bootloop with firmware version HIA_AERO_WHL 2.18.651.2 that I installed using RUU. I also performed a Factory Reset before installing SuperSU, when it started looping, I performed another Factory Reset.
After installing the firmware and TWRP, the phone boots fine, it is not until I install SuperSU that I start having issues.
Any other solutions?
S-ON
HIAEWHL (Sprint)
DarkXPSX said:
I used the same versions of TWRP and SuperSU SR and get a bootloop with firmware version HIA_AERO_WHL 2.18.651.2 that I installed using RUU. I also performed a Factory Reset before installing SuperSU, when it started looping, I performed another Factory Reset.
After installing the firmware and TWRP, the phone boots fine, it is not until I install SuperSU that I start having issues.
Any other solutions?
S-ON
HIAEWHL (Sprint)
Click to expand...
Click to collapse
I think you should wait for next Version of systemless superSU, or try MagiskSU..
[TWRP 3.0.3-6 unofficial for HTC One A9 is available]
https://forum.xda-developers.com/devdb/project/?id=12708#downloads
Thanks @Captain_Throwback
Dr.Anshuman said:
I think you should wait for next Version of systemless superSU, or try MagiskSU..
[TWRP 3.0.3-6 unofficial for HTC One A9 is available]
https://forum.xda-developers.com/devdb/project/?id=12708#downloads
Thanks @Captain_Throwback
Click to expand...
Click to collapse
That worked great, thanks man!
It even allows me to mask the root to pass SafetyNet to play Pokemon Go. It wouldn't work for me in previous firmware.
Heres the latest update from LG.
Must be at least 20f with TWRP to flash this.
To get TWRP go here: (Kdz to 20f if on 20g)
https://forum.xda-developers.com/showthread.php?t=3533338
Do NOT wipe system or you might get stuck in twrp bootloop.
**********************
FLASHING INSTRUCTIONS
**********************
1. MUST BE IN 20F.
2. DO NOT FORMAT SYSTEM.
2. TWRP BACKUP FIRST
3. Flash from TWRP.
DOWNLOAD
LG-V521-20G-Stock-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705254
LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
***********************************
LG-V521-TWRP.ZIP (Thanks to shabbypenguin)
***Also adds flashing TWRP to recoverybak so if an error comes up your stock recovery doesn't get reflashed.
https://www.androidfilehost.com/?fid=673368273298934005
***********************************************
COMING FROM ANOTHER ROM FLASHING INSTRUCTIONS
***********************************************
1. TWRP BACKUP FIRST
2. PLACE ROM IN INTERNAL STORAGE
3. WIPE DATA, CACHE, DALVIK/ART CACHE, SYSTEM
4. FLASH ROM FROM INTERNAL STORAGE.
*****IF IT REBOOTS BEFORE FINISHING FLASH, PRESS AND HOLD VOLUME DOWN AND POWER TILL OFF.
*****THEN ON REBOOT WITH VOLUME DOWN AND POWER PRESS, LET GO OF POWER ONLY FOR A SLIT SECOND AND *****REPRESS TO GO INTO FACTORY RESET MODE. THEN SAY YET, AND IT WILL GET YOU BACK TO TWRP.
*****IN TWRP, GO TO REBOOT AND SELECT POWER OFF. THEN GO TO STEP 4.
**************
ERROR???
**************
If you wipe system then flash a rom you might get stuck in twrp bootloop.
Here's a fix by ralphwiggum1:
https://forum.xda-developers.com/showpost.php?p=70851933&postcount=39
If that fix fails, then flashing stock recovery is another option. Then you'll have to reroot and get twrp again. If your on 20g, you'll have to kdz 20f and start over.
LG-V521-STOCK-RECOVERY.zip
https://www.androidfilehost.com/?fid=745425885120710531
Sent from my LG-H811 using Tapatalk
Thank you!, working 100%
LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
Sent from my LG-V521 using Tapatalk
MicroMod777 said:
LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
Sent from my LG-V521 using Tapatalk
Click to expand...
Click to collapse
what was debloated?
SiNJiN76 said:
what was debloated?
Click to expand...
Click to collapse
Most gapps and tmo bloat.
Sent from my LG-V521 using Tapatalk
SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?
rbadh91 said:
SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?
Click to expand...
Click to collapse
Odd. Flash just SuperSU then:
https://forum.xda-developers.com/showthread.php?t=3452703
Sent from my LG-H872 using Tapatalk
MicroMod777 said:
Odd. Flash just SuperSU then:
https://forum.xda-developers.com/showthread.php?t=3452703
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
It went back to stock recovery after flashing the zip. adb reboot recovery takes me to stock recovery.
Vol Down + Power to boot, and letting go of Power holding down Vol Down, then pressing Power & Vol Up takes me to the "hard reset" prompt, and it actually wipes device when selecting yes. I'm thinking the recovery has changed in 20G and it wipes the device instead of taking you to recovery.
Joey's Root Checker shows "Sorry! Root access is not properly installed on this device". SuperSU shows "There's no SU binary installed and SuperSU cannot install it. This is a problem."
I have a feeling I'll have to downgrade to 20F using KDZ.
EDIT: Weird...FlashFire shows "Root was found, but access could not be acquired! Supported roots: SuperSU, Magisk, CM SU (SELinux/Permissive)) Found root: (null)".
Installed SuperSU app, no luck. Tried Superuser app, no luck.
rbadh91 said:
SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?
Click to expand...
Click to collapse
I had the same issue. Lost root and twrp. Had to downgrade and start from scratch.
NoMoreBackdoors said:
I had the same issue. Lost root and twrp. Had to downgrade and start from scratch.
Click to expand...
Click to collapse
Yea I've had this happen multiple times now. Twrp is somewhat buggy where if theres a crash during flashing, or if you format the system partition, somehow theres a failsafe feature that restores the stock recovery.
I thought I had it figured out and made a flashable zip for twrp that also flashes it to the recoverybak partition. But it happened aga7n.
Sent from my LG-V521 using Tapatalk
MicroMod777 said:
Yea I've had this happen multiple times now. Twrp is somewhat buggy where if theres a crash during flashing, or if you format the system partition, somehow theres a failsafe feature that restores the stock recovery.
I thought I had it figured out and made a flashable zip for twrp that also flashes it to the recoverybak partition. But it happened aga7n.
Sent from my LG-V521 using Tapatalk
Click to expand...
Click to collapse
There's another update on my tablet...(after flashing your zip from 2-22). Will you be doing another zip with this new update?
New update is 95.22MB. I'm guessing security update. I would be wary, as the 20g update patches dirty cow, but still allows downgrade to 20f. This could block downgrade. Any brave souls out there want to confirm?
LvDisturbed1 said:
New update is 95.22MB. I'm guessing security update. I would be wary, as the 20g update patches dirty cow, but still allows downgrade to 20f. This could block downgrade. Any brave souls out there want to confirm?
Click to expand...
Click to collapse
I know I'm late, but I just picked one of these tablets up this week. I didn't think much about what I was doing, and did all OTA updates that where available. This was on 10/25/2017 or so. I was able to then use Uppercut and LGUP to flash backwards to V52120i_00_0619.kdz and successfully root, and install TWRP.
I didn't keep stock long, I jumped over to Lineage OS 14.1.
Be warned though, on Lineage OS the weekly on 10/27/2017 will cause a bootloop in TWRP. At least it did for me. After install, and while stuck in bootloop it is pretty easy to fix:
1. Open ADB Shell and run the following 2 commands:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Then reboot and all will be well.
sgrant said:
I know I'm late, but I just picked one of these tablets up this week. I didn't think much about what I was doing, and did all OTA updates that where available. This was on 10/25/2017 or so. I was able to then use Uppercut and LGUP to flash backwards to V52120i_00_0619.kdz and successfully root, and install TWRP.
I didn't keep stock long, I jumped over to Lineage OS 14.1.
Be warned though, on Lineage OS the weekly on 10/27/2017 will cause a bootloop in TWRP. At least it did for me. After install, and while stuck in bootloop it is pretty easy to fix:
1. Open ADB Shell and run the following 2 commands:
Then reboot and all will be well.
Click to expand...
Click to collapse
QUOTE
I've been running stock for a while and had this in a drawer for a year. I decided I'd start using it in my kitchen to pull up recipes on chrome. I decided to do a "factory reset" to start "clean" forgetting the warning not to do it. Now I'm stuck in a TWRP bootloop.
How can I get out of this?
Or should I switch to lineage?
Why there is no LG-V521-20N version?
I have a Google edition pixel and have been trying to root it. I have unlocked the bootloader, installed twrp, flash supersu, then flash verifiedboot. Once the phone boots up i check to see if it has root access with root check app, and it still does not. I follwed these instructions https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Used Supersu sr3
champstar said:
I have a Google edition pixel and have been trying to root it. I have unlocked the bootloader, installed twrp, flash supersu, then flash verifiedboot. Once the phone boots up i check to see if it has root access with root check app, and it still does not. I follwed these instructions https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Used Supersu sr3
Click to expand...
Click to collapse
Hi,
You have to look here for 8.0 : https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Read the OP again, it should say boot Twrp and not flash, because there is no flashable Twrp for O yet.
Sent from my Google Pixel using XDA Labs
Sgace said:
Hi,
You have to look here for 8.0 : https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Read the OP again, it should say boot Twrp and not flash, because there is no flashable Twrp for O yet.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
That is exactly what I did. Still root did not work. Should I try a different supersu zip?
champstar said:
That is exactly what I did. Still root did not work. Should I try a different supersu zip?
Click to expand...
Click to collapse
Supersu zip mentioned should be the latest and working.
Maybe ask in that thread.
Sent from my Google Pixel using XDA Labs
Tried this with the latest Supersu SR4 and still not working. I'm on Android 8.0 August 5,2017 security patch.
Maybe they fixed the exploit? I'm not sure why I can't get it rooted.
champstar said:
Tried this with the latest Supersu SR4 and still not working. I'm on Android 8.0 August 5,2017 security patch.
Maybe they fixed the exploit? I'm not sure why I can't get it rooted.
Click to expand...
Click to collapse
What messages does it say in twrp, as you flash SuperSU? ... if you've already flashed SuperSU, the script could be restoring the backup boot.IMG, which could be your problem...
When I bump into that, personally; I just download the factory image, then edit the flash-all.sh script and remove the -w flag (which tells the script to not wipe the device), I save the script then execute it...
It flashes the image and I end up with an unaltered boot.IMG and system, then I flash SuperSU after....
I'm on the Sept 5 image using SuperSU sr3 ... SuperSU works like a charm.
After plenty of tiral and error I have finally rooted the phone.
For some reason this tutorial was the only one to work for me.
http://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Hope this can help someone in the future.
THANKS!
champstar said:
After plenty of tiral and error I have finally rooted the phone.
For some reason this tutorial was the only one to work for me.
http://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Hope this can help someone in the future.
Click to expand...
Click to collapse
Im an htc u11+ user, the device is largely underrated thus very few resources available.
However, i was having the exact same issues you were, flashing your supersu zip worked for me after various frustrating attempts using other versions of superSU
Thanks a lot
I went to reload 5.1.11 ..I think it might be because I forgot to remove my security features now keeps rebooting to TWPR
do I have to do a compete wipe now....or is there a simple method ?? Thanks for the help!
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
ImSpiderman said:
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
Click to expand...
Click to collapse
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
double post
skyeking69 said:
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
Click to expand...
Click to collapse
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
ImSpiderman said:
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
Click to expand...
Click to collapse
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
skyeking69 said:
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
Click to expand...
Click to collapse
No you don't have to
ImSpiderman said:
No you don't have to
Click to expand...
Click to collapse
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
skyeking69 said:
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
Click to expand...
Click to collapse
That didn't work? Really strange tho
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Gradusr said:
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Click to expand...
Click to collapse
Thanks but I really don't understand this....first I don't know if encryption is on ? Don't think I have turned it off...2nd 3.2.2.0 worked fine for me before..I installed 5.1.9 and 5.1.11 with no problems.....it was when I tried to reinstall 5.1.11 and forgot to remove security features this happened now?
How old is this thread about TWRP 3.2.2.0 ?
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
WOS17 said:
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
Click to expand...
Click to collapse
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
skyeking69 said:
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
Click to expand...
Click to collapse
No, any security just double tap to wake.
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Thanks..I'll try that first....the TWRP I have is 3.2.2.0 from official page ( I think ?) I'll try 16.7 and see what happens..
WOS17 said:
No, any security just double tap to wake.
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Click to expand...
Click to collapse
I'm using 3.2.2.0 which was working fine.....the guy below tells me to use 16.7 Magisk???? Geez not sure now ?
Gradusr said:
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Click to expand...
Click to collapse
The thing is TWRP 3.2.2.0 does ask me to enter my pin code then goes to the options page...install, wipe, backup,restore...etc...
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Geez ...now when I go to reboot to recovery it gives me a warning " No OS installed, are you sure you want to reboot?? " what do I do now ??