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?
Related
I got the 64GB Sandstone Black A0001 device.. On the package it says 64GB and the back cover of the device is Sandstone Black,
and not White. BUT!! When I go to settings>about>storage it says that total memory is only 12.14GB... What is happening here?
Am I doing something wrong? The IMEI of the device is the same as on the package... So what happened?
Did you buy it through and invite? If not where did you buy it from? Does it have the CyanogenMod branding/logo on the back ?
If the answer(s) for the questions above are no then you have a Chinese variant instead of the international variant and the seller probably flashed CM on the device himself and by mistake used a 16GB version image instead of the 64GB image.
dilgit said:
I got the 64GB Sandstone Black A0001 device.. On the package it says 64GB and the back cover of the device is Sandstone Black,
and not White. BUT!! When I go to settings>about>storage it says that total memory is only 12.14GB... What is happening here?
Am I doing something wrong? The IMEI of the device is the same as on the package... So what happened?
Click to expand...
Click to collapse
Your not the first. Locate the factory images and flash the 64gb one. You will be good to go. Rest assured it truly is 64gb as its the only one in production.
Thanks. I actually bought the device second hand from a friend and it had ColorOS installed on it which I replaced with Cynogenmod CM11S.
Than I gave the device to my daughter as a present... OK - are there two different versions of the original CM11s file to flash? One for 64GB and
the other for 16GB?
dilgit said:
Thanks. I actually bought the device second hand from a friend and it had ColorOS installed on it which I replaced with Cynogenmod CM11S.
Than I gave the device to my daughter as a present... OK - are there two different versions of the original CM11s file to flash? One for 64GB and
the other for 16GB?
Click to expand...
Click to collapse
Yes correct. Just download and flash the file "cm-11.0-XNPH33R-bacon-signed-fastboot.zip" from the official Cyanogenmod/oneplus site HERE and you'll be good to go. You could search for the 64GB rom version on XDA but i personally like getting my roms from the site directly. The image on the official site is for both sizes.
S M G said:
Yes correct. Just download and flash the file "cm-11.0-XNPH33R-bacon-signed-fastboot.zip" from the official Cyanogenmod/oneplus site HERE and you'll be good to go. You could search for the 64GB rom version on XDA but i personally like getting my roms from the site directly. The image on the official site is for both sizes.
Click to expand...
Click to collapse
Thanks. So in order to flash the original file I have to root the device and flash recovery and than flash the original zip file? Actually I think that this is the
file I used to convert from ColorOS to CM11s...
dilgit said:
Thanks. So in order to flash the original file I have to root the device and flash recovery and than flash the original zip file? Actually I think that this is the
file I used to convert from ColorOS to CM11s...
Click to expand...
Click to collapse
No. don't try to flash that file with a custom recovery as it is a fastboot flashable zip. Search for a guide and you'll be good to go
This thread explains the process and requirements rather good.
Yeah as @DuckMcQUack said this is the fastboot image so you cant flash it through recovery. If you want to flash through recovery you should have a look around the forums for the recovery flashable images.
DuckMcQUack said:
No. don't try to flash that file with a custom recovery as it is a fastboot flashable zip. Search for a guide and you'll be good to go
Click to expand...
Click to collapse
Thanks again. I'll do that...
S M G said:
This thread explains the process and requirements rather good.
Yeah as @DuckMcQUack said this is the fastboot image so you cant flash it through recovery. If you want to flash through recovery you should have a look around the forums for the recovery flashable images.
Click to expand...
Click to collapse
I would go the fastboot route as i've read that recovery flashable zips have issues with ota updates :cyclops:
DuckMcQUack said:
I would go the fastboot route as i've read that recovery flashable zips have issues with ota updates :cyclops:
Click to expand...
Click to collapse
+1
I prefer fastboot also. Hasn't let me down.
S M G said:
+1
I prefer fastboot also. Hasn't let me down.
Click to expand...
Click to collapse
So I'd better download the .img file instead? And do I have to go through the wipes in the stock recovery?
dilgit said:
So I'd better download the .img file instead? And do I have to go through the wipes in the stock recovery?
Click to expand...
Click to collapse
IMHO, Yes.
The last command during the fastboot flash (from earlier link) will actually wipe your device so no need to do it through recovery.
"fastboot update -w cm-11.0-XNPH25R-bacon-signed-fastboot.zip" ((-w = Wipe :good)
PS: Btw note that the filename in the last command will be different e.g. XNPH25R should be XNPH33R, since your flashing the newer image...
S M G said:
IMHO, Yes.
The last command during the fastboot flash (from earlier link) will actually wipe your device so no need to do it through recovery.
"fastboot update -w cm-11.0-XNPH25R-bacon-signed-fastboot.zip" ((-w = Wipe :good)
PS: Btw note that the filename in the last command will be different e.g. XNPH25R should be XNPH33R, since your flashing the newer image...
Click to expand...
Click to collapse
Thanks again. So what is the .img file for?
dilgit said:
So I'd better download the .img file instead? And do I have to go through the wipes in the stock recovery?
Click to expand...
Click to collapse
dilgit said:
Thanks again. So what is the .img file for?
Click to expand...
Click to collapse
The entire Cyanogenmod 11S OS + GApps is contained within that single .zip file. Its just called a factory image not really a .img file.
An over simplified explanation: You are essentially formatting/wiping your PC and installing Windows from scratch.
I understand. Thank you very much...
dilgit said:
I understand. Thank you very much...
Click to expand...
Click to collapse
No problem, enjoy :good:
Have you been successful in flashing zip?
I actually found this thread widely helpful and informative. I was confused about the .img thing, too, until I read this. Many thanks
did u fix it?
So hi people. I have (or will soon have) a Nexus 6P. But I had a little free time and noticed TWRP was available for this device. So I decided to make a flashable version of the Nexus 5X's latest official factory image.
Downloads:
6.0.0 - MDB08I: LINK
Instructions:
Bro, it's a Nexus device. Nobody needs any instructions...Just flash to your hearts desire.
NOTE:
I do not own the device so I haven't tested it. BUT I am 80% sure it should work. Can some one confirm.
THIS ROM IS AN UNMODIFIED VERSION OF THE STOCK SYSTEM.IMG!!!
- Shawn
Reserved
is it just a flashable system.img?
k.s.deviate said:
is it just a flashable system.img?
Click to expand...
Click to collapse
It's a flashable zip...Not system.img...You flash it in TWRP
k.s.deviate said:
is it just a flashable system.img?
Click to expand...
Click to collapse
It's a flashable zip file.. TWRP.
Shawn5162 said:
It's a flashable zip...Not system.img...You flash it in TWRP
Click to expand...
Click to collapse
Exel said:
It's a flashable zip file.. TWRP.
Click to expand...
Click to collapse
i know its a twrp zip
What i meant was, is it just the system? nothing more nothing less. essentially just the system.img made into a fashable zip?
k.s.deviate said:
i know its a twrp zip
What i meant was, is it just the system? nothing more nothing less. essentially just the system.img made into a fashable zip?
Click to expand...
Click to collapse
Oh that's what you meant...The yes. It is purely stock unmodified
Shawn5162 said:
Oh that's what you meant...The yes. It is purely stock unmodified
Click to expand...
Click to collapse
cool, have you tried flashing an .img file with the latest TWRP?
k.s.deviate said:
cool, have you tried flashing an .img file with the latest TWRP?
Click to expand...
Click to collapse
You can only flash recovery.img and boot.img via TWRP
Not system.img
Shawn
Shawn5162 said:
You can only flash recovery.img and boot.img via TWRP
Not system.img
Shawn
Click to expand...
Click to collapse
thats what i wanted to hear.
added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up by reyscott1968
No one flashed this yet?
DespairFactor said:
No one flashed this yet?
Click to expand...
Click to collapse
I'm doing so right now. So far it is stuck on the Google emblem. I was already on this build and rooted. I am unfamiliar with anything but Samsung devices so please bear with me. TWRP asked if I wanted to root again before I rebooted and I said yes.
Edit: Been ten minutes and still stuck on Google emblem. Going to go back to stock and reroot.
Tulsadiver said:
I'm doing so right now. So far it is stuck on the Google emblem. I was already on this build and rooted. I am unfamiliar with anything but Samsung devices so please bear with me. TWRP asked if I wanted to root again before I rebooted and I said yes.
Edit: Been ten minutes and still stuck on Google emblem. Going to go back to stock and reroot.
Click to expand...
Click to collapse
Select no, reboot to recovery and flash supersu.
You don't need anything fancy to flash system.img, just boot to bootloader, and do a:
fastboot flash system system.img
I've done it several times to recover from bootloops after experimenting with /system.
dully79 said:
Select no, reboot to recovery and flash supersu.
Click to expand...
Click to collapse
Should I try it again? Is there anyone that can deodex this zip?
Edit: tried again. Same result. Stuck at Google emblem.
deodex, rooted, then exposed and GB^^ can we fast forward a few weeks so I can stop with all this waiting.
I can confirm that flashing this on my 5X results in a failure to boot. I've tried everything from flashing SuperSU to a full system format. I eventually resorted to using fastboot to flash system.img which resolved the issue.
What da heck man? Where's our N5x development? @sykopompos and our Frank N5x ?
Sorry for the nub question, but I'm stuck at the Google screen and I don't see a system.img anywhere in my SDK folder. Is this a separate file that needs to be downloaded? Where can I find this to flash in fastboot?
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.
Hello forum! I need help. After using the TWRP guide, I get a bootloop. Also, I tried installing a GSI (.img) file, but result is a bootloop. I used this GSI.
M1ST0R said:
Hello forum! I need help. After using the TWRP guide, I get a bootloop. Also, I tried installing a GSI (.img) file, but result is a bootloop. I used this GSI.
Click to expand...
Click to collapse
Maybe you need to flash vbmeta.img before first boot. Or try another GSI (verify using Treble Info app to know which variant you need)
What was the stock? Android 12 or 13?
Operating System Tester said:
What was the stock? Android 12 or 13?
Click to expand...
Click to collapse
Android 13. Stock by Samsung. CSC: XME; VER: A536EXXS5CWDA.
_allaie_ said:
flash vbmeta.img before first boot
Click to expand...
Click to collapse
i make it. that says in the TWRP guide.
verify using Treble Info app to know which variant you need
Click to expand...
Click to collapse
K, i try this app
but whats about bootloop after kernel flashing? and magisk too
I've checked, and I can say that the bootloop occurs after flashing TWRP_3.6.2 and disabling_vbmeta_R.
M1ST0R said:
I've checked, and I can say that the bootloop occurs after flashing TWRP_3.6.2 and disabling_vbmeta_R.
Click to expand...
Click to collapse
You need to flash the patched kernel;
1. Run multidisabler in TWRP terminal
2. Factory reset via TWRP
3. Reboot to recovery
4. ADB Push the kernel or use the sd card and flash it.
5. Boom, you can boot now.
hi, today i tried to install twrp on my phone but i got an error written in the attached image, any help?
Mmm, do they mean the AVB0 footer on the recovery image?
How did you flash the TWRP?
Was what you wrote as big as the partition?
Renate said:
Mmm, do they mean the AVB0 footer on the recovery image?
How did you flash the TWRP?
Was what you wrote as big as the partition?
Click to expand...
Click to collapse
i flashed the twrp with odin
Renate said:
Mmm, do they mean the AVB0 footer on the recovery image?
How did you flash the TWRP?
Was what you wrote as big as the partition?
Click to expand...
Click to collapse
Therefore? how can I do?
gerryscottiano said:
I flashed the twrp with odin
Click to expand...
Click to collapse
So, how big was the file that you flashed?
If what you flashed is smaller than the partition then the old AVB0 footer from the stock recovery is there.
That wouldn't agree with the position of the new AVB0 header for TWRP.
Or maybe you're supposed to defeat AVB somewhere?
See: https://android.googlesource.com/platform/external/avb/+/master/libavb/avb_footer.h
Disclaimer: I don't know Samsung and I've never run into trouble with AVB.
Renate said:
So, how big was the file that you flashed?
If what you flashed is smaller than the partition then the old AVB0 footer from the stock recovery is there.
That wouldn't agree with the position of the new AVB0 header for TWRP.
Or maybe you're supposed to defeat AVB somewhere?
See: https://android.googlesource.com/platform/external/avb/+/master/libavb/avb_footer.h
Disclaimer: I don't know Samsung and I've never run into trouble with AVB.
Click to expand...
Click to collapse
the file weighs 50 kb (I don't know what to do because it's the first time I enter the world of modding)
@gerryscottiano instead of asking this question in a new thread, it would be a better idea to ask in the thread where you got TWRP from.
Also, the TWRP image for this device is about 42MB, not 50KB.
i was wrong it is 50 mb, however i downloaded it on twrp official site
gerryscottiano said:
i was wrong it is 50 mb, however i downloaded it on twrp official site
Click to expand...
Click to collapse
Link for the file please and describe how you flashed it
V0latyle said:
Link for the file please and describe how you flashed it
Click to expand...
Click to collapse
https://dl.twrp.me/a30s/ the 3.7.0.img.tar
gerryscottiano said:
https://dl.twrp.me/a30s/ the 3.7.0.img.tar
Click to expand...
Click to collapse
Ok, and how did you flash it?
V0latyle said:
Ok, and how did you flash it?
Click to expand...
Click to collapse
so, i downloaded odin3, i put the file in the ap and i removed the auto reboot option and i connected the phone in download-mode
gerryscottiano said:
so, i downloaded odin3, i put the file in the ap and i removed the auto reboot option and i connected the phone in download-mode
Click to expand...
Click to collapse
Sounds good so far, then you try to reboot into recovery?
What exact version of Odin, and where did you download it from?
V0latyle said:
Sounds good so far, then you try to reboot into recovery?
What exact version of Odin, and where did you download it from?
Click to expand...
Click to collapse
when I try to reboot into recovery it gives me the error, the odin version is 3.14.4 and I installed it from here: https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
gerryscottiano said:
when I try to reboot into recovery it gives me the error, the odin version is 3.14.4 and I installed it from here: https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
Click to expand...
Click to collapse
AFAIK there is no 3.14.4, the latest Odin is 3.14.1.
I recommend you get rid of that and use the latest from this thread
V0latyle said:
AFAIK there is no 3.14.4, the latest Odin is 3.14.1.
I recommend you get rid of that and use the latest from this thread
Click to expand...
Click to collapse
is a modded version
gerryscottiano said:
is a modded version
Click to expand...
Click to collapse
That's fine, but what is in the XDA thread is what we consider safest.
V0latyle said:
AFAIK there is no 3.14.4, the latest Odin is 3.14.1.
I recommend you get rid of that and use the latest from this thread
Click to expand...
Click to collapse
I have a problem, I was trying to flash the recovery with the odin3 that you sent me but the oem block has been activated again and now that I have accepted to delete all the data it doesn't work for me in the firmware because there is the error of the recovery, how do I do?
gerryscottiano said:
I have a problem, I was trying to flash the recovery with the odin3 that you sent me but the oem block has been activated again and now that I have accepted to delete all the data it doesn't work for me in the firmware because there is the error of the recovery, how do I do?
Click to expand...
Click to collapse
You didn't lock the bootloader again, did you?