Related
Turbo kernel 12 broken file?!
xXxAresxXx said:
Turbo kernel 12 broken file?!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1817548&page=68
The download link work but the file .img is damaged and so don't work !
... No, it's not broken. Either your internet is failing to download the file, or you failed to read instructions and made an idiot mistake. Since we can't help your ISP, let's assume the latter. Please tell us detailed steps you've taken.
Sent from my R800x using xda premium
Trygon said:
... No, it's not broken. Either your internet is failing to download the file, or you failed to read instructions and made an idiot mistake. Since we can't help your ISP, let's assume the latter. Please tell us detailed steps you've taken.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
I'm operating with windows 8 ..And when i try to open file (.img) it say: Damaged File
I've try to download more times but it is the same..
My problem isn't this ...When i finish to follow the steps (flash kernel and rom recommended) the phone don't start ...Start but only the written sony and autoreboot ...What's wrong?
I follow this step
Downloads/Installation
Please Nandroid backup before flashing. I am not responsible for any permanent damage or data loss. I try my best not to wreck your stuff though
If you are running Turbo r8 or older, the partition map has changed (30MB moved from data to system). You MUST Nandroid Backup before flashing the r9 update, then Nandroid restore after flashing. Otherwise you WILL lose your data.
GSM ONLY - You must have a vendor-unlocked partition layout - this only needs to be done once, if you have flashed my MIUI Australia ROM in the past or an official Neo L FTF, you already have it and can skip this step. If not, flash this full FTF first which is the same as .64 FTF but with the required vendor partition to format the unallocated space (it will completely wipe your phone) - R800i_4.0.2.A.0.62_phoenixvendor.ftf on Google Drive
CDMA ONLY - No need to flash any FTF, it seems R800x already has an unlocked vendor partition.
Ensure your ROM is less than 310MB system size. If you are not sure or don't know how to check, contact your ROM builder.
Download and flash the kernel -
Turbo Kernel r12
First-time users - Enter Multiboot Menu (Vol-Down key) and go to Internal > Recovery, then format system, data and cache before doing anything else. Very important.
If you cannot enter the Boot Menu or Recovery after flashing, you need to flash the FTF first.
xXxAresxXx said:
I'm operating with windows 8 ..
My problem isn't this.. but When i finish to follow the steps (flash kernel and rom recommended) the phone don't start ...Start but only the written sony and autoreboot ...What's wrong?
I follow this step
Downloads/Installation
Please Nandroid backup before flashing. I am not responsible for any permanent damage or data loss. I try my best not to wreck your stuff though
If you are running Turbo r8 or older, the partition map has changed (30MB moved from data to system). You MUST Nandroid Backup before flashing the r9 update, then Nandroid restore after flashing. Otherwise you WILL lose your data.
GSM ONLY - You must have a vendor-unlocked partition layout - this only needs to be done once, if you have flashed my MIUI Australia ROM in the past or an official Neo L FTF, you already have it and can skip this step. If not, flash this full FTF first which is the same as .64 FTF but with the required vendor partition to format the unallocated space (it will completely wipe your phone) - R800i_4.0.2.A.0.62_phoenixvendor.ftf on Google Drive
CDMA ONLY - No need to flash any FTF, it seems R800x already has an unlocked vendor partition.
Ensure your ROM is less than 310MB system size. If you are not sure or don't know how to check, contact your ROM builder.
Download and flash the kernel -
Turbo Kernel r12
First-time users - Enter Multiboot Menu (Vol-Down key) and go to Internal > Recovery, then format system, data and cache before doing anything else. Very important.
If you cannot enter the Boot Menu or Recovery after flashing, you need to flash the FTF first.
Click to expand...
Click to collapse
..
What do you mean tried to open.img file?This is the boot file to fastboot to phone you don't need to open it! I am using it at the moment from same link no problems.Also try this "Using Fastboot may trigger a "boot menu loop" - simply enter CWM-Recovery for any slot and then select reboot to solve it."That quote is from CosmicDan page.I would suggest reading his instuctions again.:fingers-crossed:
tallman43 said:
What do you mean tried to open.img file?This is the boot file to fastboot to phone you don't need to open it! I am using it at the moment from same link no problems.Also try this "Using Fastboot may trigger a "boot menu loop" - simply enter CWM-Recovery for any slot and then select reboot to solve it."That quote is from CosmicDan page.I would suggest reading his instuctions again.:fingers-crossed:
Click to expand...
Click to collapse
Ok thank you.. I'm new with development and so i'm not very good ^^ thanks
I try and let you know
Hi!
!!! First things first: big phat huge !!!THANKS!!! to the full TeamWin Team, SGCMarkus (initial twrp tree), Phoenix591 (for inspiration), Dees Troy (for his trees), z31s1g for his brilliant theme and Captain Throwback (inspiration, too) !!!
For Pie ROMs you should use 3.3.1 recovery, either OrangeFox (based on TWRP with many very useful additions, with Magisk module manager being only one of it :good: ), or good old TWRP itself. 3.3.1 needed for decryption of pie ROMs!
Feature list:
- capable of installing treble and/or vendorized ROMs
- Possibility to leave out lockscreen settings when restoring a backup (sometimes you have to delete them manually, otherwise no login into your restored ROM possible -.- You can bypass this with this. Note: lockscreensettings are independent from your encryption settings)
- Time and date is showed correctly, independent of /data
- some extra partitions (see below)
- Oreo 3.2.3-7: compiled with (modified) 8.1 TWRP branch
- Oreo recovery: Decryption of AOSP up to 8.1 and stock ROMs userdata is working (cherrypicked stuff for bringing that up), so, with this recovery, the urgent need for flashing no-verity-opt-encrypt zip isn't there anymore
Pie is not decryptable for the moment, neither with old Oreo recovery nor with newer PIe recovery: this is being worked on. Encryption changed in Pie, this needs some extra "love"
- everything working: backup, restore, decryption, time, mtp, adb, installing of treble or vendorized builds, themeable, .........
- modem image support: backup, restore, flashing of modem images either taken directly from kdz or via diskdump (this already was available but then broken at some point of time, sry for that! ).
- Same for OP image
Don't forget your timezone settings after flashing. Also there are some extra partitions you can mount/backup/flash/explore, like LAF, persist-LG and OP configs. There's the thought of some people to flash TWRP as a second copy to LAF partition to be on the sure side when it comes to ROM switching or sth like that. You can do this, anyway it's not really recommended (by me and some others) because you'll lose download mode, but you now have the option.
Also, if you want to restore an older backup, don't restore 'firmware' from it!!! This will break your WLAN, at least, and you have to flash a modem.img to get it back working.
For extra partitions: Some of them are needed for decryption (modem / persist-lg (drm)), some are for VoLTE (OP), time is stored on /persist/time (and /data/vendor/time), modem should be known and the LAF partition should be known already (described above).
For decryption: it works as it should. Therefore it is a little bit tricky to restore a ROM which has encrypted userdata, when you'd installed any other ROM in between. or formatted data There are some points to remember when restoring, a little guide is available in 3rd post, and some tipps too.
Some instructions:
How to flash?
If starting fresh with an unmodified phone, this thread should help you installing it
When you already have TWRP installed, you can flash this recovery from within TWRP:
- Tap "Install"
- Tap "Install image" button, located down right
- Locate your downloaded image and select it
- Select "recovery" from the list which shows up then
- Install; and reboot to recovery after installing immediately, don't use it for any other tasks until rebooted pls, as it may not function. Things can go bollox when phone wasn't rebooted to recovery after installing.
And of course you can flash it via fastbootmode. Reboot to bootloader (adb reboot bootloader; when magisk is installed, you can use magisk manager => module => menu on the top right => reboot to bootloader. You can reboot to recovery from there too) and then:
fastboot flash recovery <twrp-image-name.img>
When you experience errors or sth isn't working as it should in your opinion:
When an error occurs, pls supply me a log from TWRP, taken immediately after the error showed up. You can use the "Copy to SDCard" option (advanced options) in TWRP for this. Grab this file then and upload its content to pastebin.org.
I can't help without as much detailed info as you can supply. This should include at least following information: phone model, used TWRP image (exact name of image), task you wanted to do (which ROM e.g.).
There's now an optional version of TWRP available, which contains the inclusion of internal storage in data backups (IntSD version). Exclusions (folders which won't be backed up): TWRP, Movies, Music and Download folders. These won't be included in backups, as they can be really big.
With the recovery including internal storage you can backup to internal and external storage, no matter. The data_image recovery can backup its data image to external sd only, of course.
If you want to use data_image, system_image or internal storage included in data backup, first check your filesystem on your external sdcard. It needs to be capable of writing big files, which isn't the case with fat/fat16/fat32. You need exFAT (for stock) or ext4/ntfs (only available with custom kernel and/or AOSP based builds).
DOWNLOADS:
Oreo and Pie capable 3.2.3-7 TWRP:
Download links (always the latest and newest only; one version for all):
File name: TWRP-3.2.3-7-DataIMG.img (default)
MD5sum: aac1525f9bd85d6efbc0fb65bda4a904
MAIN Download: AndroidFileHost - TWRP-3.2.3-7-DataIMG latest
File name: TWRP-3.2.3-7-IntSD.img (non-default, includes main part of internal storage in data backup)
MD5sum: 23113ad33772a5f783dcabd09fa97ebb
MAIN Download: AndroidFileHost - TWRP-3.2.3-7-IntSD latest
Some additional words to different versions;
I personally use internal w/ sdcard backup, all my pics and almost everything possible app related on my phone is on external SDcard. Some data always remains on intSD (e.g. whatsapp, the Android folder which contains settings and app data too, k-9 mail folder and others), this needs to be in a backup for me. This is, what the intSD version does: but it leaves out the big folders (download, music, movie and TWRP).
As always: Use it at your own risk! You are the one who changes stuff on your phone, I'm not responsible for anything which happens to your phone. TWRP is powerful, be careful at what you do with it :good: And it just works.
All you need to compile this yourself:
[url]https://github.com/seader/android_device_lge_joan-twrp[/url]
[url]https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni[/url]
[url]https://github.com/seader/android_kernel_lge_msm8998[/url] (not really needed as a prebuilt kernel is used)
[url]https://github.com/seader/bootable_recovery-twrp[/url] (copy of twrp recovery with encryption cherrypicks and the stuff added. encrypt-8.1 branch = intSD version, master branch = DataIMG version)
Features:
- Treblelized / vendorized: one recovery for all
- Time and date working, getting this from persist partition
- decryption working for both stock and AOSP up to 8.1; Pie is being worked on [break atm ]
- additional partitions available
- "data_image" (default) and "internalSD included" (non-default) available
- Checkbox for leaving out lockscreensettings when restoring data partition (available in main settings and restore settings; in supported themes in main settings only!)
- TWRP app removed
Changelog:
21. April 2019, TWRP 3.3.0-00, new Pie recovery:
- Newest sources used, pie branches everywhere
- tiny menu structure overhaul
- almost all the stuff from Oreo recovery back in, except:
-- decryption
-- data image function
-- inclusion of internal sdcard in backups
-- everything else is working and included (special partitions, time and date working, all the default functions working, exclusion of lockscreen settings when restoring, TWRP su and app removed)
08. Dec. 2018, TWRP 3.2.3-7, old Oreo recovery:
- OP image flashing function added
- Sources update
Older:
09. Nov. 2018:
- treble ROMs are now installable
- brought back modem partition, fully working (remember to NOT restore the "firmware" partition!)
02. Nov. 2018:
- switched from prebuilt kernel to inline kernel building for easier future updates in terms of pie / treble
- removed modem/firmware partition from backup list
- included some QCOM optimizations for buildtime
- excluded TWRP app, install prompt for this app shouldn't pop up anymore (not tested by me)
- disabled logcat
26. Oct. 2018:
- increased compatibility for some scripts / flashable zips
25. Oct. 2018:
- added optional recovery with internal sd content added to data backups (the "data_image" version is the one you already may have installed, like 3.2.3-4-f, just renamed and containing the fstab edits)
- little fstab changes regarding modem / firmware: pls update
18. Oct. 2018:
- removed decrypt files from RAMdisk and added a link to firmware instead
- added possibility to leave out lockscreen-db* files while restoring
- added data_image option; read post #3 pls
15. Oct. 2018
- added decryption of stock and AOSP based ROMs
12. Oct. 2018, pt. 2 (succesful)
- finally fixed the OP mysery... A typo from my side, sry!!
12. Oct. 2018, pt. 1 (failed)
- Added versioning, TWRP now is 3.2.3-1
- re-sorted partitions list
- OP partition won't cause an error anymore on phones where it doesn't exist; sry, didn't know, that US998 doesn't have a OP partition! In addition, it doesn't look for me like there is an equivalent partition on these phones...?
11. Oct. 2018:
- fixed some warnings
- added some additional partitions
- made OP flashable and backupable
- made vendor 'removable', so no warnings anymore for non-vendor devices
- included logcat
- added local_manifest, patch for timefix and a little description in readme
How to (re)boot to TWRP?:
If your phone is rooted:
- Magisk has options to reboot to different targets like bootloader or recovery, but this menu is a little bit hidden: you can access it by starting Magisk.Manager, going to the "Module" menu, tapping on the three dot menu on the top right. Then select your target
- If a terminal emulator is installed, open it, type "su" followed by enter and type "reboot recovery"
- You can do the same with an adb shell, open a shell and type the commands from above, they're the same
- There also are apps for rebooting to recovery or other targets. Just search around in PlayStore
- The good old "button dance" When phone is powered off, press the volume down key and power button at the same time. When a first sign of life is seen on display, immediately release the power button, but just to instantly press it again. A menu will show, which wants you to do a factory reset: do it You have to confirm this two times, and afterwards TWRP will boot without performing a factory reset. TWRP is compiled with a flag which recognizes this procedure and hinders the bootloader to pass the command for factory resetting.
Some additional infos:
- vendor partition: it's there for everyone (no more present in TWRP 3.3!). It is flagged as removable, so it can be leaved in fstab without producing errors. Ppl w/o a vendor partition (which you need to create via script when you want to flash treblelized AOSP builds) shouldn't let themselves get confused about that, it's an additional entry like external sdcard or USB OTG.
- kdzwriter: still untested (and no more present in 3.2, in 3.3 it never was), respectively tested with 21h kdz, which told me "not applicable for this device". I for know mark this as non-working. I'll leave it in this recovery, for future updates and other testers with other kdz file (no more inside).
- data image backup: chose SDCARD for backup location, and enable compression otherwise it's an ~55gb image lol. (<= it IS an 55gb image, no matter of compression. Compression doesn't work for images! So prepare for a huuuge file, and think about your filesystem on sdcard (can it handle big files? For AOSP you can chose ext4 or exfat, for stock exfat only)). This option includes internal sdcard, which is in /data/media. This can be used to do a real full backup with absolutely everything needed (incl. /sdcard/Android folder, your music, vids or anything else e.g.).
- time: when it goes wrong again, just delete the /persist/time folder from within recovery, boot up android and reboot to recovery. Should be "fixed" now. This folder isn't present in 3.3: here you can try to delete "/persist/.twrps" file (you need to re-setup TWRPs settings then) and the folder "/data/vendor/time", followed by a reboot to ROM and then to recovery again. May ned one or two reboots more to ROM or TWRP to get TWRP recognize the time correctly.
Encryption:
There's something you need to remember when restoring encrypted backups, after you have flashed another ROM (which differs from the one to restore): your secure startup settings. Write them down or have them in mind, you need it. Steps for restoring an stock or AOSP data partition encrypted backup:
- format data
- first restore your ROM only partially, means only boot and system (and only that)
- boot into your ROM you've restored
- go through the setup manager and afterwards hop into security and encryption settings
- encrypt your phone exactly the same way it was in your backup you want to restore encrypted userdata from; for 3.3 recovery it's only needed to set up any encryption config, you can put in what you want for yourpin / pattern / passwd
- if it is encrypted already, you only have to redo security settings. Use the same settings as in the backup, means pin/pattern/pw need to be the same *and* secure startup too, if you've chosen it before (see above for pie and 3.3 recovery: you can use anything. Youcan try this with oreo too, maybe it works too)
- reboot to recovery again and restore your encrypted data partition (from the backup you've already restored system and boot from)
- now you're good to go You should tick "Don't restore lockscreen settings" for leaving out the lockscreen.db* files. Otherwise you have to delete them manually to be able to get into your ROM, because lockscreen settings will prevent it. Lockscreen settings btw. are independent of encryption settings. It's the same pattern/pin/pw used, but another building site.
If you want to encrypt your AOSP ROMs userdata (only possible if you are on android up to 8.1), you can use the attached fstab file (it's for LOS 15.1 non treble), either as an example or to overwrite the existing one. Have a look at the line which contains "userdata". The fstab file is located in /system/vendor/etc/. Unzip the attachment (it is no flashable zip), put it in the correct location and overwrite the original file. Reboot your phone, then go into security settings, you should now be able to encrypt it.
This TWRP can't handle decryption of AOSP 9.0 encrypted data atm, you need 3.3 TWRP for that. There changed something from 8.1 to 9.0 which means the new stuff needed new recovery, which is included with 3.3 recovery.
Additional stuff:
- Recommended theme (original thread): [THEME][TWRP] TWRP Materialised - Black / Dark / Light / Play [27/01/18]
Edited versions of this theme, with menu entries added:
Black and Dark theme versions available here. There are two version of each: one showing "incl. internal" and one without, both have the lockscreen settings exclusion checkbox included. You'll now find this menu entry in main settings page only, it was there before too, but there was an additional entry when restoring a backup. This is gone in this theme as it didn't fit the way I wanted it to fit Pick the one you need.
Included storage: version for recovery "IntSD"
Without storage: version for recovery "DataIMG"
can i just update it by flashing it in the twrp 3.2.1-02 treble as img?
seadersn said:
reserved #2
Click to expand...
Click to collapse
What's the difference between the AFH file and Mega file?
Sent from my LG-H932 using XDA Labs
black metallic said:
can i just update it by flashing it in the twrp 3.2.1-02 treble as img?
Click to expand...
Click to collapse
yes, and then reboot to recovery again
TWRP can simply be updated that way.
BROKEN1981 said:
What's the difference between the AFH file and Mega file?
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
Im 99.9% sure thats a mirror, incase AFH is slow again.
SGCMarkus said:
yes, and then reboot to recovery again
TWRP can simply be updated that way.
Im 99.9% sure thats a mirror, incase AFH is slow again.
Click to expand...
Click to collapse
I figured as much. I had a night that AFH wanted 3 hours to download TWRP. A Google speed test gave me 78mbps.
So yeah, seems Mega is the way to go
Sent from my LG-H932 using XDA Labs
First, thanks for this. Second, what's the difference b/w the earlier "tfp" img and this "tfp-kdz" img?
joarce said:
First, thanks for this. Second, what's the difference b/w the earlier "tfp" img and this "tfp-kdz" img?
Click to expand...
Click to collapse
Stated in op. This image allows for writing of some stuff from kdz files.
Sent from my LG-US998 using Tapatalk
jip, thx
SGCMarkus said:
yes, and then reboot to recovery again
TWRP can simply be updated that way.
Im 99.9% sure thats a mirror, incase AFH is slow again.
Click to expand...
Click to collapse
cool, can i still use treble and wipe tge vendor?
I don't know if I understand it correctly. Pls correct me If I'm wrong.
The benefit of KDZ Writer is that we can update system from KDZ in TWRP.
Thanks will try this
Running it now (H932). Thank you.
seadersn said:
So, here it is: a new (the third for v30...?) thread for an already existing recovery.
Click to expand...
Click to collapse
Actually the 4th, but thank you!
First one was "H930" (which confused US998 users when they got bootloader unlock and root), 2nd one was for "US998" to counteract the H930 confusion -- but really should have been "V30" or "JOAN". @SGCMarkus then made one which not only was Oreo compatible but was "unified". Now this is 4th.
The unification thing is important. I saw over in Moto Quark threads (Droid Turbo, Moto Maxx, Moto Turbo -- all the same phone) where one initial forum was split into two because Droid Turbo at first didn't have bootloader unlock and root, the OTHER Quarks (Moto Maxx, Moto Turbo) jumped ahead in development. Then a year later when Droid Turbo got bootloader unlock and root, thanks to Sunshine, the CM dev at the time generously modified his kernel to include Droid Turbo (which was in a different "dead" forum by then). Thus all the Quarks were unified in development and could all run the same ROMs, same TWRP.
Whereas with one LG flagship phone (which I can't find right now), starting having split development. TWRP and dedicated ROMs for European (which again got bootloader unlock first, thanks to LG's mysterious ways) but then separate older TWRP and a few ROMs for the North America open market. Maybe that's improved now, which is why I can't find it, but I remember thinking "that's not right" and I didn't want that to happen to the V30.
Is the vendor partition mountable ?
Are trebleized ROMs flashable ?
Thanks for providing the new, current version of TWRP. V30 really needed an update for this. No more incorrect times/dates and Magisk giving an error due to false time/date.
Can you give a quick "dummies " tutorial on how to replace the old twrp with this new version using twrp?
Thx.
gimpy1 said:
Can you give a quick "dummies " tutorial on how to replace the old twrp with this new version using twrp?
Thx.
Click to expand...
Click to collapse
I put the new image on sd card. Booted to current TWRP. Flashed new image to recovery partition. Rebooted to system.
Mine took a few reboots to settle in. Couldn't get to it using reboot manager app. Was getting ready to do button dance, but tried reboot app one more time and it booted me to new TWRP. Everything's great now. I don't know if you're supposed to boot back to recovery after flashing the new image. That's what I didn't do.
Sent from my LG-US998 using Tapatalk
Krekos/CZ/ said:
I don't know if I understand it correctly. Pls correct me If I'm wrong.
The benefit of KDZ Writer is that we can update system from KDZ in TWRP.
Click to expand...
Click to collapse
jep, that's the intention of this tool. have a look at the pic in first post there's more to flash via kdzwriter.
FcBayernMinga said:
Is the vendor partition mountable ?
Are trebleized ROMs flashable ?
Click to expand...
Click to collapse
comes this evening, i need a bit of time for relaxing now, but i don't get it because of kids xD
Ballroomblitz said:
... I don't know if you're supposed to boot back to recovery after flashing the new image. That's what I didn't do.
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
jep, this is needed! after flashing of new recovery reboot to recovery. :good:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
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
Click to expand...
Click to collapse
Prerequisites:
Code:
. Unlocked Bootloader
Installation instructions:
Recovery Install Method:
MIATOLL
Opendesktop Cloud - a safe home for all your data
my.opendesktop.org
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Download only the platform-tools according to your device to get adb and fastboot binaries.
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the zip file attached to this thread and copy the recovery.img file into the same folder as your adb and fastboot binaries and type:
Code:
fastboot flash recovery recovery.img
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot of flashable zip you directly go in TWRP mode or the TWRP will be overwritten.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads
TWRP 3.7 recovery
My PitchBlack recovery
Credits:
Me
Huge thanks to @Captain_Throwback, mauronofrio
TWRP team, PitchBlack team
Sources
TWRP: https://github.com/TeamWin/android_bootable_recovery
Kernel Tree: from mauronofrio github
Status: Stable
TWRP: 3.7
NEWS:
31/3/2021:
- Initial Official Release
Added: fix MTP after format data & reboot recovery
Supported exfat, ntfs for storages
Supported Android 10,11,12,13 and Miui
Supported Backup - Restore fully roms (just backup Data and EFS partitions)
...
17/10/2022:
- TWRP v3.7
- Decryption fixed
20/04/2021:
- Fixed exFat for PitchBlack recovery (Thank to @jwchips for the report)
HOW TO BACKUP AND RESTORE:
Backup mode:
With a rom you are using, you boot into Recovery mode:
- Press the Backup button
- Check the partitions you need to Backup (like the image below)
- Press the Select Storage button to choose where to store the rom (with the external sd you need to format NTFS or ..., not FAT, FAT32).
- Now drag the slider to backup rom.
Restore mode:
There are 2 ways for you to restore a rom:
Method 1:
Flash the rom (zip rom), when you see the Setup Wizard screen, you reboot into recovery mode. - Press the Restore button
- Select the stored memory then choose the rom you have backed up
- Just tick the Data line (excl. Storage)
- Drag the slider to restore the rom
Note: you will have to reboot a few times to complete the restored rom.
Method 2 :
You reboot into recovery mode
- Click the Restore button
- Select the stored memory then choose the rom you have backed up
- Select the partitions backed up, except Data (excl. Storage)
- Drag the slider to restore the rom
- Reboot to system. When you see the Setup Wizard screen, you reboot into recovery mode.
- Press the Restore button
- Select the stored memory then choose the rom you have backed up
- Just tick the Data line (excl. Storage)
- Drag the slider to restore the rom data
Note: you will have to reboot a few times to complete the restored rom.
Others method: ? i don't know
Just tried PBRP-miatoll-3.1.0-20210331-1924-UNOFFICIAL.zip and I'm unable to mount my external sd card. Also is there a way to enable flashlight in pbrp? Finally is 'reboot to fastbooot' option fastbootd mode or legacy fastboot?
jwchips said:
Just tried PBRP-miatoll-3.1.0-20210331-1924-UNOFFICIAL.zip and I'm unable to mount my external sd card. Also is there a way to enable flashlight in pbrp? Finally is 'reboot to fastbooot' option fastbootd mode or legacy fastboot?
Click to expand...
Click to collapse
Im using NTFS in my external sd card and think exfat can work. Fastboot works
dungphp said:
Im using NTFS in my external sd card and think exfat can work. Fastboot works
Click to expand...
Click to collapse
Couldn't work out how to take a screenshot in pbrb (only when zip install operation finishes) orangefox shows exFAT
Can I flash it on my Curtana with Orange fox recovery already installed? Can I flash the twrp zip via OFox?
Azamsm said:
Can I flash it on my Curtana with Orange fox recovery already installed? Can I flash the twrp zip via OFox?
Click to expand...
Click to collapse
Yes, flash zip file then reboot to recovery after
dungphp said:
Yes, flash zip file then reboot to recovery after
Click to expand...
Click to collapse
Thanks @dungphp
dungphp said:
Yes, flash zip file then reboot to recovery after
Click to expand...
Click to collapse
Can I also flash magisk v22 zip and root xiaomi.eu based ROM?
Hi, does the first installation of custom recovery on a stock rom affect the data? I already unlock the bootloader and root the rom but I have the stock recovery
is the recovery directly in english?
thank you
edit: answer, does not affect data and installs in English. Thank you
MIUI Flashing works?
viethoang18 said:
MIUI Flashing works?
Click to expand...
Click to collapse
Yes
Still unable to mount (detect?) exfat microsd with latest pitchblack
jwchips said:
Still unable to mount (detect?) exfat microsd with latest pitchblack
Click to expand...
Click to collapse
I will flash, test exfat now !
jwchips said:
Still unable to mount (detect?) exfat microsd with latest pitchblack
Click to expand...
Click to collapse
PB recovery fixed exFat: https://androidfilehost.com/?fid=2188818919693786041
Sorry i did'nt test exFat
you have telegram?
viethoang18 said:
you have telegram?
Click to expand...
Click to collapse
have'nt, inbox to you
dungphp said:
PB recovery fixed exFat: https://androidfilehost.com/?fid=2188818919693786041
Sorry i did'nt test exFat
Click to expand...
Click to collapse
Thanks for the speedy response! Issue resolved =)
@dungphp
TWRP-miatoll-v3.5.2-17042021.zip doesn't always boot in recovery for me, sometimes it just does a normal reboot,
please fix
device is joyeuse
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Poco F3/Mi 11X/Redmi K40
touch and adb work
flashing works
USB OTG works
Decryption is working
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
3. select the new image
4. after that is done, if you were using a custom kernel, reflash it now
5. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_alioth
https://github.com/TeamWin/android_device_xiaomi_sm8250-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomipocof3.html
Unofficial android 12 builds: https://www.pling.com/p/1836619/
mirror: https://store.kde.org/p/1836619/
Thanks for your hard work
All function has usable especially decryption.
Thank you mate!! That's is very important for all the community .What version of magisk i have to install??But you mean flash the zip of magisk??Thanks.
Awesome, mate!
I've been waiting for this, thank you sir for your contribution!
@Nebrassy Nice work - tested on my crDroid working-build and all ok
I only can say thank you a lot!! I'll buy a beer
"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw
reas0n said:
"Failed to mount /data (Invalid argument) :/ Im on HentaiOS btw
Click to expand...
Click to collapse
I believe that rom has customized encryption, so it's not supported
Nebrassy said:
I believe that rom has customized encryption, so it's not supported
Click to expand...
Click to collapse
Damn.. I will wait for any officially supported custom ROM then so I could just get OTAs, I dont want to do another wipe and setup lol. thx anyway
raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
your what?
raystef66 said:
@Nebrassy Nice work - tested on my crDroid working-build and all ok
Click to expand...
Click to collapse
Not shared as yet?
arifqur said:
Not shared as yet?
Click to expand...
Click to collapse
Not yet. Won't take long though when first release will be posted in development.
this works "out of the box" for poco f3 with miui 12.x?
Thank you
Henkl said:
this works "out of the box" for poco f3 with miui 12.x?
Click to expand...
Click to collapse
answering my own question: you have to unlock the phone first with MIUI unlock tool.
AND unlocking involves wiating on part of xiaomi site afer registering ...can be even 7 days..
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp
lejeanlouisF said:
Hello I am not sure I didn't mess around with the job !!
Firstly, I have copied the twrp image on my device but the twrp didn't see it, so I have plugged an otg device with the file on it.
Now twrp is installed but it can't decrypt data (ask for password)
What is wrong pls ?
Secondly, when I have solved that, could I backup the boot.img with Twrp to be then patched with the Magisk installer app ?
Is it the best way to have Magisk on my device ?
Thanks !
Click to expand...
Click to collapse
The password is ur security PIN for unlocking ur phone.
No idea about backuping the boot.img in TWRP (I am not using it )
Nebrassy said:
So it asked for password, did you enter it?
As for magisk, just flash latest magisk apk with twrp
Click to expand...
Click to collapse
I have entered a password but it failed. Is it a free password ?
EDIT : It's ok, sorry. the security PIN, of course !!!
EDIT 2 : And Thank you very much for your work and your help
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Oneplus 9/Pro
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
huge thanks to @osm0sis for help in making and testing this recovery
Trees:
https://github.com/TeamWin/android_device_oneplus_lemonadep
https://github.com/TeamWin/android_device_oneplus_sm8350-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/oneplus/oneplus9pro.html
Great, will test later on EU.
Thanks for your work, much appreciated
avid_droid said:
So I'm assuming flashing kernel and magisk is done through advanced and flash .img also?
Click to expand...
Click to collapse
No, the normal way
Thank you very much.... Finally
When in recovery, I plugged my phone in and my computer doesn't see it. My computer recognizes my phone, but it doesn't show up in my File Explorer. Also, can we flash system image files?
avid_droid said:
Sorry. Meant for magisk. I don't see a flash able zip for that. The kernel is obvious
Click to expand...
Click to collapse
The magisk apk itself is a flashable zip
Red Prez16 said:
When in recovery, I plugged my phone in and my computer doesn't see it. My computer recognizes my phone, but it doesn't show up in my File Explorer.
Click to expand...
Click to collapse
Did you enter your password to decrypt when recovery booted?, if you did, check mount > enable mtp
Nebrassy said:
Did you enter your password to decrypt when recovery booted?, if you did, check mount > enable mtp
Click to expand...
Click to collapse
Ah, okay. Thank you. Also, how do I flash a system image file? Let's say HavocOS for example.
avid_droid said:
Just got the zip from here
Click to expand...
Click to collapse
Do not download from unofficial sites, they could be malicious, only download from
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Red Prez16 said:
Ah, okay. Thank you. Also, how do I flash a system image file? Let's say HavocOS for example.
Click to expand...
Click to collapse
Wait for them to release a zip
Nebrassy said:
Wait for them to release a zip
Click to expand...
Click to collapse
Ah, okay.
Red Prez16 said:
When in recovery, I plugged my phone in and my computer doesn't see it. My computer recognizes my phone, but it doesn't show up in my File Explorer. Also, can we flash system image files?
Click to expand...
Click to collapse
Pretty sure you need to mount storage for that in the mount menu
@Nebrassy I'm getting a multi-coloured white noise image when booting from fastboot (Step 1 in installation)
Currently I have LOS recovery due to installing current version of crDroid, should it be a different process for us? I was also on OOS 11.2.6.6 beforehand as 11.2.7.7 isn't out for EU (LE2123) yet.
i.e. fastboot flash boot TWRP-3.5.1-lemonadep-Nebrassy.img
(Kind of wary of doing so due to the white noise image but that's how LOS recovery was applied for crDroid instructions)
(Also was it you getting N7 BADA to search testers?)
djsubterrain said:
Pretty sure you need to mount storage for that in the mount menu
Click to expand...
Click to collapse
I did and nothing still.
djsubterrain said:
@Nebrassy I'm getting a multi-coloured white noise image when booting from fastboot (Step 1 in installation)
Currently I have LOS recovery due to installing current version of crDroid, should it be a different process for us? I was also on OOS 11.2.6.6 beforehand as 11.2.7.7 isn't out for EU (LE2123) yet.
i.e. fastboot flash boot TWRP-3.5.1-lemonadep-Nebrassy.img
(Kind of wary of doing so due to the white noise image but that's how LOS recovery was applied for crDroid instructions)
(Also was it you getting N7 BADA to search testers?)
Click to expand...
Click to collapse
The noise thing happens only on some devices, only Oneplus devices and I still have no idea what the cause could be, it seems to go away when twrp is flashed
And no, never flash twrp to boot that way, only fastboot boot and let twrp install itself with the options given
And yes, that was me
avid_droid said:
Well ill be damned... Magisk is a flashable apk. everything went through perfectly. Thank you. TWRP now installed with root and everything working so far. Appreciate you.
Click to expand...
Click to collapse
hi, are you on latest oos 11.77?
avid_droid said:
No I'm on BA 11.2.6.6
Click to expand...
Click to collapse
oh I see, gotta try later. thanks
There is no white noise in test build TWRP-3.5.1-lemonadep-1623916477.img
However, cannot pass through it in new build.
Nebrassy said:
The noise thing happens only on some devices, only Oneplus devices and I still have no idea what the cause could be, it seems to go away when twrp is flashed
And no, never flash twrp to boot that way, only fastboot boot and let twrp install itself with the options given
And yes, that was me
Click to expand...
Click to collapse
Would I be able to flash TWRP with LOS in that case?