After all, aren't they just android images? Just have the updater download the generic image and update from there.
Mek101 said:
After all, aren't they just android images? Just have the updater download the generic image and update from there.
Click to expand...
Click to collapse
Hi...
its because of GSI Roms are very universal. For a great Range of Devices.
the most Devices need to get some fixes to become GSI Rom running.
In GSI Roms are no boot/ramdisk images integrate...so if you had root on your GSI Rom with magisk. You need to restore the Stock boot/ramdisk image to avoid bootloop.
solong
speedson
Is that because magisk needs to modify the system image?
ever wonder why brands don't use one os file for every devices, yeah that's why.
Related
Does anyone have a suggestion of the easiest way to update android to the latest March security update after installing TWRP and rooting with xceede's kernel as per oRAirwolf's guide?
I see there is an updated version of the kernel available but cannot work out how to update android system without OTA or custom ROMs.
Many thanks, sorry for my ignorance.
zezayer said:
Does anyone have a suggestion of the easiest way to update android to the latest March security update after installing TWRP and rooting with xceede's kernel as per oRAirwolf's guide?
I see there is an updated version of the kernel available but cannot work out how to update android system without OTA or custom ROMs.
Many thanks, sorry for my ignorance.
Click to expand...
Click to collapse
I would recommend downloading the latest factory image (or whatever version you want to update to) and flashing all of the partitions individually (EXCEPT USERDATA, as that will wipe your device). This is what I've done for years on all my Nexus devices when updating. You'll just have to re-flash TWRP and Xceed after upgrading. Shouldn't be too difficult. Some may say you really only need to flash certain partitions like system, boot, vendor etc., but I always find it better to err on the side of caution to make sure I don't bork anything in the process.
tl;dr
See Step 9 from this post from the Nexus 6P forums (obviously, make sure you replace the angler image files with the appropriate Pixel C images): http://forum.xda-developers.com/showpost.php?p=62924118&postcount=2
Success: - Thanks for the tips.
Downloaded MXC14G vendor image from google. (Link)
Unzipped system and vendor from the image.
Downloaded xceed's modified MXC14G boot image. (Link)
Flashed system, vendor and xceeds boot via fastboot.
Rebooted into system and let it all update.
Finally rebooted into TWRP to reflash Xposed / Viper etc.
zezayer said:
Success: - Thanks for the tips.
Downloaded MXC14G vendor image from google. (Link)
Unzipped system and vendor from the image.
Downloaded xceed's modified MXC14G boot image. (Link)
Flashed system, vendor and xceeds boot via fastboot.
Rebooted into system and let it all update.
Finally rebooted into TWRP to reflash Xposed / Viper etc.
Click to expand...
Click to collapse
What version of Viper are you using? There seem to be various version out there now, which have been modified for specific devices. Please post a link to the one that you are using? Any issues with it?
SmokinCharger said:
What version of Viper are you using? There seem to be various version out there now, which have been modified for specific devices. Please post a link to the one that you are using? Any issues with it?
Click to expand...
Click to collapse
I'm using the Loliviper flashable zip. Working really well.
zezayer said:
I'm using the Loliviper flashable zip. Working really well.
Click to expand...
Click to collapse
Which specific version. I noticed that there are various loliviper versions that are device specific
I used the nexus 5 version which was recommended for the 6p and other nexus phones http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Works well!
zezayer said:
I used the nexus 5 version which was recommended for the 6p and other nexus phones http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Works well!
Click to expand...
Click to collapse
Thank you.
Hi guys,
Like the majority I am eagerly waiting for the N img to come out.
I am currently on stock 6.0.1 rom with TWRP, ElementalX Kernel and SU root. I have been flashing system.img and vendor.img for all the security updates in the past.
It would be really helpful if someone can create a best practice guide for manually upgrading to N with customised elements intact.
chinesecooler said:
Hi guys,
Like the majority I am eagerly waiting for the N img to come out.
I am currently on stock 6.0.1 rom with TWRP, ElementalX Kernel and SU root. I have been flashing system.img and vendor.img for all the security updates in the past.
It would be really helpful if someone can create a best practice guide for manually upgrading to N with customised elements intact.
Click to expand...
Click to collapse
Already exists. Follow section 11 of the guide below. Manually update then reapply your mods once 7.0 factory image is available. In sure there are some changes that SuperSU will need to address for 7.0 final.
http://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
As the title suggests my xt1922-7 is possibly bricked. I unlocked the bootloader and rooted the phone with Magisk using the wonderful guides found here on this site. I installed the Disable_Dm-Verity_ForceEncrypt ZIP file and then I started to flash a custom GSI ROM. I think this is where I messed things up.
I thought to look for a ROM from this post (ROMs that run on the G6 Play [GSI]) but none of them have successfully booted. I just want to install to the stock rom so I can try again, but fastboot won't let me because the only latest image from lolinet I can find is before the April 2020 update.
Thoughts and suggestions? I'd really just like to be able to use the device without all the bloatware that Sprint installs.
EDIT: updating OP to link where I got the stock ROM
Additional Information
I have been trying to load A/B roms, so if that's an issue someone tell me I'm stupid so I can try only the ARM64 A-only or even the ARM A roms.
maybe it's fixed? Leaving here for posterity
OG_traugdor said:
I have been trying to load A/B roms, so if that's an issue someone tell me I'm stupid so I can try only the ARM64 A-only or even the ARM A roms.
Click to expand...
Click to collapse
I followed a guide I found HERE: [guide] [root] [oreo&pie] [jeter/aljeter] [twrp, decrypt, magisk] [stock firmware]
I just flashed everything but the bootloader and partition images and it seems to work okay. I got the boot logo and the "Hello Moto" sound so that's progress.
But why can I not flash other ROMS even with TWRP, etc? I can flash, but it just reboots to the bootloader! It's driving me crazy.
I want to flash custom rom on this phone, but without twrp I can't flash zip file, so I'm stuck with older version of gsi, without twrp, I can't root my devices for other Rom, so if anyone had skill to do so, please take your time and build twrp for people in needs, thanks
Which custom ROM?
Surely the custom ROM developer will have instructions of how to flash their custom ROM.....
elmor0 said:
Which custom ROM?
Surely the custom ROM developer will have instructions of how to flash their custom ROM.....
Click to expand...
Click to collapse
GSI can be flashed over ADB & TWRP thats what he means
nadejo said:
GSI can be flashed over ADB & TWRP thats what he means
Click to expand...
Click to collapse
GSI is a system image. On a dynamic partition device, that should be flashed through fastbootd. TWRP isn't needed for that.
TWRP will come, everyone must be patient...
Do you believe there will be any custom rom (not GSI) for this device?
As I research on previous models it doesn't seems like is ever going to happen
Not many but ROG 3 had a few custom ROMS...
Yesterday I posted a Beta TWRP for this device on Telegram. If you want to try it, here's the link:
EDIT: Removed TG link. See two posts down.
You barely need custom ROMs for these devices. The stock firmware is already quite lean and you can pretty much tweak, change and optimize them as you please. Signature spoofing works too...
Official TWRP is now available: https://forum.xda-developers.com/t/official-twrp-for-asus-rog-phone-6-6-pro-qualcomm-only.4518029/
Hello all!
I am an user of OnePlus 9 pro (T-mobile). I don't want the pink startup screen, and I found a lot of resources here can help me on it.
I have backup all my personal data. I have unlocked the sim and bootloader (using the official unlock_token.bin). What is the next step?
I am lost here since there are some different posts (and some posted last year, I am not sure if this still work or not).
Thank you all!
Flash a rom or custom oos
First off do not update to A12, make sure USB debug is enabled, auto updates disabled....do that and I hope you are on A11...if so, I have exactly what you need
FizzyAps said:
Flash a rom or custom oos
Click to expand...
Click to collapse
Any link for the rom?
TheGhost1951 said:
First off do not update to A12, make sure USB debug is enabled, auto updates disabled....do that and I hope you are on A11...if so, I have exactly what you need
Click to expand...
Click to collapse
I just unlocked the bootloader. It is now Android 11 with 05/01/2021 safety update. (11.2.4.4.LE5ACB). Could you please give the next step instruction?
run93 said:
I just unlocked the bootloader. It is now Android 11 with 05/01/2021 safety update. (11.2.4.4.LE5ACB). Could you please give the next step instruction?
Click to expand...
Click to collapse
Turned off auto updates? Yes? You can update to 11.2.9.9 then stop there, but make sure auto updates are turned off!!!!! Next step will to get root!
TheGhost1951 said:
Turned off auto updates? Yes? You can update to 11.2.9.9 then stop there, but make sure auto updates are turned off!!!!! Next step will to get root!
Click to expand...
Click to collapse
I would stay away from custom roms, I have seen too many people having problems. Secondly as of right now, A12 is buggy so that is why I stay with stock A11 from T-Mobile. With the setup I can give you, you can have any custom bootanimation and custom systemwide font you want.....
First off, download and install Magisk v25.2 app from GitHub website and install it to your phone. Next download the attached file to the folder with your platform files.....
Download Magisk from this link to your phone and install it.
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
Then download this link to your platform tools folder on PC...
Download twrp-3.6.2_11-0-lemonadep.img
Download page for twrp-3.6.2_11-0-lemonadep.img
dl.twrp.me
Then download this link to your phone storage...
17.63 MB file on MEGA
mega.nz
Let me know when you are down with these three steps!!!!! And are you updated to 11.2.9.9
TheGhost1951 said:
Let me know when you are down with these three steps!!!!! And are you updated to 11.2.9.9
Click to expand...
Click to collapse
Yes. I have successfuly updated 11.2.9.9 now.
I have a question that would this work? https://forum.xda-developers.com/t/le2127-oneplus-9-pro-custom-rom-t-mobile.4490195/
I am interested in Android 12 or even 13 if possible.
run93 said:
Yes. I have successfuly updated 11.2.9.9 now.
I have a question that would this work? https://forum.xda-developers.com/t/le2127-oneplus-9-pro-custom-rom-t-mobile.4490195/
I am interested in Android 12 or even 13 if possible.
Click to expand...
Click to collapse
If you are focused on upgrading to A12 or A12 then what I have will not work. As for the custom ROM, possible it may work, but you need to follow the steps to the letter. Any OP9P custom ROM will work from the XDA forums, the question is, will there be issues? Very possible. Good luck on your journey.....
TheGhost1951 said:
I would stay away from custom roms, I have seen too many people having problems. Secondly as of right now, A12 is buggy so that is why I stay with stock A11 from T-Mobile. With the setup I can give you, you can have any custom bootanimation and custom systemwide font you want.....
Click to expand...
Click to collapse
Been running nameless for over a month and a half now and haven't had a single out-of-the-ordinary problem that can't be fixed with a simple reboot. I have the T-Mobile variant here. Data works fine.
TheGhost1951 said:
If you are focused on upgrading to A12 or A12 then what I have will not work. As for the custom ROM, possible it may work, but you need to follow the steps to the letter. Any OP9P custom ROM will work from the XDA forums, the question is, will there be issues? Very possible. Good luck on your journey.....
Click to expand...
Click to collapse
I understand about the concerns about custom ROM. I am confused that is there any official Global or EU ROM available ?
run93 said:
I understand about the concerns about custom ROM. I am confused that is there any official Global or EU ROM available ?
Click to expand...
Click to collapse
Stock.....but you need to be rooted, TWRP installed and then install the stock ROM zip in twrp.
TheGhost1951 said:
Stock.....but you need to be rooted, TWRP installed and then install the stock ROM zip in twrp.
Click to expand...
Click to collapse
Thank you for all the help today! I think I did something wrong. I successfully get TWRP (directly boot, not recovery since it is failed), and then get my phone bricked flashing the rom lineageos... Now I am trying to unbrick it...
run93 said:
Thank you for all the help today! I think I did something wrong. I successfully get TWRP (directly boot, not recovery since it is failed), and then get my phone bricked flashing the rom lineageos... Now I am trying to unbrick it...
Click to expand...
Click to collapse
Bricked as in black screen? Or does it boot to fastboot? What version of lineage are you trying to run? And what OOS were you on? You need to be on OOS 12 to run lineage 19. And twrp is not the recovery to use for that.
Look before you leap.....read read read and make sure to follow ALL steps 1step at a time.....