Related
I will try to describe problem as much as I can:
1.Unlocked bootloader(unofficial way).
2.Installed TWRP 3.0.M4-0(success).
3.Installed(in such order as stated by some guide) : CM14.1 Firmware(Kate) - 26.11.2016 >>> CM14.1-20161222 Nightly Kenzo >>> Opengapps arm64 7.1 nano with TWRP(success).
4.Reboot, CM 14.1 launches correctly, although it has saved settings and apps from MIUI, making it real mess. Now the problem starts. I assumed by doing factory reset I'll get clean 14.1 - wrong. After that turning on my phone causes it to launch TWRP instead of system.
(Failed)Attempts to fix:
1.Install CM14.1 again.
2.Wipe + install CM14.1 again.
3.Can't get into EDL mode(as stated here http://en.miui.com/thread-290959-1-1.html)
Additional info:
1.Fastboot mode launches, but 'adb devices' doesn't find anything(it was before). Device manager sees phone as well as MiFlash. Not succesful trying to update drivers(system found them up-to-date).
2.I have Kate edition, started installing after reading this http://forum.xda-developers.com/redmi-note-3/how-to/index-custom-roms-t3396628 , last posts states, that sometimes it's necessary to flash non-hlos.bin file to system(not sure if even necessary in my case, as CM14.1 launched before factory cleaning).
3.Only similar thing I found is : http://forums.androidcentral.com/sa...p-after-factory-reset-cyanogenmod-12-1-a.html , but about different device and CM version.
I'll appreciate any suggestions on how to fix it(either getting into CM14.1 or back to MIUI, preferably the first).
@edit - Solved myself. For anyone encountering such problem, I could install succesfully MIUI back, when I launched my windows in Disable Drivers Signature Mode.
what exactly have you done at the point "factory cleaning" ? do you mean anything in running android or in TWRP?
h0LLe said:
what exactly have you done at the point "factory cleaning" ? do you mean anything in running android or in TWRP?
Click to expand...
Click to collapse
Factory clean from android settings after running CM14.1 succesfully for the first time. No idea why it caused a problem, but as I wrote in edit, it is solved.
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device (and all of your apps and settings are the same)
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again ( to be sure ) - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
10. make TWRP backup when needed
11 IF YOU WANT TO UPDATE TO B02 : use this methode https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
EDIT : when you want to get rid of the bootscreen which states that you have an unlocked bootloader, follow this procedure (very easy )
https://forum.xda-developers.com/showpost.php?p=71444728&postcount=496
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
raystef66 said:
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
Click to expand...
Click to collapse
I'm on stock B29, rooted, unlocked bootloader.
Been avoiding updates, but this looks promising to keep root.
Think it will work for me? Forgot to mention I have 3.0.4 twrp
HTC55555 said:
I'm on stock B29, rooted, unlocked bootloader.
Been avoiding updates, but this looks promising to keep root.
Think it will work for me?
Click to expand...
Click to collapse
Don't know exactly.
For G users the latest update before 7.0 was the B10. Therefore B10 is the necessary flash before G users can flash N
As long as you keep TWRP running ( as far as i know do not wipe system etc...therefore i mentioned earlier to not wipe anything) and your latest backup, you can always restore it.
Hmm... I did this a week ago and forgot to flash SuperSU. Messed up big time... Axon7tool gives the what() error, but people say that even if it successfully flashes the recovery, the stock recovery remains there.
So I need the inverse process... any idea how?
Choose an username... said:
Hmm... I did this a week ago and forgot to flash SuperSU. Messed up big time... Axon7tool gives the what() error, but people say that even if it successfully flashes the recovery, the stock recovery remains there.
So I need the inverse process... any idea how?
Click to expand...
Click to collapse
Perhaps this will help : https://forum.xda-developers.com/showpost.php?p=71444519&postcount=494
unplug usb when you give command to flash twrp recovery, otherwise it always reflashes stock recovery....
Hope that helps
Thanks for the reply! I'll have to figure out how to make axon7tool work now. Much appreciated
Dear raystef66!
I'm on Resurrection Remix now-2017G (it is 7.1.1 based).I would like to have a stock 7.1.1.Can i just do the steps in your post 1,without flash b10, just flash
7.1.1 stock bootstack, system and Super SU?Would it working solution, to go from Resurrection Remix to stock 7.1.1 on 2017g?And will be twrp still prsent after those steps?
Thanks in advance!
ValVK said:
Dear raystef66!
I'm on Resurrection Remix now-2017G (it is 7.1.1 based).I would like to have a stock 7.1.1.Can i just do the steps in your post 1,without flash b10, just flash
7.1.1 stock bootstack, system and Super SU?Would it working solution, to go from Resurrection Remix to stock 7.1.1 on 2017g?And will be twrp still prsent after those steps?
Thanks in advance!
Click to expand...
Click to collapse
IMO you have to flash b10 too. Would do no harm though as long as you don't fully wipe system to keep twrp. As long as you keep a backup of twrp you can always go back. In worst case you have to flash twrp again in edl axon7tool.
@ValVK I flashed B03, then B08, then B10, and THEN B01, like any normal update. That because I don't know if B10 is only an incremental update
But after you flash the stock system, remember to root! You'll lose TWRP otherwise
Thanks all for responces! If i will go that way-flash in Twrp b08, then b10 and then Nuga, what should i wipe first in Twrp-all inclusive System, or just Factory reset? And if i will go that way, should my Twrp still intakt? (I would like avoid to Flash Twrp again, seems bit risky for me).
I had the official bootloader unlock but it broke the com.android.phone process on 7.1.1.
They are working on getting it fixed and once fixed will make the root publicly avialble.
The official root works on b10 marshmallow and is very easy to install.
@ValVK o sorry, I only flashed B03 :silly:
You should flash B03 THEN update via the native sdcard update on mifavor
raystef66 said:
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device (and all of your apps and settings are the same)
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again ( to be sure ) - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
10. make TWRP backup when needed
EDIT : when you want to get rid of the bootscreen which states that you have an unlocked bootloader, follow this procedure (very easy )
https://forum.xda-developers.com/showpost.php?p=71444728&postcount=496
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
Click to expand...
Click to collapse
Hi, I am on the stock rom 7.0 nougat for the A2017G.
Can I just flash the leaked rom 7.1.1 for a2017g model??, I have no root, total stock.
Oliver Aa said:
Hi, I am on the stock rom 7.0 nougat for the A2017G.
Can I just flash the leaked rom 7.1.1 for a2017g model??, I have no root, total stock.
Click to expand...
Click to collapse
I suggest you wait for the 7.1.1 OTA update when you're not rooted etc.
I flashed through twrp the package made by tron1 for android 7.1.1 , the bootstack and supersu to make sure i have root install at the first boot but for some reason supersu framework gets deleted. I tried flashing supersu package multiple times and it gets deleted after boot up . How could i fix this ?
S0wL said:
I flashed through twrp the package made by tron1 for android 7.1.1 , the bootstack and supersu to make sure i have root install at the first boot but for some reason supersu framework gets deleted. I tried flashing supersu package multiple times and it gets deleted after boot up . How could i fix this ?
Click to expand...
Click to collapse
Did you follow my steps ? From which version did you come ? Were you already rooted....
Perhaps flash SU 2.79 (!) in edl mode and when it is resetting for a reboot, unplug your phone before it can reboot. You get a black screen. Just press Vol+/Power and when you see ZTE logo you release. Normaly you should/can enter TWRP.
But normaly my guide should work if you were rooted, BL unlocked and on stock ROM (B08 or earlier). I do not know which steps you already performed so it's just gessing.
What you guys think??
I want to know if I update my phone to this version, can I continue using xposed
Hello, can someone create TWRP files from the new B02 image?
Gesendet von meinem ZTE A2017G mit Tapatalk
@raystef66
I have a question:
Can step 8) be skipped? (flash 7.0=A2017GV1.1.0B01 bootstack and system, flash SU2.79).
Since in step 9) we will flash immediately 7.1.1B01=A2017GV1.2.0B01 bootstack and system, and flash SU2.79.
I guess step 8) is harmless, but not necessary. Is it true? Or are there other reasons for this?
Also maybe you could at end of this guide add a link to your another guide
https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
which continues the upgrade to 7.1.1B02=A2017GV1.2.0B02 keeping TWRP, unlock, fastboot and root?
Thank you.
dnlilas said:
@raystef66
I have a question:
Can step 8) be skipped? (flash 7.0=A2017GV1.1.0B01 bootstack and system, flash SU2.79).
Since in step 9) we will flash immediately 7.1.1B01=A2017GV1.2.0B01 bootstack and system, and flash SU2.79.
I guess step 8) is harmless, but not necessary. Is it true? Or are there other reasons for this?
Also maybe you could at end of this guide add a link to your another guide
https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
which continues the upgrade to 7.1.1B02=A2017GV1.2.0B02 keeping TWRP, unlock, fastboot and root?
Thank you.
Click to expand...
Click to collapse
IMO step 8 can not be skipped due to the fact you have to have 7.0 first. Could be wrong, but then again, it only last for a minute or so
I will ad the link to upgrade B01 to B02.
Thnx !
ps : did you get B02 with my method ? Pls post on thread if succeeded - thnx !
Hi. When I first installed LOS 18.1 I had problems with fingerprint not working, so I have written a detailed guide how to fix it. Just a disclaimer - I am not responsible if you somehow break your phone while following this guide.
I am also a noob on custom ROMs, but I have done the exact same steps, and my phone appears to be working fine, so you should be all right too. After all, these steps are almost identical to all custom ROMs installation instructions, the difference is that this time we use OrangeFox recovery instead of TWRP, because LOS 18.1 seems to work better with it.
NOTE:
When I used this method myself, I went back to latest MIUI ROM. I don't know if it is necessary, but I think everything should work fine without reverting to MIUI. If you would like to try fixing it without installing MIUI ROM, then go to the first reply below for a simplified guide. Nevertheless, I recommend reading the full guide anyway, just to get a better understanding of what steps you will have to do.
Also, some steps can be skipped because probably many of you have already done them when you were installing LOS or other custom ROMs. I have only tested this fix on LOS 18.1 but it might work on other custom ROMs too, I think.
I've written this guide while following OrangeFox recovery guides, and getting help from Redmi Note 4 users on Telegram groups.
FULL GUIDE (INCLUDES GOING BACK TO MIUI):
1. Install ADB + Fastboot in your PC (I assume you use Windows 10).
Download these files:
SDK platform tools: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Google USB Driver: https://dl.google.com/android/repository/usb_driver_r13-windows.zip
I am not sure if Google USB Driver is necessary, but install it anyway because I had it installed too.
For installation instructions, use the attached "ADB Fastboot installation.txt" file.
You can check this video for visual guide as well:
At this point I recommend backing up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
2. You will need to go back to latest MIUI ROM. Use this page for instructions: https://c.mi.com/oc/miuidownload/detail?guide=2
If your Mido is global, then download "Redmi Note 4X Latest Global Stable Version Fastboot File Download" from (STEP 2).
VERY IMPORTANT! When flashing MIUI, make sure you select "Clean all" option. DO NOT select "Clean all and lock" (STEP 5).
3. After successful flashing, boot into MIUI. You may encounter this error when booting up MIUI 11: "Find device storage corrupted. Your device is unsafe now." This error also means that Wi-Fi and Bluetooth will not work. Don't worry, this will be fixed.
4. Next, download these files and put them in your SD Card (for example, Download folder).
(note: some zip file names written in this step will be outdated because Mido is still maintained - always make sure to check, download and use latest updated files).
OrangeFox recovery (R11.0) for mido:
https://dl.orangefox.download/5f14b74f26d98d90b476a532
Latest mido firmware:
https://xiaomifirmwareupdater.com/d...4XGlobal_V11.0.2.0.NCFMIXM_83170d3e3a_7.0.zip
LineageOS 17.1 with 3.18 kernel (you will need to install it first):
https://github.com/zeelog/OTA/releases/download/27.0/lineage-17.1-20201214-UNOFFICIAL-3.18-mido.zip
LineageOS 18.1:
https://github.com/zeelog/OTA/releases/download/41.0/lineage-18.1-20210417-UNOFFICIAL-mido.zip
GApps - "MindTheGapps arm64" was recommended by LOS Team for LOS 18.1 when I wrote this guide (before installing ask the ROM maintainer or users if this is still the recommended version of GApps):
MindTheGapps-11.0.0-arm64-20210412_124247.zip | by Alessandro Astone for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Also don't forget to download "persist.img" file attached below.
5. Now, make sure that your phone is charged and has more than 80% battery (just to be safe).
Also note that after the following step, you won't be able to boot to MIUI anymore, so make sure you have made a backup of your files.
Install OrangeFox recovery using this guide:
Installing OrangeFox Recovery
wiki.orangefox.tech
6. Now, follow the instructions written in the attached "Fingerprint fix and MIUI errors" text file. (note: some zip file names in step 3 of this text file will be outdated because Mido is still maintained - always make sure to check, download and use latest updated files)
7. Finally, follow the instructions written in the attached "Readme - LOS 17.1 and 18.1 installation" text file, you should start from step 4. (note: some zip file names in step 1 of this text file will be outdated because Mido is still maintained - always make sure to check, download and use latest updated files)
Good luck!
One user reported that he successfully fixed the fingerprint issue on LOS 18.1 using this guide without going back to MIUI.
When I was fixing this fingerprint problem myself, I went back to the latest MIUI ROM. I did not test this method to see if it works without installing MIUI, but it looks like it should work just fine. In case you want to try fixing it without going back to MIUI, do this:
SIMPLIFIED GUIDE (WITHOUT GOING BACK TO MIUI):
* Back up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
* Make sure that you have OrangeFox recovery installed, if not - install it.
* Download all the files mentioned in the step 4 of my initial post of this thread and put them on your SD Card. (check if there are any updated files before downloading, like newer ROM update, etc.)
* Download attached "Fingerprint fix and MIUI errors" text file, "persist.img" file and "Readme - LOS 17.1 and 18.1 installation" text file.
* Follow the "Fingerprint fix and MIUI errors" text file guide starting from step 8.
* Follow the "Readme - LOS 17.1 and 18.1 installation" text file guide, starting from step 4. I advise not to skip steps 17-18, although I'm not sure if installing latest Mido firmware is necessary at this point. But I think you should install it, just in case.
Good luck!
Cheers for all your efforts, @Rigadelt !
I'm trying your guide, as I can't get my fingerprint working in LOS18.1, although it works just fine in LOS17.1 ...
Can I ask you:
1) what for are your steps 10+11 & 23+24 in your "Readme - LOS 17.1 and 18.1 installation.txt" ?
2) at what point/step have you encrypted your phone?
Cheers! raimerik
Hi, @raimerik
1) I was advised by the Mido Telegram group users that Rebooting to recovery after ROM or GApps installation ensures that there is a lesser chance of errors during the finalizing of the ROM installation. I'm not sure if that is true, but it shouldn't hurt doing it this way either.
2) I did not encrypt my Mido, so I can't answer this question. You can find info in this post: https://forum.xda-developers.com/t/...-mido-vanilla-by-zeelog.4186179/post-83861307
What I would try to do:
* I would follow the "Readme - LOS 17.1 and 18.1 installation.txt" guide and install LOS 18.1 ROM without GApps (step 19 is the last step).
* After 18.1 ROM flashing, I would tap on "Wipe Caches" and then reboot to recovery.
* After the phone successfully reboots to OrangeFox recovery, I would then follow the Encryption guide written in the post I linked.
* After Encryption -> Dirty flash of LOS 18.1 ROM -> GApps installation process, I would reboot to recovery once again, and then try to boot the phone and see if everything works.
If I'm not mistaken, @manizuwo has fixed the fingerprint problem and encrypted his Mido using this guide, so you could ask him for advice.
Good luck! I also encourage you to share the results and info with other users here or in the main LineageOS 18.1 thread.
Rigadelt said:
* After 18.1 ROM flashing, I would tap on "Wipe Caches" and then reboot to recovery.
* After the phone successfully reboots to OrangeFox recovery, I would then follow the Encryption guide written in the post I linked.
* After Encryption -> Dirty flash of LOS 18.1 ROM -> GApps installation process, I would reboot to recovery once again, and then try to boot the phone and see if everything works.
Click to expand...
Click to collapse
Hi @Rigadelt - two minds thinking/tinkering alike!
I had updated and booted the 18.1, encrypted, went to recovery, dirty flashed the 18.1 and the gApps, wiped caches and rebooted.
Then I set up security pattern and fingerprint, which still does ONLY work if you activate SECURESTART which is an annoying bug, which the 18.1-thread-manager does not seem to understand...
(In Zeelog's 17.1 with 4.9-Kernel the fingerprint worked WITHOUT SecureStart...)
Hi all,
please find attached the Havoc OS 3.8 custom ROM, Olivelite version, and Magisk 20.4 which you will need for installation also.
I am neither the creator of this ROM or anyhow involved with the team, nor do I take any responsibility for everything which might go wrong during installation.
How I got it to work:
1. Unlock your boot loader (you will find appropriate instructions here in the forum and elsewhere on the web, also on YouTube).
2. Ensure that you have the XiaoMi Flash tool and the latest stock rom available, to be able to recover you phone when you encounter issues.
Both can be found on the Xiaomi website.
3. Get the "minimal ADB and Fastboot" tools. You will find in the web.
4. Get TWRP (you will find out what this is and why you need it here in the forum). Take care that it is a version for your phone model, else worst case it will not work.
5. Put the attached files to an external SD card in your phone.
6. install TWRP. Boot into "Fastboot" mode and install TWRP with command "fastboot flash recovery twrp.img".
7. Boot into recovery mode - if yoiu did everything right, should be TWRP now
7a. Wipe - Format data - confirm with "Yes", then go back to main menu
7b. Wipe - advanced wipe - select all except the last 2 (expecially NOT "external SD" if you put your files on there),
go back to main menu
7c. Install - select location where you've put the "havoc 3.8 update.zip" and select the file, afterwards wipe Cache / Dalvik (TWRP will give you this option after install), DO NOT REBOOT
7d. Install - select location where you've put the "magisk v20.4.zip" and select the file, afterwards wipe Cache / Dalvik and then reboot to system.
Now, hopefully, congratulations and enjoy
If something happens and it will not work at all, search the web first for solutions and, if still does not work and you do not get along with it, do not worry. You can always go back to the Xiaomi original ROM with the XiaoMi Flash Tool. Phone must be in "Fastboot" mode for this. In the flash tool, select your ROM location (ideally in the root of your drive as this tool cannot interpret spaces in paths), then confirm and ensure that you have ticked "Clean all" in the bottom, NOT "clean all and lock" - else you will have to do the unlock procedure again.
Sometimes, you need the "permissiver v5.zip" which you will find on the web. In case the above does not work, you can try to install the Permissiver. I never needed it, and I'm using 2 Redmi Olivelite.
I just tried this and had a success message from TWRP about the Havoc 3.8 flash but the Majisk file had an error from within TWRP first time & then it installed after reboot. But I still go straight into TWRP after rebooting.
Right now I have TWRP on the device & a micro SD card to get files onto the device but no OS on it & no backup as one way or another I want a ROOTed OS & it was the Chinese version when I got the phone so useless to me anyway.
What's the best approach from here to get this thing running again?
Thanks!!! Thanks!!! Thanks!!! after trying to get a GSI rom run on my daugthers olivelite i finally got a new rom working. I don't know why last guides didn'twork for me actually a recently requested a boot.img patch but i managed to patch it myself after dealing with python. Now will try to update it to 3.12 i suppouse it iwll have many improvements. But this worked right out of the box for me. Just followed each step and good to go.
For anyone interested. its de 2Gb/32Gb Global Version. with 12.0.3 latest MIUI updated applied trough fastboot. I used OFOX to test it and it worked fine by now.
If you have guide to update HAVOC please point me in the right direction.
Thanks again
I got off .Havoc precisely because it did not have voLTE support & BT HS 's didn't work. Has anyone had any luck on these 2
I absolutely thank you for this rom, I can now miraculously play Asphalt 9 on high settings at 30ish fps while on miui it struggled on lowest settings, the UI is flawless but I only have one problem I can't send nor receive SMS and the phone sometimes reboots randomly but that cannot make me go back to miui since it's too heavy for my phone.
IS THERE any fix for not being able to receive or send SMS
I have a black screen [FIxed by installing OrangeFox recovery]
here it is for g530fz devices :
used : twrp 1.1.1-1
lk2nd (postmarketos): 0.12.0 msm916
a/ pmos "works" (not so well) on that device
b/ unfortunately, few "bugs" "maybe related" to hardware persists, mainly in the reactivity on touchscreen when locked on inactive since a while.
c/ perf is highly to low (paradox for pmos ;-) ) to use it as a "common daily smartphone", mean : if you want to escape gafamnt, mount your server on a phone, or specific usages : it would be perfect. But dont expect it to run netflix everyday in firefox or falkon, it might freeze for "not only" a while.
d/ my documentation/software related to it :
samsung_g520fz
Partagé avec kDrive, le Cloud Éthique.
kdrive.infomaniak.com
[lien noveart/tabdigital]
[lien noveart/free]
[lien noveart/androidfilehost]
see for each link, normally a .img file. Unforunately, only 1 was able to host a gigabyte-sized, .img file.
Please note, without the following bug being not solved, that device could NOT get postmarketos installed through twrp with zip file :
Fail to sideload recovery.zip (#1962) · Issues · postmarketOS / pmbootstrap · GitLab
Phone: motorola-harpia (Moto G4 Play XT1607) Recovery: tool: TWRP version: 3.2.1-0 Zip built...
gitlab.com
In addition : Don't know what is the exact issue, but I found a case, where it was fixed: https://gitlab.com/postmarketOS/pmbootstrap/-/issues/1962 , sadly they didn't document how to solve it properly.
e/ im going on something else now.. if you want ungoogled/ungafamnted android, take lineageos14.1 (gprimeltexx), the fastest/best choice for that device, for common usage
==roll back to androstock/lineageos?==
for G530FZ :
used : twrp 1.1.1-1
lk2nd (postmarketos): 0.12.0 msm916
android stock :
**download mode :
simply use odin with a tar ROM
lineageos :
**download mode :
use heimdall or odin to flash the twrp
used : twrp 1.1.1-1
**twrp/recovery mode :
use twrp to flash the lineageos zip file (install button)
I really advise you to use lineageos14.1 (andro7) for better compatibility/performance
postmarketos :
you have to use heimdall with lk2nd in download mode
**download mode :
use heimdall to flash lk2nd, then reboot in lk2nd (power+volDown at bootup)
**lk2nd screen :
fastboot erase system && fastboot erase userdata && fastboot flash userdata /home/koala/.local/var/pmbootstrap/chroot_native/home/pmos/rootfs/samsung-gprimeltexx.img &&fastboot reboot
[unfortunately because of a bug, twrp can't flash .zip files of postmarketos, on that device - .img, heavier, are the only way I had]
well tested :
lineage 14.1, but you *might* have to odin it, regarding this :
Hi guys
regarding the G530fz to solve the problem I had to be oriented to Lineage 14.
Why the cell data was not detected? I don't know, but I discovered a way to fix it :
I was used before to install Lineage by just injecting the image file into the phone, then format the /data partition by simple wipe.
And for others phone, it was working.
Looks like on samsung models, it's requiring steps differently :
1/ use odin to reinstall stock firmware regarding all four files : BL, AP, CP, CSC. In the downloaded archive of the stock firmware, all files matchs with those option with odin. It's necessary to add these four files.
Flash it
2/ The phone will start. After finished, you can restart it, but in download mode.
3/ then use again odin, but flash it with only three files, excluding AP. Replace BL by the twrp bootloader.
4/ If at reboot, it's stuck on a recovery start, even without pushing the vol buttons, reflash it again with only BL.
5/ proceed normally to install lineage : download correct image plus arm (it's arm32 if Im right) pico or nano opengapps, copy them to the phone by usb, flash it then wipe /data.
6/ it should work.
If not, I remember I had to firstly flash by stock factory with all four files of stock archive, then only three including twrp instead of factory BL, then only BL if it's booting in loop into recovery instead normal mode.
Normally, it should, with lienage, detect sim cards.
If you just flash it with twrp by BL/odin, twrp will be installed, lineage can be installed too, but GSM/3G/LTE modules might never work (in my case, it happened like it)