**** Disclaimer: I'm not responsible if you destroy your device. Learn at your own risk!!! ****
Alright, So I am a bit Moderately skilled to Custom Development. I do not know a lot of in-depth either.
However, I do know enough to help other new beginners out.
As I continue to learn more info and details, I will update this post frequently.
Completed guide, I'm saving and typing as not to lose progress. Last Updated- 01/03/2021
Please do note, CROSS-VERIFY if the info here is correct before following it.
What is a Custom ROM?
Simply put, it is a new Operating System [OS].
People find their stock (the one you got with your phone) to be boring, or they dislike it or want more customization and optimization, lesser bloatware (useless unwanted system apps).
Thus some Developers made their own ROM (aka OS). Then others made it compatible with our phone. Sometimes this works perfectly, most of the time it doesn't. Thus Asking people how the ROM is, is always good to ask.
STABLE means almost no errors, UNSTABLE means a few/lots of errors.
OFFICIAL means the Developer in charge will keep updating it and has been granted the task officially. EOL means End Of Life, aka Developer, won't work on it anymore.
FOD means finger on display icon, FP means fingerprint sensor, SOT means screen on time or how long your battery will last.BB means Battery backup, or how long the battery will last.
Click to expand...
Click to collapse
How To Get a Custom ROM?
So, to flash (insert) a new Custom ROM, we first need to unlock the Bootloader. The Bootloader is what allows us to wipe (remove/erase) our data, and current OS and flash a different one.
Then we flash a Recovery. (A software that makes flashing and wiping and other stuff easy)
Then flash the ROM, Then (if needed) vendor+firmware, gapps, magisk.
So in k20 pro/Mi 9t pro, there are 5 vendors. Indians use Indian Vendor, Chinese users use Chinese Vendor, similarly for EEA, Russian, and Global.
In this Vendor zip file, nowadays, the firmware is included in them, so it isn't required to flash it separately.
If you are coming from miui 11 and want to flash custom ROM you don't need to flash the vendor.
If you are coming from miui 10 to custom ROM Android 10, you need to flash the miui 11 vendor along with the ROM.
Click to expand...
Click to collapse
How To Unlock Bootloader?
So, you should first update your software to the latest miui OS [current: MIUI 11].
Go to Settings > About Phone > tap on MIUI Version 7 times -> you unlock developer settings
Go to Settings > Additional Settings > Developer Options > enable (switch on) USB Debugging > OEM Unlocking > click on MI Unlock status > link account and device.
To link the account, you must first have a Xiaomi MI account. You can make this in settings, or head to https://account.xiaomi.com
Wait 7-15 days
Once 7-15 days have passed,
USING WINDOWS PC
BACKUP ALL FILES, CONTACTS, WHATSAPP, ANY APP settings (if any), AND SYNC/LINK accounts to cloud => YOU WILL LOSE EVERYTHING NOW
Now download the Mi Unlock tool onto your PC https://xiaomitools.com/mi-unlock-tool-en/
IN A SEPERATE FOLDER
Then download Platform Tools from attachments below.
Then download TWRP (team win recovery project) from https://dl.twrp.me/raphael/
Then download Orange Fox Recovery (OFRP) from https://files.orangefox.tech/OrangeFox-Stable/raphael/ and download the latest file. [Currently: OrangeFox-R-10.1_3-Stable-raphael.zip]
Then download Disable force encrypt zip file from attachments below
Then download adb drivers from https://www.xda-developers.com/what-is-adb/ version 1.4.3 onto your PC and run the application. (Follow from How do I install ADB?) (Or you can skip that and just get the file from attachments below and extract it to C drive as a separate folder directly)
Then download the ROM (links are given below)
Then download gapps (optional). from https://opengapps.org/ and select ARMx64 and PICO then the download button.
Then download Magisk (optional). from https://github.com/topjohnwu/Magisk/releases download the Latest Magisk-vXX.xx.zip file there.[Currently: Magisk-v20.4.zip]
Download the latest vendor file from the below links. (make sure it's the proper file for your device's variant.)
Vendor and firmware are both combined and included in the same zip file.
Global, EEA (Europe), China, Russia Q Vendor: https://xiaomifirmwareupdater.com/archive/vendor/raphael/
Indian Q Vendor: https://xiaomifirmwareupdater.com/archive/vendor/raphaelin/
Check my third comment to learn how to recognize which device variant is yours, and what vendor to download and flash.
NOW! GET READY!
Now, connect your device.
Use your cable included in the box (the charging wire) and connect it to your phone and PC.
Go to 'adb' folder in your C-drive, (on that address bar thing where it shows) This PC >OS(C> adb click on it and type cmd . This will open a Command prompt to that folder.
Type adb devices and on your phone tap on the authorize button that pops up when unlocked. Now type adb devices again.
you will get
Code:
List of devices attached
365278234e device
Now, Switch off your phone.
Open the MI Unlock Tool on your PC, run the file that is an application. Read through everything, click on unlock, confirm.
Wait till the phone fully reboots itself. DON'T TOUCH IT NOW!
Congrats, the phone is now unlocked, and you have stock MIUI 11.
Now skip everything in the setup (we wanna add a custom ROM now remember, why stop here?)
again do the adb devices. You should get the same results.
Now, on your PC
Extract the Platform Tools zip file so you get its folder.
Move the TWRP.img file into the folder.
Open that folder. on that address bar, type cmd to get a new command prompt window.
There type dir *img to confirm the file is found properly.
Now switch off your phone again.
press and hold the power button + volume down button.
you will soon enter fastboot mode.
Now, on the new command prompt where you typed dir *img
type fastboot devices and you will get an output like
Code:
342524356 fastboot
Then type fastboot flash recovery twrp(press the TAB key to autofill)
Now it's done! you have TWRP, but it isn't permanent.
Now, TWRP usage.
Now press and hold power key + volume up to enter TWRP.
Once in TWRP, unlock it.
Go to MOUNT and check if MTP is enabled..... click on "enable MTP" button.
Now copy the ofox.zip (orange fox recovery zip file) to your phone from your PC via your PC.
Now go to INSTALL tap the ofox.zip file, then flash it!
YAY now, orangefox is your Permanent Recovery.
Now go to MENU > Manage Partitions > select only data > format data
Now go to MENU > Reboot > Recovery
Now, to Flash your first Custom Rom.
Now from your PC copy the ROM zip file, Disable decrypt zip file, gapps ( if specified, optional), magisk ( if you want to root, optional)
Now go to MENU > Reboot > Recovery
Now go to FILES > tap on the ROM zip > add to queue > tap disable decrypt zip file > add to queue > (add gapps , magisk if needed) > flash
Now wait for a while (approx 10mins) till ROM boots up and complete the setup process.
Congrats you have your new ROM.
Now just let google download all your apps
Before you change settings like dark mode or use custom launchers etc...
Reboot once for the heck of it. Then Customize the way you like.
**** Backup Your Persist and save it on your PC always. ****
You can backup persist by having root then downloading a terminal app from Playstore. then typing these two commands
Code:
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Click to expand...
Click to collapse
How To Change My ROM? I wanna Try them all!
Now is the easy part, since all the setup is done!
First remove all passwords, fingerprints, and so forth.
For AOSP ROMs: (MIUI below)
AOSP ROMs will not break your L1
First Download the AOSP ROM you want, given below are some examples. (MIUI below)
Each of these might have instructions, usually saying...
Go to your Recovery, (press and hold Power + Volume Up buttons).
Then go to WIPE > select Dalvik, Cache, System, Data > then wipe them all.
Then go to [Files in OFX] [Install in TWRP] and
Only If you are coming from miui and flashing AOSP, go to orangefox settings > manage partitions > data > format > type yes (you lose everything in internal storage) then
Select the Vendor (if it's needed) (not required if moving between any android 10 ROMs) (Just make sure it's the right Vendor for your device/region) (If the previous AOSP rom uses OSS vendor, then you need to wipe vendor as well and flash the stock before proceeding) and flash it.
Select the ROM (Then > add to queue, else if you only needed ROM, just flash. and set-up! yay!)
DFE (not required if you want to be encrypted, which is not recommended.) (A must if you formatted data via orangefox settings and did that typing 'yes' thing)
Gapps (if it isn't already included in the ROM, ask first).
and Magisk (optional if you want root).
For MIUI ROMs: (AOSP above)
First Download the MIUI based ROM you want ( stock, EU, MortalOS, etc), given below are some examples.
Each of these might have instructions, usually saying...
Go to your Recovery, (press and hold Power + Volume Up buttons).
Select the Vendor (if it's needed) (not required if it's currently the proper Vendor, cause EU ROMs to use a custom vendor that works on all devices) (Just make sure it's the right Vendor for your device/region) and flash it.
Then go to WIPE > select Dalvik, Cache, System, Data, Vendor > then wipe them all. (make sure you are on your device's vendor region before wiping it.)
Then go to [Files in OFX] [Install in TWRP] and
Only If you are coming from AOSP and flashing MIUI, go to orangefox settings > manage partitions > data > format > type yes (you lose everything in internal storage) then
Select the ROM (Then > add to queue, else if you only needed ROM, just flash. and set-up! yay!)
DFE (A must if you formatted data via orangefox settings and did that typing 'yes' thing)
Magisk (optional if you want root).
Some Android ROMs
With ROMs being built, changed, and modified on a daily/weekly basis. Some changing to Mi9 fod or LOS fod or using Stock or OSS vendors. Sometimes maintainers shifting or 2 devs building the same rom. The below list is not being maintained anymore. We currently have 50 ROMs. YAY Raphael!
Update: I'm removing most of the ROMs listed here and only adding my personal favorite ROMs
AOSP ROMs
DerpfestOS (two variants, I like em both) - by @Raaj52 -> https://forum.xda-developers.com/k20-pro/development/rom-derpfest-t4132757
SuperiorOS by @HSgod -> https://forum.xda-developers.com/k20-pro/development/rom-superioros-t4130867
MortalOS (miui12) by @Raaj52 -> https://forum.xda-developers.com/k20-pro/development/rom-havoc-os-3-3-t4063081
LineageOS, Pixel Experience, PE+, PE+ Fan Edition, ParanoidOS, MookeOS, TitaniumOS, MSM Xtended, OxygenOS, OmniOS, TreskMod, AOSIP, ColtOS, ArrowOS, BootleggersOS, ExtendedUI (exui), CRdroidOS, RevengeOS, IonOS, AICP, BlissOS, CorvusOS, DerpfestOS, HavocOS, NitrogenOS, HentaiOS, Corvus, TitianiumOS, CygnusOS, CesiumOS, Project 404, DescendantOS, SyberiaOS, EvolutionX, AOSPA, POSP, LegionOS, AncientOS, RebellionOS, SuperiorOS, ShapeshiftOS, WrathOS, ZenX, AIM OS, ConquerOS, PixelDustOS, CygnusOS, StagOS, Ressurection Remix OS, Quartz, PixysOS, PePlusUI, MalluOS, StatixOS, GrapheneOS, ShapeshiftOS, MortalOS, SuperiorOS, AwakenOS, DotOS, Lemon Branch, FluidOS, LiquidOS + more!
MIUI ROMs
EU ROMs, MortalOS, RevolutionOS, Miroom, MMX, Masik + 5 other ROMs
Kernels
Perf (miui kernel), F1xy, Immensity, Englezos, Marisa, R4v3n, Void, NotKernel, Smurf, Candy, Supermad, Antarctica, Evira
MY SUPPORT
I got help from multiple telegram guys for this.
Shoutout to @ishtiak02, @ComicoX, @logosA, Bruce Wayne, SSS, @Noobmaster69 @Lacentix @Raaj52 @nevoness @joshuah1971 and a lot of others teaching me about ROMs and answering my numerous questions.
I am using the Indian variant K20 pro (aka Raphaelin)
You can always ask in the Our Telegram Group, or me, or in the comments. (not allowed to link telegram group I think)
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Reverting Back to PIE, moving from Android 10+ to Android 9 -Just don't- (RIN users)
Right, so Anti-Rollback protection is not implemented for k20 pro or mi 9tp. YOU CAN REVERT IF YOU WANT TO.
This is confirmed by users who have reverted, and by Xiaomi.eu website. Which I trust regarding this.
We've done experiments regarding this and have concluded this applies to raphaelin users (Indian variant devices) only. Unsure why, and how it is not affecting the mi9tp variant. (no confirmation with RCN)
However,
When moving from an Android 10 vendor to an Android 9 vendor, your SENSORS will break!
You can fix this simply by flashing your persist img (Hope you took that backup).
You can also fix your sensors by flashing someone else's persist img. BUT YOU WILL LOSE L1 FOREVER.
You can get L1 back by replacing the motherboard which can be done via your warranty at a service center, or by playing a hefty sum of money. nearly half the cost of the phone. NO OTHER WAY. Also, they open your phone, so it isn't SPLASHPROOF as much anymore.
You can also fix sensors by simply updating back to android 10 via the OTA method, which is found in your settings remember. (Unsure if this will retain your L1 though)
BOTTOM LINE, IF YOU ARE ON ANDROID 10, don't go to ANDROID 9 back.
Stuck at Fastboot Fix
Best Recovery
So regarding Recoveries. Choose the one you like the most.
I prefer the latest OrangeFox recovery cause it looks better, has a better UI, better settings, more functionality, and so forth. https://files.orangefox.tech/OrangeFox-Stable/raphael/
You can also choose TWRP if you like. Completely your choice. You can get that from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363 and choose the most recent one, and follow the instructions given there.
If you are just comfortable with TWRP. Always use Mauronofrio's, which is recognized as OFFICIAL.
To flash either recovery, just download the zip file, and simply flash it directly in your recovery like you do for a rom (no need to wipe anything) and it will auto-reboot into your desired recovery.
All credits to those who made the recoveries and those people who helped them.
Stuck in Stock Recovery when Rebooting Fix
Full credits to @ SivSomRao (telegram handle, since no XDA)
So, when I screwed my phone trying recoveries, I got stuck in FastBoot. no matter what I did, even Power + Vol Up got me to fastboot, and I had just wiped my OS, so I had nothing to boot into.
This happens when you wipe your SYSTEM and/or VENDOR partitions and choose reboot recovery, or flash an incompatible recovery.
After a lot of stressful minutes, I was scared half out of my mind. A guy named Shivsom helped me.
Basically what he made me do was
Download his file vbmeta_dv_shivsom.img that is given below in attachments.
Then copy the twrp.img file and vbmeta_dv_shivsom.img file to my adb Folder in my WindowsOS C drive.
Now, on your PC. Copy your TWRP.img file, or your OrangeFox.img (I prefer the TWRP.img file by Mauronofrio.)
Open the Command prompt in that folder
You can do this by clicking on the address bar of File Explorer and typing > cmd > then Enter
There type dir *img to confirm the file is found properly.
Now switch off your phone again.
Press and hold the power button + volume down button.
you will soon enter fastboot mode.
Now, on the new command prompt where you typed dir *img
type fastboot devices and you will get an output like
Code:
3e2f2d356 fastboot
Type the instructions
Code:
fastboot flash vbmeta vbmeta_dv_shivsom.img
Then type, (Since my twrp image file was re-named to twrp.img, if you haven't done so, do it)
Code:
fastboot flash recovery twrp.img
Then press and hold Power and Volume Up till you feel the haptic feedback see the TWRP recovery
Now, TWRP usage.
Now press and hold the power key + volume up to enter TWRP.
Once in TWRP, unlock it.
Go to MOUNT and check if MTP is enabled..... click on the "enable MTP" button.
Now copy the ofox.zip (orange fox recovery zip file) to your phone from your PC via your PC.
Now go to INSTALL tap the ofox.zip file, then flash it!
YAY now, orangefox is your Permanent Recovery.
Now go to MENU > Manage Partitions > select only data > format data > type 'yes' (This will delete everything in your Internal Storage so Caution)
Then quickly flash the latest miui vendor,
Now go to MENU > Reboot > Recovery
I was OverJoyed when this worked.
Now you can flash your Favourite ROM (normal clean flash, tutorial is given above), and then boot the ROM.
This was a nasty disaster. Glad I got through it.
Right, so I tried LR-twrp (it's in Chinese, but I can change the language to English). PitchBlack and PitchBlack-old Both broke my phone to get stuck in fastboot mode no matter what I did.
HENCE I conclude that for all Xiaomi devices, OrangeFox [OFX] is the best recovery. TWRP is suited for Samsung.
ERROR 7 fix and how to modify UpdaterScript
WHAT IS ERROR 7? :
Error 7 is an error that says the ROM you are flashing is not meant for your device.
It does so by comparing the phone's codenames.....
k20p and mi9tp have two codenames, one is RAPHAEL and the other is RAPHAELIN (the Indian variant)
Flashing the Raphael/raphaelin ROM on either device won't cause any problems at all.
feel free to flash it.
Latest orangefox 10.8 works with Raphael (global and Chinese variant) and orangefox 10.6 works with Rapahelin (Indian variant).
Alternatively, It could also be caused because you are required to flash the latest vendor, which you may have not.
So please read the one-line error message that appears above the ERROR 7 red message for more details
SOLUTION to ERROR 7:
I'd recommend flashing the orangefox 10.6 recovery as it's a lot simpler.
However if this doesn't work you can try updating script.
Right, so instead of using a different recovery, you choose to update the updater-script.
Copy the zip folder of the ROM to your PC
You can use 7zip software on your Windows PC. Download this software if you don't have it.
Double click the zip (don't extract it!!!) to open the zip.
Navigate to meta_info> com > Google > Android > you'll find update_script
Find the updater-script. Right-click on it, and choose the "EDIT" option. And edit the word Raphael to raphaelin (if you have the Indian variant of the phone)
Save and exit.
Click to expand...
Click to collapse
Creating Backups
Creating backups is always the safest thing to do, and you can do so via your recovery (OrangeFox or TWRP)
First, make sure you have everything working, nothing is broken in the ROM.
Second, go to your recovery and tap on Backup. Then Click on Create Backup, rename the file if you want to.
Third, Select all the partitions, cause why not, and let it finish creating the Backup.
Finally copy the backup file created to your PC in a safe location, and later when and 'if' you mess up, you can copy the backup file back and restore it.
You can restore by first wiping everything and formatting. (For safety) Then using the same recovery you used to create the backup, Flash the backup file. DO NO FLASH SOMEONE ELSE'S BACKUP FILES!!!!!! ONLY YOURS!!!!!!
How to Decrypt Your Phone.
So encryption is the safest thing for devices, It uses a secret code/key that only your phone knows to read data and information. However, when in Recovery, we Custom ROM enthusiasts like to have our data DECRYPTED. Now, This is because we can access our files from the recovery, flash ROMs only when decrypted, and transfer files. (If we have MTP enabled in recovery)
Somehow you've found yourself encrypted, which means all the files in your recovery are showing random letters + alphabets. and you cant transfer files to your phone via recovery anymore!
To solve this, or decrypt yourself. You will have to format your data partition (this will delete everything in your internal storage, so I hope you have a backup of your photos, vids, gifs, contacts, and so forth)
Just a bit of quick advice, If you can boot into your OS, go there, and transfer all your internal storage to your PC or laptop before formatting to avoid losing your stuff.
If you can't boot into your ROM, then you'll have to lose all your data in internal storage. No known method is known YET to help without losing the files.
Now the SOLUTION: Go to Orangefox settings > manage partitions > select data > tap on format > type 'YES' > swipe to confirm > you lose all your internal storage data contents, and you are now successfully decrypted.
OR if you are using TWRP. Go to WIPE > (right side button) FORMAT DATA > type 'YES' > you lose all your internal storage data contents, and you are now successfully decrypted.
You can now transfer files to your phone properly.
To stay decrypted and not get encrypted again, flash the DFE (Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip) from attachments below (or from the file attachment called disable_force_encrypt.zip above in the first post/comment) and then boot into your ROM, or if you are flashing a new custom ROM, follow the tutorial above(first post/comment)
If you want to stay encrypted. (I advise against this) Just don't flash the DFE file.
The newer latest updated dfe file I have attached in this comment is from https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 and all credits for the file go to him. The dfe file in the first comment/post is different and also works.
How to Recognize Which Device You Have And What Vendor Should You Use?
Global, EEA, China, Indian, Russian variant?
All credits for this list go to @joshuah1971 aka Superuser1958 on telegram.
Box Packaging
k20 pro-China: purple+black box with Chinese writing.
k20 pro-India: angled photo of the phone on top+ white box (NO NFC capability. hardware, not software), identifier: raphaelin.
mi 9t pro-Global: black box+ picture of the device on top, English text on side sticker. (model: M1903F11G)
mi 9t pro-RU: same as global but with Russian text+ orange sticker on the phone.
mi 9t pro-EEA: white box.
Software Differences
miui Global: version number will include "QFKMIXM", google dialer, and messages.
miui EEA: version number will include "QFKEUXM", google dialer, and messages.
miui China: version number will include "QFKCNXM", miui dialer, and messages.
miui India: version number will include "QFKINXM", miui dialer, and messages.
miui Russia: version number will include "QFKRUXM", miui dialer, and messages.
So check which device variant it is, and use the appropriate Vendor when flashing. (Go to ROM's Settings-> About phone-> MIUI Version [code in the brackets])
Vendor Links
So regarding Vendors. Choose the one your device needs.
Namely, The Indian Variant is called Raphaelin. So get your vendor from https://xiaomifirmwareupdater.com/vendor/raphaelin/
The Global, Europe, China, and Russian Vendors are gotten from https://xiaomifirmwareupdater.com/vendor/raphael/
What is OSS Vendor? How to switch to the F2FS file system on OSS ROMs only?
What is OSS Vendor?
So our device has 5 variants.
Xiaomi firmware website has all 5 official (firmware+vendor) zip files.
"Always flash your variants vendor."
"Xiaomi never showed us what's in them. Aka closed source"
But this is so confusing for some people. Idky.
Therefore, some devs decided to make a universal vendor that will work on all variants. Since they are making it. They can optimize it and also always know what's in it.
This universal vendor is called an OSS vendor. (Open Source Software) (It's not yet perfect though)
Some custom ROMs don't include vendor (cause OSS isn't perfect yet)
Some custom ROMs include OSS vendor (so we can observe how good it is in daily use)
It's always good to know if the rom is using OSS or if we have to flash the official.
Currently. Since OSS isn't perfect yet. If the rom doesn't include vendor (or it's a custom miui) do not flash/use OSS with it.
How to switch to F2FS File system?
• Go to the rightmost tab on orange fox recovery > manage partitions > data > change FS > tap on f2fs > change FS
• Now reboot recovery
• Now reboot recovery again
• You are now f2fs.
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Info about Persist and why it is IMPORTANT to make a Backup
To make a Backup: Go to orangefox/TWRP recovery and select the Backup option and choose the persist.img option and back that up. Make a copy on your PC for added protection.
Persist.img is "persist" which contains data that shouldn't be changed after the device shipped, for example, calibration data of chips(wifi, bt, camera, etc.), certificates, and other security-related files. Persist is having keys to decrypt several pieces of stuff, it is device-specific and you shouldn't flash persist of others, very very bad idea.
How you are losing L1? By flashing someone else persist.img file, and if you have done that you already lost it. You cannot recover it. You can still restore your own old persist back up, and if you are lucky you will get L1 back. Never play with the persist partition it has important information specific to your device.
In case you've just lost it, and you've realized it immediately (cause sensors, pop-up, L1 are broken), & haven't done anything to modify yet. Then you can try to restore the context. Try doing this in a terminal emulator like termux (case-sensitive) Termux is an app on play store (requires root):
Code:
su
restorecon -F -R /mnt/vendor/persist/
There is also this really nice guide by William Feng that explains the same but a bit better here:
Backup and restore persist on K20 Pro and 9T Pro
Pop-up Camera Stuck Open Fix
Does not work on MIUI based ROMs. The App must be used on AOSP ROMs
Due to some reason you did, your phone's pop-up camera is stuck open. Too scared to push it down, or it isn't going down.
Download the apk k20pro_motor.apk from attachments below > Install it > when you open it, the dialog box will inform you to set the current state of the camera. Then click on the button to get the pop-up camera down.
Enjoy. Complete Credits to @acervenky from https://forum.xda-developers.com/k20-pro/themes/app-xiaomi-motor-control-k20-pro-t3984181
Xiaomi.eu and other Custom MIUI ROMs
Right, so Xiaomi.eu is a forum like XDA where devs make miui like ROMs without the Mi ads and tracking and are more optimized.
The website is: https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Under there, you go to MIUI 11 ROMs > stable ROMs > download the proper ROM zip file.
The direct download link is https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv11/ or you can use: https://androidfilehost.com/?w=files&flid=300229
Now download xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip CAUTION, the word PRO has to be there. we have k20p not k20.
This works for only Raphael users, not Indian raphaelin users. (For raphaelin users use Orangefox 10.6 it will work then.)
The difference between Stable and beta is that in beta, newer features, security is implemented and tested, this has bugs, once those features are stable, it becomes a STABLE rom, then the next batch of features are added to the beta. Get STABLE though, it's better, the beta has weekly 2GB updates.
Now flashing is easy, Follow the rules in the first post/comment on how to flash a miui ROM.
Equally, you may also choose to use MortalOS which is a debloated MIUI ROM which can be found here -> https://forum.xda-developers.com/k20-pro/development/memeui-12-rc5-09-05-2020-t4097469
Issues Related to L1, restoring, and china-based miui roms
Thanks to @Raaj52 for conducting experiments to confirm and collect this information.
You must have a global/Indian variant phone which currently has widevine working properly to have a chance at restoring it later. China phones can't get L1 (or at least, I haven't learned a way to do so yet.)
What is Widevine L1 and L3?:
Right, so L1 or widevine L1 is a DRM security made by google after they noticed people use root, etc to steal copyrighted videos and movies in full HD and post them somewhere else for free. (Netflix and Amazon prime video app being affected.)
Losing this, means you get L3, and widevine L3 does not allow you to stream Full HD videos anymore, but you can stream SD low-quality videos. Which is never ideal.[
Now, EU latest stable, MortalOS uses modified china vendor with k20p L1 patch
So how do I save my L1 then? L1 Retention?:
Fortunately @Raaj52 found out that if you take a full Ofox or TWRP backup or everything from EU rom, (making a save on the PC, just in case) before moving to those aforementioned China-based ROMs is good.
When you try flashing miui EU latest stable after losing it by flashing a MIUI custom ROM based on China vendors, your phone gets L1, it shows you have L1 too, however, the apps on your phone DO NOT recognize it, technically the phone recognizes the widevine L1 as broken, and somehow considers it L3.
Here is where the Backup you made comes in handy, Clean flashing the backup completely and perfectly restores your L1. He also states that moving from China-based ROMs to AOSP ROMs like EvoX via clean flash (wiping vendor as well and flashing the proper vendor before flashing the AOSP ROM in the recovery) will also restore L1 (remember to format data partition when moving from miui to AOSP)
Now, It should be noted that cross-flashing vendors is very DANGEROUS, as this may break your Fingerprint Sensor, DTBO and proximity sensors. Therefore you must always flash the proper vendor for your phone (global, Indian, china) don't try flashing a vendor that isn't for your device. Unless if it's a custom MIUI rom as custom MIUI Roms come included with a Vendor. (wipe vendor before flashing custom miui ROM, after flash, don't touch the vendor)
Global vendor and Indian vendor are partially similar, and we have reason to believe that EU stable uses a modified vendor that works for both Raphael and Rapahelin. This is why EU ROMs works on both devices (MI 9t-pro and K20-pro)
Some Things to be Cautious about and to note:
Quoting our messages on telegram here:
The basic is, EU rom comes with vendor file so no need to flash a separate vendor for them. Flashing any vendor over the EU might break something because we don't know really which vendor they are using, assuming stables are global and betas are china.
On the other hand, AOSP comes without any vendor file, so it becomes mandatory to flash a vendor based on your device default vendor.
We flash vendors only when we flash AOSP's. In miui custom ROMs vendor is included.
Exception: If something is broken, clean wipe, flash your vendor, and then (advance wipe everything, including vendor) clean flash miui custom/AOSP.
Practically speaking, if you are moving from your stable own rom to Evox or any AOSP, no need to flash vendor since it is already having the default files but this is double confirm that the vendor is correct and it will not harm anyone. (AOSP to AOSP, not required to wipe vendor, but you can if you want to, I recommend wiping it and flashing your vendor again)
These are separate partitions and it will not override but to be on the safer side most rom devs prefer vendor and then rom.
If you flash an AOSP rom and want to move to a custom/stock miui rom make sure that you are own correct vendor. (Prior to wiping it in advance wipe) If not sure flash your vendor once again, then clean wipe and flash miui based rom.
Click to expand...
Click to collapse
How Get Back To My Stock ROM and/or Lock Bootloader?
To get back to your stock ROM, you have two methods, namely recovery zip ROM flash or fastboot ROM flash.
Get your stock rom from https://xiaomifirmwareupdater.com/archive/miui/raphael/
or if you need the Indian variant, Get your stock rom from https://xiaomifirmwareupdater.com/archive/miui/raphaelin/
Now, AND THIS IS SUPER IMPORTANT. Make sure you double-check and download the proper device's Region, codename, android version, and THE TYPE!!! (there are two types: recovery and fastboot types, choose the one you need)
Now for the recovery method, flash the recovery type .zip file the same way you flash any miui custom ROM. Check guide in first post/comment for method.
Now for the fastboot method, go to your mi-flash tool and enter fastboot on your device, and flash the rom there. (Now, I personally never did this method, so I can't guide the exact steps for this method, sorry)
LOCKING BOOTLOADER: You must first be using the proper stock vendor, stock rom via fastboot, and not have magisk or any MODs running on your phone. If you violate these, you WILL Hard brick your device. It is because of this I VERY STRONGLY advise against locking your bootloader for any reason whatsoever. JUST DON'T!!!
However, you can you the mi-flash tool (safest) or the debloater tool to lock your bootloader if you definitely must do it.
• Download MiFlash tool from MiFlashTool Website . The latest is the top left, marked with a NEW tag.
extract the file, and run the program "XiaoMiFlash.exe"
• Download the stock fastboot miui rom from Fastboot Website and extract the file (if its a .tgz or .tar extract again) you'll end up with a folder with one folder and 11 files (images, flash_all.bat.......misc.txt)
• Now in whatever rom you are on, go to developer settings, enable "OEM Unlocking" and "USB Debugging"
• Now boot into fastboot mode
• Connect your device to your PC
• Now in MiFlash tool, at the bottom, choose Clean all (and dont LOCK IT, I repeat do not choose to lock)
• Then on the top click on the "select" button and navigate to the folder with the 11 files & 1 folder and choose that folder.
• Click on the "Refresh" button and check if your device is shown (indicated by random numbers/letters)
• Now (recheck if its only CLEAN ALL only, and NOT lock or anything else)
• Now flash
• Wait 420s approx, or more, or less.
• It'll finish with an error and the message will say
• "error: Not catch checkpoint (\$fastboot -s . ' lock),flash is not done"
• This is cause it did not lock your bootloader. THIS IS GOOD.
• Now wait 5-10mins while miui 12.5 loads up/boots, it takes a while.
• Now, close MiFlash program, its done, no more needed.
• Now that's done, use miui 12.5 if you want, or go to recovery
• You'll see you have stock recovery now
• So go to fastboot mode, (phone connected to PC)
and flash the ofox recovery.img to get ofox recovery. via the cmd command like usual.
• Then go to recovery ofox.
• Go to wipe > format > type yes > format data to decrypt
• Reboot to recovery
• Now copy your ofox zip file to phone,
• Now flash that file to make OFOX permanent
• Now reboot to recovery again.
Click to expand...
Click to collapse
Latest MIUI-CN builds and miui custom ROMs soft bricking your device? (Mostly Raphaelin users)
Right, so this is a Xiaomi thing, which happens to many Xiaomi-based devices. It was later observed by a member on telegram that this usually happens to devices without NFC. In our case of Raphael - This would be Indian devices or Raphaelin devices.
I personally haven't experienced this, so I can't give a personal experienced-based guide on fixing this. However, another user on telegram @rockyanexpert solved his problem and shared this guide given below with me.
[
System has been destroyed. What I did:
1. Panicked a little
2. Started my lappy
3. MiUnlock Tool was pre-installed v3.xx
4. It took almost 10 minutes to show the login prompt. The connected device in fastboot. It failed to recognize the device. Started MiFlash. It did recognize the device.
5. Downloaded the latest MiUnlock. It too failed to recognize the device.
6. Downloaded XiaoMiTool v2
7. It detected the device fastboot serial correctly
8. Manually selected model Raphael.
9. Started with My device is bricked
10. It detected a locked bootloader. Opened its own version of Unlock Tool. Logged in to binded Mi Account. (My Mi Account n the binded one is the same)
11. Unlocked.
12. Tool went on ahead with waiting for the device to boot in fastboot mode.
13. I removed the device n forced boot in recovery mode. Ofox showed "Updating" n booted in orange ofox screen.
14. Rebooted system
15. Newly flashed Eu 21.2.3 started initial setup.
No data lost.
Click to expand...
Click to collapse
By these same people, they made a guide here: System destroyed issues
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
nice work @Sandeeep Kiran, keep it up.
Just got my 12/512 yesterday but my wait time is 15days (it said 360hours).:fingers-crossed:
Hi, probably today i wil try to flash xiaomi.eu rom but i have some doubt, why you are saying that wipe system is required for flash a custom rom? i have read in several thread that this wipe is not rquired
salva93 said:
Hi, probably today i wil try to flash xiaomi.eu rom but i have some doubt, why you are saying that wipe system is required for flash a custom rom? i have read in several thread that this wipe is not rquired
Click to expand...
Click to collapse
Right, so I actually had the same doubt for a while. Noone in the group seemed to properly answer this.
Some said you should, some said you shouldn't.
So I talked to the devs of note 2 (my old phone, most members now have xiaomi phones)
They all said system is required to be wiped.
However before they answered. I can already listened to our group members and figured, I will not wipe system and flash my ROM as it is.
When I did this. I noticed the recovery throwing an error from magisk. That magisk modules aren't linked to anything, and this will/may cause problems.
After reading that message I realised. System wipes everything. And if you are dirty flashing/ clean flash with no mods. System is not required to be wiped.
However most people use magisk modules. Root changes, 75hz mods and so forth. This is when system is required to be wiped.
Now. As a general rule. It is good to wipe system. No harm is being done in wiping it. Hence I reccomend it.
Although, if anyone does have a particular reason that system shouldn't be wiped. I'd love to hear the explanation of it. But this is what I know of after research. I'm still no expert in everything.
Sandeeep Kiran said:
Right, so I actually had the same doubt for a while. Noone in the group seemed to properly answer this.
Some said you should, some said you shouldn't.
So I talked to the devs of note 2 (my old phone, most members now have xiaomi phones)
They all said system is required to be wiped.
However before they answered. I can already listened to our group members and figured, I will not wipe system and flash my ROM as it is.
When I did this. I noticed the recovery throwing an error from magisk. That magisk modules aren't linked to anything, and this will/may cause problems.
After reading that message I realised. System wipes everything. And if you are dirty flashing/ clean flash with no mods. System is not required to be wiped.
However most people use magisk modules. Root changes, 75hz mods and so forth. This is when system is required to be wiped.
Now. As a general rule. It is good to wipe system. No harm is being done in wiping it. Hence I reccomend it.
Although, if anyone does have a particular reason that system shouldn't be wiped. I'd love to hear the explanation of it. But this is what I know of after research. I'm still no expert in everything.
Click to expand...
Click to collapse
Many thanks for your answer, so for now i will not risk and i will follow instructions on xioami.eu website, i'm in clean situation so i should not have any issue
bump
Good guide. Have a bump.
But till this day (Jan 6, 2020), no custom roms are stable or bugfree enough for the exception of xiaomi.eu
Default MIUIrom just works. But I hope in the near future we get to see bugfree roms and I will certainly try it! I have always used PE on my previous phones.
Cheers!!!!
bumpity bump
Nice infomation dude
whatsapp dark
root user used
Swift Installer - Themes & color engine
just share my opinion
Good guide, thx.
Guys, one question, i have to mount System/Vendor and other to wipe, or can i simple wipe without mount?
bigatim said:
Good guide, thx.
Guys, one question, i have to mount System/Vendor and other to wipe, or can i simple wipe without mount?
Click to expand...
Click to collapse
Nah, Mount is to send/transfer files.
Since you arent doing that, you dont have to mount system or vendor, but mount your internal storage though.
and for the L1 flash, mount vendor for that only, soon a magisk mod will be available for it.
So when do we need to flash disable force encryption?
If I am correct, you can simply format data and get rid of your encryption. In this case you do not need to flash disable force encryption. Also, can't you just decrypt before starting the flashing process?
I've tried RevOS and I came back to mmx.
And widevine L1 is not break. Everything gone fine.
Krullendhaar said:
So when do we need to flash disable force encryption?
If I am correct, you can simply format data and get rid of your encryption. In this case, you do not need to flash disable force encryption. Also, can't you just decrypt before starting the flashing process?
Click to expand...
Click to collapse
DFE is to remove encryption.
when you format data partition, you remove the dfe. You do this when moving from AOSP to miui or vice versa.
you can't decrypt before flashing cause there isn't a system or any data to decrypt. After you add a ROM or data, you can decrypt that.
yes, the format will get rid of your encryption. (but you also lose all your data) so flashing dfe helps retain your data. If you're scared someone will go to your recovery and steal data, add an orangefox password in its settings. Alternatively, you also have the dm-verity settings in orangefox settings you can enable. But redundant as its all included together in the dfe file I've attached.
Sandeeep Kiran said:
L3 Fix, Getting L1 after getting L3 for Global and Indian Users.
@Raaj52 Found a solution to fix L3 and get L1 again.
This fix however only works on Global and Indian vendors. (i.e mi 9t pro and k20p Indian variant)
No such solution has been found for china phones, using china vendor, DO NOT CROSS FLASH VENDORS!! it will cause a bootloop.
This patch was made for the latest EU beta, miroom. We hope it also works for future versions, and previous versions, but we are unsure. You can experiment and inform us though in the comments below.
Always have a proper fully working backup of everything rom. As caution. It's always good to take precautions.
Pop-up Camera Stuck Open Fix
Does not work on MIUI based ROMs. The App must be used on AOSP ROMs
Due to some reason you did, your phone's pop-up camera is stuck open. Too scared to push it down, or it isn't going down.
Download the apk k20pro_motor.apk from attachments below > Install it > when you open it, the dialog box will inform you to set the current state of the camera. Then click on the button to get the pop-up camera down.
Enjoy. Complete Credits to @acervenky from https://forum.xda-developers.com/k20-pro/themes/app-xiaomi-motor-control-k20-pro-t3984181
~FINISH
~Do Comment and Thank, it'll bump this guide to be noticed more, so others can find this guide and get help as well
Click to expand...
Click to collapse
hi, I followed the instructions. Netflix black screen problem still continues.What should I do ?
masik x 9.4 - black screen problem - security patch January
mi room 20.1.16 it works fine - security patch is still 2019.12.01
please masik x 9.4 fixed black screen problem.
thank you.
uurturk said:
hi, I followed the instructions. Netflix black screen problem still continues.What should I do ?
masik x 9.4 - black screen problem - security patch January
mi room 20.1.16 it works fine - security patch is still 2019.12.01
please masik x 9.4 fixed black screen problem.
thank you.
Click to expand...
Click to collapse
The patch was intended to work on security patch Jan 20th and above, which maisk is not yet updated too.
(however, @ QasimXAli in the official telegram group did manage to make it work. you can tag and ask him there.)
Currently, the person who made the mod is still working to converting it to a perfect magisk module so it's easier to flash. Also, he is waiting for the next stable update to check whether the magisk module patch will continue to work.
We just gotta wait a bit longer.
ghaf85 said:
Nice infomation dude
whatsapp dark
root user used
Swift Installer - Themes & color engine
just share my opinion
Click to expand...
Click to collapse
Thanks.
Under add-ons, I added how to get WhatsApp dark (currently in WhatsApp official beta, which will roll out to stable in three months.)
For root, everyone just uses magisk latest stable.
and Solid Explorer or Mi-explorer
I like swift, liv and flux too. but those are straight-forward. I can add them to "add-ons" if you like.
Related
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
4: Custom Roms
What are custom roms? Simply put they are modified versions of Android containing advanced tweaks, stability, and performance. Custom Roms are device specific for the most part. In other words, a Rom for the Moto G6 Plus will not work on a Moto G6 or G6 Play. There are a few exceptions to this rule, but they do not apply to the Moto G6 family so I won’t get into detail about it here. As of Android 8.0(Codename Oreo), Google has redesigned the framework of Android with a system called Project Treble. I will get in to that more later on in the Generic System Image(GSI) section of this guide, but to quickly summarize, it means Custom Roms that do not have to be built to be device specific. For a more detailed analysis of custom roms you can read the information in the spoiler tags below.
Spoiler
Android is a free open source software(FoSS)! This means anyone, anywhere in the world can help contribute to Android. This allows developers to add, remove, or modify the source code, and even publish there modified source code for others to use. The most popular example of this is called LineageOS(formerly CyanogenMod(CM)). At one point it was reported over 50 Million people ran CM! Why did 50+ million people decide to ditch the standard Android software provided by the phone’s manufacturer? There are a number of reasons such as :
Bloatware: Stock firmware is commonly infested with applications installed by your carrier to generate more revenue. Rom’s do not have this problem.
Updates: Android updates typically require approval by the carriers as they want certain functions disabled (tethering for example), to make you pay extra for this feature. Since carriers have they final say when updates are pushed out to devices, and wanted bloatware installed, etc, users were lucky to receive security updates. Users were even luckier to see a version update (Oreo to Pie for example). Rom’s do not rely on a carrier to be updated.
Stability: Since users were lucky to receive updates, you were forced to live with bugs for a long periods of time. Maybe even the entire life of the device. Since Custom Roms receive regular updates, this means bugs were fixed in a timely manner.
Performance: Custom roms are usually more optimized for the hardware they run on then stock roms. They may overclock your phone’s processor(CPU) to make it function faster then it was originally designed.
There are other various reasons but you get the idea.
For a list of features added to LineageOS (read this). Other roms may or may not include these features and more!
So how do you install a custom rom? Currently Moto G6 Plus users have access to LineageOS 15.1 (Based on Android 8.1). LineageOS 16(Android 9 Pie based) is in the development stage. There is no time line on a release just yet so not ask for an ETA! Let’s get started!
Downloads:
++Download these files to your PC.
*ADB and Fastboot Installer for Windows - (Download) - When prompted to install a driver type the number 0 and hit enter. This will install the latest version of adb and fastboot where it is system-wide. This eliminates the need for adb.exe or fastboot.exe to be in the same folder as the files you will be working with. NOTE: Windows will flag this as a virus! The installer is open source and made by a Moderator here on XDA. It is a False Positive. You can view a VirusTotal report (HERE). 26 out of 67 virus scanners report it as a virus. If your Anti-Virus is one of the ones that flag it as a virus, I would suggest you explore other Anti-Virus software, but that’s not what this guide is about.
* TWRP - (Download) - This is a modified Recovery Software allowing you to flash files that will allow you to fipe your device and install custom roms and other various things. Thanks to XDA Member @erfanoabdi who has ported it to our device.
++Download these files to your phone’s sdcard(Do not place them on the internal storage)
*Magisk - (Download) - Download the Stable version here. While not required, I do suggest you download the Latest Uninstaller and Latest Magisk Manager as well.
*copy-partitions-AB.zip - (Download) – Our phone is what’s known as an A/B device. This translates into slot_a and slot_b. The means we have a system_a partition and a system_b partition for example. By default some of these _b partitions are empty. This will populate these empty partitions with a copy of the data on the respective _a partition to help prevent you from bricking your device!
*LineageOS 15.1 [Unofficial] – You have 2 options:
lineage-15.1-20180811-UNOFFICIAL-evert.zip – This version was built on August 08 2018 by @erfanoabdi and @rahulsnair who are the real developers for the Moto G6 Plus.
lineage-15.1-20181003-UNOFFICIAL-evert.zip – This version was built on October 03 2018 by me Xplorer4x4. This version uses the same device specific binaries and source code @erfanoabdi and @rahulsnair used, but uses updated LineageOS source code. This is a bug fix release and does not include additional features.
Gapps – These are Google Apps like YouTube, PlayStore, Gmail, and more. -Again you have two options:
-OpenGapps – (Download) – Personally I prefer OpenGapps as you can customize which apps you want to install. The only downfall is that when you flash an update to LOS, you will have to flash Gapps again. In the Platform Column choose ARM64, in the Android Column choose 8.1, and then you can choose any Variant. I personally use the Nano Package and manually install the Gapps I want form the Play Store.
-MindTheGapps – (Download) – What you get is what you get. You don’t get to choose which gapps are installed, but if you flash an LOS update in the future, you won’t have to flash them again.
Please keep reading for detailed instructions on how to install LineageOS 15.1.
WARNING: This will wipe out all apps and data stored on your phone! It will not wipe your SD Card. Any apps purchased/installed from the Play Store can be restored using WiFi or LTE when you are done installing a ROM.
Known Bugs: Everything works except making calls with Bluetooth devices.
Instructions:
*On the device:
4A: Open the settings app and navigate it in this order: System -> About.
4B: On the About screen scroll down to Build Number and tap on it 5 times. You will see a notification at the bottom of the screen that says “Developer Options Enabled.”
4C: Tap the back button, and open Developer Options.
4D: Find “Android Debugging” and enable it.
*On your PC:
+Windows:
4E: Using Windows Explorer, navigate to the location of twrp-3.2.3-42-evert.img. Hold the Shift Key on your Keyboard. While holding Shift, Right Click in the window(not on the file). Depending on your windows version you should see either "Open PowerShell Window here" or "Open Command Window here." Select which ever one applies. You will see a black and white screen or a blue and white screen. The steps are the same no matter which screen you see.
copy-partitions-AB.zip
+Linux:
4E: Using your favorite terminal interface, navigate to the location of twrp-3.2.3-42-evert.img.
+Linux + MAC + Windows:
4F: Simply type(or copy and paste) the following command:
Code:
fastboot boot twrp-3.2.3-42-evert.img
*On your device(it should be booted in to TWRP at this point):
Create a TWRP Backup: Tap Backup -> Select Storage -> Micro SD Card - > OK. You will see a section that says "Select Partitions to Backup." Make sure to select all of these boxes. At the bottom of the screen Swipe the Blue Button where it says “Swipe to Backup.” When this is done, tap the Home button.
4G: Now tap on "Select Storage," select Micro SD Card, and tap OK.
4H: Navigate to the location of the copy-partitions-AB.zip and tap on the zip.
4I: Swipe the blue arrows button next to “Swipe to confirm Flash.”
4J: Tap the home button.
4K: Tap Wipe → Format Data(Do not tap Advanced Wipe, or Swipe for Factory Reset).
4L: Type yes
4M: Tap the blue check-mark in the bottom right corner.
4N: Tap Home button.
4O: Tap Install->Select Storage→Micro SD Card→OK
4P: Tap lineage-15.1-20180811-UNOFFICIAL-evert.zip or lineage-15.1-20181003-UNOFFICIAL-evert.zip
4Q: Swipe to install.
4R: When flashing is done, tape the home button.
4S: Tap Wipe→Format Data→Type yes→Tap Blue Check Mark at bottom right corner.
4T: Tape Home button when done.
4U: Tap Reboot → System
Congratulations, you have installed Lineage OS but we are not done yet! Let the device boot until you see the LineageOS Welcome screen. Note that the first time booting up a custom rom will take longer then a typical reboot. It should take no more than 5 minuets to complete!
Once on the LineageOS Welcome Screen, you can complete the setup or reboot back to your bootloader. Once the device powers off, hold the Power Button and Volume Down button until the bootloader displays on the phone screen.
4V: Boot TWRP again:
Code:
fastboot boot twrp-3.2.3-42-evert.img
4X: Tap install and navigate to the directory where you placed your gapps.zip and Magisk.zip.
4Y: Tap the Gapps.zip and choose add More zips.
4Z: Tap the Magisk.zip and Swipe to install.
We need to Wipe->Format Data one last time or else your Gapps will give you multiple errors when you boot LOS again. Once you have Formated Data, you can now reboot to system and enjoy LOS!
Small error?
Thanks for the effort that's gone into this post.
Just a quick editing note: the link to download Magisk (https://androidfilehost.com/?fid=5862345805528069013) seems to point to twrp-.2.1-37-evert.img rather than Magisk.
Detailed excellent guide. Almost everything covered.
Btw what advantage this twrp 42 holds over the one from twrp site?
JaggedPill said:
Detailed excellent guide. Almost everything covered.
Btw what advantage this twrp 42 holds over the one from twrp site?
Click to expand...
Click to collapse
Use the version from twrp website. I haven't had a chance to update the guide. Encryption is supposed to work on official twrp but I think myself and other testers verified encryption is not working right now.
Sent from my Phh-Treble vanilla using Tapatalk
What are the steps to compile for this device? Can you provide that information please? I have compiled for others, but this one is new to me and I think you use some configuration or additional files.
@Xplorer4x4 can you provide me your local_manifest file?
Does anyone know if we have any microg rom options for the Moto G6 plus?
Followed your instructions, after step 4U the device stays completely dark, no bootloader, no volume down + power key helps, nothing.
tmr2020 said:
Followed your instructions, after step 4U the device stays completely dark, no bootloader, no volume down + power key helps, nothing.
Click to expand...
Click to collapse
Try one of the following options:
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/
The second one is the official Rescue Tool from Lenovo. Read the user's guide first. I don't know why your phone is dead, but this might help you.
WoKoschekk said:
Try one of the following options:
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/
The second one is the official Rescue Tool from Lenovo. Read the user's guide first. I don't know why your phone is dead, but this might help you.
Click to expand...
Click to collapse
Thanks, I discovered the first thread after stopping banging my head against the wall. It actually worked. I can now use fastboot and adb etc. again. AFAIK, it is not possible to flash twrp recovery, it has to be booted on demand with adb/fastboot? I tried flashing lineage recovery instead, maybe I should not have done that, idk. Anyways it still booted to fastboot after that. I also seem to be confused by the a/b scheme.
Anyways I started all over with the copy-partitions-a-b (as I had a completely broken system, I cant imagine syncing the gargabe between a and b would help much?) and flashing lineage 17.1 again. It now boots to lineage. I rebooted to fastboot/twrp again to sideload opengapps (are they a/b compatible yet?!).
And how do I get a working recovery system again? I can't flash twrp? Can I flash lineage-recovery? Or something else?
And what does "active a" in twrp actually mean? That it will flash to "b"? Or that it will flash to "a"?
---------- Post added at 07:50 PM ---------- Previous post was at 07:34 PM ----------
I has just booted once to LineageOS, after trying to install Gapps, it's stuck in a bootloop. Going to twrp and selecting either A or B and then clicking on reboot, warns "no os installed"!
What am I doing wrong?
What am I doing wrong?
Click to expand...
Click to collapse
Get informations about A/B partitions (seamless updates) and how it works.
You must flash the GApps before our first boot into system.
bom Diagood morning i am stuck in the boot animation of Lineage 18.1 it does not install at all but other custom good piexel base PE style installs normal what can i do wrong ??
Rafinha863 said:
bom Diagood morning i am stuck in the boot animation of Lineage 18.1 it does not install at all but other custom good piexel base PE style installs normal what can i do wrong ??
Click to expand...
Click to collapse
Did you follow the install instructions on the official LineageOS web page?
WoKoschekk said:
Você seguiu as instruções de instalação na página oficial do LineageOS?
Click to expand...
Click to collapse
sim eu seguiyes I followed everything risks the process by adb sideload and completed but when starting the ROM it does not boot is only in the boot animations of Lineage
Rafinha863 said:
sim eu seguiyes I followed everything risks the process by adb sideload and completed but when starting the ROM it does not boot is only in the boot animations of Lineage
Click to expand...
Click to collapse
if it's an endless bootanimation then try to force reboot the device by holding the power button for 10-15 seconds.
WoKoschekk said:
se para uma animação de inicialização sem fim, tente forçar a reinicialização do dispositivo de bloqueio o botão liga / desliga por 10-15 segundos.
Click to expand...
Click to collapse
I already did this procedure and it didn't work either
Rafinha863 said:
I already did this procedure and it didn't work either
Click to expand...
Click to collapse
Latest stock ROM installed? Did you format (not only wipe!) /data?
WoKoschekk said:
Mais recente ROM de estoque instalada? Você formatou (não apenas limpe!) / Data?
Click to expand...
Click to collapse
yes I did data format every installation process correct but it is in bootanimation
WoKoschekk said:
Mais recente ROM de estoque instalada? Você formatou (não apenas limpe!) / Data?
Click to expand...
Click to collapse
Não te entendiI did not understand you are telling me to just format the date and not clean the system I noticed that in the function mount on the ceiling the actions of system vendor persist are all unchecked is this correct?
Rafinha863 said:
Não te entendiI did not understand you are telling me to just format the date and not clean the system I noticed that in the function mount on the ceiling the actions of system vendor persist are all unchecked is this correct?
Click to expand...
Click to collapse
Your internal storage is devided into several partitions e.g. /system, /vendor, /boot and /(user)data. The option format data is the same as the option factory reset. Both of them delete all your apps, settings and so on.
Your OS and all related Moto stuff is stored on /system (OS) and /vendor (Moto). By default they are unmounted, but could be mounted as r/w. If you delete them, you won't boot because no OS is installed.
Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here.
Boot with AB only. Seems this was due to some ROM compatibility issue and the FW of Samsung that time. Any Treble based ROM, based on our partition structure works now.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Thanks for your guide. I appreciate your persistence.
We must try relentlessly to get working stuff!
Incredible work testing GSI's, I might flash myself to test out
Snapshots!
Attaching few snapshots for the build and successful flash.
Akhil99 said:
Thanks for your guide. I appreciate your persistence.
We must try relentlessly to get working stuff!
Incredible work testing GSI's, I might flash myself to test out
Click to expand...
Click to collapse
Thanks mate. This guide should work on M30 all variants, ideally.
I will post once PHH gives an update and see how it goes with Dirty Flash or if I need to flash it again. Hopefully dirty flash should work.
vdbhb59 said:
Thanks mate. This guide should work on M30 all variants, ideally.
I will post once PHH gives an update and see how it goes with Dirty Flash or if I need to flash it again. Hopefully dirty flash should work.
Click to expand...
Click to collapse
Which gsi did you flash? I will flash the same for first boot for safety...
And also make a telegram group for samsung m30, so others can post their problems.
nareshfree said:
Which gsi did you flash? I will flash the same for first boot for safety...
And also make a telegram group for samsung m30, so others can post their problems.
Click to expand...
Click to collapse
I flashed the GSI by PHH (phhusson), the FLOSS one.
https://github.com/phhusson/treble_experimentations/releases
There are few groups on TG. I am no longer on TG (left a week/2 ago). I am available here for anything.
System partition or System image?
veekay said:
System partition or System image?
Click to expand...
Click to collapse
Flash as /system image.. By system partition I meant the /system portion of the OS.
Any chance you would be able to take a screenshot of the partition list that is shown after you select the image? I am trying to do this on another Samsung device and am wondering if the issue comes down to the TWRP options shown as I don't have just System - only System Image
veekay said:
Any chance you would be able to take a screenshot of the partition list that is shown after you select the image? I am trying to do this on another Samsung device and am wondering if the issue comes down to the TWRP options shown as I don't have just System - only System Image
Click to expand...
Click to collapse
It is the system image. Dont have Samsung turned on or fully setup to give snap.
There you go.. /system image..
One suggestion. Even with GSI do not try to flash any experimental zips from say Android 9 on Android 10. I just landed on bootloop and had to reflash system Magisk and DM again.
I switched to Havoc. Much more stable and has loads of features..
Couple of Havoc snaps..
vdbhb59 said:
Couple of Havoc snaps..
Click to expand...
Click to collapse
How is your use at hovac ?? Is the lock screen working?
Can you make and receive calls normally?
MiyamuraNEET said:
How is your use at hovac ?? Is the lock screen working?
Can you make and receive calls normally?
Click to expand...
Click to collapse
Nope for both. Calls only on 2G, not even 3G. Audio on speakers is not working. SMS on LTE does not work, but works only on 3G or 2G.
If anything is moved manually to /priv-app or /etc it bootloops on the next reboot.
vdbhb59 said:
Nope for both. Calls only on 2G, not even 3G. Audio on speakers is not working. SMS on LTE does not work, but works only on 3G or 2G.
If anything is moved manually to /priv-app or /etc it bootloops on the next reboot.
Click to expand...
Click to collapse
This is a matter of time soon customs will appear!
MiyamuraNEET said:
This is a matter of time soon customs will appear!
Click to expand...
Click to collapse
True. Just waiting for it. Will see if I can get to help Akhil, Sahil and Aditya.
Flashing the GAPPS build works only until one reboot after which the phone goes into boot loop. also, VOLTE does not work.
thvardhan said:
Flashing the GAPPS build works only until one reboot after which the phone goes into boot loop. also, VOLTE does not work.
Click to expand...
Click to collapse
I do not use gaaps, so not sure, but it does stick around on several reboots as well. Only time it will go to bootloop if you try to manually place any file within "/system/app" and "/system/priv-app" folders. Somehow, it ticks boot and does not start beyond Android logo.
could you please tell which phh to download exactly
vdbhb59 said:
Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here. Boot with AB only.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Click to expand...
Click to collapse
It would be very kind of you if yould could tell me exactly which phh to download from github?
---------- Post added at 09:34 AM ---------- Previous post was at 08:46 AM ----------
vdbhb59 said:
Hi All,
Today I successfully flashed the PHH GSI on my Samsung M305F. Sharing the guide on how to?..
Prerequisites:
1. Android 10 May Security Patch (June release). Get it here. Be on stock firmware, non rooted.
2. PHH/Havoc or any GSI you wish to flash. I suggest PHH one as it is regularly updated and has inbuilt FLOSS/FOSS apps build too, other than Vanila, GApps build too. Choose the GSI from the list here. Boot with AB only.
3. PHH Magisk (this is a modified Magisk for GSI images, and should work on any GSI). Please do not use any other Magisk or SuperSU for initial flash, else you will not boot. Trust me, I tried several time, and does not boot. Get the PHH Magisk here or here.
4. DM-Verity file. Download from here, here or check here for further reading.
5. TWRP for Android 10 for Samsung M30. Get it here or here.
6. USB-OTG. See #6 below for reason.
Instructions:
1. Flash Stock ROM from #1 above.
2. Ensure that you are connected to internet/mobile data so that OEM unlock option is visible. If not connected to Internet, OEM unlock will not show, as it needs to check over Samsung servers on start.
3. Wait for 15 minutes for KG state to check servers (this time frame can be less or more depending on your internet connection). Mine was 3-4 minutes. This is important for the next steps.
4. Reboot to download mode and flash the TWRP from ODIN, by selecting it in AP (auto-reboot should be unchecked). The full steps are available in the XDA post linked in #5 above.
5. Reboot to TWRP, and format data (not wipe). Reboot to TWRP again. This step is important for recovery to not get overridden by the stock recovery.
6. MTP on recovery and upon boot somehow still does not work on Linux or Windows, so copy your relevant files on USB-OTG. Akhil and Sahil are working on the recovery part of it. For normal system, that is an issue with all GSI's somehow.
7. Wipe /data, /cache and /internal storage, and then mount /data and /usb-otg.
8. Ensure /system and /vendor are not mounted, and only /data and /usb-otg are mounted. You can copy the files over from OTG to internal sd card, or directly work from OTG itself. Up to you.
9. Do not wipe anything else, and just flash as follows:
a. Flash the GSI Image (.img) file in /system partition from recovery.
b. Flash the Magisk PHH file given in the link above.
c. Flash the DM-Verity file from the link above.
10. Wipe dalvik/cache. Reboot to system.
Boot time should not be much, if you follow the steps properly. Mine took 3-4 minutes.
Post boot:
1. Inbuilt SuperSU will give binary error/update prompt. Not needed, and ignore it.
2. Once you have setup Magisk, you can then upgrade both manager and magisk itself. It will not bootloop. But for initial flashing use the Magisk given in the link, and no other, else you will bootloop.
3. MTP does not work. VoLTE, I am yet to check, so if someone can confirm that, it will be good.
4. USB-OTG works. So, you will have to use it for any file copying etc. Please format USB-OTG once from the phone, as it will otherwise give USB Error and your time would be wasted. So format from mobile first and then copy anything to USB.
5. I did not find any bugs till now. Not sure, if any present or not, as I booted today only, after 8 failed weeks.
VoLTE Fix: https://github.com/KhushrajRathod/VoLTE-Fix/
Credits:
1. Sahil_Sonar and Akhil99 for the working TWRP (finally)
2. MiyamuraNEET for helping me with flashing GSI, and giving me the link for correct DM-Verity. No other DM-Verity works.
3. phhusson for making a working GSI (especially FOSS/FLOSS one).
4. Samsung for making a BLOAT FILLED OS.
5. turbolukex5 for PHH Magisk.
6. vdbhb59 (of-course me) for not giving up, and for keeping on trying for the last 8-9 weeks..
Let me know if anything is missed..
Click to expand...
Click to collapse
when I am installing twrp and then formating data and the rebooting to system it is causing bootloop.Please help
How I can install twrp and flash gsi rom on Doogee N20?
I found this but I'm doesnt know Russian: pda.ru/forum/index.php?showtopic=955032&st=1220#entry89836105 (I cant post URL because I'm new user, so I delete the "4" from "4pda")
Sorry for my bad English.
צבי זלצברג said:
How I can install twrp and flash gsi rom on Doogee N20?
I found this but I'm doesnt know Russian: pda.ru/forum/index.php?showtopic=955032&st=1220#entry89836105 (I cant post URL because I'm new user, so I delete the "4" from "4pda")
Click to expand...
Click to collapse
That's the Google translation:
A little instruction on how to get RooT. And so, everything that you do, as always, is at your own peril and risk! All data is erased when unlocked! Make BACKUP !!! Is always!!!! I. Unlocking Boorloder-a (required for flashing the phone and everything connected with it): 1. Go to settings -> system -> About phone -> Build number (7 clicks) (Congratulations !!!! You are a developer!) < - About phone -> For developers: Enable USB debugging and OEM unlocking. 2. We connect the phone to the computer and install the ADB usb driver (on the Internet), a connection request should appear on the phone, you need to allow it. 3. Extract files from the N20_utils.rar archive (10.87 MB) (preferably not very far, the root of the disk or the created folder N20 will be there). Go to the Unlocked Bootloader folder and run the bat file, the phone will reboot and display the request "unlock? Yes / no" rocker up - yes / rocker down - no. Naturally, you need to press the volume up, otherwise there were so many actions)) 4. Congratulations! Now, with each reboot, you will have an Orange state (5-second inscription), and the ability to do whatever you want with your phone. II. We sew! 1. For the lazy (who value their time). Download the SP Flash tool (Internet), from the N20_utils.rar archive (10.87 MB) select MT6763_Android_scatter and boot_magisk_20 files for the boot partition, lk_pached for lk, etc. you can even twrp instead of native recovery. Turn off the phone, connect it to the computer and click Download in the SP Flash programs. After the OK circle appears, disconnect and reconnect the cable (easier than a forced reboot). We turn on the phone and put the magisk manager (internet). Congratulations!!! You have a root and no Orange State label! 2. Who wants more and himself: phone to computer -> go to the Unlocked Bootloader folder -> run CMD -> write "fastboot flash recovery" put a space and move the TWRP file with the mouse to the window (fast path to the file) and press ENTER -> reboot the phone to fastboot. Congratulations!!! you have TWRP. Boot into TWRP, skip the encrypted DATE message, go to formatting and format the DATE. Go to mount and connect MTP. A phone will appear on my computer, we drop the files DisableForceEncryption_Treble (disable date encryption), orange_state_disabler_v0.3 (remove orange_state) and magisk.zip (internet) into the memory section. In TWRP, click install all this and rejoice! 3. Who has nothing to do at all: go to the forum thread Development and porting of GSI firmware (Post bullik01 # 71222655) and try what catches your eye. Not all are loaded, but .... (although we do not seem to have an A / B structure, but only "arm64 A / B" were launched) PS: look for additional information here on the forum and for brotherly devices UMiDIGI A5 Pro - Firmware ( Post Xakep1993 # 86772223) Attached files recovery-TWRP_3.3-20191015-1714.img (22.81 MB) DisableForceEncryption_Treble.zip (4.24 MB)
jwoegerbauer said:
That's the Google translation:
A little instruction on how to get RooT. And so, everything that you do, as always, is at your own peril and risk! All data is erased when unlocked! Make BACKUP !!! Is always!!!! I. Unlocking Boorloder-a (required for flashing the phone and everything connected with it): 1. Go to settings -> system -> About phone -> Build number (7 clicks) (Congratulations !!!! You are a developer!) < - About phone -> For developers: Enable USB debugging and OEM unlocking. 2. We connect the phone to the computer and install the ADB usb driver (on the Internet), a connection request should appear on the phone, you need to allow it. 3. Extract files from the N20_utils.rar archive (10.87 MB) (preferably not very far, the root of the disk or the created folder N20 will be there). Go to the Unlocked Bootloader folder and run the bat file, the phone will reboot and display the request "unlock? Yes / no" rocker up - yes / rocker down - no. Naturally, you need to press the volume up, otherwise there were so many actions)) 4. Congratulations! Now, with each reboot, you will have an Orange state (5-second inscription), and the ability to do whatever you want with your phone. II. We sew! 1. For the lazy (who value their time). Download the SP Flash tool (Internet), from the N20_utils.rar archive (10.87 MB) select MT6763_Android_scatter and boot_magisk_20 files for the boot partition, lk_pached for lk, etc. you can even twrp instead of native recovery. Turn off the phone, connect it to the computer and click Download in the SP Flash programs. After the OK circle appears, disconnect and reconnect the cable (easier than a forced reboot). We turn on the phone and put the magisk manager (internet). Congratulations!!! You have a root and no Orange State label! 2. Who wants more and himself: phone to computer -> go to the Unlocked Bootloader folder -> run CMD -> write "fastboot flash recovery" put a space and move the TWRP file with the mouse to the window (fast path to the file) and press ENTER -> reboot the phone to fastboot. Congratulations!!! you have TWRP. Boot into TWRP, skip the encrypted DATE message, go to formatting and format the DATE. Go to mount and connect MTP. A phone will appear on my computer, we drop the files DisableForceEncryption_Treble (disable date encryption), orange_state_disabler_v0.3 (remove orange_state) and magisk.zip (internet) into the memory section. In TWRP, click install all this and rejoice! 3. Who has nothing to do at all: go to the forum thread Development and porting of GSI firmware (Post bullik01 # 71222655) and try what catches your eye. Not all are loaded, but .... (although we do not seem to have an A / B structure, but only "arm64 A / B" were launched) PS: look for additional information here on the forum and for brotherly devices UMiDIGI A5 Pro - Firmware ( Post Xakep1993 # 86772223) Attached files recovery-TWRP_3.3-20191015-1714.img (22.81 MB) DisableForceEncryption_Treble.zip (4.24 MB)
Click to expand...
Click to collapse
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Good day
Had the same problem, (English not so good but I know you'll understand). What I did was just installing Corvus OS rom, the 11th version. It's been quite a while since i installed it.
Tried Lineage 18.1 and adding the smallest gapps available, but everytime i get code error 1. I guess it was the twrp 3.3 version i used cause some roms requer the latest TWRP versions. The lineage is installing just right nd can reboot to system with no hiccups.
None of Android 12 gsi versions has ever been able to installed. Cause when i try to install, i get the error of "file too large for the target partition. Tried everything from the net to increase the system partition to at-least 3gig. No success.....
Is anyone who can help to install android 12 even beta version will be ok for my N20 Doogee??
Thanx
flairepathos.info said:
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Click to expand...
Click to collapse
The file is in the forum. But to make your life easier here are the link.
https://drive.google.com/drive/folders/18B-srDVia_H4aDt7uvCDUxg2e4R5kVVY?usp=sharing The file is of type .exe and that extracts when you run on the pc, the problem is that I was suspicious about the virus so I threw the file in the total virus (if you don't know what it is, just search) and 6 programs pointed it out as malware but many others didn't find anything including karpersky and bit defender, there to make sure the files were there i renown they from .exe to .zip and I looked and the files really were there but as I don't want to take the risk I didn't extract and I didn't even try anything. The file that fix the encryption are inside doogee n20.exe, the guy said it will be in .exe and when you run it extracts the file in the C folder of the computer I recommend you to rename it from .exe to .zip because if the file have a virus you can screw your pc when running
Da-Judges said:
Good day
Had the same problem, (English not so good but I know you'll understand). What I did was just installing Corvus OS rom, the 11th version. It's been quite a while since i installed it.
Tried Lineage 18.1 and adding the smallest gapps available, but everytime i get code error 1. I guess it was the twrp 3.3 version i used cause some roms requer the latest TWRP versions. The lineage is installing just right nd can reboot to system with no hiccups.
None of Android 12 gsi versions has ever been able to installed. Cause when i try to install, i get the error of "file too large for the target partition. Tried everything from the net to increase the system partition to at-least 3gig. No success.....
Is anyone who can help to install android 12 even beta version will be ok for my N20 Doogee??
Thanx
Click to expand...
Click to collapse
you can use the pixel experience lite https://github.com/ponces/treble_build_pe/releases ( remenber the lite version, because is 2,5 gig) i try and instal in my phone and worked but i cant access my storage so i search and here are the solution https://forum.xda-developers.com/t/...loop-after-any-custom-rom-doogee-n20.4357313/ i dont try it but if you want here are the solution
flairepathos.info said:
Hi, were you by any chance able to get a copy of these files ,Please upload if posssible
The original links are broken and the internet seemed to wipe all traces out, I'm looking for the N20_utils and possibly the Disable force encryption one
Click to expand...
Click to collapse
Hi, did you find N20_utils?
Note
Before getting started, I'm not a developer and I'm not on that level yet but being an enthusiast of Android ROMs especially my favorite ROM Pixel Experience (PE). However what I can contribute (as of now) is to guide newbies and answer people who is confusing with flashing PE ROM, any custom kernels, mods, Gcam and help you out from problems while trying these things.
Tons credits to @jhenrique09, without his great effort there is no born of Pixel Experience project, and we would not have a taste of stock and pure Pixel ROM without having an actual Pixel phone.
It is good that you attempt new things and seek into the freedom of pure Android experience, and the whole world of Android development, though there's some risk when you try something new.
!!! Warning: I am not responsible for any bricked devices, it is your choice to modify your device software.
Pixel Experience ROM official thread - by Henrique Silva @jhenrique09
How to unlock bootloader?
https://xiaomiwiki.github.io/wiki/Unlock_the_bootloader.html
Official ROM downloads:
Download from Pixel Experience website
Screenshots
Check telegraph here!
Pixel Experience Official Wiki Page for Redmi K20 Pro/Mi 9T Pro - Info about raphael & raphaelin
Appreciation to
@jhenrique09, founder and lead developer of Pixel Experience, and maintainer for raphael & raphaelin (Redmi K20 Pro & Mi 9T Pro Series).
@WasikFahim, a friend of mine who assists me for creating this thread.
Thanks to all developers I have been know so far.
And all developers and original creators of the attached files below and for all of the following posts.
Special thanks to @Sandeeep Kiran (TG handle @ sandeeep, due to request from him), who has proposed the idea of creating this new thread for me.
Reserved.
Nice Thread ?
How To Flash Custom Kernels
Hello Guys Hope You're Fine, Today We're Going To Learn How To Flash Custom Kernels In Recovery, So Without Further Due Let's Jump Into It:
I'm Using PitchBlack Recovery
Prerequisite:
*Backup Stock Kernel [Boot.img & Dtbo(Optional)] Image=> 1 & 2
Steps For Flashing Custom Kernels:
1.Go To Recovery.
2.For OF(Go To Files) For TWRP/PBRP(Go To Install). Image=> 3
3.Select Kernel And Swipe to Install. Image=> 4 & 5
4.Wipe Dalvic/Cache.(Optional)
5.Reboot To System.
Enjoy!!!!!! :good::fingers-crossed:
Here Are Some Recommended Kernels:
We Use LOS FOD Implementation.
Gaming & Decent Battery = F1xy
Battery Backup & Decent Gaming = Immensity
Decent Performance + Battery = Englezos (Less gaming)
Mods tutorials
ANX Camera
ANX Camera TWRP
ANX Camera magisk
Working version of ANX magisk: 185
48MP fix for ANX camera magisk module: 181
Which ones should I download? Check attached screenshots below this post.
How to install and setup MIUI camera on PE?
* For ANX Camera TWRP
1. Save zip file to internal storage (/sdcard) and reboot to recovery.
2. For orangefox go to "files", for TWRP or Pitchblack recovery go to "install".
3. Swipe button to install.
4. Reboot to system.
5. Give all permissions to ANX camera, launch and quit app for at least 3 times.
6. You're all done.
* For ANX Camera magisk modules
1. Save both camera and 48MP fix modules to internal storage (/sdcard).
2. Open magisk manager, hamburger icon on top left corner, modules, tap on "+" icon and find ANX camera zip.
3. Same goes with 48MP fix module.
4. Reboot, give all permissions to ANX camera app, then launch & quit app for at least 3 times.
5. You're all done.
* 48MP fix is already included in ANX Camera TWRP, do NOT flash the 48MP fix magisk module.
* No root needed.
+ Credits to ANX developers and contributors, @HSgod, @nuub1k, for porting and debugging MIUI camera to AOSP ROMs.
Custom boot logo
MS drive Downloads
Head to XDA thread for more info, credits for @mouhannadsukkar creating boot logo collection.
Disable force encryption
Force Encrytion and difference compared with decrypted storage
1. All ROMs have force encryption by default for now, which should be enabled while booting the device for the first time.
2. Therefore DFE, also known as "disable force encryption", which shall force the device to be decrypted (Use #-dfe to get the DFE file).
3. If you format data, it will decrypt the encrypted storage, while everything on data partition including internal storage, also known as /sdcard directory, will be erased.
4. However if you already got a decrypted storage, simply wipe data and internal storage won't have any effects, unless you do a format.
5. To keep the storage decrypted, if you want, you will need to flash DFE for every ROM and vendor update.
6. Format data only if you flash custom ROM from stock MIUI, if you want to keep your storage decrypted or you want encrypted without flashing DFE while flashing custom ROMs and vendors (if the ROM uses MIUI vendor).
7. In short formatting data is to remove encryption for an encrypted device.
How to flash DFE?
IMPORTANT: Please make sure you perform a data FORMAT (NOT wipe) via recovery before flashing DFE, otherwise device may end up with bootloop or stuck in bootloader! Everything including all files on internal storage will lost so please backup everything to elsewhere. You have been warned, I am not responsible for data loss.
1. Go to recovery and format data (NOT wiping it, the place where you will type "yes" and confirm formatting).
2. Since internal storage is purged too, copy DFE from your PC or OTG storage etc., flash via recovery.
3. The recovery console will ask you to press volume buttons for picking options, so the recommended key combination is:
+ (vol up)
- (vol down)
- (vol down)
+ (vol up)
4. Done, reboot to system and see if storage is decrypted.
F2FS
What is F2FS?
F2FS, which stands for "Flash-Friendly File System", it was invented by Samsung coorperation, mainly focus on improving random read/write efficiency of flash storage and somewhat extends its lifespan.
Notice!!!
Currently, almost all known custom ROMs support F2FS on cache and data partitions but not system for compatibility and disk quota reasons, usually there's no writing actions to system partitions except flashing/updating ROM or using root access to modify it so keep system partition as EXT4.
How to enable F2FS?
You will lose all of your data including internal storage.
1. In recovery, convert data partition to F2FS via advanced wipe, same for cache partition (Do not convert system partition to F2FS to avoid some possible problems).
2. Flash f2fs-patched-fstab.zip (attached below) via recovery.
3. Reboot.
Note: You will have to flash patch again whenever flashing/wiping vendor, otherwise you will stuck at boot animation.
Fix low microphone problem (magisk needed)
Description
Sometimes, you might feel the microphone sensitivity isn't good enough on AOSP ROMs including Pixel Experience, this might related to device tree (or source code) of K20 Pro/9T Pro series. For instance you make or pick a phone call, using voice call of some IM apps the other side might not hear you clearly, that's the time when you can have a workaround if you have magisk installed.
How to fix?
Same as you install any magisk modules via magisk manager.
magisk_iem_mic_gain_0.3.zip attached below.
Magisk manager recovery mode
What to do if my device stuck at boot animation?
Sometimes, your device might stuck at boot animation because you flashed a buggy magisk module, for obvious reasons you have to delete that for letting your device boot into OS, so what about removing it via recovery? That's how this zip comes - Magisk Manager Recovery Mode.
How?
1. Boot your device to recovery, flash provided zip file.
2. Go to advanced => terminal.
3. Type this command to launch program:
sh /sdcard/mm
4. Type l to list all installed magisk modules, locate the one which might causes the problem.
5. Type r, enter, then the name of module name as the output shown, case-sensitive!
For example:
module[]
You should type:
module
Then enter.
6. If you see there's an X inside brackets like:
module[X]
Then you're good to go.
7. Reboot your phone and that's it.
Troubleshoot and advanced guides
Stuck at bootloader
Sometimes when you flashed ROM, custom recoveries, or updating vendor and try rebooting your device thereafter, your device does not boot into system or recovery but fall into bootloader (fastboot) screen. This is due to verified boot of our device being triggered, so flashing a custom vbmeta will usually get the problem solved.
How to flash vbmeta?
You need a working PC or laptop, USB cable and install fastboot driver if you are using Windows.
1. Download attached vbmeta file to your PC, connect your phone with USB cable, make sure PC has detected the phone and it's connected properly.
2. Open CMD (if using Windows) or terminal (Linux/Mac).
3. Type the following command:
Code:
fastboot flash --disable-verity --disable-verification vbmeta fake_vbmeta_williamfeng.img
4. Reboot your device to either recovery or system, it should work fine now.
Upgrade vendor
Note: You will not lose your data so you don't need to wipe anything, just flash vendor on top of current one, no matter if device is encrypted
1. Download right vendor zip for your device variant, see official PE wiki page.
2. Reboot your device to recovery, copy vendor zip to your internal storage.
3. On your device, select install and flash vendor zip.
4. Reboot to system.
Downgrade vendor
Note: Before you downgrade your vendor you're suggested to backup all your data (including internal storage) elsewhere in case you lose them while doing so.
If your device is decrypted (NOT encrypted), the steps are same as you upgrade vendor.
Otherwise:
1. Download right vendor zip for your device variant, see official PE wiki page.
2. Reboot your device to recovery, copy vendor zip to your internal storage.
3. On your device, select install and flash vendor zip.
4. Format data partition in your recovery (the place where you'll type "yes" and confirm formatting).
5. Reboot to system.
How to update PE ROM?
You don't need to download full zip file on PE, it gives small OTA which can be downloaded from "settings => system => system updater". After downloading simply tap on 'apply/install update', then the device will boot into recovery, update and reboot back into system.
WARNING: Make sure your device always have enough charge (30% or more is suggested) for updating process.
* The update file will be downloaded to /data/system_updates
Error 7 when updating PE
- If you see updating ROM doesn't work and the recovery shows you error 7, please make sure you update vendor to correct one first.
- Try updating your recovery (TWRP/OFOX).
If it still happens, try flashing full ROM zip of latest build instead of using built-in updater from ROM.
Miscellaneous info of Pixel Experience
Changing animation of Pixel Experience - just like you have a real Pixel device!
Power-off your phone and plug into changer, you'll see that.
Video link
WARNING - THESE TOOLS WRITE TO THE DEVICE PARTITIONS DIRECTLY
If you don't know what that means...
THIS CAN REALLY SCREW UP YOUR ---
I HAVE ONLY TESTED THESE ON THE A2020U (NON-5G) - I CANNOT SAY THEY ARE SAFE ON ANY OTHER VERSION OF THE PHONE (YET)(If you want to test it on a specific model you own, send a PM or post and I can tell you to run a few (safe) things from these tools to make them compatible your phone.)
See my next post down for some more "beginner friendly" general tips and tricks for this phone, including some fixes for common problems and a quick guide for installing Magisk!
If you can't afford to brick your phone, these tools aren't made for you.
There aren't really any protections from doing damage. I made them for myself because doing them on a command line constantly is a pain. I'm just sharing them for two reasons:
1) So myself or other people have tools available to make it easier when advising someone on how to fix their phone.
2) For tinkerers who are okay taking the risk that they'll mess something up.
Thanks to @djkuz / @Unjustified Dev for the EDL tool. These scripts really just expand the use of fh_loader commands in that tool. If you are able to read C++ and want to understand fh_loader I suggest searching on google, the source code is available and from that you can better understand what the tool does / what the command line options do. Feel free to ask here too, I'll do my best to share what I know.
Anyway - below I'll go into plenty of detail of what each "tool" does and some helpful information about using them.
I write in a kind of permanent verbose mode, so if you're impatient and need a TL;DR for these... tough. =)
CURRENT VERSION: Version 1.1d
Changelog:
Version 1.1d:
- Fixed reset scripts
Version 1.1c:
- Fixed a typo in backup_GPT ¯\_(ツ)_/¯
Version 1.1b:
- Fixed errors in GPT_Tools - apparently these existed since v1.0 DO NOT USE PREVIOUS VERSIONS
- Removed the v1.1a download (use 1.1b)
Version 1.1a:
- Added script to find the COM port automatically
- Updated all scripts to use the COM port in the file COMPort (created by the above script)
- Added the missing AB Partition manipulation files (accidentally left out of v1.0)
- Added script to run the phone reset EDL command
- Fixed all the filename inconsistency in the XML files - HOPEFULLY. Please post any errors you find. Unfortunately this will make this version incompatible with v1.0 backups without some work - either rename your backup files to match the new format or use the old XML files included.
-- Especially fixed the XML typo of "uefi_sec.mbn" being backed up from both A and B to the same file (overwriting the A copy with B during an ALL backup).
- Added support for installing firmware packages created for this tool. Put them in the Firmware_Package_Restore directory and use the scripts included with them.
Basic Instructions:
1) Download zip (See attachment at the bottom, or here - Download from AndroidFileHost)
2) Unpack zip
3) Move folder to the root directory, or inside any chain of directories that do NOT have spaces in any of the names
4) Right-click on scripts and select "Run with Powershell" to run
5) If running scripts fails due to permissions, see these instructions: https://superuser.com/questions/106360/how-to-enable-execution-of-powershell-scripts
Make a "Complete Backup" (minus userdata):
1) Run Load Programmer
2) Run "backup_all"
3) Check the backup directory and verify the files were backed up and sizes make sense - a full backup should be 10,387,202,048 bytes / 39 files for the critical files and 1,626,697,728 bytes / 64 files for the non-critical (Don't include the port_trace log file when checking size)
Note: You will see a lot of "warnings" before the files begin to download, the program checking if the files already exist.
How to Use These Tools:
Important:
When the scripts run there will be a lot of information dumped to the console. It's not necessary to read all of that BUT - IF YOU DO NOT SEE THE ASCII ART "DONE" AT THE END of running any of these scripts it is likely the script encountered a serious issue. "WARNING" art is normal for some scripts, but "ERROR" means something went wrong.
None of these find the COM port automatically. It is possible (the EDL tool does) but it's just extra work I'm not paid to do =P
You will need to edit each program and change the variable at the top (usually $COMPort = "6") to whatever port number your phone shows up on.
Sorry that's inconvenient, but it should just be once per script - my port number never changes so it wasn't worth implementing automatic port finding.
This is no longer needed after v1.1a.
1. Load Programmer
This is a simple but extremely important tool! You need to run this before running anything else. This script will open a window that runs a command to open a connection to the phone (when it is in EDL / "9008" mode). The window will stay open until you close it. When working on backups I often need to re-connect the programmer, so this makes that easy - just alt-tab to it and hit enter. If you look at the script, it's fairly straightforward - just read the instructions on the screen after running it. The "secret sauce" for this is really the firehose protocol for our chipset that Unjustified Dev provided in the EDL tool.
2. Backup / Restore:
backup_all: This will backup everything on the phone EXCEPT for the huge userdata partition. It will create a backup in two directories, which I'll explain.."critical" / "non-critical": You can see that I have scripts to run these two "types" of backups. Non-critical DOES NOT MEAN NOT IMPORTANT. It means that it is not critical TO ME to back up those files EVERY time I do a backup, because they rarely change. They're EXTREMELY important to have at least one backup of for your phone. The "critical" backup files are files that change often, although some of them are extreme non-critical (cache for example). Use a different name than "critical" if you like, but the point is that only with BOTH backups run (which is what backup_all does) will you have a complete backup.restore_all: This will restore a full (both critical and non-critical) backup set. The backup files have to be in the "restore_critical" and "restore_non-critical" directories respectively. If you didn't make the backup you're trying to restore with this tool CHECK THE FILENAMES, e.g. if you used Unjustified's EDL tool you have to rename the "abl.elf" file his backup generates to "abl_a.elf" for mine. I put _a and _b on every partition that has an a/b version because I got tired of getting them confused. Of course you can always install a backup to either slot.Files moved to the "restore_" directories won't be changed at all by the restore process so you can cut/paste the files from your backup into the directory instead of copying them.
3. A/B Partition Manipulation
These are no more complicated than the backup/restore tools. But they are written to make manipulations of the A/B partitions easier.My main use for these is when I know I have a good, working ROM setup on slot A, I run A2B copy. Then no matter which slot I end up booting I'm sure it will work. (That is, if you have a working, booting slot, copying all the files from that slot to the other slot using this tool will make both slots the same.)Backup/Copy:run_AB-partition-backup: As it says, it will backup both the A/B partition files - WARNING this is NOT a full backup of the phone.run_AB-partition-swap: This will backup all the A/B partition files, then it will write the B files to A and A to B, effectively swapping the partitions and leaving you with a backup in case it screwed up. This backup is ONLY OF THE A/B FILES.. NOT the whole device!run_A2B-partition-copy (and run_B2A-partition-copy): These will do a backup of both A/B partition files, then write the A partition onto the B partition (A2B) or vice versa (B2A), effectively mirroring that partition.
Write/Restore:All the restore scripts try to find their files in the "restore_Partitions" directory - place the files from one of the backups to be restored there.restore_AB-partition-backup: Restore a backup of both the A and B partition files.restore_A-partition-backup (and B): Restore just the backup of one partition to the same partition it was taken from (A to A and B to B).restore_A2B-partition-backup (and B2A): These write from one partition backup to the other partition as the name suggests.
4. GPT Tools
These are some basic tools to directly interact with the partition tables - these are not going to be of any use to 99% of people, so just ignore them if you don't know what they do.run_fixGPT: This issues the --fixgpt command to each of the LUNs. USE AT YOUR OWN RISK. As I understand it, this will use the onboard device configuration information from each LUN (e.g. logical size) and try to rebuild the GPTs. It's similar to running patch XMLs, it can clean up flashing messes. It isn't magic and won't fix everything.Rarely will anyone need it unless they've been messing around with the flash tools recklessly... I certainly don't know anyone who would do something that dumb backup_GPT: Backup all of the header and footer (main/backup) GPTs for all the partitions (lun 0-5). I am not aware of whether any other models of the phone have more LUNs, so be careful if you're using this on a non A2020U phone.restore_GPT: Simply write an entire GPT backup set (both main and backup 0-5) onto the phone. The backups must be in the restore_GPT folder. This DOES NOT BACKUP before it runs so make sure you did your backup.
6. Set Bootable Partition:
Alright this one is important for everyone. There are two scripts here - one for slot A and one for slot B. These just run a simple command, but they will fix a common problem I (and probably others) have - when the ROM active-slot information does NOT match the partition (hard drive) bootable flag, the phone will bootloop EVEN THOUGH EVERYTHING IS GOOD.So when you flash an EDL backup (depending on which files you flash, I believe this happens because of either the bootloader or the GPT files) there is a chance the backup you're flashing was originally from a different slot than the one you're restoring it to. The config thinks it should be on slot A while the hardware thinks slot B should be booting.This will result in a fast ~3 second bootloop as the two disagree and reset.This tool changes which partition is expecting to boot - "1" for slot A and "2" for slot B.This does NOT change the active slot - the phone will continue to boot the same slot it's trying to boot. You just need to make the partition that it is trying to boot has a bootable flag.AFAIK there is no way to change the active slot (the one XBL (I think) is trying to boot), except through fastboot or when the phone fails to load the OS 8 times in a row (note - if it fail to load the OS - if the phone bootloops before "boot" is called it won't ever switch slots on its own).This was a common cause of fast bootloops for me before I figured this fix out.
It does no harm to try this as you can always switch again. If neither one works for you, then it's something wrong with the files you're flashing. If you know which slot the phone is trying to boot (the one it was on last), run the script that matches that slot.
7. Write "Unlocked" Bootloader and FRP:
Just like the original EDL tool, these very simply overwrite your existing (probably stock) bootloader (abl) files with the fastboot enabled version, and/or your FRP with the "unlocked" flag on (see description below). This will allow you to enter the bootloader menu (Vol+/- on booting) and use fastboot to unlock the bootloader.backup_FRP-and-bootloaders: As it says, this will make backups of both the FRP file and current bootloader files (ABLs).run_all: Literally just runs both of the below scripts *shrug*write_UD-bootloader: This automatically backs up both your existing A/B bootloaders before overwriting them (BOTH) with the unlocked/fastboot bootloader.WARNING - an unfortunate fact is that if you're using the stock ROM and you have this bootloader installed, it borks the USB mode so it's stuck in charge only. There's a way to fix it temporarily, I'll post it in my "tips" thread, but you have to do it every time you boot, very annoying. I can't fix it permanently because I don't know how the bootloader file was built!WARNING 2 - Android 10 will NOT BOOT with this bootloader installed. You can still install it, trying to boot will bootloop, but you can get into the bootloader menu and use fastboot - but there are no recoveries I know of that work with Android 10 right now, so there's very limited use to having fastboot right now. Hopefully we can get a port of TWRP 3.4 going for this phone..write_unlock-frp: This is also in the EDL tool, but maybe poorly explained - the FRP file holds the flag you change in the OS Developer Options to designate "allow bootloader unlock". If you FORGOT to switch that flag on and unlock, as I understand it, you get bootlooped. This can fix that for you without having to go through all the work of undoing that mess.WARNING - I have only tested this with a brand new factory reset OS WITHOUT any fingerprint/code set. It may not work if you set one. I warn against using this if you are not ready to lose your data. It's convenient if you just forgot, but if you set a pattern/fingerprint security and encrypted the filesystem overwriting the FRP might remove your ability to decrypt which would force you to factory reset. Again, I haven't tested it for that so it may work, but be careful.If you already screwed up and ran this to set the flag - the script runs a quick backup of your old FRP just in case. So you can try to restore that FRP and pray lol)
8. Specific Files:
This is just a generic program to backup/write(restore) "specific files".I include a "Reference.XML" which has a full <program> line for every partition you might want to write/read on the phone. To use this, you need to copy the lines from the reference XML into "rawprogram-specific-files.xml" for the files you want to read/write.As an example I already set up "rawprogram-specific-files.xml" with the two lines for "abl_a" and "abl_b" in it. So the script will backup or restore those files (provided you put the abl's you want to restore in the restore_files directory).I personally use this template a lot - I have one for ABLs, one for AOPs, one for BOOTs, and so on. If you are trying to fix a specific file(s) it's convenient.
9. Userdata Backup:
I put this last because, to be honest, I'm not sure how good of an idea including this even is.VERY IMPORTANT - DO NOT USE THIS USERDATA TOOL IF YOUR PHONE IS NOT THE 256GB VERSION!!!!!I will need someone with the 128GB version to send me their GPT files if they want me to make an XML that works for them. Because the userdata size for SURE depends on your phone version.Also, I wrote a script that breaks up the file into download slices (and can be written back to the phone in slices, of course) - one, to see if I could do it and if it would work (it does)... and two, so that in the horrible case that something goes wrong during the... nearly 2hrs of transfer time, for my 256gb image ... that I can at least not have to start all over. If something happens, you should be able to remove the entries in the XML for what you already have and start again.Finally - is it even worth doing? Is backing up the userdata even useful?I don't know yet.For an unecrypted pre-A10 phone I do know it works to fully flash ALL the files on the phone + the userdata all at the same time to return the phone to the exact "state" it was backed up in - all the apps and settings and everything, exactly as they were.But A10 is encryption enabled always, and it uses file encryption which sounds even worse for this idea.. and I don't know if the crypto keys change and when. So flashing an entire encrypted partition might just leave you unable to decrypt all, some, or none and you lose everything.OR it might just work - you throw the whole image on there and the decrypt key is the same, boom, easy backup.If anyone tries it, let me know how it goes (or doesn't). I'll update with any results I find.Update 1: I have confirmed that for the 256gb A2020U backing up the full phone and userdata allows you to restore the phone to that exact state. Doesn't matter if it's encrypted, password set or not, etc. If you backup the entire userdata image and reflash it that is where the phone will be. In most cases you also need all the other partitions too, but if they have not changed they don't have to be reflashed. (I confirmed going from encrypted with password -> encrypted with no password -> back up encrypted with password.. This is on Android 10 with its more complicated encryption).Another nice thing to note - of course the image of the phone will be the size of the partition (ie. 256gb for mine, 128gb for others). But if your phone storage is largely empty, you compress the backup using something like 7z once the image has been backed up. It won't take up so much space then. How much less? My 256gb image compressed is 4.5gb. lol.... it makes sense, the phone is new and there's basically no information on the userdata. Many of the pieces of my userdata backup have the same exacty hashes - meaning they are literally just all 0's... 260gb of zeros. Unfortunately you can't get away with just backing up part of the image as data could be anywhere. And over time as the sectors get written to, it will get more difficult to compress.Anyway, if anyone has a 128GB version they want to donate to science (kidding - I just need backups of the GPT) I can make the XML file to use for backing those up too.
Extra Note: All the programs automatically build a log of the console window, so if something goes by too fast just check the log. The fh_loader also creates a log and dumps it somewhat randomly about... lol.. the filename is port_trace.txt. This tends to get deleted and overwritten easily so if you want to keep it, move it when the script finishes,. it does often contain more information than the console shows - it can be useful understanding what's going on.
Extra Note 2: You'll notice a script "Create Hash List" in practically every directory. That's to strongly hint that using that script is super useful. All the files backed up through these tools, by definition, have the exact same size. If you hash your files though, you can tell if they have changed at all. This is extremely useful in troubleshooting problems.
How to install an EDL firmware package:
Note: This tool is specifically made for the firmware packages I posted. It won't work with any other package (although it can, with a little work).
1. Install the EDL tools
2. Run a backup of your phone! Even if it isn't booting.
3. Download a firmware package from this thread: [ROM][STOCK] Stock Firmware Packages (For Expanded EDL Tools)
4. Unpack the firmware archive into the tool directory "Firmware_Package_Restore"
5. Put phone in EDL mode and run Load Programmer
6. Run whichever "Write Firmware vX to Y.ps1" you want (X = firmware version, Y = A or B partition) (If you don't know which partition is currently booting, just install both.)
7. Wait for the install to finish ("done"), then reset the phone with either the power button or the reset tool
8. You might see a few bootloops and then the phone ask you to do a factory reset / system wipe.
9. Done.
PLEASE POST IN THE FIRMWARE THREAD _NOT HERE_ IF YOU RUN INTO ANY ISSUES!
Enjoy!
Also, while I'm here... some other helpful notes for this phone:
-------------------------------
General Information:
As of right now there are a lot of working options for Android 9 and quickly expanding thanks to work @Unjustified Dev did and work @rafyvitto is continuing to do! Check out some of his sGSI ROMs, lots of options!
Thanks to Unjustified LOS 16 is available for Android 9 also, and is the base install for most ROMs. See his threads for that. I may write up an install guide here that's a little more in depth than his.. not today though.
Upgrading to Android 10 with the bootloader unlocked is possible but requires a workaround:
You must unlock on Android 9 then use recovery to side-load the Android 10 update available from ZTE USA (HERE).
This will remove the fastboot enabled bootloader and requires a complete system wipe.
You will retain bootloader unlock.
Once you have updated to A10 you can run OTA updates to get up to the latest version.
Downsides to A10 include - NO RECOVERY (yet), NO CUSTOM ROMs (yet), and if you flash the fastboot enabled bootloader you CAN use fastboot, but you cannot boot- the phone will be in a bootloop until you restore the stock A10 bootloader.
-------------------------------
Resetting the phone manually:
In EDL Loop - Hold power for 20 seconds
In EDL Not-Looped - Hold power for 5 seconds
In System (booted after ZTE logo) - Hold power for 10 seconds
----------------------------------
Entering Modes:
All of these start by using reset above, THEN the button(s) below - in all except one case (EDL), when the phone resets it will vibrate and then show the blue ZTE logo.
When you feel the vibration you want to immediately release the power button and press the mode buttons.
This can be confusing and tricky - most people say "hold power + button" - that is incorrect. Most cases if you hold any button other than power the phone will not finish resetting until you release that button.
What you want to do is right before or as the phone vibrates, then you hold the button. Once the ZTE screen is up it is probably too late if you missed it. So hold power for your reset and be ready to push the button you want when you feel the vibration.
The one exception - EDL mode. For EDL mode you can (and must) hold the key combo just before/during the restart.
Recovery Mode: Vol+ Button
Factory Test Mode: Vol- Button
Bootloader/Fastboot Mode: Vol+/- Button (both) when phone is NOT plugged into USB (if you are too early pressing the combo, even with the USB unplugged, you will get EDL mode)
Emergency Download Mode: Vol+/- Button (both) when phone IS plugged into USB
--------------------------------
EDL Flash Errors (esp. when EDL looped):
There is NO indication the phone is even ON when you are EDL stuck/looped. Other than when you plug into the computer with the right drivers it shows up as a 9008 device (9008 mode is EDL for Qualcomm).
Even when you can see the phone on your computer, it can often "freeze" in EDL if it is left idle for too long (not connected to and being used by a Sahara programmer).
If you try the EDL tool or another flash tool and they give you errors related to the Sahara programmer not loading or no "hello", do this:
Reset the phone - use a clock to count if you need, has to be accurate since there's no indication of when it resets. Press down Vol+/- and the power button, count to 20sec, then release JUST the power button. Keep holding both of the volumes for another 5 sec, then release them. That will get you back into a fresh EDL. You can watch your Device Manager to see the phone disconnect as an indicator when to let go of the power button. If you mess up the timing, wait a bit before trying again so the phone isn't in the middle of rebooting.
Easiest way to tell if you're in EDL is to watch the Device Manager while you do it. Otherwise there is just a lot of guess work, since there's no logo or vibration when you get it right, phone just appears off.
--------------------------------
USB Mode Stuck After Unlocking:
Something about the fastboot/"unlocked" bootloader causes the USB mode when you boot in the OS to be stuck on "Charge Only" mode.
Luckily I found @meow sir 's comment tucked away in this thread, and he knew a way to fix it (thanks!):
1. Open the phone dialer
2. Dial in "*#*#DEBUG#*#*" (debug = 33284)
(Sometimes takes a little bit to open, but a debugger menu will open)
3. Select the 2nd option for USB
4. Pick the only option - this will unset some strange "testing" mode and you can use MPT again.
Unfortunately this fix doesn't stick, you have to do it every time unless you switch back to the stock ABL. =(
--------------------------------
Installing Magisk, Quick Guide:
- You must have your bootloader unlocked already! This works on both A9 and A10.
1. Use this tool to create a full backup! (backup_all)
2. Go into the "critical" directory created by the backup and find the files for boot_a.img and boot_b.img - rename them to boot_a_bak.img and boot_b_bak.img and keep that window open, need them in a second
2. Boot into the OS. Download the Magisk Manager APK from HERE
3. Copy the APK and both of those boot files to your phone, open a file manager and install the APK
4. Open Magisk Manager and click on "Install" for Magisk (upper right)
5. Select "Patch Boot ROM" (or whatever it says.. something like that..)
6. Navigate to boot_a_bak.img and patch it.
7. Go to your Downloads directory (where Magisk dumps the patched file) and rename it to boot_a_magisk
8. Go back to Magisk and repeat those steps for boot_b
9. Copy the two patched Magisk boot files to your computer, into the folder with your "critical" files backup.
10. Rename the Magisk files to "boot_a.img" and "boot_b.img"
11. Move all the files from the "Backup\backup_all-critical-(...)" directory to the "Restore\restore_critical" directory in my tools
12. Finally, reboot into EDL.. almost there!
13. Run "restore_all-critical" (don't forget to run Load Programmer first..)
14. It will restore all you files, kinda a waste of time - if you know how to use the "Specific Files" tool this is a perfect time to use it to flash JUST the boot files. But anyway - this will get it done.
15. When done flashing, reboot the phone and open Magisk Manager to confirm it is installed!
The Magisk team recommend you DO NOT FLASH your stock boot files back to uninstall it, instead they say you should run their uninstaller.zip. However, I am not sure how to uninstall it if you're on A10 since we don't have a recovery that can flash zips? (Unless the stock recovery works for that, I don't think it would..)
I suspect (but have not tried) that on our phone flashing the boot files back over Magisk will not really be a problem since the recovery and ramdisk are all wrapped up into the boot image. But I don't recommend trying it if you value your data! Fair warning.
---------------------------
Alright that's everything. Good luck!
This will be useful for a lot of folks on here, thanks for taking the time to look for a work around.
rafyvitto said:
This will be useful for a lot of folks on here, thanks for taking the time to look for a work around.
Click to expand...
Click to collapse
Glad to be helpful! Usually I lurk the forums getting information I need to unlock/root/etc lol.. but I saw I actually could contribute something to this forum so hopefully it encourages people to get interested in this phone. It's looking pretty sweet now that I'm not spending days fighting with bootloops!
Indeed,on the note of attracting more users. im going to be releasing something for the pixel lovers very soon ?
Thanks Bob!
I'm on A10 with unlocked bootloader. I made all EDL tool backups when on A9 but these were done before correcting the typos as suggested. So I am not confident of successfully flashing back to A9 (preference).
Therefore I will likely flash the magisk-patched boot files to attempt root and report my experience...
Sent from my ZTE A2020U Pro using Tapatalk
big thx, glad to see some life to this almost dev-dead device
Hey thanks for the post. I'm thinking about buying the phone but have a quick question. Can I update to the latest version of Android 9 before unlocking or will the OTA be Android 10. How would I go about updating to the latest version version of Android 9 and not go to Android 10. Can I download the Android 9 OTA from somewhere and flash that one? Thanks in advance for the help!
Crackass said:
Hey thanks for the post. I'm thinking about buying the phone but have a quick question. Can I update to the latest version of Android 9 before unlocking or will the OTA be Android 10. How would I go about updating to the latest version version of Android 9 and not go to Android 10. Can I download the Android 9 OTA from somewhere and flash that one? Thanks in advance for the help!
Click to expand...
Click to collapse
:good: I think your question borderlines on needing its own thread in the Q&A section but I'll answer you anyway...
Currently as long as you are on A9 when you get the phone you can just do OTA updates from firmware version 1.10 to 1.11 to 1.13 (not sure what android security update that is), after 1.13 it goes to A10.
There is an A10 firmware available from ZTE to SD card sideload. Once installed it has to be updated to the latest A10 via a couple OTA updates.
Going directly from A9 to A10 via OTA goes directly to the latest version.
You cannot flash the A9 OTA... because flashing an OTA is an oxymoron... but I guess you mean can you download the A9 firmware and flash them. The answer is... maybe. ZTE does not offer official downloads any A9 firmware for A2002U (USA version), only A10.
They do offer A9 firmware for A2020G (european) and I think other foreign versions (RU, CN). These cannot be interchanged, if you have the US or EU or CN phone you need to use that firmware... from what I have read. I could be wrong, I don't have those phones.
But there is an unofficial stock A9 firmware for the A2020U here on the forums, uploaded by @rafyvitto . That will get you to.. I forget.. 1.11? That can be flashed using the original EDL tool or, with a little modification, the EDL tools in this thread.
Additionally.. if I ever get around to it... I plan to upload all three A9 firmware packages for the US version which can be flashed with the EDL tools in this thread. Not sure if it's really necessary, but I have them.. it's just a matter of figuring out hosting them and spending the time to upload them.
bobthenormal said:
:good: I think your question borderlines on needing its own thread in the Q&A section but I'll answer you anyway...
Currently as long as you are on A9 when you get the phone you can just do OTA updates from firmware version 1.10 to 1.11 to 1.13 (not sure what android security update that is), after 1.13 it goes to A10.
There is an A10 firmware available from ZTE to SD card sideload. Once installed it has to be updated to the latest A10 via a couple OTA updates.
Going directly from A9 to A10 via OTA goes directly to the latest version.
You cannot flash the A9 OTA... because flashing an OTA is an oxymoron... but I guess you mean can you download the A9 firmware and flash them. The answer is... maybe. ZTE does not offer official downloads any A9 firmware for A2002U (USA version), only A10.
They do offer A9 firmware for A2020G (european) and I think other foreign versions (RU, CN). These cannot be interchanged, if you have the US or EU or CN phone you need to use that firmware... from what I have read. I could be wrong, I don't have those phones.
But there is an unofficial stock A9 firmware for the A2020U here on the forums, uploaded by @rafyvitto . That will get you to.. I forget.. 1.11? That can be flashed using the original EDL tool or, with a little modification, the EDL tools in this thread.
Additionally.. if I ever get around to it... I plan to upload all three A9 firmware packages for the US version which can be flashed with the EDL tools in this thread. Not sure if it's really necessary, but I have them.. it's just a matter of figuring out hosting them and spending the time to upload them.
Click to expand...
Click to collapse
Just wanted to chime in, interchanging firmware between each model is possible, you would only need to reflash your model/nonhos/tz partitions to the ones of your variant to have working ril/fod fp/sensors.
Ok Bob I gave it a go and successfully rooted my A2020U running stock A10 v2.09. This is my experience...
Firstly, my A2020U could not connect so I used the @Unjustified Dev Tool ("original tool") to easily determine my com port (i.e. 3). I edited the your scripts accordingly (using Notepad++) and got connected.
I'd rather not fiddle with the hardware buttons to change modes so I used the CLI to "adb reboot edl" to get into EDL mode.
I executed the backup_all.ps1 script.
It echoed several "warnings" indicating that it could not find files. However, the created backup folders did in fact include those files.
I noted that none of the "A" slot files include the "_a" postfix; the "B" slot files did include "_b".
Now I needed to transfer those boot files to my device by first rebooting my device and connecting via MTP.
I noted that the original tool offered a reboot menu option (but sadly only after executing a successful operation). So, not wanting to fiddle, I used the original tool to backup my boot files, then used the menu option to reboot; On my device I then manually selected it to connect via MTP.
After transferring the "boot.img" and "boot_b.img" files to my device, and installing Magisk Manager. I patched them and transferred them back to my PC.
To "flash" (restore) the patched files I decided to cut 'n' paste the two lines regarding them from your Reference.xml file into your rawprogram-specific-files.xml file, replacing your example lines.
I executed your run_write-files.ps1 script and it completed successfully.
Not wanting to fiddle again with the hardware buttons (just so that I can get the reboot option), I backed up the patched files using the original tool and rebooted. Now my device is successfully rooted.
Thank you!
Additional notes and suggestions:
1. Can you please investigate the "false" warnings? See my (redacted) log file attached;
2. It would be great if you could create/duplicate a script within your expanded tool set (or main program) to determine and set the appropriate COMPort (and teach us non-coders the actual commands);
3. Would you also consider investigating and including a reboot device script? (It looks like the original tool calls reset.xml);
4. Note that, at the time of reporting this, the latest versions for the Manager and Magsk are 8.02 (307) and 21.0 (21000) respectively, and that I had to switch the update channel to "beta" for the patched files to pass SafetyNet;
5. Because rooting is a likely use of your tool I am attaching my modified rawprogram-specific-files.xml file which targets the boot files for convenience.
bobthenormal said:
...
Additionally.. if I ever get around to it... I plan to upload all three A9 firmware packages for the US version which can be flashed with the EDL tools in this thread....
Click to expand...
Click to collapse
If this can help me get my A10 device to a state where I can install a custom recovery and cutom ROMs, I would appreciate it!
eKeith said:
Ok Bob I gave it a go and successfully rooted my A2020U running stock A10 v2.09. This is my experience...
Firstly, my A2020U could not connect so I used the @Unjustified Dev Tool ("original tool") to easily determine my com port (i.e. 3). I edited the your scripts accordingly (using Notepad++) and got connected.
I'd rather not fiddle with the hardware buttons to change modes so I used the CLI to "adb reboot edl" to get into EDL mode.
I executed the backup_all.ps1 script.
It echoed several "warnings" indicating that it could not find files. However, the created backup folders did in fact include those files.
I noted that none of the "A" slot files include the "_a" postfix; the "B" slot files did include "_b".
Now I needed to transfer those boot files to my device by first rebooting my device and connecting via MTP.
I noted that the original tool offered a reboot menu option (but sadly only after executing a successful operation). So, not wanting to fiddle, I used the original tool to backup my boot files, then used the menu option to reboot; On my device I then manually selected it to connect via MTP.
After transferring the "boot.img" and "boot_b.img" files to my device, and installing Magisk Manager. I patched them and transferred them back to my PC.
To "flash" (restore) the patched files I decided to cut 'n' paste the two lines regarding them from your Reference.xml file into your rawprogram-specific-files.xml file, replacing your example lines.
I executed your run_write-files.ps1 script and it completed successfully.
Not wanting to fiddle again with the hardware buttons (just so that I can get the reboot option), I backed up the patched files using the original tool and rebooted. Now my device is successfully rooted.
Thank you!
Additional notes and suggestions:
1. Can you please investigate the "false" warnings? See my (redacted) log file attached;
2. It would be great if you could create/duplicate a script within your expanded tool set (or main program) to determine and set the appropriate COMPort (and teach us non-coders the actual commands);
3. Would you also consider investigating and including a reboot device script? (It looks like the original tool calls reset.xml);
4. Note that, at the time of reporting this, the latest versions for the Manager and Magsk are 8.02 (307) and 21.0 (21000) respectively, and that I had to switch the update channel to "beta" for the patched files to pass SafetyNet;
5. Because rooting is a likely use of your tool I am attaching my modified rawprogram-specific-files.xml file which targets the boot files for convenience.
Click to expand...
Click to collapse
Nice! :good:
For the questions..
0. Thanks for the heads up on filenames! I completely missed that the _a files don't have the labels... As you probably noticed all the files are backed up correctly still (no missing/overwritten files), but I removed the _a from all the A slot files. That was my original "fix", so I guess I started building this package before I got annoyed by not having the _a/_b consistency. I'll update the correct XML file and upload it as a new version.
1. Don't worry about those! They're part of using the fh_loader interface. Warnings are usually just fine, ERRORS are bad. I'll add a note to the post when I get a chance so people don't get scared by that.
It's only when you do a backup the program is really only designed in the "writing" sense, for backups you literally run an identical XML to writing but you send a flag that reverses the process. So it weirdly checks if the files it is going to copy (which of course don't exist) exist, and it throws the standard warning, but then it just creates them (of course).
I can't turn those off without lowering the verbosity setting for that tool. I decided to leave it set to high because if someone has a problem and they post their log file (like so!) it's very useful to troubleshoot.
2. I'll think about it / try. Not very hard to program but a little time consuming.
I'll throw a copy of lsusb.exe in the next version. Windows port of the linux command. People can simply run that on a command prompt and it will list all the active COM ports/devices. If you're not familiar with it - you can also find out by clicking on the windows start bar or pressing the windows key and typing in "Device Manager". In the hardware list there is a category for COM ports where it lists them.
3. Yeah that's very easy I'll put one in the next version as well.
4. Helpful to know. Interesting that you needed beta to pass... I didn't think to mention I use the canary builds (not really recommended... the current one crashes when I try to hide Magisk Manager lol)
5. Thanks! Maybe I should make a directory specific to boot backup/write... but I do think anyone not comfortable doing the change you did might not want to be flashing their boot files anyway haha.. things to consider I guess.
As for getting you back from A10, definitely. I'll figure out how to upload them to one of those file sharing sites in a week or two.
In the mean time, with a backup from this tool you're safe (as far as bricking goes, you'll have to system wipe) to try rafy's EDL backup to revert to A9. I'll find the actual post... I should have been less lazy and linked it in my post lol... HERE - rafyvitto's EDL.
If flashing his backup doesn't boot right away try the tool I included to fix the bootable partition. If it still doesn't work after that (maybe mention here what happened) then just restore your backup.
Do you have the 128gb phone by chance?
Thanks much, especially for your detailed clarifications and convenient link!
I have the 8/256GB (P855A03_NA) model.
PS
I want to spend more time on ensuring I have a complete device backup before nuking with another EDL; will dedicate some time this week...
Sent from my ZTE A2020U Pro using Tapatalk
eKeith said:
Thanks much, especially for your detailed clarifications and convenient link!
I have the 8/256GB (P855A03_NA) model.
PS
I want to spend more time on ensuring I have a complete device backup before nuking with another EDL; will dedicate some time this week...
Sent from my ZTE A2020U Pro using Tapatalk
Click to expand...
Click to collapse
Oh nice, with the 256gb model you're good to use the userdata backup program too. Sounds ideal for you since, like me, you want a really bulletproof backup. If you run a full backup and then run the userdata backup you literally have a "phone state" so you can return your phone back to exactly where it was, not have to wipe system or anything.
Of course I'd hate to be wrong so as usual, do at your own risk! Lol. But I am using that method and it has worked great. The downside being over an hour of waiting for the userdata to download or upload... and having to store 256gb (for long term storage you can compress it down to literally a few gb).
I've been kinda busy, but working on getting some of those things from my last post done hopefully this week.
bobthenormal said:
Oh nice, with the 256gb model you're good to use the userdata backup program too. Sounds ideal for you since, like me, you want a really bulletproof backup. If you run a full backup and then run the userdata backup you literally have a "phone state" so you can return your phone back to exactly where it was, not have to wipe system or anything.
Of course I'd hate to be wrong so as usual, do at your own risk! Lol. But I am using that method and it has worked great. The downside being over an hour of waiting for the userdata to download or upload... and having to store 256gb (for long term storage you can compress it down to literally a few gb).
I've been kinda busy, but working on getting some of those things from my last post done hopefully this week.
Click to expand...
Click to collapse
That's great to know! Your user data backup option has simplified my life.
I will wait for your next revision to do a full backup plus user data before nuking.
I am looking forward to moving on from ZTE's A10 to one of Ray's ROMs...
Sent from my PH-1 using Tapatalk
Updated to 1.1a - kind of had to rush on some things so keep an eye out for mistakes, especially in the XML files, and let me know if you find any.
Should have an 1.09 (A9) firmware package up "Soon(TM)", just have to make the xml files then upload the file somewhere.
EDIT: Already needed to update to 1.1b - I found that the GPT_Tools had a big error that probably was there since 1.0 and no one noticed! Backups of the GPT should now actually work...
Thank you @bobthenormal !
Looking forward to your A9 EDL backup...
Sent from my PH-1 using Tapatalk
eKeith said:
Thank you @bobthenormal !
Looking forward to your A9 EDL backup...
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
It's up -- see the new thread.
I didn't have time to test it so make sure you backup but I'm 99,99% sure it will work. I tested it several times in the past, but to make the firmware package I took out all the (I hope) unnecessary files.
There's one thing I'm not sure of - whether you'll need to use the Fix Bootable tool after installing it. IF you need to, then I believe you will have to install it to partition B and then run fix bootable B. (The 1.10 backup was taken originally from the B partition).
If you find that it works without having to do that, let me know... it may not be necessary if wherever that bootable flag is stored didn't get included in the firmware package.
bobthenormal said:
It's up -- see the new thread.
I didn't have time to test it so make sure you backup but I'm 99,99% sure it will work. I tested it several times in the past, but to make the firmware package I took out all the (I hope) unnecessary files.
There's one thing I'm not sure of - whether you'll need to use the Fix Bootable tool after installing it. IF you need to, then I believe you will have to install it to partition B and then run fix bootable B. (The 1.10 backup was taken originally from the B partition).
If you find that it works without having to do that, let me know... it may not be necessary if wherever that bootable flag is stored didn't get included in the firmware package.
Click to expand...
Click to collapse
Thank you @bobthenormal !
I should be able to give it a go this weekend and inform...
Sent from my PH-1 using Tapatalk