I flashed the Android GSI (Generic System Image) but now I want to go back to Oxygen OS how do I go back.....I tried just flashing the zip for Oxygen OS but it keeps bootlooping so I figured since I flagged a new system image it wouldn't work so how do I flash the Oxygen OS system image???
Help I'm really confused can't find anything online
Abhaypraseeth said:
I flashed the Android GSI (Generic System Image) but now I want to go back to Oxygen OS how do I go back.....I tried just flashing the zip for Oxygen OS but it keeps bootlooping so I figured since I flagged a new system image it wouldn't work so how do I flash the Oxygen OS system image???
Help I'm really confused can't find anything online
Click to expand...
Click to collapse
On recovery wipe everything and format data then flash oos zip and magisk if you want to keep root and TWRP!! That's all
intoxicated.mad said:
On recovery wipe everything and format data then flash oos zip and magisk if you want to keep root and TWRP!! That's all
Click to expand...
Click to collapse
Ok I'll try that over the weekend thanks!
intoxicated.mad said:
On recovery wipe everything and format data then flash oos zip and magisk if you want to keep root and TWRP!! That's all
Click to expand...
Click to collapse
It didn't work
Abhaypraseeth said:
I flashed the Android GSI (Generic System Image) but now I want to go back to Oxygen OS how do I go back.....I tried just flashing the zip for Oxygen OS but it keeps bootlooping so I figured since I flagged a new system image it wouldn't work so how do I flash the Oxygen OS system image???
Help I'm really confused can't find anything online
Click to expand...
Click to collapse
Can you explain what the Android GSI is and where it gets flashed to? What OOS version were you on before you flashed the AGSI?
Abhaypraseeth said:
It didn't work
Click to expand...
Click to collapse
I think you need to head towards unbrick tool
shadeau said:
Can you explain what the Android GSI is and where it gets flashed to? What OOS version were you on before you flashed the AGSI?
Click to expand...
Click to collapse
Android GSI stands for Generic System Image and its a system image that can be installed on treble supported devices such as OnePlus 5T I installed it to get Pie for my phone...this was before Pie for OnePlus 5T was released and I had OOS 5.1.6 before I installed Android GSI
intoxicated.mad said:
I think you need to head towards unbrick tool
Click to expand...
Click to collapse
Does the unbricking tool include a system image?
Abhaypraseeth said:
Android GSI stands for Generic System Image and its a system image that can be installed on treble supported devices such as OnePlus 5T I installed it to get Pie for my phone...this was before Pie for OnePlus 5T was released and I had OOS 5.1.6 before I installed Android GSI
Click to expand...
Click to collapse
I'm going to guess that you might need a stock system image to flash. If you made a backup of one in TWRP before flashing the AGSI then you can just flash that. Otherwise you can see if the unbricking tool works. There's an all-in-one till tool for the 5T but it didn't look like it has a factory image. Worst case I can extract one for you (I would clean flash a ROM and extract the image since my current one has Magisk injected). Just let me know if the other fixes don't work.
shadeau said:
Does the unbricking tool include a system image?
I'm going to guess that you might need a stock system image to flash. If you made a backup of one in TWRP before flashing the AGSI then you can just flash that. Otherwise you can see if the unbricking tool works. There's an all-in-one till tool for the 5T but it didn't look like it has a factory image. Worst case I can extract one for you (I would clean flash a ROM and extract the image since my current one has Magisk injected). Just let me know if the other fixes don't work.
Click to expand...
Click to collapse
I have a system image extracted from OSS 5.1.6 I tried flashing that too but still says no OS installed and also I tried installing through Aroma installer but still booted back to TWRP
Abhaypraseeth said:
I have a system image extracted from OSS 5.1.6 I tried flashing that too but still says no OS installed and also I tried installing through Aroma installer but still booted back to TWRP
Click to expand...
Click to collapse
Have you tried flashing the system image through fastboot?
shadeau said:
Have you tried flashing the system image through fastboot?
Click to expand...
Click to collapse
no i have not
can you tell me the steps (i know how to flash the image in fastboot) but after that how do i flash OOS
EDIT
I tried the unbrick tool and it worked thanks guys for your help
Related
Okay, lemme get this clear that I'm not a pro in all this stuff. Infact, I'm a total idiot.
I have tried to flash a lot of ROMs on my Moto G5 (cedric) but only 3 of them have worked, namely:
1) Pixel Expirience 7.1.2
2) Ressurection Remix 7.1.2
3) Viper OS 7.1.2
I don't know whats the problem and whether it is with my phone or the ROMs. Also, even after i used these ROMs, the apps which need root access weren't working and yes i did select the Root Access setting to ADB only(cause thats was the only option other than Off). Plz help me guys.....
Astitva_ said:
Okay, lemme get this clear that I'm not a pro in all this stuff. Infact, I'm a total idiot.
I have tried to flash a lot of ROMs on my Moto G5 (cedric) but only 3 of them have worked, namely:
1) Pixel Expirience 7.1.2
2) Ressurection Remix 7.1.2
3) Viper OS 7.1.2
I don't know whats the problem and whether it is with my phone or the ROMs. Also, even after i used these ROMs, the apps which need root access weren't working and yes i did select the Root Access setting to ADB only(cause thats was the only option other than Off). Plz help me guys.....
Click to expand...
Click to collapse
First you need to say how you have done the flashing of roms and which rom didn't flash, or what error you got while installing the rom. And second is you need to install magisk manager to gain root access with twrp, by enabling the root access in developer option won't give you root access you need to install it via twrp.
riyan65 said:
First you need to say how you have done the flashing of roms and which rom didn't flash, or what error you got while installing the rom. And second is you need to install magisk manager to gain root access with twrp, by enabling the root access in developer option won't give you root access you need to install it via twrp.
Click to expand...
Click to collapse
I tried flashing them through TWRP. They all were based on Oreo 8.1. I tried Lineage, Invicta, Viper, RR and pixel expirience. As for the error, i don't really know what error it was but Lineage and RR were stuck on the boot loader and the rest just didnt flash.....
Astitva_ said:
I tried flashing them through TWRP. They all were based on Oreo 8.1. I tried Lineage, Invicta, Viper, RR and pixel expirience. As for the error, i don't really know what error it was but Lineage and RR were stuck on the boot loader and the rest just didnt flash.....
Click to expand...
Click to collapse
Chance are you are using the wrong twrp
64bit roms require you to use the 64bit twrp
See the first post of the lineageos thread for the 64bit twrp
Or you can test out the 64bit twrp that uses my encryption edits
https://forum.xda-developers.com/g5/help/help-testing-build-twrp-arm64-t3874472
If you want to root flash the latest version of Magisk and then install the magisk manager app manually if it's not installed
TheFixItMan said:
Chance are you are using the wrong twrp
64bit roms require you to use the 64bit twrp
See the first post of the lineageos thread for the 64bit twrp
Or you can test out the 64bit twrp that uses my encryption edits
https://forum.xda-developers.com/g5/help/help-testing-build-twrp-arm64-t3874472
If you want to root flash the latest version of Magisk and then install the magisk manager app manually if it's not installed
Click to expand...
Click to collapse
I'm sorry but i didn't get what you said. I'm really sorry but I'm really a noob. I would like it if you helped me out a bit....
Astitva_ said:
I'm sorry but i didn't get what you said. I'm really sorry but I'm really a noob. I would like it if you helped me out a bit....
Click to expand...
Click to collapse
All custom oero roms for this device are 64 bit
You need to flash them with a twrp that has been compiled for 64bit twrp use
My official twrp is for 32bit roms only and will not flash 64bit roms - you will get error 7 or I think error 256 or something like that
Flash the 64bit twrp if you want to flash 64bit custom roms - process is the same as if flashing the official twrp via fastboot but you obviously use the 64bit twrp image instead
As mentioned link to 64bit twrp is on the lineageos 15.1 thread first page or try the version in the link I posted in previous post
TheFixItMan said:
All custom oero roms for this device are 64 bit
You need to flash them with a twrp that has been compiled for 64bit twrp use
My official twrp is for 32bit roms only and will not flash 64bit roms - you will get error 7 or I think error 256 or something like that
Flash the 64bit twrp if you want to flash 64bit custom roms - process is the same as if flashing the official twrp via fastboot but you obviously use the 64bit twrp image instead
As mentioned link to 64bit twrp is on the lineageos 15.1 thread first page or try the version in the link I posted in previous post
Click to expand...
Click to collapse
So, I can directly flash the new twrp like i flash the roms right?? Also, what can i do for project treble in my phone...i mean, i cant find redwolf for moto g5(cedric)
Astitva_ said:
So, I can directly flash the new twrp like i flash the roms right?? Also, what can i do for project treble in my phone...i mean, i cant find redwolf for moto g5(cedric)
Click to expand...
Click to collapse
You flash twrp via fastboot commands
fastboot flash recovery recovery.img
Although it is technically possible to flash twrp via twrp if you select image flash & select recovery as the image you are flashing but I'd stick with the fastboot method
I don't own this device anymore so no idea about files that are no longer available
TheFixItMan said:
You flash twrp via fastboot commands
fastboot flash recovery recovery.img
Although it is technically possible to flash twrp via twrp if you select image flash & select recovery as the image you are flashing but I'd stick with the fastboot method
I don't own this device anymore so no idea about files that are no longer available
Click to expand...
Click to collapse
Okay, so i flashed the twrp...but still therom isnt flashing....should i upload the rom so that you can see it?
basically;
if a rom has [64bit] in the title, then it's 64 bit, if it is then you need a 64bit recovery which you can easily find on the forum. you dont even need to know what that means.
Astitva_ said:
Okay, so i flashed the twrp...but still therom isnt flashing....should i upload the rom so that you can see it?
Click to expand...
Click to collapse
Just link to the rom on xda and give the twrp error
The rom either isn't for this device eg you are trying to flash a moto g5 plus or s rom or you are using the wrong twrp or you haven't formatted system data cache before flashing the rom
I try to install the recovery stock but it does not load, it stays on the fastboot screen, can someone help me?
Thank you
Recovery stock: https://anonfile.com/PcuaWeScmf/recovery_img
th3binary said:
I try to install the recovery stock but it does not load, it stays on the fastboot screen, can someone help me?
Thank you
Recovery stock: https://anonfile.com/PcuaWeScmf/recovery_img
Click to expand...
Click to collapse
Dirty flash the current ROM that you are running and boot into system, then boot into recovery to check.
tnsmani said:
Dirty flash the current ROM that you are running and boot into system, then boot into recovery to check.
Click to expand...
Click to collapse
right now I have lineage OS 16, but I want to install oxygen OS 5.0.8, the problem is that I can not start the oxygen recovery stock, and I can not reinstall oxygen OS, because if it does not load the recovery, I can not do an installation by adb sideload
th3binary said:
right now I have lineage OS 16, but I want to install oxygen OS 5.0.8, the problem is that I can not start the oxygen recovery stock, and I can not reinstall oxygen OS, because if it does not load the recovery, I can not do an installation by adb sideload
Click to expand...
Click to collapse
Why not through TWRP?
Please be generous with information. Cryptic posts will not allow others to help you. What is your current setup, what have you tried, what are the steps taken, what are the results thereof etc?
tnsmani said:
Why not through TWRP?
Please be generous with information. Cryptic posts will not allow others to help you. What is your current setup, what have you tried, what are the steps taken, what are the results thereof etc?
Click to expand...
Click to collapse
let's see, the only problem I have is that I can not start the recovery of Oxygen OS to install Oxygen OS again, and I do not understand why ... twrp starts without problems, the file that I provide above is the last recovery Available stock that you could find to get back to Oxygen OS by adb sideload through your stock recovery
th3binary said:
let's see, the only problem I have is that I can not start the recovery of Oxygen OS to install Oxygen OS again, and I do not understand why ... twrp starts without problems, the file that I provide above is the last recovery Available stock that you could find to get back to Oxygen OS by adb sideload through your stock recovery
Click to expand...
Click to collapse
The stock recovery file which you have may not be the correct one. The link you have given doesn't work. I only get a blank page.
I still don't understand why you can't use TWRP for flashing the stock ROM.
tnsmani said:
The stock recovery file which you have may not be the correct one. The link you have given doesn't work. I only get a blank page.
I still don't understand why you can't use TWRP for flashing the stock ROM.
Click to expand...
Click to collapse
you have to give it twice to download to download the recovery, when I try to install the rom oxygen OS downloaded from the one plus website, it seems to be installed, but when I go to restart it tells me that there is no operating system installed
I am currently on aex 5.2 ,a simple normal rom who has nothing with vendor or factory partition,
Can anybody tell the steps to install it, current recovery on my device is twrp 3.3.0.1
vickyfule said:
I am currently on aex 5.2 ,a simple normal rom who has nothing with vendor or factory partition,
Can anybody tell the steps to install it, current recovery on my device is twrp 3.3.0.1
Click to expand...
Click to collapse
Simply flash the required ROM, no extra steps needed
visheshjain25 said:
Simply flash the required ROM, no extra steps needed
Click to expand...
Click to collapse
I think it is a treble rom so i have to fladh vendor and then treble supported twrp ?
vickyfule said:
I think it is a treble rom so i have to fladh vendor and then treble supported twrp ?
Click to expand...
Click to collapse
All that has been reversed, no need to flash those things now and as far as your TWRP is concerned I think it is treble so you can proceed
I have a Pixel 3 XL and I was following this Guide to root it.
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
When I get to part 2-10 (The part to install Magisk) my phone wont boot into the OS. Instead I end up back at TWRP. If I reinstall TWRP from my download folder or restore a back up I can get back into the OS. I still have TWRP installed but no root. I know I'm doing something wrong but I'm not sure. Like I've said TWRP is install but not Magisk.
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
ktmom said:
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
Click to expand...
Click to collapse
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
ktmom said:
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
Click to expand...
Click to collapse
I tried the easiest method first, which was installing the Magik app and flashing the zip, I got the following error,
Device platform: arm64-v8a
copying image to cache
Unpacking boot image
! Unsupported/Unkown image format
! Installation failed
I'll try flashing the stock image, but should I flash twrp again after the image? I've done this before in the past because some phones require it as part of the rooting instructions. Does this order sound right, flash stock image, reboot, flash twrp reboot, then Magisk?
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Just tried the beta version (19.4) and I'm stuck in a standard bootloop. I'll try and get it into recovery.
No worries, I forgot to mention that I restored a back up
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Surely not on Pie. I'm using 19.3 on the last Pie.
ktmom said:
Surely not on Pie. I'm using 19.3 on the last Pie.
Click to expand...
Click to collapse
I'm on pie, but your first suggestion was the fix. I had to flash the factory img before doing everything else. I just had to put a little more time a side and not be lazy.
Hey guys. Until the RR dev makes a thread, this will continue to stay in Discussion. I am NOT the dev for RR. So wanted to get the rom more exposure.
Rom: https://sourceforge.net/projects/resurrectionremix-ten/files/instantnoodlep/
Kernel source: https://github.com/luk1337/android_kernel_oneplus_sm8250
Changelog: https://get.resurrectionremix.com/ten/changelog/Changelog.txt
Be on OOS 10(both slots)(local upgrade last OOS 10 for slot b)
Flash twrp both slots(https://downloads.sourceforge.net/p...=cfhcable&r=https://forum.xda-developers.com/)
Flash rom
Reboot twrp
Wipe userdata(always a must when switching between OOS and custom)
(Optional) install kernel and magisk
Reboot
**UPDATE** this flash instructions work. I use these and ONLY these instructions. If you have a better way, good for you, but if you can't get it to boot, use these.
***UPDATE 2*** if you have installed Android 11 prior to installing this rom, you must msm back to OOS 10 and local upgrade OOS 10 again to slot b and only use Android 10 recovery
Nice one. :good:
Is twrp ok to wipe now? Or would we need stock to do so?
If the latter then may be worth booting twrp and retaining stock recovery to wipe.
Good to see a ROM thread for this.
Excellent.
My thanks to the dev too, it's appreciated.
dladz said:
Nice one. :good:
Is twrp ok to wipe now? Or would we need stock to do so?
If the latter then may be worth booting twrp and retaining stock recovery to wipe.
Good to see a ROM thread for this.
Excellent.
My thanks to the dev too, it's appreciated.
Click to expand...
Click to collapse
I've had no issues using latest twrp
jamescable said:
I've had no issues using latest twrp
Click to expand...
Click to collapse
Does it have oos cam?
areyouanand said:
Does it have oos cam?
Click to expand...
Click to collapse
Honestly, don't know. I don't use OOS can, but I don't think so
jamescable said:
Hey guys. Until the RR dev makes a thread, this will continue to stay in Discussion. I am NOT the dev for RR. So wanted to get the rom more exposure.
Rom: https://get.resurrectionremix.com/?dir=ten/instantnoodlep
Kernel source: https://github.com/luk1337/android_kernel_oneplus_sm8250
Be on OOS
Flash twrp both slots
Flash rom
Reboot twrp
Wipe userdata(always a must when switching between OOS and custom)
(Optional) install kernel and magisk
Reboot
Click to expand...
Click to collapse
Why to boot to twrp after flashing the rom?
We can just boot the twrp( not flash it)
Flash rom
Flash magisk ( optional)
Format data
Reboot
It should be mentioned that these builds are blind builds. The Dev doesn't own the device.
Kollachi said:
It should be mentioned that these builds are blind builds. The Dev doesn't own the device.
Click to expand...
Click to collapse
Correct but doesn't matter. I tested first few builds before they were released and now alots of people used them. They aren't beta or alpha but stable. So? What's your point?
cultofluna said:
Why to boot to twrp after flashing the rom?
We can just boot the twrp( not flash it)
Flash rom
Flash magisk ( optional)
Format data
Reboot
Click to expand...
Click to collapse
8pro has a recovery partition. So unless you flash a rom that overwrites twrp with another recovery (stock OOS, etc) then twrp will remain after rom flash
jamescable said:
Correct but doesn't matter. I tested first few builds before they were released and now alots of people used them. They aren't beta or alpha but stable. So? What's your point?
Click to expand...
Click to collapse
It's simple. If people run into issues or whatever he can't probably fix it. It was the same with treskmod for example.
Kollachi said:
It's simple. If people run into issues or whatever he can't probably fix it. It was the same with treskmod for example.
Click to expand...
Click to collapse
[Mod Edit] Telegram link removed.
jamescable said:
[Mod Edit] Telegram link removed.
Click to expand...
Click to collapse
He is blind building from latest los source that's all. Respect him for doing that, but it's not 100% guarantee for a fully working rom.
jamescable said:
8pro has a recovery partition. So unless you flash a rom that overwrites twrp with another recovery (stock OOS, etc) then twrp will remain after rom flash
Click to expand...
Click to collapse
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
cultofluna said:
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
Click to expand...
Click to collapse
1. Is NOT useless. That is for clean flashing which is ALWAYS recommend by every dev. When you dirty flash, it's at your own peril.
And 2. Once again. The OnePlus 8 pro has a recovery partition. So twrp does not get overwritten when you flash a rom. Like on 7 pro, we had to flash twrp after every rom flash. Not needed on 8 pro.
cultofluna said:
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
Click to expand...
Click to collapse
1. I think he meant to say reboot to recovery and not boot the twrp.img.
2. Yes you can boot twrp only. That's what im doing since OP7. But you will need to do this everytime you wanna flash something with twrp.
jamescable said:
1. Is NOT useless. That is for clean flashing which is ALWAYS recommend by every dev. When you dirty flash, it's at your own peril.
And 2. Once again. The OnePlus 8 pro has a recovery partition. So twrp does not get overwritten when you flash a rom. Like on 7 pro, we had to flash twrp after every rom flash. Not needed on 8 pro.
Click to expand...
Click to collapse
On your flashing instructions you said. "flash twrp on both slots"
So im asking one more time,... why not just to boot the twrp img on fastboot and flash the rom...
What is this about recovery partition ... everybody knows that the 8 pro has a separate recovery partition
EDIT..Reboot to twrp after flashing the Rom is useless...
I insist. .dont needed
cultofluna said:
On your flashing instructions you said. "flash twrp on both slots"
So im asking one more time,... why not just to boot the twrp img on fastboot and flash the rom...
What is this about recovery partition ... everybody knows that the 8 pro has a separate recovery partition
EDIT..Reboot to twrp after flashing the Rom is useless...
I insist. .dont needed
Click to expand...
Click to collapse
It's in the pic I uploaded. Even the twrp dev said to flash it. So you won't have to fastboot boot anymore. Once you flash it. It's on your phone and won't go away when you reboot recovery
Every phone used to have a boot(kernel) partition, system partition, modem/radio partition, bootloader, userdata, and a few other INCLUDING recovery partition. Recently, the recovery was missing but now it's back. So we no longer have to have to boot twrp but flash it
Hello everyone, I need help installing this rom please, I have the latest TWRP 3.4.0-14-Mauronofrio installed in both slots, latest stable OOS in both slots, I have an IN2025 and for some reason I get this error with TWRP. Thanks in advance guys.
oscarmaldonado said:
Hello everyone, I need help installing this rom please, I have the latest TWRP 3.4.0-14-Mauronofrio installed in both slots, latest stable OOS in both slots, I have an IN2025 and for some reason I get this error with TWRP. Thanks in advance guys.
Click to expand...
Click to collapse
That is strange. I also have 2025. Try moving the rom to phone instead of usb device. Since this is an updated twrp may be an issue. However. I did NOT have OOS installed on both slots. I flashed latest OOS full rom, used OOS recovery to wipe data. Booted and then flashed twrp to both slots, flashed RR, reboot recovery and flashed magisk