Hi guys,
would someone with Android 7.0 final build be so kind and send me a TWRP backup of the vendor parition/bootloader/radio?
I built AOSP for the Nexus 5X, but it is no good without the according blobs, and factory images are not online yet
Thanks for your help!
Here's the OTA image with all those files you need:
https://android.googleapis.com/pack.../cd8d8f775bcdb6a76a496a3a664caba0b9ed47f9.zip
sprremix said:
Here's the OTA image with all those files you need:
https://android.googleapis.com/pack.../cd8d8f775bcdb6a76a496a3a664caba0b9ed47f9.zip
Click to expand...
Click to collapse
Ah yes, I can install the previous factory image and flash OTA. Thanks for the idea :good:
Factory images for 5X are now online.
miisterlim said:
Factory images for 5X are now online.
Click to expand...
Click to collapse
And brick phones
Factory image works just fine, make sure you have the latest fastboot and adb, and give it time.
@petrus764 where to download the latest fastboot?
Thank you for your understanding.
Danielf85 said:
@petrus764 where to download the latest fastboot?
Thank you for your understanding.
Click to expand...
Click to collapse
I use minimal adb and fastboot which comes with version 1.0.35 rc and that works for me.
http://forum.xda-developers.com/showthread.php?t=2317790
Apparently there's a newer version too, 1.0.36 which you can get from here http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
of course the latest is always available via the android sdk, but who can be bothered download all of that just for adb and fastboot.
When I upgrade Cyanogenmod, I download the matching archive from here:
https://developers.google.com/android/nexus/images#bullhead
and do (with MTC20F for example):
flashboot flash bootloader bootloader-bullhead-bhz10r.img
flashboot flash radio radio-bullhead-m8994f-2.6.32.1.13.img
flashboot flash vendor vendor.img
Are there any other files I should be flashing such as boot.img?
xdadevelopersrocks said:
When I upgrade Cyanogenmod, I download the matching archive from here:
https://developers.google.com/android/nexus/images#bullhead
and do (with MTC20F for example):
flashboot flash bootloader bootloader-bullhead-bhz10r.img
flashboot flash radio radio-bullhead-m8994f-2.6.32.1.13.img
flashboot flash vendor vendor.img
Are there any other files I should be flashing such as boot.img?
Click to expand...
Click to collapse
No. Everything else is contained in the rom zip.
Sent from my Nexus 5X using Tapatalk
OK, is there a better way of figuring out which version to download from developers.google.com than watching the output from TWRP when installing a ROM?
xdadevelopersrocks said:
OK, is there a better way of figuring out which version to download from developers.google.com than watching the output from TWRP when installing a ROM?
Click to expand...
Click to collapse
The rom dev will inform you which Android base is installed if you read their changelog. Then you download that factory image from Google to flash vendor. Radio and bootloader are optional.
Sent from my Nexus 5X using Tapatalk
Hi everyone,
I flashed pixel rom and my bootloader has changed to that of pixel with all the white and new icons.
Is there a way that i can revert back to the old black bootloader that came out of the box. I wish to come back to the old hence the new one doesn't seem to have access to the adb
Thanks,
Charles
Flash bootloader from latest factory img.
icrunchbanger said:
Flash bootloader from latest factory img.
Click to expand...
Click to collapse
via TWRP?
charlesco29.cc said:
via TWRP?
Click to expand...
Click to collapse
No. Via bootloader. After -flash bootloader bootloader.img-
Do a reboot and you are done.
How to go back to stock.. Please helppppp?? The new bootloader in this rom doesnot allow me to flash stock image. Help pleaseeee
Do you have fastboot working? If yes, simply flash sock ROM via fastboot: https://developers.google.com/android/images
If no, maybe flashing TOT can help you (I didn't test): https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Hi I am new to the Nexus 5x and need assistance. I dont know what factory image from https://developers.google.com/android/images#bullhead I need if I have metro pcs. And every time I need to go into custom recovery do I need to flash it threw bootloader with the custom rom folder in the adb folder? Please someone help me I am really confused
HaxUrMom69 said:
Hi I am new to the Nexus 5x and need assistance. I dont know what factory image from https://developers.google.com/android/images#bullhead I need if I have metro pcs. And every time I need to go into custom recovery do I need to flash it threw bootloader with the custom rom folder in the adb folder? Please someone help me I am really confused
Click to expand...
Click to collapse
Factory images are universal for this device. All carriers are supported. Just flash the June factory image.
You can flash the boot, system, recovery, and vendor images through TWRP. Those same images can be flashed in the bootloader. Radio and bootloader images must be flashed in bootloader. Does that answer your question? If not, read my guide and see if that resolves your questions:
https://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Factory images are universal for this device. All carriers are supported. Just flash the June factory image.
You can flash the boot, system, recovery, and vendor images through TWRP. Those same images can be flashed in the bootloader. Radio and bootloader images must be flashed in bootloader. Does that answer your question? If not, read my guide and see if that resolves your questions:
https://forum.xda-developers.com/showthread.php?t=3206930
Click to expand...
Click to collapse
So when you install a new rom you don't need to flash the vendor image also? Because some ROMs say to also flash vendor image when installing a rom
tactical bacon said:
So when you install a new rom you don't need to flash the vendor image also? Because some ROMs say to also flash vendor image when installing a rom
Click to expand...
Click to collapse
This is covered in-depth with FAQ #9 of my link above. But in short, each monthly security update brings a new vendor image that must be installed. Each time your rom updates to a new month's security update, you need to install that vendor image. If you flash back to a previous month's rom, you need to flash that respective vendor image. Only exception is if your rom includes the vendor image in the rom zip.
Sent from my Nexus 5X using Tapatalk
Sorry one last question. I am on the latest security update stock, if I was to flash the latest AOSP extended on the latest security update all I would have to do is flash the ROM and gapps? But when the new security update is added to the ROM then I would flash the vendor image. Sorry if I'm asking to many questions but I don't want to run into a problem.
tactical bacon said:
Sorry one last question. I am on the latest security update stock, if I was to flash the latest AOSP extended on the latest security update all I would have to do is flash the ROM and gapps? But when the new security update is added to the ROM then I would flash the vendor image. Sorry if I'm asking to many questions but I don't want to run into a problem.
Click to expand...
Click to collapse
You're fine, ask away! Yes to both questions. Let's say the July security update is released for your custom rom. You would flash the July vendor.img then your rom and then that's it.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You're fine, ask away! Yes to both questions. Let's say the July security update is released for your custom rom. You would flash the July vendor.img then your rom and then that's it.
Click to expand...
Click to collapse
Just one more thing. I just realized there is no sd slot. where would I put the ROM and gapps
tactical bacon said:
Just one more thing. I just realized there is no sd slot. where would I put the ROM and gapps
Click to expand...
Click to collapse
I have my stuff in subfolders inside /sdcard
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
I have my stuff in subfolders inside /sdcard
Click to expand...
Click to collapse
Thanks for the help. I just flashed asop extended and everything works fine. Do you have a recommended ROM for stability?
I recently bought a Chinese phone from a relatively unknown manufacturer, so I was unable to find any TWRP images that match the device, I was wondering if it was possible to extract the boot image directly from a GSI ROM. My end goal is to install Magisk so if there is a better way to go about this please let me know.
can you tell model and brand
Hsnmastoor said:
can you tell model and brand
Click to expand...
Click to collapse
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
XDA-Developer30 said:
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
Click to expand...
Click to collapse
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Hsnmastoor said:
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Click to expand...
Click to collapse
Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
If you wish to root your Mediatek Android phone, we'd dropped a guide on rooting using Magisk and stock boot.img at https://www.hovatek.com/forum/thread-21427.html , no custom recovery is required. Se
forum.hovatek.com
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
Thank you for the reply, I forgot to mention that I used Hsnmastoor's method successfully.
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
elmapq said:
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
Click to expand...
Click to collapse
And your device is...???
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
Tecno Spark 6 ke7
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
I have a Vortex V22 MTM6761 There is no stock rom. It has unofficial GSI Pixel experience plus 13.0 running on it. I too would like to root. How can I retrieve the boot.img file from the GSI rom? Or how can I pull it from the phone via terminal and fastboot? All help is greatly appreciated! Happy Saint Patricks Day!
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
LinhBT said:
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
Click to expand...
Click to collapse
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
defcondoc said:
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
Click to expand...
Click to collapse
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
.
LinhBT said:
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
Click to expand...
Click to collapse
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
defcondoc said:
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
Click to expand...
Click to collapse
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
LinhBT said:
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
Click to expand...
Click to collapse
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
I have 2 models I cannot find stock ROM's for:
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB - manufacture date year 2022
Moxee M2160 Model MH-T6000 2APQU-MH-T6000 Q6006_V1.0 - manufacture date year 2022
Can anyone find anything? I have scoured the web for months!
I can't believe there is nothing available for these phones.
Please let me know if you can find a stock ROM. I would love to learn where and how you found them. As I've have found nothing for months and months.
Thank you!!!
defcondoc said:
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
Click to expand...
Click to collapse
You CAN extract the boot.img via terminal ONLY IF you're on a ROOTED devices!