Related
Good day to everyone! I wish to provide proper steps on how to install the latest Oreo custom ROMs via TWRP in order to lessen the clutter in the custom ROM threads.
You'll need the following:
Latest TWRP Official (Fastboot TWRP)
Latest TWRP Installer (PERMANENT TWRP)
Considering you already installed TWRP via fastboot, we'll make it so that it will be permanently installed and you will not need to flash TWRP via bootloader again.
Download ROM + GApps (or no gapps if Pixel Experience)
Reboot to latest Official TWRP
Do necessary wipes (FORMAT data if having storage number issue; if not, wipe system/data/cache) then transfer ROM + gapps + magisk to internal/external storage
Flash ROM (don't reboot)
Flash latest TWRP Installer (for Permanent TWRP)
Reboot recovery (no need to transfer slots anymore as TWRP does it automatically)
Flash Gapps + Magisk
Reboot to system
To DIRTY FLASH or update the same ROM with an updated version
Reboot to recovery
Flash ROM
Flash TWRP Installer
Reboot recovery
Flash Gapps + Magisk
Reboot to system
For installing custom kernels
Download custom kernel
Reboot recovery
Flash custom kernel
Reboot to system
All of these has been tried and tested by me already.
Hey , where to flash rom??
As you have written gapps + magisk , gapps + magisk twice
sikoo1996 said:
Hey , where to flash rom?
As you have written gapps + magisk , gapps + magisk twice
Click to expand...
Click to collapse
I don't know what you mean. Read it again but slowly.
thnx man.
please add instructions to flash twrp permanent or share link.
vkbhanwariya said:
thnx man.
please add instructions to flash twrp permanent or share link.
Click to expand...
Click to collapse
+1
vkbhanwariya said:
thnx man.
please add instructions to flash twrp permanent or share link.
Click to expand...
Click to collapse
dceamit46 said:
+1
Click to expand...
Click to collapse
Guys, TWRP Installer IS the Permanent TWRP. That's why you need to flash it every time after flashing custom ROMs.
joeyhuab said:
Guys, TWRP Installer IS the Permanent TWRP. That's why you need to flash it every time after flashing custom ROMs.
Click to expand...
Click to collapse
thanks mate now ROM flashing seems very easy
vkbhanwariya said:
thanks mate now ROM flashing seems very easy
Click to expand...
Click to collapse
You're welcome! Good luck in switching ROMs!
Sent from my Xiaomi Mi A1 using XDA Labs
joeyhuab said:
You're welcome! Good luck in switching ROMs!
Click to expand...
Click to collapse
I really want to thank you for putting this up. Its immensely helpful and once again you are best at what you do.
gunmanrishi said:
I really want to thank you for putting this up. Its immensely helpful and once again you are best at what you do.
Click to expand...
Click to collapse
You're more than welcome and I'm always more than glad to help out the community. :highfive:
Sent from my Xiaomi Mi A1 using XDA Labs
With custom ROMs we have to install Twrp installer every time along with ROM zip, bit awkward.
Is it just me but every time I flash twrp after flashing rom, I got error 20 when flashing gapps. Here's my steps:
- flash rom
- switch partition
- flash twrp
- reboot recovery (or bootloader then flashboot recovery)
- flash gapps -> error 20
Without flashing twrp permanent, I can flash gapps, no error.
madhpharma said:
With custom ROMs we have to install Twrp installer every time along with ROM zip, bit awkward.
Click to expand...
Click to collapse
Yep. That's because the ROM being flashed overwrites the recovery since there's no recovery partition.
kopitalk said:
Is it just me but every time I flash twrp after flashing rom, I got error 20 when flashing gapps. Here's my steps:
- flash rom
- switch partition
- flash twrp
- reboot recovery (or bootloader then flashboot recovery)
- flash gapps -> error 20
Without flashing twrp permanent, I can flash gapps, no error.
Click to expand...
Click to collapse
Did you flash the TWRP.img or TWRP Installer.zip in TWRP?
Sent from my Xiaomi Mi A1 using XDA Labs
joeyhuab said:
Yep. That's because the ROM being flashed overwrites the recovery since there's no recovery partition.
Did you flash the TWRP.img or TWRP Installer.zip in TWRP?
Click to expand...
Click to collapse
Twrp installer, to be exact Twrp-recoveryInstaller-3.2.1-2-oreo.zip
joeyhuab said:
Guys, TWRP Installer IS the Permanent TWRP. That's why you need to flash it every time after flashing custom ROMs.
Click to expand...
Click to collapse
If we need to flash it every time after flash rom so how it's called permanent TWRP I don't understand. That because our device don't have recovery partition? If that so where this TWRP installed ( in which partition)?
cherryb8844 said:
If we need to flash it every time after flash rom so how it's called permanent TWRP I don't understand. That because our device don't have recovery partition? If that so where this TWRP installed ( in which partition)?
Click to expand...
Click to collapse
It's called permanent twrp because it won't get replaced by built in recovery whenever you reboot to recovery from system. TWRP gets installed within a part of the system partition.
Sent from my Xiaomi Mi A1 using XDA Labs
kopitalk said:
Is it just me but every time I flash twrp after flashing rom, I got error 20 when flashing gapps. Here's my steps:
- flash rom
- switch partition
- flash twrp
- reboot recovery (or bootloader then flashboot recovery)
- flash gapps -> error 20
Without flashing twrp permanent, I can flash gapps, no error.
Click to expand...
Click to collapse
Error 20 if I'm not wrong, means you are using the wrong gapps package.
Are you using the right one?
varben said:
Error 20 if I'm not wrong, means you are using the wrong gapps package.
Are you using the right one?
Click to expand...
Click to collapse
Yes, I certainly use the right one (8.1), that's why I was baffled when twrp says that my device is 7.1.2 every time I tried to flash the 8.1 gapps. Anyway, flashing rom then straightaway followed by gapps and magisk was fine. I can flash twrp installer later on. But I just don't understand why.
kopitalk said:
Yes, I certainly use the right one (8.1), that's why I was baffled when twrp says that my device is 7.1.2 every time I tried to flash the 8.1 gapps. Anyway, flashing rom then straightaway followed by gapps and magisk was fine. I can flash twrp installer later on. But I just don't understand why.
Click to expand...
Click to collapse
Well that's weird. Works for me by flashing Gapps and Magisk after rebooting to recovery since it switches slots when you do that. Did you possibly come from a Nougat ROM which is why that's the error showing up?
Sent from my Xiaomi Mi A1 using XDA Labs
joeyhuab said:
Well that's weird. Works for me by flashing Gapps and Magisk after rebooting to recovery since it switches slots when you do that. Did you possibly come from a Nougat ROM which is why that's the error showing up?
Click to expand...
Click to collapse
I was thinking of that too but no, I was on Oreo Jan built the first time I rooted the phone and flash LOS15.1. Do you think I should at least flash Oreo stock once? Maybe my bootloader is still Nougat
DO NOT UPGRADE MAGISK TO 19.x OR YOUR PHONE WILL BOOTLOOP!
All you need is an unlocked bootloader.
Install:
1. Download the file for your device
2. Flash via fastboot
Code:
fastboot flash boot boot.img
3. Reboot
4. Install Magisk Manager
Download for Firmware 53.0.A.6.92:
I3113: Download
I4113: Download
If you like my work, press thanks
I would appreciate your Donation
thanks a lot!
My device is I4193, I flashed the your rooted image of I4113(as they have the same boot image).
my device can boot normally, but in magisk manager , the device still shown as unroot.
wang4632 said:
thanks a lot!
My device is I4193, I flashed the your rooted image of I4113(as they have the same boot image).
my device can boot normally, but in magisk manager , the device still shown as unroot.
Click to expand...
Click to collapse
You need to download the boot-magisk.img and not the boot-stock.img
Schritti said:
You need to download the boot-magisk.img and not the boot-stock.img
Click to expand...
Click to collapse
yes, I download the boot-magisk.img. of wihch the file size is a bit larger then stock one.
wang4632 said:
yes, I download the boot-magisk.img. of wihch the file size is a bit larger then stock one.
Click to expand...
Click to collapse
Could you try the I3113 one? Should also boot.
Schritti said:
Could you try the I3113 one? Should also boot.
Click to expand...
Click to collapse
I tried this one. it can boot normally, but magisk manager still shows unroot..
can you please help patching the stock boot image of I4193?
i uploaded the stock boot image, here is the download link:
https://drive.google.com/file/d/1aN-kTQN8g_HodjSqcPr42e-cyvMriDd0/view?usp=sharing
wang4632 said:
I tried this one. it can boot normally, but magisk manager still shows unroot..
can you please help patching the stock boot image of I4193?
i uploaded the stock boot image, here is the download link:
https://drive.google.com/file/d/1aN-kTQN8g_HodjSqcPr42e-cyvMriDd0/view?usp=sharing
Click to expand...
Click to collapse
Here you go
https://mega.nz/#F!DyQDHI5S!BN44I8xHfk8yf-9AFj5axg
Please report if it works, so i can add it to OP
Schritti said:
Here you go
https://mega.nz/#F!DyQDHI5S!BN44I8xHfk8yf-9AFj5axg
Please report if it works, so i can add it to OP
Click to expand...
Click to collapse
it didn't work. same as before, it boot normally, but shows unroot in magisk manager.
Form XperiaFirm, I saw I4193 is only for HongKong and Taiwan, I'm not sure if it has some difference form other models, maybe I can post the patched boot image in some Chinese forums, I hope some more users can help test it .
Schritti said:
DO NOT UPGRADE MAGISK TO 19.x OR YOUR PHONE WILL BOOTLOOP!
All you need is an unlocked bootloader.
Install:
1. Download the file for your device
2. Flash via fastboot
Code:
fastboot flash boot boot.img
3. Reboot
4. Install Magisk Manager
Download for Firmware 53.0.A.6.92:
I3113: Download
I4113: Download
If you like my work, press thanks
I would appreciate your Donation
Click to expand...
Click to collapse
I wiped my device by using newflasher to flash the stock 53.0.A.6.92 firmware and then flashed boot-magisk-I4113, and now it works. I can see root status in magisk manager.
I don't know what is the reason, but anyweay it works now. thnak you!
wang4632 said:
DO NOT UPGRADE MAGISK TO 19.x OR YOUR PHONE WILL BOOTLOOP!
All you need is an unlocked bootloader.
Install:
1. Download the file for your device
2. Flash via fastboot
I wiped my device by using newflasher to flash the stock 53.0.A.6.92 firmware and then flashed boot-magisk-I4113, and now it works. I can see root status in magisk manager.
I don't know what is the reason, but anyweay it works now. thnak you!
Click to expand...
Click to collapse
Great!
Could be because you maybe had your phone rooted with 19.0 on the previous firmware
But i cant install modules from magisk. MMMM, can install, after restart not appear modules in modules part
@Schritti Can you make this for .8.71 firmware if possible please? Many thanks in advance
Chronic2k13 said:
@Schritti Can you make this for .8.71 firmware if possible please? Many thanks in advance
Click to expand...
Click to collapse
You can use my TWRP to flash Magisk 18.1
https://forum.xda-developers.com/xperia-10/development/recovery-twrp-3-3-1-0-unofficial-t3941158
Schritti said:
You can use my TWRP to flash Magisk 18.1
https://forum.xda-developers.com/xperia-10/development/recovery-twrp-3-3-1-0-unofficial-t3941158
Click to expand...
Click to collapse
I don't think it is possible to install magisk without sd card decrypt working.
ToastedToast said:
I don't think it is possible to install magisk without sd card decrypt working.
Click to expand...
Click to collapse
External SD should be fine
I flashed magisk-boot.img and all worked.
Now i wanted to unroot and stupid me, not thinking about what i am doing, i unrooted through magisk manager.
So i'm stuck in a boot loop.
Flashing the stock-boot.img in fastboot mode now got me to fastboot not recognizing my phone anymore.
When i check "fastboot devices" it returns "???????????? fastboot".
Flash mode still allows me to flash another boot.img with "fastboot flash boot stock-boot.img" but that doesn't fix the bootloop.
Any ideas?
Newflasher with xperifirm firmware files. Then factory reset from booted phone to re-gain safetynet
ToastedToast said:
Newflasher with xperifirm firmware files. Then factory reset from booted phone to re-gain safetynet
Click to expand...
Click to collapse
Wow! That worked! Thank you so much!!!
VelocityHD said:
Wow! That worked! Thank you so much!!!
Click to expand...
Click to collapse
blade85 said:
Since I'm in a similar situation can you please send me the links where I can download the original firmware images?
Thanks in advance
Click to expand...
Click to collapse
Forget it I found everything, which Market and Operator did you take? I see there's no Austrian package?
Does anyone also have a european 53.0.A.6.92 firmware? Would need it to be able to root it
I was running Oxygen OS 9 with XXX nolimt magisk rom updated to oxygen OS 10 and now the phones stuck on the boot logo screen and i cant access recovery, when i try to push Twrp with adb it just freezes. ideas?
Fastboot rom.
Lostmymind904 said:
I was running Oxygen OS 9 with XXX nolimt magisk rom updated to oxygen OS 10 and now the phones stuck on the boot logo screen and i cant access recovery, when i try to push Twrp with adb it just freezes. ideas?
Click to expand...
Click to collapse
Link? T mobile version flashed to international.
jimmy123322 said:
Fastboot rom.
Click to expand...
Click to collapse
Link? T mobile version flashed to international.
try use TOOLS ALL IN ONE and use Flash ROM VIA ADB option
ele95 said:
try use TOOLS ALL IN ONE and use Flash ROM VIA ADB option
Click to expand...
Click to collapse
tried that with a rom i downloaded from the oneplus website but it failed guessing fastboot roms are different??downloading fastboot OOS 10 now
Lostmymind904 said:
tried that with a rom i downloaded from the oneplus website but it failed guessing fastboot roms are different??downloading fastboot OOS 10 now
Click to expand...
Click to collapse
You can use the TMobile MSM tool
Thanks everyone problem solved ?
had the same issue ..
turned out to be of 2 parts
1. old twrp with no auppprt for Q that didn't read encryption
2. didn't un install magisk before upgrading
edl helped with the boot but reverted to the bootloop aftwr that until i used the fixes above
Lostmymind904 said:
Thanks everyone problem solved ?
Click to expand...
Click to collapse
How did you end up fixing it? Just curious which route you took
sparky2029 said:
How did you end up fixing it? Just curious which route you took
Click to expand...
Click to collapse
Short guide for people having my problem.
1. download the all in one tool https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
2. download a fastboot rom(A regular OTA won't work) https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424 (10.0-GM21AA for me)
3. Open the "all in one tool" and select "flash factory images" and navigate to the the Fast boot ROM you've downloaded.
4. Select the "wipe all data" (you'll loose everything)and "reboot after flash" options.
5. Wait
6. Done.
I got a Motorola G8 Power, and as far as I know, it will not get Android 12, so I was wondering if there is already any Android 12 stable GSI (because I doubt that there are any ROMS, and even less likely for this device).
Also, if I installed it, would I get any OTA updates? What about Google Play Services? Would it be better to just install a ROM like HavocOS (GSI) and wait for them to release the Android 12 update?
Thanks in advance.
Apparently now their is. Check https://ci.android.com/builds/branches/aosp-android12-gsi/grid?
Tell me how it goes!
KevinKraze said:
Apparently now their is. Check https://ci.android.com/builds/branches/aosp-android12-gsi/grid?
Tell me how it goes!
Click to expand...
Click to collapse
Thanks! Will try to flash it and I'll tell you
ByteSeb said:
Thanks! Will try to flash it and I'll tell you
Click to expand...
Click to collapse
Did it work?
kelvinchinedu said:
Did it work?
Click to expand...
Click to collapse
It did not work for me. I just think that this has to do with Android 11, as I tried to install other ROMS and none of them worked. Well, one did, but it was stuck in a bootloop. I am planning on trying again, though.
When u xtract the zip file did u get system img
kelvinchinedu said:
When u xtract the zip file did u get system img
Click to expand...
Click to collapse
Yes. You have to get the version that corresponds to your phone. For example, my Moto G8 Power is an ARM64 device, so I visited this website and downloaded this zip file containing the boot images, the system image and the vbmeta image.
How did u flash it
kelvinchinedu said:
How did u flash it
Click to expand...
Click to collapse
I am trying to flash it via Fastboot, so I rebooted my phone into the bootloader and entered the commands:
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
It has not worked for me, as I get the "Preflash validation failed" error, but it could work for you
I have latest twrp I can use it.
kelvinchinedu said:
I have latest twrp I can use it.
Click to expand...
Click to collapse
Yes, just flash the images one by one instead of flashing the zip
How?
One by one
kelvinchinedu said:
How?
One by one
Click to expand...
Click to collapse
In TWRP, Go to Install, then tap on "Install Image" and select the images
What about the vendor am I going to flash it?
I tried flashing the a125f firmware via Odin but it gave me a pit error, currently on the Canadian firmware
comicc said:
I tried flashing the a125f firmware via Odin but it gave me a pit error, currently on the Canadian firmware
Click to expand...
Click to collapse
You cannot, unless you use BROM Mode, which I do not recommend, since A125W and A125F are really different even though the model just has a change in the letter at the end, and it can brick your device permanantly.
TheWorldYT said:
You cannot, unless you use BROM Mode, which I do not recommend, since A125W and A125F are really different even though the model just has a change in the letter at the end, and it can brick your device permanantly.
Click to expand...
Click to collapse
how would it brick? could I not just reflash og firm?
comicc said:
how would it brick? could I not just reflash og firm?
Click to expand...
Click to collapse
Yeah you cannot, because the A125F is very different, and the A125W, if unlocked version is already equivalent to the A125F, so why would you? I think you can use A125F TWRP, and etc on A125W fine, so no need.
and A125F will give you pretty much the exact same signal and speed capabilities as the A125W, so if that's your reasoning, there's absolutely no need to do it.
TheWorldYT said:
Yeah you cannot, because the A125F is very different, and the A125W, if unlocked version is already equivalent to the A125F, so why would you? I think you can use A125F TWRP, and etc on A125W fine, so no need.
and A125F will give you pretty much the exact same signal and speed capabilities as the A125W, so if that's your reasoning, there's absolutely no need to do it.
Click to expand...
Click to collapse
i wanted to use a custom kernel because the a12 is pretty slow but they all boot loop, and twrp has my storage encrypted and touch doesnt work
comicc said:
i wanted to use a custom kernel because the a12 is pretty slow but they all boot loop, and twrp has my storage encrypted and touch doesnt work
Click to expand...
Click to collapse
You could ask @physwizz
comicc said:
i wanted to use a custom kernel because the a12 is pretty slow but they all boot loop, and twrp has my storage encrypted and touch doesnt work
Click to expand...
Click to collapse
If your storage is encrypted you didn't install twrp correctly.
1. Connect to pc and boot into stock recovery
2. Factory reset
3. Reboot into download mode.
4. flash twrp tar file into the ap slot
5. reboot to recovery
6. Advanced, terminal. Type multidisabler (twice).
7.
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
8. Reboot to recovery from main menu (not just reboot)
Backup boot, data, super and dtbo
9. Reboot to system
physwizz said:
If your storage is encrypted you didn't install twrp correctly.
1. Connect to pc and boot into stock recovery
2. Factory reset
3. Reboot into download mode.
4. flash twrp tar file into the ap slot
5. reboot to recovery
6. Advanced, terminal. Type multidisabler (twice).
7.
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
8. Reboot to recovery from main menu (not just reboot)
Backup boot, data, super and dtbo
9. Reboot to system
Click to expand...
Click to collapse
my twrp works now but i still cant install any kernels
comicc said:
my twrp works now but i still cant install any kernels
Click to expand...
Click to collapse
What is your baseband?
physwizz said:
What is your baseband?
physwizz said:
What is your baseband?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
just to be sure i can install it just bootloops, my baseband is A125WVLS5BVL2
comicc said:
just to be sure i can install it just bootloops, my baseband is A125WVLS5BVL2
Click to expand...
Click to collapse
There are no kernels available for this baseband.
I will order the source code
physwizz said:
There are no kernels available for this baseband.
I will order the source code
Click to expand...
Click to collapse
did you get the kernel?
comicc said:
did you get the kernel?
Click to expand...
Click to collapse
Source code has just been posted
physwizz said:
Source code has just been posted
Click to expand...
Click to collapse
how do i build it?
comicc said:
how do i build it?
Click to expand...
Click to collapse
You can follow my guides or you can wait for me to have some time.
Physwizz Collection
INDEX: Kernel Building Guides from physwizz About Me https://t.me/physwizz2/2 Building with GCC (beginners start here) https://t.me/physwizz2/182 GITHUB for Beginners https://t.me/physwizz2/10 Building with Clang https://t.me/physwizz2/43 AOSP https://t.me/physwizz2/645 Using Anykernel3...
t.me
physwizz said:
You can follow my guides or you can wait for me to have some time.
Physwizz Collection
INDEX: Kernel Building Guides from physwizz About Me https://t.me/physwizz2/2 Building with GCC (beginners start here) https://t.me/physwizz2/182 GITHUB for Beginners https://t.me/physwizz2/10 Building with Clang https://t.me/physwizz2/43 AOSP https://t.me/physwizz2/645 Using Anykernel3...
t.me
Click to expand...
Click to collapse
okay, please tell me when you have the time because i dont have a device to build it on
comicc said:
okay, please tell me when you have the time because i dont have a device to build it on
Click to expand...
Click to collapse
I just have to try to complete my current task.
I'm doing twrp for a01core
physwizz said:
I just have to try to complete my current task.
I'm doing twrp for a01core
Click to expand...
Click to collapse
what are you gonna do to the kernel? for the a12