Hi, I had TWRP version 3.4.1B and wanted to resize file system in advanced wipe options, but it didn't show me the system partition. I mounted the system partition and the system partition still does not show up. I have installed the latest TWRP 3.5.0 and the problem exists.
uvzen said:
Hi, I had TWRP version 3.4.1B and wanted to resize file system in advanced wipe options, but it didn't show me the system partition. I mounted the system partition and the system partition still does not show up. I have installed the latest TWRP 3.5.0 and the problem exists.
Click to expand...
Click to collapse
@uvzen,
This is because there is no "actual" fixed system partition any more.
Starting with Android 10, these read-only partitions:
System
Vendor
Product
System Ext
ODM
are now stored dynamically within a large fixed partition named super.
I would recommend you check with your TWRP developer to find out if your version has dynamic partition support.
For more info on dynamic partitions, check out this site:
https://source.android.com/devices/tech/ota/dynamic_partitions
Thanks for the information.
Yes, my version supports dynamic partitions but I have a problem because I want to convert one app to a system app in the link2sd app but I don't have space on the / system partition.
Hey, has this solved your issue ?
uvzen said:
[QUOTE = "tecknight, post: 84584063, member: 2651082"]
[USER = 10585339] @uvzen [/ USER],
Dzieje się tak, ponieważ nie ma już "rzeczywistej" partycji systemowej .
Począwszy od systemu Android 10 , te partycje tylko do odczytu:
System
Sprzedawca
Produkt
System Ext
ODM
są teraz przechowywane dynamicznie w dużej stałej partycji o nazwie super .
Zalecałbym skontaktowanie się z programistą TWRP, aby dowiedzieć się, czy twoja wersja obsługuje partycje dynamiczne.
Aby uzyskać więcej informacji na temat partycji dynamicznych, odwiedź tę witrynę:
https://source.android.com/devices/tech/ota/dynamic_partitions
[/ZACYTOWAĆ]
Dzięki za informację.
Tak, moja wersja obsługuje partycje dynamiczne, ale mam problem, ponieważ chcę przekonwertować jedną aplikację na aplikację systemową w aplikacji link2sd, ale nie mam miejsca na partycji / system.
Click to expand...
Click to collapse
@uvzen,
You will need to use English in the future as XDA is an English only site. Just this time I translated your answer and I get:
Thanks for the information.
Yes, my version supports dynamic partitions but I have a problem because I want to convert one app to a system app in the link2sd app but I don't have space on the / system partition.
Yes, I can see why you would have that problem, the dynamic partitions are read-only and are in no way designed to be written to. In addition, changing your system partition directly can cause serious problems. It is usually MUCH safer to change your system partition when booted up under Magisk.
Is your device currently rooted using Magisk ?
tecknight said:
Yes, I can see why you would have that problem, the dynamic partitions are read-only and are in no way designed to be written to. In addition, changing your system partition directly can cause serious problems. It is usually MUCH safer to change your system partition when booted up under Magisk.
Is your device currently rooted using Magisk ?
Click to expand...
Click to collapse
Yes, I have the latest root magisk
uvzen said:
Yes, I have the latest root magisk
Click to expand...
Click to collapse
OK, check out this thread:
https://forum.xda-developers.com/t/mount-system-as-rw-on-android-10-with-magisk-20-4.4081043/
It explains the issue with the /system partition under Android 10+ and Magisk and specifically addresses link2sd here:
https://forum.xda-developers.com/t/mount-system-as-rw-on-android-10-with-magisk-20-4.4081043/post-83160125
The gist of the thread is that if you have SPECIFIC changes you want to make to the system partition. you can make them ONLY using a Magisk module, by inserting files into the filesystem.
I'm not sure if that would work with what you are trying to do or not.
tecknight said:
OK, check out this thread:
https://forum.xda-developers.com/t/mount-system-as-rw-on-android-10-with-magisk-20-4.4081043/
It explains the issue with the /system partition under Android 10+ and Magisk and specifically addresses link2sd here:
https://forum.xda-developers.com/t/mount-system-as-rw-on-android-10-with-magisk-20-4.4081043/post-83160125
The gist of the thread is that if you have SPECIFIC changes you want to make to the system partition. you can make them ONLY using a Magisk module, by inserting files into the filesystem.
I'm not sure if that would work with what you are trying to do or not.
Click to expand...
Click to collapse
Thanks, but I've already found a simpler method to convert as a system app on android 10 without Link2SD. I used this thread: https://forum.xda-developers.com/t/module-terminal-app-systemizer-v17-3-1.3585851/
This module is simple to use and it works.
uvzen said:
Hi, I had TWRP version 3.4.1B and wanted to resize file system in advanced wipe options, but it didn't show me the system partition. I mounted the system partition and the system partition still does not show up. I have installed the latest TWRP 3.5.0 and the problem exists.
Click to expand...
Click to collapse
Where did you find a trustworthy TWRP for joyeuse? On TWRP's official supported device list I can't find the Xiaomi Redmi Note 9 Pro (global version). The closest is the Xiaomi Redmi Note 9 Pro 5G (gauguininpro) but that's a different device.
There area few TWRP's that people share here, but I wouldn't trust those, I have no idea who made them.
Related
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
WARNING #1: CURRENTLY THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
USEFUL LINK OF TW ROMS:
http://forum.xda-developers.com/showthread.php?t=2616221
CURRENT PROJECT STATUS:
v3.72 (NB1): Beta testing, no rom-slots
v3.71 (MK2): Debugging some rom-slot issues
v3.65 (TW4.2): Stable
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (2 on the S4 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for 3 different sizes of /data partitions: 1GB, 2GB and 3GB. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press under the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting.
By "under", I mean on the touch key portion of the front display on either side of the center button.
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Go into your old Safestrap app and use the "Uninstall Recovery" button
THEN, open a "file explorer" of some sort (even TW "My Files" will work)
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK
Grant SU access
Use the "Install Recovery" button
All set, now you can reboot and re-activate whatever rom-slot you were using
KNOWN ISSUES:
[v3.72] ROM-SLOTs aren't supported yet
[v3.72] "Reboot Recovery" doesn't work in the APK?
NEW TO v3.72:
TWRP 2.7.0.x update for the base recovery. This includes vibration support, backup time/date fixes and more.
ROM-SLOTs now have a 16gb size limit (vs 4gb previously) [THEY DON'T WORK YET IN KK THO SO BE PATIENT]
DOWNLOADS:
CONFIRM THAT YOU ARE USING AN AT&T SAMSUNG GALAXY S4 (NOT THE ACTIVE MODEL)
MAKE SURE IF YOU ARE UPGRADING TO v3.7x FROM v3.65 THAT YOU USE THE "UNINSTALL RECOVERY" BUTTON IN THE v3.65 APK BEFORE INSTALLING v3.7x.
NOTE: USE ONLY ROMS THAT MATCH UP WITH YOUR TOUCHWIZ VERSION. IF YOU'RE ON MK2 THEN ONLY USE ROMS BASED ON MK2 AND IF YOU'RE ON MF3 ONLY USE ROMS BASED ON MF3
FIND YOUR STOCK OPERATING SYSTEM VERSION BELOW AND USE THAT FILENAME:
FOR USERS OF NB1:
USE 3.72+:BETA Safestrap-JFLTE-3.72.apk (updated 2014-04-02)
FOR USERS OF MK2:
USE 3.71+:BETA Safestrap-JFLTEATT-3.71.apk (updated 2013-12-27)
FOR USERS OF MF3 (TW4.2):
LATEST FILE: Safestrap-JFLTEATT-3.65.apk (updated 2013-11-15)
Main XDA Downloads Page
Mirror 1 (Goo.im)
Mirror 2 (Crackflashers)
ALSO DOWNLOAD THE KERNEL MODULES .ZIP THAT MATCHES YOUR BUILD # (FLASH THIS AFTER ROMS):
MF3: http://forum.xda-developers.com/devdb/project/dl/?id=508
MK2: http://forum.xda-developers.com/devdb/project/dl/?id=3275
HOW TO MANUALLY REMOVE SAFESTRAP:
[ INSTRUCTIONS ONLY FOR PRIOR TO v3.65. REMOVE VIA APK FOR v3.70+ ]
Enter adb shell from your pc:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
As of version 3.6x, Safestrap Recovery is now based on TWRP 2.6.3.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
This thread is a development ONLY thread.
For discussion go here:
http://forum.xda-developers.com/showthread.php?t=2428254
XDA:DevDB Information
Safestrap Recovery v3.71 (JB) / v3.72 (KK), a Tool/Utility for the AT&T Samsung Galaxy S 4
Contributors
Hashcode, DeesTroy & TeamWin
Version Information
Status: Beta
Current Stable Version: 3.71
Stable Release Date: 2013-12-27
Current Beta Version: 3.72
Beta Release Date: 2014-04-02
Created 2013-09-18
Last Updated 2014-04-02
Reserved
KNOWN ISSUES:
Bluetooth remote control isn't working on rom-slots.
CHANGELOG:
[2013/11/13] TWRP updates
[2013/11/13] "toolbox" binary / symlinks in recovery fixed
[2013/11/11] Uninstall from the APK fixed
[2013/09/17] /sdcard mounting bugfix
[2013/09/17] Hijack improments to support default rootfs files
[2013/09/17] ROM-slot image creation bugfix for size > 2gb
[2013/09/12] Much improved block device handling
[2013/09/11] Bugfix in script translation
[2013/09/11] hijack / init.rc tweaks
[2013/09/11] Bugfix for display lag / buffering issue (WIP)
[2013/09/10] Adjust "ROM-slot" display in UI
[2013/09/10] /data/media handling changes
[2013/09/06] custom twrp.fstab files
[2013/09/06] /data/media handling changes
Reserved
KNOWN ROM INSTALL / ISSUES:
All TW-based ROMs. If you don't have wifi make sure to flash the kernel modules for your stock kernel version.
Looks promising,
Thanks
Sent from my GT-I9505G using XDA Premium HD app
Add the MF3 kernel module .zip to the "Downloads" section.
http://forum.xda-developers.com/devdb/project/?id=680#downloads
Keep this on your SD card and flash it to the ROM-slot AFTER flashing a rom.
This will update your kernel modules to match the MF3 kernel and restore function to: wifi, bluetooth, gps etc.
Thank you so much hash!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
An at&t thread. Yes! andyfredrick
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hashcode said:
Add the MF3 kernel module .zip to the "Downloads" section.
http://forum.xda-developers.com/devdb/project/?id=680#downloads
Keep this on your SD card and flash it to the ROM-slot AFTER flashing a rom.
This will update your kernel modules to match the MF3 kernel and restore function to: wifi, bluetooth, gps etc.
Click to expand...
Click to collapse
WIFI WORKS!!!!!!!! and so does everything else...
Hash can i backup my stock rom to the external sd card and than delete it so i get my 10gigs back? is that safe?
hope this helps out some people!!.. nice job man!! :good:
Just install gpe wifi gps work! i also went back to stock rom and everything worked perfect
Andrew149 said:
WIFI WORKS!!!!!!!! and so does everything else...
Hash can i backup my stock rom to the external sd card and than delete it so i get my 10gigs back? is that safe?
Click to expand...
Click to collapse
God , no!
Sent from my SPH-L720 using XDA Premium 4 mobile app
rebel1699 said:
God , no!
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well that sucks! i hate having only 3gigs of user space =[
Graviton Rom works on SS... no issues at the moment ...what else are other users using?
---------- Post added at 07:12 AM ---------- Previous post was at 06:51 AM ----------
Can I flash performance mods zips only on slot 1 like killjoy or flyon mod etc? Or no because the stock kernel doesn't have init.d support?
Edit: as long as you flash to slot 1-4 everything will be safe. .. currently using darth stalker rom and that has init.d support, no issues at the moment.
HI
sykoj82 said:
Graviton Rom works on SS... no issues at the moment ...what else are other users using?
---------- Post added at 07:12 AM ---------- Previous post was at 06:51 AM ----------
Can I flash performance mods zips only on slot 1 like killjoy or flyon mod etc? Or no because the stock kernel doesn't have init.d support?
Click to expand...
Click to collapse
HELLO GREETINGS GUYS, GREAT JOB, I HAVE A DOUBT REGARDING THE SAFE ROMS SUPPORT STRAPS, AND ROM VERSIONS
1 - VERSION 4.3 SUPPORT? SS
2 - VERSION 4.2.2 SUPPORT? ROMS SUPPORT IS SS
3-THEME CAN FLASH MOD, ECT ..,?
* FINALLY HAVE MANY ROM Pacht LOKI LOKI IS DEVE install AFTER THE ROM OR NOT ONLY THE MODULE MF3? SORRY FOR MY ENGLISH I AM USING GOOGLE TRANSLATOR .. THANKS ..
HOLA CHICOS SALUDOS ,,GRAN TRABAJO,TENGO UNA DUDA EN CUANTO LOS ROMS SOPORTE PARA SAFE STRAPS,Y VERSIONES DE ROM
1- 4.3 VERSION SOPPORTE?SS
2- 4.2.2 VERSION SOPPORTE?SS CUAL ROMS SOPORTE
3-SE PUEDE FLASHEAR MOD THEME, ECT..,?
POR ULTIMO MUCHOS ROM TIENE LOKI PACHT SE DEVE INTALAR EL LOKI DESPUES DEL ROM O NO SOLAMENTE EL MODULO MF3 ? DISCULPEN POR MI INGLES ESTOY USANDO GOOGLE TRADUCTOR..GRACIAS..
So I've searched and searched, but can't seem to find a clear answer and I want to make sure of this before I try.
My "stock" ROMs are always CM-based 4.3 ROMs (haven't used TW in awhile). I got my S4 when it was still MDL so my qfuse isn't blown - so my intended use for this is only for the additional ROM slots. I have gathered that, at least for now, the only ROMs we can flash to the additional slots have to be TW or GPE 4.2.2. But my question is, does my primary ROM also have to meet that description? Or can I keep my 4.3 AOSP ROM as my primary?
AT&T Error
Hello,
I flashed the GEP rom to Rom Slot 1 and now I am getting an error that says Kernel Fail; System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help. There is a yellow triangle.
I followed the instructions, but now have a hosed phone unless I can somehow restore the backup of my stock rom.
Any information would be helpful.
Thanks for your efforts.
dtruong23 said:
Hello,
I flashed the GEP rom to Rom Slot 1 and now I am getting an error that says Kernel Fail; System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help. There is a yellow triangle.
I followed the instructions, but now have a hosed phone unless I can somehow restore the backup of my stock rom.
Any information would be helpful.
Thanks for your efforts.
Click to expand...
Click to collapse
Oh no...I hope I don't see that. I wish you luck! Was your phone encrypted to begin with?
Does anybody know why it would say this? Now I'm hesitant to flash anymore roms.
sykoj82 said:
Oh no...I hope I don't see that. I wish you luck! Was your phone encrypted to begin with?
Click to expand...
Click to collapse
Phone was not encrypted. I might have to take it in to AT&T or Best Buy Samsung Experience store. The phone gets into Download Mode, so at least that still works.
dtruong23 said:
Phone was not encrypted. I might have to take it in to AT&T or Best Buy Samsung Experience store. The phone gets into Download Mode, so at least that still works.
Click to expand...
Click to collapse
Wow...so far I flashed 2 different roms...I haven't tried the one you flashed...good luck to u... I'm definitely scared to flash any more roms...but you are 100% positive slot 1 was activated before flashing right? Thats the only thing I can think of that "stock" was activated..
dtruong23 said:
Phone was not encrypted. I might have to take it in to AT&T or Best Buy Samsung Experience store. The phone gets into Download Mode, so at least that still works.
Click to expand...
Click to collapse
What GPE rom did u flash?? did u flash the kernel module zip??
April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now !
https://twrp.me/google/googlepixelc.html
I would like to continue this thread for publishing test builds and other troubleshooting.
Once the changes are stable and tested I will merge them into TeamWin github for the next official build.
Known issues:
- FBE (file based encryption) is not working correctly, pls use FDE (full disk encryption) instead.
fwtool
The "fix fastboot" advanced menu item has been removed as it's not part of the official TWRP sources.
The fwtool is still existing (/sbin/fwtool) - only the menu item has gone.
If you need the fwtool, to fix fastboot, you can use it like before, but now you have to type the command into terminal inside TWRP.
For more details, pls have a look here .. http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
Installation:
Please install the new version from your current TWRP.
Pls make a "reboot to recovery" once you have installed the new version.
Of course you can install it via fastboot too.
Sources:
https://github.com/TeamWin/android_device_google_dragon
https://github.com/omnirom/android_bootable_recovery
DOWNLOAD:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
Have fun!
XDA:DevDB Information
[TWRP][dragon], Tool/Utility for the Google Pixel C
Contributors
followmsi
Version Information
Status: Stable
Current Stable Version: 3.3.1-2
Stable Release Date: 2017-04-01
Created 2016-06-17
Last Updated 2023-01-11
Changes:
Official 3.7.0_9-1 (2023-03-25)
- Exclude MTP
- Restore stock values for init.recovery.dragon.rc
- Enable Screen Timeout
https://dl.twrp.me/dragon/twrp-3.7.0_9-1-dragon.img.html
Official 3.7.0 (2022-10-10)
- New official version -> https://twrp.me/site/update/2022/10/10/3.7.0-released.html
Official 3.6.2 (2022-06-01)
- New official version -> https://twrp.me/site/update/2022/06/01/twrp-3.6.2-released.html
Official 3.6.1 (2022-03-10)
- New official version -> https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html
Official 3.6.0 (2021-11-28)
- New official version -> https://twrp.me/site/update/2021/11/28/twrp-3.6.0-released.html
Official 3.5.2 (2021-04-07)
- New official version -> https://twrp.me/site/update/2021/04/07/twrp-3.5.2-released.html
Official 3.5.1 (2021-03-17)
- New official version -> https://twrp.me/site/update/2021/03/17/twrp-3.5.1-released.html
Official 3.5.0 (2020-12-31)
- New official version -> https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html
Official 3.4.0-0 (2020-06-22)
- New official version -> https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Official 3.3.1-2 (2020-03-01)
- Script updates to improve encryption -> Thanks to updateing from Team Mokee !
Official 3.3.1-1 (2020-01-27)
- Script updates for Android 10
- Added more languages
- Fixed build issues
- New Kernel
Official 3.3.1-0 (2019-05-19)
- New official version
Official 3.3.0-0 (2019-04-10)
- New official version
Official 3.2.3-0 (2018-07-29)
- New official version
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Official 3.2.2-0 (2018-06-30)
- New official version
* DRM changes
Official 3.2.1-0 (2017-12-18)
- New official version
Official 3.2.0-0 (2017-11-29)
- New official version
Official 3.1.1-1 (2017-09-15)
- Including all changes for Oreo and for better en/decryption from unofficial V1 and V2
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O-v2.img (2017-09-11)
- New "pulldecryptfiles.sh" to copy all "bin" and "lib64" files from system/vendor partitions.
Unofficial 3.1.1-0 twrp-3.1.1-0-dragon-Android-O.img (2017-07-31)
- Official TWRP Nougat ramdisk mixed with new Oreo kernel binary to support Android 8.0 (SDcardFS .. etc.)
Official 3.1.1-0 (2017-05-17)
- Upgrade to 3.1.1-0
Unofficial 3.1.1-0 (2017-05-14)
- Latest TWRP changes (3.1.1)
- Latest kernel sources (2017-05-12)
- Latest LineageOS changes (Android 7.1.2)
Official 3.1.0-0 (2017-04-01)
- Removed "Data (incl. storage)" partition for usb-otg backup of "complete" data partition.
3.1.0-2
- Custom installer script problems should be fixed now.
3.1.0-1
- Removed all the FBE changes - will take longer to get it running on dragon
- Added NTFS-3G support for NTFS R/W -> USB-OTG
- Used new kernel binary with changed F2FS config
3.1.0-0
- @dees-Troy just tagged version 3.1.0 - made a new version based on latest sources.
- Added some more config changes for FBE.
3.0.3-4
- Used latest TWRP and AOSP soruces and enabled some features for FBE encryption.
3.0.3-3
- Added "Data (incl. storage)" partition for usb-otg backup of "complete" data partition
- fstab modification (usb-otg -> auto)
3.0.3-2
- F2FS enabled
- tegra-3.18 kernel -> v170210 (ntfs + f2fs enabled)
3.0.3-1
- Based on Android 7.1.1 AOSP -> android-7.1.1_r14
- Based on TWRP branch for Android 7.1
- tegra-3.18 kernel -> v170208 (ntfs + f2fs enabled)
v23
- Based on Android 7 AOSP -> android-7.0.0_r3
- Based on TWRP branch for Android 7
- tegra-3.18 kernel -> v160907
v22
- Based on Android 7 AOSP -> android-7.0.0_r1
- Based on TWRP branch for Android 7
- chromeos-3.18 kernel -> v160823
- Maybe not fully working as v21 due to new sources.
v21
- Added BRIGHTNESS PATH ... Thx to @ggow
v20
- Added Battery PATH ... Thx to @ggow
v19
- "Failed to unmount `/system `(Device or resource busy)" - Finally fixed now
- New versioning
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
v17
- "Failed to unmount `/system `(Device or resource busy)" - Not fully fixed - hopefully soon !
- chromeos-3.18 kernel -> v160618
v16
- ADB shell was not working in recovery - fixed now !
- chromeos-3.18 kernel -> v160617
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
DarthDestroyeis said:
Well done to both you and NYChitman!
I have noticed that when I go to make a backup, it finishes but is unable to unmount partitions after the backup saying that it is busy. If I reboot I am able to mount and unmount properly
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the feedback ..
Did you install something before .. maybe still mounted from before ?
Or you just made the backup only ?
Which partitions did you backup ? .. system as well .. or just data ?
Pls post recovery.log on pastebin.com .. helps a lot !
Thanks
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
DarthDestroyeis said:
http://pastebin.com/SDEw6EWL
Backed up system, data, vendor, etc.
Made a twrp backup before wiping to install new rom
System partition locks up and is unable to be wiped or flashed over until I reboot recovery
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
It´s always system which is complaining .. no other partitions, correct ?
Thanks ... will have a look.
Yup... just the system partition.
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
ilpolpi65 said:
N4 + Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip (flashed via fastboot) +TWRP_dragon_3.0.2-0_v16.img.
loop boot recovery..I tried everything but no chance to boot into system again
Click to expand...
Click to collapse
You did flash system-vendor update.zip via fastboot ?
No good idea.
The kernel and the TWRP are fine to flash via fastboot, but not the system.img and vendor.img.
Like written on first page of the updatr.zip thread.
Pls install the package via TWRP.
Or use unmodified stock image from Google for fastboot.
For recovery bootloop I know only "fastboot reboot".
I had the bootloop once myself, as I still was on M, but the command did help me.
YevOmega said:
Hey. I'm back. Considering taking the risk and installing TWRP again. Will I still be able to take OTAs? No, right?
Click to expand...
Click to collapse
I am not the OTA User
As I know, the tool "flashfire" from Chainfire should handle the whole OTA process smoothly.
The Update.zip packages I do anyway, because I am used to it .. over the years.
Did this for Nexus Flo ... Nexus 10 as well.
For Pixel C I just publish them, because nobody as else is doing it.
Look in Flo and manta xda .. They have these packages too, done by others.
Because of all the problems with OTA .. in the past ..and still today.
Today we have systemless root and regular OTA...times are changing.
Maybe it's time for something like flashfire in the next time ..
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
ilpolpi65 said:
sorry I made a typo :
I meant Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip ( I extracted boot.img)
Click to expand...
Click to collapse
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
followmsi said:
This should work .. the boot.img is just stock.
Were you rooted and decrypted before?
You did install SuperSu afterwards ?
And 'fastboot reboot' did not help either ?
People have reported they had to go back to M to be able to boot again.
There was one recovery bootloop with stock recovery as well ,
Maybe you try another kernel (boot.img) too ?
A fresh one .. below from the stock kernel
Strange issue .. for me not reproducable at all!
Sorry, can't help you better ..
Click to expand...
Click to collapse
True... It's really strange..but..pixel c too is a strange device...
anyway thanks for your help !
DarthDestroyeis said:
Yup... just the system partition.
Click to expand...
Click to collapse
v17
- "Failed to unmount `/system `(Device or resource busy)" - fixed now
- chromeos-3.18 kernel -> v160618
Please have a try with v17.
My problems are gone .. no more warning messages while doing backup or restore.
"Failed to unmount `/system `(Device or resource busy)"
Pls test as well !
Thanks
sorry for all this quick releases today .. this is the last one for now !
but when something new is working .. I would like to share it with you ...
v18
- MTP is working in recovery now !
- Added dragon keyboard layout files
Enjoy !
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
redukt said:
Moah ey..... Yesterday I may had need it urgently ´cause I can´t restore a nandroid lol - this fuxxing mount issue...
Well but a clean flash and set up the device completely new is always a pleasure - isn´t it?
Will test it asap and thx again for your hard work
Click to expand...
Click to collapse
Today I have made 3 backups and restores
No problems or messages so far ..
But pls test on your device as well .... On Pixel C you never know
Cheers
Ok, will test it now without wipes
redukt said:
Ok, will test it now without wipes
Click to expand...
Click to collapse
Hopefully
*Only tested on TA-1032 but it should work on other models too*
Downloads:
Build 1:
https://mega.nz/#!qIhFkKia!AkUMvQJ0PGVnSePabTvOgO-oUAMZahlCNaZfy2gE4vE
This TWRP now supports removing data encryption on Oreo.
General Changelog for TWRP version:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Changelog:
Build 1:
- Initial release
What works:
- Touch
- OTG
- Backup (system.img backup doesn't work but don't worry, you can backup System and you'll be fine)
- Restore
- Flashing IMGs and ZIPs
What doesn't work:
- Battery percentage is incorrect (it's possible to fix but need some time)
- MTP (it's possible to fix but need some time)
- you tell me
For full backup you need to remove encryption so you can backup /data too.
If you're wondering why protect_f, protect_s, para and uboot partitions have 0MB it's because these partitions have less then 1MB.
Comment if link need to be updated.
Credits:
@mohancm for Lenovo K4 Note TWRP
Screenshots:
i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1
Riadh300 said:
i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1
Click to expand...
Click to collapse
i installed it without problems, tell me your device model and how you installed it.
Worst thing that could happen is that recovery got bricked, to recover simply flash new recovery. it worked for me, with twrp flash img, with flashify and with SP Flash Tool. Maybe you flashed it in wrong way.
Also please can someone flash/test this twrp so i can see does it work for others.
System and Data can be backed up and restored on oreo with this twrp?
Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It
ChalapathiRevanth said:
Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It
Click to expand...
Click to collapse
Top.
Thank you
Reygal21 said:
System and Data can be backed up and restored on oreo with this twrp?
Click to expand...
Click to collapse
data can be backed up only after removing encryption, system can be backed up without problems.
As for restore, it works on Nougat (i restored whole rom when i tried substratum theme)
but i didn't tested for Oreo.
I think that will work on Oreo too because there is no change in partition mount points between Nougat and Oreo.
Update:
I found out that incorrect battery percentage and MTP are not kernel issue so it is possible to fix it.
Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !
Nikola Jovanovic said:
Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !
Click to expand...
Click to collapse
it's ported from Lenovo K4 Note TWRP which have MT6753 CPU
Though i noticed that medifire007 is smother, especially when changing storage. This TWRP have latest TWRP version and touch works smoothly while on mediafire007 TWRP you need to wait in beginning to work.
Can this work on Nokia 1 with Android Oreo 8.1?
abdul_manan said:
Can this work on Nokia 1 with Android Oreo 8.1?
Click to expand...
Click to collapse
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.
SkaboXD said:
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.
Click to expand...
Click to collapse
Thanks Bro! It worked! But there is a new problem Now. Here it is..
https://forum.xda-developers.com/nokia-1/help/stock-recovery-error-nokia-1-black-t3798928
Tested and working on TA-1028 variant with Android nougat. Installed SuperSU and everything seems okay. Thx dev:victory:
Is there any custom Rom and kernel for Nokia 3 .
Stock Nokia 3 Rom and kernel is really bad
Can i use for Nokia 3 locked bootloader???
How to install ?
please Post Nokia 3 TA1032 Android 8.1 Custom recovery
Umairali321 said:
please Post Nokia 3 TA1032 Android 8.1 Custom recovery
Click to expand...
Click to collapse
Doesn't work on 8.1? Did you tried it?
Havoc 3.0 Q gsi fixed build for Huawei P10 Lite
About
Originally Havoc 3.0 Q gsi based on v204 compiled by ExpressLuke , but for Hi6250 some bugs persist , so I managed to fix them and repacked the IMG then highly compressed.
Fixed
* Camera * media ( sound , video , YouTube ..) * NFC * battery usage * auto brightness * phone Info's ( build number , model , manufacturer , device name .. ) * added Havoc bootanimation .
Bugs
* Offline charging ( requires permissive kernel , Labyrinth kernel 2.0 by Dil3mm4 tested * Blurry can be fixed in phh treble settings > Huawei features > 3rd option ( disabling hwcomposer ).
Installation
* Extract img from xz archive * go to TWRP and do a full wipe (system, data, cache, dalvik/art cache) * flash the image in system image partition * flash root (optional) NOTE1: If you are coming from Android 9 flashing root is a MUST DO ! NOTE2: Flash only the Magisk zip linked in this post ! * reboot to System * reboot to TWRP * flash gapps (optional) * Enjoy !!!
Download
https://mega.nz/#!2S4xxQ6C!f0KJlCA_9_yyJzWZAtlNYVJHktSuyyFY7p82kXK4caM
Twrp recommended ( by @Pretoriano80 ):
https://mega.nz/#!LLhBXSzY!3runNNoW9z1tOHSu-heIUhyy-4u8XHvc8rZMsn547so
Magisk.phh:
https://mega.nz/#!uX4k1KjS!2gnUV3IyLt8XXf4NO3RyZEJnt5YNJQ8tY9i11oGfKYM
Credits: @phhusson ExpressLuke @haky 86 @DarkJoker360 @Dil3mm4
Regards!
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x,bootloader unlocked and TWRP
Based On: AOSP
Version Information
Status: Stable
Created 2019-12-01
6 hrs SoT
Hami_Do said:
6 hrs SoT
Click to expand...
Click to collapse
Wow that's really impressive for a 3000 mAh device! Many people aren't getting that on the Note 10 Plus!
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
No, it's simply Havoc GSI with several fixes included especially for our device/platform and no, gapps are not included (you would have known if you read the first post more carefully )
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Hami_Do said:
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Click to expand...
Click to collapse
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
TureX said:
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
Click to expand...
Click to collapse
the suggested twrp in first post works perfectly on most hi6250 ( emui 8 ) , plus it has an option ( exclude OEM path from data wipe ) from there you don't need to format data & internal storage to boot any gsi/dssi AFAIK.
Only sometimes installing gapps requires resize system from advanced wipe menu.
thanks.. any build for havoc 2.9 ?
How can I remove the bottom pad that appears when I want to use the keyboard?
itsm03 said:
thanks.. any build for havoc 2.9 ?
Click to expand...
Click to collapse
the best 2.9 build here:
https://sourceforge.net/projects/ha...90912-phhgsi_arm64_a-Official.img.xz/download
1- wipe system data cache
2-flash havoc 2.9 and boot up to system
3- reboot to twrp and :
4- flash offline charger fix for pie
5- flash nfc patch for pie
6- flash hwcomposer ( follow instructions )
7- flash gapps and magisk ( optional )
Enjoy.
All flashable patches you find them here:
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
ghassan haddad said:
How can I remove the bottom pad that appears when I want to use the keyboard?
Click to expand...
Click to collapse
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Hami_Do said:
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Click to expand...
Click to collapse
I Couldn't post pictures since new members need to wait, add to that I got only one answer telling me that it may not be possible.
I was referring to this pad in the picture
Now Gsi's based on v207 and later are stable , here you find latest Havoc Q gsi :
https://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/ARM64/A/
Probably only NFC patch is needed :
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745/page3
=========
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Achieve is currupt :-/
i get Error while flashing image, here is the log
Erro 255
I get error while flashing image here is the log
I have the saame problem on WAS-LX1
anvetoti said:
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Click to expand...
Click to collapse
Any help?
Help this guy and me, please!
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
NeoPreacher said:
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
Click to expand...
Click to collapse
I think you're right, I also think it's due to encryption or data partition (not magisk because I made a clean installation), because I had the same problem, stuck on boot, with all the Roms (PIE and Q) that require TWRP.
The only rom without problems was OpenKirin-OmniROM Pie Alpha 6.2 which does not require a custom recovery for installation !!
Do you have any operational suggestions to give me or I just have to try with pretoriano's twrp_0.5_test ??
What do you think if :
- In a stock recovery I do a factory reset
- From fastboot I do fastboot erase system, userdata and cache (or better to use format command for userdata?)
- the I flash system.img
- then I flash TWRP
- and then install magisk and gapps from TWRP?
TX
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.5.1 :
Wrappedkey support running only on FBE devices - CaptainThrowback
TWRP App log information reduced - epicX67
Refresh details after system wipe and adb sideload - AdrianDC
Chinese translation updates - betaxb
Support keymaster 2 - PeterCxy
add tzdata to TWRP for timezones - CaptainThrowback
ParitionManager: support delayed adopted storage mount - PeterCxy
Support to start terminal from file manager directory - AndroiableDroid
Nano support - nebrassy
Add nano support to open files from file manager - CaptainThrowback
Include new magisk apk support to be installed by TWRP - ianmacd
Add support to change directory name where TWRP stores backups - epicX67
Add bash support - not the default shell - DarthJabba9
ORS support to format data - AdrianDC
Add support to flash both slots when flashing an image - epicX67
NL translation updates - ianmacd
Cleanup
Installation cleanup - remove dupe PackageExtractFn - klabit87
Remove logd-reinit service - CaptainThrowback
Fixes
Restore system root context - bigbiff
Only include keymaster 2 if tree supports it - CaptainThrowback
Strip lines containing '--' in language_helper.py - ianmacd
Unlocalized string fix - ianmacd
DOWNLOADS: twrp-3.6.2_9-0-ginkgo.img
HOW TO FLASH:
Fastboot Method :
fastboot flash recovery twrp-3.5.2_9-1-ginkgo.img
Boot to OLD TWRP > INSTALL > Select Image > Navigate to twrp-3.5.2_9-1-ginkgo.img > Select it & Swipe to Flash
CREDITS:
TeamWin
CyanogenMod/Lineage Android
XDAevDB Information
[RECOVERY][OFFICIAL]TWRP-3.5.2 for Xiaomi Redmi Note 8/8T, Kernel for the Android General
Contributors
Erwinabs
mauronofrio
Source Code: https://github.com/TeamWin/android_device_xiaomi_ginkgo
Version Information
Status: Stable
Features:
- Decryption works
- Otg works
- Backups works
- Flash Rom works
- F2FS support
- Fastboot boot command support
- Compatibility.zip error fixed
- Willow fully supported
- Android 11 Decryption
- Android 12.1 Decryption
- Android 13 DecryptionDOWNLOAD BUILD :Base A9
twrp-3.6.2_9-0-ginkgo.img64M2022-06-05 20:01:45 UTCtwrp-3.6.1_9-0-ginkgo.img64M2022-03-13 23:24:43 UTCtwrp-3.5.2_9-1-ginkgo.img64M2021-07-04 14:16:19 UTCtwrp-3.5.2_9-0-ginkgo.img64M2021-04-05 05:10:04 UTCtwrp-3.5.1_9-0-ginkgo.img64M2021-03-13 23:04:47 UTCtwrp-3.5.0_9-1-ginkgo.img64M2021-03-06 17:20:59 UTCtwrp-3.5.0_9-0-ginkgo.img64M2020-12-28 17:19:58 UTCtwrp-3.4.0-1-ginkgo.img64M2020-07-22 22:06:01 UTCtwrp-3.4.0-0-ginkgo.img64M2020-06-22 11:27:29 UTCtwrp-3.3.1-1-ginkgo.img64M2020-02-15 00:04:51 UTCtwrp-3.3.1-0-ginkgo.img64M2019-12-05 00:59:27 UTC
Base A10
twrp-3.5.2_10-2-ginkgo.img64M2021-09-26 17:01:39 UTC
Base A11
twrp-3.6.2_11-0-ginkgo.img64M2021-09-26 17:01:39 UTC
Base A12.1
twrp-3.6.2_12-0-ginkgo.img64M2022-07-11 17:01:39 UTC
twrp-3.6.2_12-1-ginkgo.img64M2022-07-2217:01:39 UTC
twrp-3.6.2_12-2-ginkgo.img64M2022-09-21 17:01:39 UTC
Guide Install TWRP - HERE
Does this work with the android 11 decryption? Because my current 3.4x keeps saying "Unable to Decrypt FBE".
22naresn said:
Does this work with the android 11 decryption? Because my current 3.4x keeps saying "Unable to Decrypt FBE".
Click to expand...
Click to collapse
Yes work
Great, I'll try it out!
22naresn said:
Great, I'll try it out!
Click to expand...
Click to collapse
yes, everything is working fine
my suggestion：hiding the persist partion to avoid someone wipe it by mistake。
Suit yourself
wsdyleon said:
my suggestion：hiding the persist partion to avoid someone wipe it by mistake。
Suit yourself
Click to expand...
Click to collapse
Thanks
wsdyleon said:
my suggestion：hiding the persist partion to avoid someone wipe it by mistake。
Suit yourself
Click to expand...
Click to collapse
And hiding it for backup and restore too? I don't think it's a good idea.
x3r0.13urn said:
And hiding it for backup and restore too? I don't think it's a good idea.
Click to expand...
Click to collapse
persist is needed when you lose imei
x3r0.13urn said:
And hiding it for backup and restore too? I don't think it's a good idea.
Click to expand...
Click to collapse
u r →，it's not a good idea for someone。That was the fault that who first “display” the persist partion。
the best solution i thought was that giving one special option to whether display the persist partion
can you guys work on metadata based encryption
to decrypt it.
iamsaalim said:
can you guys work on metadata based encryption
Click to expand...
Click to collapse
Yes bhai
Cool cool
Anyway to force flash this via QFIL?
Every time i connect to internet the phone blocks via mi account.
Do not have the number ou access to the registered mi account anymore.
Anyone knows how to solve this withwout contacting a shaby russian that have the misteryous authorized account?
Erwin Abs said:
DOWNLOAD BUILD :
Official Build :- twrp-3.5.2_9-1-ginkgo.img
Unofficial Build :- recovery_3.5.2_9-Unofficial.img
Click to expand...
Click to collapse
Any clear summary of differences between official and unofficial builds?
pnin said:
Any clear summary of differences between official and unofficial builds?
Click to expand...
Click to collapse
no special difference, just add it
Nixye said:
Anyway to force flash this via QFIL?
Every time i connect to internet the phone blocks via mi account.
Do not have the number ou access to the registered mi account anymore.
Anyone knows how to solve this withwout contacting a shaby russian that have the misteryous authorized account?
Click to expand...
Click to collapse
Dont know , search in youtube
Changelog:
- initial Build A10
twrp-3.5.2_10-0-ginkgo.img