Develop Bugs

My problems with ICS

My problems with ICS are:
1.- Wifi don't work fine, tested with a, b, g, and n and nothing..... works when it want
2.- brigthness changes without my permission
3.- sometimes touchscreen fail
4.- I can't downgrade to Honeycomb (3.2.80)
Heeeelp please.

Vicente said:
My problems with ICS are:
1.- Wifi don't work fine, tested with a, b, g, and n and nothing..... works when it want
2.- brigthness changes without my permission
3.- sometimes touchscreen fail
4.- I can't downgrade to Honeycomb (3.2.80)
Heeeelp please.
Click to expand...
Click to collapse
Hi !
If you want you can downgrade to Honeycomb ....after install Root ICS version , you need to copy archos.ext4.update into your device and into SDE recovery copy zImage and initramfs appropriate ..ext4.update ...now you can install Original Archos Firmware .aos appropiate your version of downgrade !
Good luck !

surdu_petru said:
Hi !
If you want you can downgrade to Honeycomb ....after install Root ICS version , you need to copy archos.ext4.update into your device and into SDE recovery copy zImage and initramfs appropriate ..ext4.update ...now you can install Original Archos Firmware .aos appropiate your version of downgrade !
Good luck !
Click to expand...
Click to collapse
I'm not so sure, recover ydid change in ICS.
But you should be able to run Honeycomb- rename 3.2.x initramfs.cpio.gz to initramfs.cpio.lzo (ICS recovery requires initramfs to be named initramfs.cpio.lzo, content is the same)

Ok, Thanks......
Tomorrow flash it
Thank you again

gen_scheisskopf said:
I'm not so sure, recover ydid change in ICS.
But you should be able to run Honeycomb- rename 3.2.x initramfs.cpio.gz to initramfs.cpio.lzo (ICS recovery requires initramfs to be named initramfs.cpio.lzo, content is the same)
Click to expand...
Click to collapse
Hi!
Of course ! you are right ...I missed this thing ...Thanks !

How did you do it have you a tutorial and download link because i have tried several honeycomb but it dont work for me to go back to honeycomb
Device archos 80 g9 1 ghz

stapbeest said:
How did you do it have you a tutorial and download link because i have tried several honeycomb but it dont work for me to go back to honeycomb
Device archos 80 g9 1 ghz
Click to expand...
Click to collapse
1. Download custom/rooted Honeycomb firmware
2. Extract files on pc
3. Copy archos.ext4.update to storage
4. Rename initramfs.cpio.gz to initramf.cpio.LZO
5. Boot to Recovery
6. Select Reset Android (I don't think that ICS files will suit for Honeycomb)
7. Select Flash Kernel (use zImage and initramfs.cpio.lzo)
8. Reboot and enjoy
tapatalked from Desire

Thanks give it a try tonight i didnt do the reset android step and after that i can flash origenel honeyice but i dont have to delete android kernel.

I have tried it as your tutorial but everytime i get not futher than de archos boot logo and with custom rom a bootloop this is wat i do
reformated device
install original firmware
then root and install sde and unistall pauls root
copy ics root ext4 update to internal storage
reboot in sde
select recovery system
format system
reset android
then go back to developer and install kernel
reboot to original firmware (because he dont let you direct boot in developer)
shut down en in sde select developer edition
then al the same with a 3.2.80 root
then nothing only bootscreen i have waited half een hour
what i am doing wrong most i also delete android kernel?

gen_scheisskopf said:
1. Download custom/rooted Honeycomb firmware
2. Extract files on pc
3. Copy archos.ext4.update to storage
4. Rename initramfs.cpio.gz to initramf.cpio.LZO
5. Boot to Recovery
6. Select Reset Android (I don't think that ICS files will suit for Honeycomb)
7. Select Flash Kernel (use zImage and initramfs.cpio.lzo)
8. Reboot and enjoy
tapatalked from Desire
Click to expand...
Click to collapse
This procedure works for me.... I'm with HoneyComb again
1. Download custom/rooted Honeycomb firmware
2. Extract files on pc
3. Copy archos.ext4.update (524.288 KB) to storage
4. Rename initramfs.cpio.gz to initramf.cpio.LZO
5. Boot to Recovery
6. Select Reset Android
7. Select Flash Kernel (use zImage and initramfs.cpio.lzo)
8.- Reboot and enjoy ------ You must reboot in developer mode.

After installing kernel i can only choose reboot in sde so he first boots normal android or is there a trick to direct reboot in developer or a button combo for that

stapbeest said:
I have tried it as your tutorial but everytime i get not futher than de archos boot logo and with custom rom a bootloop this is wat i do
reformated device
install original firmware
then root and install sde and unistall pauls root
copy ics root ext4 update to internal storage
reboot in sde
select recovery system
format system
reset android
then go back to developer and install kernel
reboot to original firmware (because he dont let you direct boot in developer)
shut down en in sde select developer edition
then al the same with a 3.2.80 root
then nothing only bootscreen i have waited half een hour
what i am doing wrong most i also delete android kernel?
Click to expand...
Click to collapse
- Why uninstall pauls root?...... You must be root for this procedure.
1.- Install SDE Developer (Pauls Root)
2.- Reformat Device
3.- Install ICS (official)
4.- Copy to data/media archos.ext4.update to storage (Surdu Petru, 5xx.xx KB)
5.- Reboot in Recovery
6.- Select Reset Android
7.- Select Flash Kernel (use zImage and initramfs.cpio.lzo, remember rename initramfs.cpio.gz to initramfs.cpio.lzo )
8.- Reboot as Developer edition
Optional.....For permanent Root, in second reboot delete kernel
Good luck

After installing kernel i can only choose press on/off button to reboot and then the device reboot only in original firmware i cant choose reboot in developer mode or most i press de volume up and power down to go direct back in sde or is there another way.

stapbeest said:
After installing kernel i can only choose press on/off button to reboot and then the device reboot only in original firmware i cant choose reboot in developer mode or most i press de volume up and power down to go direct back in sde or is there another way.
Click to expand...
Click to collapse
In Developer Edition menu choose Remove android kernel- device will boot only to SDE (official firmware will not be accessible until you flash .aos update again)
tapatalked from Desire

Oke so first reset android then remove android kernel and then flask kernel i gonna try this tonight.

thanks all for your help i finally have honeycomb thank you thank you
Keep up al the good work
Greetings
Stefan

also the external keyboard is n/w

have you see that
http://forum.xda-developers.com/showthread.php?t=1549611

[ROOT] tutorial for root Bluboo S8 with TWRP

As promised, here is the tutorial to root the bluboo s8 with TWRP and even install alternative roms via TWRP.
As always, you do this at your own risk, I am not responsable in case of brick of your smartphones.
This way of installing TWRP is accurate and works with the version V11 of NEEDROM and V14 official ROM. I did not try with the classic factory ROM.
UPDATE 28 NOV 2017 : Added trick (in the procedure) to force the phone to keep TWRP and not restore the original recovery.
Step 1: Prepare your PC
First DON'T USE THE ORIGINAL BLUBOO USB CABLE. Use only a USB-C cable from another smartphone or a universal cable. and in a USB 2 plug. The original bluboo s8 cable does not work properly.
- Download the ROM V11 on NEEDROM : Official V11 ROM for Bluboo S8
- Decompress it and open scatter file with a text editor. Change value MT6755 with MT6750 if needed
- Download TWRP : Twrp version for bluboo s8
- Decompress it and rename recovery(1).zip to recovery.zip
- Delete the file mt6750_androidscatter.txt
- Edit the file MT6755_Android_scatter.txt and change the line "platform: MT6755" to "Platform: MT6750" and save it. Rename this file to MT6750_androidscatter.txt
- Download SP FLash Tools here : last version
- If it's not done yet, install the android drivers. (search on Google)
- Install ADB drivers and utilities in a directory /ADB (see google, they are everywhere)
- Download the latest supersu .zip here : SuperSU last version
Step 2, if needed : Install the ROM stock V11 20170815
- Put your Bluboo in developer mode: Go to "settings" then "About" and then click on "build version" several times.
- Enable USB debugging: In developer tools
- Now you have to turn off the smartphone
- Launch SPFlash tools then load the V11 ROM into it
- Go in upgrade mode, not in dowload mode (Dont choose format all ! ! ! ! !)
- Clic on Download button
- connect cable and Start bluboo s8
- After flash done, reboot smartphone
Once the rom is installed, pass it also in developer mode as already done previously.
(you can, if you want, make all OTA updates before doing the rest tutorial ..)
Step 3 : Install TWRP
note that with this method, you don't need to unlock the bootloader.
- Copy the file supersu.zip in the root of the smarpthone
- Launch SPFLASH TOOLS and put the modified MT6750_androidscatter.txt on it.
- Check that there is only "recovery" checked
- Make sure the recovery points to the recovery.img file of the TWRP folder
- SPFLASH Tools must be in "download only" mode
- Click on Download
- Open a command window and go to your ADB directory
- Type ADB DEVICES. (if needed, confirm in the bluboo screen)
- If all is ok, Prepare the command line: "ADB reboot recovery", but do not validate it
- Reboot the smartphone.
- Spflashtools will flash recovery with TWRP
(update of 28 nov here)
- After flashing the recovery, remove the USB cable, press volume- and reconnect the cable to reboot in android-test-mode (or After flashing the recovery, for first reboot, press VOL- and ON to go to the test page of the smartphone) to prevent the smartphone from loading the system and returning the original recovery.
When you are in the test page (a line with chinese caractere), type ADB REBOOT RECOVERY and TWRP is loading.. (works really all times)
- The phone reboot in recovery mode and TWRP appears. (The launch of TWRP can take a little time, do not panic)
- In TWRP, start installing superSU as usual.
- Once installed, reboot the smartphone (without installing utility, if it offers it)
- The phone restarts and is rooted 
- From now on, TWRP is really installed in recovery on your smartphone, so you can install custom roms with.
To go in recovery mode, go to adb and type "ADB Reboot Recovery". that else.
information :
I repeat: This method works without unblocking the bootloader.
Anyway, the vol + key does not work in fastboot mode with bluboo s8, so only a method without unlocking is possible. My method is adapted.

So step 4 can't be done normally!?! I mean without doing step 1 and 2 ?!? Besides I tried to unlock my bootloader, did everything correctly, but I got stuck on "CHOOSE VOLUME UP TO UNLOCK BOOTLOADER in mobile screen "
Coz if I press volume up nothing happens?!? Only volume down work, that to cancels the whole process . Plz clarify and explain..

I have the same problem with the locked boot loader. I can't pres Vol Up , only Vol Down.

Personally I did not need to unlock the bootloader so ..
Technically, by following the tutorial in order, there is no need to unlock the boot loader. I know that only a few bluboo s8 have unlocked ok (with the line "unlock bootloader" active in "developer option" menu), all the others have the volume + which does not work.
Anyway the unlocking of the bootloader is not useful here. Do not forget that you must be in Rom v11 !
And the photo of my bluboo s8 with twrp :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Tested today, the leegoo s8 ROM ported, installed with TWRP and result is wondefull ....
Much better thought than the original rom of the bluboo, lighter .. Top!
This is screen capture of the phone state :

Hello fanfan7110,
apparently you're French, so am I. Are DRMs implemented in the Leagoo ROM? Do Molotov Tv and Mycanal applications work?
thank you

Hello,
I tried the tuto but it doesn't work. When I reboot in recovery, there's an android down with a red sign and it says no command. I tried several times and it's always the same...

When you get dead android press volume up+ power.The v.11 stockrom did notvwork for me.Spflashtool gave erfors.I found another stockrom from september on a russian site that worked.No need to adb reboot recovery descriebed here just do it with the phone turned on an you will get the dead android.Power + volume up gets you into twrp.

Hello,
Thank you for your answer, I'll try that as soon as I can.

After you root the device can we make update the roms to go back to V20 ? or we stuck on the V11 without the update . i try so many time to root and remove the initiator app to have the launcher i want ,without luck .
---------- Post added at 03:10 PM ---------- Previous post was at 03:10 PM ----------
samot4 said:
When you get dead android press volume up+ power.The v.11 stockrom did notvwork for me.Spflashtool gave erfors.I found another stockrom from september on a russian site that worked.No need to adb reboot recovery descriebed here just do it with the phone turned on an you will get the dead android.Power + volume up gets you into twrp.
Click to expand...
Click to collapse
where did you find the roms ? can you copy the link here please ?

I have sent you a message with the link.
I installed Elephone rom ported for Bluboo s8.Its clean from adware and works better then the stockrom.Its not roted but thats easely done with twrp.

note that the bluboo s8 don't work well in USB 3.0. You need to use a USB 2.0 and a compatible Cable (not the official)

for those who do not manage to keep TWRP, I explained in the first step how to do it (you have to launch the command in ADB, to prevent it from rebooting completely.) If it reloads the system first, it replaces twrp)

if i can do it , you can do it too

I put my bluboo in the original rom to redo the procedure and check that everything works as expected.
I put my twrp back in again. But for those who can not flash the twrp and keep it, I added a solution at the end of the post.
This trick works because I did it live again a few seconds ago ..
It's your turn !

Hello,
I managed to install the TWRP recovery but the problem is that the phone always restarts in recovery! No way to start the system!
Do you have a solution for that?
Thank you

After flashing the recovery, remove the USB cable, press volume- (NOT VOL+) and reconnect the cable to reboot in android-test-mode[/B (a line with chinese caractere)] (or After flashing the recovery, for first reboot, press VOL- and ON to go to the test page of the smartphone) to prevent the smartphone from loading the system and returning the original recovery.
When you are in the test page (a line with chinese caractere), in the adb window type ADB REBOOT RECOVERY and TWRP is loading.. (works really all times)
- The phone reboot in recovery mode and TWRP appears. (The launch of TWRP can take a little time, do not panic)

Yes, I managed to do that. The phone restarted in recovery. I installed SuperSU, the phone to restarted normally on the ROM and it was well rooted. Then I wanted to reboot and since it reboot only in recovery, I can't reboot the ROM anymore.
---------- Post added at 03:38 PM ---------- Previous post was at 02:44 PM ----------
It's finally good I did it all over again and now it works!
Thank you very much for this tuto

Bloqué twrp
Bonjour Fanfan, et meilleurs voeux pour 2018.
j'ecris en francais car j'ai du mal en anglais et j'ai vu que vous etiez francais.
Mon bluboo s8 reste bloqué sur twrp suite a une tentative de root avec un logiciel dedié.
Il ne veut pas booter apres flashage de la rom; impossible d'avancer; Auriez vous une piste ou une solution?
Merci de votre réponse.

Bonjour,
J'ai eu le même problème. Il faut reflasher la ROM stock avec Flastool pour que le téléphone redémarre normalement.
Ensuite il faut suivre exactement le tuto de fanfan7110 et pour moi ça a fini par fonctionner...

T-Mobile OnePlus 7T Internat'l ROM Version Conversion – Guaranteed Method That Works If All Else Fails

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?

Installing, Updating, Backup and Restore Guide for OP8 Pro

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...

TWRP + LineageOS boot loop?

Heya guys,
I did get TWRP + LineageOS 18.1 working on this tablet a few months ago, and have been enjoying it (along with Magisk + google apps).
I had to use Odin, since no other method worked - but I had to borrow a laptop for that (since I don't use Windows, and the Linux apps didn't work at all).
Since LineageOS 19.1 was released, I thought I would give the upgrade a try, and also the backup + restore method a try for TWRP (must be tried + tested right? .. Or so I thought).
So, I get a USB drive, exfat formatted, double the size of the internal storage.
I backup all partitions except for "Dtbo", "cache", "EFS" (so all the stuff that might be touched by a potential patching I wanted backed up)..
Data, I also renamed the "media" to "mediabak" and backed that up - so that I wouldn't lose any media files either.
I then "install"ed the LineageOS 19.1 zip file using the TWRP "install" button.... Cleared the cache, aaaaand got the LineageOS boot animation and then just continual reboot...
5 reboots later, I boot into TWRP: "no worries - I shall restore from my backups!" I say to myself.
I restore everything except the "data" partition, thinking "it's OK, it's only data and it'll save me time restoring that"
... NOPE! - reboot and now I just get continual reboots but no boot animation.
"Maybe I need to wipe them before hand?" - so I select to wipe the partitions (vendor, system, cache, ...).. Only data+recovery not being wiped.
Restore
.... NOPE!
"Let's try data - maybe there's something funny in there?"
.... NOPE! - and what's worse, I get a tar extraction error (255) - probably due to the fact the partition isn't encrypted (as a guess) - I found a webpage showing the "data" files in the backups are only tar files, and on my laptop they show as OK except for having some missing "TWRP.security.encrypt" and something about a missing equals sign on the extended metadata (so I think the data is all intact, so I can probably transfer / extract it after I get the tablet back).
"Let's just try to re-install LineageOS 18.1 from the images... Wipe system, grab the image from the net, use TWRP to 'install' the image"
.... NOPE! - still stuck with a boot loop.
Why will TWRP not install the OS properly?
How can I trust TWRP after this, with no ability to restore things?
What am I missing here, since there's no logs or errors for me to check I'm flying blind here and fairly annoyed at the fact that something so simple (essentially extracting files and running a few scripts for a 'normal' upgrade run) is failing so hard.
... Can anyone point me in the right direction?
--
Paul_one

*UPDATE*
So, I've got a semi-update:
I' was able to use Odin again to flash stock ROM, then re-flash vbmeta.tar, then re-flash recovery, then re-flash lineageOS 19.1
19.1 looks AWEFUL on first boot, nowhere near as 'refined' as 18.1 (using a scroll window center aligned makes me thing of old HTML from the late 90s before CSS).
Anyway, so I am able to boot into LineageOS 19.1 .. If I restore the "system_image" and wipe the data partition (clicking the 'wipe data' button) it allows me to also boot into 18.1 .. GREAT ....
...Except...
I still cannot restore the data partition using TWRP.
Still errors with a "extractTarFork()" error, code 255 .
The tars look "fine" on my Linux machine, and extract with only missing extended metadata errors.
I wrote a script to extract the tar files and run it in the TWRP terminal - it errors about file duplicates (no metadata errors).
I see that this is actually due to a character length limit on the filenames.
One sub-directory it tries to extract (sessions) is shortened (to 'session') and all files within it are extracted as the new shortened directory name... Meaning that it tries to delete a file (which it cannot since it's a directory) and write the file (which it cannot since the directory exists with that name)!
How is this possible when ALL android pathnames are disgustingly long. How has this not been seen before and why is this so cr*p?
There's 2 other 'tar' files (sym-links to 'toybox' - which I assume is a busybox clone) which are a different size to the normal one in the PATH... So I'm going to try those, but I'm a little lost as to how effective this will be, and I'm AMAZED that these errors aren't coming up on any google search since it seems it's broken from the foundational commands!
... How this ever backed up 'correctly' in the first place I will never know - but I'll never trust TWRP to 'backup' my data partition again..
--
Paul_one

Further update:
I progressed with the boot of the system to include a user account and put a decryption pattern on.
After rebooting, ensuring the "wiping" method was "rm -fr" in the settings, I was able to restore from the TWRP data backup.
I then have been able to copy the contents of the old /data/media directory into the new one.
... yet again: however....
The boot of the OS now is stuck on "tablet is starting", with no progress, no change, nothing.
I've tried another restore of the system_image but that hasn't changed anything.
I'll leave it going, just incase it's like a "restorecon" and all the files are being 'corrected' (which could understandably take a long time)... But isn't tarused to stop this sort of b**ks from happening?
This is the worst experience of "backup" I have had in over 20 years!!
If I had known the backup + restore mechanism wasn't actually tested I would have performed my own "dd" to stop any of this.
Hopefully this will be a warning for anyone else trying to use TWRP for 'backup' of actual data and people can make a much better choice going forward.
--
Paul_one

Another update:
So, I am attempting to check through various differences between a "clean" /data, and the /data that's restored and doesn't let the UI come up fully.
I thought "logcat" might be able to point me in the right direction (error message about "Unable to find com.android.systemui")... But it's not exactly helping me out with the mass of other minor errors etc.
I was able to get a tiny bit further by renaming the "/data/app" directory, so I'm now prompted for the pattern to decrypt/log in ... But the "tablet is starting" pops up after (as if the setup wizard is completing or something).
Pressing home does nothing. I can pull down the status bar to access things in there - but the "home" isn't coming up properly.
So, now it's just a long journey of trial+error to try and find the problematic files/directories.
--
Paul_one

[ROM][OFFICIAL][gts4lv|gts4lvwifi][12] LineageOS 19
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project, with...
forum.xda-developers.com
The difference between 18.1&TWRP and 19.1&TWRP is inability of TWRP to decrypt /data/media were TWRP directory locates. So once installed, 19.1 makes backup/recovery functions of TWRP inoperable since TWRP cannot nor decrypt nor find encrypted /data/media/TWRP. You can make sure of that with the file manager while in TWRP, seeing abracadabra instead of directory names in /data/media, which is an alias path to /storage/emulated/0 (0 stands for user0), where Download, TWRP etc locates.
The only thing You can do with TWRP when 19.1 installed is to whipe System and FORMAT Data.
Then, wifhout leaving TWRP, You can INSTALL, not RECOVER, prepared on external SD 18.1 zip. You can't recover since You can't create /data structure by means of TWRP, but installation of 18.1 can. Then reboot into system, scip all settings and reboot to TWRP. Now You can recover to previously saved 18.1 BACKUP.

vpn560 said:
The only thing You can do with TWRP when 19.1 installed is to whipe System and FORMAT Data.
Then, wifhout leaving TWRP, You can INSTALL, not RECOVER, prepared on external SD 18.1 zip. You can't recover since You can't create /data structure by means of TWRP, but installation of 18.1 can. Then reboot into system, scip all settings and reboot to TWRP. Now You can recover to previously saved 18.1 BACKUP.
Click to expand...
Click to collapse
That's unfortunate. I only discovered this now after upgrading from 18.1 to 19.1 four days ago....and then tried doing a backup through TWRP....which threw up a 255 fork error....
Wondering if a fix will be included with the next vewrsion....twrp-installer-3.6.1_9-0-lake.zip....
Is there any other backup/recovery through recovery you can recommend?

Bonjour,
j'ai installé lineageos 19.1 (20221025) avec TWRP (3-5-1) sur mon oneplus 5T
tout est OK
Mais lors des mises à jour proposées par le telephone (>paramètres>systeme>gestionnaire de mises à jour) le tel redemarre en bootloops sur le logo lineage ???
Réinstallation de linéage mais en faisant un wipe paramètres usine et installation de TWRP (3-7-0)
= tout fonctionne paraitement (les mises à jour de la branche également)
Si ça peut servir....

djimel said:
Bonjour,
j'ai installé lineageos 19.1 (20221025) avec TWRP (3-5-1) sur mon oneplus 5T
tout est OK
Mais lors des mises à jour proposées par le telephone (>paramètres>systeme>gestionnaire de mises à jour) le tel redemarre en bootloops sur le logo lineage ???
Réinstallation de linéage mais en faisant un wipe paramètres usine et installation de TWRP (3-7-0)
= tout fonctionne paraitement (les mises à jour de la branche également)
Si ça peut servir....
Click to expand...
Click to collapse
- English Plesse
- wrong forum ; this is for Samsung Tab S5e, not Oneplus..