Huawei P9 EVA-L09 TWRP All Partition Restore - Huawei P9 Questions & Answers

I've done all partitions backup and then Restore by TWRP.
My TWRP version is: 3.1.0-3
Backup was created two months ago.
After Restore I have some problems with system behavior:
I can not run Settings
App "Files" is not visible and I can't run this app.
I've tried restore few times also with positive md5 verification and its still the same.
Can someone tell me what is wrong? What I suposed to do to have my phone working please.?
Edit:
I've solved an issue with File Manager App by installing slightly newer version from ApkMirror site
When i run Settings App it shows up for 0.5sek and then close.
I've tried to:
Clear data of Settings App (acces to this by Root Uninstaller)
Wipe Dalvik Cache partition
Wipe Cache partitnion.
Camera app and every app that need access to camera (mirror, compass) doesn't work also...
Edit. Problem is solved by flashing new software (same version) via dload method
I disovered propable cause in TWRP backup mechanism:
TWRP 3.1.1-0
* bump up TWRP version to 3.1.1
* fix backup of /version
* use device specific and updated prebuilts (+kernel)
* remove the ability to flash images to ext4 mounted partitions
TWRP 3.1.0-3
* kernel updated for proper loop support
* magisk can now be installed and is supported by every rom running b380+ kernel (tested on b383)
* native_package.xml has been changed to device specific version

Related

[Rom] [TCL S960/Alcatel - Idol x+] - Miui 8 Port - Unofficial (Updated 30/Jul/2016)

Hi All,
***MIUI 8 is now operational on our TCL_S960!
I managed to get it running on TCL S960 (IDOL X+),
Here's my work... (I am not a developer but I followed some instructions online and was able to make it at least for me...)
Probably there will be bugs - so let me know
I'll try to fix what I know...
If you want to use my work elsewhere, you must request in advance and make sure that credits goes to the correct people....
Supported Languages:
All languages that are supported by Xiaomi.EU roms.
Credits:
Xiaomi.eu - for the translations and guides.
Latest version Download links:
Android File Host: (WIP)...
30/Jul/2016 -
Older Versions (Miui8)
24/Jul/2016 (fixes to 14/7/2016) - https://www.androidfilehost.com/?fid=24651429356503158
14/Jul/2016 - https://www.androidfilehost.com/?fid=24591000424947416
7/7/2016 - https://www.androidfilehost.com/?fid=24591020540823614
30/6/2016 - https://www.androidfilehost.com/?fid=24591020540823614
Older Versions (MIUI7):
26/5/2016 - https://www.androidfilehost.com/?fid=24566454284190288
19/5/2016 - https://www.androidfilehost.com/?fid=24533103863143479
12/05/2016 - https://www.androidfilehost.com/?fid=24533103863139453
05/05/2016 - https://www.androidfilehost.com/?fid=24533103863137243
28/4/2016 - https://www.androidfilehost.com/?fid=4996500813288309006
14/4/2016 - https://www.androidfilehost.com/?fid=24499762636000772
7/4/2016 - https://www.androidfilehost.com/?fid=24459283995317117
31/3/2016 - https://www.androidfilehost.com/?fid=24459283995310311
17/3/2016 - https://www.androidfilehost.com/?fid=24459283995303903
XdaDevDB:
Installations:
Important:
Prior to any install make sure to backup your existing ROM. (TWRP backup?) if you wish to backup your SMS/Contacts there are a bunch of apps that can do it... (MobilePro is an example)
Backup your IMEI just in case... (Use MobileUncle or similar)
If you chose to install - your warranty is void.
I am not responsible for any damage that may be caused by this ROM.​
Did you make a backup? - Save your backup on a PC...
First time transition to MIUI8 requires re-partition of the phone to increase system size.
you will need a different recovery to finalise the process.
1. Copy the Repartition zip file to phone.
2. Copy the Philz recovery to your phone.
3. Install Philz recovery.
4. Reboot into recovery
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
8. Restore your backup.
9. Boot the phone.
10. Copy the MIUI8 install file to phone.
11. Click on the 3 dots
12. Chose select update file --> select your copied file.
13. Phone will Reboot and install.
If the above version does not work, you will need to use SP-Flash tools to install the EBR1, EBR2 files in the zip.
Then continue from step 6 (Format partitions)
if coming from another rom/ Fresh install
as ususal... - I recomend a total wipe, but it is not a must....
Wipe Cache, Dalvik, Data, System, custpack.
Install Rom from internal memory
reboot.​
Wait patiently - it will take 3-4 minutes on the 1st boot.
To update (existing Miui Rom):
Copy rom to SD Card
Open updater app.
Click on the 3 dots
Chose select update file --> select your copied file.
Reboot​
*** Make sure to disable Automated OTA... as it is based on Redmi Note 3G MTK, and I can't promise to keep this forever...
Recovery:
I used TWRP 2.8.7.0 for TCL S960
Other recoveries:
CWM - Link
TWRP 2.6.3 - Link
If you like my work feel free to buy me beer Donation link
Known Issues:
Default theme - some icons are missing - Use another theme icon set...
When making full wipe - unable to login to MiAccount - Install 6.1.28 version --> login, then update to latest.
TouchAssistant APK exceeds the space of System partition - I removed it, you can install it manually after the rom installs. - Link solved after repartition.
31/3/16 - Additional settings FC - Fixed.
12/05/2016 - Fixed wallpaper carousel FC when unlocking device
Some screenshots:
Miui8:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Miui7:
XDA:DevDB Information
TCL S960/Alcatel (IdolX+), ROM for the Android General
Contributors
hellfreezover, Xiaomi.eu
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: MIUI
Version Information
Status: Beta
Current Beta Version: 26-05-2016
Beta Release Date: 2016-07-15
Created 2016-01-22
Last Updated 2016-07-30
Reserved
Changelog: (Latest Version)
24/7/2016 - still based on 6.7.14
Fixed Settings menus.
Enabled "Button mode"
Enabled additional settings to split the menu bar.
Fixed MIUI version to 8...
System seems to be running faster...
Older versions:
14/7/2016
System
Fix - Fingerprint issues (07-12)
Fix - Fingerprint scanner made the device freeze and reboot (07-12)
Lockscreen, Status Bar, Notification Bar
Optimization - Clickable arrow for Wi-Fi (07-12)
Optimization - A prompt about entering password and activating fingerprint after rebooting the device (07-13)
Fix - Customized carrier name isn't shown in Second space (07-12)
Home screen
Optimization - Landscape mode for Task manager (07-08)
Optimization - Task Manager stability (07-13)
Fix - Issues with wallpaper when switching to Second space (07-13)
Delete - Home screen Music widget (07-13)
Gallery
New - Delete directly from the screenshot preview page (07-12)
Optimization - Adjusted size for the button which creates new albums (07-12)
Optimization - "Show original" option appears only on cloud or optimized items (07-12)
Optimization - Double tap to zoom in, swipe up without entering sharing mode (07-12)
Optimization - When auto-rotate is off in Gallery, it won't influence the rest of the system (07-13)
Fix - Scrolling screenshot issues in Notes and Mail (07-12)
Fix - Couldn't go back to the original photo after making a screenshot or finishing editing/sharing it (07-12)
Fix - Couldn't pick up calls while making Scrolling screenshots (07-13)
Fix - Enter system app while editing a scrolling screenshot in the OOB flow (07-13)
Delete - Removed Edit option for GIF images (07-12)
Weather
Fix - Issues with curves in forecasts (07-13)
Optimization - Set C/F in settings (07-13)
7/7/2016
Highlights
New - Saved and available Wi-Fi networks appear first in the list (07-05)
New - After a permission is restricted, a clickable notification is sent to the user which can restore permissions (07-05)
Lock Screen, Status Bar, Notification Bar
New - Animation of WiFi connection (07-07)
Optimization - separate "Ringtone and Vibration" permission in Notification (07-07)
Fix - Switching notification bar style in landscape view issues (07-07)
Fix - In Second Space, enter Mi Home in lock Screen issue (07-07)
Desktop
Optimization - Restore app uninstallation sound effect (07-07)
Fix - Recent app tray, long press to enter wrong app info page issue (07-07)
Fix - Recent app tray, switching view mode issues (07-07)
Settings
New - Saved and available Wi-Fi networks appear first in the list (07-05)
Clock / Calculator
Optimization - "Shutdown alarm", "Set default alarm sound" moved up In Clock settings. (07-01).
30/6/2016 - Miui 8.
26/5/2016 -
Gallery
New - Deleting synced photos from internal storage without deleting from Mi Cloud (05-25)
Cleaner
Optimization - Accessibility support (05-24)
Fix - FC issues (05-24)
19/05/2016 -
System
Optimization - Background CPU processes caused performance issues (05-16)
Optimization - Delayed response for charger's notifications (05-19)
Fix - Wireless display caused reboots (05-19)
Fix - Read mode appeared more red than it should be (05-19)
Fix - Draining battery while using GPS in some cases (05-19)
Fix - Bluetooth turned on automatically with the device (05-19)
Settings
New - Introducing Shortcut menu. Check out the new MIUI 8 feature early. You can turn it on in Additional settings. (05-17)
TouchAssistant must be installed post rom.
Mi Cloud
New - Added "Back up now" feature for fast backups (05-19)
12/05/2016 -
System
Optimization - System storage UI (05-05)
Optimization - Background processes kept CPU busy and lead to performance issues (05-09)
Fix - Issues with adding fingerprint (05-05)
Fix - Problems with sound when listening to some songs using earphones (05-05)
Fix - Issues with video chats in some cases (05-05)
Fix - Sound disappeared in long phone conversations (05-05)
Fix - Fingerprint unlock didn't respond in some cases (05-05)
Backup
New - Optimizing transferring rate in File Transfer (05-09)
05/05/2016 -
System
Optimization - System storage UI (05-05)
Fix - Issues with adding fingerprint (05-05)
Fix - Problems with sound when listening to some songs using earphones (05-05)
Fix - Issues with video chats in some cases (05-05)
Fix - Sound disappeared in long phone conversations (05-05)
Fix - Fingerprint unlock didn't respond in some cases (05-05)
Security
New - Added on/off switch for App lock (05-03)
New - Customized settings for App lock (05-03)
28/4/2016 -
System
Optimisation - Improved speed and performance for devices which have been used for a long time (04-27)
Weather
New - New white design (04-27)
Cleaner
New - New design for Cleaner (04-27)
Gallery
New - Progress list for syncing with Mi Cloud (04-27)
Optimization - Added a prompt notifying about Mi Cloud trash bin when deleting photos for the first time (04-27)
Optimization - Improved sharpness for big photos (04-27)
Security
New - Fingerprint support for App lock in Redmi 3 Pro (04-27)
14/4/2016 -
System
Optimization - Improved algorithms for Silent and DND modes to be used at the same time. (04-13)
Fix - Storage leaks lead to performance problems (04-08)
Fix - Security Center FC in Hebrew Language
7/4/2016 -
Lockscreen, Status Bar, Notification Bar
Optimization - Improved order of switches in notification shade (04-06)
Fix - Music lock screen appeared when a game was running in the background (04-06)
Settings
Optimization - Improved algorithms for international roaming (04-06)
Mi Account
New - Added more items to personal info (04-06)
Cleaner
Optimization - Press and hold to add items to exceptions (04-06)
Optimization - Fixed problems with performance after clean-ups (04-06)
Mi Cloud
Fix - Couldn't find device or sign in to Mi Account due to wrong system time (04-06)
Fix - Fixed issues with incorrect time in backup lists (04-06)
Bug fixes by Xiaomi.
Fixed Additional settings FC.
31/3/2016 general bug fixes by Xiaomi.
24/3/2016
System
Optimization - Apps open faster, system animations work smoother (03-17)
Optimization - Increased image processing speed for image decryption database (03-22)
Fix - Problems with performance after switching from mobile data to Wi-Fi (03-18)
Backup
In some cases Mi Mover stopped working after the connection was established (03-18)
Clock / Calculator
New - Option for deleting an alarm automatically after it was used if it had been set to go off only once (03-23)
thank you
thank you for this awesome Rom. but the sound setting under audio force closes im on viper4android
Did you try sound settings without viper?
For me it works... but I did had to do a clean install...
Sent from my ASUS_Z00XS using XDA Free mobile app
Hi i just tried your rom bt i am stuck at mi login.. It says checking find device status and stays there only.... What to do now...?
santhosh5639 said:
Hi i just tried your rom bt i am stuck at mi login.. It says checking find device status and stays there only.... What to do now...?
Click to expand...
Click to collapse
Try using an older version like 6.1.28, then log in to miui, then update without full wipe.
I have reported this to miui, it is under discussion...
Sent from my ASUS_Z00XS using XDA Free mobile app
Updated OP with the link to 6.1.28 version
Sent from my ASUS_Z00XS using XDA Free mobile app
Updated OP with MIUI 8 for TCL.
Sent from my ASUS_Z00XS using XDA Free mobile app
Bricking my phone
Dear Hellfreezover,
I tried to install your ROM, but I bricked my phone.
(I installed ROM before several times, I never made mistake, but now I did it.)
When I used SP flashtool I selected "Firmware upgrade" option instead of "Download only" option (I never did it before) and I started to install TWRP recovery but I got error message.
Now I can not use my phone, but I know that I can be repairable just I need important files....
...these all files or just some of them:
- PRELOADER
-MBC
-EBR1
-UBOOT
-BOOTIMG
-RECOVERY
-SEC-RO
-LOGO
-EBR2
-CUSTPACK
-MOBILE_INFO
-ANDROID
-CACHE
-USRDATA
Now I get this error message when I try to update the recovery.
Could u send me these files? Or could you link me URL where I can find these files?
Sorry for disturbing, I shame on me, I did ROM install before without mistake, but now I screwed up...
Regards,
Peter (Hungary)
I am not at home now,
I have the files...
You can get searching TCL multi language rom 70 languages and download it through SP flash tools, then, repartition and finally the rest....
Sent from my ASUS_Z00XS using XDA Free mobile app
Olympos.81 said:
Dear Hellfreezover,
I tried to install your ROM, but I bricked my phone.
(I installed ROM before several times, I never made mistake, but now I did it.)
When I used SP flashtool I selected "Firmware upgrade" option instead of "Download only" option (I never did it before) and I started to install TWRP recovery but I got error message.
Now I can not use my phone, but I know that I can be repairable just I need important files....
...these all files or just some of them:
- PRELOADER
-MBC
-EBR1
-UBOOT
-BOOTIMG
-RECOVERY
-SEC-RO
-LOGO
-EBR2
-CUSTPACK
-MOBILE_INFO
-ANDROID
-CACHE
-USRDATA
Now I get this error message when I try to update the recovery.
Could u send me these files? Or could you link me URL where I can find these files?
Sorry for disturbing, I shame on me, I did ROM install before without mistake, but now I screwed up...
Regards,
Peter (Hungary)
Click to expand...
Click to collapse
Check your PM - I sent you a link with all files needed...
Updating problem
hellfreezover said:
Check your PM - I sent you a link with all files needed...
Click to expand...
Click to collapse
Thank you very much, I could unbrick my mobile! :good: :fingers-crossed: :highfive:
I tried to upgrade my ROM according to your instructions, but I could not do it.
What I did:
1. Unbrick my mobile with your files.
2. I copied your MIUI8 ROM, Repartition and Philz zip files to my mobile.
3. In SP Flash I downloaded Philz.zip what contains recovery.
4. I rebooted my mobile in recovery mode.
5. I installed the Repartition zip. (...but I think it was unnecessary, because I did it when I unbricked my mobile.)
6. I tried to reboot my mobile into reocvery mode, but it was not available (after repartition.)
7. I had to download your TWRP 2.8.7.0 recovery to my mobile via SP-Flash tool.
8. I tried to reboot, but same situation: this recovery also was not available.
9. I had to download other 2.6.3 or 2.7.0 TWRP recovery to my mobile.
10. I could reach recovery from that point.
11. I installed your MIUI 8 rom, and it was successful according to message.
12. In spite fo this the ROM can not start: "Idol X+" is appearing and go away and black screen is flashing without logo or sound.
What do I do in wrong way?
Otherway, before I unbricked my mobile and after also I tried to upgrade my ROM to your MIUI 8 version in different way.
Then I had different problem: when I did the uploading of your ROM into my exist differnet rom (like offical ROM, LeWa ROM or modded MIUI 5 rom) in recovery mode the installation was finally failed, unsuccessful: "/data" directory can not reachable/readable/writeable or somehting else.
(I have screenshot, I will share.)
Regards,
Peter
Olympos.81 said:
Thank you very much, I could unbrick my mobile! :good: :fingers-crossed: :highfive:
I tried to upgrade my ROM according to your instructions, but I could not do it.
What I did:
1. Unbrick my mobile with your files.
2. I copied your MIUI8 ROM, Repartition and Philz zip files to my mobile.
3. In SP Flash I downloaded Philz.zip what contains recovery.
4. I rebooted my mobile in recovery mode.
5. I installed the Repartition zip. (...but I think it was unnecessary, because I did it when I unbricked my mobile.)
6. I tried to reboot my mobile into reocvery mode, but it was not available (after repartition.)
7. I had to download your TWRP 2.8.7.0 recovery to my mobile via SP-Flash tool.
8. I tried to reboot, but same situation: this recovery also was not available.
9. I had to download other 2.6.3 or 2.7.0 TWRP recovery to my mobile.
10. I could reach recovery from that point.
11. I installed your MIUI 8 rom, and it was successful according to message.
12. In spite fo this the ROM can not start: "Idol X+" is appearing and go away and black screen is flashing without logo or sound.
What do I do in wrong way?
Otherway, before I unbricked my mobile and after also I tried to upgrade my ROM to your MIUI 8 version in different way.
Then I had different problem: when I did the uploading of your ROM into my exist differnet rom (like offical ROM, LeWa ROM or modded MIUI 5 rom) in recovery mode the installation was finally failed, unsuccessful: "/data" directory can not reachable/readable/writeable or somehting else.
(I have screenshot, I will share.)
Regards,
Peter
Click to expand...
Click to collapse
Hi,
I think what you missed is the format of system, data, cache - after the installation of re partition, in Philz recovery.
also - you need to verify that your SD-Data is mounted correctly (sometimes in Philz it adds a 0, and then you will not find files there...
You need to change the mount location before you reboot recovery.
Sorry I have no pictures for this, but it is in the menu...
if the above does not work
Try extracting EBR1, EBR2 from repartition file, install them with Philz recovery through SP-Flash tool.
reboot into recovery --> format data, system, cache - check again where SD is mounted...
Reboot recovery
Install rom - if works great if not:
Install TWRP 2.8.7
Place new ROM and install
let me know if this works for you.
The 1st install will take a few minutes until you will see something on the phone...
hellfreezover said:
Hi,
I think what you missed is the format of system, data, cache - after the installation of re partition, in Philz recovery.
also - you need to verify that your SD-Data is mounted correctly (sometimes in Philz it adds a 0, and then you will not find files there...
You need to change the mount location before you reboot recovery.
Sorry I have no pictures for this, but it is in the menu...
if the above does not work
Try extracting EBR1, EBR2 from repartition file, install them with Philz recovery through SP-Flash tool.
reboot into recovery --> format data, system, cache - check again where SD is mounted...
Reboot recovery
Install rom - if works great if not:
Install TWRP 2.8.7
Place new ROM and install
let me know if this works for you.
The 1st install will take a few minutes until you will see something on the phone...
Click to expand...
Click to collapse
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
---------- Post added at 05:49 PM ---------- Previous post was at 05:02 PM ----------
Olympos.81 said:
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
Click to expand...
Click to collapse
My problem is now:
/E: Unable to mount '/system'
/E: Unable to mount '/protect_s'
/E: Unable to mount '/protect_f'
Olympos.81 said:
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
---------- Post added at 05:49 PM ---------- Previous post was at 05:02 PM ----------
My problem is now:
/E: Unable to mount '/system'
/E: Unable to mount '/protect_s'
/E: Unable to mount '/protect_f'
Click to expand...
Click to collapse
you can change the mount location in Philz recovery...
6.a. - check to see where the SDCARD data directory is mounted(\data or \data\0), if it is the \data\0 - change it back to \data in the philz recovery, otherwise - upgrades will not work in TWRP.
I followed your instruction, please see my notes and check my pictures:
1. Copy the Repartition zip file to phone.
OK!
2. Copy the Philz recovery to your phone.
OK!
Please see it, I copied everything to my phone from Window 10, so these files copied into /data directory:
http://kepfeltoltes.hu/160717/factory_directory_www.kepfeltoltes.hu_.jpg
3. Install Philz recovery.
I did it from factory recovery:
http://kepfeltoltes.hu/160717/IMG_1596_www.kepfeltoltes.hu_.jpg
(You can not see the "Philz*.zip" file because of bad quality of picture, but belive me, it is.
4. Reboot into recovery
OK!
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
I did it:
http://kepfeltoltes.hu/160717/IMG_1597_www.kepfeltoltes.hu_.jpg
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
I did not need the format, because your Repartition.zip was installed successfully, and format was done by Repartition.zip as you requested:
Begin:
http://kepfeltoltes.hu/160717/IMG_1598_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1599_www.kepfeltoltes.hu_.jpg
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
Because of your Repartition procedure all files were deleted from /data directory so I had to upload TWRP 2.8.7.0 recovery from SP-Flash tool to mobile:
http://kepfeltoltes.hu/160717/Recovery_www.kepfeltoltes.hu_.jpg
8. Restore your backup.
(I do not know what is it...maybe I make a mistake here. I skiped this step.)
9. Boot the phone.
OK.
10. Copy the MIUI8 install file to phone.
Negative. There is no operation system, because Repartition.zip formatted /data and /system directory.
Furthermore, Internal storage is 0 from the Repartition.zip is completed.
http://kepfeltoltes.hu/160717/IMG_1603_www.kepfeltoltes.hu_.jpg
11. Click on the 3 dots
Negative.
12. Chose select update file --> select your copied file.
I had to use OTG-USB cable and chose the MIUI 8 rom in TWRP 2.8.7.0
But from now due to unavailable /data, /cache / etc - internalt storage is 0 - the installation however started, but failed.
Begin:
http://kepfeltoltes.hu/160717/IMG_1604_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1605_www.kepfeltoltes.hu_.jpg
13. Phone will Reboot and install.
Negative.
Where do I make mistake?
Olympos.81 said:
I followed your instruction, please see my notes and check my pictures:
1. Copy the Repartition zip file to phone.
OK!
2. Copy the Philz recovery to your phone.
OK!
Please see it, I copied everything to my phone from Window 10, so these files copied into /data directory:
http://kepfeltoltes.hu/160717/factory_directory_www.kepfeltoltes.hu_.jpg
3. Install Philz recovery.
I did it from factory recovery:
http://kepfeltoltes.hu/160717/IMG_1596_www.kepfeltoltes.hu_.jpg
(You can not see the "Philz*.zip" file because of bad quality of picture, but belive me, it is.
4. Reboot into recovery
OK!
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
I did it:
http://kepfeltoltes.hu/160717/IMG_1597_www.kepfeltoltes.hu_.jpg
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
I did not need the format, because your Repartition.zip was installed successfully, and format was done by Repartition.zip as you requested:
Begin:
http://kepfeltoltes.hu/160717/IMG_1598_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1599_www.kepfeltoltes.hu_.jpg
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
Because of your Repartition procedure all files were deleted from /data directory so I had to upload TWRP 2.8.7.0 recovery from SP-Flash tool to mobile:
http://kepfeltoltes.hu/160717/Recovery_www.kepfeltoltes.hu_.jpg
8. Restore your backup.
(I do not know what is it...maybe I make a mistake here. I skiped this step.)
9. Boot the phone.
OK.
10. Copy the MIUI8 install file to phone.
Negative. There is no operation system, because Repartition.zip formatted /data and /system directory.
Furthermore, Internal storage is 0 from the Repartition.zip is completed.
http://kepfeltoltes.hu/160717/IMG_1603_www.kepfeltoltes.hu_.jpg
11. Click on the 3 dots
Negative.
12. Chose select update file --> select your copied file.
I had to use OTG-USB cable and chose the MIUI 8 rom in TWRP 2.8.7.0
But from now due to unavailable /data, /cache / etc - internalt storage is 0 - the installation however started, but failed.
Begin:
http://kepfeltoltes.hu/160717/IMG_1604_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1605_www.kepfeltoltes.hu_.jpg
13. Phone will Reboot and install.
Negative.
Where do I make mistake?
Click to expand...
Click to collapse
First you missed your previous MIUI backup...
but that is not the issue...
I would recommend formatting the /system, /data, /cache partitions - even though that it shoes success...
Then reboot recovery (to PHILZ)
Make sure your SDCARD mount is without the "0"...
Try to flash ROM using ADB sideload, in PHILZ touch...
if it doesn't work, try installing with TWRP 2.6.3 recovery.
I shared what I did on my phone and it worked...
If all the above fails - try installing EBR1, EBR2 from SP-Flash tool, then Recovery (Philz), Format cache, system, data, then install rom through PHILZ or TWRP...
Somebody could install this rom as Hellfreezover described?
---------- Post added at 09:23 PM ---------- Previous post was at 09:05 PM ----------
hellfreezover said:
First you missed your previous MIUI backup...
but that is not the issue...
I would recommend formatting the /system, /data, /cache partitions - even though that it shoes success...
Then reboot recovery (to PHILZ)
Make sure your SDCARD mount is without the "0"...
Try to flash ROM using ADB sideload, in PHILZ touch...
if it doesn't work, try installing with TWRP 2.6.3 recovery.
I shared what I did on my phone and it worked...
If all the above fails - try installing EBR1, EBR2 from SP-Flash tool, then Recovery (Philz), Format cache, system, data, then install rom through PHILZ or TWRP...
Click to expand...
Click to collapse
Dear Hellfreezover!
I am sure, that you are advanced or professional developer and you have more experience about mobiles and ROMS, but now, I think what you have written in instructions is different as you have done it in real life.
...or someting is wrong with ROMs.
So...
I tried to follow your instruction several times and when I have reached that point that there were no error message at the beginning of installation of ROM, finally, it was also unsucessfull:
- begining: http://kepfeltoltes.hu/160717/IMG_1592_www.kepfeltoltes.hu_.jpg
- ending: http://kepfeltoltes.hu/160717/IMG_1593_www.kepfeltoltes.hu_.jpg
(See, there is no error message as before like "unmount /data" or somthing else...)
I am hardly a professional....
I used philz, and my files the way I described...
There may be some issues, I had miui Rom installed before...
And there is another guy that did the repartition process... using SP flash tools...
You can try maybe replacing the EBR1, EBR2 in the original Rom and choose firmware update....
Then install the twrp recovery and the Rom...
hellfreezover said:
I am hardly a professional....
I used philz, and my files the way I described...
There may be some issues, I had miui Rom installed before...
And there is another guy that did the repartition process... using SP flash tools...
You can try maybe replacing the EBR1, EBR2 in the original Rom and choose firmware update....
Then install the twrp recovery and the Rom...
Click to expand...
Click to collapse
Now I tried again and again, I followed again your every intsructions and I tried the following ROMs with TWRP 2.6.3.0:
- xiaomi.eu_multi_TCL_S960_6.7.14_v8-4.4 (latest) - Failed
- xiaomi.eu_multi_TCL_S960_6.6.30_v8-4.4 (previous) - Failed
- xiaomi.eu_multi_TCL_S960_6.3.10_v7-4.4 - Success!
Now, the MIUI 7 is running.
I am trying to upgrade to latest MIUI 7 and after to MIUI 8....
...but I am afraid: this will be again failed.

Camera is black throughout OS - HELP

Hi guys,
So - full story;
* Wanted to try the RR ROM posted (didn't really notice the MM warnings)
* Flashed, failed, full wipe/format, restored full nandroid backup (all options/partitions checked)
* After restore camera was black, and phone got very hot
* Wipe/Fact. Reset in TWRP and set phone up anew
* Back in OS, everything is normal except camera is still black (also snap, messenger, OpenCamera APK)
Tried:
* Install P9 Plus Camera APK from this thread
* Wipe/Reinstall
Info:
On VIE-L09C432B360 (installed originally via FF, but I have the full .zip (I think)
This wasn't an issue before the TWRP Nandroid Restore, so I can't see how it's a problem now. Please help?
UPDATE;
I've pulled the hwcamera2.apk from the B360 nougat build I have installed, but it refuses to install, saying the package is corrupt. Google tells me this is because of a signing issue. However, I tried to install via ADB instead, which gave me this line:
Code:
D:\Android>adb install D:\Android\HwCamera2.apk
Failed to install D:\Android\HwCamera2.apk: Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES: Failed to collect certificates from /data/app/vmdl1241921743.tmp/base.apk: /data/app/vmdl1241921743.tmp/base.apk: File res/drawable-xxxhdpi-v4/bg_camera_shutterbutton_audionote.png in manifest does not exist]
Is there ANYONE that has ANY ideas out there? Please help.. I can't even do a full on restore to stock, I don't know how

[RECOVERY][OFFICIAL][sagit] TWRP 3.2.2-0 for Xiaomi Mi 6

Team Win Recovery Project
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
FEATURES:
FBE Decryption support
MTP support
ADB root
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
CONTRIBUTIONS:
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
TWRP for Mi 6, Tool/Utility for the Xiaomi Mi 6
Contributors
TheStrix
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2017-06-10
Last Updated 2018-07-07
FAQ
FAQ:
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
MY RECOVERY KEEP GETTING REPLACED WITH STOCK RECOVERY... WHAT KIND OF MAGIC IS THIS?
The file: /system/bin/install-recovery.sh present in stock system is responsible for that.
You can simply stop this from happening by deleting it or renaming it to install-recovery.sh.bak using any root explorer or via TWRP (Advanced -> File Manager).
Reserved
Nice
Praying for good developers working on Mi6
Thx for TWRP
thanks
Thanks a lot for your work.
Any comparison to ValoXis / cofface version?
Thanks
Thanks a lot for your work!
Can I disable dm-verify with this revovery when using official MIUI rom?
Can not be backed up
.nice thank you !
Maybe lineage is next ? ?
Any reason why it asks me for a password?
Thanks!
Yeah, Parth its here
Now it's time to xiaomi to release kernel sources
Successfully re-flashed from ValoXis version via official TWRP app.
Thanks Strix!
Tried to restore from backup, This is the thing what I backed up :
1. Backup1 : boot, recovery, EFS
2. Backup2 : system, system image, data, cache
I tried to restore from backup2 first from failing the installation of China dev ROM. Wipe system, data, cache, dalvik, and do the backup.
It's booted okay (it uses the custom boot animation I picked), but at the end / near the end of the boot animation, there's low battery sound played, then the device is switched off.
Tried again to wipe everything, restore backup2, then backup1, I got the same "low battery" sound notification.
In the end I had to reflash Xiaomi.eu ROM and start fresh.
So what actually happened there?
Hello, after installing twrp this one does not stay, do you have a solution? thank you
Thanks a lot for your work!
I hope Sagit can get recovery by ZCX
Sent from my Xiaomi Mi 6 using XDA Labs
TWRP 3.1.1-1 release:
Fixes the nandroid backup/restore issue
(Notice: backups made using old recovery builds still won't restore fine)
Other updates
Also for some of you've have been wondering,
MY RECOVERY KEEP GETTING REPLACED WITH STOCK RECOVERY... WHAT KIND OF MAGIC IS THIS?
The file: /system/bin/install-recovery.sh present in stock system is responsible for that.
You can simply stop this from happening by deleting it or renaming it to install-recovery.sh.bak using any root explorer or via TWRP (Advanced -> File Manager).

[CLOSED]TWRP 3.3.1-1 for Pixel 3A XL [OFFICIAL]

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.
Code:
[I]#include <std_disclaimer.h>
/*
* Your warranty is not void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/[/I]
Note: Please be aware that you cannot install this without a kernel with LZMA compression support, I believe most ROMs have included my commit for this so you should be good for all custom ROMs and kernels. If not please file a request to the maintainer.
In addition, please be aware that TWRP is currently not compatible with Android 10. If you would like to use TWRP you will need to go back to Android 9. If you would like more information you can read at the link here.
Not a huge problem, stock users can just temporarily boot TWRP if you have access to a PC.
Not compatible with Android Q.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to transfer the zip onto your device.
Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Changelog:
[BETA]
3.3.1-0: Initial release for Pixel 3A XL devices
3.3.1-1: Fixed having to manually change slots before rebooting.
3.3.1-2: Updated to July blobs!
3.3.1-3: Can now install TWRP to boot image. ADB, MTP, LOGD, Repack Tools and Logcat have all been removed to save the necessary space for this to work. You can grab stuff while in the OS, then flash it in TWRP (Keep in mind I have only tested this on stock as of now, feel free to test it on whatever ROM you use. It should work, but let me know if it doesn't).
3.3.1-4: Changed back to LZMA compression, also added back all the features besides ADB/Logcat. As long as your kernel supports LZMA you will be able to take advantage of installing it permanently without having to worry about space restrictions.
3.3.1-5:
Add persist entry to fstab
* To allow TWRP to store a backup settings file on /persist
and also to be used as QCOM time fix source during early boot.
Revert "Don't include logcat."
Revert "Don't include repack tools."
3.3.1-6:
Revert "Revert "Don't include repack tools.""
Add haptics firmware.
* This obviously on it's own isn't enough to get haptics working for the 3A in TWRP, but its a start.
Don't include a precompiled update_engine_sideload
* This should fix the issue of flashing officials for StatiXOS
[STABLE]
3.3.1-0: Initial official release!
Download:
https://twrp.me/google/googlepixel3axl.html
XDA:DevDB Information
TWRP, Tool/Utility for the Google Pixel 3a XL
Contributors
ZVNexus, janjan
Source Code: https://github.com/TeamWin/android_device_google_bonito
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-07-17
Current Beta Version: 3.3.1-6
Beta Release Date: 2019-06-27
Created 2019-06-27
Last Updated 2019-11-15
Reserved
Awesome! Thank you so much!
So as of this moment, there is only the ability to boot to twrp via fastboot?
DriveEuro said:
Awesome! Thank you so much!
So as of this moment, there is only the ability to boot to twrp via fastboot?
Click to expand...
Click to collapse
Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.
So does anyone know if TWRP + Magisk work on Android Q for root?
ZVNexus said:
Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.
Click to expand...
Click to collapse
I don't mind, I haven't flashed TWRP to a device since Treble came out, but it's easy enough to boot an image, so at least for my usage case, this is all I need
otg mounting problem
ZVNexus said:
Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.
Click to expand...
Click to collapse
no you shouldn't have waited!! thanks a lot specially from all of us checking if twrp came out every day!
hey maybe you can give me a tip since i have a problem mounting otg:
when i boot twrp image if i go to backup/select storage i find a storage/usb partition (0MB)
when i connect otg (and go to mount) it becomes storage/usbotg 1 (12000MB)
but the problem is that if i click it doesn’t remain selected, and the log reports “Unable to find partition for the path ‘/storage’ ”
if i go to mount or backup/select storage and click usbotg 1 storage it doesn’t remain selected and the log reports “E: unable to locate partition for ‘/storage/usbotg-1’ ”
(i’ve tried also with different keys but i don't think it's the point anyway the 1st was an 256GB usb/SD and the 2nd a 16GB usbkey but logs reports same error)
any tip?
I'm on Q DP4. Anyone having luck flashing Magisk (canary)? In B slot it fails to mount system and vendor. I change to A slot. It completes. I reboot on A slot, I get stuck at Google starting logo and the phone never boots. If I attempt to boot B slot afterwards, it boots up fine, but I obviously don't have Magisk installed, verified with the Magisk APP.
Anyone have a clue?
Just to provide feedback.
Fastboot booted the image, it prompted for my pin, mounted system, and was able to backup properly, moved backup to computer.
Wiped the phone, reboot and went through setup, everything was working.
Back to twrp, adb pushed the backup to the phone, restored the backup and everything was functioning.
Also tested and was able to sideload flash Magisk.
So everything seems to be working as intended.
Thank you so much for your hard work!
My TWRP is NOT prompting for pin/pattern. That has to be part of this...
Wiped data via google recovery. The phone booted to Pie (i had previously did the OTA from Pie to Q beta 4). So now I'm back on Pie somehow (without reflashing). I booted to TWRP, installed Magisk successfully.
So overall, I'm not sure if this was related to Q beta 4 OTA occupying B slot while Pie still was on A slot.
Thanks to all for their work with TWRP!
Antonyo13 said:
Just to provide feedback.
Fastboot booted the image, it prompted for my pin, mounted system, and was able to backup properly, moved backup to computer.
Wiped the phone, reboot and went through setup, everything was working.
Back to twrp, adb pushed the backup to the phone, restored the backup and everything was functioning.
Also tested and was able to sideload flash Magisk.
So everything seems to be working as intended.
Thank you so much for your hard work!
Click to expand...
Click to collapse
On previous devices I have run into TWRP restore issues if I had a security PIN set on the device when I backed up. During your test did you have a PIN setup on the phone?
artiemon said:
On previous devices I have run into TWRP restore issues if I had a security PIN set on the device when I backed up. During your test did you have a PIN setup on the phone?
Click to expand...
Click to collapse
I had a pattern, not sure if it makes a difference between pattern and pin.
I will say the only thing weird i noticed was when i wiped the phone (the default wipe from twrp, not a full format of data from twrp), when i booted I was prompted for my pattern on first unlock before the device setup. Even though it was wiped.
But restoring was perfectly fine.
Antonyo13 said:
I will say the only thing weird i noticed was when i wiped the phone (the default wipe from twrp, not a full format of data from twrp), when i booted I was prompted for my pattern on first unlock before the device setup. Even though it was wiped.
But restoring was perfectly fine.
Click to expand...
Click to collapse
That is normal on pixels. If you factory reset in TWRP your password still stays
spaceman860 said:
That is normal on pixels. If you factory reset in TWRP your password still stays
Click to expand...
Click to collapse
Thank then everything is working great. No issues at all with TWRP
So just confirming - I am , I assume encrypted , as I have a PIN and a pattern with DU ROM. Can i safely backup the existing ROM and flash another and then be able to restore if need be using this version of TWRP?
jcrompton said:
So just confirming - I am , I assume encrypted , as I have a PIN and a pattern with DU ROM. Can i safely backup the existing ROM and flash another and then be able to restore if need be using this version of TWRP?
Click to expand...
Click to collapse
Yes. This is how it has worked in the past. Don't see why it wouldn't work like this currently. If you flash a different vendor image or system image, you'll want to revert back before you restore your old ROM backup.
DriveEuro said:
Yes. This is how it has worked in the past. Don't see why it wouldn't work like this currently. If you flash a different vendor image or system image, you'll want to revert back before you restore your old ROM backup.
Click to expand...
Click to collapse
Revert back to what? Sorry I don't understand?
Flash back the original vendor and system images.
GQJ said:
Revert back to what? Sorry I don't understand?
Click to expand...
Click to collapse
He was answering my question about hypothetical referring back to a prior rom from a backup
neshipda said:
no you shouldn't have waited!! thanks a lot specially from all of us checking if twrp came out every day!
hey maybe you can give me a tip since i have a problem mounting otg:
when i boot twrp image if i go to backup/select storage i find a storage/usb partition (0MB)
when i connect otg (and go to mount) it becomes storage/usbotg 1 (12000MB)
but the problem is that if i click it doesn’t remain selected, and the log reports “Unable to find partition for the path ‘/storage’ ”
if i go to mount or backup/select storage and click usbotg 1 storage it doesn’t remain selected and the log reports “E: unable to locate partition for ‘/storage/usbotg-1’ ”
(i’ve tried also with different keys but i don't think it's the point anyway the 1st was an 256GB usb/SD and the 2nd a 16GB usbkey but logs reports same error)
any tip?
Click to expand...
Click to collapse
I didn't test OTG before I uploaded, didn't have an OTG cable, but now that I know its a problem I'll look into it.

Installing, Updating, Backup and Restore Guide for OP6/6T

This is a bit late but why not. THIS IS A COMPILATION OF ALL THE OS METHODS YOU NEED FOR THE OP6/6T.
ENJOY my guide
DISCLAIMER:
*I am not responsible for bricked devices, damage to your device*
Sorry for a long list of methods, some work for others and some don't. But I recommend to pick a method and stick to it. Maybe read the part at the top as some have notes about mine or someone else's experience/recommendation. Don't skip steps and follow each step.
If stuck, just ask and I or anyone else will try and help
I am here to post methods for anyone who is interested/need help. I have tested these myself and helped others who may be struggling
Download
The guide has loads of files/ zips/ tools to use/flash/install. But no worries as everything can be downloaded and there are links AT THE BOTTOM OF THIS THREAD (NOT COMMENTS) to where to download:
SDK Platform Tools (Fastboot tools) from Developer Android
TWRP from mauronofrio
Magisk from topjohnwu
Gapps (Google Apps) from NikGapps. I recommend omni for ROMs that don't include Gapps.
Fastboot ROM for OP6 + OP6T from mauronofrio
MSMDownload tools for OP6 + OP6T from Some_Random_Username
IMPORTANT NOTES!
YOU REQUIRE Platform Tools (Fastboot Tools) IN ORDER TO USE THE METHODS IN THIS GUIDE AS TWRP NEEDS TO BE INSTALLED!
YOU NEED TO HAVE A UNLOCKED BOOTLOADER AS WELL!
For GAPPS, u can use the same or a updated version of the package. But has to be the same type u used to install it like (stock, full, Omni, basic, etc). ONLY FLASH/INSTALL IF the RESTORE SCRIPT DIDN'T SHOW UP during a DIRTY FLASH/UPDATE AND ONLY FLASH AFTER REBOOTING TO RECOVERY AFTER FLASHING/INSTALLING A OS/BUILD ZIP FILE!
How to get Platform Tools
These tools are used to install TWRP, to unlock the bootloader of your device and is needed to use the METHODS in this guide.
Download the platform tools.zip of your software platform (Mac, Windows, Linux)
Extract the platform-tools.zip
To use it go into your platform-tools folder
Press shift + right-click and choose command prompt or PowerShell
Connect your device when it's in fastboot mode and done
How to install TWRP
Sadly this Guide is for Windows, but other platforms like Mac or Linux can be found online.
YOU CAN USE THIS METHOD TO INSTALL A NEWER VERSION OF TWRP TOO
You need to have downloaded Platform Tools which the link is attached below.
Transfer the TWRP.img file into the platform-tools folder
Now transfer TWRP.zip into your device's internal storage. (connect -> allow file transfer -> drag and drop files)
If you want root download and transfer magisk.apk and the link is supplied below. Also, RENAME from .apk to .zip
Now we must boot into fastboot mode. (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Now connect your device to a Windows device
Press shift + right-click. Choose command prompt or PowerShell
Enter "fastboot devices" and your device should be displayed if it's connected
Type "fastboot boot twrp" file name (do twrp + press tab) and press enter
Then you should be booted into TWRP
Enter the password and swipe to allow modifications
Press install and find your TWRP.zip file
Swipe to confirm Flash
If you want root do this
Press the back arrow and find your magisk.zip
Swipe to confirm Flash
Reboot to the system and done
Otherwise, just reboot to system. Up to u
Installing a Custom ROM
Install Custom ROM on OP6T from OOS
Make sure u have BACKED UP your device and have the latest OOS installed in both slots. If u do, go to Method 3.
If u have finalize.zip, go to Method 2.
Method 1
If u don't have OOS installed in both slots or finalize.zip, use this method.
Transfer OOS.zip file, TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot TWRP
Flash OOS + TWRP
reboot recovery
Flash OOS + TWRP
Reboot recovery
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
If u have finalize.zip, do this method. Using finalize is way quicker as there's less flashing and rebooting.
Transfer OOS.zip file, finalize.zip, TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot to TWRP
Flash OOS + finalize
Boot to Bootloader
Boot to TWRP
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 3
Once you have installed OOS in both slots do this part.
Transfer TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot to TWRP
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Installing Custom Rom not from OOS
You can use finalize method or just flash OOS + TWRP way. The finalize way is there for some who like less flashing and rebooting.
Using the methods in Install Custom ROM on OP6T from OOS
Using the old way, use Method 1
Using finalize.zip, use Method 2
Remember to factory reset (wipe, but no need to wipe internal storage)
Backing Up OOS and Custom ROM
Make sure u have installed the latest TWRP version from mauronofrio
You should use TitaniumBackup or Migrate to back up your apps and contacts.
Also, have a copy of your Internal Storage folders if u have important files.
TWRP Backup backs up your OS like Apps, settings and set up, but not internal storage.
NEVER BACKUP SYSTEM AND VENDOR! ONLY SYSTEM.IMG or VENDOR.IMG IF YOU HAVE TO!
Restoring it makes going back way easier like you have never left
Or you can go manually and try and restore everything, but why do that when you got TWRP?
I do both ways of backing up
Backing up OOS
Boot TWRP recovery
Choose Backup
Choose boot, data. YOU DO NOT NEED TO BACKUP System.img and Vendor.img!
Swipe to backup
Once done, either boot to system or mount
Transfer the whole TWRP folder onto a storage device
Done
Backing up a Custom ROM
Boot TWRP recovery
Choose Backup
Choose boot, data, system.img, vendor.img
Swipe to backup
Once done, either boot to system or mount
Transfer the whole TWRP folder onto a storage device
Done
Restoring OOS and Custom ROM
Restoring OOS TWRP Backup
To restore OOS use either fastboot ROM or MSM. Fastboot is the fastest and easiest way if u have a TWRP backup which there's a method to how to make one in this guide. BUT if you are restoring to go back to stock OOS then use MSM
I use Fastboot ROM restore for that too as we are restoring our data anyways and also for switching/installing a custom ROM. Much easier in my experience.
DOWNLOAD FULL ZIP OF OOS version of your TWRP backup otherwise you could risk doing the whole restore method again OR setup from SCRATCH! IF you aren't restoring a TWRP backup, I recommend either TRANSFER or DOWNLOAD via WiFi or oxygen updater, a UPDATED version of OOS AFTER doing either fastboot ROM or MSM restore methods. As they restore a old version of OOS!
Restoring using Fastboot ROM
Download fastboot ROM of your choice using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Restoring using MSM Download Tool
Download latest MSM version of your choice using the link in the Download Link section.
Extract/ un-zip
Click on MSM tool .exe file
Turn off device
HOLD BOTH volume buttons
Connect your phone
Wait for your device to be connected and it should show as green
Click verify to check and press start
Wait till phone reboots
The setup device and u can carrying on restoring your device if u don't want a unlock bootloader or return to what your device was like before.
Go into developer options
Allow OEM unlocking
Reboot to bootloader
Enter "fastboot devices" to check your device is connected
Enter "fastboot oem unlock"
Swipe for yes
Then it will reboot again
continue to the next method
For both fastboot and MSM
Once booted into system, set it up and update to OOS version of your TWRP backup.
Download the full zip using the link in the Download Link section.
Transfer the OOS .zip to internal storage.
Go into settings -> system update -> Update via local upgrade -> find zip file and press install
Do this twice to make sure you have installed that version of OOS in both slots
Boot to bootloader
Boot TWRP
Install TWRP
Reboot recovery
Transfer whole TWRP Folder into internal storage
Restore only boot and data
Swipe to restore
If you have backed up your internal storage folders do this
Reboot to recovery
Transfer all your internal storage folders
Reboot to system and done
Otherwise, just reboot to system. U can update OOS as well if it's outdated. The method is below to update OOS with ROOT. Up to u
RESTORING TWRP BACKUP HAS ISSUES ON THESE ROMs
CrDroid (Method 1 + 2 don't work). Method 3 works (install Gapps if the ROM doesn't have it!)
Restoring a Custom ROM TWRP backup 1
I tried using this method, but it didn't work for me.
You can use this method to switch ROMs too
Boot TWRP Recovery
Flash OOS + Finalize
Boot to bootloader, boot TWRP
Flash TWRP
Reboot Recovery
Transfer twrp backup
Restore System.img, Vendor.img and boot
Boot to system and setup system
Reboot to recovery
Restore data
Reboot system. Done
I had an issue with this method where rebooting system it was from fresh and my data didn't restore. If this happened to you, then do method 2 (Restoring a Custom ROM TWRP Backup 2)
Restoring a Custom ROM TWRP Backup 2
The first method didn't work for me. But this method did
Restore fresh like you're going back to OOS.
Choose one method. Fastboot or MSM method.
I prefer the fastboot method.
Download fastboot ROM using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Once booted into system, set it up briefly and DO NOT RESTORE ANYTHING.
Boot to bootloader
Boot TWRP
Install TWRP
Reboot recovery
Transfer whole TWRP Folder into internal storage
Restore everything (System.img, vendor.img, boot.img and data)
Swipe to restore. If data couldn't restore then boot system, setup system, boot TWRP and restore data.
Reboot system. The first reboot might go dodgy and it did for me.
Reboot system and transfer all your internal storage stuff
done
If this did not work still. Then do the 3rd method...
Restoring a Custom ROM TWRP backup 3
If the previous 2 methods has failed for you. Then try this.
Restore fresh like you're going back to OOS.
Choose one method. Fastboot or MSM method.
I prefer the fastboot method.
Download fastboot ROM using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Once booted into system, set it up and update to OOS version of your TWRP backup.
Download the full zip using the link in the Download Link section.
Transfer the OOS .zip to internal storage.
Go into settings -> system update -> Update via local upgrade -> find zip file and press install
Do this twice to make sure you have installed that version of OOS in both slots
Transfer TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to bootloader
Boot TWRP
Install TWRP
Reboot to Recovery
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Otherwise, just Format data -> reboot to recovery. Up to u
Reboot Recovery
Transfer twrp backup
Restore data
Reboot system. Done
If it still fails, repeat steps 1 to 15. But restore everything and you should be back on your custom ROM like you never left.
Updating OOS and Custom ROM
Update OOS with Root (Magisk)
Always do a TWRP backup before updating your OS in case
Download the full zip file of the latest OOS, transfer the zip file to internal storage NOT IN ANY FOLDER
Download and transfer twrp.zip file to internal storage
Go into settings, system update, update via local upgrade and choose the file
Wait till the installation has finished. If failed TRY AGAIN!
DO NOT REBOOT!
Go into Magisk Manager, modules
Find the twrp zip file and install TWRP
DO NOT REBOOT!
Go into Magisk Home
Press install
Press install via inactive slot
Reboot system and done
You will reboot into the next slot
You don’t have to repeat the installation to install the latest OOS in the other slot. But you should and I use this method many times and has never let me down.
Updating OOS without root
Go to System Update -> find the update install and reboot.
Or download the zip -> transfer to internal storage -> update via local upgrade -> reboot and done
Update a Custom ROM
Method 1
Always do a TWRP backup before updating your OS in case
Use this method just to update the ROM.
Boot recovery
Flash new version + twrp
Reboot recovery
Flash new version + twrp
If the ROM doesn't have GApps included,
The restore script should show up during the installation of the new ROM.zip
BUT if the restore script DIDN'T pop up do this
Reboot to recovery
Flash Gapps if not included
Reboot to system
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
This method uses finalize.zip
Boot recovery
Flash new version + finalize + twrp
If the ROM doesn't have GApps included,
The restore script should show up during the installation of the new ROM.zip
BUT if the restore script DIDN'T pop up do this
Reboot to recovery
Flash Gapps if not included
Reboot to system
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Updating vendor
Use Method 1 and 2 for ROMs with Gapps. Use Method 3 for ROMs with no Gapps included.
Method 1
If u haven’t updated your Custom ROM and your Vendor… You can use this method to update both or just the vendor.
Boot recovery
Flash OOS + twrp
Reboot recovery
Flash OOS + twrp
Reboot recovery
Flash Custom ROM + twrp
Reboot recovery
Flash Custom ROM + twrp
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system
Method 2
This method uses finalize.zip
Boot recovery
Flash OOS + finalize + twrp
Reboot recovery
Flash Custom ROM + finalize + twrp
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system
Method 3
This method is for ROMs with no Gapps included
You can use this method as well for updating to a vendor that has a NEWER ANDROID version like from OOS 10 to OOS 11 vendor.
Boot recovery
Flash OOS + Custom ROM + twrp
Reboot recovery
Flash OOS + Custom ROM + twrp
If u flashed GApps, the restore script should show up during the installation of the ROM.zip
If the GApps script didn't show up do this
Otherwise, skip step 3
Flash Magisk if u want root, otherwise skip step 2
Reboot to recovery
Flash Magisk
Flash Gapps
Reboot to system and done
Download Links:
SDK Platform Tools (Fastboot Tools) Here
OOS versions for OP6 (under Signed Flashable zips) Here
OOS versions for OP6T (under Signed Flashable zips) Here
TWRP for OP6 Here
TWRP for OP6T Here
Magisk Here
NikGapps Here
Stock Fastboot ROM for OP6 Here
Stock Fastboot ROM for OP6T Here
MSMDownloadTool for OP6 Here
MSMDownloadTool for OP6T Here
TitanumBackup App Here
Migrate App Here
Credits:
@mauronofrio For his amazing work on the TWRP recovery and Stock Fastboot ROMs for OP6/6T
@topjohnwu For his work on Magisk
@Nikgapps For their work on creating Gapps
@Some_Random_Username For his Collection of MSMDownloadTool for OP6/6T
@OPTeam For the collection of OOS zips for OP6/6T
@dreamwhite For the method (Method 3) of updating the vendor which works wonders for ROMs with no GApps included
First
Hey Guys,
Need a some expert advice please.
Long story short. I need to replace my OP 6T McLaren's battery as I have serious degradation in battery capacity (73% Serious Loss), meaning the battery is no longer charging to 3700mAh, max charging atm is around 2600mAh, which it drains very quickly. FYI Anything above 80% is the limit for average performance, >90% is best. You can use the OP Diagnostic App 1.0.0.9 to determine your own status. Does not work on all OP devices above 6 btw. Maybe other versions work. Anyway, will be getting OP to change the battery (no real local guys I can trust tbh, all Sammy & Apple guys...) and they want me to Factory Reset the device (complete wipe including internal storage (backed up already to PC)) before sending the device to the OP Repair Center for the obvious reasons of Privacy & Security.
On my device, I have a suite of apps that are no longer available to install with APK specially Signed, but won't be able to re-install (long story & can discuss in a PM more if there is an interest to help on this). These APK will not work any other way, I've tried! This being said, I know that TWRP Nandroids work well & have been doing these backups for yrs and have restored backups with these apps installed and it works! But I have not had to restore any as of late and TWRP Backup has somewhat changed in regards to the partition selections available. See TWRP Options pic below.
When OP returns the device to me, it will mostly likely be on the latest release of 10.3.11 (Hopefully).
Here is the current setup and runs perfectly!
OOS 10.3.11
TWRP: twrp-3.5.2_9-0-fajita
Magisk 23
The last Nandroid done today (No PW for good measure, but secured locally offline), I selected all partitions. Is this the best way to insure I get my full device backup restored?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm guessing that I will have to, Unlock the Bootloader, reinstall TWRP same version the Nandroid was created with in order to restore that backup.
Looking forward to hearing from you guys to make the best decision before proceed with the factory reset.
Thanking you all in advance for your time & assistance!
Cheers!
plepew said:
Hey Guys,
Need a some expert advice please.
Long story short. I need to replace my OP 6T McLaren's battery as I have serious degradation in battery capacity (73% Serious Loss), meaning the battery is no longer charging to 3700mAh, max charging atm is around 2600mAh, which it drains very quickly. FYI Anything above 80% is the limit for average performance, >90% is best. You can use the OP Diagnostic App 1.0.0.9 to determine your own status. Does not work on all OP devices above 6 btw. Maybe other versions work. Anyway, will be getting OP to change the battery (no real local guys I can trust tbh, all Sammy & Apple guys...) and they want me to Factory Reset the device (complete wipe including internal storage (backed up already to PC)) before sending the device to the OP Repair Center for the obvious reasons of Privacy & Security.
On my device, I have a suite of apps that are no longer available to install with APK specially Signed, but won't be able to re-install (long story & can discuss in a PM more if there is an interest to help on this). These APK will not work any other way, I've tried! This being said, I know that TWRP Nandroids work well & have been doing these backups for yrs and have restored backups with these apps installed and it works! But I have not had to restore any as of late and TWRP Backup has somewhat changed in regards to the partition selections available. See TWRP Options pic below.
When OP returns the device to me, it will mostly likely be on the latest release of 10.3.11 (Hopefully).
Here is the current setup and runs perfectly!
OOS 10.3.11
TWRP: twrp-3.5.2_9-0-fajita
Magisk 23
The last Nandroid done today (No PW for good measure, but secured locally offline), I selected all partitions. Is this the best way to insure I get my full device backup restored?
View attachment 5319753
I'm guessing that I will have to, Unlock the Bootloader, reinstall TWRP same version the Nandroid was created with in order to restore that backup.
Looking forward to hearing from you guys to make the best decision before proceed with the factory reset.
Thanking you all in advance for your time & assistance!
Cheers!
Click to expand...
Click to collapse
Idk if u have read Mauronofrio's XDA thread on TWRP backups. BUT NEVER BACKUP OR RESTORE SYSTEM OR VENDOR! From my guide, you don't need to backup vendor.img or system.img or anything else that's not Boot or Data FOR OOS. Make sure you have everything like a copy of everything folder/file in your internal storage before u wipe it.
BUT because you're going to wipe your device. U should have a copy of everything in case but don't backup system or vendor as they're useless and will crash your system if u restore those!
After you've got your device from repair, follow my method to restore OOS TWRP backup on your device and YOU'LL only NEED TO RESTORE BOOT + DATA. Once you have booted back to your system, everything should be there like you never left, but transfer your internal storage stuff as some apps store files in your internal storage. Once that is done, that should be it and it would be like you've never left
If the TWRP backup restore doesn't work let me know, but from my experience with going back to OOS via my TWRP backup I only backed up and restored boot + data for OOS. Custom ROMs are different but isn't the case for you
Extreme_Ninja2099 said:
Idk if u have read Mauronofrio's XDA thread on TWRP backups. BUT NEVER BACKUP OR RESTORE SYSTEM OR VENDOR! From my guide, you don't need to backup vendor.img or system.img or anything else that's not Boot or Data FOR OOS. Make sure you have everything like a copy of everything folder/file in your internal storage before u wipe it.
BUT because you're going to wipe your device. U should have a copy of everything in case but don't backup system or vendor as they're useless and will crash your system if u restore those!
After you've got your device from repair, follow my method to restore OOS TWRP backup on your device and YOU'LL only NEED TO RESTORE BOOT + DATA. Once you have booted back to your system, everything should be there like you never left, but transfer your internal storage stuff as some apps store files in your internal storage. Once that is done, that should be it and it would be like you've never left
If the TWRP backup restore doesn't work let me know, but from my experience with going back to OOS via my TWRP backup I only backed up and restored boot + data for OOS. Custom ROMs are different but isn't the case for you
Click to expand...
Click to collapse
Wow, thanks for the quick reply!
I have not read Mauronofrio thread and will do!
I completely missed the system & vendor piece in your instructions....my bad!
So just to confirm, my backup that I have done with all checked off is good, but only restore Boot & Data with an exact duplicate of the current Internal Storage...right?
Going forward, when creating the Backup, just select Boot & Data and I'm good to go? Or select all Except: System Image(only) & Vendor options (both)?
Also, just so I can understand a bit better, "System" is the actual OOS? Meaning, if I restore Boot & Data on any OOS, all my apps and data will be as I never left, or we should always restore on the OOS that was current at the moment of the Backup (which I have always done in the past).
PS. I may just do the backup again, just to make sure SYSTEM & VENDOR are not there for good measure!
plepew said:
Wow, thanks for the quick reply!
I have not read Mauronofrio thread and will do!
I completely missed the system & vendor piece in your instructions....my bad!
So just to confirm, my backup that I have done with all checked off is good, but only restore Boot & Data with an exact duplicate of the current Internal Storage...right?
Going forward, when creating the Backup, just select Boot & Data and I'm good to go? Or select all Except: System Image(only) & Vendor options (both)?
Also, just so I can understand a bit better, "System" is the actual OOS? Meaning, if I restore Boot & Data on any OOS, all my apps and data will be as I never left, or we should always restore on the OOS that was current at the moment of the Backup (which I have always done in the past).
PS. I may just do the backup again, just to make sure SYSTEM & VENDOR are not there for good measure!
Click to expand...
Click to collapse
First off, I already posted everything you need in my last comment and that's what I usually do. Everything should be there and not like you need to pay or reply to get the extra stuff that you may need. No point in replying asking for more as I'll just be repeating myself over and over.
Just choose boot & data for TWRP backups for OOS specifically going forward and after you got your device from repair. System, vendor doesn't work in my experience and will crash your system. Only backup the .img variant which was stated by the dev (Mauronofrio) for TWRP for OP6/6T devices. Only backup system.img and vendor.img if u need to backup system+vendor, but YOU don't have to for OOS and I said this previously.
JUST DO A BACKUP OF EVERYTHING OTHER THAN SYSTEM AND VENDOR. YOU SHOULD ONLY BACKUP SYSTEM.IMG AND VENDOR.IMG NEVER SYSTEM OR VENDOR.
They never work and will increase the size of your backup and will take even longer to transfer to your storage device from your phone.
YES, to your new question. You should update/ be on the same OOS version as your TWRP backup before u restore data + boot. Restore OOS via fastboot or msm and update to get to the same version of OOS as your TWRP backup. YOU should only do this if your phone is in the wrong version of OOS as your backup after you've got it back from REPAIR.
ALWAYS BE ON THE SAME VERSION OF OOS AS YOUR TWRP BACKUP BEFORE YOU RESTORE YOUR TWRP BACKUP OF OOS!
Maybe take a copy of your wifi passwords, take a google backup in settings, take a copy of sms/call logs and contacts. Other stuff that you may not have stored just in case the TWRP backup fails, but it shouldn't. Good luck
This should be it and there isn't anything else that you'll need
Extreme_Ninja2099 said:
First off, I already posted everything you need in my last comment and that's what I usually do. Everything should be there and not like you need to pay or reply to get the extra stuff that you may need. No point in replying asking for more as I'll just be repeating myself over and over.
Just choose boot & data for TWRP backups for OOS specifically going forward and after you got your device from repair. System, vendor doesn't work in my experience and will crash your system. Only backup the .img variant which was stated by the dev (Mauronofrio) for TWRP for OP6/6T devices. Only backup system.img and vendor.img if u need to backup system+vendor, but YOU don't have to for OOS and I said this previously.
JUST DO A BACKUP OF EVERYTHING OTHER THAN SYSTEM AND VENDOR. YOU SHOULD ONLY BACKUP SYSTEM.IMG AND VENDOR.IMG NEVER SYSTEM OR VENDOR.
They never work and will increase the size of your backup and will take even longer to transfer to your storage device from your phone.
YES, to your new question. You should update/ be on the same OOS version as your TWRP backup before u restore data + boot. Restore OOS via fastboot or msm and update to get to the same version of OOS as your TWRP backup. YOU should only do this if your phone is in the wrong version of OOS as your backup after you've got it back from REPAIR.
ALWAYS BE ON THE SAME VERSION OF OOS AS YOUR TWRP BACKUP BEFORE YOU RESTORE YOUR TWRP BACKUP OF OOS!
Maybe take a copy of your wifi passwords, take a google backup in settings, take a copy of sms/call logs and contacts. Other stuff that you may not have stored just in case the TWRP backup fails, but it shouldn't. Good luck
This should be it and there isn't anything else that you'll need
Click to expand...
Click to collapse
Thank you!!
Hey guys, for some reason I ended up on "Unmodified System Partitions", must have tapped the screen a few times in error while handling the phone I guess.
What should I do?
Unable to go back to TWRP main menu without selecting an option.
I am rooted, on stock OOS and not doing customs ROM at this time...
What should I do?
Select "Keep Read Only"? or Swipe to "Allow Modifications"?
thanking you guys in advance for you help & guidance!
plepew said:
Hey guys, for some reason I ended up on "Unmodified System Partitions", must have tapped the screen a few times in error while handling the phone I guess.
What should I do?
Unable to go back to TWRP main menu without selecting an option.
I am rooted, on stock OOS and not doing customs ROM at this time...
What should I do?
Select "Keep Read Only"? or Swipe to "Allow Modifications"?
View attachment 5320971
thanking you guys in advance for you help & guidance!
Click to expand...
Click to collapse
Swipe to allow modifications. But it seems that your internal storage corrupted. Not sure what you did and how you got into this situation.
After you swiped to allow modifications... If the internal storage files are a messed up, try to switch slots and reboot recovery
Extreme_Ninja2099 said:
Swipe to allow modifications. But it seems that your internal storage corrupted. Not sure what you did and how you got into this situation.
After you swiped to allow modifications... If the internal storage files are a messed up, try to switch slots and reboot recovery
Click to expand...
Click to collapse
I swiped and yeah, the IS was messed up in File Managfer(TWRP).
Selected Reboot then Selected the Slot I remembered I was on : "A"
Rebooted & Boom all good!
Thank you for the help once again! You rock!!
plepew said:
I swiped and yeah, the IS was messed up in File Managfer(TWRP).
Selected Reboot then Selected the Slot I remembered I was on : "A"
Rebooted & Boom all good!
Thank you for the help once again! You rock!!
Click to expand...
Click to collapse
Cool and at least that was a easy fix
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
jas84701 said:
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
Click to expand...
Click to collapse
Well u posted this twice which isn't necessary and people will try and reply. But I'm not sure if there is a way to know and as long as u copied the whole TWRP folder for that backup, u should be fine restoring it with a newer version of TWRP. If it really matters to you, then maybe try and find the latest TWRP on the date you did the backup? I think just using a newer TWRP version should be fine
Should I use the same Gapps package I flashed during clean installing when updating custom rom?
Waynenolan92 said:
Should I use the same Gapps package I flashed during clean installing when updating custom rom?
Click to expand...
Click to collapse
U don't have to use the same gapps package. Using a updated one would be better. But, u only have to for ROMs that don't include gapps (vanilla builds) AND the Restore script doesn't show up during installation. Opengapps doesn't have that script but nikgapps does. Using dirty flash/updating a ROM should show the restore script and if it doesn't then just reboot to recovery and flash the updated or same gapps package. This can also be the same for updating the base/vendor (use method 3 in that section of the guide). I hope this helps
Extreme_Ninja2099 said:
U don't have to use the same gapps package. Using a updated one would be better. But, u only have to for ROMs that don't include gapps (vanilla builds) AND the Restore script doesn't show up during installation. Opengapps doesn't have that script but nikgapps does. Using dirty flash/updating a ROM should show the restore script and if it doesn't then just reboot to recovery and flash the updated or same gapps package. This can also be the same for updating the base/vendor (use method 3 in that section of the guide). I hope this help
Click to expand...
Click to collapse
Thanks for your replay)))it's my first using vanilla rom(without Gapps), so I flashed nikigapps Omni package, and my question is: should I always use the same package, or I can go with core package for example?
Waynenolan92 said:
Thanks for your replay)))it's my first using vanilla rom(without Gapps), so I flashed nikigapps Omni package, and my question is: should I always use the same package, or I can go with core package for example?
Click to expand...
Click to collapse
U can... But it doesn't really matter as a updated package works fine and u only need to use it if the nikgapps restore script doesn't show up when updating the ROM or vendor/base (OOS underneath)
I want to CHANGE custom ROMs (havoc to Lineage OS a11 to a12) I have taken TWRP back up of boot+data+system.img+ vendor.img. once I flash the new a12 Lineage plus Nikapps core plus magisk. What steps to restore data? any response is appreciated in advance. Thank you.

Categories

Resources