Sid127 has skillfully adapted TWRP 3.6.x for compatibility with the Nokia 6.1 Plus, see [OFFICIAL] TWRP 3.6.0 | DRG/DRG_sprout support thread. Which is great, because TWRP added Android 11 compatibility, see TWRP 3.6.0 Released (Nov 28, 2021), and (as of Mar 10, 2022) also TWRP 3.6.1 Released.
His installation procedure did not work on my Nokia 6.1 model 1043. Even with different models, you are advised to instead better proceed with my Instructions below!
I have tested his build thoroughly with [OFFICIAL] LineageOS 18.1 (Android 11) installed and found most (but not all!) featured reliably working. To spare you unnecessary time fiddling around, do read my report over in his thread.
I do not know if the differences between the Nokia 6.1 Plus (DRG) and our Nokia 6.1 (Plate 2 aka PL2) have any effect on TWRP, or if a TWRP for a 6.1 Plus can be used for a 6.1 without any adaptations. @Raghu varma @Sid127 @theimpulson , what do you know or think?
I encourage everybody who has an Android 11 ROM installed on their Nokia 6.1 to install Sid127's 3.6.x TWRP with my instructions, then test and report back below. Esp. more data about the "TWRP not seeing SD if formatted as and chosen as sole Internal" issue as outlined in my post over in Sid127's thread would be of great value.
Installation Instructions for Nokia 6.1 (adapted from Sid127's original procedure)
1. Download the latest TWRP img file (not the .zip!) from the official TWRP for DRG_sprout downloads page
2. Download the launcher scripts .zip for your OS, Windows or macOS, attached to this post. Extract 'boot twrp-3.6.1_9-0-DRG_sprout' and place it "next" to (= into the same folder as) the downloaded image file
3. Boot your Nokia to Download (aka bootloader/ fastboot) Mode
4. Connect it to your computer with a USB cable
5. Double-click the launcher script (you can disregard the error)
6. Head to TWRP's "Advanced" section and tap onto "Flash Current TWRP" (info)
7. Sid127 has not included the "Fix Recovery Bootloop" option in the "Advanced" section. I'm always getting a off/on flashing TWRP screen when I try to reboot into recovery at this step. If you do, too, also perfrom steps 8 - 11:
8. Download Raghu Varna's TWRP 3.4.0 for Nokia 6.1 img file
9. From the launcher scripts .zip you downloaded before, extract 'boot twrp-3.4.0-0-PL2_sprout-11.0-20200909' and place it "next" to (= into the same folder as) the downloaded image file
10. Double-click the launcher script (you can disregard the error)
11. In TWRP, go into the "Advanced" section and select the "Fix Recovery Bootloop" option
12. Head over to the "Reboot" option and reboot to Recovery
TWRP should boot. If it does: well done
13. Optional: now flash Magisk if you want root, recommended from its release section on GitHub, or otherwise the latest "Canary" (= pre-release) version: direct-download always latest apk | latest version information. Iinstall the .apk via TWRP, then boot into your ROM and also install the .apk there.
ATTENTION: the installed TWRP will be lost if you update your ROM or flash another ROM, and the process (incl. re-installing Magisk via TWRP) has to be repeated then!
___________________________________________
Official TWRP for Nokia 6.1 references:
official page @twrp.me (latest v.3.3.1-1 2020-01-07)
source on GitHub (latest commit 2021-01-01)
RootedLee said:
Sid127 has skillfully adapted TWRP 3.6.0 for compatibility with the Nokia 6.1 Plus, see [OFFICIAL] TWRP 3.6.0 | DRG/DRG_sprout support thread. Which is great, because TWRP added Android 11 compatibility, see TWRP 3.6.0 Released (Nov 28, 2021).
I have tested his build thoroughly on my Nokia 6.1 (model 1043) with LineageOS 18.1 [OFFICIAL] installed and found all except one thing fully working, see my report over in his thread.
I do not know if the differences between the Nokia 6.1 Plus (DRG) and our Nokia 6.1 (Plate 2 aka PL2) have any effect on TWRP, or if a TWRP for a 6.1 Plus can be used for a 6.1 without any adaptations. @Raghu varma @Sid127 @theimpulson , what do you know or think?
I encourage everybody who has an Android 11 ROM installed on their Nokia 6.1 to test Sid127's 3.6.0 TWRP, and report back below. Esp. more data about the "TWRP not seeing SD if formatted as and chosen as sole Internal" issue as outlined in my post over in Sid127's thread would be of great value.
Official TWRP for Nokia 6.1 references:
official page @twrp.me (latest v.3.3.1-1 2020-01-07)
source on GitHub (latest commit 2021-01-01)
Click to expand...
Click to collapse
Sounds good ! but according to my view till Android 11, majority of the twrp files ( unofficial/official ) or whatever files should work with proper decryption/backup support. Anyway the real game begins from Android 12 twrp support with decryption. Until that no comments.. !!
@Raghu varma gotcha. Re. SD card: can you reproduce the issue (provided you do also have your SD as sole internal)?
@Raghu varma just to let you know: in Sid127's boot twrp-3.6.0_9-0-DRG_sprout.img, "Fix Recovery Bootloop" is missing in the Advanced section...
Nokia 6.1 TWRP 3.6.0/ 3.4.0 USB OTG Instructions
Best results you will have if
a) your Nokia is (close to) fully charged, andb) you use a USB flash storage with low power consumption, like a regular USB flash drivec) you use a USB C flash drive so you can connect it directly, rather than via a USB C OTG adapter
ATTENTION: on my Nokia 6.1 model 1043, USB OTG does not always turn on reliably every time. Often it needs several attempts before I see the LED on any of my flash drives light up.
When I connect them booted into my ROM (LineageOS 18.1 [Android 11]), they are always detected right away, so it's definitely an issue with TWRP not always initiating USB OTG, for some reason.
Also be aware that USB OTG does not work at all if TWRP is booted "live" without flashing.
In this example, slots are filled as follows:
A = active slot with ROM + TWRP 3.6.0 installed as Recovery Ramdisk (via Advanced > Flash Current TWRP), to enable booting into TWRP rather than the ROM's built-in recovery if choosing to boot into recovery
B = slot with TWRP flashed to boot, so it boots directly when booting up in that slot
Method A: With the device powered off and (via USB cable) connected to a power source, either one of your computer's USB ports or plugged into your charger, hold the Volume Up + Power keys. Keep holding both buttons until the “TWRP” logo appears on the screen, then release the Power key first, followed by the Volume Up key.
Once TWRP has booted all the way, disconnect your Nokia from your power source and connect it to your USB storage device. If it is equipped with a LED, you should see it light up.
Continue below at "Mutual steps"
---------
OR Method B (more complicated but in my trials better chance for success):
Connect your Nokia to your computer via USB and boot it into bootloader
fastboot --set-active=b (sets B as active slot)
fastboot reboot
-> should boot into TWRP
Once TWRP has booted all the way, disconnect your Nokia from your power source and connect it to your USB storage device. If it is equipped with a LED, you should see it light up.
"Mount" button -> USB OTG
"Reboot" button -> set Current Slot to A
still in Reboot -> tap onto "Recovery"
TWRP should boot on slot A
---------
Mutual steps:
Mount: USB OTG might already be auto-mounted. If not, try to mount. Also mount System
Backups -> select Storage: USB OTG
Backups should work. To verify, do a test Backup followed by Restore of Boot/ System/ Data, then boot System = into your ROM for verification.
Ta-daaaa
twrp-3.6.1_9-0-DRG_sprout.img | ChangeLog
Updated launcher scripts see bottom of first post (attachments).
If you were rooted, remember to re-install Magisk afterwards.
RootedLee said:
Sid127 has skillfully adapted TWRP 3.6.0 for compatibility with the Nokia 6.1 Plus, see [OFFICIAL] TWRP 3.6.0 | DRG/DRG_sprout support thread. Which is great, because TWRP added Android 11 compatibility, see TWRP 3.6.0 Released (Nov 28, 2021).
His installation procedure did not work on my Nokia 6.1 model 1043. Even with different models, you are advised to instead better proceed with my Instructions below!
I have tested his build thoroughly with [OFFICIAL] LineageOS 18.1 (Android 11) installed and found most (but not all!) featured reliably working. To spare you unnecessary time fiddling around, do read my report over in his thread.
I do not know if the differences between the Nokia 6.1 Plus (DRG) and our Nokia 6.1 (Plate 2 aka PL2) have any effect on TWRP, or if a TWRP for a 6.1 Plus can be used for a 6.1 without any adaptations. @Raghu varma @Sid127 @theimpulson , what do you know or think?
I encourage everybody who has an Android 11 ROM installed on their Nokia 6.1 to install Sid127's 3.6.0 TWRP with my instructions, then test and report back below. Esp. more data about the "TWRP not seeing SD if formatted as and chosen as sole Internal" issue as outlined in my post over in Sid127's thread would be of great value.
Installation Instructions for Nokia 6.1 (adapted from Sid127's original procedure)
1. Download the latest TWRP img file (not the .zip!) from the official TWRP for DRG_sprout downloads page
2. Download the launcher scripts .zip for your OS, Windows or macOS, attached to this post. Extract 'boot twrp-3.6.0_9-0-DRG_sprout' and place it "next" to (= into the same folder as) the downloaded image file
3. Boot your Nokia to Download (aka bootloader/ fastboot) Mode
4. Connect it to your computer with a USB cable
5. Double-click the launcher script (you can disregard the error)
6. Head to TWRP's "Advanced" section and tap onto "Flash Current TWRP" (info)
7. Sid127 has not included the "Fix Recovery Bootloop" option in the "Advanced" section. I'm always getting a off/on flashing TWRP screen when I try to reboot into recovery at this step. Therefore:
8. Download Raghu Varna's TWRP 3.4.0 for Nokia 6.1 img file
9. From the launcher scripts .zip you downloaded before, extract 'boot twrp-3.4.0-0-PL2_sprout-11.0-20200909' and place it "next" to (= into the same folder as) the downloaded image file
10. Double-click the launcher script (you can disregard the error)
11. In TWRP, go into the "Advanced" section and select the "Fix Recovery Bootloop" option
12. Head over to the "Reboot" option and reboot to Recovery
TWRP should boot. If it does: well done
13. Optional: now flash Magisk if you want root, recommended from its release section on GitHub, or otherwise the latest "Canary" (= pre-release) version: direct-download always latest apk | latest version information. In any case, rename the .apk to .zip to install via TWRP, then boot into your ROM and install the .apk.
ATTENTION: the installed TWRP will be lost if you update your ROM or flash another ROM, and the process (incl. re-installing Magisk via TWRP) has to be repeated then!
___________________________________________
Official TWRP for Nokia 6.1 references:
official page @twrp.me (latest v.3.3.1-1 2020-01-07)
source on GitHub (latest commit 2021-01-01)
Click to expand...
Click to collapse
me puedes ayudar, no se como enviar un mensaje en privado
@imarxda Eu não falo português - por favor digite sua pergunta em https://translate.google.com e cole a tradução em inglês aqui.
Também em https://translate.google.com você pode colar um endereço de Internet (URL) no campo de texto à esquerda e ter uma página inteira traduzida, veja aqui
Related
Pi Dark [substratum] - Apps on Google Play
Android Pie like Substratum Theme 🎨
play.google.com
Default Dark Theme for Substratum - Apps on Google Play
Dark material theme for the Substratum Theme Engine
play.google.com
[GUIDE/TUTORIAL/HOWTO] Motorola Moto G 4G Any version to Android 9 Pie/LineageOS 16
[GUIDE/TUTORIAL/HOWTO] Motorola Moto G 4G/LTE 2013 Peregrine XT1039 Any version to Android 9 Pie/LineageOS 16
Complete guide to install Android 9 on your Motorola Moto G 4G/LTE.
This tutorial only applies to this model, to check the correct version:
in Android, go to Settings > About, make sure it is this model: Motorola Moto G 4G 2013 Peregrine XT1039.
We will only use a USB 2.0 port and a phone fully charged (but USB3 works too).
CHANGELOG
v14. TWRP 3.5, Magisk 22, BitGApps
v13. Rework tutorial (TWRP 3.4 manipulation, latest Magisk)
v12. Latest fastboot binary, TWRP 3.4, USB drivers for 32/64 bits, Magisk root, boot logo and simpler tutorial
v11. LOS 16 2020 Septembre update (thx to @sdembiske)
v10. LOS 16 2020 May update
v9. Updated pack with TWRP recovery 3.3.1-0, fix glitches in tutorial
v8. Moved tutorial for Android 9 and updated pack with TWRP recovery 3.3.0-0 and Addonsu 16
v7. Updated pack v5 with newest TWRP and removed outdated custom kernel, added links for newest ROMs
v6. Added Google Mobile Services (GMS) certification
v5. Added custom Bootlogo flash
v4. Recovery TWRP 3.2.1-0, MD5 signature for kernel and recovery
v3. Custom kernel, overclock, recovery TWRP 3.1.1-0, no /cache in F2FS (bootloops)
v2. Moved to Android 7.1 Nougat
v1. Initial release
1 ) WHAT YOU NEED
- djibe Moto G 4G pack (~20 Mo): http://bit.ly/motoGLTEdjibepackv5
(Contains link to Motorola Bootloader unlock + flashable Bootloader unlocked logo + TWRP Recovery 3.5.0_9-0 + Magisk root + Motorola USB drivers x32/64 + fastboot)
+ ROM LineageOS Unofficial 16: https://forum.xda-developers.com/moto-g/4g-development/rom-lineageos-16-0-t3835030
Download latest build available here: https://mega.nz/file/haBkzLCA#Aw4qZ09cKi5Jqs-p6SiUaDpxD_bMOQ8PzXACT1xKhr0
Want older and stable versions ?
Use this if you want to give/sell your phone to someone.
Grab Lineage OS 14.1 for peregrine here: https://forum.xda-developers.com/t/rom-lineageos-14-1-substratum-for-moto-g-lte-peregrine.3967207/
+ BitGApps ARM 9 R13: https://xiaomifirmware.com/download/16147/
For LineageOS 14.1, use this package: https://opengapps.org/?arch=arm&api=7.1&variant=pico
+ a microSD card formatted in FAT32 : copy ROM, GApps, Magisk and logo.zip on it.
You can chose another boot logo from this collection: https://forum.xda-developers.com/showthread.php?t=2686441
And download the file according here: https://androidfilehost.com/?w=files&flid=49201
2 ) INSTALL DRIVERS
Install Motorola 64 bits drivers (32 or 64 bits depending on your Windows version).
Then plug Moto G to PC and let the install go on.
3 ) BACKUP YOUR DATA
When your phone is connected to Windows, search for all .jpg, .mp3, .mp4 files on your phone and make copies on your PC.
Then, with an app like Backupyourmobile, backup all your SMS, MMS, contacts.
Make sure the backup is located on microSD card.
4 ) UNLOCK BOOTLOADER
Update your Moto G to the latest official Android 5.1 Lollipop.
In Android, go to Settings > About > Updates. Make sure you have latest version.
Then, go to Motorola website (shortcut in my archive or right below):
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b[/URL]
Subscribe using your Google Account or email.
Shut down phone.
Power it on in fastboot mode: Hold Power et Volume- during 3-4 secondes and release.
Screen is black with lines of text, starting with AP Fastboot Flash Mode (S).
Connect phone to USB2, wait for fastboot drivers to install.
In Windows, select the /flash subfolder you unzipped from my archive.
On keyboard, make a combo Shift + right click -> Open command windows here.
Write this command in Windows terminal :
Code:
fastboot oem get_unlock_data
confirm using Enter.
Command sends back a message like this :
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
OKAY [ 0.146s]
Select all text -> right click -> select all.
Open a notepad editor, and paste text.
Rework the text to get it on 1 line, and remove all spaces and "(bootloader)" messages.
It should look like this : 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Now, copy this text line and paste it in Motorola website : https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Below, click on Verify Eligibility.
Next, I Agree.
You get the unlock key by email, looking like : 56ITMEJ2BFHX5JVXMA4J
Use this unlock key in the following Windows command :
Code:
fastboot oem unlock YOUR_UNLOCK_CODE
Confirm with enter and wait a moment ... till success is confirmed : "Unclock Completed, wait to reboot",
don't disconnect it from PC !
phone reboots to Android with a blank screen "Warning, Bootloader unlocked".
Keep Windows command opened.
4 ) FLASH RECOVERY & BOOTLOADER LOGO
Shutdown phone again.
Power on in fastboot mode: Hold Power et Volume- during 3-4 secondes and release.
In Windows command, use this command:
Code:
fastboot flash recovery twrp-3.5.0_9-0-peregrine.img
confirm with Enter.
Terminal confirms : "Finished. Total time: 0.670s".
### In bootloader screen, you see error "mismatched partition size (recovery)" ? No problem. TWRP is smaller than stock recovery.
### For future TWRP updates, TWRP binary can be flashed from TWRP recovery itself (Install > Install Image)
Now, on the phone in fastboot mode, press Volume- to select the Recovery option. Confirm with Volume+.
Welcome to TWRP 3.5 recovery.
TWRP asks for Keep System Read Only ? -> check "Never show this screen during boot again" and Swipe to Allow Modifications.
### You don't see this waring screen? Then you'll get "TWRP unable to mount storage" while trying to wipe partitions.
### > in TWRP, go to Reboot > Recovery so Recovery will refresh and popup the partition writing privilege.
5 ) WIPE PARTITIONS
In TWRP home screen, go to Wipe > Format data.
Type yes and confirm to format partition.
Go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage (if you really made a backup from step 2), then Swipe to Wipe,
then back.
### Don't try F2FS, it won't work.
Go to Reboot > Recovery.
Let phone reboot.
6 ) FLASH ROM, OPENGAPPS AND BOOTLOGO
Back to TWRP Home menu. Then tap on Install > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
then Add more Zips > BiTGApps*.zip,
optional: then Add more Zips > logo*.zip,
then Swipe to confirm Flash.
Wait for operation to end.
### Don't flash Magisk now
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Wait for the phone to boot during 10 minutes.
7 ) ROOT ACCESS AND DEVELOPER MENU
With Magisk, you are root once phone is started. No extra manipulation needed.
For developer menu: open the Settings menu > About Phone.
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Now go to Settings menu > System > Developer settings.
Switch Advanced restart on.
Now use menus to Restart > Recovery.
Back to TWRP, go to Install > magisk*.zip
Reboot.
You are root.
8 ) ENHANCE PHONE
Go to Settings > Developer options
In drawing, set Windows animation scale, Transition animation scale to Animation off (or 0.5x).
Install Greenify, grant Superuser privileges and follow tutorial to set as System app.
Switch on:
- Smart hibernation > Enabled
- Light hibernation
- Aggressive sleep
- Automatic hibernation
That's it.
### When I play music, it comes out of the phone speaker but not the headphone jack.
Use stock AudioFX app to fix this.
Enjoy,
djibe
New version to upgrade Moto G to Android 7.1 Nougat
Enhenced tutorial
Updated version with overclocking of the Moto G 4G
Overclocking introduced
Tutorial updated for better performances
TWRP 3.2 and MD5 file verification for Kernel flash
Added : flash bootloader unlocked screen at boot.
New version of tutorial to obtain the Google Play Certification.
Do you think I should upgrade tutorial for Lineage OS 15.1 ?
Thread and pack updated with latest LOS updates.
guide updated
Tutorial updated
Hi guys, tutorial updated to enjoy Android 9 on your old Moto G 4G !!!
Enjoy
Added download links for older Android versions if needed
Checked for newer packages.
Tutorial is up to date.
Works, except no sound from headphone jack
This worked for me today which I was chuffed about until I started to use the phone and found that when I played music it came out of the phone speaker but not the headphone jack. Any ideas?
Robert Steed said:
This worked for me today which I was chuffed about until I started to use the phone and found that when I played music it came out of the phone speaker but not the headphone jack. Any ideas?
Click to expand...
Click to collapse
I've just found the solution to this which is to disable Audio FX.
@Robert Steed. thx for sharing.
@Robert Steed. thx for sharing.
NOTE:
This guide is meant for this thread: https://forum.xda-developers.com/nokia-7-plus/development/9-0-miui-10-nokia-fihgsisdm66064-t3900312
This guide may unusable on newer builds in the future.
In case you want to restore back to stock, firmware can be downloaded from https://fih-firmware.hikaricalyx.com/index_en.html and you can flash it with either patched OST LA or NOST.
It's tested on following models:
PL2 Nokia 6.1 TA-1054
DRG Nokia X6 TA-1099
C1N Nokia 7 TA-1041
B2N Nokia 7 Plus TA-1062
Flash it at your own risk if your type is not listed above.
To Chinese users:
请点击下面的链接阅读中文版教程。
如需转载请通过 Coolapk 私聊联系我。
Please read Chinese guide from here: https://www.coolapk.com/feed/103010...id=1121588&shareFrom=com.coolapk.market_9.0.1
Click to expand...
Click to collapse
Let me introduce you how to flash MIUI build.
In this guide, we will take "Nokia-miui10-2019-02-13.img.xz" build for example.
Part 1: Bootloader Unlock
I won't introduce you how to unlock the bootloader for your phones here.
Part 2: Install latest Android Pie build
I'm not sure about latest Android Pie build for Global Android One Devices, but AFAIK the Chinese builds we've tested are all [fih_codename]-347C-0-00CN-B04, January 2019 Update.
Make sure you have installed this build.
For your convenience, you can download following full OTA that we tested:
B2N-347C-0-00CN-B04: https://ota-filesite.c2dms.com/SWImage/500002276
Part 3: Flash the system itself
Download packages from ROM topic, and make sure you have extracted the img.xz file.
You must use Platform Tools provided by Google: https://developer.android.com/studio/releases/platform-tools
I'm not sure if Minimal ADB and Fastboot package is usable.
Boot your phone to Fastboot / Download mode, then execute this command:
Code:
.\fastboot flash system D:\Nokia-miui10-2019-02-13.img
To flash the system image to your current slot, no matter if it's slot A or B.
Format the userdata partition and reboot bootloader again to prevent temporarily boot failure:
Code:
.\fastboot -w reboot-bootloader
Part 4: Install permission patches to patch vendor, and root it
Boot into TWRP temporarily, but it depends on you if you want to install TWRP permanently:
Code:
https://forum.xda-developers.com/nokia-7-plus/development/recovery-twrp-3-2-3-0-t3892644
In this example we do not install TWRP permanently.
Swipe the button to allow system modification, and connect your phone to PC, copy FBE_Disabler.zip, Magisk-v18.1.zip, Permissiver_v2.zip and vendor-2019-02-16.zip you downloaded to internal storage of your phone.
In case you want to ask, Magisk can be downloaded from https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
Tap "Mount" on your phone and check both "vendor" and "system" partition to mount them.
Click back, Tap "Install", and install these 4 zip packages in character order.
After installed, please reboot your phone and ignore the TWRP Official App installation prompt.
Please wait at least 3 minutes for booting.
After your phone boots, you'll find the default language is Simplified Chinese. Here's how to to change the language to non-Chinese:
- Open "设置" (Settings)
- Tap "更多设置" (More Settings)
- Tap "语言和输入法" (Languages and Input)
- Tap "语言" (Language)
- Choose your own language
Hope you can find it lol.
Then, please download and install Magisk Manager on your phone and reboot your phone.
Part 5: Fix Xiaomi Account issue, and GMS feature
Copy "MIUI_Account_Fix.zip" to Download directory of internal storage, and add this as Magisk Module under Magisk Manager, then reboot.
If it's too difficult for you to enter your phone to MTP mode, here's the trick:
- Connect your phone to PC when screen UNLOCKED
- When the phone prompts "USB is connected", tap the prompt
- Tap "Data Transfer (MTP)"
- You may need to drag the notification center and choose again
- Copy required files
Click to expand...
Click to collapse
Copy gms.apk to your phone and install it on your phone directly. Install it may take few minutes and please wait patiently. After installation completed, you can login both Xiaomi Account and Google Account properly.
I needn't to mention how to replace the camera, it's pretty easy.
That wraps up the whole guide.
Done a nice work mate ...
Wondering if this could run on the Aquos S3 6/128 .. it's basically the same hardware
henri_p said:
Wondering if this could run on the Aquos S3 6/128 .. it's basically the same hardware
Click to expand...
Click to collapse
No you can't, as I've tested it on Sharp Aquos S2 SS2 and SAT.
FIH already abandoned both S2 and S3 and they even don't release Android 9.0 for them unlike Japanese Sharp Android One devices.
Pretty much sucks, I have an S3 6/128 with locked bootloader, seems it sadly going to stay at Oreo with that silly UI on top of it :crying: ... too bad, the device looks great and is of a good quality built
can i flash at without bootunlocked i have nokia 7
Faisal kacho said:
can i flash at without bootunlocked i have nokia 7
Click to expand...
Click to collapse
No
k3dar7 said:
No
Click to expand...
Click to collapse
Thankz If i use ost tOol then
In my nokia 6.1 plus it couldn't install .. when i try to flashing system img file its eror volume full ..
Can anyone fixed this problem?
can i install this gsi on my nokia 7 plus global version?
Hr bro, I get the same error as u mentioned above. Please reply back if u have succeeded.
---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------
rahul387 said:
In my nokia 6.1 plus it couldn't install .. when i try to flashing system img file its eror volume full ..
Can anyone fixed this problem?
Click to expand...
Click to collapse
Hi bro, I get the same error as mentioned above reply back if u have succeeded.
how to
@hikari_calyx
how to flash [fih_codename]-347C-0-00CN-B04, January 2019 Update. ? i try OST6.2.8 but not flash finish
my device DRG Nokia X6 TA-1099 (00CN_2_21F) bootloader unlock
help my how can i flash 347C-0-00CN-B04
today i download DRG-347C-0-00CN-B04.full.Zip and trying but failed
how can i installed MIUI help me
hikari_calyx said:
NOTE:
This guide is meant for this thread: https://forum.xda-developers.com/nokia-7-plus/development/9-0-miui-10-nokia-fihgsisdm66064-t3900312
This guide may unusable on newer builds in the future.
In case you want to restore back to stock, firmware can be downloaded from https://fih-firmware.hikaricalyx.com/index_en.html and you can flash it with either patched OST LA or NOST.
It's tested on following models:
PL2 Nokia 6.1 TA-1054
DRG Nokia X6 TA-1099
C1N Nokia 7 TA-1041
B2N Nokia 7 Plus TA-1062
Flash it at your own risk if your type is not listed above.
Let me introduce you how to flash MIUI build.
In this guide, we will take "Nokia-miui10-2019-02-13.img.xz" build for example.
Part 1: Bootloader Unlock
I won't introduce you how to unlock the bootloader for your phones here.
Part 2: Install latest Android Pie build
I'm not sure about latest Android Pie build for Global Android One Devices, but AFAIK the Chinese builds we've tested are all [fih_codename]-347C-0-00CN-B04, January 2019 Update.
Make sure you have installed this build.
For your convenience, you can download following full OTA that we tested:
B2N-347C-0-00CN-B04: https://ota-filesite.c2dms.com/SWImage/500002276
Part 3: Flash the system itself
Download packages from ROM topic, and make sure you have extracted the img.xz file.
You must use Platform Tools provided by Google: https://developer.android.com/studio/releases/platform-tools
I'm not sure if Minimal ADB and Fastboot package is usable.
Boot your phone to Fastboot / Download mode, then execute this command:
Code:
.\fastboot flash system D:\Nokia-miui10-2019-02-13.img
To flash the system image to your current slot, no matter if it's slot A or B.
Format the userdata partition and reboot bootloader again to prevent temporarily boot failure:
Code:
.\fastboot -w reboot-bootloader
Part 4: Install permission patches to patch vendor, and root it
Boot into TWRP temporarily, but it depends on you if you want to install TWRP permanently:
Code:
https://forum.xda-developers.com/nokia-7-plus/development/recovery-twrp-3-2-3-0-t3892644
In this example we do not install TWRP permanently.
Swipe the button to allow system modification, and connect your phone to PC, copy FBE_Disabler.zip, Magisk-v18.1.zip, Permissiver_v2.zip and vendor-2019-02-16.zip you downloaded to internal storage of your phone.
Tap "Mount" on your phone and check both "vendor" and "system" partition to mount them.
Click back, Tap "Install", and install these 4 zip packages in character order.
After installed, please reboot your phone and ignore the TWRP Official App installation prompt.
Please wait at least 3 minutes for booting.
After your phone boots, you'll find the default language is Simplified Chinese. Here's how to to change the language to non-Chinese:
- Open "设置" (Settings)
- Tap "更多设置" (More Settings)
- Tap "语言和输入法" (Languages and Input)
- Tap "语言" (Language)
- Choose your own language
Hope you can find it lol.
Then, please download and install Magisk Manager on your phone and reboot your phone.
Part 5: Fix Xiaomi Account issue, and GMS feature
Copy "MIUI_Account_Fix.zip" to Download directory of internal storage, and add this as Magisk Module under Magisk Manager, then reboot.
Copy gms.apk to your phone and install it on your phone directly. Install it may take few minutes and please wait patiently. After installation completed, you can login both Xiaomi Account and Google Account properly.
I needn't to mention how to replace the camera, it's pretty easy.
That wraps up the whole guide.
Click to expand...
Click to collapse
Heya,
This is a guide aimed on helping you to switch to a custom rom from the stock firmware.
For any questions, feel free to join our Telegram groups.
PREREQUISITES
1) Stock rom recommended by the maintainer of the rom that you want to flash. Typically for Q roms, 10.0.13.0, 10.0.18.0, 11.0.4.0 work well. (Link here).
2) The custom rom you want (Custom Rom list here).
3) Platform-Tools by Google for adb and fastboot (Link here).
4) TWRP Recovery Image and installer zip (Link here and here).
5) Force Encryption Disabler (Link here).
6) MiFlash by Xiaomi (Download the latest version from here).
7) An unlocked Bootloader
INTRODUCTION
Installing a custom ROM on an Android phone used to be a walk in the park. However, some newer phones, like Xiaomi Mi A2 Lite, have what's called an A/B partition layout. This facilitates an update process on stock ROMs, however it makes it harder to install and develop custom ROMs. You can read more about A/B partitions here.
The upshot is that Mi A2 Lite doesn't have a recovery partition. Instead, when you install TWRP, it gets installed to the boot partition. Which means that every time you install or update a ROM, you will need to re-flash the recovery ZIP. One more thing to keep in mind is that the ROM always gets installed to another slot. Meaning, if you're currently in the slot B, the ROM will be installed to slot A and vice versa.
INSTALLATION PROCESS
A) Installing Stock Rom as a Base
1) Extract the platform tools zip file and open the new extracted folder.
2) Open a command line / PowerShell window in that folder by holding the shift key and right clicking into the empty space of the folder. Press the "open PowerShell / Command line window here" option.
3) Plug the device into your PC with a Micro USB cable.
4) Hold down the power button and the volume down button for ~10-15 seconds. You should see the fastboot screen.
5) In the Command Line / PowerShell window type: "cmd" and hit Enter. Then, type "fastboot oem edl" and hit Enter again. If your device can't get detected (Stuck on "Waiting for any device") and nothing happens on your phone's screen, check the notes section of the guide below.
This will reboot your device into edl mode (Emergency Download Mode). The screen should turn off and the led indicator should be blinking indefinitely
5) Extract the MiFlash zip file and open the extracted folder
6) Launch the Mi Flash application by double clicking the XiaoMiFlash.exe file
7) Install the necessary drivers for MiFlash (Click ok in the dialogues).
8) Extract the downloaded stock rom.
9) Press the "select" button and point into the previously extracted folder. (There should be an images folder and some other sh and bat files in the same directory).
10) Click "Clean All" all in the bottom left.
11) Press "Refresh".
12) Your device should appear (COM port). (If not, check the notes section of the guide below)
13) Click "Flash". The process will take around 200-350 seconds.
14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots.
DO NOT UPDATE OR MAKE ANY MODIFICATIONS IN THE BOOTED STOCK ROM IN ANY WAY.
B) Install the Custom Rom
(If you want to flash PixelExperience Official, continue with this guide by the PE team. If you face any issues, check the NOTES section of this guide)
1) Paste the downloaded custom rom (zip file) into your sd card and insert it into your phone.
2) Hold down the power button alongside with the volume down button. You should see the fastboot screen shortly.
3) Copy the TWRP IMG file to the platform-tools folder
4) Copy the TWRP Installer Zip file to your SD Card.
5) Open a cmd / PowerShell window in the platform-tools folder (like Step 2 of Section A)
6) Type: "fastboot boot twrp-3.4.0-3-unofficial-daisy.img".
7) You will see the recovery on your phone, prompting you to enter the password. Choose "Cancel"
8) Go into the main menu of TWRP. Press Wipe, then "Format Data". Type "yes" and press enter. (Keep in mind that all of your data will be wiped and there is no going-back).
9) Go back and press "Advanced Wipe". and select everything except "SD Card". Swipe to confirm the action.
10) Go into the main menu. Press "Install", "Select Storage" and select "Micro SD Card".
11) Flash the zips in this order (Click on them and swipe to confirm the action)
- Custom ROM
- TWRP Installer ZIP
- Force Encryption Disabler
DO NOT install Magisk, GApps or anything else yet, we will do that later!
(Some ROMs do not require Force Encryption Disabler as Force Encryption is disabled by default, although flashing that zip won't hurt anything)
After everything is done, DON'T TAP REBOOT YET. Instead, go back to the main menu, choose "Reboot", change the slot (e.g. if it says "Current Slot: A", tap "Slot B", vice versa.
12) Tap "Recovery" in the reboot menu.
13) Copy anything you would like to install on your phone (Magisk, Gapps, etc.) and flash it the usual way (optional)
(Some roms like EvolutionX and Pixel Experience have Gapps built-in so do not flash any gapps package in such roms.)
(Flashing Magisk isn't necessary but some roms may need it for CTS / SafetyNet to pass.)
14) Reboot to System and enjoy your Rom.
DIRTY FLASHING / MANUALLY INSTALLING A NEW BUILD
Manually Installing a new ROM build a.k.a Dirty Flashing is also somewhat complicated on A/B phones like Xiaomi Mi A2 Lite. However, if you follow these steps, you should be good to go:
1) Download the new build and copy it to your phone.
2) Reboot into the recovery mode (hold power + volume up) and flash the ROM ZIP.
3) Here's where the fun part begins: since we've just overwritten the boot partition, we don't have TWRP anymore, so we need to flash it again.
4) Once again, after you're done, don't tap on "Reboot" yet, instead, go back to the main menu, change the slot, and tap "Recovery".
5) Once the phone boots into recovery again, flash Magisk (optional) and Gapps if you had flashed them before.
6) Reboot the phone to system.
PSA: Dirty Flashing rom builds may cause unexpected problems and for this reason, it is recommended to perform a clean flash (Format Data) every time you want to flash a new build of your rom or switch to a different one.
SEAMLESS UPDATES
LOS Updater (which is used in Lineage OS and many other roms) downloads the ROM ZIP automatically and installs it to the inactive slot, which spares us the need to reboot into recovery. Thus, these updates look like OTA updates from the stock rom. However, there are a few gotchas here too:
After the OTA is installed, DON'T TAP ON "REBOOT". Instead, go to Magisk Manager and install a module called "TWRP A/B Retention Script" (you should be able to find it in the "Downloads" section)
Then, go to the Manager's main menu, tap on "Install" and choose "Install to inactive slot (After OTA)"
After the installation process is completed, you can reboot. You have to repeat the process every time you get an OTA if you want to keep Magisk and TWRP on your newly updated system.
- - - - NOTES - - - -
- Windows is the only supported operating system by this guide.
- If when you type a fastboot command (like fastboot oem edl) it just shows "Waiting for any device", it is probably due to missing drivers. See this page on how to install the Google USB driver that is required for fastboot to detect your phone.
- If you have an older version of Windows like 8, 8.1, 7 etc, your device might not get detected by MiFlash due to missing drivers. In this case, you will have to install the Qualcomm EDL driver on your own (Link here). Windows 10 finds and installs the driver automatically.
- If SafetyNet doesn't pass, ensure you have not modified anything in the system partition and that you have enabled Magisk Hide in Magisk Manager. If it still does not pass, try using the "MagiskHide Props Config" Magisk Module (More Info here). If it still doesn't work, try reinstalling your rom. If there are still issues regarding safetynet, it may be the rom's problem or google's new server-side changes might have affected your device (Learn more here)
- If some apps detect root and do not function properly (like banking apps), make sure SafetyNet passes. Also, you can try selecting the app in the MagiskHide section of Magisk Manager. The "Hide Magisk Manager" option in the Settings of Magisk Manager can be useful too.
- MIUI Roms / Ports have a special installation procedure (different from the one presented here) and thus, it is recommended that you take a look at their respective xda thread(s) and / or in the appropriate telegram group.
- If your download speed is slow when downloading the stock rom base, try using a download manager like IDM. If the speed is still slow, it is an issue with xiaomi's servers and there is nothing that can be done about it.
- 3.18 kernels such as butterfly, dragonheart etc, do NOT work and / or cause unexpected issues in updated custom roms because these roms use newer 4.9 kernels. The recommended custom 4.9 kernel is Sleepy and it can be found on Telegram (https://t.me/Laciakerneltg). Therefore, there will be no support offered if you are using a 3.18 kernel in a ROM that uses 4.9 kernels (all new UPDATED roms do)
- If your fingerprint doesn't work / partially works, flash this fix in twrp (This issue exists in the official version of pixel experience)
- Android 11 ROMs might require extra steps that are not mentioned here, please follow the respective maintainer's installation guide for now.
CREDITS
tkchn for some parts of the guide
@Offain for FED
@FDoop for some links and guides
Amazing ?
Detailed Guide
LinkBoi said:
Heya,
This is a guide aimed on helping you to switch to a custom rom from the stock firmware.
For any questions, feel free to join our Telegram groups.
PREREQUISITES
1) Stock rom recommended by the maintainer of the rom that you want to flash. Typically for Q roms, 10.0.13.0, 10.0.18.0, 11.0.4.0 work well. (Link here).
2) The custom rom you want (Custom Rom list here).
3) Platform-Tools by Google for adb and fastboot (Link here).
4) TWRP Recovery Image and installer zip (Link here and here).
5) Force Encryption Disabler (Link here).
6) MiFlash by Xiaomi (Download the latest version from here).
INTRODUCTION
Installing a custom ROM on an Android phone used to be a walk in the park. However, some newer phones, like Xiaomi Mi A2 Lite, have what's called an A/B partition layout. This facilitates an update process on stock ROMs, however it makes it harder to install and develop custom ROMs. You can read more about A/B partitions here.
The upshot is that Mi A2 Lite doesn't have a recovery partition. Instead, when you install TWRP, it gets installed to the boot partition. Which means that every time you install or update a ROM, you will need to re-flash the recovery ZIP. One more thing to keep in mind is that the ROM always gets installed to another slot. Meaning, if you're currently in the slot B, the ROM will be installed to slot A and vice versa.
INSTALLATION PROCESS
A) Installing Stock Rom as a Base
1) Extract the platform tools zip file and open the new extracted folder.
2) Open a command line / PowerShell window in that folder by holding the shift key and right clicking into the empty space of the folder. Press the "open PowerShell / Command line window here" option.
3) Plug the device into your PC with a Micro USB cable.
4) Hold down the power button and the volume down button for ~10-15 seconds. You should see the fastboot screen.
5) In the Command Line / PowerShell window type: "cmd" and hit Enter. Then, type "fastboot oem edl" and hit Enter again. If your device can't get detected (Stuck on "Waiting for any device") and nothing happens on your phone's screen, check the notes section of the guide below.
This will reboot your device into edl mode (Emergency Download Mode). The screen should turn off and the led indicator should be blinking indefinitely
5) Extract the MiFlash zip file and open the extracted folder
6) Launch the Mi Flash application by double clicking the XiaoMiFlash.exe file
7) Install the necessary drivers for MiFlash (Click ok in the dialogues).
8) Extract the downloaded stock rom.
9) Press the "select" button and point into the previously extracted folder. (There should be an images folder and some other sh and bat files in the same directory).
10) Click "Clean All" all in the bottom left.
11) Press "Refresh".
12) Your device should appear (COM port). (If not, check the notes section of the guide below)
13) Click "Flash". The process will take around 200-350 seconds.
14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots.
DO NOT UPDATE OR MAKE ANY MODIFICATIONS IN THE BOOTED STOCK ROM IN ANY WAY.
B) Install the Custom Rom
1) Paste the downloaded custom rom (zip file) into your sd card and insert it into your phone.
2) Hold down the power button alongside with the volume down button. You should see the fastboot screen shortly.
3) Copy the TWRP IMG file to the platform-tools folder
4) Copy the TWRP Installer Zip file to your SD Card.
5) Open a cmd / PowerShell window in the platform-tools folder (like Step 2 of Section A)
6) Type: "fastboot boot twrp-daisy-3.3.1.0-offain.img".
7) You will see the recovery on your phone, prompting you to enter the password. Choose "Cancel"
8) Go into the main menu of TWRP. Press Wipe, then Advanced Wipe and select everything except "SD Card".
9) Go back and press "Format Data".
10) Go into the main menu. Press "Install", "Select Storage" and select "Micro SD Card".
11) Flash the zips in this order (Click on them and confirm the action) :
- Custom ROM
- TWRP Installer ZIP
- Force Encryption Disabler
DO NOT install Magisk, GApps or anything else yet, we will do that later!
PSA: Some ROMs do not require Force Encryption Disabler as Force Encryption is disabled by default.
After everything is done, DON'T TAP REBOOT YET. Instead, go back to the main menu, choose "Reboot", change the slot (e.g. if it says "Current Slot: A", tap "Slot B", vice versa.
12) Tap "Recovery" in the reboot menu.
13) Copy anything you would like to install on your phone (Magisk, Gapps, etc.) and flash it the usual way (optional)
PSA: Some roms like EvolutionX and Pixel Experience have Gapps built-in so do not flash any gapps package in such roms.
PSA2: Flashing Magisk isn't necessary but some roms may need it for CTS / SafetyNet to pass.
14) Reboot to System and enjoy your Rom.
DIRTY FLASHING / MANUALLY INSTALLING A NEW BUILD
Manually Installing a new ROM build a.k.a Dirty Flashing is also somewhat complicated on A/B phones like Xiaomi Mi A2 Lite. However, if you follow these steps, you should be good to go:
1) Download the new build and copy it to your phone.
2) Reboot into the recovery mode (hold power + volume up) and flash the ROM ZIP.
3) Here's where the fun part begins: since we've just overwritten the boot partition, we don't have TWRP anymore, so we need to flash it again.
4) Once again, after you're done, don't tap on "Reboot" yet, instead, go back to the main menu, change the slot, and tap "Recovery".
5) Once the phone boots into recovery again, flash Magisk (optional) and Gapps if you had flashed them before.
6) Reboot the phone to system.
PSA: Dirty Flashing rom builds may cause unexpected problems and for this reason, it is recommended to perform a clean flash (Format Data) every time you want to flash a new build of your rom or switch to a different one.
SEAMLESS UPDATES
LOS Updater (which is used in Lineage OS and many other roms) downloads the ROM ZIP automatically and installs it to the inactive slot, which spares us the need to reboot into recovery. Thus, these updates look like OTA updates from the stock rom. However, there are a few gotchas here too:
After the OTA is installed, DON'T TAP ON "REBOOT". Instead, go to Magisk Manager and install a module called "TWRP A/B Retention Script" (you should be able to find it in the "Downloads" section)
Then, go to the Manager's main menu, tap on "Install" and choose "Install to inactive slot (After OTA)"
After the installation process is completed, you can reboot. You have to repeat the process every time you get an OTA if you want to keep Magisk and TWRP on your newly updated system.
- - - - NOTES - - - -
- Windows is the only supported operating system by this guide.
- If when you type a fastboot command (like fastboot oem edl) it just shows "Waiting for any device", it is probably due to missing drivers. See this page on how to install the Google USB driver that is required for fastboot to detect your phone.
- If you have an older version of Windows like 8, 8.1, 7 etc, your device might not get detected by MiFlash due to missing drivers. In this case, you will have to install the Qualcomm EDL driver on your own (Link here). Windows 10 finds and installs the driver automatically.
- If SafetyNet doesn't pass, ensure you have not modified anything in the system partition and that you have enabled Magisk Hide in Magisk Manager. If it still does not pass, try using the "MagiskHide Props Config" Magisk Module (More Info here). If it still doesn't work, try reinstalling your rom. If there are still issues regarding safetynet, it may be the rom's problem or google's new server-side changes might have "hit" your device (Learn more here)
- If some apps detect root and do not function properly (like banking apps), make sure SafetyNet passes. Also, you can try selecting the app in the MagiskHide section of Magisk Manager. The "Hide Magisk Manager" option in the Settings of Magisk Manager can be useful too.
- MIUI Roms / Ports have a special installation procedure (different from the one presented here) and thus, it is recommended that you take a look at their respective xda thread(s) and / or in the appropriate telegram group.
- If your download speed is slow when downloading the stock rom base, try using a download manager like IDM. If the speed is still slow, it is an issue with xiaomi's servers and there is nothing that can be done about it.
- 3.18 kernels such as butterfly, dragonheart etc, do NOT work and / or cause unexpected issues in updated custom roms because these roms use newer 4.9 kernels. The recommended custom 4.9 kernels are: Sleepy (can be found in Telegram) and Loki (Link here). Therefore, there will be no support offered if you are using a 3.18 kernel in a rom that uses 4.9 kernels (all new UPDATED roms do)
CREDITS
tkchn for some parts of the guide
@offain for TWRP IMG and FED
@FDoop for some links and guides
@ScaryMen1325 for fixing MTP in @offain's twrp for 4.9 kernels
Everyone who builds Custom Roms
Click to expand...
Click to collapse
Hi LinkBoi,
Hope You're Doing Great.
Detailed Guide...
Really Appreciated For Your Hardwork.
Thanks,
MUHAMMAD Asif Qasim
Wow, so much information in one place. Thanks for spending your time on this.
Pat750 said:
Wow, so much information in one place. Thanks for spending your time on this.
Click to expand...
Click to collapse
Thanks for the positive feedback
Thanks for the great and detailed work..
I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again
mancarv said:
I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again
Click to expand...
Click to collapse
Not quite the same... But the stock rom .tgz can be flashed using fastboot. That's what I do, since my main system is a Mac.
I think EDL/miflash can fix some things fastboot can't (eg. partition table).
For "flash stock and erase data" it should be fine.
mancarv said:
I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again
Click to expand...
Click to collapse
Are you on mac or linux? For, mac, I know little about the process. Edl flashing is certainly not possible in mac os. Regarding linux, there is qdl if you wanna try it, but i do not recommend it. For fastboot flashing, you can try the .sh scripts in the stock rom's folder but no support will be given.
Guys thanks for your answers, sorry for being late I have been occupied. I'm on Linux, Ubuntu 18.04. I didn't remember that stock roms come with sh script. Has been a long time since I did this kind stuff and it was with a ZTE Open with Firefox OS :laugh: Maybe I'm gonna try downgrade, I'm testing the last stock version and it is working good so far .
Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?
93starletgt said:
Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?
Click to expand...
Click to collapse
Yes
93starletgt said:
Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?
Click to expand...
Click to collapse
depends one which stock version you're on. The ones I have recommended have been tested and work well. Users have reported that latest stock q works well too. From my experience, anything over 10.0.13.0 is good but if you have weird bugs, try to flash any of the recommended stock roms first and see if those bugs persist.
TWRP Recovery Update
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 4/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Merged all TWRP 3.4.0-0 Changes
• Based on @TogoFire's OFRP device tree:
- Enabled System-as-Root
- Updated recovery.fstab
- Updated Rootdir & Blobs
- Added bootctrl from Stock Q
- Updated kernel, in the bootable image, to 4.9.233
- Fixed stability issues
- Fixed mounting issues
Note:
- The Tap-to-wake gesture was removed
- Decryption doesn't work (it never did)
Credits:
- @TogoFire for the device tree (Massive kudos to him for making a fully stable tree)
- @lslx_22S99176LF, @LmAo_device for testing
- @ScaryMen1325 for the MTP fix
LinkBoi said:
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 4/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Merged all TWRP 3.4.0-0 Changes
• Based on @TogoFire's OFRP device tree:
- Enabled System-as-Root
- Updated recovery.fstab
- Updated Rootdir & Blobs
- Added bootctrl from Stock Q
- Updated kernel, in the bootable image, to 4.9.233
- Fixed stability issues
- Fixed mounting issues
Note:
- The Tap-to-wake gesture was removed
- Decryption doesn't work (it never did)
Credits:
- @TogoFire for the device tree (Massive kudos to him for making a fully stable tree)
- @lslx_22S99176LF, @LmAo_device for testing
- @ScaryMen1325 for the MTP fix
Click to expand...
Click to collapse
Original post has been updated aswell
Twrp update 2
If you have the recovery loop issue (the device is always booting to recovery), go to advanced > fix recovery loop, confirm the action and it should be fixed )
Twrp update 2
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 5/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Based on @TogoFire's TWRP device tree:
- Updated kernel image in the bootable image to 4.9.234.
- Fixed USB, to be recognised better.
- Added the double-tap-to-wake (dt2w) gesture. (When the screen is off, you can press it twice to open it)
- Remove the reboot to EDL option as it didn't work
Note:
- Decryption doesn't work
- If you have any issues regarding double tap to wake, try to delete the .twrps file in the TWRP folder (can be found in the Internal Storage).
Credits:
- @TogoFire for the device tree (all of the work is his)
- @lslx_22S99176LF, @proxer05 for testing
Awesome guide, thanks a lot!
I have a question, if i want to install some patches and fixes throgth TWRP, is necessary to change the slot before reboot?
LinkBoi said:
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 5/9/2020
Click to expand...
Click to collapse
Is this using some kind of Magisk based stuff to install or something because between this and the Force-enc disabler zip linked in this thread, something is causing my banking app to think my phone is rooted even though it isn't. I'd rather avoid having to install magisk purely for the sake of making my bank app work properly, so what's with this?
EDIT: well, I installed magisk anyway and got safetynet passing + magiskhide set up but the bank app still thinks im rooted so rip me i guess
EDIT 2: "Back in March of 2020, Google made some changes to SafetyNet that permanently trips when your bootloader is unlocked no matter what you do." welp,
Wher can I find "TWRP A/B Retention Script" in Magisk?
There is a new Design with no Download Selection.
If you've recently purchased a Xiaomi Poco X3 Pro, but were on the fence about using it until an AOSP ROM became available then you're in luck. Kudos to @kubersharma for his contribution by providing us the first official AOSP release, ArrowOS v11.0 [vayu].
Now, throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. These are fully detailed instructions to make it easier for newbs.
I've spent the better part of my day figuring all of this stuff out so hopefully you won't go through the trouble I did. PLEASE DO NOT PM ME FOR HELP. REPLY TO THIS GUIDE BELOW, THANKS. NOW LET'S BEGIN!!!
UNLOCK BOOTLOADER
1. Unlock the bootloader with Xiaomi Unlocker tool.
a. Be aware this process will factory reset the device before proceeding.
b. Download the Mi Unlock app onto your PC. Extract the contents within the zip file into an empty folder then run the app.
c. Register for Xiaomi account and sign in with your Mi Account.
d. Your Mi Account must be added to your Mi Settings
Sign into your Mi Account on the device.
Go to Settings –> About Phone –> tap on MIUI version (For POCO) until it says Developer options is enabled.
Back out of About Phone, Additional Settings –> Developer options –> Mi Unlock status.
Agree, then "Add account and device".
e. Shut down your phone manually, and hold Vol down + Power button to enter Fastboot mode.
Download and install the latest Xiaomi USB Drivers or here (or Google's latest USB drivers for Windows if all else fails) for your PC.
Connect the device to the computer via USB cable, and confirm that your phone shows up recognized as "Android Bootloader Interface" (in Device Manager), and click "Unlock" in the Unlock app.
NOTE: If Windows does not recognize the device due to it automatically installing the wrong "Kedacom Device Driver" then you will have to manually install the drivers for "Android ADB Interface/Android Bootloader Interface".
f. After your first initial unlock attempt, you MUST wait 168 hours before unlock process can fully complete.
Wiping the device or removing the Mi account from the device could result in the timer being reset.
g. After the waiting period expires, click "Unlock" in the Unlock app. You will notice the phone will restart followed by subsequent different screens during the phone's boot sequence including the "POCO" screen which now displays an "open lock icon" at the top, indicating your bootloader unlock attempt and will eventually end up on a "This device is locked" screen where you have to confirm you are the device owner by entering your Mi Account password to "activate this device"; connect to your WiFi prior to doing so if the device lacks an active sim card.
FLASH CUSTOM RECOVERY, DECRYPTION DISABLER, & ROM THEN ROOT
2. Download the Official ArrowOS v11.0-vayu fastboot ROM for POCO X3 Pro [direct link here].
a. NOTE: ArrowOS requires MIUI V12.0.4.0 firmware so it recommended to downgrade to this version before flashing ArrowOS otherwise the ROM may not boot.
b. Choose the GApps build type which "includes Play services and now some AOSP apps have been replaced with GApps... All GApps packages and other[sic] files [were] extracted from original firmware images for Pixel4XL (coral)."
3. [OPTIONAL] Download the latest version of Encryption Disabler then copy it along with the fastboot ROM into a folder named 'TWRP' on the root of your microSD.
4. Ensure USB Debugging is already enabled on your device (in Settings –> Additional Settings –> Developer options).
5. Remove any screen unlock (i.e., fingerprint, PIN, pattern or password) in MIUI.
6. Power off device and put it in Fastboot mode (Vol down + Power button).
7. Download the latest SDK Platform Tools from Google for adb compatibility and create a folder called "adb" in the root of the "C:\" drive.
a. Extract the files adb, AdbWinApi.dll, AdbWinUsbApi.dll, and fastboot into the folder.
b. Ensure the latest USB drivers are installed for your PC, connect the device to the computer via USB cable, and confirm that your phone shows up recognized as "Android Bootloader Interface".
c. Launch "Command Prompt" on your PC and run the command:
cd C:/adb
To show a list of devices (including your phone) connected to your PC, enter the command:
fastboot devices
8. Download the unofficial Pbrb (test3) recovery file (PitchBlack Recovery Project 3.1.0 unofficial) by Alex Besida and copy it into the ADB install folder and rename it to "recovery.img".
9. Flash custom recovery file in CMD, run commands:
fastboot flash recovery "recovery.img"
fastboot boot recovery.img
10. Your device should automatically boot into custom recovery. At this point, the microSD will become accessible from recovery or the PC, but the device's internal storage will not be which makes using a microSD card much more imperative for this process since the recovery is in early access development.
a. Go to Wipe –> Format Data, type "yes" to perform data wipe; Back out to the main menu.
b. Go to Install –> Navigate to the TWRP folder on the microSD (via "external_sd").
Select "Arrow-v11.0-vayu-OFFICIAL-20210424-GAPPS.zip" and flash the ROM, but do not change any of the checkboxes that show up before doing so.
Format data (not wipe) before rebooting into the new ROM.
NOTE: At most it takes around 1 minute to boot back up.
11. [OPTIONAL] Power off the device and boot back into recovery.
a. Go to Install –> Navigate to the TWRP folder on the microSD.
Select " Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip" and flash it, but do not change any of the checkboxes that show up before doing so.
NOTE: This will disable forced encryption of data partition for better performance and internal SD + Data mounting in TWRP. It's not needed for the ROM to work, but due to disabling encryption it compromises security.
Reboot into the new ROM.
12. After going through the phone's boot sequence, you'll be presented with the initial phone setup process onscreen where you can begin recovering your data.
13. Go to Settings –> About phone –>tap on Build number until it says Developer options is enabled.
a. Back out to Settings –> System –> to access Developer options –> Enable USB Debugging.
14. Installing Magisk via custom recovery will fail in the background, resulting in an unresponsive "POCO" screen which is caused by installer scripts not being able to properly detect the correct device info or the recovery environment does not meet its expectation. In this case, you will need to use the Patch Image method as it is guaranteed to work 100% of the time. Installing Magisk through custom recoveries on modern devices is no longer recommended due to this reason.
a. Pull down the Notification Bar from the top of the screen and change "Charging this device via USB" to "File Transfer".
b. Open " Arrow-v11.0-vayu-OFFICIAL-20210424-GAPPS.zip " and copy "boot.img" to the phone's internal storage.
c. Download the latest version of Magisk (Magisk v22.1) and copy it to the phone's internal storage and use the native "Files" app to install the apk.
NOTE: Magisk binaries (ZIP) are now included within Magisk Manager APK file. Now you don’t have to download it separately. You can install the .apk file or rename its extension to .zip then flash it through custom recovery / TWRP.
d. Launch Magisk from the app drawer and go to "Install" under Magisk –> "Select and Patch a File," select the "boot.img" you copied internally –> "LET'S GO".
e. Copy the generated patched file to the ADB folder and flash it via fastboot by running the following commands:
cd C:/adb
fastboot flash boot boot.img
f. Reboot into the new ROM and voila!
fastboot reboot
g. Use an app such as Root Checker or BusyBox Checker (from the Play Store) to confirm root status.
h. To bypass/restore SafetyNet validation, open the Magisk app, go to Settings (cogwheel icon) and enable MagiskHide.
SIDENOTES:
These are either my comments or other user's comments that may be considered helpful as it relates to ArrowOS
Picture guide unlock bootloader, flash custom ROMs & root Xiaomi Poco X3 Pro (Credits to @pl1992aw)
Using TWRP to install OTA Updates
Installing OTA updates
Stability of 'PitchBlack Recovery Project' Recovery
How to verify SafetyNet status
Feel feel to let me know of other threads or comments that are also related to installing ArrowOS.
Excellent guide
My suggestions in terms of improvements:
- 7-day waiting time before unlocking: I would mention that wiping the device or removing the Mi account from the device could result in the timer being reset;
- DFE/Encryption Disabler: it's optional, not needed for the ROM to work and thanks to disabling encryption it compromises security;
- Firmware: Arrow OS requires MIUI V12.0.4.0 firmware, so before flashing Arrow OS it's recommended to downgrade MIUI to this version, otherwise the ROM might not boot
In the future, once more custom ROMs come out, it should be easy to turn this guide into general flashing instructions instead and not just for Arrow OS, which would be a great resource to have here
kamild_ said:
Excellent guide
My suggestions in terms of improvements:
- 7-day waiting time before unlocking: I would mention that wiping the device or removing the Mi account from the device could result in the timer being reset;
- DFE/Encryption Disabler: it's optional, not needed for the ROM to work and thanks to disabling encryption it compromises security;
- Firmware: Arrow OS requires MIUI V12.0.4.0 firmware, so before flashing Arrow OS it's recommended to downgrade MIUI to this version, otherwise the ROM might not boot
In the future, once more custom ROMs come out, it should be easy to turn this guide into general flashing instructions instead and not just for Arrow OS, which would be a great resource to have here
Click to expand...
Click to collapse
Fair enough, thanks for the suggestions. I can add them in.
Thanks for this detailed guide! I'm currently on MIUI 12.0.2 - do you know if I have to update to 12.0.4 first or if I can follow your guide directly?
Aulig said:
Thanks for this detailed guide! I'm currently on MIUI 12.0.2 - do you know if I have to update to 12.0.4 first or if I can follow your guide directly?
Click to expand...
Click to collapse
Yes, you have to update to MIUI 12.0.4.0 before flashing.
How stable is the PBRP Beta? Great Guide btw
DeblaGaming said:
How stable is the PBRP Beta? Great Guide btw
Click to expand...
Click to collapse
More stable than other unofficial custom recoveries such as OrangeFox, especially when it comes to functionality. Based on my experience using OrangeFox, it failed to flash anything that was already present on my microSD, but PBRP worked OOB w/ no issues first time, and allowed me to copy over files onto the microSD while the device was in recovery while simultaneously being connected to my PC. Thanks btw.
AusVGM said:
Yes, you have to update to MIUI 12.0.4.0 before flashing.
Click to expand...
Click to collapse
Thank you, I did that now and then followed the guide (without disabling encryption as that's an important feature to me). Super easy to follow even though I haven't been modding a lot these past years. Worked perfectly, thanks @urbanman2004
Tip: make sure to check safetynet with an app and not magisk, as described in the thread linked regarding magisk hide
Aulig said:
Thank you, I did that now and then followed the guide (without disabling encryption as that's an important feature to me). Super easy to follow even though I haven't been modding a lot these past years. Worked perfectly, thanks @urbanman2004
Tip: make sure to check safetynet with an app and not magisk, as described in the thread linked regarding magisk hide
Click to expand...
Click to collapse
Thanks for the compliment... I didn't feel the need to include how someone could check their device's SafetyNet status, but the app I use is called SafetyNet Helper Sample in the Play Store.
Very detailed instruction thumbs up...
My questions
1. For miui requirement the MIUI V12.0.4.0 , is it free or need specific version like chinese or europe or asia or america for more clearly
2. In future when twrp or custom recovery available , can we just flash the rom via recovery as simple as that. Like other phone
bla.tiga said:
Very detailed instruction thumbs up...
My questions
1. For miui requirement the MIUI V12.0.4.0 , is it free or need specific version like chinese or europe or asia or america for more clearly
2. In future when twrp or custom recovery available , can we just flash the rom via recovery as simple as that. Like other phone
Click to expand...
Click to collapse
Thanks for the compliment. To answer your questions:
1) Any version of MIUI V12.0.4.0 will do.
2) To flash future OTA updates (ROMs), it will require flashing the "compatible recovery" (vayu ArrowOS Recovery) in fastboot mode, rebooting the device then followed by installing the OTA update once it becomes available and letting it flash automatically.
hello all,
I have flashed vanilla version of ArrowOS, and magisk...
could somebody help me with installing microG for VANILLA build ROM? I'm new to microG stuff, so I don't really know from where should I install, what version etc.
some apps are not running as they require Google play services
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
as400l said:
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
Click to expand...
Click to collapse
Best that your question be taken up w/ the devs.
as400l said:
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
Click to expand...
Click to collapse
So I have some breaking news:
I can confirm that the latest unofficial alpha version of TWRP (TWRP-3.5.1-vayu-Nebrassy-1) is capable of decrypting and reading internal storage. Due to this advancement, I can also confirm that ArrowOS OTA updates will officially work using TWRP. There is NO NEED TO USE ANY OTHER CUSTOM RECOVERY BESIDES TWRP.
Hi everyone, i have one dubt in unlock bootloader process...
When phone wipe /data partition???, after or before wait the time to unlock???
Let's remain on topic and avoid bickering.
My bootloader unlocks in 4 days and I am planning to change the room using your guide. I have a doubt, I am a beginner. can I do step 8 with TWRP instead of Pbrb (test3)? Would the steps be the same with the change?
@newbrn of course. Pitch Black is literally a dark themed TWRP with some tweaks.
Hello, I'm new here, I've been dealing with certain ROM mods for a little while. My test device is an old Samsung Galaxy S4 mini (GTI9195). Now I've been sitting for a few days trying to figure out how to bring my device up to date as best as possible. Lineage OS seemed the best to me. Unfortunately there is no officially confirmed software for my device directly from Lineage, which is why I looked elsewhere. I came across this thread on XDA: https://forum.xda-developers.com/t/...520-r890-unofficial-11-0-0-lineageos-18-1-for -s4-mini.4189967/ . The user arco68 is, so to speak, the boss among S4 mini modifications. Unfortunately, I can't find exact instructions anywhere (especially for the recovery) on how to install all the packages correctly. That's why I researched. I was able to record various steps, but cannot determine if they are correct. Can someone on this forum please help me? My steps:
1. Turn on developer options
2. Turn off OEM encryption (if available)
3. USB debugging on.
4. Download and install Android platform tools in Path
5. Download and zip Magisc
7. Put the phone in bootloader/fastboot/download mode (volume down + home)
8. Flash Team Win Recovery Project (or other custom recovery).
9. Restart phone and boot into recovery mode (volume up + home + power)
10. Erase all data
11. Copy Google Apps to Phone (Optional)
12. Copy Lineage OS (or other custom rom) to phone
13. Install packages one by one (OS first)
14. Reboot device
15. Wait and set up
Okay, First of all requirement-
A portable sd card- Because after flashing twrp, you might face issue where you can't access internal storage from twrp. That's because the phone might be encrypted. You have to decrypt it by flashing a "disable dm verity- forceencrypt.zip". In this case, you might not be able to transfer files from pc when booted into twrp. So, It's a smart move to insert a sd card containing all required files before to avoid these problems.
Another requirement is samsung drivers installed in pc. I will attach that file.
Follow these steps -
1/Unlock bootloader -Go to developer options. Turn on oem unlocking. It will tell you that you're going to loss all data. Proceed. If it doesn’t tell you anything, then there is definitely some extra process to unlock bootloader of your device.(search on internet)
2/Download your phone's official firmware in pc- it will help you if anything goes wrong. Search " Sm fw" on google. Go to first site. Create an account. Search the model number, Download a firmware that matches with all your device's information in "About phone".
3/ Download the lineageos rom and twrp recovery for your model. Then install device info hw from play store to check bits(32/64). Search open gapps. Go to the website. "arm" is for 32 bit & "arm64" is for 64 bit. Select which matches to your device’s bit. Then select the android version of the custom rom. Then select "Pico". Download the file. Next, download latest magisk 25.2 from github page. Rename the apk file to "magisk.zip" Move rom,gapps, magisk.zip to SD CARD. Keep twrp in pc.
4/In pc, download latest odin software. It's an special software for samsung download mode. (There is no fastboot mode in samsung)
5/Boot your device into download mode. And connect with pc.
6/In pc, extract the twrp file(If It's in zip format). Open odin software, Go to options, turn off auto reboot. Now select "AP" & select that extracted twrp file. Click open. Then hit start button.
(Note that most of the samsung devices can't boot stock rom after flashing twrp. So you have to flash custom rom to boot your device. Follow the next step)
7/Boot into twrp wipe>format data>type "yes". Press home button. Install>Select storage>SD card>select the rom.zip. Then add more zips> select the gapps.zip. Again, add more zips> select magisk.zip. After all, swipe to flash.
After installation, reboot device.
What if anything goes wrong?
Extract the stock firmware that you downloaded from sm fw. Connect device in download mode. Open odin, select AP,BL,CP,CSC file one by one. Start flashing. You device will be alive again.