Related
ONLY FOR SGH-T999V VERSION OF GALAXY S3
UPDATED 2012-12-29: Resources at the bottom
JELLY BEAN UPDATE FROM VIDEOTRON DECEMBER
If you have made the Jelly bean update from Videotron in december 2012, you can't go trough these step. You need to first restore the stock
firmware. (2012-05-28 12:10:55 - download from my resource folder) and after go with the normal step from the Android ICS 4.0 not from JB. That's what I had to do to return to CM10.
Install ClockworkMod and Root
Requirements:
• Start from ICS not from Jelly Bean (update from Videotron in december 2012), if you have Jelly Bean restore to ICS with the method bellow.
• Handset USB drivers (T-Mobile_T999_GSIII_Samsung_USB_Driver_v1_4_6_0.exe, 23.2 MB) installed on the PC
• Enable USB debugging on your handset. Go to Settings > Developer options > USB Debugging.
• Maintain a phone battery charge of at least 75%
• Download the following to your PC:
o Odin3 v3.04 (Odin3-v3.04.zip, 457 kB) https://www.dropbox.com/s/t7mhx4huexiqu1b/Odin3-v3.04.rar
o ClockworkMod Recovery (clockworkmod.TAR, 6.8 MB) https://www.dropbox.com/s/1iplxgsticl1d4q/clockworkmod.TAR
o CWM-SuperSU-v0.87 https://www.dropbox.com/s/xbe27r6khd54ypd/CWM-SuperSU-v0.87.zip
Instructions:
a. Copy the CWM-SuperSu-v0.87.zip file on your phone at the root of sdcard.
1. Extract the Odin ZIP file to a folder on your computer, preferably on your Desktop where you can easily find it.
2. Turn off your phone.
3. Reboot it into Download Mode by holding down the Volume Down, Home, and the Power buttons until you see “Warning!!” displayed on the screen. Press the Volume Up key again to continue to Download Mode. You will know when you are in Download Mode when you see a green Android with “Downloading” text displayed. If you don’t see it, try again.
4. Go to the folder where you extracted Odin and double-click on Odin3 v3.04.exe to run it.
5. Connect your phone to your PC and if drivers will install again, allow installation to finish first.
6. Odin should recognize your phone. You will know if it did when the COM box in the leftmost part of the window turns blue. An “Added!!” message will also be displayed in the message box.
7. In Odin, click the PDA tab and select the clockworkmod.TAR file.
8. Double check that the “Auto Reboot” and “F. Reset Time” options are ticked.
9. Click Start in Odin to flash ClockworkMod Recovery on your phone and wait for the flashing to finish.
10. Once done, your phone will automatically reboot and you will see a message in Odin saying “Pass!”. This indicates that you can now unplug your phone and close Odin.
11. Boot into ClockworkMod Recovery. Turn off your phone and hold down the Volume Up, Home, and the Power buttons together until the screen turns on. Let go of the buttons and your phone should now boot into ClockworkMod Recovery.
12. Click on install zip, zip from sdcard and select your CWM-SuperSu zip file and flash it.
13. You can press Reboot now.
Great! You now have ClockworkMod Recovery installed
Install ClockworkMod Touch
Requirements:
- done the previous step (Install ClockworkMod and Root)
- Download the following to your PC:
o ClockworkMod Touch https://www.dropbox.com/s/1ydtp2jyo5br9ww/recovery-clockwork-touch-5.8.4.7-d2tmo.img
Instructions:
1. Download ClockworkMod Touch from http://www.clockworkmod.com/rommanager for your device (for this tutorial i use the one in download list)
2. Rename the file cwmtr.img to make the task easier
3. Place the file in your root sdcard
4. install an terminal emulator like this one: https://play.google.com/store/apps/...idterm&feature=nav_result#?t=W251bGwsMSwyLDNd
5. Run this commands:
su
dd if=/sdcard/cwmtr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
6. reboot in recovery mod,
Good ! you have the touch clockworkmod !
Install CyanogenMod 9 on T999V
Requirements:
- Done the two previous step (1. Install ClockworkMod and Root and 2. Install ClockworkMod Touch)
- Download the following to your PC:
o CyanogenMod 9 http://www.clockworkmod.com/rommana...tlies&deviceName=Samsung Galaxy S3 (T-Mobile)
o Google Apps http://www.clockworkmod.com/rommana... Apps&deviceName=Samsung Galaxy S3 (T-Mobile)
Instructions:
1. Place the Cyanomodgen 9 zip and google apps zip on your phone on root sdcard.
2. Reboot in recovery mode
3. Once the device boots into the ClockworkMod Recovery, Select backup and restore to create a backup of current installation on the Samsung Galaxy S III.
4. Select the option to Wipe data/factory reset.
5. Then select the option to Wipe cache partition.
6. Select Install zip from sdcard.
7. Select Choose zip from sdcard.
8. Select the CyanogenMod zip and flash it
9. Install the Google Apps by performing steps 6 - 7 again and choosing the Google Apps zip
10. Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option.
It's done ! you boot in CyanogenMod 9 !!!
Install CyanogenMod 10 on T999V
Requirements:
*- Done the two previous step (1. Install ClockworkMod and Root *and 2. Install ClockworkMod Touch)
- Download the following to your PC:
* * * * *o CyanogenMod 10 http://get.cm/?device=d2tmo
* * * * * o * *Google Apps http://goo.im/gapps/gapps-jb-20120726-signed.zip
Instructions:
1. Place the Cyanomodgen 10 zip and google apps zip on your phone on root sdcard.
2. Reboot in recovery mode
3. Once the device boots into the ClockworkMod Recovery, *Select backup and restore to create a backup of current installation on the Samsung Galaxy S III.
4. Select the option to Wipe data/factory reset.
5. Then select the option to Wipe cache partition.
6. Select Install zip from sdcard.
7. Select Choose zip from sdcard.
8. Select the CyanogenMod *zip and flash it
9. Install the Google Apps by performing steps 6 - 7 again and choosing the Google Apps zip
10. Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option.
It's done ! you boot in CyanogenMod 10 !!!
Update between CyanogenMod builds
- Make a full backup of your phone with Titanium backup
- Download the new build from here: http://www.clockworkmod.com/rommana...htlies&deviceName=Samsung Galaxy S3 (T-Mobile)
- Place it on the root of sdcard
- Reboot in recovery mode
- Make a backup of your phone (restore if the new builg is wrong)
- Wipe Cache
- Optionnal: wipe dalvik (by default flashing new rom clear dalvik anyway)
- Install your new build from zip
- Reboot
- If you loose some data or app restore from titanium backup.
Done! you have new your new build!
Download your Stock firmware
- Download http://fus.nanzen.se/download.php?id=12
- In the droplist (choose a firmware) select Android
- In the next droplist select the SGH-T999V
- Select your region, for me it's VTR for Videotron in canada
- Click on "Check firmware" and wait
- After under the result section click on Download.
Done! you have your stock firmware.
Reset Binary counter
- Go to the Play Store and get Triangle Away (https://play.google.com/store/apps/...leaway&feature=nav_result#?t=W251bGwsMSwyLDNd)
- Give the root user rights
- Open triangle away and click on Reset Flash counter
- wait and reopen triangle away and check the status.
Now! you have your binary counter to 0.
Restore the stock firmware in Galaxy S3
- Download Odin (https://www.dropbox.com/s/t7mhx4huexiqu1b/Odin3-v3.04.rar)
- Download your Stock Firmware (see previous step)
- Put your device in restore mode (press and hold home + volume up + power when device shutdown keep pressing only home and volume up until you see samsung logo)
- now wipe cache and wipe data
- Put your device in Download mode (press and hold home + volume down + power when device shutdown keep pressing only home and volume down until you see samsung logo)
- press volume up to go in download mode
- open Odin, now ou see a com port added to odin (it's your phone)
- check if checkbox Auto Reboot and F. reset Time are checked.
- Click on PDA and select your firmware md5 file
- when you are ready, click on start and wait
When your device is restarting you will see your stock firmware running !
RESOURCES ARE HERE NOW:
https://www.dropbox.com/sh/1f8zmsfzgeiuxku/XZ6_NvbcdW
(I'm not sure if I made the shared folder the good way, so don't be shy to inform me if there is a trouble.)
it contains:
-files
-url shortcut for download updated ressources (shortcut from chrome)
Has anybody else tried this yet on their Canadian gs3...???
Rickkins said:
Has anybody else tried this yet on their Canadian gs3...???
Click to expand...
Click to collapse
i don't know but i'm customer of Videotron and i make 1 week research before apply this recipe to flash my phone, and my phone work perfect!
Try it !
fox4305 said:
i don't know but i'm customer of Videotron and i make 1 week research before apply this recipe to flash my phone, and my phone work perfect!
Try it !
Click to expand...
Click to collapse
Thanks, I may just do that.
What part of this procedure actually "roots" the phone...???
Yes, I am indeed that noobular...
Rickkins said:
Thanks, I may just do that.
What part of this procedure actually "roots" the phone...???
Yes, I am indeed that noobular...
Click to expand...
Click to collapse
The first one root the phone.
Sent from my SGH-T999 using xda premium
Rickkins said:
Has anybody else tried this yet on their Canadian gs3...???
Click to expand...
Click to collapse
I just did this on my Videotron (Canadian) GS3 T999V and it works great
simondadiamond said:
I just did this on my Videotron (Canadian) GS3 T999V and it works great
Click to expand...
Click to collapse
cool !
Can someone with a Wind Mobile SGH-T999V comment on their experience with this?
I'm using a wind GS3. It's really a great rom. I've tried the redrum r4, but HSPA+ doesn't work, and a lot of t-mobile apps. Then I tried this rom, found out that every thing works. It won't overwrite the baseband. Mine is still T999VVLLE6. This is a rom that you really need to try.
Sent from my SGH-T999V using xda app-developers app
grey43 said:
I'm using a wind GS3. It's really a great rom. I've tried the redrum r4, but HSPA+ doesn't work, and a lot of t-mobile apps. Then I tried this rom, found out that every thing works. It won't overwrite the baseband. Mine is still T999VVLLE6. This is a rom that you really need to try.
Sent from my SGH-T999V using xda app-developers app
Click to expand...
Click to collapse
Do you know why the HSPA+ doesn't work? I've had phones flashing new ROMs and the data wasn't working because I forgot to add WIND's APN in the mobile network settings
adslee said:
Do you know why the HSPA+ doesn't work? I've had phones flashing new ROMs and the data wasn't working because I forgot to add WIND's APN in the mobile network settings
Click to expand...
Click to collapse
The WIND APN was there by default. 3G does work but HSPA+ not. I have no idea why this happens. Maybe it's just simply Redrum is made from T-mobile stock ROM. Did anybody else try this great ROM?
hi, many thanks for this post.
quick question? I downloaded my stock firmware, do I just throw it in my SDcard's ROOT and flash using Clockwork ?
im awfully new to this sorry
GearshiftJB said:
hi, many thanks for this post.
quick question? I downloaded my stock firmware, do I just throw it in my SDcard's ROOT and flash using Clockwork ?
im awfully new to this sorry
Click to expand...
Click to collapse
check this tutorial and follow this one but with your stock firmware
http://www.androidauthority.com/galaxy-s3-gt-i9300-android-4-0-4-ics-xxalf2-stock-firmware-100309/
that sound great for you ?
Many thanks to the OP!!
I would like to start with saying many thanks to the OP!! Merci mon ami!!
I also have a Videotron phone that is now rooted and flashed thanks to the OP.
I have been messing around quite a bite lately with different roms on this Phone.
So far I have found that CM10 seems to work best for my phone and has the less amount of bugs.
To the new guys finding this thread and wanting to root/flash your phone. I stress the need for a full backup before applying a new rom.
After installing Clockworkmod - follow the OP's instruction to make a full backup of your phone.
And until you are very familiar with the process. Keep a copy on your internal SD for easy flash back to the stock rom.
Lets get a lot of people involved in this thread so we can gain the most knowledge about these phones/mods.
If you guys have any questions please ask away.
Thanks all.
peleberchot said:
I would like to start with saying many thanks to the OP!! Merci mon ami!!
I also have a Videotron phone that is now rooted and flashed thanks to the OP.
I have been messing around quite a bite lately with different roms on this Phone.
So far I have found that CM10 seems to work best for my phone and has the less amount of bugs.
To the new guys finding this thread and wanting to root/flash your phone. I stress the need for a full backup before applying a new rom.
After installing Clockworkmod - follow the OP's instruction to make a full backup of your phone.
And until you are very familiar with the process. Keep a copy on your internal SD for easy flash back to the stock rom.
Lets get a lot of people involved in this thread so we can gain the most knowledge about these phones/mods.
If you guys have any questions please ask away.
Thanks all.
Click to expand...
Click to collapse
How's CM10? Any huge bugs on the ROM or flaws so far?
CM10
adslee said:
How's CM10? Any huge bugs on the ROM or flaws so far?
Click to expand...
Click to collapse
Hi There.
I have been using CM10 for a daily driver for about 1 week now. My current build dates from the 14th.
It is very stable on my phone and have not experienced a crash.
I did wipe clean before installing the rom. Make sure you have backups before doing anything.
You should always have a full backup made with Clockworkmod and easily accessible on your main SD card in case something goes wrong.
But dont be shy to use the latest CyanogenMod 10. You can always revert back if you don't like it.
peleberchot said:
Hi There.
I have been using CM10 for a daily driver for about 1 week now. My current build dates from the 14th.
It is very stable on my phone and have not experienced a crash.
I did wipe clean before installing the rom. Make sure you have backups before doing anything.
You should always have a full backup made with Clockworkmod and easily accessible on your main SD card in case something goes wrong.
But dont be shy to use the latest CyanogenMod 10. You can always revert back if you don't like it.
Click to expand...
Click to collapse
I assume you are using the T-mobile nightly build of CM10 correct?
galaxy s3
Bonjour ,je suis nouveau ici et besoin d'aide merci ,j'ai le galaxy s3 sgh-t999 cloclworkmod recovery v5.8.4.7 je me demande si je peux siuvre la meme instruction en haute
autre question pour quoi je vois pas mon carte ext sdcard dans le mode recovery v5.8.4.7
cette etape: Copy the CWM-SuperSu-v0.87.zip file on your phone at the root of sdcard
est-ce que je dois copier dans mon sdcard ou ext sdcard
car quand je reboote mon covery cloclworkmod recovery v5.8.4.7 je vois pas mon ext sdcard
merci j'attend votre repondre
Hello, I am new here and need of help(assistant) thank you, I have the galaxy s3 Sgh-t999 cloclworkmod recovery v5.8.4.7 I wonder if I can follow the same instruction in the other high question for which I see not my card(map) is sdcard in the recovery mode v5.8.4.7 this stage: Copy the CWM-SuperSu-V0.87 zip takes off has to your phone at the root of sdcard I have to copy in my sdcard or ext-sdcard because when I reboote my covery cloclworkmod recovery v5.8.4.7 I see not my and ext-sdcard thank you I wait your to answer
Videotron Galaxy S3
samsung glx3 said:
Bonjour ,je suis nouveau ici et besoin d'aide merci ,j'ai le galaxy s3 sgh-t999 cloclworkmod recovery v5.8.4.7 je me demande si je peux siuvre la meme instruction en haute
autre question pour quoi je vois pas mon carte ext sdcard dans le mode recovery v5.8.4.7
cette etape: Copy the CWM-SuperSu-v0.87.zip file on your phone at the root of sdcard
est-ce que je dois copier dans mon sdcard ou ext sdcard
car quand je reboote mon covery cloclworkmod recovery v5.8.4.7 je vois pas mon ext sdcard
merci j'attend votre repondre
Hello, I am new here and need of help(assistant) thank you, I have the galaxy s3 Sgh-t999 cloclworkmod recovery v5.8.4.7 I wonder if I can follow the same instruction in the other high question for which I see not my card(map) is sdcard in the recovery mode v5.8.4.7 this stage: Copy the CWM-SuperSu-V0.87 zip takes off has to your phone at the root of sdcard I have to copy in my sdcard or ext-sdcard because when I reboote my covery cloclworkmod recovery v5.8.4.7 I see not my and ext-sdcard thank you I wait your to answer
Click to expand...
Click to collapse
Hi,
From my experience with the phone. Yes you have to copy all the files to the internal SD and not your external SD card. There must be a setting but I can't find it.
So to keep everything safe just copy all the needed files to the root of your internal SD card.
Cheers!
Marc
---------- Post added at 09:19 PM ---------- Previous post was at 08:53 PM ----------
sluma said:
I assume you are using the T-mobile nightly build of CM10 correct?
Click to expand...
Click to collapse
Yes I am using the CM10 d2tmo releases. Which are for the T-Mobile version of the S3.
I tried to post a link but I guess I cant... look for something called BBQLog and you will find the change logs and the releases.
And here is the thread about it on the main forums. You will find a lot of info from other users and say what kind of issues they are having with the latest builds. So you can decide to flash or not to flash
http://forum.xda-developers.com/showthread.php?t=1778217
You will also find a link in that thread to the BBQLog website.
Cheers!
Marc
---------- Post added at 09:25 PM ---------- Previous post was at 09:19 PM ----------
ok.
Sorry I tried to break up those post into two instead of one post but it did not work. Obviously I have no idea what I am doing on here yet... lol.
And yes just trying to pad a bit my post count. It's a bit silly that you have to have 10 post counts before you can post links or even have a signature!!
But I will survive and be here .. hehe.
It seems like a great community.
Have a great evening all.
Cheers!!
Marc
samsung glx3 said:
Bonjour ,je suis nouveau ici et besoin d'aide merci ,j'ai le galaxy s3 sgh-t999 cloclworkmod recovery v5.8.4.7 je me demande si je peux siuvre la meme instruction en haute
autre question pour quoi je vois pas mon carte ext sdcard dans le mode recovery v5.8.4.7
cette etape: Copy the CWM-SuperSu-v0.87.zip file on your phone at the root of sdcard
est-ce que je dois copier dans mon sdcard ou ext sdcard
car quand je reboote mon covery cloclworkmod recovery v5.8.4.7 je vois pas mon ext sdcard
merci j'attend votre repondre
Hello, I am new here and need of help(assistant) thank you, I have the galaxy s3 Sgh-t999 cloclworkmod recovery v5.8.4.7 I wonder if I can follow the same instruction in the other high question for which I see not my card(map) is sdcard in the recovery mode v5.8.4.7 this stage: Copy the CWM-SuperSu-V0.87 zip takes off has to your phone at the root of sdcard I have to copy in my sdcard or ext-sdcard because when I reboote my covery cloclworkmod recovery v5.8.4.7 I see not my and ext-sdcard thank you I wait your to answer
Click to expand...
Click to collapse
oui je confirme car sd interne de votre cellulaire et oui vous pouvez effectué la même manipulation.
This is the new thread for Pie & 10 TWRP Recovery 3.3.1-x
Feature list:
- Pie stock ROMs are fully decryptable with this TWRP, either protected with secure startup or without :good: OREO encrypted userdata is not decryptable with 3.3 . However, if you're on encrypted oreo and update to pie stock, either via zip or kdz, crypto gets migrated and you're good to go in terms of access to your encrypted data with 3.3. So, with this recovery, the urgent need for flashing no-verity-opt-encrypt zip isn't really there anymore
- everything working: backup & restore even with encrypted userdata, no matter if it's from oreo or pie. If you restore a backup containing an encrypted userdata, you'll need to format userdata before, for crypto removal. But only when coming from another encrypted ROM, otherwise you can just restore, boot up (it will use the encryption settings you"ve set up) ; decryption; time & dat; mtp; adb; installing of ROMs and zips in general; themeable; .........
- Possibility to leave out lockscreen settings when restoring a backup (sometimes you were forced to delete them manually, otherwise no login into your restored ROM possible -.- You can bypass this with this. Note: lockscreensettings ≠ encryption pin/pw/pattern.)
- Time and date is shown correctly, independent of /data. This should work after a few boots of ROM and TWRP, TWRP needs to get the data once and later on it will then be calculated from persist's settings file.
- modem image support: backup, restore, flashing of modem images either taken directly from kdz or diskdump. Same for OP partition (not present on USA and some others possibly)
- For removing encryption completely you can now do it as already known, via format userdata. Crypto is removed with it now again.
- busybox instead of toolbox/toybox, for better zip compatibility as it looks for now
- Pie 3.3.1-x: compiled with full 9.0 TWRP sources
- capable of installing every ROM and zip files
- some extra partitions (see below)
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.
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 too (described above).
For decryption: it works as it should. Therefore it is a little bit tricky to restore a backup of a ROM which had encrypted userdata, when you'd installed any other ROM in between. There are some points to remember when restoring, a little guide is available in old thread's third post (https://forum.xda-developers.com/showpost.php?p=77839649&postcount=3), 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:
- Copy the new image file to one of your phone storages
- 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>
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.
This time no optional version of TWRP is available, it's "one for all". This TWRP works for every V30 model, and only for them. I removed vendor partition too btw, there isn't any active development about that, so it's useless and only confuses ppl. DataImage function is available.
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).
CHANGELOG:
February 23rd, 2020, TWRP 3.3.1-2:
- corrected blocksize for formatting crypto related partitions
- included timezone data, maybe helps some ppl with time still not showing correct; should speed up time calc
- used pre-compiled full mke2fs and e2fsdroid binaries
- enabled ntfs experimental support (rw in kernel, NTFS_3G flag in twrp / ofox)
- minimal tweaks
- enabled F2FS and NTFS support
January 1st, 2020, TWRP 3.3.1-1:
- Formatting problem solved, TWRP now removes crypto as it should when user initiates a data format
- small fixings like checkbox layout in restore menu
- Moved a LOGERR to LOGINFO: "E: Unable to decrypt FBE device". Couldn't get rid of it with our needed config...
Dec. 30th, 2019, TWRP 3.3.1-0:
- initial first version
- almost everything working like in 3.2 oreo TWRP
- Formatting your device doesn't remove crypto from disk, so a "fresh" (formatted) userdata gets disturbed by old security lock
DOWNLOADS:
Nougat, Oreo and Pie capable 3.3.1-0 TWRP, but decrypting support only for PIE (AOSP untested, stock confirmed):
Download links below (always the latest and newest only; one version for all):
File name: TWRP-JOAN-3312_2020-02-23.img
MD5sum: 2fd78a606b65274977f1cd63080d5f23
MAIN Download: MEGA, TWRP-JOAN-3312_2020-02-23.img
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 the stuff added. Pie is "encrypt-9.0" branch. omni's android-9.0 branch almost fully compatible, beside not being able to remove crypto (dirty hack, sry )
Much appreciated for your hard work. Twrp after all is the base for all customization
Thanks!
sure, enjoy it
btw, is there someone with oreo encrypted...? would be nice to know if it's decryptable with this new twrp too, and we therefore only need this one (and the other one can be archived...?)?
which is spoken very early, there's a lot left to do for 3.3 running really flawlessly. but, of course, this will be continued and being further worked on :good: starting right now xD
@ChazzMatt: it will take a while until wtf can be updated with this new one here. this is in an late beta stage, it works but has some quirks left. nothing that can destroy a phone but this twrp isn't fully working at this point of time and therefore not possible to use "in productive threads".
Everything works as well as the previous stable recovery.
I have tried:
1. backing up and restoring ROMs
2. Flashing, ROMs(stock pie and aosp Q), kernels and other mods.
Big thanks ??
In my case time is still not correct, I have to choose a different timezone compared to actual.... When booted up normally, it is correct.
kanehun said:
In my case time is still not correct, I have to choose a different timezone compared to actual.... When booted up normally, it is correct.
Click to expand...
Click to collapse
it needs some boots and reboots to recovery. after setting up everything it showed in twrp as it should :good: i'll add the tzdata back, a registry of all timezones, used for calculation of time, maybe it helps.
Time zone is beyond screwed up, 3 hours off without DST. Also, I'm on Oreo and it's asking for the decrypt password to access internal SD.Going back to 3.2.3-7.
ldeveraux said:
, I'm on Oreo and it's asking for the decrypt password to access internal SD.Going back to 3.2.3-7.
Click to expand...
Click to collapse
Try using the Pie compatible Decryption Disabler and then Reformatting data...
Have you tried flashing the @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) before reformatting?
Flash Magisk,
Flash Pie-compatible encryption disabler,
Flash JohnFawkes Root Checker disabler,
Reformat data (where you type yes),
Reboot to recovery from within TWRP,
Flash Magisk AGAIN,
Reboot phone.
See this post: https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
_____________
7. MORE TWRP ACTIONS - Now turn off data encryption and install essential items… all in TWRP:
(This is not a "menu" in TWRP, it's merely a list of what you NEED to do before booting to the OS)
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Install the Magisk zip. (This is to give the encryption disabler root privileges)
d. Install @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
e. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
g. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
h. Re-flash the Magisk zip again. (This is to make sure, due to Pie changes.)
i. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
ChazzMatt said:
Try using the Pie compatible Decryption Disabler and then Reformatting data...
Have you tried flashing the @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) before reformatting?
Flash Magisk,
Flash Pie-compatible encryption disabler,
Flash Root Checker disabler,
reformat data (where you type yes),
reboot to recovery from within TWRP,
flash Magisk AGAIN,
reboot phone.
See this post: https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
_____________
7. MORE TWRP ACTIONS - Now turn off data encryption and install essential items… all in TWRP:
(This is not a "menu" in TWRP, it's merely a list of what you NEED to do before booting to the OS)
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Install the Magisk zip. (This is to give the encryption disabler root privileges)
d. Install @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
e. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
g. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
h. Re-flash the Magisk zip again. (This is to make sure, due to Pie changes.)
i. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
Click to expand...
Click to collapse
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
ldeveraux said:
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
Click to expand...
Click to collapse
Were you already on a decrypted ROM using the older version of TWRP? Trying to figure out if the same encrypted internal storage situation will happen to me if I bother to try this Pie version of TWRP. Just would stick with Oreo TWRP if it's going to be this whole hassle to upgrade.
Thanks!
:victory: thank you seadersn!
ldeveraux said:
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
Click to expand...
Click to collapse
It's the exact steps people have to do when installing TWRP to work with bootloader unlocked Pie KDZ.
We needed new Encryption Disabler and we needed new Root Checker Disabler and we needed to flash Magisk twice.
The order of steps had to be rewritten besides new files.
Those have been in effect ever since EU H930 got Pie. Works on Oreo AND Pie bootloader unlocked KDZ.
drewcu said:
Were you already on a decrypted ROM using the older version of TWRP? Trying to figure out if the same encrypted internal storage situation will happen to me if I bother to try this Pie version of TWRP. Just would stick with Oreo TWRP if it's going to be this whole hassle to upgrade.
Thanks!
Click to expand...
Click to collapse
I'm on the TWRP flashable US99820H, so no clue
ChazzMatt said:
It's the exact steps people have to do when installing TWRP to work with bootloader unlocked Pie KDZ.
Those have been in effect ever since EU H930 got Pie.
Click to expand...
Click to collapse
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
ldeveraux said:
I'm on the TWRP flashable US99820H, so no clue
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
Click to expand...
Click to collapse
Any TWRP flashable ROM was likely decrypted and is similar to my situation (except I'm on Pie VS99630c). Sounds like upgrading to TWRP 3.3.1 Pie is more hassle than it's worth and I'll stay put.
Thanks.
ldeveraux said:
I'm on the TWRP flashable US99820H, so no clue
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
Click to expand...
Click to collapse
Sure. I'm still on stock rooted Oreo firmware, also.
But those two new files, different order of steps work with both Oreo AND Pie Bootloader Unlocked KDZ with 3 2.3.7 -- whereas the older method and (with original decryption and root check disabler files) were in place before Pie.
WTF has always had decryption and root check disabler files and reformat of data to install TWRP.
What's different now is newer files to be effective on Pie KDZ as well as different order of steps -- as well as flashing Magisk at the beginning and again at the end.
I am hoping those files and steps also work with this new TWRP 3.3.1.
---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------
drewcu said:
Any TWRP flashable ROM was likely decrypted and is similar to my situation (except I'm on Pie VS99630c). Sounds like upgrading to TWRP 3.3.1 Pie is more hassle than it's worth and I'll stay put.
Thanks.
Click to expand...
Click to collapse
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
ChazzMatt said:
Sure. I'm still on stock rooted Oreo firmware, also.
But those two new files, different order of steps work with both Oreo AND Pie Bootloader Unlocked KDZ with 3 2.3.7 -- whereas the older method and (with original decryption and root check disabler files) were in place before Pie.
WTF has always had decryption and root check disabler files and reformat of data to install TWRP.
What's different now is newer files to be effective on Pie KDZ as well as different order of steps -- as well as flashing Magisk at the beginning and again at the end.
I am hoping those files and steps also work with this new TWRP 3.3.1.
---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
Click to expand...
Click to collapse
I am on John Fawkes' Pie VS99630c TWRP flashable ZIP using TWRP 3.2.3.7. The concern is whether upgrading TWRP to 3.3.1 is as simple is flashing the IMG file within TWRP 3.2.3.7, or whether we'll have to reflash multiple things in a whole list of steps. If it's the latter, then why not just stay on TWRP 3.2.3.7 which seems to do everything we need in terms of flashing Pie ROMs?
ChazzMatt said:
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
Click to expand...
Click to collapse
it's only formatting data switched to "fastboot -w" (reformats cache and data) or "fastboot erase userdata" (reformats data). both remove eventually present encryptions. everything else works like in the default wtf recovery :good: and that's really an enerving point... i want to simply format my userdata in twrp and not have to switch to fastboot...
formatting now works :good:
drewcu said:
I am on John Fawkes' Pie VS99630c TWRP flashable ZIP using TWRP 3.2.3.7. The concern is whether upgrading TWRP to 3.3.1 is as simple is flashing the IMG file within TWRP 3.2.3.7, or whether we'll have to reflash multiple things in a whole list of steps. If it's the latter, then why not just stay on TWRP 3.2.3.7 which seems to do everything we need in terms of flashing Pie ROMs?
Click to expand...
Click to collapse
it's the first: flashing image easily. only thing is, as described above, removing encryption requires fastboot. atm not possible to do this in recovery as usual. therefore nod suitable for wtf thread, but for anybody else, especially the ones who have pie installed and want to acces their data in twrp when encrypted. i'll test oreo decryption compatibility soon, zip needs downloading time lol
oreo decryption compatibility not given with 3.3 but: you can easily migrate from encrypted oreo via fw zip to pie, it adopts the storage encryption then and 3.3 is able to unlock :good: i've got a solution for 3.3 not being able to remove encryption: i keep a copyof 3.2.3-7 image on external sd and install it when formatting needed xD then back to 3.3 and good to go.
workaround no more needed, working now
If you purchased a OnePlus 7T which went on sale recently, but still aren't able to replace the T-Mobile firmware with the internat'l variant then you're in luck. I came across a few guides which were a smoking gun, but I was never fully able to get it to work successfully and "failed miserably". And a few posts I read helped spur some ideas and inspired me to think outside the box in order to come up with a much more predictable viable solution here. Throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. The instructions given were made with the expectation that you already have the bootloader unlocked and installed the necessary drivers with adb setup. I followed this guide here as point of reference which I think could be potentially bypassed by using this method instead to completely streamline the process. Best of all, I spent 15 hours yesterday trying to figure this out so hopefully you won't have to go through what I did. NOW LET'S BEGIN!!!
FLASH OPERATIONS
I. Just to give a little background for those of you who followed the guide I referenced, whenever I attempted to flash the 10.0.13-GLOBAL fastboot rom it would display the error message "Flashing is not allowed for Critical Partitions" multiple times then auto reboot T-Mobile logo splash screen, indicating that the process failed.
At this point, hold Vol Up + Power till the device shuts down and boot into fastboot.
On the PC, download the All In One v2.0.1.3 tool.
Download 10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT.zip or from here.
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
II. Download and extract "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip" into a folder called "adb" in the root of the C: drive.
III. While the phone is turned on, we must boot into FastbootD. The fastbootD screen has the OnePlus logo centered at the top with 3 language choices. Run "cmd" as admin and type:
Code:
adb reboot bootloader
fastboot reboot fastboot
IV. Enter this command to check what version of Fastboot you've booted into:
Code:
fastboot getvar is-userspace
"Yes" means you're in FastbootD.
V. To flash the "10.0.13-GLOBAL" fastboot rom, run the bat script by entering these commands:
Code:
cd C:/adb
flash-all.bat
During flash process, it will reboot once into FastbootD again (stock recovery menu) and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.13HD65AA rom image.
Take the opportunity to perform a system update to Oxygen OS 10.0.15.HD65AA.
Enable developer mode: Go to Settings –> About phone (at bottom) –> tap Build number (towards right) until it says Developer Mode is enabled.
Go to Developer Options –> Enable USB Debugging and "allow". Go to "Default USB configuration" and change it to "File Transfer".
ROOT THE DEVICE
VI. Download and copy magisk_patched 10.0.8 international (global) into the ADB folder. Rename it to "modded-boot.img". Flash the modded-boot.img file to achieve temporary root. While the phone is turned on, in cmd type:
Code:
adb reboot bootloader
cd C:/adb
fastboot boot modded-boot.img
The device will reboot on its own once the process has completed.
VII. Download Magisk Manager and copy it to the phone's internal storage and use the native "Files" app to install the apk.
Launch Magisk Manager. Click "Cancel" on the "Requires Additional Setup" message.
Update "Manager" if using an outdated apk. Update "Magisk" via Direct Install and Reboot.
After the reboot, the device will retain root which can be verified using apps like Root Checker in the Play Store.
Someone who hasn't already tried converting their stock T-Mobile firmware to the OnePlus Internat'l firmware variant and is interested enough to follow these steps, please update me with your results after going through the process to confirm it was successful, I would greatly appreciate it.
If you have any helpful suggestions that could offer more insight or if there seems to be any holes or missing explanations within my instructions missing feel free to comment.
Kudos to @mauronofrio, without his tools none of this would be possible
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
dimelus said:
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
Click to expand...
Click to collapse
Okay, so this was MY experience. I did the MSM tool thing then started flashing the Global ROM. My phone did the same thing, and I panicked BUT my phone eventually booted into T-mobile's software. All I did was mash all three buttons to get back to the bootloader and flashed the Global firmware and it worked.
draymond1987 said:
Okay, so this was MY experience. I did the MSM tool thing then started flashing the Global ROM. My phone did the same thing, and I panicked BUT my phone eventually booted into T-mobile's software. All I did was mash all three buttons to get back to the bootloader and flashed the Global firmware and it worked.
Click to expand...
Click to collapse
But did you setup the phone, activated usb debug again? or you just power it off and go vol+/power to enter in recovery?
dimelus said:
But did you setup the phone, activated usb debug again? or you just power it off and go vol+/power to enter in recovery?
Click to expand...
Click to collapse
I immediately went back to the bootloader. I didn't set up the phone.
Also, power down + vol down. You'll get into the Chinese recovery. Then select the options to get into fastboot
draymond1987 said:
I immediately went back to the bootloader. I didn't set up the phone.
Also, power down + vol down. You'll get into the Chinese recovery. Then select the options to get into fastboot
Click to expand...
Click to collapse
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
dimelus said:
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
Click to expand...
Click to collapse
What I would do, and it's silly but could work. Go back into fastboot and issue the "
fastboot flashing unlock_critical" command, again. I know this happened to me too because I had these errors and I just tried, out of desperation. I dunno if it's because the phone is on the T-mobile software, that it freaks out like that, question mark?
dimelus said:
I'm trying all different guides to do this to my 7T.
After this step:
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
The phone just botted on T-Mobile rom... what should I do?
Click to expand...
Click to collapse
Did you not flash 10.0.3HD65AA rom image which is step "I."? If you go out of step and not follow the instructions as they're laid out then of course you're going to have problems.
urbanman2004 said:
If you purchased a OnePlus 7T which went on sale recently, but still aren't able to replace the T-Mobile firmware with the internat'l variant then you're in luck. I came across a few guides which were a smoking gun, but I was never fully able to get it to work successfully and "failed miserably". And a few posts I read helped spur some ideas and inspired me to think outside the box in order to come up with a much more predictable viable solution here. Throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. The instructions given were made with the expectation that you already have the bootloader unlocked and installed the necessary drivers with adb setup. I followed this guide here as point of reference which I think could be potentially bypassed by using this method instead to completely streamline the process. Best of all, I spent 15 hours yesterday trying to figure this out so hopefully you won't have to go through what I did. NOW LET'S BEGIN!!!
FLASH OPERATIONS
I. Just to give a little background for those of you who followed the guide I referenced, whenever I attempted to flash the 10.0.13-GLOBAL fastboot rom it would display the error message "Flashing is not allowed for Critical Partitions" multiple times then auto reboot T-Mobile logo splash screen, indicating that the process failed.
At this point, hold Vol Up + Power till the device shuts down and boot into fastboot.
On the PC, download the All In One v2.0.1.3 tool.
Download 10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT.zip or from here.
Open All In One v2.0.1.3 –> Flash Factory Images –> Browse directory for the fastboot rom –> check off "Wipe all data" and "Reboot after flash" –> Flash Rom.
During flash process, it will reboot once, NOT into fastboot, but stock recovery menu (FastbootD), and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.3HD65AA rom image.
II. Download and extract "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip" into a folder called "adb" in the root of the C: drive.
III. While the phone is turned on, we must boot into FastbootD. The fastbootD screen has the OnePlus logo centered at the top with 3 language choices. Run "cmd" as admin and type:
Code:
adb reboot bootloader
fastboot reboot fastboot
IV. Enter this command to check what version of Fastboot you've booted into:
Code:
fastboot getvar is-userspace
"Yes" means you're in FastbootD.
V. To flash the "10.0.13-GLOBAL" fastboot rom, run the bat script by entering these commands:
Code:
cd C:/adb
flash-all.bat
During flash process, it will reboot once into FastbootD again (stock recovery menu) and pick up where it left off and resume flashing the rest in which the process can be visible from the PC.
After completion, the device will be updated to Stock OTA 10.0.13HD65AA rom image.
Take the opportunity to perform a system update to Oxygen OS 10.0.15.HD65AA.
Enable developer mode: Go to Settings –> About phone (at bottom) –> tap Build number (towards right) until it says Developer Mode is enabled.
Go to Developer Options –> Enable USB Debugging and "allow". Go to "Default USB configuration" and change it to "File Transfer".
ROOT THE DEVICE
VI. Download and copy magisk_patched 10.0.8 international (global) into the ADB folder. Rename it to "modded-boot.img". Flash the modded-boot.img file to achieve temporary root. While the phone is turned on, in cmd type:
Code:
adb reboot bootloader
cd C:/adb
fastboot boot modded-boot.img
The device will reboot on its own once the process has completed.
VII. Download Magisk Manager and copy it to the phone's internal storage and use the native "Files" app to install the apk.
Launch Magisk Manager. Click "Cancel" on the "Requires Additional Setup" message.
Update "Manager" if using an outdated apk. Update "Magisk" via Direct Install and Reboot.
After the reboot, the device will retain root which can be verified using apps like Root Checker in the Play Store.
Someone who hasn't already tried converting their stock T-Mobile firmware to the OnePlus Internat'l firmware variant and is interested enough to follow these steps, please update me with your results after going through the process to confirm it was successful, I would greatly appreciate it.
If you have any helpful suggestions that could offer more insight or if there seems to be any holes or missing explanations within my instructions missing feel free to comment.
Kudos to @mauronofrio, without his tools none of this would be possible
Click to expand...
Click to collapse
Thanks for your guide lines.. I am a very newby yet 71 years old.. been messing with hardware and software since 1984, always learning. new to Flashing Rom's , I converted two 6T's and 3 7T from TMO to 1+, the third 7T gave me a fit, because I purchased from someone who didn't tell me that someone had tried to convert to dual sim and I had a hard time to solve the issue.. Two things,, for everyone trying to do this.. Branded to Global or Dual Sim, One You have to have the Correct Drivers for Windows for the ADB and Fastboot.. and it has to be setup correctly.. as for some drivers that are signature issue for windows, and you have exclamation mark because of signatures, as for Win10,
restart your windows with Shift key held down and select restart, when it boots into blue screen select "troubleshoot"
from that select " Startup blue secreen. " after that Select Item #7 which is to forces Windows to ignore Signature error reporting. select Start , then go on with your process for Brand to dual sim or Global, etc..
THANK YOU for Your Information and Procedure Steps to Convert from Branded to Dual / Global, etc.. made it very less time consuming...Appreciate You and All those who have given Good Guidance - Thank You
does this method unlock the sim card?
goggolar said:
does this method unlock the sim card?
Click to expand...
Click to collapse
No, you have a completely separate issue. The OnePlus 7T device I purchased already had an unlocked sim card. You need to refer to your phone carrier who provides you service.
It needs the bootloader unlocked?
SBruno said:
It needs the bootloader unlocked?
Click to expand...
Click to collapse
Yep
CaptRicXT912 said:
Gracias por sus lineamientos .. Soy muy nuevo por 71 años .. he estado jugando con hardware y software desde 1984, siempre aprendiendo. nuevo en Flashing Rom's, convertí dos 6T y 3 7T de TMO a 1+, el tercer 7T me encajó, porque le compré a alguien que no me dijo que alguien había intentado convertir a dual sim y tenía un Es difícil resolver el problema. Dos cosas, para todos los que intentan hacer esto. Con la marca Global o Dual Sim, una Debe tener los controladores correctos para Windows para ADB y Fastboot ... y debe estar configurado correctamente ... como para algunos controladores que son un problema de firma para Windows, y tiene un signo de exclamación debido a las firmas, como para Win10,
reinicie sus ventanas con la tecla Shift presionada y seleccione reiniciar, cuando se inicie en la pantalla azul, seleccione "solucionar problemas"
a partir de ahí, seleccione "Pantalla azul de inicio". Después, seleccione el elemento n. ° 7, que obligará a Windows a ignorar el informe de errores de firma. seleccione Inicio, luego continúe con su proceso de Marca a SIM dual o Global, etc.
GRACIAS por su información y procedimiento Los pasos para convertir de marca a dual / global, etc. hicieron que consumiera mucho menos tiempo ... Le agradezco a usted y a todos los que han dado una buena orientación - Gracias
Click to expand...
Click to collapse
seria de mucha ayuda si usted o alguien me ayudara en este problema estoy atascado en la version de android 10 de t-mobile la computadora no reconoce el dispositivo almenos que lo reinicie de fabrica, en modo fastboot no lo reconoce y estoy desesperado soy nuevo en esto
Excellent work, it did the job for mine. Followed your procedure and a couple of interpretations to get through it to the end.
Thank You for the help!
This worked for me, I wasn't even trying to convert my phone.. just restore a soft brick turned semi-hardbrick.
I haven't done android modding since my Zuk Z1! Previously I had modded my Galaxy s3, some LG [it was the one with RGB home button, man I miss that], and Z1. Yesterday I decided I was finally ready to mod my oneplus 7t [hd1907] after 2 years of ownership. Bootloader unlock, Rooted, modded some things, and then Sound wouldn't play in the speakers, wifi dead, hotspot dead, amongst other broken features. Trouble is, I wasn't thinking like I used to and didn't have my img files backed up. All I wanted to do was revert back to the stock firmware.. but I ended up in a softbrick somehow. I can't find tmo op7t firmware anywhere online.. I was going to try flashing it with adb.Well I came across your guide here, and when all hope was lost I thought I might as well give it a try.. and it worked! Now instead I'm on international software! Even better than just recovering stock! Well youtube is throwing a connection error but I am hoping it just means I need to update my gapps.. Thank you very much this helped me recover my phone..
dimelus said:
Did u have errors when flashing like:
FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS?
I just did what you said, power vol down and went again into the fastboot.
But there are some errors happing atm
Click to expand...
Click to collapse
I actually had "FLASHING IS NOT ALLOWED FOR CRITICAL PARTITIONS" on the first flash as well, and it never booted properly either. On the second flash I was getting "Invalid sparse file format at header magic".. However in the end of the process my phone was working.
I'm going to update gapps and update firmware to the latest OTA now, which popped up in the notifications already! Thanks again Urbanman.
Edit: "some LG [it was the one with RGB home button, man I miss that]" I checked my post history it was LG optimus G pro.
I now have the latest firmware for t-mobile 11.0.1.11. With the help of your method, can I flash the global firmware? Or do I need to first somehow lower the firmware version from t-mobile?
k.stahanov73 said:
I now have the latest firmware for t-mobile 11.0.1.11. With the help of your method, can I flash the global firmware? Or do I need to first somehow lower the firmware version from t-mobile?
Click to expand...
Click to collapse
Superboy58 msmtool will get u global oos10, then ota to 11.0.9.1 or oos12 global
HueyT said:
Superboy58 msmtool получит u global oos10, затем ota на 11.0.9.1 или oos12 global
Click to expand...
Click to collapse
I can not flash through msm .. at the fastboot stage after a reboot I ALWAYS boot into the old system !! always! already made 50 attempts and changed the cords and ports and no use!
Maybe it's because I have Windows 7?
Hello, first of all I want to apologize for any grammatical mistake since I do not speak English and this text was translated through a web page. Let's start, for a long time I came with emotions to try custom roms on my device (motorola moto g7 play ((XT1952-2)), I decided to try the lineageOs and to my surprise I managed to make it work, but I did not have the Gapps so I wore To investigate to install them, after investigating, I tried to install them but everything went wrong, very bad, the cell phone had been soft bricked and I was about 5 hours trying to solve it since the bootloader had been blocked and there was no way to install ANYTHING, After solving it, I found that I cannot install LineageOS in any way, I spent about 4 hours testing and it always throws me an error and this affects the entire device since I have to use the Motorola assistant on every failed occasion ( Rescue and Smart Assistant), I attach one of the problems that I get when trying to install the OS. I hope a prompt solution, thank you very much
Instalando archivo zip
Buscando archivo digest...
Step 1/2
Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)
Proceso Updater terminó con ERROR : 1
Error instalando archivo zip
Actualizando detalles de la particion
I tried in all the ways I could but did not reach any solution, I only use the stock motorola firmware, but the fact of installing a custom rom rejects it anyway.
ulisesgomez23 said:
Hello, first of all I want to apologize for any grammatical mistake since I do not speak English and this text was translated through a web page. Let's start, for a long time I came with emotions to try custom roms on my device (motorola moto g7 play ((XT1952-2)), I decided to try the lineageOs and to my surprise I managed to make it work, but I did not have the Gapps so I wore To investigate to install them, after investigating, I tried to install them but everything went wrong, very bad, the cell phone had been soft bricked and I was about 5 hours trying to solve it since the bootloader had been blocked and there was no way to install ANYTHING, After solving it, I found that I cannot install LineageOS in any way, I spent about 4 hours testing and it always throws me an error and this affects the entire device since I have to use the Motorola assistant on every failed occasion ( Rescue and Smart Assistant), I attach one of the problems that I get when trying to install the OS. I hope a prompt solution, thank you very much
Instalando archivo zip
Buscando archivo digest...
Step 1/2
Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)
Proceso Updater terminó con ERROR : 1
Error instalando archivo zip
Actualizando detalles de la particion
I tried in all the ways I could but did not reach any solution, I only use the stock motorola firmware, but the fact of installing a custom rom rejects it anyway.
Click to expand...
Click to collapse
Which recovery are you using? Twrp, or Lineage? it's not stock is it?
i use Twrp
Yes, I know about that application, I always use it when the phone throws me an error.
Let me explain, I have the bootloader unlocked so I connect the cell phone to the pc in fastboot mode and with a terminal I run "fastboot set_active a" to activate slot a, after this I use "fastboot boot <here I put the address where it is located the twrp recovery> "once started I go to wipe and delete dalvik, cache, data, and system, and after all this I go to install and look for my LineageOS.zip file and I proceed to install it, as soon as the installation begins, when the bar progress is 25%, the operation is canceled and I get the error that I mentioned before (Installing zip file
Searching for digest file ...
Step 1/2
Error applying update: 28 (ErrorCode :: kDownloadOperationExecutionError)
Updater process ended with ERROR: 1
Error installing zip file
Updating partition details)
After this the cell phone is without operating system so I have to use the motorola application (Rescue and Smart Assistant) to be able to recover my phone.
I want to clarify that the phone the first time I perform the steps everything worked perfectly, LineageOS was installed but when I turned it on first I got a black screen that said N / A and after a few seconds I started LineageOS, this I understand what happened due to that the OS was installed in slot b, but I have no idea, I can no longer flash any rom since it always gives me an error and there is nothing to solve it
This is a bit late but why not. THIS IS A COMPILATION OF ALL THE OS METHODS YOU NEED FOR THE OP8 Pro.
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 infected_
Magisk from topjohnwu
Gapps (Google Apps) from NikGapps. I recommend omni for ROMs that don't include Gapps.
Fastboot ROM for OP8Pro from mauronofrio
MSMDownload tools for OP*Pro 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 or ANY RECOVERY TOO
You need to have downloaded Platform Tools which the link is attached below.
Transfer the TWRP.img file into the platform-tools folder
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 Power + Vol + -> 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 flash recovery_a twrpname.img " file name (do twrp + press tab) and press enter
Then press enter and type this: fastboot flash recovery_b twrpname.img
Now choose to boot to recovery using the volume buttons
Enter the password and swipe to allow modifications
You have now installed TWRP and we've now checked that it has been successfully installed!
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
How to boot into EDL mode
This will have more than one method to boot into EDL mode.
Method 1
This is the basic method to boot into EDL mode
Turn off device
HOLD BOTH volume buttons
PLUG IN your device
Press the POWER button and CARRY ON HOLDING the volume buttons
You should be in EDL mode now
If your device still isn't in EDL mode try this
Open device manager in windows
Try the steps again
If not then try method 2
Otherwise, well done you have booted into EDL mode
Method 2
If you didn't manage to boot into EDL mode using method 1. If you can boot into system, do this method
Both methods will need you to download and install the All-in-one-tool from the download section
Go into developer options
Turn on USB debugging
Connect your device if u haven't
Press allow
Open the All-in-one-tool
Choose reboot EDL Mode
You should be in EDL mode now
Method 3
If you cannot boot into system and have bricked your device, try this method
This method uses TWRP to boot into EDL mode
IF U STILL CANNOT BOOT INTO EDL MODE and have bricked your device...
Install TWRP in the "How to install TWRP" section
Once you're in the home screen
Press reboot
Choose reboot to EDL
You should be in EDL mode now
Method 4
If you cannot boot into system and have bricked your device, try this method
This method will need you to download and install the All-in-one-tool from the download section
This method works if your on OOS or any ROM. Not after any failed attempt of wiping your device using MSM.
IF U STILL CANNOT BOOT INTO EDL MODE and have bricked your device...
Install TWRP in the "How to install TWRP" section
Once you're in the home screen, press reboot and choose the other slot (If ur current slot is Slot A then choose slot B and vice versa)
Reboot to system
If you're able to boot to the system
Skip the setup screen
Go into developer options
Turn on USB debugging
Connect your device if u haven't
Press allow
Open the All-in-one-tool
Choose reboot EDL Mode
You should be in EDL mode now
Installing a Custom ROM
Method 1
Follow the method suggested in the XDA thread. Stick to each method and follow the process!
If you want root and TWRP do this
Reboot to bootloader
Type: fastboot flash recovery_a twrpname.img
Then press enter and type this: fastboot flash recovery_b twrpname.img
Now boot to recovery
Find the magisk.zip file
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
This method uses TWRP and isn't suggested in XDA thread of ROMs. I have tested this method with CrDroid and it works. BUT you will need a usb c OTG device (a device that can connect to ur phone via USB C) as this method will wipe ur internal storage
Transfer TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Type: fastboot flash recovery_a twrpname.img
Then press enter and type this: fastboot flash recovery_b twrpname.img
Now boot to recovery
Flash Build.zip (Custom ROM zip file)
Flash 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
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
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 SUPER() for OOS! U CAN BUT IT COULD BREAK THE SYSTEM IF YOU RESTORE IT!
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 can restore DTBO, EFS, Modem, but DO NOT BACKUP SUPER()) RESTORING SUPER() breaks OOS
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 (You can restore DTBO, EFS, Modem, YOU CAN BACKUP SUPER()) BUT RESTORING SUPER() could break the ROM
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
To restore OOS use MSM. Fastboot was the fastest and easiest way if u have a TWRP backup. BUT it doesn't work from my testing and only MSM successfully works.
Update: Fastboot ROM currently don't work under my testing. MSM is still the best way to restore to OOS and TWRP backups don't currently work. I don't recommend trying to use the fastboot ROM installer for OOS as you would have file transfer issues...
As of now, use MSM and just transfer what you have backed up. It's sad that TWRP backups don't work, u can try and post how it went. But for now, I don't RECOMMEND RESTORING OR USING TWRP BACKUPS!
I use MSM Download Tool restore for that. It will reset everything and will lock the bootloader. So, it makes for switching/installing a custom ROM a bit annoying.
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 the MSM restore method. As they restore an old or different version of OOS!
Restoring using MSM Download Tool
Download latest MSM version
Extract/ un-zip
Click on MSM tool .exe file
Now we need to boot your device into EDL mode
Turn off device
HOLD BOTH volume buttons
PLUG IN your device IMMEDIATELY
Press the POWER button and CARRY ON HOLDING the volume buttons
If you cannot boot into EDL mode
Try the methods to boot into EDL mode in the "How to boot into EDL mode" section
Otherwise, carry on the method
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. Or u don't have a TWRP backup
Restoring OOS TWRP Backup
If you have a TWRP backup of OOS, follow this method to restore your system data.
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
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
Type "fastboot flash recovery_a twrpname.img " file name (do twrp + press tab) and press enter
Then press enter and type this: fastboot flash recovery_b twrpname.img
Reboot to recovery
Transfer whole TWRP Folder into internal storage
It is suggested to remove the SIM tray before you restore the TWRP backup and it can cause issues
Restore boot and data (You can restore DTBO, EFS, Modem, but DO NOT RESTORE SUPER())
Swipe to restore
Go to the next part to transfer your internal storage files + folders
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
You must remove your SIM tray before restoring the TWRP backup
Update: These methods were from my previous compilation guide for the Op6/6T. But as of now, TWRP backups aren't recommended for custom ROMs and I have only tested restoring TWRP backup for OOS. I haven't tested these methods myself nor know someone who has tested/recommends them for custom ROMs.
If u want to switch ROMs or unbrick your device I recommend using the MSM method in restoring with MSM section.
Restoring a Custom ROM TWRP backup 1
Restore fresh like you're going back to OOS.
Choose one method. Fastboot or MSM method.
I prefer the fastboot method.
Restore the device using MSM
Once booted into system, set it up briefly and DO NOT RESTORE ANYTHING.
Boot to bootloader
Type "fastboot flash recovery_a twrpname.img " file name (do twrp + press tab) and press enter
Then press enter and type this: fastboot flash recovery_b twrpname.img
Reboot to 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 to system. The first reboot might go dodgy and it did for me.
Reboot to system and transfer all your internal storage stuff
done
If this did not work still. Then do the next method...
Restoring a Custom ROM TWRP backup 2
If the previous method 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.
Restore the device using 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
Type "fastboot flash recovery_a twrpname.img " file name (do twrp + press tab) and press enter
Then press enter and type this: fastboot flash recovery_b twrpname.img
Follow the installation method suggested in the XDA thread for your ROM
Once it has been installed
Reboot to Recovery
Transfer twrp backup
Restore data
Reboot system. Done
If it still fails, repeat steps 1 to 18. 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
Update: As of now TWRP backups aren't recommended and haven't been tested, But this method works for updating OOS
Download the full zip file of the latest OOS, transfer the zip file to internal storage NOT IN ANY FOLDER
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 Home
Press install
Press install via inactive slot
Reboot system and done
You will reboot into the next slot
If you want TWRP do this
Reboot to bootloader
Type: fastboot flash recovery_a twrpname.img
Then press enter and type this: fastboot flash recovery_b twrpname.img
Now boot to recovery
Enter the password and swipe to allow modifications
You have now installed TWRP and we've now checked that it has been successfully installed!
Reboot to system and done
Otherwise, just reboot to system. Up to u
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
Follow the method suggested in the XDA thread. Stick to each method and follow the process!
Method 1
This method is for Custom ROMs that allows OTA updates and include GAPPS
Certain custom ROMs have this feature. Right now: Evo X
Go into settings, system update and press update
Wait till the installation has finished. If failed TRY AGAIN!
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
If you want TWRP do this
Reboot to bootloader
Type: fastboot flash recovery_a twrpname.img
Then press enter and type this: fastboot flash recovery_b twrpname.img
Now boot to recovery
Enter the password and swipe to allow modifications
You have now installed TWRP and we've now checked that it has been successfully installed!
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
This method is for Custom ROMs that allows OTA updates and don't include GAPPS
Certain custom ROMs have this feature. This method is for vanilla ROMs: CrDroid
Go into settings, system update and press update
Wait for the update to download and Press install
Wait till the installation has finished. If failed TRY AGAIN!
Press reboot
Done
If you want TWRP do this
Reboot to bootloader
Type: fastboot flash recovery_a twrpname.img
Then press enter and type this: fastboot flash recovery_b twrpname.img
Now boot to recovery
Enter the password and swipe to allow modifications
You have now installed TWRP and we've now checked that it has been successfully installed!
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 3
For Custom ROMs that don't have OTA updates.
Follow the method suggested in the XDA thread. Stick to each method and follow the process!
Before the last step which is to reboot to system...
If you want root and TWRP do this
Reboot to bootloader
Type: fastboot flash recovery_a twrpname.img
Then press enter and type this: fastboot flash recovery_b twrpname.img
Now boot to recovery
Enter the password and swipe to allow modifications
You have now installed TWRP and we've now checked that it has been successfully installed!
Reboot to system and done
Otherwise, just reboot to system. Up to u
Download Links:
All in one tool Here
SDK Platform Tools (Fastboot Tools) Here
OOS versions for OP8Pro (under Signed Flashable zips) Here
TWRP for OP8Pro Here
Magisk Here
NikGapps Here
MSMDownloadTool for OP8Pro Here
TitanumBackup App Here
Migrate App Here
Credits:
@infected_ For your amazing work on the TWRP recovery and method to install TWRP
@osm0sis For your amazing work on developing a version of TWRP that allows flashing
@mauronofrio All in one tool
@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 OP8Pro
@BillGoss For his help to restore TWRP backup on the 8/8T Series
First Comment
Updates
21/10/21 - Released the XDA thread that is a compilation of all methods you need for the OP8 Pro
Not sure about the OP8 sadly as I don't own one and this is a very early version of the XDA thread...
I currently don't have my OP8 Pro yet, but I'll be getting it tomorrow and this guide will definitely help me and many people
24/10/21 - Updated the XDA thread as some methods won't work and haven't been specifically tested for the OP8 Pro
I would require testing, but can't risk my device...
Fastboot ROM by Mauronofrio don't work and only recommended way is using MSM
Added how to boot into EDL mode methods
Crossed out methods that aren't recommended and need testing
23/12/21 - Added method 2 for installing a custom ROM using twrp
Added a link to download the .img and .zip files
13/1/22 - Updated section for Restoring OOS TWRP Backup in Restoring OOS and Custom ROM section
I have tested and successfully restored my boot and data on OOS
29/01/22 - Updated section for booting into EDL mode
Added a new method and changed it to method 3
Changed the previous method 3 to method 4 due to the fact that the method only works if the user has an OS installed. Not if the user did a failed attempt of wiping the system with MSM
31/01/22 - Added credit for BillGoss for his help on finding a method to restore TWRP backups for 8T which works on the 8/8 Pro.
Updated method on restoring TWRP backup for OOS. Made it clear which partition is safe to restore and which isn't
19/02/21 - Something caught my attention on updating custom ROMs... Specifically vanilla ROMs with no gapps.
Added new Method 2 in the Update a custom ROM section and replaced old Method 2 as Method 3
25/03/22 - Updated backup methods for OOS and Custom ROMS
OP8 Pro doesn't have separate system and vendor partitions. Only SUPER() which breaks on OOS.
Updated Backing up on OOS and Custom ROM methods in Backing Up OOS and Custom ROM section.
This could help some people. Thank you.
xtcislove said:
This could help some people. Thank you.
Click to expand...
Click to collapse
It can be quite annoying trying to find methods for different things in terms of installing updating and looking at different websites. Why not just compile them in one XDA thread
Nice guide , Thank you.
OnePlus 8 Pro 256GB RAM Device
OS: OxigenOS 11.0.10.10IN11BA
Rooted device with Magisk 23.0 installed
Good evening
I would like to know if I can install TWRP on my device without losing any data (apps, data, etc.) because my device is in "BOOTLOADER" mode open all the time?
I spotted the version of TWRP for OxygenOS 11 which is: "twrp-op8-3.6.0_11-infected-b5.img" with the following XDA link:
[TWRP][3.7.0-13][instantnoodle]TWRP for OnePlus 8/8Pro ][OFFICIAL][BETA 3]
TWRP for OnePlus 8 and 8 Pro TWRP is an open source, community project. TWRP development is done by a large support community with many people who are willing to answer questions and help people with their devices either through our IRC...
forum.xda-developers.com
On the other hand, this method of installing TWRP removes the Magisk app and the root of the device if I understood correctly and you have to install Magisk again with TWRP and the file “Magisk-v23.0.apk renamed to “Magisk-v23.0.zip”
Finally, is it possible to perform full "Nandroid Backup" backups and restore these backups, as can be done with a Samsung S7 device for example?
I send you all my congratulations on all your work and all your explanations.
Thanks in advance for your advice on installing TWRP!!
Good evening, best regards,
Jean-Noel
nadnan said:
OnePlus 8 Pro 256GB RAM Device
OS: OxigenOS 11.0.10.10IN11BA
Rooted device with Magisk 23.0 installed
Good evening
I would like to know if I can install TWRP on my device without losing any data (apps, data, etc.) because my device is in "BOOTLOADER" mode open all the time?
I spotted the version of TWRP for OxygenOS 11 which is: "twrp-op8-3.6.0_11-infected-b5.img" with the following XDA link:
[TWRP][3.7.0-13][instantnoodle]TWRP for OnePlus 8/8Pro ][OFFICIAL][BETA 3]
TWRP for OnePlus 8 and 8 Pro TWRP is an open source, community project. TWRP development is done by a large support community with many people who are willing to answer questions and help people with their devices either through our IRC...
forum.xda-developers.com
On the other hand, this method of installing TWRP removes the Magisk app and the root of the device if I understood correctly and you have to install Magisk again with TWRP and the file “Magisk-v23.0.apk renamed to “Magisk-v23.0.zip”
Finally, is it possible to perform full "Nandroid Backup" backups and restore these backups, as can be done with a Samsung S7 device for example?
I send you all my congratulations on all your work and all your explanations.
Thanks in advance for your advice on installing TWRP!!
Good evening, best regards,
Jean-Noel
Click to expand...
Click to collapse
That version of twrp is fine and no, installing twrp doesn't remove magisk so u don't have to reinstall it.... There is a method on how to install TWRP as well. For TWRP backups, it's suggested to remove the SIM tray before restoring the backup. I have updated the guide as I have successfully managed to restore a TWRP backup of OOS. So, I have added a method on how to do that.
Only restore boot and data. U can restore DTBO and EFS too, but I honestly can't tell the difference before and after restoring these partitions. U cannot restore Persist as it is a critical partition in the system. From my testing, DO NOT RESTORE SUPER (SYSTEM.IMG, VENDOR.img, ETC)! as this will BRICK YOUR DEVICE! I have tried this from my testing and it doesn't work! But only restoring the other partitions except for persist works fine
Thank you very much for your quick feedback.
My "rooted" Oneplus 8 allows me to use the "Swift Backup" application which makes a complete backup of applications (;apk), data, but also all system settings.
I only used the restore of apps with their data and cfelma works very well.
The TWRP function only serves, for me, to perform a "nandroid backup" image. Is it useful to set up TWRP in this sole objectiof?
The manipulations to perform backups and then, possibly, restores, seem much more complicated to me than my operations carried out years earlier with two Samsung S7 or S7 Edge devices!!
Best regards
Jean-Noel
TWRP can also flash/install magisk to grant root as well. U should still have a nandroid backup like swift may be able to restore app and settings once set up ur device like new again then u have to restore everything manually. With a nandroid backup u restore the boot and data that isn't in the internal storage. After restoring it, boot to system and there'll be nothing else to restore other than ur internal storage files and the system, settings, apps, wifi and security will be there like u never left (password will be removed, but u just need to add a new one and fingerprints + face unlock will be restored). Swift backup can't do that, just keep hold of ur boot, dtbo, efs, persist and data partitions of the TWRP backup and have a copy of it in a storage device in case
Extreme_Ninja2099 said:
TWRP peut également flasher/installer magisk pour accorder également root. Vous devriez toujours avoir une sauvegarde nandroid comme Swift peut être en mesure de restaurer l'application et les paramètres une fois que vous avez configuré votre appareil comme neuf, puis vous devez tout restaurer manuellement. Avec une sauvegarde nandroid, vous restaurez le démarrage et les données qui ne se trouvent pas dans le stockage interne. Après l'avoir restauré, démarrez sur le système et il n'y aura rien d'autre à restaurer que vos fichiers de stockage internes et le système, les paramètres, les applications, le wifi et la sécurité seront là comme si vous ne l'aviez jamais quitté (le mot de passe sera supprimé, mais vous avez juste besoin pour en ajouter une nouvelle et les empreintes digitales + reconnaissance faciale seront restaurées). La sauvegarde rapide ne peut pas faire cela, gardez simplement vos partitions de démarrage, dtbo, efs, persist et données de la sauvegarde TWRP et ayez-en une copie dans un périphérique de stockage au cas où
Click to expand...
Click to collapse
Extreme_Ninja2099 said:
TWRP can also flash/install magisk to grant root as well. U should still have a nandroid backup like swift may be able to restore app and settings once set up ur device like new again then u have to restore everything manually. With a nandroid backup u restore the boot and data that isn't in the internal storage. After restoring it, boot to system and there'll be nothing else to restore other than ur internal storage files and the system, settings, apps, wifi and security will be there like u never left (password will be removed, but u just need to add a new one and fingerprints + face unlock will be restored). Swift backup can't do that, just keep hold of ur boot, dtbo, efs, persist and data partitions of the TWRP backup and have a copy of it in a storage device in case
Click to expand...
Click to collapse
Thank you very much for your information.
I use the Google translator to translate your information into French but I do not fully understand the translation of your message:
- The installation of TWRP does not delete any data from my device and I will not need to redo all the settings already installed: Wifi connection with the Box, applications with data, Nova app settings for example, the phone call log, SMS-MMS, WhatsApp, etc. will not be deleted: is that right?
- Installing TWRP does not remove the root of the device with Magisk in place: is that right?
- Are there particular parameters to indicate to perform 1 “Nandroid Backup” with TWRP?
- Are these the same parameters to be saved as in the attached image made with a Samsung S7 Edge device?
- Does 1 "Nandroid Backup" made with TWRP restore the entire backup, such as an image of a partition made with Acronis True Image on Windows, for example?
- If this is not the case, what should be given as parameters?
- If I understand correctly, if the device is password protected, this password is removed by restoring "Nandroid Backup"?
- All applications, data, messaging settings, Wifi connection with Box, call log, SMS-MMS, WatsApp and others are restored with the "Nandroid Backup)?
- Can “OTA” updates be installed as I can each time an update is notified to me with the “Oxygen Updater” app?
I'm sorry for all these questions but I would like to take advantage of your experience without risking damaging my device which has been working perfectly since it was purchased in October 2020 and which is just rooted, starting with a full version of OxygenOS 10, then OxygenOS 11 and finally all the OTA updates offered by OnePlus.
Again, thank you very much for your help and advice...
Best regards,
Jean-Noel
nadnan said:
Thank you very much for your information.
I use the Google translator to translate your information into French but I do not fully understand the translation of your message:
- The installation of TWRP does not delete any data from my device and I will not need to redo all the settings already installed: Wifi connection with the Box, applications with data, Nova app settings for example, the phone call log, SMS-MMS, WhatsApp, etc. will not be deleted: is that right?
- Installing TWRP does not remove the root of the device with Magisk in place: is that right?
- Are there particular parameters to indicate to perform 1 “Nandroid Backup” with TWRP?
- Are these the same parameters to be saved as in the attached image made with a Samsung S7 Edge device?
- Does 1 "Nandroid Backup" made with TWRP restore the entire backup, such as an image of a partition made with Acronis True Image on Windows, for example?
- If this is not the case, what should be given as parameters?
- If I understand correctly, if the device is password protected, this password is removed by restoring "Nandroid Backup"?
- All applications, data, messaging settings, Wifi connection with Box, call log, SMS-MMS, WatsApp and others are restored with the "Nandroid Backup)?
- Can “OTA” updates be installed as I can each time an update is notified to me with the “Oxygen Updater” app?
I'm sorry for all these questions but I would like to take advantage of your experience without risking damaging my device which has been working perfectly since it was purchased in October 2020 and which is just rooted, starting with a full version of OxygenOS 10, then OxygenOS 11 and finally all the OTA updates offered by OnePlus.
Again, thank you very much for your help and advice...
Best regards,
Jean-Noel
Click to expand...
Click to collapse
Uh idk what u are going on about now... Like this specifically for the OnePlus 8 Pro not S7 Edge... Best to ask in the XDA forum for the S7 Edge. I'm pretty sure I've answered all your questions by now and everything you need to know is in the guide or in my replies
I was just doing a comparison to see if a "Nandroid Bacqup" of a One Plus 8 Pro device with TWRP is the same as the backup made by TWRP for a Sansung S7 Edge device.
I also wanted to know if the restoration was identical between the two devices already mentioned with TWRP.
I'm well advised to go to a forum attributed to the S7 Edge if I need to, but it's not!!
I'm having "buyer's remorse" after trying OOS12. Is it possible to boot back to the other slot? Unless 12 did something I assume it still has OOS11 on it. Probably not though as I haven't seen it mentioned as a downgrade option anywhere. Things have really gotten complicated in the last few years when it comes to this dance.
Hi
I have OOS 11.0.11.11.IN11BA, rooted with Magisk 23.0
And I want to update OOS
The new version in the system update is IN2023_11.C.16_1160_202204222258
I followed the instructions,
downloaded the zip file (with oxygen updater)
(oneplus8prooxygen_15.e.16_ota_1036_all_2204222258_57eced36.zip)
updated via local upgrade
installed Magisk to inactive slot
rebooted
But after the reboot, it still says that there is a system update
Tried also without local upgrade, directly from system update app, again the same.
Any idea?
Hello
OnePlus 8 Pro with OxygenOS IN2023_11_C.15
I installed the “OnePlus8ProOxygen_15.E.15_OTA_1032_all_2204021901_1b9e6.zip” file on April 22 and I set it up by following the following tutorial:
How to Install OTA Updates on Rooted Android Devices using Magisk [Without Losing Root]
An OTA update has arrived, but you cannot install it because your Android device is rooted? Well, that's a known downside of rooting Android. In this guide, you will learn how to install OTA updates…
www.thecustomdroid.com
I follow this procedure for all OTA updates since OxygenOS 10 without any difficulty.
I haven't downloaded the "oneplus8prooxygen_15.e.16_ota_1036_all_2204222258_57eced36.zip" file yet, so I can't tell you what it says next for persistent update reporting.
I think I will perform this very recent update tomorrow and I will inform you of the indications that I can observe.
Best regards
Good evening
I just performed the OTA update just now with the update installation offered in the device settings while following the tutorial that I told you previously.
I did not use the file “OnePlus8ProOxygen_15.E.15_OTA_1032_all_2204021901_1b9e6.zip”
Everything went well and the smartphone is now in version IN2023_11_C.16
The Oxygen Updater application indicates that the system is up to date.
Software update in system settings does not show an update to install.
Have a good evening.
Best regards
nadnan said:
Good evening
I just performed the OTA update just now with the update installation offered in the device settings while following the tutorial that I told you previously.
I did not use the file “OnePlus8ProOxygen_15.E.15_OTA_1032_all_2204021901_1b9e6.zip”
Everything went well and the smartphone is now in version IN2023_11_C.16
The Oxygen Updater application indicates that the system is up to date.
Software update in system settings does not show an update to install.
Have a good evening.
Best regards
Click to expand...
Click to collapse
thank you for your reply
which version of magisk do you have?
This is the latest version currently available...