Hi guys,
How do i update the pixel experience rom from android 12 to 13? is it just flash it through recovery and adb sideload, or is there any necessary step i should do before flashing it? like updating the recovery maybe? Im using pixel experience custom recovery and my device is unroot, only bootloader is unlocked
Any answers would be appreciated, thanks!
Maybe ask in an appropriate thread, but you could try dirty flash, stock is flashed the same way.
Odeya said:
Hi guys,
How do i update the pixel experience rom from android 12 to 13? is it just flash it through recovery and adb sideload, or is there any necessary step i should do before flashing it? like updating the recovery maybe? Im using pixel experience custom recovery and my device is unroot, only bootloader is unlocked
Any answers would be appreciated, thanks!
Click to expand...
Click to collapse
Backup all data and dirty flash. If you get errors, clean flash is helpful
Since it's a jump from one Android version to another, it's better to clean flash. Although, a dirty flash should still be possible once you wipe OS.
There should be a new, updated recovery file to flash as well. Tbh, the jump from A12 to 13 is not as big as the previous upgrades, with not much gains.
Related
I'm trying to install LineageOS and I am pretty much stuck on one part. I'm on stock currently and do not have two but my device is unlocked. Now my question is if I need to flash twrp that is given in the LineageOS thread and then reboot into recovery and flash the ROM+ GApps or if I need to flash twrp compatible with EMUI5 then flash LineageOS+ GApps and finally flash the twrp that is compatible with LineageOS giving in that thread... Before anyone says that if I'm confused I shouldn't be flashing Roms I'd like to say I have tons of experience doing so but this is troubling me and I just rather ask a question if anyone has an answer to it before I pull the trigger and just do it.
Hello guys is there anyone willing to help me out?
Im long term HTC user in the past 15 Plus years i was flshing whatever i want and im familiar with this but i switched to Pixel 2 and i want to clear for myself few things prior before to brick it.
I also read this guide: https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
But its seems like the thread is not updated and some users mention problems with flashing Magisk etc.
Im fully Stock locked bootloader with the latest Android Pie from 5 January 2018
The Pixel i use is Google Edition worlwide version not loocked to any network etc.
The main reason to want to Bootloader unlock it is because i need the Magisk in order to be able to flash and use few of the must have for me apps that i use all the time.
1st is SAURON audio - without Magisk and TWRP this is not posible.
2nnd few additional Magisk modules that i use non stop in the past few years.
What is not clear for me is the steps and exactly the second steb with Flashing Flashing factory images?!
In HTC i need to get the bootloader unlock S-OFF is i want and flash a TWRP in this case i can flash on top Magisk so here is different and not very clear for me as well.
When im now on the latest Android version from 5 January do i need still to flash FACTORY IMAGE after unlocking the bootloader?
Is anyone willing to help to clear the things out before to mess the device.
Thanks in advance
tsalta said:
Hello guys is there anyone willing to help me out?
Click to expand...
Click to collapse
Hi If you just want to unlock bootloader, there is no reason to flash factory image again. Just allow unlock bootloader in developer options, reboot to bootloader and run fastboot flashing unlock, this will fully wipe/factory reset your device.
Now you could boot/flash TWRP and install magisk.
When will be new monthly update available, flash it with help of this thread:
Code:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
Good luck :good:
somin.n said:
Hi If you just want to unlock bootloader, there is no reason to flash factory image again. Just allow unlock bootloader in developer options, reboot to bootloader and run fastboot flashing unlock, this will fully wipe/factory reset your device.
Now you could boot/flash TWRP and install magisk.
When will be new monthly update available, flash it with help of this thread:
Code:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
Good luck :good:
Click to expand...
Click to collapse
Thank you for the info.
So this mean i dont need to flash Image if im with the latest stock Version.
I prefer to stay stock just miss some Magisk modules thats why i wondering what to do.
Can i flash just a Kernel for example KiriSakura after unlock the bootloader and install TWRP just to flash Kiri Kernel with the stock rom im now and other Magisk stuffs like Sauron etc.
Thanks again
Hi exactly, if you run latest stock you havn't flash it again after bootloader unlock.
If you want to petmanently flash twrp, you have to do it before flashing magisk, othetwise you willn't be able to boot os only twrp.
Is it possible to downgrade back to Oreo?
I know there is ARB, but I read that some users are able to get back to 8.1 from 9.0
Everytime I try to flash an 8.1 Rom (Global Stable 10.2.2.0) via Fastboot, I brick my Phone and can only flash a PIE rom (Global Stable 10.3.2.0) to make it work again.
If I am missing something and it is somehow possible, any help would be highly appreciated.
You can try to flash oreo fastboot rom with mi authorized account. Maybe it works, i have tried and tested with RN5(whyred), not tried with RN6(tulip) yet.
As both devices shares same chipset, Hopefully it works
I got it working again. I just flashed Global Stable 10.3.2.0 with Android Pie via fastboot. After that, I installed TWRP and installed Global Stable 10.2.2.0 with Android 8.1 via Recovery and Wiped my phone.
I have no idea why it is working with twrp and not with fastboot, but whatever. I now have my Android 8.1 back even with all these ARB stuff :good:
MartinDaDon said:
I got it working again. I just flashed Global Stable 10.3.2.0 with Android Pie via fastboot. After that, I installed TWRP and installed Global Stable 10.2.2.0 with Android 8.1 via Recovery and Wiped my phone.
I have no idea why it is working with twrp and not with fastboot, but whatever. I now have my Android 8.1 back even with all these ARB stuff :good:
Click to expand...
Click to collapse
Hi there, folk. I have the same issue since months ago and cannot get downgrade. Can u please be more specific within :
-which TWRP you used (if you can share the post link)
-did you wiped all partitions ? System, dalvik cache, etc?
I'd to be grateful with your help.
kathsfernan said:
Hi there, folk. I have the same issue since months ago and cannot get downgrade. Can u please be more specific within :
-which TWRP you used (if you can share the post link)
-did you wiped all partitions ? System, dalvik cache, etc?
I'd to be grateful with your help.
Click to expand...
Click to collapse
hi there,
sorry for the late reply.
1. TWRP was the official: https://eu.dl.twrp.me/tulip/
2. After flashing the Android 8.1 rom through twrp, i used "format data" and did a reboot.
hope i was able to help
Hey everyone,
I have an unlocked OP 7 pro.
Lately, I decided to go back to custom roms after a year or so of sticking with rooted stock.
I've tried to flash Pixel Experience & Flamingo OS and while both completed successfully, they won't pass the bootloader.
Then I tried to install crDroid using the script the author has provided and suddenly it does boot to recovery and I was able to flash the rom completely and boot to it.
Has anyone encountered such a case and has a workaround for it?
Thanks
E1adi said:
Hey everyone,
I have an unlocked OP 7 pro.
Lately, I decided to go back to custom roms after a year or so of sticking with rooted stock.
I've tried to flash Pixel Experience & Flamingo OS and while both completed successfully, they won't pass the bootloader.
Then I tried to install crDroid using the script the author has provided and suddenly it does boot to recovery and I was able to flash the rom completely and boot to it.
Has anyone encountered such a case and has a workaround for it?
Thanks
Click to expand...
Click to collapse
Just wanna to let any future visitors of this thread how I've solved it.
1. I use the msmtool to reflash stock and lock the bootloader on the way. (Here)
2. I installed OTA stock updates.
3. I unlocked the bootloader again
4. Voila, now I was able to flash stuff.
Good luck everyone
Sorry, I couldn't find the answer. I installed lineage 20 on my one plus 9. I also installed the custom recovery required by lineage. I want to try out the pixel rom but what do I do about the custom lineage recovery? Do i use msm tools to restore it first? or can i install the unofficial twrp i saw on this forum instead or is there a stock recovery I can easily find to change it back? Thanks for any help.
gisted said:
Sorry, I couldn't find the answer. I installed lineage 20 on my one plus 9. I also installed the custom recovery required by lineage. I want to try out the pixel rom but what do I do about the custom lineage recovery? Do i use msm tools to restore it first? or can i install the unofficial twrp i saw on this forum instead or is there a stock recovery I can easily find to change it back? Thanks for any help.
Click to expand...
Click to collapse
I just made this same switch now back on stock waiting for 13.1 Download dtbo,vendor_boot,boot from pixel extended. Flash all 3 In fastboot. Reboot recovery wipe data sideload Pe
Thanks for the help!
gisted said:
Sorry, I couldn't find the answer. I installed lineage 20 on my one plus 9. I also installed the custom recovery required by lineage. I want to try out the pixel rom but what do I do about the custom lineage recovery? Do i use msm tools to restore it first? or can i install the unofficial twrp i saw on this forum instead or is there a stock recovery I can easily find to change it back? Thanks for any help.
Click to expand...
Click to collapse
OnePlus 9 does not have a dedicated recovery partition anymore (most modern phones don't have anymore). Instead, recovery now resides inside boot, meaning they share the same kernel. That's the reason every ROM instruction says to flash the provided boot, vendor_boot and dtbo images. Note that these 3 images are the same found in that particular ROM zip. Anyway, the point is that when you flash boot, the recovery is flashed too.
So, in your case, even if you are on LineageOS 20, and you can access LineageOS recovery, you can just go ahead and do a factory reset and flash the Pixel ROM through adb sideload. After that, boot, vendor_boot and dtbo will be automatically flashed/updated to Pixel's. But the recommended way is still to make sure you first flash those given 3 images before going to recovery and proceeding with factory reset and flashing.