VertexOS 1.9 [UNOFFICIAL][2017/2/11] [KIPPER] [AOSP+LOS] - Wileyfox Storm

HI ALL! With new Rom
VertexOS aims to provide a simple but enhanced near-stock AOSP experience with carefully selected features and an emphasis on stability and smoothness.​
what doesn't work ?
everything is working perfectly.
Coming from another ROM, OR if a CLEAN FLASH is required
1) Download the Vertex... .zip file.
2) Download a 7.1 GApps package.
3) Boot into recovery (TWRP)
4) Full wipe (Dalvik Cache, Cache, System, Factory Data Reset)
5) Flash the Vertex... .zip file
6) Flash Nougat-compatible GApps : http://opengapps.org/ / ARM64,7.1,pico
7) Reboot
Download:https://www.androidfilehost.com/?fid=745425885120707303
enjoy!
Credits:
- LineageOS
- AOSPA
- Citrus-CAF
- DU
- PureNexus
- Zephyr-OS
IF YOU LIKE MY WORK PLEASE HIT THANKS .
-IMPORTANT- : To install this rom you must have installed TWRP-3.0.3.0 , download from here https://www.androidfilehost.com/?fid=529152257862697990
To easy install from TWRP recovery :
1- open "install" section.
2- SELECT "install img" in the bottom .
4- Chose the place of TWRP-3.0.3.0.
5- install as RECOVERY , then reboot to recovery.
XDA:DevDB Information
ROM [AOSP + LOS], ROM for the Wileyfox Storm
Contributors
PS-DEV
Source Code: https://github.com/VertexOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP + LOS
Version Information
Status: Stable
Created 2017-02-11
Last Updated 2017-02-20

Received

Received !

Firstly, thanks loads for producing these ROMs it is much appreciated. :good:
I am unfortunately having issues getting both this and your CypherOS rom to work.
After full wipes of everything both roms get stuck on the "Wileyfox powered by Android" boot screen.
I get the same result sideloading via adb and from the internal memory.
I have tried TWRP 3.0.2.0 and older versions, I have also tried old and new Cyanogen recoveries.
I have successfully got the Slimrom 7.1 rom working and the LineageOS 14.1 rom which also works but with many random reboots.
Any thoughts on what I might be missing when flashing your ROMs?
Again many thanks for the work.

Any chance of grabbing your recipe for building this from source? Own personal use only. I have the VertexOS repo cloned. A copy of your roomservice and local manifest would help enormously.
This seems much more stable than Lineage at the moment. Please note you *MUST* use TWRP 3.0.2-1, the non-test version, to install Vertex and a fastboot -w also can't hurt.

Cannot inatall gapps (Wrong Architecture)
Hi,
I installed VortexOS 1.9... but when I tried to install ARM64 7.1 pico Open gapps package then following Error occurs:
"ERROR 64: Wrong architecture to set-up Open GApps pre-bundled busybox"
I use TWRT 3.0.3-0 (kipper)
Any ideas what I made wrong?
best regards, Chuck

Vertex appears to be built as ARMv7, which means 32 bit. Try the 32 bit pico.

I installed fine with the nano apps and 64 bit, no issues

miSAKe said:
Firstly, thanks loads for producing these ROMs it is much appreciated. :good:
I am unfortunately having issues getting both this and your CypherOS rom to work.
After full wipes of everything both roms get stuck on the "Wileyfox powered by Android" boot screen.
I get the same result sideloading via adb and from the internal memory.
I have tried TWRP 3.0.2.0 and older versions, I have also tried old and new Cyanogen recoveries.
I have successfully got the Slimrom 7.1 rom working and the LineageOS 14.1 rom which also works but with many random reboots.
Any thoughts on what I might be missing when flashing your ROMs?
Again many thanks for the work.
Click to expand...
Click to collapse
Check the first post . i have been edit.

Chron0s said:
Any chance of grabbing your recipe for building this from source? Own personal use only. I have the VertexOS repo cloned. A copy of your roomservice and local manifest would help enormously.
This seems much more stable than Lineage at the moment. Please note you *MUST* use TWRP 3.0.2-1, the non-test version, to install Vertex and a fastboot -w also can't hurt.
Click to expand...
Click to collapse
show your PM.

Chron0s said:
Vertex appears to be built as ARMv7, which means 32 bit. Try the 32 bit pico.
Click to expand...
Click to collapse
NO NO
ARM64 ARMv8 .

ChuckeCheese said:
Hi,
I installed VortexOS 1.9... but when I tried to install ARM64 7.1 pico Open gapps package then following Error occurs:
"ERROR 64: Wrong architecture to set-up Open GApps pre-bundled busybox"
I use TWRT 3.0.3-0 (kipper)
Any ideas what I made wrong?
best regards, Chuck
Click to expand...
Click to collapse
1- check to wipe this partitions :
- SYSTEM
- CACHE
- Dalvick-cache.
- DATA
and dont forget to factory reset .
2- first install rom then Gapps. download from here http://bit.ly/2kQf3Le

PS-DEV said:
Check the first post . i have been edit.
Click to expand...
Click to collapse
Thanks again,
Unfortunately I could not get that recovery to work via TWRP 3.0.2.1 or fastboot.
I can flash it but not boot to recovery.
If booting the image directly I get
Code:
FAILED (remote: dtb not found)
I will try building it myself when I get some time.

miSAKe said:
Thanks again,
Unfortunately I could not get that recovery to work via TWRP 3.0.2.1 or fastboot.
I can flash it but not boot to recovery.
If booting the image directly I get
Code:
FAILED (remote: dtb not found)
I will try building it myself when I get some time.
Click to expand...
Click to collapse
You flash via TWRP or fastboot ??
And looking for the method to install TWRP 3.0.3.0 ?
And after chose recovery , you install in "boot" or "reocvery" section ?

PS-DEV said:
You flash via TWRP or fastboot ??
And looking for the method to install TWRP 3.0.3.0 ?
And after chose recovery , you install in "boot" or "reocvery" section ?
Click to expand...
Click to collapse
Both, from TWRP i selected recovery, this flashes but results in recovery not loading.
from fastboot the flash fails, as does booting the image via fastboot.

miSAKe said:
Both, from TWRP i selected recovery, this flashes but results in recovery not loading.
from fastboot the flash fails, as does booting the image via fastboot.
Click to expand...
Click to collapse
The phone boot to rom or not ??

PS-DEV said:
The phone boot to rom or not ??
Click to expand...
Click to collapse
Yes can still boot to Slimrom 7.1 with or without working recovery.
I have reverted to TWRP 3.0.2.1 though.
Thanks for your help.

miSAKe said:
Yes can still boot to Slimrom 7.1 with or without working recovery.
I have reverted to TWRP 3.0.2.1 though.
Thanks for your help.
Click to expand...
Click to collapse
Can you check your bootloader version ?
Because TWRP 3.0.3.0 Needs to kipper-13-.... bootloader
See the photo .

PS-DEV said:
Can you check your bootloader version ?
Because TWRP 3.0.3.0 Needs to kipper-13-.... bootloader
See the photo .
Click to expand...
Click to collapse
Got it kipper-12.1
I reverted to stock recently.
Solved the issue, thank you very much.

miSAKe said:
Got it kipper-12.1
I reverted to stock recently.
Solved the issue, thank you very much.
Click to expand...
Click to collapse
Stock firmware or what? ,, to install version 13 Bootloader , just install any nightly cm13 then back to recovery and install TWRP 3.0.3.0 ??.

Related

What ROM can I install on my NEO?

Hello,
do you know if I can install the following ROM downloaded from this site (CM13):
http://www.cyanogenmods.org/forums/...od-13-marshmallow-rom-gt-i9300i-i9301i-i9301q
Otherwise do I have to install only ROMs that came from cyanogenmod.org (CM 12.1)?
https://webcache.googleusercontent.....org/?device=s3ve3g+&cd=1&hl=it&ct=clnk&gl=it
(I used a cached link because at the moment the site is offline)
Thank you.
tramsss said:
Hello,
do you know if I can install the following ROM downloaded from this site (CM13):
http://www.cyanogenmods.org/forums/...od-13-marshmallow-rom-gt-i9300i-i9301i-i9301q
Otherwise do I have to install only ROMs that came from cyanogenmod.org (CM 12.1)?
https://webcache.googleusercontent.....org/?device=s3ve3g+&cd=1&hl=it&ct=clnk&gl=it
(I used a cached link because at the moment the site is offline)
Thank you.
Click to expand...
Click to collapse
CM 12.1 Official
Download: https://dl.dropboxusercontent.com/u/17361181/cm-12.1-20161031-NIGHTLY-s3ve3g.zip
CM13 is not stable to normal use.
Mr.gRisáK said:
CM 12.1 Official
Download: https://dl.dropboxusercontent.com/u/17361181/cm-12.1-20161031-NIGHTLY-s3ve3g.zip
CM13 is not stable to normal use.
Click to expand...
Click to collapse
Thank you for your reply. I tried several ways to flash Cyanogen to my (non rooted) phone but none worked!
I first followed this guide and I tried to flash it using Android recovery, but I get the following error:
E:footer is wrong
E:signature verification failed
Then I tried to follow this guide, both from Windows 7 and Linux, but the terminal hangs on <waiting for device> message when i run fastboot command, from both operating systems. Here I tried to install several drivers (Samsung, Google and so on...) and even tried to follow all the possible ways, including linux settings, to get rid of that error: none worked.
Finally, I tried this guide and I flashed several files: latest TWRP version, some old TWRP versions and even CWM recovery. None worked. The flash is done with no errors, but when I try to go in Recovery Mode I always get the Android recovery.
What the hell is wrong with my phone?
Thank you!
tramsss said:
Thank you for your reply. I tried several ways to flash Cyanogen to my (non rooted) phone but none worked!
I first followed this guide and I tried to flash it using Android recovery, but I get the following error:
E:footer is wrong
E:signature verification failed
Then I tried to follow this guide, both from Windows 7 and Linux, but the terminal hangs on <waiting for device> message when i run fastboot command, from both operating systems. Here I tried to install several drivers (Samsung, Google and so on...) and even tried to follow all the possible ways, including linux settings, to get rid of that error: none worked.
Finally, I tried this guide and I flashed several files: latest TWRP version, some old TWRP versions and even CWM recovery. None worked. The flash is done with no errors, but when I try to go in Recovery Mode I always get the Android recovery.
What the hell is wrong with my phone?
Thank you!
Click to expand...
Click to collapse
What version of S3 Neo do you have ?
I9300I , I9301I ??
Maybe try install original samsung rom with odin and then install again TWRP with odin.
My phone is I9301I.
If i follow your hint, can I flash the latest version among these?
Do you have any other suggestion for flashing the whole ROM with Odin?
(it would be my first time...)
Thank you in advance for your support!
tramsss said:
My phone is I9301I.
If i follow your hint, can I flash the latest version among these?
Do you have any other suggestion for flashing the whole ROM with Odin?
(it would be my first time...)
Thank you in advance for your support!
Click to expand...
Click to collapse
For first time You must register on sammobile (official samsung site).
And try download original ROM from: https://www.sammobile.com/firmwares/database/GT-I9301I/ (official site) and just select your country.
http://odindownload.com/download/Odin3_v3.12.3.zip <--- odin
https://www.youtube.com/watch?v=UBU4MFYiu_I <---- Instruction how to use odin
If everything going to be okey try again install cm12.1
TWRP with odin ---> https://forum.xda-developers.com/showpost.php?p=56085899&postcount=2 2nd Method !
1. Download the ROM = https://dl.dropboxusercontent.com/u/17361181/cm-12.1-20161031-NIGHTLY-s3ve3g.zip
2. Download GAPPS = http://opengapps.org/ my best opinion is ARM 5.1 PICO
3. Transfer the zip files to your SD card
4.. Reboot to recovery mode ( Vol UP + Home + Power )
5. Wipe data / Factory Reset
6. Install CM zip and GApps zip
7. Reboot to system
Enjoy! :fingers-crossed:
I'm downloading the file I9301IXCUAPH1_I9301IITVAOL1_ITV.zip from your link (I have registered an account).
Meanwhile, please tell me: isn't the link I posted before safe?
Mr.gRisáK said:
For first time You must register on sammobile (official samsung site).
And try dowonload from: https://www.sammobile.com/firmwares/database/GT-I9301I/ official site just select your country.
http://odindownload.com/download/Odin3_v3.12.3.zip <--- odin
https://www.youtube.com/watch?v=UBU4MFYiu_I <---- Instruction how to use odin
If everything going to be okey try again install cm12.1
TWRP with odin ---> https://forum.xda-developers.com/showpost.php?p=56085899&postcount=2 2nd Method !
1. Download the ROM = https://dl.dropboxusercontent.com/u/...TLY-s3ve3g.zip
2. Download GAPPS = http://opengapps.org/ my best opinion is ARM 5.1 PICO
3. Transfer the zip files to your SD card
4.. Reboot to recovery mode ( Vol UP + Home + Power )
5. Wipe data / Factory Reset
6. Install CM zip and GApps zip
7. Reboot to system
Enjoy! :fingers-crossed:
Click to expand...
Click to collapse
All went fine! Thank you sooo much!
PS: CM12.1 has wrong link.
tramsss said:
All went fine! Thank you sooo much!
PS: CM12.1 has wrong link.
Click to expand...
Click to collapse
Sorry my fault! :crying:
Now works :highfive:
You are welcome ! :fingers-crossed:

I get an error everytime I try to flash a ROM

Hi, I have this problem that it's driving me crazy, everytime I flash a ROM TWRP gives me this error:
Code:
Updater process ended with ERROR: 7
Error installing zip file: etc
My phone is a SM-J500FN with TWRP Recovery 3.1.0-0 by Zonik, so far I tried LineageOs (both 13.1 and 14.0) and Resurrection Remix, I get always the same error.
edit: also tried with AospExtended, no luck whatsoever.
Odin Eidolon said:
Hi, I have this problem that it's driving me crazy, everytime I flash a ROM TWRP gives me this error:
Code:
Updater process ended with ERROR: 7
Error installing zip file: etc
My phone is a SM-J500FN with TWRP Recovery 3.1.0-0 by Zonik, so far I tried LineageOs (both 13.1 and 14.0) and Resurrection Remix, I get always the same error.
edit: also tried with AospExtended, no luck whatsoever.
Click to expand...
Click to collapse
You need to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms which are based on AOSP/Lineage (cm).
TWRP 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844.
If you still have errors when flashing, then choose in TWRP "Copy log to sdcard" (something like that) and post the recovery.log .
#Henkate said:
You need to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms which are based on AOSP/Lineage (cm).
TWRP 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844.
If you still have errors when flashing, then choose in TWRP "Copy log to sdcard" (something like that) and post the recovery.log .
Click to expand...
Click to collapse
So first I need to downgrade my stock ROM then I can flash Lineage/whatsoever ROM?
Odin Eidolon said:
So first I need to downgrade my stock ROM then I can flash Lineage/whatsoever ROM?
Click to expand...
Click to collapse
Yes. Just like i told you in my previous post, you have to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms based on AOSP/Lineage (cm).
#Henkate said:
Yes. Just like i told you in my previous post, you have to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms based on AOSP/Lineage (cm).
Click to expand...
Click to collapse
Bad news, it doesn't work.
Downgraded to 5.1.1, installed the TWRP linked by you, but still error 7 when I try to flash a ROM.
edit: ok, this time I tried to flash LineageOS 13.1 and it worked. Now I have to figure out how to flash Lineage 14
Odin Eidolon said:
Bad news, it doesn't work.
Downgraded to 5.1.1, installed the TWRP linked by you, but still error 7 when I try to flash a ROM.
edit: ok, this time I tried to flash LineageOS 13.1 and it worked. Now I have to figure out how to flash Lineage 14
Click to expand...
Click to collapse
I've told you:
If you still have errors when flashing, then choose in TWRP "Copy log to sdcard" (something like that) and post the recovery.log.
Click to expand...
Click to collapse
In recovery.log you can see what's the problem.
#Henkate said:
I've told you:
In recovery.log you can see what's the problem.
Click to expand...
Click to collapse
Yeah, you're right, sorry.
But good news, flashed LOS 14 on the old 13.1, everything works fine.
Thanks for your help!

i flashed gsi (project treble) image on bnd-l24 and booted with no problems

i had to find out if it will work followed this guide (https://www.xda-developers.com/flash-generic-system-image-project-treble-device) and it booted will try other project treble roms and report back here also eveything worked i didnt have a apk crash or force close the little time i used it also the camera apk worked great not as good as stock but not as bad as rros:laugh::laugh::laugh::laugh:
You flashed RR ph Treble or Lineage 15.1. How's the battery ? SOT? Does it support VOLTE?
Please Report
Honor 7x project treble
I flashed the Resurrection Remix phh-Treble and the LineageOS 15.1 phh-Treble will try the third and report back so far the battery life is normal haven't notice any abnormal drain and I can't confirm about the volte
dcraffam said:
i had to find out if it will work followed this guide (https://www.xda-developers.com/flash-generic-system-image-project-treble-device) and it booted will try other project treble roms and report back here also eveything worked i didnt have a apk crash or force close the little time i used it also the camera apk worked great not as good as stock but not as bad as rros:laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
Hi Dude, After seeing your message, I tried this on the Honor 7X BND AL10 with EMUI 8 (Manually updated) with the Lineage OS (ARM 64 A-ONLY DEVICE) using the fastboot method. I wiped everything including system and I tried with both stock recovery installed and Twrp recovery installed and I also tried wiping using fastboot "fastboot -w" command. After that I installed using the fastboot and it went well and shows as finished but when I tried to boot, it just doesn't boot at all. I don't even see the lineage OS boot logo or something and eventually it goes to Huawei E recovery.
Could you please tell me which version exactly you flashed like aosp or RR or Lineage and Arm 64 A-only device or AB-device etc... A lot of people would really appreciate that.
Thetpcguy said:
Hi Dude, After seeing your message, I tried this on the Honor 7X BND AL10 with EMUI 8 (Manually updated) with the Lineage OS (ARM 64 A-ONLY DEVICE) using the fastboot method. I wiped everything including system and I tried with both stock recovery installed and Twrp recovery installed and I also tried wiping using fastboot "fastboot -w" command. After that I installed using the fastboot and it went well and shows as finished but when I tried to boot, it just doesn't boot at all. I don't even see the lineage OS boot logo or something and eventually it goes to Huawei E recovery.
Could you please tell me which version exactly you flashed like aosp or RR or Lineage and Arm 64 A-only device or AB-device etc... A lot of people would really appreciate that.
Click to expand...
Click to collapse
im going to write a quick lil guide on how im doing this for you right now
.................................................HOW TO FLASH GSI ON HONOR 7X ................................
DO SO AT OWN RISK I HOLD NO LIABLILTY
LETS BEGIN
1 you must be on stock emui 8 you must not have a pin set or device encrypted or frp lock and boot loader must be unlocked
2 download one of the 3 images listed here ( https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ )
( i personally only tried the ( LineageOS 15.1 phh-Treble Thread) and the (Resurrection Remix phh-Treble Thread) ((((((download the a only arm64image))))))))
3 download the 8.1 pico gaapps package for arm64 found here ( http://opengapps.org/ )
4 now you must download this twrp i know it works from the honor 7x oreo twrp ill upload it or you can download it from the thread
5 flash the twrp twrp_ramdisk_oreo_7-4-18.img linked in fastboot then reboot recovery (note) there will be two recoverys i upload one needed to flash the (gsi) and the other twrpimgmount_ramdisk.img is used to flash (((twrp backup)) to go back to stock oreo as the first one wont boot once the (gsi) is flashed only the mount twrp.img will the( twrp_ramdisk_oreo_7-4-18.img) will boot with the stock emui beta for some reason
6 create full backup with the twrp_ramdisk_oreo_7-4-18.img flashed in step 5 (personally i backed up everything i could )
7 factory reset data using twrp
8 flash the (gsi) image u downloaded in step 2 to system image .......... tap install change the type from zip to image select the (gsi) and flash to system image partion
9 flash pico gapps 8.1 arm 64 ( the rest are to big o flash ))
reboot device tada you booted a stock (gsi)
i couldnt upload recoveries but they can be found here https://forum.xda-developers.com/devdb/project/?id=25826#downloads
to go back to stock emui fastboot recovery flash the twrpimgmount.img factory reset and restore backup some partions will fail like bdm image,, data,, the partions that do uncheck those and restore backup agin flash stock recovery (RECOVERY_RAMDIS.img) and factory reset and you will be on emui8 agin
let me know if you have any problems im going t ry the phh treble aosp (gsi) now
Thetpcguy said:
Hi Dude, After seeing your message, I tried this on the Honor 7X BND AL10 with EMUI 8 (Manually updated) with the Lineage OS (ARM 64 A-ONLY DEVICE) using the fastboot method. I wiped everything including system and I tried with both stock recovery installed and Twrp recovery installed and I also tried wiping using fastboot "fastboot -w" command. After that I installed using the fastboot and it went well and shows as finished but when I tried to boot, it just doesn't boot at all. I don't even see the lineage OS boot logo or something and eventually it goes to Huawei E recovery.
Could you please tell me which version exactly you flashed like aosp or RR or Lineage and Arm 64 A-only device or AB-device etc... A lot of people would really appreciate that.
Click to expand...
Click to collapse
Try Flashing AOSP 8.1 ARM64 A-Only device system.img as its more updated than lineage or RROS.
Only, A-Only system.img should work on our device as per treble wiki on github.
TrainerRed said:
Try Flashing AOSP 8.1 ARM64 A-Only device system.img as its more updated than lineage or RROS.
Only, A-Only system.img should work on our device as per treble wiki on github.
Click to expand...
Click to collapse
Hi, I already flashed the AOSP version and it's booted up and working fine but I wanted the lineageOS as it has all the built in customisations. I just don't know why the lineage os didn't work as it was reported above the it's working. Maybe it's the variant thing? I have BND AL-10. I don't know Anyway thanks!!
Thetpcguy said:
Hi, I already flashed the AOSP version and it's booted up and working fine but I wanted the lineageOS as it has all the built in customisations. I just don't know why the lineage os didn't work as it was reported above the it's working. Maybe it's the variant thing? I have BND AL-10. I don't know Anyway thanks!!
Click to expand...
Click to collapse
How is the rom ? Is it can be used as daily driver ?
You still using AOSP or back to EMUI already ?
If you don't mind can you write review of Whats working and Whats Not?
TrainerRed said:
How is the rom ? Is it can be used as daily driver ?
You still using AOSP or back to EMUI already ?
If you don't mind can you write review of Whats working and Whats Not?
Click to expand...
Click to collapse
I installed it without any gapps or anything just bare minimum just to see if it boots or not. Here is what I observed during my short stay:laugh:
1. There is no VOLTE
2. The camera is working
3. I can't talk much about battery but there is no crazy drain as such so yeah
4. I don't know why you said it's the latest but the security patch is the same based on March, 2018 and it's android 8.1
5. The launcher seemed like the ice cream sandwich (Took me back to good ol days)
6. It felt smooth and unusual lag
I can't say much and suggest whether or not you can use it as a daily driver when I never used it as a daily driver. It's your call.
Hit the "Thanks" button if you really feel like thanking me:good:
dcraffam said:
.................................................HOW TO FLASH GSI ON HONOR 7X ................................
DO SO AT OWN RISK I HOLD NO LIABLILTY
LETS BEGIN
1 you must be on stock emui 8 you must not have a pin set or device encrypted or frp lock and boot loader must be unlocked
2 download one of the 3 images listed here ( https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ )
( i personally only tried the ( LineageOS 15.1 phh-Treble Thread) and the (Resurrection Remix phh-Treble Thread) ((((((download the a only arm64image))))))))
3 download the 8.1 pico gaapps package for arm64 found here ( http://opengapps.org/ )
4 now you must download this twrp i know it works from the honor 7x oreo twrp ill upload it or you can download it from the thread
5 flash the twrp twrp_ramdisk_oreo_7-4-18.img linked in fastboot then reboot recovery (note) there will be two recoverys i upload one needed to flash the (gsi) and the other twrpimgmount_ramdisk.img is used to flash (((twrp backup)) to go back to stock oreo as the first one wont boot once the (gsi) is flashed only the mount twrp.img will the( twrp_ramdisk_oreo_7-4-18.img) will boot with the stock emui beta for some reason
6 create full backup with the twrp_ramdisk_oreo_7-4-18.img flashed in step 5 (personally i backed up everything i could )
7 factory reset data using twrp
8 flash the (gsi) image u downloaded in step 2 to system image .......... tap install change the type from zip to image select the (gsi) and flash to system image partion
9 flash pico gapps 8.1 arm 64 ( the rest are to big o flash ))
reboot device tada you booted a stock (gsi)
i couldnt upload recoveries but they can be found here https://forum.xda-developers.com/devdb/project/?id=25826#downloads
to go back to stock emui fastboot recovery flash the twrpimgmount.img factory reset and restore backup some partions will fail like bdm image,, data,, the partions that do uncheck those and restore backup agin flash stock recovery (RECOVERY_RAMDIS.img) and factory reset and you will be on emui8 agin
let me know if you have any problems im going t ry the phh treble aosp (gsi) now
Click to expand...
Click to collapse
Thanks for your detailed steps you documented.
But I did much simpiler. (but i did not flash gapps- so that would need to add some steps)
1. starting from stock EmUI 8 with stock recovery
2. Reboot to recovery perform factory reset.
3. when reset is done, while still in recovery plug in usb to phone and pc
4. select reboot, When screen goes off press and hold volume down. You will boot to fastboot
5. fastboot flash system C:\Users\Mr\Downloads\system-arm64-aonly.img
(your path to file will be different, unless you are also user "mr")
To return to stock do same steps but point fastboot flash to the stock emui system.img
Huawei camera works?
Which will you think better? Aosp lineages rr?
Thx
I tried flashing treble and lineage from twrp but neither worked on my bnd-l24. After flashing it just boots to the fastboot screen.
eskimowarrior7 said:
I tried flashing treble and lineage from twrp but neither worked on my bnd-l24. After flashing it just boots to the fastboot screen.
Click to expand...
Click to collapse
I have flashed to L24-- PHH RRos. It worked ok, gave a verdor image miss-match error.
did you factory reset before booting,
mrmazak said:
I have flashed to L24-- PHH RRos. It worked ok, gave a verdor image miss-match error.
did you factory reset before booting,
Click to expand...
Click to collapse
Yes, even tried the process a few more times. No luck.
eskimowarrior7 said:
Yes, even tried the process a few more times. No luck.
Click to expand...
Click to collapse
each time I started with flash stock recovery, then did factory reset
then from recovery reboot directly to fastboot
and fastboot flash system
mrmazak said:
Thanks for your detailed steps you documented.
But I did much simpiler. (but i did not flash gapps- so that would need to add some steps)
1. starting from stock EmUI 8 with stock recovery
2. Reboot to recovery perform factory reset.
3. when reset is done, while still in recovery plug in usb to phone and pc
4. select reboot, When screen goes off press and hold volume down. You will boot to fastboot
5. fastboot flash system C:\Users\Mr\Downloads\system-arm64-aonly.img
(your path to file will be different, unless you are also user "mr")
To return to stock do same steps but point fastboot flash to the stock emui system.img
Click to expand...
Click to collapse
Hi, Could you tell me which model and variant of Honor 7x you are using. I tried this on BND AL10 and it doesn't boot with all the stuff above. However, I could boot into AOSP GSI.
For BND AL10 users, Only the AOSP GSI is working but both the RR and the Lineage are not working. I tried all three with same method.
1. Wiped/ Factory reset
2. Installed using "fastboot flash system system.img"
I posted this message because I wasted a lot of time & data LOL so maybe this would be helpful to others. However, if somehow you manage to do it on AL10, please post it here.
Thetpcguy said:
Hi, Could you tell me which model and variant of Honor 7x you are using. I tried this on BND AL10 and it doesn't boot with all the stuff above. However, I could boot into AOSP GSI.
Click to expand...
Click to collapse
I'm using the L24
Thetpcguy said:
For BND AL10 users, Only the AOSP GSI is working but both the RR and the Lineage are not working. I tried all three with same method.
1. Wiped/ Factory reset
2. Installed using "fastboot flash system system.img"
I posted this message because I wasted a lot of time & data LOL so maybe this would be helpful to others. However, if somehow you manage to do it on AL10, please post it here.
Click to expand...
Click to collapse
Any updates if I can use it as my daily driver?

[Fastboot ROM] Stock Android 10 v11.0.11.0 April

Stock Android 10 Fastboot Rom Project
How i made is using payload dumper to unpack payload.bin file inside recovery rom and editing flashing scripts to be usable for this unpacked files.
Requirements
ADB must be installed on PC (Click to ADB to download if you dont have it)
Unlocked Bootloader( fastboot flashing unlock + fastboot flashing unlock_critical )
Steps to install
> Unzip zip file into desktop and open the folder.
> Then run flash_all.bat file and it will install the new update and reboot to system automatically.
(Your files will not be erased if you already unlocked bootloader.)
Latest - v11.0.11.0 - Global - April Security Patch
Recommended Server : Quebec, Canada
DO NOT MIRROR THE DOWNLOAD LINKS BEFORE ASKING ME !
AndroidFileHost - v11.0.11.0 April Security Patch
AndroidFileHost - All Versions
If you want to lock your bootloader after installing it , you can use flash_all_lock.bat OR i prefer to lock it manually by doing this;
Run flash_all.bat and make sure phone boots after installing then open fastboot mode and type
fastboot flashing lock_critical
Then phone will restart automatically into recovery and wipe data.
After screen goes black hold power + volume down button (to open fastboot again) then type
fastboot flashing lock
And after booting you can disable OEM unlock from developer options if you want to.
XDA:DevDB Information
[Fastboot ROM] Android 10 Update , ROM for the Xiaomi Mi A3
Contributors
TechGenius
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader
Version Information
Status: Stable
Current Stable Version: 11.0.11.0
Stable Release Date: 2020-04-07
Created 2020-03-19
Last Updated 2020-04-07
XDA:DevDB Information
[Fastboot ROM] Stock Android 10, ROM for the Xiaomi Mi A3
Contributors
TechGenius
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader
Version Information
Status: Stable
Current Stable Version: 11.0.11.0
Stable Release Date: 2020-04-07
Created 2020-04-07
Last Updated 2020-04-07
@TechGenius
thanks man
i updated my phone via ota rom
would you please put boot.img of this rom , it does not exist in ota file !
really good job bro thanks again
Is this possible on build with Magisk without twrp
Thanks dude!
Would your script flash on both slots A & B?
i does not go further than sending modem_b.
what can i do?
C:\Users\MingBee\Downloads\laurel_sprout_global_images_V11.0.11.0.QFQMIXM_10.0>fastboot flash modem_b "C:\Users\MingBee\Downloads\laurel_sprout_global_images_V11.0.11.0.QFQMIXM_10.0\images\modem.img" ||
Sending 'modem_b' (114084 KB)
Click to expand...
Click to collapse
Hi! Does it would update 11.0.7.0 with root and TWRP, without losing the data?
Thank you!!
any one that downloaded this rom please upload boot.img
#MmdRza said:
any one that downloaded this rom please upload boot.img
Click to expand...
Click to collapse
https://forum.xda-developers.com/sho...&postcount=340
PS
@TechGenius thanks for making Fastboot ROM for April build. You are truly a genius.
moyses said:
Is this possible on build with Magisk without twrp
Click to expand...
Click to collapse
#MmdRza said:
any one that downloaded this rom please upload boot.img
Click to expand...
Click to collapse
Have a look at THIS POST, you'll find the original boot and the pre-rooted one
HERE is the how-to guide and a list of original boots.
fuqi said:
i does not go further than sending modem_b.
what can i do?
Click to expand...
Click to collapse
did you solved?
Just installed using a notebook with windows 10 64Bit (i had issue with 32bit laptop)
Everything is fine but still receive the notification of android 10 update to install
i used a .bit file from a different release and it worked.
no update nag for me.
hi , at first thanks for your work!
2nd question: anibody have issues installing twrp? i' m stuck on fastboot everytime i try to install it.
Same issue here.
phillow said:
Same issue here.
Click to expand...
Click to collapse
i try to install the patched boot image in the previous page for having root with magisk, give it a try :good:
Is this the one that got pulled off?
Therion8594 said:
i try to install the patched boot image in the previous page for having root with magisk, give it a try :good:
Click to expand...
Click to collapse
Have you tried it ? I flashed 11.0.11.0 fastboot A10 on girls Mi A3 .. and rooted it without TWRP using magisk 20.4 and im facing reboot to fastboot issue instead to recovery after trying any possible custom recovery there is for this phone..
Masleyko said:
Have you tried it ? I flashed 11.0.11.0 fastboot A10 on girls Mi A3 .. and rooted it without TWRP using magisk 20.4 and im facing reboot to fastboot issue instead to recovery after trying any possible custom recovery there is for this phone..
Click to expand...
Click to collapse
Yes i don't know why but every recovery i've tried It go go fastboot..flash the boot image in the previous Page and everything work .
Therion8594 said:
Yes i don't know why but every recovery i've tried It go go fastboot..flash the boot image in the previous Page and everything work .
Click to expand...
Click to collapse
Because the twrp .IMG file was built only for pie. For Android 10 you will have to use this https://mega.nz/file/1HRAWYKQ#V9OmPxSy3r06qmW8uGszSEBp4qOBJMbmvsaCow2mTJw
Once it is flashed you can use the standard twrp or orangefox or shrp recovery.zip if you want to keep a custom recovery installed
Credits again to @Sapper Morton for creating this Android 10 flashable image
garylawwd said:
Because the twrp .IMG file was built only for pie. For Android 10 you will have to use this https://mega.nz/file/1HRAWYKQ#V9OmPxSy3r06qmW8uGszSEBp4qOBJMbmvsaCow2mTJw
Once it is flashed you can use the standard twrp or orangefox or shrp recovery.zip if you want to keep a custom recovery installed
Credits again to @Sapper Morton for creating this Android 10 flashable image
Click to expand...
Click to collapse
Yes, i've already flashed but i come back to MIUI for the battery, thanks anyway :good:

Guide to flash realmeUI 2.0 beta builds [Global Variant Only]

DISCLAIMER: YOU ARE RESPONSIBLE FOR WHAT YOU DO​The only reason behind posting this guide is because now we have a way to fix device if any unusual things happen after flashing beta builds. Beginners & noobs who doesn't have any idea about flashing stuff should stay away.
PREREQUISITES:
1. Bootloader Unlocked Device
2. OrangeFox
3. Stable OZIP (Android 10 | realmeUI 1.0 | C35)
4. Beta ZIP (Android 11 | realmeUI 2.0 | F06)
5. Unofficial OrangeFox beta build (For realmeUI 2.0 A11 FW only)
6. realmeUI 2.0 stock recovery
7. A11 VBMETA
8. Patched VBMETA
PROCESS TO FLASH:
1. Just to be on safer side we are going to make sure everything is stock & all partitions are unmodified. So reflash latest Stable OZIP (C35) via OrangeFox.
2. Format data & reboot to System (This is optional but better to do it, we never know what might happen with realme device)
3. Reboot back to Bootloader if realmeUI 1.0 boots fine
4. Flash OrangeFox build which you used previously & also flash patched vbmeta (fastboot flash vbmeta patched_vbmeta.img)otherwise you get "Boot is destroyed........"
5. Boot into custom recovery & copy downloaded Beta ZIP
6. Flash the Beta ZIP & format data.
7. Reboot to System. realmeUI 2.0 should boot now.
COMMON ISSUES & FIXES:
1. Device stuck at white realme splash logo
Sol. Few people reported it booted when they flashed patched vbmeta so you can first try that. If doesn't work then you can flash A11 vbmeta (fastboot flash vbmeta vbmeta.img) attached here & reboot to system
2. Device stuck at Yellow realme boot animation
Sol. If it's stuck for more than 2-3mins then reboot to bootloader & format data by executing fastboot erase userdata ., never do fastboot -w it's messing up data partition in A11 due to new changes introduced by realme
3. Stuck in bootloader (fastboot)
Sol. Flash the unofficial OrangeFox rescue build & boot into it, copy C35 OZIP to internal storage. Flash it & format data. Reboot to System. Wait for public realmeUI 2.0 release.
4. Unofficial OrangeFox beta build stuck at Ofox splash & display keeps blinking
Sol. This happens because Ofox can't decrypt realmeUI 2.0 data, only way to boot this ofox build properly is by formatting data, reboot back to bootloader. fastboot erase userdata
5. Device doesn't have realmeUI 2.0 Stock Recovery
Sol. Flash the attached stock recovery
reserved
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
bharatgsp said:
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
Click to expand...
Click to collapse
na it doesn't work
ChromiumPD said:
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Click to expand...
Click to collapse
Right will update guide, thank you
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
kurtextrem said:
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
Click to expand...
Click to collapse
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Zippka224 said:
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Click to expand...
Click to collapse
edited guide, use ofox only. TWRP doesn't seem to work for everyone.
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
4j17h said:
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
Click to expand...
Click to collapse
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Tierri said:
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
Click to expand...
Click to collapse
Well there are two ways, we can use stock recovery to downgrade from beta builds to C34
Another way would be to flash unofficial Ofox build, copy C34 OZIP to internal storage & flash it.
kurtextrem said:
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Click to expand...
Click to collapse
OTA updater app is verifying the update & rebooting to stock recovery, so if we can figure out the same way we can install custom ozips via stock recovery too
How would you recommend to bring over apps & their settings to A11? After formatting data they'll be lost. Which backup method is able to restore them? Have you rooted it already?
Magisk?
Cool ! It works fine thank you.
but I noticed that the "Unofficial OrangeFox beta build" cant mount internal storage issue with following error : "could not mount /data and unable to find crypto footer"
So is there another way to Root my device without wiping data?
Hi
First Thank you for this post .
I want to restore a stock recovery UI 1.0 now i am using orangefox recovery on C.34
can i restore without format data or waiting UI 2.0 stable ??
Many Thanks
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
tuga49 said:
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
Click to expand...
Click to collapse
try to install patched vbmeta its work form me
So for me I dirty flashed the f06.zip beta on c.35 in official [email protected]_1 release and flashed vbmetaA11 but it failed to then i flashed patched_vbmeta.img and voila it booted just fine and optimizing apps appeared.
Thanks very much to Original Poster we can now use Realme UI 2.0 because of him.
Thanks a lot once again

Categories

Resources