Related
Hello all,
So I originally had unlocked my bootloader and installed a ROM but determined that I would rather have stock so I reverted to the stock ROM and re-locked my bootloader. However, I attempted to update my OS as prompted in the OS and I received a failure while trying to install the 1MB update and now I have no bootable OS so I know now that I have to restore again. I was wondering how I can prevent this again or if this was just a bad case?
I downloaded and used the stock image files from this post: http://forum.xda-developers.com/showthread.php?t=1998802
Could it be that the stock image doesn't check properly when installing the update? Any help is appreciated, thanks!
I could be wrong, but it's possible the factory images listed on that link are older, and there was a known issue with the older factory image for the N10 that caused the 4.2.1 update to fail.
I would recommend trying the factory image on Google's actual site: https://developers.google.com/android/nexus/images#mantaray
espionage724 said:
I could be wrong, but it's possible the factory images listed on that link are older, and there was a known issue with the older factory image for the N10 that caused the 4.2.1 update to fail.
I would recommend trying the factory image on Google's actual site: https://developers.google.com/android/nexus/images#mantaray
Click to expand...
Click to collapse
Thanks for the reply. I did previously download that factory image but then the fastboot commands to restore would be different no? I would have to update each partition manually?
fastboot flash boot
fastboot flash recovery
etc.
vs.
fastboot -w update image xxxxxx
Do you know if there is a guide available to update the OS using the factory image zip instead of the one listed on the post in my first post?
TheEmpyre said:
Thanks for the reply. I did previously download that factory image but then the fastboot commands to restore would be different no? I would have to update each partition manually?
Click to expand...
Click to collapse
Did you try just running the batch file included with the factory image? I believe the image off Google's site has additional commands that erase and/or format partitions first, flash the bootloader, restart back into bootloader, and then flash the image.
Edit: Here's the entire batch file:
Code:
@ECHO OFF
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-mantaray-jop40c.zip
echo Press any key to exit...
pause >nul
exit
TheEmpyre said:
Thanks for the reply. I did previously download that factory image but then the fastboot commands to restore would be different no? I would have to update each partition manually?
fastboot flash boot
fastboot flash recovery
etc.
vs.
fastboot -w update image xxxxxx
Do you know if there is a guide available to update the OS using the factory image zip instead of the one listed on the post in my first post?
Click to expand...
Click to collapse
I found this on google website:
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
Do I have to execute the ./fastboot command first (running Mac OS X)?
./fastboot flash-all.sh OR ./flash-all.sh ?
So strange thing, I just plugged it into my computer and it went through with the update and is functioning normally....insteresting. Nonetheless I guess I now know to just run the script if I need to flash stock
TheEmpyre said:
I found this on google website:
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
Do I have to execute the ./fastboot command first (running Mac OS X)?
./fastboot flash-all.sh OR ./flash-all.sh ?
Click to expand...
Click to collapse
in order to run the script, you just run ./flash-all.sh and it should work; the "fastboot" command on its own probably wouldn't do anything unless you have fastboot in PATH or whatever, but I'm not too familiar with the process on OS X (you might even have to have Android SDK installed)
It seems like there needed to be a thread dedicated to the issues that users have been seeing with this recent OTA, as it seems like there has been a few problems with updating if you ever used Motorola's Stock 5.1 Image, I'll begin by listing the steps necessary to successfully apply the OTA update regardless of what software version you are currently running, there is also a TWRP System Image for those of you who don't want to go through the fastboot process or return to stock
Official OTA Update Procedure
1) Use TWRP and make a full backup, then connect your phone to your computer and transfer the backup files to your computer
2) Reboot your phone into the bootloader, either by doing adb reboot-bootloader or the physical key combination (power off then press and hold the power and volume down key for ~4 seconds)
3) Download the Stock 5.1.0-LPA23.12-15.0 Image from here, do NOT use Motorola's Recovery Image to do this procedure, it will fail, as the hashes are not what the OTA is expecting for the system.img, and extract the contents to a folder on your computer
4) Download the OS relevant attached mfastboot zip and unzip the contents to the same folder on your computer (if you are having issues with mfastboot try reefuge's version and see if it helps!)
5) Open up a command prompt in the directory and use the following commands to flash the 5.1 Stock Image, erasing the userdata partition is not required but it is highly recommended, as you can easily restore the TWRP data partition after doing these steps if you want your personal data back
Code:
[B]not required, but recommended![/B]
mfastboot erase userdata
[B]required[/B]
mfastboot erase cache
mfastboot erase customize
mfastboot erase clogo
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot -P flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
6) Reboot your phone and do your initial 5.1 phone setup, and then immediately check for System Updates
7) Download the OTA and select to install the OTA
8) Rejoice in your completed OTA update, if the update fails to install, upload the recovery logs (or tell us the problem) and we will try to help!
9) You can now install TWRP and root if desired, and restore your TWRP data backup if you erased it beforehand
TWRP System Image
The TWRP System Image can be used instead of trying to apply the OTA update, this is a backup of my own phone's system partition after doing the OTA update, so it's already on 222.27.5...
Alright, after quite a bit of time uploading...
Here is the TWRP System Image
1) Download the Stagefright System 222.27.5 TWRP backup from the above link
2) Unzip the Stagefright System 222.27.5 folder to your computer
3) Copy the Stagefright System 222.27.5 folder to your phones internal storage, to the TWRP/BACKUPS/TA0000008VJ/ directory
4) Reboot your phone into recovery (TWRP)
5) Click Restore and select the Stagefright System 222.27.5 folder
6) Verify that the System partition is selected and then Swipe to Restore
7) Clear your cache
8) Boot into system and enjoy the new patch
_
Obligatory initial post
If this guide helped you at all, please show your support by either donating or telling people about how they can fix their device, pay it forward!
Please forgive me for being paranoid and not immediately running out and flashing some random OS image off the internet without first asking: what's the provenance of this OS image?
vtluu said:
Please forgive me for being paranoid and not immediately running out and flashing some random OS image off the internet without first asking: what's the provenance of this OS image?
Click to expand...
Click to collapse
The image is a Motorola signed Image, it's just not the same one that they have listed on the Recovery page, here is the details from the factory version info file inside the zip
Code:
BUILD REQUEST INFO:
SW Version: ghost_retail-user 5.1 LPA23.12-15 15 release-keysMSM8960PRO_BP_23255.138.89.00R
MBM Version: 30.BE
Modem Version: MSM8960PRO_BP_23255.138.89.00R
FSG Version: ONEBIN_BP_FSG_2.3.03_v127
Build Fingerprint: motorola/ghost_retail/ghost:5.1/LPA23.12-15/15:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 222.21.15.ghost_row.Retail.en.US
Model number: Moto X
Android Version: 5.1
Baseband Version: MSM8960PRO_BP_23255.138.89.00R
Build Number: LPA23.12-15
Build Date: Sat May 9 01:44:45 PDT 2015
OTHER MISC VERSION INFO:
Subsidy Lock Config: None
Blur Version: Blur_Version.222.21.15.ghost_row.Retail.en.US
Version when read from CPV: ghost_retail-user 5.1 LPA23.12-15 15 release-keys
I can confirm that the stock image linked in the original post actually allows the update to succeed. I originally tried flashing the "official" firmware (TMO_Retail_XT1053_5.1_LPA23.12-15.222.21.15.ghost_row.Retail.en.US.tgz) from Motorola's site , since I had used firmware from Motorola's page to go back to stock for previous OTAs successfully, but the Stagefright OTA failed to install over that "stock" version. After flashing over to the image from motofirmware.center (GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip), the OTA installed smoothly. Looks like someone at Motorola made a mistake with the Lollipop 5.1 firmware they uploaded to their official page.
mastarifla said:
The image is a Motorola signed Image, it's just not the same one that they have listed on the Recovery page, here is the details from the factory version info file inside the zip
Click to expand...
Click to collapse
Thanks for the clarification. :good:
EDIT: false alarm about LTE functionality deleted, my bad. Happy flashing!
Sorry for posting again, but would it be possible to create a zip file for this OTA that will flash in TWRP?
vtluu said:
Thanks for the clarification. :good:
Warning: it looks like I might have lost LTE support on T-Mobile US after applying the above flash (it shows me using HSPA+). Could be a false alarm or me being clueless. Will edit this post once I've verified one way or the other.
EDIT: confirmed, after putting back the image I got from the official Motorola page, I see "LTE" once again under "Cellular network type" in "SIM status", whereas with the above image it said "HSPA+". There might be a way of mixing and matching the radio firmware to fix that, but I haven't tried. At this point I think I'll just sit tight and wait for an update to the update from Moto.
Click to expand...
Click to collapse
T-Mobile default's data to HSPA+, then once you start using data it "revs up" to LTE, this is a network topology thing
You could also use the dialer code (*#*#4636#*#*) to verify that your preferred network type is set correctly, mine is set to LTE/GSM auto (PRL)
Thanks. Will try again. (The most painful part being having to wait 15-20 minutes for ART to recompile my 109 apps after each reflash.)
UPDATE: all good. And the OTA update worked as well.
AaronCompNetSys said:
Sorry for posting again, but would it be possible to create a zip file for this OTA that will flash in TWRP?
Click to expand...
Click to collapse
I think all that has to be done for that is to remove the fingerprints from the flash script right?
If so, here you can try this version in TWRP... I didn't remove the patch hash checks, so if you used the Motorola Image you will still fail when flashing
mastarifla said:
I think all that has to be done for that is to remove the fingerprints from the flash script right?
If so, here you can try this version in TWRP... I didn't remove the patch hash checks, but theoretically they could be removed, but that seems quite risky...
Click to expand...
Click to collapse
I just tried it and it failed to install with TWRP. Bummer! Thanks for trying.
Being on Motorola Stock 5.1 image I flashed stock image linked in OP using RSD Lite. I did not erased Userdata during flash. Afer that OTA installed just fine.
sisterchick said:
I just tried it and it failed to install with TWRP. Bummer! Thanks for trying.
Click to expand...
Click to collapse
When did it fail? Was it due to the sha-1 mismatch? Or was it not even able to begin?
If it was the mismatch, then you would have gotten the same error with the stock recovery, which is resolved by flashing the 5.1 stock image that I linked to in the OP, you could also try removing the hash checks in the build-script, but that would be somewhat risky-ier
Al936 said:
Being on Motorola Stock 5.1 image I flashed stock image linked in OP using RSD Lite. I did not erased Userdata during flash. Afer that OTA installed just fine.
Click to expand...
Click to collapse
Awesome, I added to the OP that you don't need to wipe your data partition but it's still highly recommended
Do I need to unzip the pack I downloaded? For some reason system.img won't unzip. I keep getting an error that says "CRC failed in 'system.img". File is broken." I'm using 7zip to try to extract the files.
Shemlon said:
Do I need to unzip the pack I downloaded? For some reason system.img won't unzip. I keep getting an error that says "CRC failed in 'system.img". File is broken." I'm using 7zip to try to extract the files.
Click to expand...
Click to collapse
You should unzip the .zip, but you should not "unzip" the .img. The .img is a binary file that should stay as is (don't try to open it).
Alright I made a version of the update.zip without the patch checks
Edit: Unfortunately no luck as the patching cant be forced on the Motorola Image, as the places where they patch seem to be different than the other zip's system image
Will I need to reinstall TWRP and reroot my phone when I'm done? I apologize for the really basic questions guys.
Shemlon said:
Will I need to reinstall TWRP and reroot my phone when I'm done? I apologize for the really basic questions guys.
Click to expand...
Click to collapse
No problem, yes, you will need to re-install TWRP and re-root your phone if you are doing the full procedure
Thank you dude!
Looks like all problems cuz of missmatching hashes in prev firmware and OTA. I just flashed from your link following things and OTA installed fine:
mfastboot flash motoboot motoboot.img
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Click to expand...
Click to collapse
Success!
Thanks! You saved me a bunch of time fixing my wife's phone that failed-to-update correctly like so many others.
FWIW:
1) Do NOT use the regular android sdk 'fastboot'; use the motorola-tweaked mfastboot version attached above. I've gotten away with using the regular fastboot util for most things, but the device failed to boot past the unlocked bootloader warning screen until I reflashed system using mfastboot instead.
2) I got an error updating the gpt partition (something about downgrading security versions), but it didn't seem to matter.
3) I didn't wipe the userdata partition either, and all was fine. Had a TWRP backup just in case, though.
5.1 -> 5.1.1 == done. Secure... for now. (according to this Stagefright Detector app)
Doubt this original MotoX will get Marshmallow 6.0, so I might be switching it to CyanogenMod 13 in a couple months.
I wanted to make this post about my adventure with my old Pixel 2. I was getting non-stop red lines out of the log in TWRP. Many times I would have problems mounting system and vendor partitions as well as vendor partitions needing "to be cleaned".
This led me to believe that I may have a corrupted partition, so I did some research into how the partitions are organized, and what happens when you flash a lot of ROMs. Perhaps you want to go back to the stock firmware? Perhaps - like in my case - you want to install a ROM such as GrapheneOS that's meant to lock the bootloader afterwards, and act more like the stock ROM.
What I didn't understand up until recently is how exactly the A and B slots of phones like the Pixel 2 work. They work because the firmware allows updating OTA to the opposite slot of what's active. That way - in the worst case scenario - you can actually boot into the opposite slot and regain access to your phone. I'm not an expert on this, but that's my basic understanding.
So now that that's covered, another important aspect is flashing ROMs. If you are like me and like testing many different ROMs, you may end up running into issues such as the one I stated above with TWRP.
The only way I was able to avoid these types of issues is to run some commands through fastboot.
One such command is
Code:
fastboot format system
This command will format the system partition and make it easier to install ROMs without running into issues.
Another command is
Code:
fastboot format vendor
This command was very important in my case, because the vendor partition was actually unusable for my slot A. Doing this command finally fixed that issue.
Another thing to note is ROMs can be installed in both slots. A lot of people don't do this, because they leave their bootloader unlocked and probably just run the ROM for half a day, and flash another. In my case, I needed to flash both slots in order to lock the bootloader in GrapheneOS, and allow the OS to update OTA. If you don't flash both slots, that won't work.
Just to clarify further, these are the commands (at the bootloader) I ran (from a command prompt in Windows) in order from start to finish when I was flashing a ROM I wanted to keep:
Code:
fastboot --set-active=a
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot --set-active=b
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
// Let the phone reboot into the new ROM, let it sit for a minute,
// then reboot into bootloader manually and then continue with fastboot:
fastboot --set-active=a
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
Once I've done this, and can confirm it successfully loads into the ROM I've installed, I can now say that I have a clean, fresh install in BOTH slots A and B.
I'll update this thread if I can think of anything else that can help newbies like me.
Cheers!
HCFL said:
I wanted to make this post about my adventure with my old Pixel 2. I was getting non-stop red lines out of the log in TWRP. Many times I would have problems mounting system and vendor partitions as well as vendor partitions needing "to be cleaned".
This led me to believe that I may have a corrupted partition, so I did some research into how the partitions are organized, and what happens when you flash a lot of ROMs. Perhaps you want to go back to the stock firmware? Perhaps - like in my case - you want to install a ROM such as GrapheneOS that's meant to lock the bootloader afterwards, and act more like the stock ROM.
What I didn't understand up until recently is how exactly the A and B slots of phones like the Pixel 2 work. They work because the firmware allows updating OTA to the opposite slot of what's active. That way - in the worst case scenario - you can actually boot into the opposite slot and regain access to your phone. I'm not an expert on this, but that's my basic understanding.
So now that that's covered, another important aspect is flashing ROMs. If you are like me and like testing many different ROMs, you may end up running into issues such as the one I stated above with TWRP.
The only way I was able to avoid these types of issues is to run some commands through fastboot.
One such command is
Code:
fastboot format system
This command will format the system partition and make it easier to install ROMs without running into issues.
Another command is
Code:
fastboot format vendor
This command was very important in my case, because the vendor partition was actually unusable for my slot A. Doing this command finally fixed that issue.
Another thing to note is ROMs can be installed in both slots. A lot of people don't do this, because they leave their bootloader unlocked and probably just run the ROM for half a day, and flash another. In my case, I needed to flash both slots in order to lock the bootloader in GrapheneOS, and allow the OS to update OTA. If you don't flash both slots, that won't work.
Just to clarify further, these are the commands (at the bootloader) I ran (from a command prompt in Windows) in order from start to finish when I was flashing a ROM I wanted to keep:
Code:
fastboot --set-active=a
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot --set-active=b
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
// Let the phone reboot into the new ROM, let it sit for a minute,
// then reboot into bootloader manually and then continue with fastboot:
fastboot --set-active=a
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
Once I've done this, and can confirm it successfully loads into the ROM I've installed, I can now say that I have a clean, fresh install in BOTH slots A and B.
I'll update this thread if I can think of anything else that can help newbies like me.
Cheers!
Click to expand...
Click to collapse
Would this help in bootloop as well? I have a pixel 1st gen that does. I have flashed and or tried to anyways factory images...OTA and even was able to boot twrp and get lineage to flash, only to get a random reboot and bootloop. I would need to flash the factory image in order to get this phone operable. Should I flash a factory image and then do your steps or should I do the steps first and then flash the factory image?
Nope. Did not work. Seems as if the stock recovery is fubar
I wanted to create a discussion for flashing GSI's and experimentations with Treble on our Pixel 3a. If you're unfamiliar with GSI's and Treble, please check out the wiki and FAQ here. Not all GSI's run flawless on our device, as to be expected, there WILL BE bugs here and there. These methods will wipe userdata, so backup all of your important data before attempting to flash a GSI. Make damn sure you have a way to recover your device in case something goes wrong!
What you'll need:
Fastboot and ADB installed correctly.
Factory image for Sargo - get it here.
An unlocked bootloader.
A GSI to install.
(vbmeta.img / vendor.img can be extracted from our factory image.)
Auto install a GSI:
The Universal Auto GSI Installer by @zedomax works for our device with all the GSI's I have tried from XDA. His instructions and video tutorial is included in the thread. The script is very easy to set up and use to install a GSI.
Manually install a GSI:
Code:
From stock Android 10 or 11
Boot into fastboot, then to fastbootd:
$ fastboot reboot fastboot
Disable verify boot (AVB) by flashing vbmeta.img:
$ fastboot --disable-verification flash --slot all vbmeta vbmeta.img
Find your current slot:
$ fastboot getvar current-slot
Delete the product partition to free up space for the system partition (Current slot):
$ fastboot delete-logical-partition product_a
The postfix _a should match the slot ID from our last command.
Erase the system partition:
$ fastboot erase system
Flash the GSI:
$ fastboot flash system system.img
This will take a bit.
Now wipe userdata and reboot:
$ fastboot -w reboot
Other resources regarding flashing GSI's:
Google's instructions.
Known issues and releases.
Android 11 Installation and info, translate to read.
Reserved
Hi every one, in this thread, I will guide How to Flashing GSIs for all Android devices (2021).
- A to Z for new babie, just only fastboot guide.
- I'm highly recommend using pHH GSIs image rom. (List here) AND DO NOT ASK ME SGSI ROM.
Code:
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
1. Prepair:
- Brain (to understand what I write below and make sure u will do it right)
- Using this app Treble Info to check your devices is support Treble (A/B, A only or VNDK)
- Unlock your Bootloader devices.
- Payload dumper for extract payload.bin BASE Rom. -> Check this video HOW TO EXTRACT Payload.bin rom
- U must be on stock rom to flashsing GSIs rom (flashing your stock rom on 1 slot, DO NOT FLASH ON BOTH SLOT). If u are on custom rom, then u will need to flash stock rom again.
- ADB driver, fastboot driver (guide for windows)
1.1 BASE ROM: Highly recommend using Lineage OS rom for base rom. (and u can try with another base rom, for example, on xiaomi devices, u have MIUI rom and AOSP rom aka OSS, and u can try both of these for BASE ROM)All u need in base rom:- vendor.img (must be in the same BASE ROM with boot.img) DO NOT try to mix with another boot.img- boot.img (must be in the same BASE ROM with vendor.img) DO NOT try to mix with another vendor.img- system_vbmeta.img (or vbmeta.img) or u can download this vbmeta.img here- patched magisk boot.img (if u want to root your devices)- vendor overlays: Some devices with notch/hole need this. (u can extract your stock rom to have this)- phh magisk v23 (download here)1.2 GSI ROM: I'm highly recommend using pHH GSIs image rom. (List here)All u need in GSI rom:- Yes, GSI rom aka system.img (recommend to rename it system.img)- product.img (download here) - credit @kusti4202. Flashing:
- Guide for A/B devices.
- Put your devices on FastbootD (using code adb reboot fastboot or using physical buttons power key and volume down key to make devices go to bootloader, then using code fastboot reboot fastboot to make your devices is on FASTBOOTD mode)
- Using these code instructions below: all in FastbootD
Step1:
Code:
fastboot getvar current-slot (see which slot u are using. Ex: a , b)
fastboot --set-active=b (if u are using slot a, change b to a) to make sure u're flashing gsi on 1 slot
Step2: vbmeta.img, vendor.img is from BASE ROM. product_gsi.img is from GSI ROM
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot flash product product_gsi.img
Step3: system.img is from GSI ROM. Some devices is request system.img <3GB, so your choise vanilla or full GAPPS GSI ROM.
Code:
fastboot erase system
fastboot flash system system.img
Step4: -w will wipe all data in your devices. boot.img is from BASE ROM.
Code:
fastboot -w
fastboot flash boot boot.img
fastboot reboot
Step5: when your gsi rom booted, flash boot patched magisk to have it root.
If it NOT BOOT, try to delete your product.img
Code:
fastboot delete-logical-partition product
If it NOT BOOT, change another vendor, boot from another BASE ROM!!!!
Good luck guys!!!!!
Successed boot GSI ROM ON PIXEL 4, PIXEL 3, PIXEL 3XL, XIAOMI REDMI K40.
I will make auto file flashing gsi rom later.
Video prop gsi rom, video guide on post 2.
Bugs + FAQ in #3
CREDIT:
@phhusson for all GSI ROM
@Allexwin50 for product_gsi
1. VIDEO GUIDE
2. Review
- Dot OS 5.2 GSI rom on Pixel 4:
BUGS ON PIXEL:
-VOLTE
i see you took that product img from my post, but you credited the wrong person for it
@Allexwin50 is the one who made it afaik, you can also see him being mentioned in my post for it
nice guide. i'm curious to test on my note 10 5g with mtk cpu. but i dont have a second phone. its a shame cause i'm modding addicted. but i can't risk to brick my phone. maybe in future... or if i buy a second phone. like note 8 2021
wetito said:
nice guide. i'm curious to test on my note 10 5g with mtk cpu. but i dont have a second phone. its a shame cause i'm modding addicted. but i can't risk to brick my phone. maybe in future... or if i buy a second phone. like note 8 2021
Click to expand...
Click to collapse
wym by "note 8 2021"???????
because i would like to test on mtk device
nambavuong said:
Hi every one, in this thread, I will guide How to Flashing GSIs for all Android devices (2021).
- A to Z for new babie, just only fastboot guide.
- I'm highly recommend using pHH GSIs image rom. (List here) AND DO NOT ASK ME SGSI ROM.
Code:
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
1. Prepair:
- Brain (to understand what I write below and make sure u will do it right)
- Using this app Treble Info to check your devices is support Treble (A/B, A only or VNDK)
- Unlock your Bootloader devices.
- Payload dumper for extract payload.bin BASE Rom. -> Check this video HOW TO EXTRACT Payload.bin rom
- U must be on stock rom to flashsing GSIs rom (flashing your stock rom on 1 slot, DO NOT FLASH ON BOTH SLOT). If u are on custom rom, then u will need to flash stock rom again.
- ADB driver, fastboot driver (guide for windows)
1.1 BASE ROM: Highly recommend using Lineage OS rom for base rom. (and u can try with another base rom, for example, on xiaomi devices, u have MIUI rom and AOSP rom aka OSS, and u can try both of these for BASE ROM)All u need in base rom:- vendor.img (must be in the same BASE ROM with boot.img) DO NOT try to mix with another boot.img- boot.img (must be in the same BASE ROM with vendor.img) DO NOT try to mix with another vendor.img- system_vbmeta.img (or vbmeta.img) or u can download this vbmeta.img here- patched magisk boot.img (if u want to root your devices)- vendor overlays: Some devices with notch/hole need this. (u can extract your stock rom to have this)- phh magisk v23 (download here)1.2 GSI ROM: I'm highly recommend using pHH GSIs image rom. (List here)All u need in GSI rom:- Yes, GSI rom aka system.img (recommend to rename it system.img)- product.img (download here) - credit @kusti4202. Flashing:
- Guide for A/B devices.
- Put your devices on FastbootD (using code adb reboot fastboot or using physical buttons power key and volume down key to make devices go to bootloader, then using code fastboot reboot fastboot to make your devices is on FASTBOOTD mode)
- Using these code instructions below: all in FastbootD
Step1:
Code:
fastboot getvar current-slot (see which slot u are using. Ex: a , b)
fastboot --set-active=b (if u are using slot a, change b to a) to make sure u're flashing gsi on 1 slot
Step2: vbmeta.img, vendor.img is from BASE ROM. product_gsi.img is from GSI ROM
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot flash product product_gsi.img
Step3: system.img is from GSI ROM. Some devices is request system.img <3GB, so your choise vanilla or full GAPPS GSI ROM.
Code:
fastboot erase system
fastboot flash system system.img
Step4: -w will wipe all data in your devices. boot.img is from BASE ROM.
Code:
fastboot -w
fastboot flash boot boot.img
fastboot reboot
Step5: when your gsi rom booted, flash boot patched magisk to have it root.
If it NOT BOOT, try to delete your product.img
Code:
fastboot delete-logical-partition product
If it NOT BOOT, change another vendor, boot from another BASE ROM!!!!
Good luck guys!!!!!
Successed boot GSI ROM ON PIXEL 4, PIXEL 3, PIXEL 3XL, XIAOMI REDMI K40.
I will make auto file flashing gsi rom later.
Video prop gsi rom, video guide on post 2.
Bugs + FAQ in #3
CREDIT:
@phhusson for all GSI ROM
@Allexwin50 for product_gsi
Click to expand...
Click to collapse
Is possible flash Gsi A11 or A12 in Huawei Mate9 runing Harmony OS ?
aureliolage said:
Is possible flash Gsi A11 or A12 in Huawei Mate9 runing Harmony OS ?
Click to expand...
Click to collapse
Hi, I have a MHA-L29 that I bootloader unlocked with PotatoNV and have twrp and android gsi by phh installed, I can help but I can't guarantee anything as you have a china model
SamJN1344 said:
Hi, I have a MHA-L29 that I bootloader unlocked with PotatoNV and have twrp and android gsi by phh installed, I can help but I can't guarantee anything as you have a china model
Click to expand...
Click to collapse
Can help me but here i run Harmony os
SamJN1344 said:
Hi, I have a MHA-L29 that I bootloader unlocked with PotatoNV and have twrp and android gsi by phh installed, I can help but I can't guarantee anything as you have a china model
Click to expand...
Click to collapse
??
buy a huawei with Harmony for modding.... curious choice
Lenovo didnt provide vendor.img for my tablet TB-J606F how can I backup\extract it from existing system?
I have root and I tried dd if=/dev/l9Y/.magisk/block/vendor .... and it didnt have permission. Is this only works on custom recovery? becuse I didnt find any for my device
I tried just flashing GSI 12 on the tablet and it worked but auto brightness and some more small but anoying suff didnt work perfect
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
Does this code make our system becoming fail to pass safetynett ? i dont know either . coz for me , after using kdragon zygisk safetynet fix also cant pass cts and basic test. im on ancientOS GSI right now for my mojito device
I was on a custom ROM, used this guide, I didn't even have to flash the stock ROM. I flashed crDroid GSI.
ronen1n said:
Lenovo didnt provide vendor.img for my tablet TB-J606F how can I backup\extract it from existing system?
I have root and I tried dd if=/dev/l9Y/.magisk/block/vendor .... and it didnt have permission. Is this only works on custom recovery? becuse I didnt find any for my device
I tried just flashing GSI 12 on the tablet and it worked but auto brightness and some more small but anoying suff didnt work perfect
Click to expand...
Click to collapse
Do you have super.img??
Benjamin B C H said:
Do you have super.img??
Click to expand...
Click to collapse
For that, use product GSI to be able to flash the system image. Worked for me.
Benjamin B C H said:
Do you have super.img??
Click to expand...
Click to collapse
I have 5 super files
ronen1n said:
I have 5 super files
Click to expand...
Click to collapse
Extract those super images and you might get the vendor file
Benjamin B C H said:
Extract those super images and you might get the vendor file
Click to expand...
Click to collapse
how can I do it? I tried few tools and it didnt work