Vendor Partition is missing in Wipe menu in TWRP - Samsung Galaxy A20 Questions & Answers

I flashed TWRP recovery I used last week, to install SparkOS and I do remember following a tutorial that said wipe Dalvik, Cache, Data, System and Vendor, which I did successfully and installed the custom rom. I didn't last much and reverted to Stock Rom.
Cut to yesterday I flashed the same recovery as last time, and when I went to wipe the partitions I didn't find Vendor. Checked Mount menu clicked on Vendor it didn't show up under Wipe.
Should I ignore this and continue with installing my custom rom after wiping (Dalvik, Cache, Data and system only) or this is a problem and I am not able to install any custom rom until I wipe Vendor Partition?

It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.

ai.Sanaul said:
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
Click to expand...
Click to collapse
I followed it step by step, but I'm gonna try different versions and see if shows up. Otherwise I'll revert back to stock and hang my hat.

ai.Sanaul said:
It may cause problem or maybe not. Try Orange Fox recovery or any other recovery which supports to wipe vendor data and then flash your Custom Rom correctly as in tutorial.
Click to expand...
Click to collapse
Updating the TWRP version from 3.3.1 to 3.6 fixed the problem. Thank you for the help.

Ikarisdruig said:
Updating the TWRP version from 3.3.1 to 3.6 fixed the problem. Thank you for the help.
Click to expand...
Click to collapse
welcome

Related

Can't flash oreo roms

Hi,
I have a problem installing 8.1 oreo roms on my phone. I follow standard procedure: wipe dalvik, cache, system, data -> install rom + gapps -> wipe cache. After my phone restarts, it displays rom logo, but doesn't load (even after 15-20 minutes of waiting). All I can do is load in fastboot and restore my backup. I use twrp 3.2.1-0, unofficial 8.1 pico gapps from 2018/01/30.
So far I tried:
-Installing rom and gapps separately.
-Installing rom, rebooting, installing gapps.
-Installing rom + gapps, then wiping data.
-Installing rom + gapps, then not wiping anything.
-Factory reset, then install rom + gapps.
-Installing rom + different gapps versions.
Additional notes:
-At one point I successfully installed NitrogenOS (about a month ago) and it is my current rom and backup. But I can't clean flash it again.
-When I install rom only (without any gapps) it boots up fine without errors or long loading.
Can anyone help?
Same problem I am also facing. Using Pixel experience ROM but now not able to flash cosmic official rom...remaining on bootanimation
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
devito666 said:
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
Click to expand...
Click to collapse
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
sanchez8096 said:
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
Click to expand...
Click to collapse
Thanks for the Link!
But unfortunately still Not booting...tried atomic official and teammexs Rom...
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
*then tap back, FORMAT DATA and confirm by typing "yes"
Flash
Rom
Gapps
Magisk stable (if preferred if not next >>>)
Magisk beta (always flash after stable)
Busybox flashable zip (if needed)
Mods such as MIUI cam mod
Font package
Wipe to factory reset
Reboot
After 1st boot
Reboot to TWRP
Install Magisk modules ( USN or Viper4android etc)
Reboot system
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Suo.Eno said:
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Click to expand...
Click to collapse
I didn't need to format data on Oreo nos
As mentioned in other threads on this topic, I just wanted to mention here as well that I am also affected by these Oreo boot loops and haven't found a solution yet. I somehow managed to get PixelExperience to install once, but downgraded now to a Nougat build for other reasons (better battery and GCamMod compatibility).
sanchez8096 said:
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
Click to expand...
Click to collapse
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Sunny Za said:
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Click to expand...
Click to collapse
I am using 3.2.1-0 twrp. Rom itself flashes fine, it's the gapps that create infinite boot.
Exact Same issue Here...
I have same problem too .. can't boot in to any Oreo ROM with Gapps .. really isn't any solution here?
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
sanchez8096 said:
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
Click to expand...
Click to collapse
Can someone upload me some backup? Pixel Experience would be a best ! Thanks a lot
Anyone have an idea what the problem might be?
I'm facing the same problem. I have a Redmi 3S (international, 3GB version). Doesn't matter what Oreo ROM I try (clean install), they all get stuck in bootloop on boot animation. It doesn't get far enough in the boot process to do a logcat with ADB, so I'm not able to post it.
I'm using TWRP 3.2.1-0 but have tried Red Wolf recovery as well and it yields the same results... I don't think it's a gapps issue since I've tried booting several ROMS without installing gapps.
I have rebooted several times while it's still in the boot process, remounted system in TWRP, wiped everything, ...
If anyone has an idea to get the logs, fire away. Can't boot so can't install liveboot or something like that.
bump
any solution?
The Problem still occurs...
Flashed PE successfully once, but since i went Back to official Nougat lineage os, No Oreo Roms can be booted with gapps

Sanity Check on Flashing Stock 5.1.4

Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
UPDATE: I did do something stupid after all. I forgot that my Oneplus was decrypted. So all I had to do was go into TWRP and go to Wipe and format data to re-encrypt it.
Z-Blade said:
Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
Click to expand...
Click to collapse
When starting fresh, wiping of internal storage should be considered. I recommended 2 guides here https://forum.xda-developers.com/on...nos-beta-1-android-oreo-t3710003/post77205633

Redmi note 7 stuck on boot image

I was using PE rom and I flashed a kernel and wiped cache and dalvik, after rebooting i couldn't turn on my mobile data for some reason. I went back to orange fox recovery and wiped system, cache, data, dalvik, vendor. Then i tried rebooting but it says no os installed. I used my other phone to download the latest PE rom and saved it on my sd card so i can flash it on my phone. I wiped cache, data, system, dalvik and vendor again before flashing the PE rom. After i flashed the rom im stuck on the boot image of PE i dont know why. Anyone knows how to fix this?
Is bc i wiped my phone's firmware too and thats the reason why my phone wont boot completely?
My device is redmi note 7. Thank u in advance
Skye1080p said:
I was using PE rom and I flashed a kernel and wiped cache and dalvik, after rebooting i couldn't turn on my mobile data for some reason. I went back to orange fox recovery and wiped system, cache, data, dalvik, vendor. Then i tried rebooting but it says no os installed. I used my other phone to download the latest PE rom and saved it on my sd card so i can flash it on my phone. I wiped cache, data, system, dalvik and vendor again before flashing the PE rom. After i flashed the rom im stuck on the boot image of PE i dont know why. Anyone knows how to fix this?
Is bc i wiped my phone's firmware too and thats the reason why my phone wont boot completely?
My device is redmi note 7. Thank u in advance
Click to expand...
Click to collapse
OMG!
1. You should never wipe system or vendor.
2. You should never wipe the firmware. Why on earth would you want to do that?
3. Format the data partition; reboot the recovery; flash a working firmware image (if you did indeed wipe the firmware); flash PE; hope for the best
DarthJabba9 said:
OMG!
1. You should never wipe system or vendor.
2. You should never wipe the firmware. Why on earth would you want to do that?
3. Format the data partition; reboot the recovery; flash a working firmware image (if you did indeed wipe the firmware); flash PE; hope for the best
Click to expand...
Click to collapse
Thank you for the knowledge! After formatting data and flashing PE it finally worked! I really appreciate it man.
Skye1080p said:
Thank you for the knowledge! After formatting data and flashing PE it finally worked! I really appreciate it man.
Click to expand...
Click to collapse
:good: Hit the "Thanks" button.

Phone boots into recovery after flashing an OTA

Hi,
I have been using Derpfest on my Redmi Note 6 Pro for a long time. To flash the latest version, I wiped cache, dalvik cache and data (as per their instructions) and then flashed the full zip. For some reason, the phone does not boot anymore, it goes into Mi logo, reboots, and then boots into recovery.
I have tried clearing data, dalvik, cache, system and internal storage and then flashing two different custom ROMs (Derpfest and HavocOS) but it still does not work.
Can someone please help me recover my phone?
Thanks
Saad Ismail said:
Hi,
I have been using Derpfest on my Redmi Note 6 Pro for a long time. To flash the latest version, I wiped cache, dalvik cache and data (as per their instructions) and then flashed the full zip. For some reason, the phone does not boot anymore, it goes into Mi logo, reboots, and then boots into recovery.
I have tried clearing data, dalvik, cache, system and internal storage and then flashing two different custom ROMs (Derpfest and HavocOS) but it still does not work.
Can someone please help me recover my phone?
Thanks
Click to expand...
Click to collapse
Format data.
DarthJabba9 said:
Format data.
Click to expand...
Click to collapse
This worked, thank you so much. It's so bad I wasted whole day on this .-.
Flash the last miui rom. Recovery Edition. https://c.mi.com/thread-2959490-1-0.html?t=1585141449432&utm_source=share
Boot up and than install the rom you want.
Saad Ismail said:
This worked, thank you so much. It's so bad I wasted whole day on this .-.
Click to expand...
Click to collapse
The latest Derpfest uses a new kind of encryption (FBE). This requires formatting data if you were on an earlier version (or any other ROM) with FDE. This really should have been stated clearly in the Derpfest instructions and changelog (perhaps it was - I don't know). If you were using OrangeFox Recovery, you might have seen something (in red) about Android Rescue Party, advising clean-flashing the ROM.

Most custom roms dont work for me - Am i doing something wrong?

Hello! Since i got this device, every time i try to install any custom rom, sometimes i have a good luck and one of those works, but other times they dont, i just get an "Android Setup keeps failing" so i cant even do the initial setup. The only roms that worked for me for now are the PE BS and Corvus, i tried LOS, PE, Havoc and almost any other rom and i get this problem, tried roms with and without gapps, different gapps versions and build but i just keep getting this problem.
The way i install a rom its like this:
- Wipe dalvik, data, cache and system
- Format data
- Reboot recovery
- Flash latest fw
- Flash rom
- Reboot Recovery
- Flash magisk
And i just keep getting this issue :c skipping magisk but i just get the same problem. I dont know if someone have or had this problem and know how to solve it.
Thanks in advance!
Arthur King said:
Hello! Since i got this device, every time i try to install any custom rom, sometimes i have a good luck and one of those works, but other times they dont, i just get an "Android Setup keeps failing" so i cant even do the initial setup. The only roms that worked for me for now are the PE BS and Corvus, i tried LOS, PE, Havoc and almost any other rom and i get this problem, tried roms with and without gapps, different gapps versions and build but i just keep getting this problem.
The way i install a rom its like this:
- Wipe dalvik, data, cache and system
- Format data
- Reboot recovery
- Flash latest fw
- Flash rom
- Reboot Recovery
- Flash magisk
And i just keep getting this issue :c skipping magisk but i just get the same problem. I dont know if someone have or had this problem and know how to solve it.
Thanks in advance!
Click to expand...
Click to collapse
When you say "flash latest fw" what do you mean? Latest MIUI firmware? If yes why? You wipe everything just to install the firmware again?
It should be:
- Wipe dalvik, data, cache and system
- Format data
- Reboot to recovery (TWRP)
- Flash ROM
-Flash Gapps if wanted and not included in custom ROM
- Flash magisk
- Boot to system
Sent from my Mi 9T using XDA Labs
Wolfcity said:
When you say "flash latest fw" what do you mean? Latest MIUI firmware? If yes why? You wipe everything just to install the firmware again?
It should be:
- Wipe dalvik, data, cache and system
- Format data
- Reboot to recovery (TWRP)
- Flash ROM
-Flash Gapps if wanted and not included in custom ROM
- Flash magisk
- Boot to system
Sent from my Mi 9T using XDA Labs
Click to expand...
Click to collapse
Yeah thats what i mean, and i flash it everytime because those times that i skipped that the rom didnt even booted, so i just assumed that its necessary. But also, tried the way you say it and still got the same result.
I think that i need to flash MIUI by fastboot for something like a "clean flash" because y tried everything even using the zip to skip the encryption but... Nothing, still the same :c
Arthur King said:
Yeah thats what i mean, and i flash it everytime because those times that i skipped that the rom didnt even booted, so i just assumed that its necessary. But also, tried the way you say it and still got the same result.
I think that i need to flash MIUI by fastboot for something like a "clean flash" because y tried everything even using the zip to skip the encryption but... Nothing, still the same :c
Click to expand...
Click to collapse
Best should be to follow the instructions by the ROM developer,
for example Arrow OS:
How to install:
Reboot to recovery
Wipe System , Cache, ART Cache and Data
Flash the ROM
Flash any addons (GApps, Magisk...)
Format data if you are encrypted
Reboot
(Formatting data is later here)
Or Bliss ROM:
First Time Install / Clean Flash
0. Flash proper firmware, latest firmware for your device variants.
1. Reboot to Recovery
2. Format data
3. Wipe system
4. Flash the ROM (DO NOT WIPE VENDOR, EVER)
5. Reboot to System
6. Reboot to Recovery
7. Flash Magisk (Optional)
8. Reboot to System
Sent from my Mi 9T using XDA Labs
Wolfcity said:
Best should be to follow the instructions by the ROM developer,
for example Arrow OS:
How to install:
Reboot to recovery
Wipe System , Cache, ART Cache and Data
Flash the ROM
Flash any addons (GApps, Magisk...)
Format data if you are encrypted
Reboot
(Formatting data is later here)
Or Bliss ROM:
First Time Install / Clean Flash
0. Flash proper firmware, latest firmware for your device variants.
1. Reboot to Recovery
2. Format data
3. Wipe system
4. Flash the ROM (DO NOT WIPE VENDOR, EVER)
5. Reboot to System
6. Reboot to Recovery
7. Flash Magisk (Optional)
8. Reboot to System
Sent from my Mi 9T using XDA Labs
Click to expand...
Click to collapse
Yeah, i tried that too, like mixing steps, or changing when do i format data, skipping magisk and even on roms without gapps skipping gapps but still get the same results
I just dont know what to do
Arthur King said:
Yeah, i tried that too, like mixing steps, or changing when do i format data, skipping magisk and even on roms without gapps skipping gapps but still get the same results
I just dont know what to do
Click to expand...
Click to collapse
Best may be to ask a ROM developer by PM what could be the problem. I'm still on stock so my knowledge about it is more theoretical.
Sent from my Mi 9T using XDA Labs
edit : nvm wrong thread

Categories

Resources