Related
Hey all!
As you all know, Wileyfox has started rolling out Nougat for their devices, starting with the codenamed marmite family (Swift 2, 2 Plus and 2X models). With this new update, Wileyfox has also included a bunch of BLOATWARE I personally NEVER expected from them. I mean, I didn't request ads in my launcher, and why do I need to forcefully use Truecaller dialer instead of the cleaner, AOSP-based one? That's why I've created this Wileyfox Debloater tool, to keep the system apps as clean and stockish as possible.
App removals included:
- AndroidPay
- BasicDreams
- BookmarkProvider
- Google Books
- Chrome
- CMFileManager
- Drive
- Duo
- Gmail
- GooglePrintRecommendationService
- GoogleTTS
- Hangouts
- Keep
- Maps
- Google Music
- News and Weather
- PhotoTable
- talkback
- Google Videos
- WFChromeCustomization
- Youtube
- Contacts
- FoxHole
- Mms
- SnapdragonGallery
- TrueCaller
- All bundled-apps from /system/vendor/bundled-app
- Possibly more in the future.
(Note: All the moved Google Apps were removed for the sole reason that they can also be downloaded from the Play Store.)
App additons / other features included:
- Google Contacts, in replacement of the half-dummy, prebundled Contacts app (which was missing link with the Dialer).
- Google Dialer, in replacement of TrueCaller.
- Google Messages, in replacement of Wileyfox Mms app.
- AOSP's Launcher3, in replacement of FoxHole (Wileyfox's Launcher).
- Framework and permission files for Google Dialer to work.
- Small tweaks in the build.prop, including drop of min processors to work from 2 to 1, and rise of maximum processors to work from 4 to 8, as well as increasing the Android compiler default amount of processors from 4 to 6.
- Possibly more in the future, too.
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
(To learn how to properly upgrade your device, kindly check post [URL="https://forum.xda-developers.com/swift-2/development/debloat-wileyfox-debloater-quickly-t3587536/post72258926#post72258926"]#25[/URL])
2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Downloads:
- For the latest Wileyfox Swift 2, Swift 2 Plus and Swift 2X firmware: Wileyfox-TOS118C-Debloater--11-05-17.zip
(For version TOS089 check Wileyfox-TOS089-Debloater--10-04-17.zip)
- For more Wileyfox devices, coming soon
Installation instructions:
1. Update your device to Nougat
2. Unlock your bootloader and flash TWRP
3. Download the latest version zip
4. Boot into TWRP, make a backup if you wish (although is highly recommended), choose Install and locate and flash the ZIP.
5. Reboot and enjoy!
6. Are you missing missed calls notifications? Is the caller ID always showed as a number instead of a contact name during phone calls? Check post #16!
Uninstall instructions:
Check post #6
Enjoy, and don't forget to leave a Thanks if you loved it!
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
rivierakid said:
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
Click to expand...
Click to collapse
That is also a possibility but:
1. Launcher3 conflicts with the already installed launcher, so it's impossible to get that out of the way
2. I got latest version working here using the required libraries (extracted from a Pixel), so yeah, probably both possibilities are just fine
And for the third one, just wanted to say there's no need to reactivate them (if you manage to deactivate them, ofc), and, all of the packages the script moves are stored in a safe place (/system/__bloat), so they can be restored from there
I don't remember if I had a problem with a previous OTA update for Wileyfox, but I was not able to install an update without reactivation a disabled app.
I'm not sure...
You could select a default launcher and the phone has really enough RAM, so I think it is not necessary to remove the FoxHole from the system.
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
The final solution for this is LineageOS, if they provide the source
Excellent! Thanks for providing this...such a stupid shame that Wileyfox decided to do this. I'm just hoping that they now release their sources so that we can start working on a proper release of Lineage!
*Edit: Nice! https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937/commits/all*
JT
rivierakid said:
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
Click to expand...
Click to collapse
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Hello,
thanks for your effort to the community.
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
linuxct said:
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Click to expand...
Click to collapse
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
MCPoppa said:
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
Click to expand...
Click to collapse
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
jdtanner said:
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
Click to expand...
Click to collapse
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
linuxct said:
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
Click to expand...
Click to collapse
Everytime i installed twrp i got stuck in a bootloop :/
MCPoppa said:
Everytime i installed twrp i got stuck in a bootloop :/
Click to expand...
Click to collapse
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
linuxct said:
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
Click to expand...
Click to collapse
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
MCPoppa said:
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
Click to expand...
Click to collapse
I explained it last night here, but I also stated it in the OP:
linuxct said:
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
[B]2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.[/B]
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Click to expand...
Click to collapse
linuxct said:
I explained it last night here, but I also stated it in the OP:
Click to expand...
Click to collapse
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
MCPoppa said:
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
Click to expand...
Click to collapse
Try flashing it to your recovery partition, my guess is that now that DM-verity is disabled everything should work fine
Cheers!
Quick update post after two days of usage, yesterday I noticed I didn't receive any notifications on missed calls, and that the caller ID always showed as a number although I had it added as a contact.
I realised that I didn't have any "Phone" app chosen as default in Android settings, so I was missing those notifications until I opened the Google Dialer app.
In case it happens to you, to sort it out go into Settings > Apps, then hit the gear in the top right corner and make sure you've a config similar to this one (Launcher3, Google's "Phone" and Google's "Messages" chosen as default Home, Phone and Messaging apps).
I hope this is clear for everyone, since it's not something I can fix on my side/requires the user to do the change
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Ianharding said:
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Click to expand...
Click to collapse
Firsts things first: After heavily modding the system like you did on Marshmallow, make sure not to update your device through the regular OTA but using a recovery image like the ones posted in this device's forum.
For magisk: are you sure you flashed it correctly? Magisk disables that dmverity message you are mentioning, so maybe you installed an old version or wasn't properly flashed.
My advice is: download everything: the recovery image, the debloater and Magisk. Boot into TWRP, wipe EVERYTHING if possible, including Data cache dalvik cache and system partitions. Once done, flash the recovery image zip, and right after that, without rebooting, flash the debloater and magisk. Reboot and everything should work perfectly
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
digidude512 said:
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
Click to expand...
Click to collapse
As soon as you root any Marshmallow/Nougat phone Android Pay will not work, according to this article
I have never used Android Pay so it doesn't make any difference to me. My phone is much better now that I have debloated it. I also installed Evie Launcher and Halo Browser, both small minimalist apps and everything is really smooth.
Instead of a Debloater, could the Stock ROM not be debloated and rezipped as a custom 'Lite' version?
WARNING: You can't downgrade anymore once you flashed U4/S4 March update !
https://samfrew.com/model/SM-A805F/
SM-A8050
SM-A805F
SM-A805N you can't unlock bootloader on this variant! (R1Q_KOR_SINGLE.pit)
You will need:
-Odin v3.14.1
https://dl2018.sammobile.com/Odin3-v3.14.1.zip
-Galaxy A80 Latest USB Driver
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
You want to download latest firmware directly from server? (fast download)
Samfirm 0.4.1 or Frija 1.4.2
https://samfirmtool.com/samfirm-v0-4-1
https://github.com/wssyncmldm/frija/releases
Frija not working ? install both vcredist_x00 for your device !
(Check your windows settings to know which version to install).
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
-https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
-https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-A805F) and your CSC : (mine is LUX).
(All CSC's and models on Samfrew: https://samfrew.com/model/SM-A805F/).
-Download and extract SM-A805XX_1_00000000000000_xxxxxxxxxx_fac.zip
On your device:
If you want to unlock bootloader:
-Go to Settings then to About phone and find your build number.
-Tap on your build number 6 times until you see “You’re now a developer”.
-Go in Developer options > enable OEM unlocking.
-Connect the device to your PC.
-Power off your device with POWER and volume DOWN and directly hold volume UP and DOWN together!
-Device will boot in DOWNLOAD MODE.
-Long press volume UP to unlock the bootloader. This will wipe your data and automatically reboot your device!
If you dont want to unlock bootloader:.
-Download and extract Odin and open it as administrator.
Still in DOWNLOAD MODE:
-Click on BL and select BL_A805FXXXU4AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on AP and select AP_A805FXXXU4AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
-Click on CP and select CP_A805FXXXU4AXXX_CP14483800_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
(If you want to keep your data don't flash CSC).
-Click on CSC and select CSC_OMC_OXM_A805FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_OXM_A805FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on START and wait for installation, when done you can unplug your device.
ROOTYour KNOX status will be tripped if you follow this tutorial...What's knox ? : https://www.google.com/search?q=samsung+knox+explained
-Download the latest stock firmware for your Samsung Galaxy A80 with Samfirm/Frija app (faster) or Samfrew/Sammobile website (way slower).
https://samfrew.com/model/SM-A805F/
-Extract the SM-A805XX_1_EXAMPLE_0000000000_fac.zip file with 7zip or any other unzipper.
-Copy the (AP_A805XXXXU1XXXX_CL00000000_QB00000000_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar.md5) file and transfer it to your internal storage.
-Download and install Magisk Manager APK https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
-Open Magisk Manager and go to Install > Install > Select and Patch a file.
-Navigate through the storage and select the extracted AP file.
The firmware will be patched and will be found in Internal Storage/Download/magisk_patched.tar.
-Transfer the patched file to your PC.
-Turn OFF your device and boot into DOWNLOAD MODE.
-In Odin, click on AP and select the patched tar file, Uncheck “Auto Reboot” and click on Install.
The tool will flash Magisk V20 on your Samsung Galaxy A80.
To boot in recovery or boot the system with Magisk installed:
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery
My storage was reduced from 128gb to 32gb after doing this. Is there a fix?
any improvement..? could anyone confirm thats this way work corectly
edited: i hv tried still on unlock bootloader without root capability.. unfortunately there's not suitable magisk work on this device whatever try to patched method but still null
damn samsung device i hv ever owned
haanz85 said:
any improvement..? could anyone confirm thats this way work corectly
edited: i hv tried still on unlock bootloader without root capability.. unfortunately there's not suitable magisk work on this device whatever try to patched method but still null
damn samsung device i hv ever owned
Click to expand...
Click to collapse
Just fixed mine by doing the bootloader unlock and root steps above,
setup the phone without Google but with debug mode enabled,
flash twrp,
format data (the one that makes you type yes),
setup the phone with Google and debug mode, then
reflash the firmware with Odin (stock BL, magisk_patched AP, stock CP, and HOME_CSC).
Now I have 108gb storage with root! I just have to hold volume up+power button every time I boot, though.
Nazato said:
Just fixed mine by doing the bootloader unlock and root steps above,
setup the phone without Google but with debug mode enabled,
flash twrp,
format data (the one that makes you type yes),
setup the phone with Google and debug mode, then
reflash the firmware with Odin (stock BL, magisk_patched AP, stock CP, and HOME_CSC).
Now I have 108gb storage with root! I just have to hold volume up+power button every time I boot, though.
Click to expand...
Click to collapse
what version twrp u used? doesn't you have problems in reading internal storage or USB MTP/ connect pc? Does all run normally? please gv link the worked twrp if u have..
Could you please be more detailed in this steps?? I got this problems too. plz help.
hosheaxu said:
Could you please be more detailed in this steps?? I got this problems too. plz help.
Click to expand...
Click to collapse
read carefully every step bro. after flashing magisk patched then setup phone from beginning without setup google acount just skip, then check again by activating developer menu & usb debugging on. at the end reset from about menu..then phone's should reboot, after that install magisk manager then follow until finished process. & now after reboot u already got rooted beloved phone . congrats
haanz85 said:
what version twrp u used? doesn't you have problems in reading internal storage or USB MTP/ connect pc? Does all run normally? please gv link the worked twrp if u have..
Click to expand...
Click to collapse
Only the latest version from blackbuga, and yes, I can't access my internal storage through USB when in twrp. It doesn't bother me that much, because I only needed twrp to format the data so the storage goes back to 108gb from 32gb. Everything's been running fine so far.
Nazato said:
Only the latest version from blackbuga, and yes, I can't access my internal storage through USB when in twrp. It doesn't bother me that much, because I only needed twrp to format the data so the storage goes back to 108gb from 32gb. Everything's been running fine so far.
Click to expand...
Click to collapse
but why u need twrp just for get normal storage.. while my storage going fine without twrp & i just try reset in finalizing process then install magisk at the end & everything looks good.
right now I'm just curious why there's no more dev interest in working on custom recovery & roms which is in other hand there's plenty developer working on galaxy s series with snapdragon soc with great support for official/unofficial builds whether twrp or cust roms. so sad considering the device is quite a potential to be developed
haanz85 said:
but why u need twrp just for get normal storage.. while my storage going fine without twrp & i just try reset in finalizing process then install magisk at the end & everything looks good.
right now I'm just curious why there's no more dev interest in working on custom recovery & roms which is in other hand there's plenty developer working on galaxy s series with snapdragon soc with great support for official/unofficial builds whether twrp or cust roms. so sad considering the device is quite a potential to be developed
Click to expand...
Click to collapse
I just followed op's instructions in his A70 topic lol I get you. I came from iOS and I was really excited when I got the phone, but after seeing the development scene... I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Nazato said:
I just followed op's instructions in his A70 topic lol I get you. I came from iOS and I was really excited when I got the phone, but after seeing the development scene... I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Click to expand...
Click to collapse
yeah it's possible for sensitive pricing from first launching. in my country first launching price going around $705 then after few month until approaching new device release info to be released in February. on new years then the price going down until just left $549,50 then i decided to bought it :victory:
maybe many people's thinking like me, wait & see before grab this phone's :laugh:
Nazato said:
I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Click to expand...
Click to collapse
.
Actually, the truth is something else and the price range is not relevant at all.
If you have A series, it is low price range of Sammy phones and if you owned previously Iphone, you jumped "from horse to donkey".
Here you can find android ultra expensive devices successfuly rooted and in everyday ongoing development.
As pricey device is, more support you have ( All S,S+ and Note series, for example).
I have very expensive Galaxy Fold device...successfully rooted with regulary ongoing development, therefore, price is not relevant at all.
There on IOS is missing crucial users inteligence, knowledge and developers on IOS users market.
Simply said...they don't have and don't need developer oriented users and no quality devices to be upgraded or "pushed" further more.
Also...IOS is CLOSED SOURCE system not opened for free development because Apple can't make profit of that.
tin2404 said:
.
Actually, the truth is something else and the price range is not relevant at all.
If you have A series, it is low price range of Sammy phones and if you owned previously Iphone, you jumped "from horse to donkey".
Here you can find android ultra expensive devices successfuly rooted and in everyday ongoing development.
As pricey device is, more support you have ( All S,S+ and Note series, for example).
I have very expensive Galaxy Fold device...successfully rooted with regulary ongoing development, therefore, price is not relevant at all.
There on IOS is missing crucial users inteligence, knowledge and developers on IOS users market.
Simply said...they don't have and don't need developer oriented users and no quality devices to be upgraded or "pushed" further more.
Also...IOS is CLOSED SOURCE system not opened for free development because Apple can't make profit of that.
Click to expand...
Click to collapse
but what about this device? are u still make exception from regular ongoing development.. until now there's no famous developer that saw it for builds known roms out there although this doll already succesfully rooted, but none of them build us twrp with fully support & maybe one or two working cust roms
Android 10 is released.
https://samfrew.com/model/SM-A805F/
A805FXXU4BTC3
BK said:
Android 10 is released.
https://samfrew.com/model/SM-A805F/
A805FXXU4BTC3
Click to expand...
Click to collapse
Is This only for france devices?
android 10
Thanks for your help..
i want ask we can do the root and TWRP recovery for android 10 i wanna update my phone but dont know if its ok or not i need the root and dont want lose it
can you help please if its ok or not ???
thanks
uae.coool said:
Thanks for your help..
i want ask we can do the root and TWRP recovery for android 10 i wanna update my phone but dont know if its ok or not i need the root and dont want lose it
can you help please if its ok or not ???
thanks
Click to expand...
Click to collapse
go right ahead I'm rooted on Android 10 right now just follow the instructions again
i rooted all went ok but when i transfer my all data i find out no root and i tried to install TWRP but i really cand do this and every time fall
please help
uae.coool said:
i rooted all went ok but when i transfer my all data i find out no root and i tried to install TWRP but i really cand do this and every time fall
please help
Click to expand...
Click to collapse
just flash everything again (magisk patched AP) with HOME_CSC. DON'T WIPE
Nazato said:
just flash everything again (magisk patched AP) with HOME_CSC. DON'T WIPE
Click to expand...
Click to collapse
ok thanks will try it now
other things is losing the memory showing 32gb after the root and when wipe no root ???
and one more things please how to install TWRP i tried many time but stack in the samaung logo ???
thanks again
ROM dedicated for All Quark (Moto MAXX/Turbo and Droid Turbo - XT1225, XT1250 and XT1254)
This ROM is the LineageOS from https://lineageos.org/ with specific changes to improve the experience for Quark that is why the ROM has the MOD type, all modification are in the changelog
Download:
ROM:
Sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Gapps:
Open GApps :
Open Gapps Click Here
Choose Platform: ARM, Android: 10.0, and a Variant the one that have all you need, I recommend the nano pack but it may not have all you need so check before download.
TWRP For Quark:
TWRP Use laste Mod version that I release Click Here
Installation:
Make sure you are running latest MOD TWRP from xda TWRP thread
Download the latest ROM and GApps**.
Reboot to recovery (recommended make a backup)
Coming from different ROM? Then Always wipe Data (without media aka without internal memory)
Wipe System*
Flash the latest build and GApps **
Reboot and enjoy!
* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update
** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update
Changelogs:
LineageOS - 17.1 source and Quark Changelog (Click Here)
What's working :
Everything minus VoLTE support for XT1254 (1225 doesn't have this featuring).
Known Android 10 issues :
Not PRE-ROOTED, ROOT solution is available read this thread second post
Old issue maybe resolved on latest TWPR update but... TWRP may not be able to backup or decrypt data encrypted on Oreo or Up: no know workaround, one day TWRP will support it.
Can't swipe/draw the pattern in lock screen : Screen lock pattern is set with the extra option of patterns "Directly show pattern view" and ambient display enable all at the same time, will bug ambient display for the wave or pick featuring of gestures, this doesn't bug when you received a notification, disable one or the other until the bug is fixed.
General bug help/fix in second post or some were in the thread, use XDA building "Search Thread" option to find general help for this thread project...
Source:
LineageOS Source
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
XDA:DevDB Information
[ROM][All Quark][10.x]LineageOS ROM for Quark
Contributors
Felipe Leon (fgl27) is the main contributor (as I'm the one making it).
But the XDA community the quark user base plus the open source community from XDA, github and the LineageOS team is what make this project so good, thank you all :good:.
ROM OS Version: 10.x
ROM Kernel: Linux 3.10.x
Based On: LineageOS 17.x
Version Information
Status: Stable
Created 2020-24-01
Last Updated Check Changelog click here
Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2) Check the boot reason prop "ro.boot.bootreason" :
Using the app BHB27 Kernel Audiutor > logs section > search in a log > mark getprop > search keyword "reason".
If the result is power_key_press the device didn't reboot it power off.
Code:
[ro.boot.bootreason]: [power_key_press]
On this case, is recommended to set the battery "Automatic power saver" from default 15% to a higher value then the one yours device is power it self off.
-----------------------------
If the result is reboot the device reboot it self
Code:
[ro.boot.bootreason]: [reboot]
On this case, is recommended to just share a log, do as is recommended on next post.
Bootloop to TWRP after a Factory Reset (Settings/System/Reset option/Factory reset):
This is a Nougat and up problem, it only happens if you are using a TWRP from the official site (with is not update to properly support Nougat and Up Android versions) or a old version of TWRP, to fix it just flash latest MOD TWRP version from the TWRP xda.
TWRP xda thread Click Here
Pictures access, view, sharing or related:
One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example.
You take a picture or a screenshot and can't see or share it with some apps, the simple fix is just erased/delete the folder with that problem for example the DCIM (camera folder) and or Pictures (Screenshot) folder under Main storage (or any folder were you face a picture or file access related problem), of course you can backup the files to another folders first using a file explorer that can see the files (maybe necessary one with ROOT access), then let the OS service recreate the folder, it will automatic recreates after you take a new picture or screenshot (or manually make the new folder if is a custom folder mane by you), test to see if the problematic app can see after.
USB OTG player:
On latest android version Nougat and above, to play anything from a USB OTG device is needed proper permission, that is not simple to give as the app must request it to be given, so to play anything from a USB driver find a app like this one
VVM XT1254 only
VVM app (VVM may only be accessible via play with the link, click here and chose open with play), VVM may not work correctly google has it on version is free and seems to work 100% Google voice, the in the phone app of b this ROM also has a dedicated option for voice calls
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix.
Always post a bug with @fgl27 and a log .zip generated by the app
BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP (ROOT is needed for this)...
Even after a random reboot share a log
If is a Reboot/Power off related bug make the log as soon the device finishes boot up
duplicated
Really nice! Getting a battery replacement for my Droid so that it can work as a backup phone. Tysm for Android 10!
Won't stay on long enough to do hardly anything. Reboots into recovery on its own, thankfully. What am I missing?
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Won't stay on long enough to do hardly anything. Reboots into recovery on its own, thankfully. What am I missing?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
Inform what you are doing
The ROM is much much smoother than pie ROMs...Thank you so much bro ......Android 10 on this 6 year old handset is just unbelievable....
fgl27 said:
Inform what you are doing
Click to expand...
Click to collapse
Full wipe, except internal storage, Flashing rom, gapps, onto xt1254, in twrp 3.2.3mod4, reboot. About a minute into setup, phone powers down & reboots into recovdry
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Full wipe, except internal storage, Flashing rom, gapps, onto xt1254, in twrp 3.2.3mod4, reboot. About a minute into setup, phone powers down & reboots into recovdry
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
And just the ROM? What happens
fgl27 said:
And just the ROM? What happens
Click to expand...
Click to collapse
Same thing. This ain't my first rodeo, and I'm stumped!
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Same thing. This ain't my first rodeo, and I'm stumped!
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
The odd thing is what is doing the call to recovery? it doesn't just go to recovery because of a fail to boot something is calling it.
Maybe a problem on data partition don't know but is a odd behavior.
Try to log that, adb is enable but you must give permission connect the usb cable during boot try to connect "adb shell" will refuse as is missing permission, as soon as the device finishes boot do again "adb shell" give the permission, next boot after the bootanimation start, you will be able to "adb shell" but before enable ROOT for adb "adb root" then after connect "adb shell" open two windows one do a "logcat" another "dmesg -w"
share the log information.
Thanks / Flashlight issue
Thank you for your invaluable contributions. Keep up the good work!
So far, the ROM has been working fine except for two bugs: the flashlight function is not working (I took a photo with flash so the leds on the device are OK), and the home/launcher app (Trebuchet) keeps crashing.
Kind regards!
fgl27 said:
The odd thing is what is doing the call to recovery? it doesn't just go to recovery because of a fail to boot something is calling it.
Maybe a problem on data partition don't know but is a odd behavior.
Try to log that, adb is enable but you must give permission connect the usb cable during boot try to connect "adb shell" will refuse as is missing permission, as soon as the device finishes boot do again "adb shell" give the permission, next boot after the bootanimation start, you will be able to "adb shell" but before enable ROOT for adb "adb root" then after connect "adb shell" open two windows one do a "logcat" another "dmesg -w"
share the log information.
Click to expand...
Click to collapse
Yoiks! Not quite that tech savy. Even tried after a full wipe & zip-by-zip install. If I have to be happy with RR Pie, so be it. Not all that bad. My Turbo has some miles on it, rebuilt twice already. Got one last battery & display in the wings. Best, last phone Motorola made. Don't waste your time, further, on what's likely a hardware flaw.
Sent from my LM-V405 using Tapatalk
I think your not using latest twrp
newbe1droidx said:
I think your not using latest twrp
Click to expand...
Click to collapse
Looks like I wasn't. I thought 3.2.3mod4 was the last best available.
Update: Um, yeah, still no luck. Used 331m1. My Turbo has a weird glitch, apparently. [emoji34]
Sent from my LM-V405 using Tapatalk
Kinzhal said:
Thank you for your invaluable contributions. Keep up the good work!
So far, the ROM has been working fine except for two bugs: the flashlight function is not working (I took a photo with flash so the leds on the device are OK), and the home/launcher app (Trebuchet) keeps crashing.
Kind regards!
Click to expand...
Click to collapse
Trebuchet doesn't crash for me try to share a log.
On next build flashlight is OK
Einsteindks said:
Looks like I wasn't. I thought 3.2.3mod4 was the last best available.
Update: Um, yeah, still no luck. Used 331m1. My Turbo has a weird glitch, apparently. [emoji34]
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
twrp doesn't affect this I tested And 10 on it before making 331 was all fine...
does the custom kernel I share works for you on Pie?
fgl27 said:
Trebuchet doesn't crash for me try to share a log.
On next build flashlight is OK
twrp doesn't affect this I tested And 10 on it before making 331 was all fine...
does the custom kernel I share works for you on Pie?
Click to expand...
Click to collapse
Overall answer; I don't know. I've stopped trying for now. It doesn't stay on long enough to access the logs. There's a pop up saying a certain file has stopped working. I'll look into that this weekend and post that information. I can only think that it's something to do with my phone's Hardware, one small minor flaw is screwing the whole thing up.
Update: well, I had a little time to kill. I reinstalled just the ROM only. 'com.android.phone keeps stopping' Would not having a SIM card installed be related to this error?
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Overall answer; I don't know. I've stopped trying for now. It doesn't stay on long enough to access the logs. There's a pop up saying a certain file has stopped working. I'll look into that this weekend and post that information. I can only think that it's something to do with my phone's Hardware, one small minor flaw is screwing the whole thing up.
Update: well, I had a little time to kill. I reinstalled just the ROM only. 'com.android.phone keeps stopping' Would not having a SIM card installed be related to this error?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
noting crashing to me, sim or no sim.
I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 17.1 source and Quark Changelog (Click Here)
First You Need an unlocked bootloader there are many guides to unlock the bootloader on Samsung devices I recommend this one Unlock Guide
Once you have an unlocked bootloader we can proceed
1: Flash Twrp if you don't have it already: Snapdragon Twrp Or Exynos Twrp Download The Twrp For your device Model And Also Download Vbmeta Disabled, Reboot Into Download Mode By Pressing Volume Up And Volume Down When Booting The device
Download Odin and Samsung Drivers On your Computer Odin And Samsung Drivers
After You have Odin And Samsung Drivers, Open Odin and On the AP Section Select The Twrp You downloaded And On the Userdata Section Select The Vbmeta Disabled You Downloaded , GO TO OPTIONS AND DISABLE AUTO REBOOT!!!, Press The Start Button and once it Finishes, You Should Press The Power Button And Volume Down And When It Starts To Reboot Press The Volume UP And Power Button If you Did it right you Should Boot Into Twrp
2:
On Twrp Go to Wipe > Format Data > Type Yes (This will WIPE ALL DATA ON THE DEVICE!!!)
Then Go to Reboot > Recovery
After It reboots Go to Reboot > Fastboot
Download Adb On your Computer Adb Download And extract it into a folder, Then Press Shift On your Keyboard And Right Click At the same time Select The "Open Command Prompt Here" Option, You should see A command Prompt
Now You need To Download The Gsi You want to flash, (You can Find Many Gsi In the s20 fe Gsi's Group Here) Or you can Also Check Treble Gsi's Group
(Roms Based on Older PHH Patches than v303 Will not work)
Once You have the Gsi you want to flash Copy it into the adb folder And Also RENAME THE FILE to sys.img
Now On the Command Prompt You can Run > fastboot flash system sys.img
(If You Cant Get Your Drivers Working i recommend Trying ubuntu Because it has Drivers Pre Installed)
If you Dont get any errors then you are Good Reboot your device and you should see the gsi is installed
Fixing Rounded Corners:
Reboot Into Twrp And Open Adb On your computer
Download The Overlay and place it in the adb folder
Run ( adb shell mount /dev/block/dm-1 /vendor )
Then Run ( adb shell rm /vendor/overlay/framework-res__auto_generated_rro_vendor.apk )
Then ( adb push treble-overlay-samsung-rq8.apk /vendor/overlay )
Bootloop Problems:
You may have a bootloop If you are using A newer Vendor
This Was Tested On the one Ui 3.0 Vendor I Recommend Downgrading to 3.0 Vendor If you can
!!! I am not sure if its working on one UI 3.1 Vendor !!!
(Vendor is the one UI version you have)
Magisk:
To flash magisk you need some special Instructions, !!!Without them flashing magisk will result in a bootloop!!!
They are a bit complicated and you can find them Here (I don't recommend Using Magisk With Gsi's)
Issues?
Current issues are: 60fps Video Recording, Fingerprint Sensor And MTP
Fingerprint Might be fixed On android 12!!!
IF YOU ENCOUNTER PROBLEMS JOIN THE S20 FE HELP GROUP Here
(THIS WAS ALL TESTED ON SNAPDRAGON I AM NOT SURE IF IT WORKS ON EXYNOS)
I haven't clicked to look but is the magisk for GSIs that thing where you have to reboot from recovery to activate root ?
I suppose if it is the phone still wouldn't pass SafetyNet would it ?
3mel said:
I haven't clicked to look but is the magisk for GSIs that thing where you have to reboot from recovery to activate root ?
I suppose if it is the phone still wouldn't pass SafetyNet would it ?
Click to expand...
Click to collapse
no, you can fix magisk but its a bit hard, And yes you can pass safetynet with magisk, Some roms like pe+ Can pass safetynet without it tho
If only the fingerprint sensor worked on GSI ROMS. I would have definitely went for it.
S20 FE 5G rooted on android 11 (one ui 3.0)
Kolyei said:
If only the fingerprint sensor worked on GSI ROMS. I would have definitely went for it.
S20 FE 5G rooted on android 11 (one ui 3.0)
Click to expand...
Click to collapse
that's down to Samsung doing the bare minimum to qualify for treble compatibility, same as the vendor layers of most OEMs. only Sony went the extra mile to actually make sure their hardware would work apparently.
3mel said:
that's down to Samsung doing the bare minimum to qualify for treble compatibility, same as the vendor layers of most OEMs. only Sony went the extra mile to actually make sure their hardware would work apparently.
Click to expand...
Click to collapse
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.
Doomer231 said:
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.
Click to expand...
Click to collapse
any hardware OEMs add has supposed to have been functional for the last 3 years. they control their vendor layers which should work seamlessly with the OS layer. I'm paraphrasing the xda page that introduces treble and Phhuson.
OEMs have little interest in making treble work as it does nothing for them (they think). if google support was the reason 60fps would work for video recording but it doesn't.
Doomer231 said:
Not really, it has been confirmed that android 12 will add official support for underscreen scanners, so GSI devs aren't wasting any time on fixing FOD.
Click to expand...
Click to collapse
it was android 11 that broke it lol, on a10 it was fine
QUESTION for the GSI users out there...
do you have any of the screen juddering while trying to scroll or touch screen dead spots that occasionally happen ? any ghost touch issues, I suppose with the caveat of if you had them before ?
3mel said:
QUESTION for the GSI users out there...
do you have any of the screen juddering while trying to scroll or touch screen dead spots that occasionally happen ? any ghost touch issues, I suppose with the caveat of if you had them before ?
Click to expand...
Click to collapse
i never had any issues in one ui and i also dont on gsi
Does doing this guide trip Knox on the phone?
pOLLYpOCKET said:
Does doing this guide trip Knox on the phone?
Click to expand...
Click to collapse
yes, if you unlock your bootloader it trips knox
how can i found vbmate file for fold 2 ?
rowihel2012 said:
how can i found vbmate file for fold 2 ?
Click to expand...
Click to collapse
Do not install a gsi on the fold, it will be horrible as stock android has bad support for folding devices
overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)
luisf0202 said:
overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)
Click to expand...
Click to collapse
sounds like a question for the mighty phhuson and friends
luisf0202 said:
overlay commands not functional (gives file not found error framework-res__auto_generated_rro_vendor.apk)
Click to expand...
Click to collapse
try this instead adb shell rm /vendor/overlay/framework-res__auto_generated_rro_vendor.apk
For me fixing round corners disabled nav buttons and when choosing gestures as nav keys only swipe up for home gesture works back button is broken
are you using a 3rd party launcher ? navigation gestures are or were supposedly broken on 3rd party launchers regardless of which rom you're running.
no, im using quick step. But even with gestures disabled i dont have any buttons
Everything you do, you do at your own risk. I'm not responsible for all damages, this can also lead to loss of warranty.
Hi,
Probably many of you know how to do a Magisk install without TWRP, but this guide is for people who don't know and don't want to mess things up.
I will try to show you step by step how to do it.
Many thanks to:
kdrag0n
topjohnwu
Leave them a nice feedback
!!! Before we start make sure your device is unlocked, if you don't know how to do it below is link to official Xiaomi guide !!!
https://c.mi.com/thread-2262302-1-0.html
Requirement
Xiaomi Mi Flash ver. =>3-14-0 - Needed to install all adb drivers Download
ADB & Fastboot tools - Could be the one built into Mi Flash tool I'll use this to make it simple
Magisk =>24.2 - This software is base of our rooting process Download
SafetyNet Fix => 2.2.1 (Zygisk) - Needed to backdoor SafetyNet fail check, at the moment it is only working method for Mi Pad 5 Download Make sure you download the Zygisk version!
Boot.img - You can download from official MIUI website full flashable rom and separate boot.img file from there, or use my if your Miui version is China 13.0.5, EEA 13.0.3, Global 13.0.1
China 13.0.5EEA 13.0.3Global 13.0.1Installation
To make it easier, Green color mean what you need to do on Tablet, Orange on PC
Unzip Mi Flash tool
Open folder and run XiaoMiFlash.exe, if window "Driver" won't pop-up click on the Driver tab and then "Install" button and close all windows.
Connect your tablet to computer, when your tablet ask how you want use USB, choose File Transfer/Android Auto
Copy to internal storage Magisk-v****.apk, safetynet-fix-v****.zip and boot.img
Open File Manager on your tablet find a folder where you copied all files, and install Magisk
Open Magisk app, and click on Install in section Magisk, then select "Select and Path a File", after that find your boot.img file and click on it
Click "LET'S GO" button on the right side and wait until process will be finished
On your computer in the tablet's storage window, go to the file specified in the application probably /Download/magisk_patched-*****
Copy this file to a subfolder of Mi Flash on your computer, exactly to MiFlash2020-3-14-0\Source\ThirdParty\Google\Android and change the name of this file to boot.img
Open PowerShell/Windows Terminal in this folder (Hold Shift + Right click -> Open PowerShell window here)
Make sure your tablet have enabled USB debugging in Developer options Setting -> Additional settings -> Developer options -> USB debugging
Turn off your tablet, then hold down Power and VOL- until the screen lights up, then release power button, if Fastboot appears, everything went fine
Go back to your Terminal window and type to check if your computer see your tablet
Code:
./fastboot.exe devices
If you see answer "******** fastboot" it mean there is communication between PC and Tablet
Next type this command to flash patched boot image
Code:
./fastboot.exe flash boot boot.img
Next type this command to reboot your device
Code:
./fastboot.exe reboot
Restart can take a longer time than normal
Open Magisk app and check status of Magisk, if you see for exaple "Installed 24.2 (24200)" everything went fine
Open Settings in right corner of app and in section App click on Hide the Magisk app then type name for hidden app, it will ask to install new app so do it
Open again Magisk app and open Settings in section Magisk enable Zygisk (Beta) and Enforce DenyList
Click on Configure DenyList than click on three dots in right corner and uncheck Show system apps
Search for all the apps in the list below and check them. It is important to click on their name to see all modules, once you have done this click on the box to activate all of them
Code:
Google
Google Assistant (I have two)
Google Pay
Google Play services
Google Play Store
After that reboot your tablet, and open again Magisk app
On the bottom click on Modules
Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
After that reboot your device one more time
After reboot open Android Settings go to Apps and Unhide system services than find and clear all data of Google Play services and Google Play Store
Reboot tablet last time
If you have reached this point it means that everything has gone correctly, probably for about 3 hours you will still not be able to install Netflix and some banking applications but after this time everything will be back to normal, this is because Google's servers have detected that Magisk has been installed but that the application has been changed and Zygisk has been enabled so at the next check it notices that everything is Ok and gives access back.
Quick explaination what happend here:
Magisk has been installed and device is Rooted
The application has been changed and hidden
Zygisk has been activated and hidden from Google services
SafetyNet-fix was installed, which restores the functionality of SafetyNet and Widevine L1, which is blocked after the installation of Magisk and unlocked Bootloader
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Nux01 said:
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Click to expand...
Click to collapse
Hi Nux01,
1. Unfortunately yes, TWRP isn't supported for Pad 5 yet.
2. It won't work, TWRP app is only making a request to TWRP custom recovery, until it doesn't exist you can't even install custom ROM
3. It is, but i didn't test it yet on Pad 5, and I don't know if it will work with new decides because last release is from 20.07.2020.
https://github.com/francescotescari/XiaoMiToolV2/releases
4. Yes, you need Xiaomi account, also your device has to be logged in, and registered to unlock, Xiaomi made complete guide how to do this, link is on the top of this post.
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Nux01 said:
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Click to expand...
Click to collapse
I mean it's quite old release so it may not work with current unlock bootloader process on new devices like a Xiaomi 12, Xiaomi Pad 5 etc. I can't promise it won't brick your device, only confirmed method is by official Xiaomi tool.
Thank you
I'll wait a little bit before rooting my tablet.
Have a nice day.
Followed the instruction, worked like a charm. Although I had unknown "chinese sings" errors with the driver install it worked. By the way there is a newer version of the flashing tool.
Thanks for the effort of writing this down!
Hello,
I just managed to unlock the bootloader of my tablet "Pad 5".
I tried under Mac and Linux with Xiaomitool V2 without success (error 20036 and 20045).
I also tried with VirtualBox who did not recognize the tablet.
I succeeded with VMware and Windows 7 by testing different drivers and it worked.
I just root the tablet with Magisk.
On the other hand, is there the equivalent of TWRP to make a complete system backup. Apart from Titanium and MyBackup.
Thanks for your help.
thanks dude.
didn't try this yet, just wondering.
can't i just flash recovery and then flash magisk.apk?
thanks
Can i update ota to 13.0.2 after rooted? Just update and root again?
Cpanel10x said:
Can i update ota to 13.0.2 after rooted? Just update and root again?
Click to expand...
Click to collapse
You can update, but after that you need root again but with boot.img from 13.0.2
How to get the boot.img 13.0.2? I checked the 3GB Firmware and only found vendor_boot.img. Is it the same thing?
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Thomas Brown 99 said:
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Click to expand...
Click to collapse
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Thanks for this awesome guide. Do you have some suggest about the magisk modules to install?
thanks, it just worked perfectly and your step by step guide is very handy and helpful. thanks so so much.
vjsaini00 said:
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Click to expand...
Click to collapse
Today evening, I'll add more boot.img
kisielec said:
Today evening, I'll add more boot.img
Click to expand...
Click to collapse
eagerly waiting, Thanks
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
24. Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
25. After that reboot your device one more time
Click to expand...
Click to collapse
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
cysmaster said:
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
Click to expand...
Click to collapse
I also have this module installed without problems, as there is no recovey for Pad5, it is a good idea to install in magisk the module Magisk Bootloop Protector, which serves exactly to prevent what you are afraid that happen with your tablet