Related
So as written in the title, i've tried flashing different Supersu versions. I also tried doing so on official oxygen os, cyanogenmod 13 and now currently using paranoid CM, it would get stuck in a boot loop everytime i tried to flash supersu. Any help there ? I'm sure i haven't got root access already !
gabytzu339 said:
So as written in the title, i've tried flashing different Supersu versions. I also tried doing so on official oxygen os, cyanogenmod 13 and now currently using paranoid CM, it would get stuck in a boot loop everytime i tried to flash supersu. Any help there ? I'm sure i haven't got root access already !
Click to expand...
Click to collapse
What version you using? You want 2.65 or higher .
Try the latest beta SuperSU and you will have no problem at all!
Thank you very much guys ! I've initially tried to flash 2.52, 2.56 and 2.65, none of them worked, it went well with 2.72 or w/e is that last one .
Try to change that supersu zip file and try other versions
If you haven't unlocked the bootloader then it won't boot into a modified system. To unlock the bootloader you need to reflash the stock recovery from here: https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img. Once flashed, boot into OxygenOS, go to settings, go to About Phone, tap on "build number" until it says that you're a developer. Back to settings, go to Developer, and turn on OEM unlock. Now boot into Fastboot, and on the computer you used to flash TWRP in the first place, use the command "fastboot oem unlock". Then you can flash TWRP and use whatever rom you like or flash SuperSU on OOS.
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
are you using the minimal adb to flash the recovery not flashtools like the root thread says to coz if your using flashtool thats y ur in bootloop im on the uk customiseed and have no issues
buzzinkeegs said:
are you using the minimal adb to flash the recovery not flashtools like the root thread says to coz if your using flashtool thats y ur in bootloop im on the uk customiseed and have no issues
Click to expand...
Click to collapse
Which root thread are you referring to? I've seen quite a few and none of the ones I followed mentioned minimal adb. I'm using Flashtool on windows to flash the ROM and I'm using linux for fastboot, since it doesn't work on Windows for some reason and it's too much effort to troubleshoot when it works fine on Linux.
RNZL3R said:
Which root thread are you referring to? I've seen quite a few and none of the ones I followed mentioned minimal adb. I'm using Flashtool on windows to flash the ROM and I'm using linux for fastboot, since it doesn't work on Windows for some reason and it's too much effort to troubleshoot when it works fine on Linux.
Click to expand...
Click to collapse
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
that 1
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
While flashing the ROM through flashtool, deselect option FOTA-KERNEL, this will keep twrp as your recovery.
Also you can use X-GEN Rom which is based on latest stock rom to flash it from TWRP instead of flashtool
Should I flash TWRP now and then re-flash the UK ROM?
RNZL3R said:
So I've unlocked my bootloader and have been trying to install TWRP and try various ROMS. I've only tried paranoid android and Lineage 14.1. Lineage 14.1 doesn't work with gapps, and paranoid doesn't work with blueooth. So I'm going to the stock UK rom.
What I'd like to do is go with the stock UK rom, but I want TWRP too so I can flash things (like a debloat script.) However, whenever I install the UK ROM, twrp stops working. If I re-flash TWRP, the the phone gets stuck in a boot loop.
Click to expand...
Click to collapse
while flashing stockrom, uncheck FOTAKERNEL.sin in FLASHTOOL FIRMWARE SELECTION PANEL.
this way you can keep the twrp intact
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
You have to be decrypted or flash DMverity for A12. I assume You mean Magisk 24.1 the current version is 24.3
Hi. This is what I did:
I downloaded and installed original firmware through fastboot (fastboot was still on).
I also installed original recovery through fastboot.
After that my oneplus 5t was in stock condition, apart from the bootloader, which was unlocked.
After that I managed to install TWRP through fastboot, and then lineage 19.
The thing is that TWRP doesn't support lineage 19, for one reason or another. Or it could be the other way around (lineage 19 doesn't support TWRP). In any case I had a phone which would only go in fastboot mode.
At least I knew what to do, as I did it already: reinstall stock firmware and recovery.
Long story short, I installed LOS recovery and lineage 19, and everything works fine.
Thanks everyone, and especially thaidroid, for the support.
Have a nice day.
miclombardo said:
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Its not working cus you need to format data in recovery and then reboot it.
kirknado18 said:
Its not working cus you need to format data in recovery and then reboot it.
Click to expand...
Click to collapse
It wont boot cus your encrypted formatting data will allow op5t to boot.
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
paradoxiumwind said:
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
Click to expand...
Click to collapse
What recovery are you on? TWRP?
I use the one posted alongside each version: https://download.lineageos.org/dumpling
can you help?
I need to root so I can titanium backup everything. but I can't root. I suspect I might need to fully format and wipe and start again, I tried wiping data and doing a fresh install, but after sideloading magisk it just fails to boot every time now.
Does it boot regularly BEFORE installing magisk? I am trying to define the source of the problem.
I have installed lineage 19 and magisk, and I confirm you that it's possible
Yes. It boots fine if I just install lineage then nevermindthegapps. problem only occurs if I flash magisk. I tried installing the .apk and patching the .boot image manually in it and then fastboot flashing that, but same thing.
oh - one possible thing that it may be - is that I had a couple of modules loaded (I think a gcam fix mod and something similar) in magisk, and I read somewhere about people having them stuck 'installed' despite demoving all traces of magisk app. whether that is the problem I don't know.
This is very strange. That's what I did:
Sideload lineage recovery
Sideload lineage 19
Download magisk apk
Patched boot image from lineage 19.zip
Sideload the patched boot image
And that's it it all worked
May I suggest you to start all over again?
is wiping system data sufficient or do I need to format it? I'd rather not lose my appdata- but I can't rescue it without root / titanium backup :/
Try first without formatting, and see how it goes
I wiped system/cache, installed lineage-19.1-20220719-nightly-dumpling-signed.zip / mindthegapps, phone booted up fine - rebooted fine.
ok, good. Now download latest magisk app and patch the boot img.
do I click patch vbmeta in image?
Yes.
First extract the file called boot.img from lineage.zip you just installed.
Then in magisk select "patch vbmeta in image".
Magisk should produce a file named something like " magisk_pached-24300_f41h3.img".
That patched file should be sideloaded.
Installation is explained really well by topjohnwu
it wouldn't flash without selecting vbmeta, so tried with, flashed it, now i'm sitting looking at the boot logo.
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img