Related
Bevor you do something with your Device do a Backup of all your Data (Contacts, Pic´s ect.) outside of your Device (in a Cloud or on your PC)I'm not responsible for bricked devices, dead SD Cards, broken phone chargers etc.You do all at your own Risk!
If you are new, just work the first 3 steps from top to bottom.
Flash Root & Odin3:
At the https://autoroot.chainfire.eu/ site you can Download the the Root File for your Device (Link to A300FU). When you Downloaded the "CF-Auto-Root-xxx.zip" File unzip it. In this zip you will find the Odin3xxx.exe and the Root .tar.md5 File
You need this Odin3 tool also for TWRP and going Back to Stock Rom
For Root: Make sure your device is in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3xxx.exe file, press the PDA/AP button, select the Root .tar.md5 file, and click Start, never interrupt this action! You can find more detailed instructions and assistance at [CENTRAL] CF-Auto-Root Thread
Flash TWRP:
You can Download the TWRP File at the [RECOVERY][ROOT][TWRP 3.0.2-1]Samsung Galaxy A3(2015) SM-A300F/FU/G/H/M Thread. I recommend the Build from Post 80 it has working MTP & OTG for the FU Device!
To Install Start download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the TWRPxxx.tar file, and click Start, never interrupt this action! After Reboot you can get there by holding VolUp+Home+Power when the device is turned off.
There are also a TWRP 2.8.7.0 and a TWRP 3.0.0-0 but both have small bugs so i recommend TWRP 3.0.2-1 only if you have Problems try to downgrade
TWRP Bugs:
TWRP 2.8.7.0 Can only Install CM12.1 ROMs, it has no MTP & no OTG
TWRP 3.0.0-0 Can only Install CM13 ROM & it has no MTP but OTG is Working
TWRP 3.0.2-1 Can not install @cbolumar ROMs and the Build from Opening Post has no OTG
TWRP 3.1.0 Only tested with LineageOS, it still has no MTP!!!
Flash a Custom ROM:
You can Install a ROM now with TWRP you can enter TWRP by holding VolUp+Home+Power when the device is turned off.
In TWRP IT IS HIGHLY RECOMMEND TO DO FIRST A BACKUP! (I Recommend to placed at the SD Card)
Backup -> Storage : Micro SDcard -> Ok -> [x] Boot, [x] System, [x] Data, [x] Cache, [x] Recovery, [x] EFS, [x] MODEM, [x] APNHLOS -> Swipe to Backup
If anything goes wrong you can easy Restore your Device in TWRP without losing anything, so it's also recommended to Backup your Custom ROM
Now you need your Custom Rom, Google Apps like Opengapps for ARM and i recommend latest Magisk[/URL, OR (if you prefer) [URL="http://download.chainfire.eu/supersu"]SuperSU to Manage Root Access.
Place this zip Files at your Device (I Recommend to placed at the SD Card)
Now you enter TWRP and go to:
Wipe -> Advanced Wipe -> [x] Dalvik / ART Cache, [x] System, [x] Data, [x] Cache -> Swipe to Wipe
Now go back to main menu and select:
Install -> Storage : Micro SDcard -> Ok -> now choose your ROM zip first, you can "Add More Zips" and choose Gapps zip and if you want you can Add direct Magsik OR SuperSU zip as well -> Swipe to Confirm Flash
After placing files the Device need a Reboot, at the First Start it will Install your Rom, so be patiently at first start!
Flash Xposed:
Magisk user on Android M (6.x) or better follow this Thread [2018.5.6][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27) by topjohnwu
SuperSU user on Android M (6.x) or better follow this Thread [OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo [v90-beta3, 2018/01/29]
info:
SDK 21: Android 5.0 | SDK 22: Android 5.1 | SDK 23: Android 6.0 | SDK 24: Android 7.0 | SDK 25: Android 7.1 | SDK 26: Android 8.0 | SDK 27: Android 8.1
at CM12.1 ROM's Offical Xposed works fine.
Download the "sdk22-arm" zip, and Install it with TWRP first start need a long time! be patient!
After the Framework is installed you install the "XposedInstaller" apk, done.
For stock rom you should visit [UNOFFICIAL] Xposed for Samsung Lollipop by arter97 but it´s for deodex'ed ROMs for this you should visit [Deodex][SM-A300] Deodex Thread for Samsung Galaxy A3
emtepe35 said:
Working only on MM touchwiz (tested by me on A300FU with TWRP 3.0.2-1)
How to install:
- Install this Xposed Installer App version http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
- Make a nandroid backup
- Copy the Xposed file and the uninstaller to your sdcard
- Flash "xposed-vxx.x-sdkxx-tw-armxx-custom-build-by-wanam-xxxxxxxx.zip" through a custom recovery (TWRP/CWM...)
- Reboot and Waiiiiiiiiit, it may take several minutes to boot up depending on your Rom size.
xposed.zip download (ARM SDK23)
https://www.androidfilehost.com/?fid=24591000424962808
Official thread link:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
Flash Stock ROM:
Download your Firmware at Sammobile than i recommend you to Wipe all (Advanced Wipe) in TWRP except the SDcard!
Boot your Device in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the .tar.md5 file, and click Start, never interrupt this action!
After doing this you lose TWRP and Root so if you need it you have to install it new.
You should not try to Flash 4.x ROMs it could Brick your Device!
With a Stock Marshmallow ROM it is recommended to use a Custom Kernel
A300FU / A300Y Custom Kernel:
Kraken Kernel R1 from @bulgar
Will only work with at Stock Marshmallow (6.x) ROM
-soon- LineageOS Support
hadesKernel from @corsicanu
Will only work with at Stock Marshmallow (6.x) ROM
A300FU / A300Y Modification:
[MOD][Stock Rom] Enable More Quick Tiles on Touchwiz from @astrit1
Will only work with at Stock Lollipop (5.x) ROM
There are still the following Bugs:
No Bugs
[ROM][A300FU][6.0.1] [GS]Mod from @[GS]
There are still the following Bugs:
Private Mode Not Work
WHASISTROM We have a simple stock rom [A300FU/OL3/OJ5] from @nowheel Discontinued
nowheel said:
Bad news i abbandoned project.. after my hdd is broken with project and all whasistrom file, work document and other.
Click to expand...
Click to collapse
A300FU / A300Y Custom ROMs:
Check also in All Samsung Galaxy A3 (2015)'s ROMs Thread from @Falaysia
-Recommended-
LineageOS 15.1 Unofficial for Samsung Galaxy A3 (2015) from @vl_w
There are still the following Bugs:
* FM works only on headphones
* Unable to capture video in 1080p (only 720р works)
* Incorrectly work with secondary sim (incall sound issues)
* On FU and H doesn't adjusting flahlight brightness
* On H incorrectly detecting battery temperature
* Hardware keystore doesn't work (only software)
* NFC sometimes doesn't work
LineageOS 14.1 Unofficial for Samsung Galaxy A3 from @vl_w
There are still the following Bugs:
no Bugs
CyanogenMod 12.1 for Samsung Galaxy A3 from @evilracer123 Discontinued
Meizirkki said:
OP is no longer working on a300fu
Click to expand...
Click to collapse
In the Opening Post is not the latest Build!
This is the post with the last Build from 19th January 2016
evilracer123 said:
Here's the newest build:
https://mega.nz/#!OcJ0BKKQ!hkQN4SnzY-40tm9v79vzP_erZxIxtpa0_jPwMvLQaiU
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by using CPU Awake - Wake Lock with Unlimited time & Activate on Reboot (Clean Master turns it off btw) or Wake Lock - PowerManager with "PARTIAL_WAKE_LOCK")
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-Folders are not displayed correctly with LCD density 260 DPI (can be Fixed by changing it to 240 DPI)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
-for some users "com.qualcomm.timeservice" fc time to time (can be Fixed by disable the automatic services in Time settings)
-for some users gps are not Working
at my device:
-Cast screen is not Working
CyanogenMod 12.1 Resurrection Remix from @cbolumar Discontinued
garbanura said:
he switched to a5 and abandoned a3 for good, i know from first hand sorry.
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by open integrated Kernel Adiutor and allow Root access)
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
at my device:
-Cast screen is not Working
Note: can only installed with TWRP 2.8.7.0 after installing you can upgrade your Recovery to TWRP 3.0.2-1
CyanogenMod 12.1 from @cbolumar Discontinued
garbanura said:
he switched to a5 and abandoned a3 for good, i know from first hand sorry.
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by using CPU Awake - Wake Lock with Unlimited time & Activate on Reboot (Clean Master turns it off btw) or Wake Lock - PowerManager with "PARTIAL_WAKE_LOCK")
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
-for some users "com.qualcomm.timeservice" fc time to time (can be Fixed by disable the automatic services in Time settings)
at my device:
-Cast screen is not Working
Note: can only installed with TWRP 2.8.7.0 after installing you can upgrade your Recovery to TWRP 3.0.2-1
Hope this will Help to answering the most Questions
By the way i'm not a Dev, i'm only a regular user that wants to help!
You will also get Information and Help at the Everything Samsung a3 Thread :good:
Nice guide. Which one would you recommend between the CM12.1 and CM12.1 RR?
Also, for downgrading TWRP, you just need to flash the older version, right?
King-V said:
Nice guide. Which one would you recommend between the CM12.1 and CM12.1 RR?
Also, for downgrading TWRP, you just need to flash the older version, right?
Click to expand...
Click to collapse
Definitely CM12.1 RR!
Right just flash first TWRP 2.8.7.0 via Odin3 install the ROM and than Flash TWRP 3.0.2-1 via Odin3, btw. the Build from post 80 has a working MTP and OTG in TWRP (only in TWRP not at the ROM!)
And you can anytime time flash TWRP 2.8.7.0 again if you have to Install new
So only good ROM for daily driver will be @mygalaxya cm13?
emtepe35 said:
So only good ROM for daily driver will be @mygalaxya cm13?
Click to expand...
Click to collapse
This could need some time, i recommend to try CyanogenMod 12.1 Resurrection Remix, or a Stock MM with aresKernel :good:
Jonny_Hood said:
This could need some time, i recommend to try CyanogenMod 12.1 Resurrection Remix, or a Stock MM with aresKernel :good:
Click to expand...
Click to collapse
It's lot to do with RR to make it stable without SOD etc. (I really need normal usb connection for daily usage)
What's twrp should I use with stock mm to flash ares kernel and can I go back to lollipop via odin? (Mygalaxya's cm13 needs LP bootloader and modem)
emtepe35 said:
It's lot to do with RR to make it stable without SOD etc. (I really need normal usb connection for daily usage)
What's twrp should I use with stock mm to flash ares kernel and can I go back to lollipop via odin? (Mygalaxya's cm13 needs LP bootloader and modem)
Click to expand...
Click to collapse
Best is TWRP 3.0.2-1 and yes you can go back anytime via odin
Jonny_Hood said:
Best is TWRP 3.0.2-1 and yes you can go back anytime via odin
Click to expand...
Click to collapse
Thanks I tried this but I flashed wrong firmware and wifi was broken but I know how to repair it.
Tomorrow I'll try flash compatible firmware and try again.
After flash MM and reflash LP it was a bootloop in first boot. I went to download mode and flash twrp then restore backup and it boots up.
Thanks
emtepe35 said:
Thanks I tried this but I flashed wrong firmware and wifi was broken but I know how to repair it.
Tomorrow I'll try flash compatible firmware and try again.
After flash MM and reflash LP it was a bootloop in first boot. I went to download mode and flash twrp then restore backup and it boots up.
Thanks
Click to expand...
Click to collapse
This Bootloop thing happened at my Device sometimes too, if i flashed a stock ROM via Odin, thats why i started to Wipe all Partitions via TWRP before flashing, that works for me flawless
Than happy flashing tomorrow
Jonny_Hood said:
This Bootloop thing happened at my Device sometimes too, if i flashed a stock ROM via Odin, thats why i started to Wipe all Partitions via TWRP before flashing, that works for me flawless
Than happy flashing tomorrow
Click to expand...
Click to collapse
OK I've got one last question the wipe in twrp means it deleting it to zero and if I accidentally go to system and not to download I'll get hard brick? Or wipe means it restoring it to factory files? Wipe modem too?
Sorry for noob questoms but I want to be sure before do anything
emtepe35 said:
Wipe in twrp means it deleting it to zero?
Click to expand...
Click to collapse
Yes
emtepe35 said:
If I accidentally go to system and not to download I'll get hard brick?
Click to expand...
Click to collapse
No it will not brick, if you accidentally go to system it will stuck at A3 logo, than you can go to Download Mode with pressing "VolDown+Home+Power" for 30 Sec
emtepe35 said:
Or wipe means it restoring it to factory files? Wipe modem too?
Click to expand...
Click to collapse
Wipe -> Advanced Wipe -> [x] Dalvik / ART Cache, [x] System, [x] Data, [x] Internal Storage, [x] Cache -> Swipe to Wipe -> go back -> go back -> Format Data -> yes
Added to Sticky Roll-Up Thread
Cheers
Razvan
Forum Moderator
Razvan said:
Added to Sticky Roll-Up Thread
Cheers
Razvan
Forum Moderator
Click to expand...
Click to collapse
Thank you very much
What about stock marshmallow xposed?
Sorry I'm noob and I can't find it alone.
emtepe35 said:
What about stock marshmallow xposed?
Sorry I'm noob and I can't find it alone.
Click to expand...
Click to collapse
As far i know, it will not working with Stock MM.
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Jonny_Hood said:
As far i know, it will not working with Stock MM.
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Click to expand...
Click to collapse
I had a LP stock Samsung touch wiz and it was working. Some people tells they have MM xposed. I'll try to ask them
emtepe35 said:
I had a LP stock Samsung touch wiz and it was working. Some people tells they have MM xposed. I'll try to ask them
Click to expand...
Click to collapse
Let me know if and how it work
I'm happy with this.
Working only on MM touchwiz (tested by me on A300FU with TWRP 3.0.2-1)
How to install:
- Install this Xposed Installer App version http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
- Make a nandroid backup
- Copy the Xposed file and the uninstaller to your sdcard
- Flash "xposed-vxx.x-sdkxx-tw-armxx-custom-build-by-wanam-xxxxxxxx.zip" through a custom recovery (TWRP/CWM...)
- Reboot and Waiiiiiiiiit, it may take several minutes to boot up depending on your Rom size.
xposed.zip download (ARM SDK23)
https://www.androidfilehost.com/?fid=24591000424962808
Official thread link:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Hi, what I have to do to downgrade my A300FU to lollipop (Brand Italy Vodafone)?
InfamousMykol said:
Hi, what I have to do to downgrade my A300FU to lollipop (Brand Italy Vodafone)?
Click to expand...
Click to collapse
Stock ROM:
Download your Firmware at Sammobile than i recommend you to Wipe all (Advanced Wipe) in TWRP except the SDcard!
Boot your Device in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the .tar.md5 file, and click Start, never interrupt this action!
After doing this you lose TWRP and Root so if you need it you have to install it new.
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 everyone. These packs are for A2017 and A2017G for now. A2017U will be added soon.
Full stock ROM. You can make your phone fully original.
You can unbrick your device with this ROM.
You are responsible for everything.
Your data will be erased. Backup all your stuffs.
Backed up by @asderdd from forum.turkdevs.com
Download:
MiFlash 20160401.exe [url]https://drive.google.com/file/d/0B065LdNGqJLGM2xfSkZMbVYwc3M/view[/URL]
ADB Installer 1.4.3.exe [url]https://drive.google.com/open?id=0B065LdNGqJLGWUtFczMyTUdTTTQ[/URL]
A2017 (Chinese Version)
ZTE_A2017V2.0.0B13_FULL_EDL_PACKAGE_BY_TURKDEVS
https://www.androidfilehost.com/?fid=889764386195932870
ZTE_A2017V2.0.0B08_FULL_EDL_PACKAGE (Android 7.1.1 - MiFavor UI 5.0) [url]https://drive.google.com/open?id=0B065LdNGqJLGaUpXRV9WRVNkUEk[/URL]
A2017G (Global European Version)
ZTE_A2017GV1.2.0B06_FULL_EDL_PACKAGE_BY_TURKDEVS.7z [url]https://www.androidfilehost.com/?fid=745425885120758978[/URL]
ZTE_ZTE A2017GV1.2.0B09_FULL_EDL_PACKAGE_BY_TURKDEVS.zip
https://androidfilehost.com/?fid=962021903579497293
A2017U (US Version)
https://www.androidfilehost.com/?fid=673368273298988889
Instructions:
- Install MiFlash. Driver will be installed automatically.
- Install ADB
- Enable USB Debugging.
- Reboot edl.
- Make sure you see to device as "Qualcomm HS-USB QDLoader 9008"
- Open MiFlash. Browse and choose folder you've downloaded.
- Click Refresh. You should see your device on list.
- Flash and wait until installation is done.
- You can turn on your device.
To install a ROM to another model. (Ex: B08 Chinese ROM to U devices.)
1. Download Chinese ROM
2. Download latest bootstack zip for your device from @DrakenFX topic.
3. Move NHLOS.bin from bootstack to ROM folder.
4. Flash ROM as guide.
You can not get signal if you don't do these steps.
Thanks.
@asderdd
Source: [url]https://forum.turkdevs.com/konu/edl-unbrick-zte-axon-7-all-stock-roms.13629/[/URL]
Please hit the thanks button if I help you.
i put supersu 2.82 and when restarted, stopped in axon door
Just to be clear, Is this stock b08? I mean, it is not modified or pre-rooted? Thanks.
yes, its a stock rom
What does that mean, it is just a stock rom? Did you did any modifications to it? Why can't we flash through TWRP?
iker84 said:
yes, its a stock rom
Click to expand...
Click to collapse
Thanks.
Raffikie said:
What does that mean, it is just a stock rom? Did you did any modifications to it? Why can't we flash through TWRP?
Click to expand...
Click to collapse
It's not for twrp. The OP said to flash it in miflash.
i read in other forum, magisk and supersu, causes bootloop, i probe to install supersu and have bootloop
iker84 said:
i read in other forum, magisk and supersu, causes bootloop, i probe to install supersu and have bootloop
Click to expand...
Click to collapse
I'm using magisk 13.6 only on B08 and I don't have any problems. All passed on safetynet.
Magisksu is working fine + I can also hide root from any app I choose.
If it helps, this is how I installed magisk on my stock chinese unit.
1. Reboot to twrp.
2. Flash unSu to remove all traces of root.
3. Restore original boot.img
4. Flash magisk 13.6
5. Reboot
otaconremo said:
Just to be clear, Is this stock b08? I mean, it is not modified or pre-rooted? Thanks.
Click to expand...
Click to collapse
Fully stock. As first day when you buy the phone.
i dont have signal in my 2017g
iker84 said:
i dont have signal in my 2017g
Click to expand...
Click to collapse
Because this rom is for A2017. install a2017g bootstack from twrp or delete nhlos.bin from folder. Extract nhlos from 2017g bootstack and reinstall rom.
WesTD said:
Because this rom is for A2017. install a2017g bootstack from twrp or delete nhlos.bin from folder. Extract nhlos from 2017g bootstack and reinstall rom.
Click to expand...
Click to collapse
thanks!
otaconremo said:
I'm using magisk 13.6 only on B08 and I don't have any problems. All passed on safetynet.
Magisksu is working fine + I can also hide root from any app I choose.
If it helps, this is how I installed magisk on my stock chinese unit.
1. Reboot to twrp.
2. Flash unSu to remove all traces of root.
3. Restore original boot.img
4. Flash magisk 13.6
5. Reboot
Click to expand...
Click to collapse
not for me!
bootloop in axon window
WesTD said:
Hi everyone. This ROM is for A2017 for now. Other variants will be added soon.
Full stock ROM. You can make your phone fully original.
You can unbrick your device with this ROM.
You are responsible for everything.
Your data will be erased. Backup all your stuffs.
Backed up by @asderdd from forum.turkdevs.com
Download:
MiFlash 20160401.exe https://drive.google.com/file/d/0B065LdNGqJLGM2xfSkZMbVYwc3M/view
ADB Installer 1.4.3.exe https://drive.google.com/open?id=0B065LdNGqJLGWUtFczMyTUdTTTQ
ZTE_A2017V2.0.0B08_FULL_EDL_PACKAGE (Android 7.1.1 - MiFavor UI 5.0) https://drive.google.com/open?id=0B065LdNGqJLGaUpXRV9WRVNkUEk
Instructions:
- Install MiFlash. Driver will be installed automatically.
- Install ADB
- Enable USB Debugging.
- Reboot edl.
- Make sure you see to device as "Qualcomm HS-USB QDLoader 9008"
- Open MiFlash. Browse and choose folder you've downloaded.
- Click Refresh. You should see your device on list.
- Flash and wait until installation is done.
- You can turn on your device.
Thanks.
@asderdd
Source: https://forum.turkdevs.com/konu/edl-unbrick-zte-axon-7-all-stock-roms.13629/
Click to expand...
Click to collapse
Can we root post flashing ? Please let me know the procedure too.
I am getting 'cannot read hello packet' when trying to flash
Raffikie said:
I am getting 'cannot read hello packet' when trying to flash
Click to expand...
Click to collapse
Reboot edl on every try to flash. If you still can't install it try on another pc. I was getting same error, i did it on another PC
In B06 my LED isn't working. How about this ROM? Any issues?
Gesendet von meinem ZTE A2017G mit Tapatalk
otaconremo said:
I'm using magisk 13.6 only on B08 and I don't have any problems. All passed on safetynet.
Magisksu is working fine + I can also hide root from any app I choose.
If it helps, this is how I installed magisk on my stock chinese unit.
1. Reboot to twrp.
2. Flash unSu to remove all traces of root.
3. Restore original boot.img
4. Flash magisk 13.6
5. Reboot
Click to expand...
Click to collapse
How did you flash TWRP. Once on B08 it won't let me...
ultramag69 said:
How did you flash TWRP. Once on B08 it won't let me...
Click to expand...
Click to collapse
I used tenfar's tool which I had since MM. I don't know why but there are already two users who got bricked using tenfar's tool on b08 but mine is okay.
Also, i have mine BL unlocked since MM and OTA'd till b08.
If I install this via edl will it restore stock recovery. I have twrp with a locked bootloader and can't install otas. Want to go completely back to stock in order to continue to receive updates
About
**********
I've created a flashable ROM zip of the latest H990DS KDZ SEA Region. Everything is working correctly on my H990 Single SIM.
ARB
**********
0
Security Patch
**********
1 April 2019
Download
**********
1. With modem & cust partitions (only if you know what you are doing):
https://drive.google.com/open?id=1YARnnE4-V1y9Jd1EhTzdizdkd6DaAYz_
2. Without modem & cust partitions (keeps your existing modem, recommended):
https://drive.google.com/open?id=1gCHxAk3hXjCsA4Qm3djgSmJEb3rSL5WA
Installation process:
**********
1. Upgrading / flashing over another stock Oreo ROM:
• Flash latest TWRP
• BACKUP everything
• Wipe (caches)
• Flash ROM
• Flash Magisk
• Flash MK2000 Oreo kernel (Important!)
• Reboot
• Enjoy
2. Clean from scratch install:
• Flash latest TWRP
• BACKUP everything
• Backup everything you want to put back, it will be wiped
• Clean wipe (data, system, caches)
• Flash ROM
• Flash Magisk
• Flash MK2000 Oreo kernel (Important!)
• Reboot
• Enjoy
flashing the second rom without modem or cust now on my h990ds , i hope everything goes well
sniper9911 said:
flashing the second rom without modem or cust now on my h990ds , i hope everything goes well
Click to expand...
Click to collapse
Just please remember to flash MK2000 kernel after you flash the ROM without rebooting in-between.
I made the mistake of rebooting afterwards and the stock kernel restored the stock recovery and wiped my device.
(This wasn't an issue because I made a full backup of all of my data though)
updated successfully
Updated the dirty way flashed over my current ROM ... I wiped cache and art cache just in case
Seems legit and so far my device is finishing the data setting , i did make a backup of my firmware files just in case and so far it went smoothly
All i did was downloading the ROM , Twrp , mk2000 h990ds v2.1 And Magisk latest
Flashed Twrp first then recovery rebooted , wiped Dalvick and cache then flashed ROM then flashed mk2000 then magisk and phone booted
Thanks for the update
I have also updated my H990DS successfully by "dirty" upgrade keeping all apps.
I just added H990DS_Hide_Boot_Warning.zip to remove the error message at boot start.
sniper9911 said:
Thanks for the update
Click to expand...
Click to collapse
tapir1505 said:
I have also updated my H990DS successfully by "dirty" upgrade keeping all apps.
Click to expand...
Click to collapse
Thanks for your feedback!
Glad to know it is working correctly
Against 20a the only difference is s3curity patch?
faeterov said:
Against 20a the only difference is s3curity patch?
Click to expand...
Click to collapse
I'm not sure of any other difference except the security patch.
I assume there are some minor tweaks as the update notification
generally mentions "usability improvements", but LG being LG don't
release a change-log so who knows unfortunately...
I have installed v20b (stock room and rooted room), but this version do not support fingerprint sensor, terrible, it took me more than 2 days for this :crying::crying:
luuhungit said:
I have installed v20b (stock room and rooted room), but this version do not support fingerprint sensor, terrible, it took me more than 2 days for this :crying::crying:
Click to expand...
Click to collapse
You'll need to provide more details than this.
Which variant V20? What ROM did you come from? Did you backup partitions? etc.
Also: to add, this is normally a modem issue and is resolved by restoring / flashing the correct modem
jl10101 said:
You'll need to provide more details than this.
Which variant V20? What ROM did you come from? Did you backup partitions? etc.
Also: to add, this is normally a modem issue and is resolved by restoring / flashing the correct modem
Click to expand...
Click to collapse
maybe, thank for idea
i is using h900ds, taiwan version
yesterday, i used LGUP to flash v20b version with refusbish function, but second sim and fingerprint inactive.
maybe refusbish function did not flashed all partition on device
today, i have to flash v10c to use dirtysanta root, then flash all partition of v20b version, but ignore aboot to keep bootloader unlocked, it is using with old data partition very well.
luuhungit said:
maybe, thank for idea
i is using h900ds, taiwan version
yesterday, i used LGUP to flash v20b version with refusbish function, but second sim and fingerprint inactive.
maybe refusbish function did not flashed all partition on device
today, i have to flash v10c to use dirtysanta root, then flash all partition of v20b version, but ignore aboot to keep bootloader unlocked, it is using with old data partition very well.
Click to expand...
Click to collapse
Go to 10c root flash 20a partitions through Patched LGUP ignoring aboot aboot.bak and recovery recovery.bak (tarp may be gone but as long as you'll have boatloads unlocked you can flash twrp back)after that just flash only 20b system via LGUP Partitions DL I dunno whats going on with LG KDZs from now on all you should keep the old partitions from 20A and just flash system
jl10101 said:
Just please remember to flash MK2000 kernel after you flash the ROM without rebooting in-between.
I made the mistake of rebooting afterwards and the stock kernel restored the stock recovery and wiped my device.
(This wasn't an issue because I made a full backup of all of my data though)
Click to expand...
Click to collapse
unfortunately im using F800L, so it will not work if i flash this rom into my device.
is there any change to tell me how to update the security patch for my device?
thx b4 m8
can I use this patch for H990DS IDN (Indonesia version) that is still 2.0? It's dual sim version...
thanks
stingbandel said:
can I use this patch for H990DS IDN (Indonesia version) that is still 2.0? It's dual sim version...
thanks
Click to expand...
Click to collapse
Yes. Use mk200 beta38
Update to 20B and Just remember to back up firmware and efs folders from Oreo 20A and restore after flashing 20B otherwise you will lose the second sim
sniper9911 said:
Updated the dirty way flashed over my current ROM ... I wiped cache and art cache just in case
Seems legit and so far my device is finishing the data setting , i did make a backup of my firmware files just in case and so far it went smoothly
All i did was downloading the ROM , Twrp , mk2000 h990ds v2.1 And Magisk latest
Flashed Twrp first then recovery rebooted , wiped Dalvick and cache then flashed ROM then flashed mk2000 then magisk and phone booted
Thanks for the update
Click to expand...
Click to collapse
I followed exact steps in OP (wiped caches, flashed 20b ROM, Magisk 19.3, MK2000 v2.2b38 H990DS, rebooted) and thought it worked for me as well until I noticed some built-in system apps were not working. Calendar, Chrome and others had strange names in Apps list (Chrome was called "add to dictionary" and Calendar was something like "on time (%s,..."). I managed to get them working again by stopping them and reinstalling from the apk files in system but wasn't sure I woudn't have other issues, so I wiped system partition and reflashed it although it didn't seem to change anything. When I noticed Bluetooth wouldn't enable I decided to go back to 20a by flashing full ROM (all done through TWRP) but that didn't fix the issue. I had even tried going back to MK2000 2.1 but no change. Finally had to do full restore from TWRP backup to get BT working again. Would like to have latest security patch.
Does anyone have any ideas what went wrong? Could any Magisk modules cause issues? Any help is appreciated.
Works perfect.
I flashed it straight from Lineague 16.1 after wipe, no problems.
(LG H990DS)
albaniax said:
Works perfect.
I flashed it straight from Lineague 16.1 after wipe, no problems.
Click to expand...
Click to collapse
Good to hear! Thanks for the feedback!
Hi. H990DS Twn variant. Currently running stock rom 20a (first oreo rom released for 990DS).
I see that you've uploaded another stock rom for 990DS that is 20H. But security patch is from FEB.
But this is a newer thread, so I assume this is the newest release. Could you please just confirm if this is the rom I should flash.
Thanks in advance
Salvaparalyzer said:
Hi. H990DS Twn variant. Currently running stock rom 20a (first oreo rom released for 990DS).
I see that you've uploaded another stock rom for 990DS that is 20H. But security patch is from FEB.
But this is a newer thread, so I assume this is the newest release. Could you please just confirm if this is the rom I should flash.
Thanks in advance
Click to expand...
Click to collapse
I'm not sure why 20H is effectively a "newer" ROM going by LG's naming convention.
They used 20B (this ROM) with a newer security patch, and the actual file is newer than 20H.
I would normally assume that 20H should have a newer security patch and be a newer build of Oreo, but it seems not.
This ROM essentially is the latest available. I cannot find any changelogs to verify that 20H has a newer system / android build though. Sorry!
Dont worry guys if u got confused with the flashing steps of encryption and decryption
[Flashing process from miui or any Custom rom] :-
Install Ptwrp
Format data By typing "YES"
Flash latest Chinese wkly fw
Flash ROM
Flash GAPPS (Optional)
Flash Fcrypt (Optional) [This will make u decrypted]
Reboot
Enjoy
In Custom ROMS Encryption To Encryption :
If you are encrypted and want to switch roms:
1. Remove lock screen password
2. Back up your apps and stuffs
3. Boot to recovery
4. Wipe only Data in advance wipe
5. Flash new ROM and stuffs (Make sure it is properly wrappedkey supported) else can get error or worst.
5. Reboot
6 Done. Profit :good:
Encryption to Decryption :
If u are encrypted and want to get decrypted :
1. First format data (by typing yes)
2. Flash latest Chinese wkly fw
3. Flash rom then gapps then fcrypt zip and
4. Done.. (Magisk is optional after 1st boot).
5. Profit :good:
[ Decryption to Decryption ]
If decrypted and want to stay decrypted
1. Go adv. wipe :- wipe [data, system, vendor , dalvik, caches]
2. Flash ROM
3. Flash GAPPS (Optional)
4. Flash Fcrypt
5. Reboot
6. Enjoy
Note : Make sure you you flash latest Chinese wkly fw.?
Well if you found it useful then Hit the thanks button (it's FREE of Cost)
WELL, IF U LIKE MY WORK Then HIT the Thanks Button . KThanks.
Thanks a lot buddy really needed this. U helped me a lot . Kudos 2 ur hardwork #lifesaver
Hey..what are the steps to move from custom rom (decrypted) to MIUI (decrypted) ?
Thanks ?
sujju said:
Hey..what are the steps to move from custom rom (decrypted) to MIUI (decrypted) ?
Click to expand...
Click to collapse
Who wants to go to miui hahahaha..
anyways
1. Format data
2. Flash Miui recovery zip
3. Flash “no-verity-force-encrypt.zip” file.
4. Reboot
5. ENJOY :good:
RupeshRN said:
Thanks
Click to expand...
Click to collapse
:angel::angel:
sourav24071999 said:
Who wants to go to miui hahahaha..
anyways
1. Format data
2. Flash Miui recovery zip
3. Flash “no-verity-force-encrypt.zip” file.
4. Reboot
5. ENJOY :good:
Click to expand...
Click to collapse
Thanks..
Just to be sure, formatting data would erase internal storage. You mean then I would sideload the zips through TWRP?
sujju said:
Thanks..
Just to be sure, formatting data would erase internal storage. You mean then I would sideload the zips through TWRP?
Click to expand...
Click to collapse
Yes formattinfg data will erase ur storage . NO sideload
sourav24071999 said:
Dont worry guys if u got confused with the flashing steps of encryption and decryption
[Flashing process from miui or any Custom rom] :-
Install Ptwrp
Format data By typing "YES"
Flash latest Chinese wkly fw
Flash ROM
Flash GAPPS (Optional)
Flash Fcrypt (Optional) [This will make u decrypted]
Reboot
Enjoy
In Custom ROMS Encryption To Encryption :
If you are encrypted and want to switch roms:
1. Remove lock screen password
2. Back up your apps and stuffs
3. Boot to recovery
4. Wipe only Data in advance wipe
5. Flash new ROM and stuffs (Make sure it is properly wrappedkey supported) else can get error or worst.
5. Reboot
6 Done. Profit :good:
Encryption to Decryption :
If u are encrypted and want to get decrypted :
1. First format data (by typing yes)
2. Flash latest Chinese wkly fw
3. Flash rom then gapps then fcrypt zip and
4. Done.. (Magisk is optional after 1st boot).
5. Profit :good:
[ Decryption to Decryption ]
If decrypted and want to stay decrypted
1. Go adv. wipe :- wipe [data, system, vendor , dalvik, caches]
2. Flash ROM
3. Flash GAPPS (Optional)
4. Flash Fcrypt
5. Reboot
6. Enjoy
Note : Make sure you you flash latest Chinese wkly fw.?
Click to expand...
Click to collapse
Damn the community really needed this. Good job man.
Could you also add steps to move from MIUI to Custom? (Both encrypted) and vice versa.
im on the previous weekly build of xiaomi.eu rom and i haven't flashed fcrypt disabler, Now how should i update my rom to the latest weekly build? can i use the built-in updater app or should i follow some other procedure? also is it fine to stay encrypted?
Naveenthemi said:
Damn the community really needed this. Good job man.
Could you also add steps to move from MIUI to Custom? (Both encrypted) and vice versa.
Click to expand...
Click to collapse
?? Welcome
Sachin ET said:
im on the previous weekly build of xiaomi.eu rom and i haven't flashed fcrypt disabler, Now how should i update my rom to the latest weekly build? can i use the built-in updater app or should i follow some other procedure? also is it fine to stay encrypted?
Click to expand...
Click to collapse
Use in build ota updater
Hi, can somebody link the fcrypt zip?
Hello,
I was on MIUI , then flashed PE 10,
switched back to MIUI.
Sensors aren't working now !
I tried with MIUI Fastboot rom as well as ZIP file.
still no luck
suggestions please !
How to go back to miui 11 from pe 10 rom
I was in miui 11 encrypted , then i came to pe 10 encrypted , now how can i go back to miui 11 without losing sensor?
rasik107 said:
Hello,
I was on MIUI , then flashed PE 10,
switched back to MIUI.
Sensors aren't working now !
I tried with MIUI Fastboot rom as well as ZIP file.
still no luck
suggestions please !
Click to expand...
Click to collapse
Ofc it wont be wrking.. y dont u guys read changelogs or imp notes if u flash pe then roll back to miui rip to sensors and L1 . For fix check violet official grp. or pe for violet grp.
John878 said:
I was in miui 11 encrypted , then i came to pe 10 encrypted , now how can i go back to miui 11 without losing sensor?
Click to expand...
Click to collapse
Stick to Andriod 10 roms.
sourav24071999 said:
Stick to Andriod 10 roms.
Click to expand...
Click to collapse
That means once you came to PE, than no way to go back to MIUI?
drjmvgami said:
That means once you came to PE, than no way to go back to MIUI?
Click to expand...
Click to collapse
No.. untill memeui fix this
Is it gona encrypt havoc os because it already decrypted?