Related
I prepared a stripped down version for NUBIA RED MAGIC 2.36 CN ROM (you can find the full ROM here http://ui.nubia.cn/rom)
I take out a lot of CN applications. You can flash over the OpenGAPPS and get Google applications, make the ROM more usable in the European countries.
DOWNLOAD
https://mega.nz/#F!xsFnkQDL!XQXUTVjq8xDfvG_OElXTYw
Install:
- First: don't forget to backup your files, if you come from Global ROM you will need to erase also internal storage of your phone!
- you will need TWRP installed. Look how to in sakilxda's thread (thank you sakilxda! ): https://forum.xda-developers.com/red-magic/how-to/unlock-bootloader-flasah-twrp-nubia-red-t3828466
- Download Oppen Gapps for ARM 64 - 8.1 nano (or micro/mini etc at your need - https://opengapps.org/)
- copy the downloaded ROM and GAPPS in your phone's internal storage
- go in TWRP, Advanced Wipe: wipe Dalvik/Art Cache, Cahe, Syste, Data.
- go to install menu and chose the ROM add to zip list also the GAPPS you downloaded: IS IMPORTANT TO FLASH GAPPS IMMEDIATELY AFTER ROM, ELSE WILL NOT WORK CORRECTLY!
- OPTIONAL: you can add also blu_spark r36 Red Magic's kernel (THANK YOU blu_spark) from: https://forum.xda-developers.com/red-magic/development/kernel-t3813055
- Wipe cache when finish and reboot!
Good luck!
Screen shots
Great! I am going to try now and will let you know the result. Thank you so much!
---------- Post added at 03:55 AM ---------- Previous post was at 03:52 AM ----------
I faced the error: "invalid zip file format" ----> this is my mistake, sorry ^^
---------- Post added at 04:17 AM ---------- Previous post was at 03:55 AM ----------
I have flashed but stucking at " checking for updates"...
---------- Post added at 04:42 AM ---------- Previous post was at 04:17 AM ----------
I have passed the problem. I am feeling happy with this rom. Thanks a lot!
---------- Post added at 04:50 AM ---------- Previous post was at 04:42 AM ----------
@ABM30: could you please guide me to root it?
Flash magisk zip file check xda through twrp and then install the magisk manager apk like any other app.
How passed the problem can you tell us so if anyone faced it to know how to over passed it?
strakell said:
How passed the problem can you tell us so if anyone faced it to know how to over passed it?
Click to expand...
Click to collapse
If you stuck on searching updates: just push power button and slide the restart button.
After this it will start over but will pass the update chek!
For root: download the magisk.apk and Magisk-v18.1(18100).zip from download link that I have given.
Put them in your phones internal storage. Install magisk.apk and run it once.
Then go in recovery TWRP and instal Magisk-v18.1(18100).zip, wipe cahe when asked.
Restart phone =>ROOTED!
You can find Magisk also in google Play!.
Have fun!
strakell said:
How passed the problem can you tell us so if anyone faced it to know how to over passed it?
Click to expand...
Click to collapse
ok
1. The error: "invalid zip file format" ----> I forgot to extract the zip file that I download from Mega.nz .
2. Stucking at " checking for updates"... ---> I removed sim card then restarted. After that, I skipped all of setup steps. after all, I can access home screen launcher.
Now I found the bug: I can not access to "developer options" in settings
---------- Post added at 06:48 PM ---------- Previous post was at 06:45 PM ----------
ABM30 said:
If you stuck on searching updates: just push power button and slide the restart button.
After this it will start over but will pass the update chek!
For root: download the magisk.apk and Magisk-v18.1(18100).zip from download link that I have given.
Put them in your phones internal storage. Install magisk.apk and run it once.
Then go in recovery TWRP and instal Magisk-v18.1(18100).zip, wipe cahe when asked.
Restart phone =>ROOTED!
You can find Magisk also in google Play!.
Have fun!
Click to expand...
Click to collapse
thank you, but where are download links of the magisk.apk and Magisk-v18.1(18100).zip that you told?
oh sorry, I have saw them: https://mega.nz/#F!xsFnkQDL!XQXUTVjq8xDfvG_OElXTYw
ABM30 could you please explain step by step how I can get twrp and how go back to official recovery so I can flash official ROM ,I really appreciate that!
strakell said:
ABM30 could you please explain step by step how I can get twrp and how go back to official recovery so I can flash official ROM ,I really appreciate that!
Click to expand...
Click to collapse
I can help you:
Download:
- Rom: https://mega.nz/#F!xsFnkQDL!XQXUTVjq8xDfvG_OElXTYw
-Open Gapps for ARM 64 - 8.1 nano (or micro/mini etc at your need - https://opengapps.org/)
1. Boot to bootloader and unlock bootloader: "fastboot oem nubia_unlock NUBIA_NX609J"
2. flash twrp: twrp-3.2.3-x_blu_spark_v9.85_redmagic.img
3. reboot to recovery (twrp), copy the downloaded ROM and GAPPS in your phone's internal storage
4. in TWRP, Advanced Wipe: wipe Dalvik/Art Cache, Cahe, Syste, Data.
5. go to install menu and chose the ROM to flash
6. FLASH GAPPS IMMEDIATELY AFTER ROM, ELSE WILL NOT WORK CORRECTLY! (IT IS IMPORTANT!!)
7. Wipe cache when finish and reboot.
*There are some little different if you want to use official rom from CN ROM (you can find the full ROM here http://ui.nubia.cn/rom)
Download: CN Rom from the link above
1. Extract from the rom to get 2 files: "recovery.img" & "boot.img"
2. Copy "recovery.img" & "boot.img" to Minimal ADB and Fastboot, open command window from here.
3. reboot to bootloader (power off the device then back on with 'vol down' + power button)
4. unlock bootloader: "fastboot oem nubia_unlock NUBIA_NX609J"
5. Wipe your device.
"fastboot -w"
6. Flash recovery:
"fastboot flash recovery recovery.img"
7. Update your ROM.
fastboot update <CNRomFile.zip>
Your phone will update and automatically reboot into the new ROM.
tlgod said:
I can help you:
Download:
- Rom: https://mega.nz/#F!xsFnkQDL!XQXUTVjq8xDfvG_OElXTYw
-Open Gapps for ARM 64 - 8.1 nano (or micro/mini etc at your need - https://opengapps.org/)
1. Boot to bootloader and unlock bootloader: "fastboot oem nubia_unlock NUBIA_NX609J"
2. flash twrp: twrp-3.2.3-x_blu_spark_v9.85_redmagic.img
3. reboot to recovery (twrp), copy the downloaded ROM and GAPPS in your phone's internal storage
4. in TWRP, Advanced Wipe: wipe Dalvik/Art Cache, Cahe, Syste, Data.
5. go to install menu and chose the ROM to flash
6. FLASH GAPPS IMMEDIATELY AFTER ROM, ELSE WILL NOT WORK CORRECTLY! (IT IS IMPORTANT!!)
7. Wipe cache when finish and reboot.
*There are some little different if you want to use official rom from CN ROM (you can find the full ROM here http://ui.nubia.cn/rom)
Download: CN Rom from the link above
1. Extract from the rom to get 2 files: "recovery.img" & "boot.img"
2. Copy "recovery.img" & "boot.img" to Minimal ADB and Fastboot, open command window from here.
3. reboot to bootloader (power off the device then back on with 'vol down' + power button)
4. unlock bootloader: "fastboot oem nubia_unlock NUBIA_NX609J"
5. Wipe your device.
"fastboot -w"
6. Flash recovery:
"fastboot flash recovery recovery.img"
7. Update your ROM.
fastboot update <CNRomFile.zip>
Your phone will update and automatically reboot into the new ROM.
Click to expand...
Click to collapse
Thank you very much for your time ,I think you forget to write in line 2 after the unlock bootloader what I have to type in adb for the custom recovery
tlgod said:
I can help you:
Download:
- Rom: https://mega.nz/#F!xsFnkQDL!XQXUTVjq8xDfvG_OElXTYw
-Open Gapps for ARM 64 - 8.1 nano (or micro/mini etc at your need - https://opengapps.org/)
1. Boot to bootloader and unlock bootloader: "fastboot oem nubia_unlock NUBIA_NX609J"
2. flash twrp: twrp-3.2.3-x_blu_spark_v9.85_redmagic.img
3. reboot to recovery (twrp), copy the downloaded ROM and GAPPS in your phone's internal storage
4. in TWRP, Advanced Wipe: wipe Dalvik/Art Cache, Cahe, Syste, Data.
5. go to install menu and chose the ROM to flash
6. FLASH GAPPS IMMEDIATELY AFTER ROM, ELSE WILL NOT WORK CORRECTLY! (IT IS IMPORTANT!!)
7. Wipe cache when finish and reboot.
*There are some little different if you want to use official rom from CN ROM (you can find the full ROM here http://ui.nubia.cn/rom)
Download: CN Rom from the link above
1. Extract from the rom to get 2 files: "recovery.img" & "boot.img"
2. Copy "recovery.img" & "boot.img" to Minimal ADB and Fastboot, open command window from here.
3. reboot to bootloader (power off the device then back on with 'vol down' + power button)
4. unlock bootloader: "fastboot oem nubia_unlock NUBIA_NX609J"
5. Wipe your device.
"fastboot -w"
6. Flash recovery:
"fastboot flash recovery recovery.img"
7. Update your ROM.
fastboot update <CNRomFile.zip>
Your phone will update and automatically reboot into the new ROM.
Click to expand...
Click to collapse
THANK YOU tlgod! Well done!
There is also the alternative to go back to official ROM:
1. Download the official ROM - CN or Global - you can find links in this thread
2. Copy ROM in internal storage (preferable in root)
3. Go in Settings-System Update-Menu (3 dots in upper right corner) - local update
4. Choose the ROM you downloaded and install > if you choose CN ROM: you are back to original recovery, boot, ROM
5. If you want to go back to global ROM you will have some more steps: need to wipe all USER DATA and CACHE in original Recovery after update (this will erase your internal memory !!!!!!!!!!!!!!! so BACKUP BACKUP....!!!!!!, now the phone can be restarted.
Global ROM will encrypt your Phone!!!! therefore when you go from Global to CN or back you need to wipe your USER DATA and lost everything from internal storage!!!!!!!!!!!!!
You can watch also: https://www.youtube.com/watch?v=z5wOxvzxrfQ
Is in Spanish but ..self explanatory
strakell said:
Thank you very much for your time ,I think you forget to write in line 2 after the unlock bootloader what I have to type in adb for the custom recovery
Click to expand...
Click to collapse
In download link I given you can find everything you need: ROM, Magisk and now also TWRP: twrp-3.2.3-0-nx609j.img
it can be used for TWRP installing as mentioned by tlgod!
tlgod said:
ok
1. The error: "invalid zip file format" ----> I forgot to extract the zip file that I download from Mega.nz .
2. Stucking at " checking for updates"... ---> I removed sim card then restarted. After that, I skipped all of setup steps. after all, I can access home screen launcher.
Now I found the bug: I can not access to "developer options" in settings
---------- Post added at 06:48 PM ---------- Previous post was at 06:45 PM ----------
thank you, but where are download links of the magisk.apk and Magisk-v18.1(18100).zip that you told?
oh sorry, I have saw them: https://mega.nz/#F!xsFnkQDL!XQXUTVjq8xDfvG_OElXTYw
Click to expand...
Click to collapse
Yes, I put everything in one folder (ROM Magisk.apk and zip, twrp), so you don't need another link.
For developer bug: you need to root the phone and you will get acces to developer options!
P.S. Sometimes a restart is also a good option!
ABM30 said:
In download link I given you can find everything you need: ROM, Magisk and now also TWRP: twrp-3.2.3-0-nx609j.img
it can be used for TWRP installing as mentioned by tlgod!
Click to expand...
Click to collapse
Like this:
fastboot flash recovery twrp-3.2.3-0-nx609j.img
Is it correct?
strakell said:
Like this:
fastboot flash recovery twrp-3.2.3-0-nx609j.img
Is it correct?
Click to expand...
Click to collapse
rename the recovery twrp-3.2.3-0-nx609j.img to recovery.img and then: fastboot flash recovery recovery.img this is how it worked to me.
ABM30 said:
rename the recovery twrp-3.2.3-0-nx609j.img to recovery.img and then: fastboot flash recovery recovery.img this is how it worked to me.
Click to expand...
Click to collapse
Now I get it right. Thanks.
ABM30 said:
Yes, I put everything in one folder (ROM Magisk.apk and zip, twrp), so you don't need another link.
For developer bug: you need to root the phone and you will get acces to developer options!
P.S. Sometimes a restart is also a good option!
Click to expand...
Click to collapse
Thank you, I have done that and It works!
A little help please , I did the procedure to unlock bootloader and flash custom recovery all went ok right away from the fastboot mode I went to twrp which was in Chinese I change the language to English I didn't do anything enything else because for now I only wanted to have custom recovery to flash magisk, i reboot to ROM I had all nice till now but when I'm trying to reboot to recovery to flash magisk I can't find the twrp only official recovery ,what am I doing wrong?
strakell said:
A little help please , I did the procedure to unlock bootloader and flash custom recovery all went ok right away from the fastboot mode I went to twrp which was in Chinese I change the language to English I didn't do anything enything else because for now I only wanted to have custom recovery to flash magisk, i reboot to ROM I had all nice till now but when I'm trying to reboot to recovery to flash magisk I can't find the twrp only official recovery ,what am I doing wrong?
Click to expand...
Click to collapse
Unfortunately it has happened to me also at the beginning. My unlocking counter is at 20.
So you need to do the following:
Unlock your bootloader again, flash TWRP (again ), go through ROM install procedure (again) as I mentioned in 1st post, but this time put also blu_spark r36 Red Magic's kernel in zip list to be flashed. In this way the original kernel (which has some security measures implemented in it and in case of some modifications in ROM it will overwrite the recovery with a backup from internal memory, I think is located in DATA folder...) will be overwritten and recovery will be preserved. At least this procedure I find at this moment.
Good Luck!
i'm try Red Magic OS V3.06 android Pie, and new Game Mode are perfect, but not have gapp, im test flash gapp in twrp but not work, you can pls help me add opengapp to new rom.
Thanks you very much.
chipheo62 said:
i'm try Red Magic OS V3.06 android Pie, and new Game Mode are perfect, but not have gapp, im test flash gapp in twrp but not work, you can pls help me add opengapp to new rom.
Thanks you very much.
Click to expand...
Click to collapse
Till now I didn't succeed to, but keep working on.
Hello
I am trying to update for a while now, but I just cannot get it installed.
I already have TRWP 3.3.0.0 running on a rooted Pocophone F1.
I am still kind of newbie using LOS, sorry. Some stuff I still don't understand even though spending lots of time reading and googling and reading...
What I do:
I start TRWP and wipe: WIPE ADVANCE Dalvik,Cache,System,Data
I install in the following order:
beryllium-V10.3.6.0.PEJMIXM-9.0-vendor-firmware
lineage-16.0-20191003-nightly-beryllium-signed
Disable_Dm-Verity_ForceEncrypt_02.04.2019
Magisk-v19.4
open_gapps-arm64-9.0-mini-20191003
then I reboot, stare a while on the working LOS-installing-log and...
boot to TRWP
I am experiencing problems while installation for some time, so I already tried:
- wiping dalvik after each zip during installation
- Magisk-v19.3
- leave out open-gapps
- beryllium-9.6.27-9.0-vendor-firmware
- lineage-16.0-20190807-nightly-beryllium-signed
- lineage-16.0-20190929-nightly-beryllium-signed
Where do I find information on which corresponding vendor/firmware to be used for LOS16?
Looking at the screen while installation of lineage-16.0-20191003-nightly-beryllium-signed, I read: "... Target: ...V10.2.3.0.PEJMIXM..."
So I guess I should flash that mentioned vendor/firmware version for that mentioned LOS version, but I just don't know where to download that vendor/firmware. It is not available on the server of akhilnarang...
Maybe I'm wrong and there might be another problem, I just do not know what to do.
Best regards
what rom your using before you installed los?
Clean flash would be needed ..you should wipe internal too to get it working , dont forget to remove all you password , fingerprint and face unlock.
Boot to recovery wipe system/dalvik/data/cache/internal before doing this you need to do a nandrioid back up..
do this:
download the lastest vendor:
beryllium-V10.3.8.0.PEJMIXM-9.0-vendor-firmware
next the LOS rom:
lineage-16.0-20191003-nightly-beryllium-signed
open_gapps-arm64-9.0-mini-20191003
and then
download the latest DFE version 19.3:
you can download it in telegram pocof1 group chat
and then wipe dalvik cache after that reboot system
first boot reboot to twrp recovery and the flash magisk v19.3 the reboot system....
i hope this method will help you..goodluck!!!
Prior to now, I had a 6 month old LOS working up to now.
My last attempt:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
says: "If you plan to install custom kernels, flash the zip AFTER installing Magisk".
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Zackptg5 says:"If you're not encrypted: flash all of your stuff, then FLASH THIS ZIP LAST"
I use the most recent DFE Disable_Dm-Verity_ForceEncrypt_10.01.2019 from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/page64
most actual vendor/firmware i find here: https://xiaomifirmwareupdater.com/firmware/beryllium/
is: fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
I have not found a trustworthy source for the very new 10.3.8.0, but this should not be an issue...
So then, my new order is:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- Magisk-v19.4
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
Done that and REBOOT SYSTEM and....
Pocophone boots into FASTBOOT...
I am really pissed off at this point.
I can still enter TRWP 3.3.0.0 by pressing ON+VOLUP
I don't know any further.
So then, my new order is:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- Magisk-v19.4
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
Done that and REBOOT SYSTEM and....
Pocophone boots into FASTBOOT...
Why you didn't follow my instructions? clearly you dont understand ...
Oh...
I read your reply again, so is it correct you want me to:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT to RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
? ok in this order?
Sorry, found another mistake in my last description, now I tried:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT SYSTEM
-> after REBOOT SYSTEM, Poco F1 instantly starts into FASTBOOT. I then press ON+VOLUP to enter RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
-> still, Poco F1 instantly starts into FASTBOOT again.
That is where I am stuck now.
Andi900rr said:
Sorry, found another mistake in my last description, now I tried:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT SYSTEM
-> after REBOOT SYSTEM, Poco F1 instantly starts into FASTBOOT. I then press ON+VOLUP to enter RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
-> still, Poco F1 instantly starts into FASTBOOT again.
That is where I am stuck now.
Click to expand...
Click to collapse
install a global rom via twrp the latest one with 10.3.8.0 recovery flashable
go to twrp
flash the miui stable ..and then flash magisk 19.3 ..format data then reboot ... and then follow the steps i already given..
watch this for your reference https://www.google.com/url?sa=t&sou...BMAF6BAgFEAk&usg=AOvVaw09B7QXYvADkv7ZyNQtvH1K
Ok, will do that next day, thank you for your help and patience!!
In Recovery, I cannot "Swipe to unlock" anymore...
The touchscreen is not working. I had that issue several times in the past already. Rebooting to Recovery sometimes helps, but not now.
Andi900rr said:
In Recovery, I cannot "Swipe to unlock" anymore...
The touchscreen is not working. I had that issue several times in the past already. Rebooting to Recovery sometimes helps, but not now.
Click to expand...
Click to collapse
ok so its time to flash rom via fastboot ..just download the latest stable 10.3.8 fastboot rom after you install back up everthing first before flashing so you can restore if anything happens..back up only Boot , Recovery , System image , Vendor image , Efs and your good to go.. watch these and download are already included in this video https://www.google.com/url?sa=t&sou...BMAJ6BAgFEA4&usg=AOvVaw2naYU5q2jUaE5qUeskrBed[/url]
Before anything else ..use the twrp 3.2.3.0 recovery
Man, flash MIUI 10.3.8.0 on fastboot. ONLY MIUI. then boot... if it boot, tell us
Success flashing:
miui_POCOF1Global_V10.3.8.0.
recovery-20181211
Magisk-v19.3
rebootet to recovery, now into TWRP 3.2.3-0
I still wonder what was the problem and what was the solution...
Maybe formatting data was the solution?
From here, I backed up:
Boot
Recovery
System.image
Vendor.image
Efs
Backup created successfully; also copied to PC.
I wonder when installing LOS again from here on, if I should...
- update to TWRP 3.3.0-0
- update to Magisk-v19.4
or not.
bamz1117 said:
what rom your using before you installed los?
Clean flash would be needed ..you should wipe internal too to get it working , dont forget to remove all you password , fingerprint and face unlock.
Boot to recovery wipe system/dalvik/data/cache/internal before doing this you need to do a nandrioid back up..
do this:
download the lastest vendor:
beryllium-V10.3.8.0.PEJMIXM-9.0-vendor-firmware
next the LOS rom:
lineage-16.0-20191003-nightly-beryllium-signed
open_gapps-arm64-9.0-mini-20191003
and then
download the latest DFE version 19.3:
you can download it in telegram pocof1 group chat
and then wipe dalvik cache after that reboot system
first boot reboot to twrp recovery and the flash magisk v19.3 the reboot system....
i hope this method will help you..goodluck!!!
Click to expand...
Click to collapse
you can download it in telegram pocof1 group chat
Click to expand...
Click to collapse
please guide me to the group
****
I did the exact order bamz1117 wrote:
flashed:
-beryllium-V10.3.7.0.PEJMIXM
-lineage-16.0-20191003-nightly-beryllium-signed
-open_gapps-arm64-9.0-mini-20191003
-DFE 19.3
wipe dalvik
reboot system
and back into FASTBOOT...
Seems I am back where a was coming from? I am confused.
I have the suspicion that one of my zips is corrupted/defective/unproper version, but I have no idea which one.
When I flash
- beryllium-V10.3.6.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- Disable_Dm-Verity_ForceEncrypt_02.04.2019
wipe dalvik
reboot
- Magisk-v19.3
at least I see the LOS install logo working for quite a long time, but after that it reboots to TWRP recovery.
I noticed the following things:
concerning FW/vendor:
- beryllium-V10.3.6.0.PEJMIXM
I downloaded from https://mirror.akhilnarang.me/MIUI/beryllium/
is 451MB in size
- the newer ones:
fw_beryllium_miui_POCOF1Global_V10.2.3.0.PEJMIXM_a0319918c1_9.0
fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM_aa86bd1d08_9.0
are 91 MB each, I downloaded from https://xiaomifirmwareupdater.com/firmware/beryllium/
are those files fake?
Where to download V10.3.8.0 from a trustworthy source?
Would someone please explain me the proper order for a clean re-install (while rooted and TWRP recovery already installed) AND explain the reason behind that particular order?
My current understanding, which might be wrong:
1. Firmware/vendor first (obvioulsy this is giving hardware support to the operating system like with a PC), then
2. Lineage OS (this is the operating system) and
3. openGapps third (this modifies the operating system and includes google apps)
4. DFE (a kind of a script? which modifies the operating system by disabling verity/encryption/quota when setting the filename of the zip accordingly)
5. Magisk (offers services in order to hide rooting etc. to prevent apps with higher security e.g. online banking to detect security nonconformity and thus stop working)
Please correct me where and why I am wrong in that order - I want to understand it.
Thank you.
I dont know why but I lost TWRP meanwhile.
My Pocophone only starts into fastboot mode, I cannot invoke TWRP Recovery anymore.
I tried to flash the latest stock rom with "Tool all in one", which tells me bootloader is still unlocked.
But when I try to flash, a command window opens and closes immediately and nothing happens.
I try to run "Tool all in one" as admin, but it does not start.
I dont know what to do.
Was able to flash twrp 3.3.0-0 via fastboot... If I enter Recovery, it shows twrp 3.2.3-0 .... idk,wtf
I am able to restore Miui10 from backup! It runs!
But flashing vendor/LOS/DFE/Magisk is not working! WTF! No idea why.
Still have THE SAME fastboot-loop issue after flashing vendor/LOS/DFE/Magisk I STARTED WITH the first post.
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Recovery
The LineageOS 17.1 reovery is recommended
If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot
Current lineage 17.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/shamu
Google apps: Opengapps Use an ARM (not ARM64) package for Android 10
HEADS UP: When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
Changelog
Builddate: 2020.06.17
Changes:
[new] June security updates
[new] LineageOS clock
Builddate: 2020.05.29
Changes:
[new] May security updates
[fix] ULL audio fixes
[new] Add back serif fonts
[fix] Screen turning itself on when no lockscreen is set
[new] Etar calendar
Builddate: 2020.04.12
Changes:
[new] April security updates ROM & kernel
Builddate: 2020.04.08
Changes:
[new] Initial LineagOS 17.1 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, elektroschmock, npjohnson
Source Code: http://github.com/lineagos
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2020-04-08
Last Updated 2020-04-08
Reserved
First build isn't out yet, but I don't want the LineageOS 16.0 thread to be spammed with 17.1 questions
Will waiting for the build you might want to read the Changlog for the first LineageOS 17.1 release:
Changelog 24
Will there be a possibility to root?
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Thanks @Elektroschmock and @npjohnson for keeping the Nexus 6 alive in 2020. :good:
Eazy said:
Will there be a possibility to root?
Click to expand...
Click to collapse
Yes you can use your root solution of choice.
Only thing coming with the ROM is adb root.
dlbarron said:
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Click to expand...
Click to collapse
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Elektroschmock said:
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Click to expand...
Click to collapse
Actually, I've been running Lineage and CM before that since I brought the phone home. So there's no way I had the latest stock image installed ever.
Thanks, I'm all set
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
BootloopedMillennials said:
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
Click to expand...
Click to collapse
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
xrenoix said:
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
Click to expand...
Click to collapse
My system got corrupted by the previous process. So I had to do a fresh install.
BootloopedMillennials said:
My system got corrupted by the previous process. So I had to do a fresh install.
Click to expand...
Click to collapse
Hello you have test wipe system with twrp ? Or test repair ? And use pico gapps for trébuchet launcher not work with mirco gapps but pixel launcher work ? !
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Best would be to use built in update. Unless you want to do a clean install, there's no reason to do it.
the update inside of lineage is blocking updating to lineage 17.1 , i tried tha earlier and i jsut tried it again. then it gives the link to the wiki page.so thats not going to work.i will have to do the old method of flashing through twrp or hoping that there is a command line approach to flashing lineage through lineage recovery.
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Sorry, I didn't ignore your question, but I first had to check.
It's kind of hard to imagine how a blind person would do it if you can see.
If you have Lineage recovery installed and are able to boot into recovery do the following steps:
Press the Volume Down button 1 time
Press the power button two times
You are now in the adb apply update mode.
There you can install all the zip files you want. I guess you script does the rebooting to system itself.
If you need further help just ask.
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
s_dino said:
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
Click to expand...
Click to collapse
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Elektroschmock said:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Click to expand...
Click to collapse
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
s_dino said:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
Click to expand...
Click to collapse
You still have those options:
Go to "Factory Reset"
There you can choose which partition you want to wipe.
- Wipe data/factory reset
- Wipe cache
- Wipe system
I guess you want the "wipe system" option
Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.
runekock said:
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
Click to expand...
Click to collapse
It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.
Hi all,
I'm trying to install Havoc OS on my P20 lite (2018 model - ANE-LX1 8.0.0.0.135(C432)). My current version of EMUI is 8.0. So I need to install a A version of ARM and NOT AB.
The system image is
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have TWRP 3.4.0 installed and working. PS, I have also tried this via fastboot (fastboot flash system Havoc-OS-v3.1-20200202-ARM64A-GSI.img.xz) with the same results
Before flashing the ROM and my GAPPS file (open_gapps-arm64-10.0-nano-20200808.zip). Via TWRP I wipe Dalvik/Cache/System/Data
Then I installed the ROM via TWRP install and selected .img install, there are no errors and the screen output says it is installed correctly.
Then I flashed the GAPPS mentioned above. After that I wipe Dalvik/Cache again.
And reboot....nothing happens. The phone boots back up and goes straight to TWRP again. It's like the ROM is not being initialized at all.
Any help would be appreciated.
MayhemIam said:
Hi all,
I'm trying to install Havoc OS on my P20 lite (2018 model - ANE-LX1 8.0.0.0.135(C432)). My current version of EMUI is 8.0. So I need to install a A version of ARM and NOT AB.
The system image is
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have TWRP 3.4.0 installed and working. PS, I have also tried this via fastboot (fastboot flash system Havoc-OS-v3.1-20200202-ARM64A-GSI.img.xz) with the same results
Before flashing the ROM and my GAPPS file (open_gapps-arm64-10.0-nano-20200808.zip). Via TWRP I wipe Dalvik/Cache/System/Data
Then I installed the ROM via TWRP install and selected .img install, there are no errors and the screen output says it is installed correctly.
Then I flashed the GAPPS mentioned above. After that I wipe Dalvik/Cache again.
And reboot....nothing happens. The phone boots back up and goes straight to TWRP again. It's like the ROM is not being initialized at all.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi,
1. On Oreo use this TWRP
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
2. You have to extract system.img (cca 1,2GB) from .xz package (unpack it on PC), then transfer it to SD .
Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery (se the note bellow!)
P.S.: it's recommended install TWRP over eRecovery:
Copy downloaded TWRP file to the SD card, and also copy to card Stock ramdisk_recovery , download here: (for EMUI 8 only! )
https://mega.nz/#!04dG0JBb!hEgTk6DMKVDffttHiXGqa_YR_zG5UYwTMEi41KTkZi8
Since A8 and above you can not install TWRP over eRecovery from fastboot, follow instructions:
- install TWRP from fastboot , reboot to TWRP, select install image, and flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery. Reboot system. After the boot screen appears in the recovery with the inscription "Your device is booting now ..." press and hold Volume Up
for 3 sec, device will boot to TWRP.
-Alf- said:
Hi,
1. On Oreo use this TWRP
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
2. You have to extract system.img (cca 1,2GB) from .xz package (unpack it on PC), then transfer it to SD .
Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery (se the note bellow!)
P.S.: it's recommended install TWRP over eRecovery:
Copy downloaded TWRP file to the SD card, and also copy to card Stock ramdisk_recovery , download here: (for EMUI 8 only! )
https://mega.nz/#!04dG0JBb!hEgTk6DMKVDffttHiXGqa_YR_zG5UYwTMEi41KTkZi8
Since A8 and above you can not install TWRP over eRecovery from fastboot, follow instructions:
- install TWRP from fastboot , reboot to TWRP, select install image, and flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery. Reboot system. After the boot screen appears in the recovery with the inscription "Your device is booting now ..." press and hold Volume Up
for 3 sec, device will boot to TWRP.
Click to expand...
Click to collapse
Hi Alf my man
So I am having a bit of trouble with your instructions. I am very sure it is my own fault! I just want to clarify the steps please. I have downloaded the 2 provided files you gave in the link.
1
Install TWRP via
"fastboot flash recovery_ramdisk TWRP-oreo-smart.img"
2
Boot into newly flashed TWRP and flash the 2 files again as specified
"....flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery...."
3
Reboot after step 2 and go into TWRP again and perform the system.img install as per instructions via TWRP
"Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery"
I take it that I need to install my GAPPS package as well in this stage?
4
After factory reset from stock recovery the OS should boot and initiate...
Thanks again man for your help!
MayhemIam said:
Hi Alf my man
So I am having a bit of trouble with your instructions. I am very sure it is my own fault! I just want to clarify the steps please. I have downloaded the 2 provided files you gave in the link.
1
Install TWRP via
"fastboot flash recovery_ramdisk TWRP-oreo-smart.img"
2
Boot into newly flashed TWRP and flash the 2 files again as specified
"....flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery...."
3
Reboot after step 2 and go into TWRP again and perform the system.img install as per instructions via TWRP
"Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery"
I take it that I need to install my GAPPS package as well in this stage?
4
After factory reset from stock recovery the OS should boot and initiate...
Thanks again man for your help!
Click to expand...
Click to collapse
I have done as instructed yet there is am issue at the last step. I can boot into stock recovery but when I try and do a Factory Reset via the menu the reset only goes to 9% and gives a large orange/red exclamation mark.....so it did not finish. When I try and reboot and load the OS it goes into a boot loop and that is it.
MayhemIam said:
I have done as instructed yet there is am issue at the last step. I can boot into stock recovery but when I try and do a Factory Reset via the menu the reset only goes to 9% and gives a large orange/red exclamation mark.....so it did not finish. When I try and reboot and load the OS it goes into a boot loop and that is it.
Click to expand...
Click to collapse
Okay, reboot system. You can perform factory reset later (if needed).
---------- Post added at 19:17 ---------- Previous post was at 18:56 ----------
Please provide me the link where you downloaded Havoc OS
-Alf- said:
Okay, reboot system. You can perform factory reset later (if needed).
---------- Post added at 19:17 ---------- Previous post was at 18:56 ----------
Please provide me the link where you downloaded Havoc OS
Click to expand...
Click to collapse
No it's stuck on a bootloop Alf :crying:
MayhemIam said:
No it's stuck on a bootloop Alf :crying:
Click to expand...
Click to collapse
Don't panic! IMO it's time to clean your phone , download Service ROM
https://androidhost.ru/5NX
Unpack .zip package, find dload file and copy it to the SD card (without unpacking it!). Then turn off the phone and flash ROM using three button combo.
(instruction can be found in file ReleaseDoc).
Important: the process will erase all your data and will lock again the bootloader!
I will now try to install Havoc 3.1A and I will let you know, okay?
-Alf- said:
Don't panic! IMO it's time to clean your phone , download Service ROM
https://androidhost.ru/5NX
Unpack .zip package, find dload file and copy it to the SD card (without unpacking it!). Then turn off the phone and flash ROM using three button combo.
(instruction can be found in file ReleaseDoc).
Important: the process will erase all your data and will lock again the bootloader!
I will now try to install Havoc 3.1A and I will let you know, okay?
Click to expand...
Click to collapse
Well I can still dload back to my old EMUI 8.0 OS! I just did it again and it works. I can get back into my OS no probs. I have done this about 6 times today, lol. I really do not want to lock my bootloader again as it took me a long time to get it unlocked!
Thnx for the reply!
MayhemIam said:
Well I can still dload back to my old EMUI 8.0 OS! I just did it again and it works. I can get back into my OS no probs. I have done this about 6 times today, lol. I really do not want to lock my bootloader again as it took me a long time to get it unlocked!
Thnx for the reply!
Click to expand...
Click to collapse
Also just for me to understand. I have EMUI 8.0 running then I can't upgrade to a Android 9 Custom ROM?
MayhemIam said:
Also just for me to understand. I have EMUI 8.0 running then I can't upgrade to a Android 9 Custom ROM?
Click to expand...
Click to collapse
I'm not sure I fully understand your question, you cannot upgrade to A9 , you can flash Custom ROM based on A9 (which requires A8 OS).
Btw, I tried flash Havoc 3.1, 3.0, tried several TWRP, no luck. Flashed system.img from fastboot, nothing. It seems A-only version doesn't work on ANE. I have no idea what the problem is...
(hehe, R.I.P. English )
-Alf- said:
I'm not sure I fully understand your question, you cannot upgrade to A9 , you can flash Custom ROM based on A9 (which requires A8 OS).
Btw, I tried flash Havoc 3.1, 3.0, tried several TWRP, no luck. Flashed system.img from fastboot, nothing. It seems A-only version doesn't work on ANE. I have no idea what the problem is...
(hehe, R.I.P. English )
Click to expand...
Click to collapse
OK I can't upgrade to EMUI 9 but I can upgrade to a custom ROM which has Android 9 (through AB partition)?
"...you can flash Custom ROM based on A9 (which requires A8 OS)." Which means I can upgrade to any custom ROM which has Android 9 / 10?
What is the difference then between the following?
ARM64A
ARM64AB
-Alf- said:
Okay, reboot system. You can perform factory reset later (if needed).
---------- Post added at 19:17 ---------- Previous post was at 18:56 ----------
Please provide me the link where you downloaded Havoc OS
Click to expand...
Click to collapse
Oh snap man, I only saw the last part of your post now.
I tried the following ROMS.
Most of them was downloaded from SourceForge man.
Havoc-OS-v3.0-20191225-ARM64A-Unofficial.img.xz
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have tried others as well but they were ARM64AB....
MayhemIam said:
OK I can't upgrade to EMUI 9 but I can upgrade to a custom ROM which has Android 9 (through AB partition)?
"...you can flash Custom ROM based on A9 (which requires A8 OS)." Which means I can upgrade to any custom ROM which has Android 9 / 10?
Click to expand...
Click to collapse
For example:
Pixel Experience, ROM for the Huawei P20 Lite
Contributors
DarkJoker360
Source Code: https://github.com/DarkJoker360
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8 unlocked bootloader & twrp
MayhemIam said:
OK I can't upgrade to EMUI 9 but I can upgrade to a custom ROM which has Android 9 (through AB partition)?
"...you can flash Custom ROM based on A9 (which requires A8 OS)." Which means I can upgrade to any custom ROM which has Android 9 / 10?
What is the difference then between the following?
ARM64A
ARM64AB
Click to expand...
Click to collapse
What is the difference then between the following?
ARM64A
ARM64AB
OK so the answer is
Use ARM64xA - when your phone is using Android 8.0 (EMUI 8.0)
Use ARM64xAB - when your phone is using Android 9 (EMUI 9.1)
-Alf- said:
For example:
Pixel Experience, ROM for the Huawei P20 Lite
Contributors
DarkJoker360
Source Code: https://github.com/DarkJoker360
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8 unlocked bootloader & twrp
Click to expand...
Click to collapse
Hi Alf,
I have abandoned ship to get HavocOS on my device
But I'm trying now the following AOSP Android 10 Q
https://www.getdroidtips.com/android-10-huawei-p20-lite/
I'm going to try and use this TWRP (twrp-3.4.0-0-anne.img)
Will let you know how it goes!
MayhemIam said:
Hi Alf,
I have abandoned ship to get HavocOS on my device
But I'm trying now the following AOSP Android 10 Q
https://www.getdroidtips.com/android-10-huawei-p20-lite/
I'm going to try and use this TWRP (twrp-3.4.0-0-anne.img)
Will let you know how it goes!
Click to expand...
Click to collapse
Getdroidtips? Really reliable source
I finally installed Havoc 3.8ab (latest version), I'm disappointed . No Music player, no Sound recorder (=no call recording) , no email client, Calendar etc. etc....
I think you should upgrade to EMUI 9.1 and try AB versions , hm?
-Alf- said:
Getdroidtips? Really reliable source
I finally installed Havoc 3.8ab (latest version), I'm disappointed . No Music player, no Sound recorder (=no call recording) , no email client, Calendar etc. etc....
I think you should upgrade to EMUI 9.1 and try AB versions , hm?
Click to expand...
Click to collapse
I would have really like to test an earlier version then which did not have all those missing features! It seemed to me that customization was very good on the ROM....
facepalm on Get Droid Tips....because the only tip I got from them is more than 12 hrs of trying to implement their crappy advice!
Ok I will upgrade to EMUI 9 then Alf.
Thanks for all the advice man and flashing along side me
Try Havoc 2.9 for Oreo , the Rom is just perfect . (own experience, tested on 8.0.0.126 )
INSTALL ON CLEAN OS (if your current OS is Custom ROM, flash stock ROM).
Download and unpack on your PC Havoc 2.9 arm64a:
https://sourceforge.net/projects/ha...90914-phhgsi_arm64_a-Official.img.xz/download
Flash extracted Havoc.img from fastboot using command
fastboot flash system (file name).img
Before booting up the ROM, you will need to perform a factory reset in stock recovery!!!
Reboot system.
In the Phh-Treble Settings-Huawei features, select fast charge 4000mA and Enable blurry UI workaround
If you want to install GAPPs or Magic (Magic v20.3 works without problems) , use TWRP by "ascuccio" (own experience), download link:
https://mega.nz/#!EsdTgYqZ!2QX9wgAhA653Dp2MkDTLPHa3tmFdNqmC5CDDHB-7f5Y
Screenshots:
https://mega.nz/#!1tlnlSyS!3SdAkZwf9miFVMkEXiq5Ypy3PcTOhuuohywk1ta-eXI
MayhemIam said:
Hi all,
I'm trying to install Havoc OS on my P20 lite (2018 model - ANE-LX1 8.0.0.0.135(C432)). My current version of EMUI is 8.0. So I need to install a A version of ARM and NOT AB.
The system image is
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have TWRP 3.4.0 installed and working. PS, I have also tried this via fastboot (fastboot flash system Havoc-OS-v3.1-20200202-ARM64A-GSI.img.xz) with the same results
Before flashing the ROM and my GAPPS file (open_gapps-arm64-10.0-nano-20200808.zip). Via TWRP I wipe Dalvik/Cache/System/Data
Then I installed the ROM via TWRP install and selected .img install, there are no errors and the screen output says it is installed correctly.
Then I flashed the GAPPS mentioned above. After that I wipe Dalvik/Cache again.
And reboot....nothing happens. The phone boots back up and goes straight to TWRP again. It's like the ROM is not being initialized at all.
Any help would be appreciated.
Click to expand...
Click to collapse
You have tried to decrypt the data?
https://forum.xda-developers.com/honor-7x/development/mod-decrypt-data-emui-8-t3765403
Dego02 said:
You have tried to decrypt the data
Click to expand...
Click to collapse
No comment...
I tried to flash Lineage OS on my Galaxy J5 (2017) /sm-j530f/.
Unfortunately im getting the following Error:
"E2001: Failed to update vendor image."
Thank you for the help!
GonicTEAM said:
OrangeFox R11.0 (it's MANDATORY) - Download from here
Repartition script - Download from here
GApps: ARM64 > 10 > Pico - Download from here
Magisk 21.4 or newer for root - Download from here
Installation:
Enter to recovery mode and make a backup of your EFS & Modem (recommend).
Go to the Files tab and flash "LOS17.1-Repartitioner-exynos7870.zip". The recovery will auto-reboot.
Now, go to the Trash Bin and then go to the "Format data" tab, type "yes" and the tick to format data.
Go to the Wipe tab, select SYSTEM, CACHE, DALVIK, VENDOR, DATA and INTERNAL STORAGE, then swipe the bar.
Install the lineage-17.1-xx-UNOFFICIAL-j7xelte.zip
Install the GApps zip
Install Magisk (optional)
Reboot and wait. Without GApps, it boot in 15s. With Pico GApps, it boot on 1min 5s.
Done!
Click to expand...
Click to collapse
I got Moto E5 Plus, ineed stepby step details on how to update vendor image, im new to this. please help