Related
Upon booting the 2nd RC build of Dirty Unicorns, I am faced with the dialog saying that the vendor image is out of date,
I have downloaded one from developer.google.com, I just need to know what I have to do to get it onto my Pixel.
fastboot flash vendor vendor.img
Which leads to the next question (or two):
Using a Windows computer, how do I compile the img file? (I could only find the binary at google, a tgz archive containing an .sh file)
Is there a fastboot flashable image available?
pTeronaut said:
Which leads to the next question (or two):
Using a Windows computer, how do I compile the img file? (I could only find the binary at google, a tgz archive containing an .sh file)
Is there a fastboot flashable image available?
Click to expand...
Click to collapse
If you download the full image from Google there is a second compressed file in the full image that has a vendor.img file. Also the just below the download link on the forum for the du ROM there is a link for the vendor image .
The third ROM release from DU does not require vendor image flash if you're already on the latest image.
Otherwise, reboot to bootloader.
Open your command prompt.
Use the command "fastboot flash vendor vendor.img".
I go the extra mile and do two commands.
"fastboot flash vendor_a vendor.img"
"fastboot flash vendor_b vendor.img"
Though it's probably not necessary.
As mentioned above, download the full Google image.
https://developers.google.com/android/images
Then extract it, and keep extracting it again and again until you find the vendor.img.
You can use TWRP to flash the vendor image. No need for fastboot.
spaceman860 said:
You can use TWRP to flash the vendor image. No need for fastboot.
Click to expand...
Click to collapse
Does that work with twrp on pixel?
toknitup420 said:
Does that work with twrp on pixel?
Click to expand...
Click to collapse
Yes
spaceman860 said:
Yes
Click to expand...
Click to collapse
Sweet deal. I didn't know that was working on pixel yet. Good looks for the info.
Flashing
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?
Vestell said:
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?
Click to expand...
Click to collapse
Did you unzip the file twice
There another zip inside the folder. Extract that and open your command prompt in there
mac796 said:
Did you unzip the file twice
There another zip inside the folder. Extract that and open your command prompt in there
Click to expand...
Click to collapse
I exstract it to a ADB folder and I opened the command prop there.
Vestell said:
If I try to do fastboot flash vendor vendor.img it says Failed remote command not allowed.
Can someone help me?
Click to expand...
Click to collapse
Hello... Is your bootloader unlocked?
Good luck...
5.1 said:
Hello... Is your bootloader unlocked?
Good luck...
Click to expand...
Click to collapse
Hello,yes its unlocked, I flashed Revolution recovery for nougat, I tryed to do /vendor mount -f in terminal and it says:
Permission Denied,If I flash extracted system.img with fastboot flash system system.img it says OKAY and when its done, I boot up my p9 lite but it wont boot to the system.
Vestell said:
Hello,yes its unlocked, I flashed Revolution recovery for nougat, I tryed to do /vendor mount -f in terminal and it says:
Permission Denied,If I flash extracted system.img with fastboot flash system system.img it says OKAY and when its done, I boot up my p9 lite but it wont boot to the system.
Click to expand...
Click to collapse
Hello I never heard of revolution recovery...
I know about TWRP. You can install vendor.img with TWRP by the way. :good:
Also, maybe you should post in the P9 lite forum... This is the Google Pixel XL forum...
Good luck...
5.1 said:
Hello... Is your bootloader unlocked?
Good luck...
Click to expand...
Click to collapse
5.1 said:
Hello I never heard of revolution recovery...
I know about TWRP. You can install vendor.img with TWRP by the way. :good:
Also, maybe you should post in the P9 lite forum... This is the Google Pixel XL forum...
Good luck...
Click to expand...
Click to collapse
Its a TWRP for p9 lite,if I try to install it I can choose between Recovery and boot, and srry that Im posting in google pixel XL forum,but im just looking for solutions that I could try, btw there is no P9 lite forum
Vestell said:
Its a TWRP for p9 lite,if I try to install it I can choose between Recovery and boot, and srry that Im posting in google pixel XL forum,but im just looking for solutions that I could try, btw there is no P9 lite forum
Click to expand...
Click to collapse
Sorry... Since i don't own the device, it's unlikely I can help you. Maybe flashing g P9 lite requires a different process, I don't know. Again, i guess you won't find much help in this forum.
Good luck...
where do i get the vendor image to install in twrp? the only thing that showed up under, "install image" was twrp. Do I need to install a factory vendor image from google?
ken2736 said:
where do i get the vendor image to install in twrp? the only thing that showed up under, "install image" was twrp. Do I need to install a factory vendor image from google?
Click to expand...
Click to collapse
U need extracted vendor img from stock Google zip then flash image in twrp. Yes click image button. Then click on vendor then flash.
hey everyone,
I recently purchased a used Nexus 5x that is running fine so far. my only problem is i get the message "internal problem, contact manufacturer" after every boot.
the phone is running android 7.0 (NDR90S) and the seller told me he trie to root and flash custom firmware but somehow the boot loader always locked itself. Now its not possible to perform an OTA update to 8.0 (get it offered all the time).
According to the developer setting the Bootloader is unlocked. I read that it should be fine to flash the vendor.image. Is this correct so far?
I had trouble finding this information, and since we have no working TWRP yet, here is a way to get low-level access to al lot of files.
Full credits go to: @s3axel, Source
So you flashed a module that is now causing a bootloop?
Follow these steps:
0. check if you can boot using stock boot.img, if that does not work, then you have a bigger problem then I had and this guide may not work for you.
1. Get the stock recovery.img by extracting it from the same OTA file as your current build, using payload_dumper
2. Follow s3axel's guide to get adb to work in recovery mode (after you unlock the drive)
s3axel said:
It's actually pretty easy and this would most probably also work for the 7T...
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash
Click to expand...
Click to collapse
3. rename the image_new.img to unsecure_adb_recovery.img
4. flash usecure recovery
Code:
fastboot flash recovery unsecure_adb_recovery.img
5. get into the adb shell
Code:
adb shell
then find the magisk module folder
Code:
cd /data/adb/modules
6. remove the module
Code:
rm -rf name_of_module
7. exit shell
8. reboot back to fastboot (See notes below)
9. flash stock recovery
Code:
fastboot flash recovery recovery.img
10. boot patched boot image to try if magisk worked
Code:
fastboot boot patched_magisk.img
Hopefully, if it boots again with root and Magisk
This worked very well and was very easy to do.
11. Use Magisk apk to install magisk to boot img. Or flash your patched magisk.
Notes:
DO NOT try adb reboot fastboot, I was hoping this would work (I was tired, ok...)
I got stuck in a bootloop (it kept asking me to unlock my device)
to break out of this loop, I used the forced off method: hold power + volume up & down until screen blacks out
From power off to bootloader:
press & hold volume down and power
and hold down until you get back to recovery, reboot to fastboot then flash stock recovery back to secure your ADB and return to as much stock as possible :good:
Here is my patched prop.default
Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!
Y not create a core only boot image from magisk andThat share here so it would b really helful to all....
grandpajiver said:
Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!
Click to expand...
Click to collapse
The Recovery.img is from stock, so not a per-device thing.
I was just too lazy to find a place to upload large files.
I am currently on 10.0.4 but with 10.0.5 showing up, it would need updating later on.
I am not sure if you can flashboot boot recovery, certainly worth a try? Not sure how all this works, so I just flashed recovery and then flashed stock after I was done.
I also tested the TWRP build by not flashing it but booting it directly, but that was not very productive given it's current state.
hafiz.hasan said:
Y not create a core only boot image from magisk andThat share here so it would b really helful to all....
Click to expand...
Click to collapse
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!
If only I didn't have tons of crap at work. This may be the gateway to v4a.
I have the images but not the extractor. Hmmmmm.
FreezyExp said:
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!
Click to expand...
Click to collapse
Nice.. So are you gonna help building core only boot img for our device.?
hafiz.hasan said:
Nice.. So are you gonna help building core only boot img for our device.?
Click to expand...
Click to collapse
Nope sorry, not at this time.
There is a pull request on the magisk github that allows us to build Core-Only, so I will be waiting for that.
This guide contains the information that solved my immediate issue with not being in possesion of core-only.
Without having to deal with a lot of unknowns, just download some tools, extract some files, edit a few lines then patch it back up.
Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.
grandpajiver said:
Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.
Click to expand...
Click to collapse
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
This isn't fun to work on through a locked down Windows 10 pc. gonna try again on my chromebook after I get the 1.0.0.6 build.
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.
grandpajiver said:
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.
Click to expand...
Click to collapse
I got updated to 1.0.0.6.. I went from the '0' version to 'I'. Shrug.
fastboot boot recovery.img nor fastboot boot recovery recovery.img works... sigh.
I do have the full OTA. OnePlus7TOxygen_14.I.08_OTA_008_all_1911061912_10a180d3.zip. Dunno if anyone needs it.
I am on Linux. I used mktool to unpack and repack. I set all the flags properly between entered fastboot and Flash the new image to recovery as specified. device immediately hangs. I hold the keys to enter fastboot mode again and of course I can't run shell as ADB is not available in fastboot.
every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks
morback said:
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks
Click to expand...
Click to collapse
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?
morback said:
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?
Click to expand...
Click to collapse
I have not fiddled around with fastboot ROMs. But you should be able to download your OOS rom with Oxygen Updater.
If someone else haven't uploaded the stock recovery, you'll need to use a tool like this to extract the payload bin inside the zip. The recovery is named recovery.img
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Anyone here can help me, because I'm stuck in fastboot mode after I tried to root my device using magisk.
Qfil not recognise my device (also Adb, using "Adb devices" devices)
Bootloader Unlocked
Unrooted
Hi you need to activate Test Mode in Windows and install qdloader drivers in device manager (listed as Qh_USB_BULK or something like that) Google it. In my Google drive folder is a Firmware for qfil otherwise download it from Hikary calyx Website. Just Google 'Nokia 3.2 edl firmware'. You need to remove those lines in rawprogram0.xml which are not as image there. So compare the filenames in this file and delete those lines where a image is not in that folder (like dp_AP_signed.mbn is not in that folder so remove the line)
Good luck
i am also stuck on fastboot mode. i want to get back to stock rom. whats the procedure
s3tupw1zard said:
Hi you need to activate Test Mode in Windows and install qdloader drivers in device manager (listed as Qh_USB_BULK or something like that) Google it. In my Google drive folder is a Firmware for qfil otherwise download it from Hikary calyx Website. Just Google 'Nokia 3.2 edl firmware'. You need to remove those lines in rawprogram0.xml which are not as image there. So compare the filenames in this file and delete those lines where a image is not in that folder (like dp_AP_signed.mbn is not in that folder so remove the line)
Good luck
Click to expand...
Click to collapse
Would the "Nokia 3.2 edl firmware" work as well for the Nokia 2.2? I haven't found any firmware specific for the 2.2. Also, would the firmware contain the boot.img file? (I just want to root the 2.2 and this is the file I'm missing).
I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.
MRza3ter said:
I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.
Click to expand...
Click to collapse
please teach me how to do this pleaseeee i dont get it
fjeeg said:
please teach me how to do this pleaseeee i dont get it
Click to expand...
Click to collapse
Okay so what you want to do is download the stock ROM, just go in Google then search nokia 3.2 stock ROM, after download right click then extract, then hold shift then right click on nothing in the extracted file then click on open with powershell, after that just type the code
MRza3ter said:
Okay so what you want to do is download the stock ROM, just go in Google then search nokia 3.2 stock ROM, after download right click then extract, then hold shift then right click on nothing in the extracted file then click on open with powershell, after that just type the code
Click to expand...
Click to collapse
mine says that the partition table doesnt exist
Hello fellow XDA'ers
I have waited and unlocked the phone, running the MIUI 12.5.1.0 (RKHEUXM) the EU Official Rom that came with the phone, and was following the guide on how to root from NaldoTech, but i'm stuck, magisk can't patch any Firmware file i throw at it...
Don't know what i am doing wrong, i opened the zip files manually looking for the boot.img file but i cant seem to find it in any of the Firmwares i download from XiaomiFirmwareUpdater.
Also tried downloading the rom file and extracting the contents using the xiaomi-flashable-firmware-creator, but no luck with that either, throws some permission error at extracting the payload.bin
what can i do from here??
thanks in advance
Easy peasy
Steps
Download Adb and fastboot tool.
Or just download TWRP image and start CMD from there "the folder containing the twrp img" (in destination bar type cmd and press Enter) /the drivers should be installed and working properly ofc.
1- set phone in fastboot mode then plug it in to PC
2- Type: fastboot boot twrp.img (twrp here is the img file)
Then the phone will boot into twrp.
The phone will be shown in PC. Paste Magisk in the phone. Then go back and flash it using TWRP. Then reboot to system. And you're all done.
laid1995 said:
.
Click to expand...
Click to collapse
doesnt boot to twrp just turns off :S
Fyat said:
doesnt boot to twrp just turns off :S
Click to expand...
Click to collapse
You're doing something wrong then.
Check all drivers are set up properly. Try flashing twrp then boot to it using Volume UP + Power button.
Make sure you download Nebrassy's twrp 3.5.10
Managed to do it, not with twrp tho, the way i intended originally, i found this payload extractor, went on miui and download latest package (on the phone), after that sent the file to pc and extracted the contents to the payload extractor tool, follow the tool's guide and Tadaaaa! got yoursef a boot.img.
after that was simple and follow the rest of the NaldoTech guide, which is sending the boot.img to phone, open magisk manager, click install, select the boot image to pach, wait couple seconds and done. After that just copy the magisk patched boot image to pc and turn off your phone, enter fastboot, and flash the boot.img in boot_a and boot_b.
and you are done boot the phone and open magisk app to see the installed confirmation
Fyat said:
Managed to do it, not with twrp tho, the way i intended originally, i found this payload extractor, went on miui and download latest package (on the phone), after that sent the file to pc and extracted the contents to the payload extractor tool, follow the tool's guide and Tadaaaa! got yoursef a boot.img.
after that was simple and follow the rest of the NaldoTech guide, which is sending the boot.img to phone, open magisk manager, click install, select the boot image to pach, wait couple seconds and done. After that just copy the magisk patched boot image to pc and turn off your phone, enter fastboot, and flash the boot.img in boot_a and boot_b.
and you are done boot the phone and open magisk app to see the installed confirmation
Click to expand...
Click to collapse
Whatever was your way, I'm glad you managed to do it
sir i need boot.img file for poco f3
ZAki6464 said:
sir i need boot.img file for poco f3
Click to expand...
Click to collapse
Good
Which version do you need?
Is this international version I should get to use in USA on T-Mobile to root the same way as you?
Amazon F3
I'm using Europe version currently on Global 12.5.6.0 (RKHEUXM)
Fyat said:
I'm using Europe version currently on Global 12.5.6.0 (RKHEUXM)
Click to expand...
Click to collapse
Do you have access to gpu rendering tweaks in turbo game mode ? I can't make it work, I'm on same version than you
Greenspoof said:
Do you have access to gpu rendering tweaks in turbo game mode ? I can't make it work, I'm on same version than you
Click to expand...
Click to collapse
I'm not sure where to find these options as i do not use the turbo mode, can you point to it?
Hi all,
I would like to flash some GSI roms into our phone ( OP9P ) but several guides I followed doesn't worked....
Is anyone knows a reliable guide to follow ?
Mnay thanks
Jack Droid said:
Hi all,
I would like to flash some GSI roms into our phone ( OP9P ) but several guides I followed doesn't worked....
Is anyone knows a reliable guide to follow ?
Mnay thanks
Click to expand...
Click to collapse
You know that in an gsi not all will work ?
And when you flash the gsi to system Partition have you disabeld vbmeta_system ?
Yes and no.
BTW, I would like to try.
Can you help me with a reliable guide ?
Use this
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
Hmmmm.....
I believe already tried this guide but I'm not really sure.....
In any case, I'll carefully follow all the steps as it seems interesting....Thanks !
One question :
when adivsed to put "fastboot reboot fastboot", it means that you need to be on fastbootD environment and not bootloader environment ( with green written START on top, just to understand ), correct ?
Jack Droid said:
Hmmmm.....
I believe already tried this guide but I'm not really sure.....
In any case, I'll carefully follow all the steps as it seems interesting....Thanks !
One question :
when adivsed to put "fastboot reboot fastboot", it means that you need to be on fastbootD environment and not bootloader environment ( with green written START on top, just to understand ), correct ?
Click to expand...
Click to collapse
Yes fastboot reboot fastboot for reboot to fastbootd
Ok, thanks.
I try and I'll let you know....!
Hi ChrisFeiveel84,
just a fast question :
I have downloaded a GSI rom that is a rar file.
Unpacking it, I obtains a GSI image file but in order to proceed further, I have to put payload.bin into Fastboot Enhance but payload.bin is fused into the image file....
Normally, with all other custom roms, it is enough to drag the relevant zip file on the payload.dumper and you can obtain all inside img files......
How can I extract GSI iso file in order to have payload.bin file ???
Many thanks
Jack Droid said:
Hi ChrisFeiveel84,
just a fast question :
I have downloaded a GSI rom that is a rar file.
Unpacking it, I obtains a GSI image file but in order to proceed further, I have to put payload.bin into Fastboot Enhance but payload.bin is fused into the image file....
Normally, with all other custom roms, it is enough to drag the relevant zip file on the payload.dumper and you can obtain all inside img files......
How can I extract GSI iso file in order to have payload.bin file ???
Many thanks
Click to expand...
Click to collapse
a gsi have no payload bin
than a gsi is only a system image
(gsi gerneric system image and this is not a rom)
and the gsi you flash (the image ) to system partition (end the rest you use from your rom what you have on your phone )
Here is reported :
Gathering your assetsOn your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
Now go to payload dumper and open your version zip
Go to partitions and CTRL click vbmeta, boot, system.
check the allow incremental box on the side
click extract images and extract them to your folder
Now go to payload dumper and open your version zip : when you try to put zip file, it advise you that you need to put payload.....
Jack Droid said:
Here is reported :
Gathering your assetsOn your computer open platform-tools-enchanted folder and launch FastbootEnhance.exe
Now go to payload dumper and open your version zip
Go to partitions and CTRL click vbmeta, boot, system.
check the allow incremental box on the side
click extract images and extract them to your folder
Now go to payload dumper and open your version zip : when you try to put zip file, it advise you that you need to put payload.....
Click to expand...
Click to collapse
you get the data from the full rom packet (the rom you currently have on your cellphone) you have to download it (or make a backup of the partitions with the msm tool like vbmeta vbmeta_system)
mmmmmmm......no
Simply, I tried with Win10 i.o. Win7 and Fastboot Enhance is now checking for payload AND zip file so that I can proceed with GSI ZIP extraction and so on...
Anyway, thanks for your kind replies !
you only need the vbmeta and vbmeta_system image and the gsi
and flash this
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase system
fastboot flash system Gsi.img