Database Info

Leagoo t10 help with bootloader unlock

Hi,
Can anybody help me how to unlock the bootloader and root Leagoo t10.
Thanks.

I solved it myself...
I finaly found a way how to unlock the bootloader...
1. I had to turn off the phone
2. hold the volume up button and insert the usb cable to connect to the pc
3. the phone starts at that point to recovery mode and after it I had to reboot to bootloader (from recovery)
4. then I could use the basic fastboot program (it finaly detected the phone via the commant "fastboot devices") and use the command "fastboot oem unlock" to unlock the bootloader
5. I finaly also had to folow the promt on the phone (the phone asked if I realy want to unlock it) to allow the bootloader to be unlocked
6. The bootloader is unlocked (when starting, the phone shows that its been unlocked)
I think that rooting after this wont be a problem...

PS
I forgot to mention that I also installed PdaNet drivers meanwhile which might be the cause fastboot was able to detect my device...

Hi
Finaly did you manage to root it successfully ?
I am just discovering this phone and I am very interested. But I need it to be rooted
Thanks

No not yet.... The trouble is not the root itself but the backing up before doing it... There are no rooting apps witch can do it automatized yet but that should be solved in the future... The problem is creating the scatter file for backup because the software doing that for Mediathek procesors was not updated for a while and can't handle the 67xx series...

There is presently a flash sale on gearbest, I just ordered it. I hope too that the necessary tools will be available some day. Thanks for the explanation. And wait...

You might be interested that a few days ago there is a downloadable version of the official Leagoo t10 software with all backups and the scatter file included... You can Google it but I believe it was page called something like " need ROMs"...
Now I could try now to Port a custom recovery but after 20 hours of trying I gave up for some time again.... I ported at least 6 recoveries from TWRP and CWM but non worked and the f*cking system of the Leagoo t10 has a failsafe witch automaticky recovers the factory recovery on any standard boot... You should look some time on that need ROMs website because if someone ports a functioning recovery on the t10 that is most probably the first place to be available... If you would have a custom recovery installed rooting would be no problem... Good luck with your new phone... I at least take it the way that I learned more about Android and the ways around it in three months than I have in that last three years thanks to Mediathek...

So I got a version of TWRP working only when you use fastboot to boot to it, the screen is frozen if you try to flash it.
Link here
command is fastboot boot <imgname>
You can root from there, not done much else but playing with it just now.

How did you managed to Port it? I tried at least 3 TWRPs from other mt6797 devices (and modified them trough image kitchen) but none worked... I also tried once to boot to one trough fastboot but that also didn't work... And you said you rooted it with that TWRP but woul it be possible to do MAGISK root this way? Because T10 has only Android 6.0 now and basic root would do the update (when it comes out) harder...
Thanks.

It took me a few hours but I got the LG K10 TWRP to work with it, not sure about MAGISK as I said I only just got it working. I see this device is discontinued now too so unlikely to see much more than this I think.

Thanks... If you got something else working please write about it because it's really hard to find anything useful about this device... And thank you again for the root advice, I will do it as soon as I have some time.

The root worked... With the TWRP from alpha232 I was able to install supersu 2.82 (trough "fastboot boot <image name>" to TWRP and install the zip from there) and my Leagoo T10 is now rooted... (Thanks Alpha232). If someone finds out a way to port TWRP for T10 I woul welcome it if he would share the way how to do it... I woul be also glad if someone could tell me how to go around the failsafe which restores the factory recovery on normal boot for this device.

RCT6973W43 ROM needed

I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo

kapicarules said:
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
Click to expand...
Click to collapse
Hey bro, I've used these guys. Good luck
https://www.needrom.com
Sent from my HTC One M9 using Tapatalk

No RCA I might need to find a similar tablet and dump the firmware

kapicarules said:
No RCA I might need to find a similar tablet and dump the firmware
Click to expand...
Click to collapse
It's been a while since I played with RCA devices, which version of Android is it running?

NepoRood said:
It's been a while since I played with RCA devices, which version of Android is it running?
Click to expand...
Click to collapse
Android 6.0

kapicarules said:
Android 6.0
Click to expand...
Click to collapse
Sorry, not on the Chinese site we used for Viking and Maven firmware, it may show up eventually though...

link me to that chinese website

kapicarules said:
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
Click to expand...
Click to collapse
Bro,the device hasn't even been rooted yet. I just purchased one today. There is supposedly a bootloader unlock but no custom recovery yet and no root yet

DMon04 said:
Bro,the device hasn't even been rooted yet. I just purchased one today. There is supposedly a bootloader unlock but no custom recovery yet and no root yet
Click to expand...
Click to collapse
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...

Getting anywhere on this?
darkvoxels said:
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Click to expand...
Click to collapse
You get anywhere on dev for this device? I found one at work and was wanting to give it a shot.. unfortunately it's barren here and supa old hah.. AOSP would be nice for this though.

BA_Flash_GOD said:
You get anywhere on dev for this device? I found one at work and was wanting to give it a shot.. unfortunately it's barren here and supa old hah.. AOSP would be nice for this though.
Click to expand...
Click to collapse
Unfortunately I did not. Mine is still a brick sitting on a shelf, been playing with GSI/Treble for oneplus 6 lately.

darkvoxels said:
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Click to expand...
Click to collapse
I realize this is an old post but I'm hoping you may be able to help me.
I just got this device and was wondering how you got the bootloader unlocked. When I try to select OEM unlock in settings it just jumps back to off. And fastboot flashing unlock gives me an error.
Any help would be appreciated.

Isrgish said:
I realize this is an old post but I'm hoping you may be able to help me.
I just got this device and was wondering how you got the bootloader unlocked. When I try to select OEM unlock in settings it just jumps back to off. And fastboot flashing unlock gives me an error.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi yeah it's been a while since I bricked mine.. still sitting on a shelf as brick.. If I remember correctly when you do the OEM unlock from fastboot it flashes very briefly the screen to the unlock with instructions and button combination. What I did was run the command while using my phone to record the screen so see the instructions, then I went back watched the video to see what they were
I then went back to fastboot got the command ready again got my fingers in position before hitting enter and just tried to be as fast about it as possible and it worked for me.

darkvoxels said:
Hi yeah it's been a while since I bricked mine.. still sitting on a shelf as brick.. If I remember correctly when you do the OEM unlock from fastboot it flashes very briefly the screen to the unlock with instructions and button combination. What I did was run the command while using my phone to record the screen so see the instructions, then I went back watched the video to see what they were
I then went back to fastboot got the command ready again got my fingers in position before hitting enter and just tried to be as fast about it as possible and it worked for me.
Click to expand...
Click to collapse
Thanks for the reply.
How did you do a record the screen? Is there such an option while in fastboot?
Thank You,

darkvoxels said:
... using my phone to record the screen so see the instructions, then I went back watched the video to see what they were ...
Click to expand...
Click to collapse
Can you please tell me how you recorded the screen while in fastboot?
Thanks

I managed to get the bootloader unlocked on my Alco RCA Voyager III and just never got around to finding recovery or anything for it, this device a lost cause or am I just missing something? I don't think I can pull off making a recovery or rom yet but I can give it a shot if no one else is bothering with this device now a days.

@Trolldizzle How did you get it unlocked?
Thanks

@Isrgish I used fastboot flashing unlock command if I remember correctly, been a little bit since I did the unlock but I am like 90% sure that was the command.

i had get link here : findrom.info/rca-rct6973w43
you can try

Here you can find thr ROM. http://detonnot.com/3Xt3

[TEST][Recovery] realme u1 twrp recovery

Team Win Recovery Project 3.x, or twrp for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface*
Prerequisites
1. Unlocked bootloader.
Bugs
1. You Tell Me
Instructions
1. Go to the fastboot mode.
2. Download the*recovery.img*and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
[
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
TWRP RECOVERY
{Mod edit}
XDAevDB Information
TWRP For Realme U1
Contributors @KSUBROTO
Version Information
Status:*Beta
Based on :*TWRP
Disclaimer:- This project hasn't been tested and flash at your own risk.

Thanks

Send me Bugs List

Will it work on RU1 pie?

dheva02 said:
Will it work on RU1 pie?
Click to expand...
Click to collapse
You Can Try

dheva02 said:
Will it work on RU1 pie?
Click to expand...
Click to collapse
You Can Test

What custom ROMS are supported on Realme U1 and which among those is best for privacy and stability concerned users?

Deepakk88 said:
What custom ROMS are supported on Realme U1 and which among those is best for privacy and stability concerned users?
Click to expand...
Click to collapse
No Custom ROM For Realme U1

What can i expect if i go ahead an install Linegae OS anyway, will it work reasonably well or will it be full of bugs and i face the risk of bricking my phone? I have no programming knowledge at all but I want to ger rid of or limit google's and other giants endless spying.

Deepakk88 said:
What can i expect if i go ahead an install Linegae OS anyway, will it work reasonably well or will it be full of bugs and i face the risk of bricking my phone? I have no programming knowledge at all but I want to ger rid of or limit google's and other giants endless spying.
Click to expand...
Click to collapse
I think Gsi Lineage Less Bug No Reason bricking your device

Did you tested it ?

CorcRoazBa said:
Did you tested it ?
Click to expand...
Click to collapse
I didn't Test Because I don't Have device But Some people It Work

CorcRoazBa said:
Did you tested it ?
Click to expand...
Click to collapse
I didn't Test Because I don't Have device But Some people Say It Work

Urgent help
I have hard bricked my device, even motherboard is dead. Phone is in waranty. What should i say to realme support so they won't be able to tell that I tried to install custom ROM.

Deepakk88 said:
I have hard bricked my device, even motherboard is dead. Phone is in waranty. What should i say to realme support so they won't be able to tell that I tried to install custom ROM.
Click to expand...
Click to collapse
Just Brick Flash Stock rom flash it fix

I told them that the phone failed to start after a software update. They repaired it in 2 hrs and gave it back. So the motherboard was not fried as I thought.
What happened was that the TWRP recovery you provided has not worked, my device failed to get in to TWRP recovery after I have re-started the phone, So, I tried to flash with other TWRP versions that some people linked to in their posts on Realme U1 on other websites. None of them worked and after sometime my phone went in to bootloop, I got it in to fastboot screen by holding down the power and vol down button and tried various fastboot commands, none of them fixed the bootoop. I finally gave the command 'fastboot oem reboot -recovery' then it switched off the phone.

Deepakk88 said:
I told them that the phone failed to start after a software update. They repaired it in 2 hrs and gave it back. So the motherboard was not fried as I thought.
What happened was that the TWRP recovery you provided has not worked, my device failed to get in to TWRP recovery after I have re-started the phone, So, I tried to flash with other TWRP versions that some people linked to in their posts on Realme U1 on other websites. None of them worked and after sometime my phone went in to bootloop, I got it in to fastboot screen by holding down the power and vol down button and tried various fastboot commands, none of them fixed the bootoop. I finally gave the command 'fastboot oem reboot -recovery' then it switched off the phone.
Click to expand...
Click to collapse
Wait 2 minutes Twrp Work Only Work Color OS 5
Try This one For color os 6 pie https://forum.xda-developers.com/an...overy-unofficial-twrp-rmx1831-realme-t3947909

Hello sir
Sir please provide Realmi U1 costom recovery

Thread closed as the OP is no longer member of XDA.
@CyberJalagam Thanks for the heads-up.

TF303CL boot fail

Hi!
Unfortunately there is no topic for Asus Tf303CL, but since it is the member of the TF3xx family I hope this post can stay here.
The problem is, that I'm stuck at the Asus boot (static white) logo and can't go further in booting.
I've tried ADB, but there's no response on the "adb devices" command.
I've also tried fastboot, but only two commands are woriking:
"fastboot devices" comes back with an alphanumeric number and
"fastboot continue" turns off the tablet.
The other fastboot commands are returning with the message "fastboot failed <remote failure>"
So finally I've found some hints that maybe with xFSTK I would able to fix fastboot, then with the Asus Flast Tool I supposed to be able to flash the stock raw rom (which I've already done before).
But unfortunately xFSTK is ether not working (no communication) or I'm using it wrong. As far as I know TF303CL has Intel SoC with Baytrail platform, so I used the Baytrail B0 tab in xFSTK and I've loaded the *ifwi*.bin file which I found in the stock raw rom.
Is this the right way to fix fastboot or I have to do something else? Or the tablet may has hardware defect?

mucden1 said:
Hi!
Unfortunately there is no topic for Asus Tf303CL, but since it is the member of the TF3xx family I hope this post can stay here.
Click to expand...
Click to collapse
I think it was a good idea to open this thread. To my mind your device is really very close related to TF300T and TF700T. The OS is Android 4.4. So it might be worth to attempt to flash a CR like "KatKiss - Nougatella"
But before you may start is to clarify following:
1. Is the bootloader on your device unlocked?
2. Is there already any custom recovery like TWRP on your device?
3. Can you boot into fastboot protocol by holding Power on and Volume down together?
If you cannot get access neither through ADB or Fastboot, your device is bricked for good. Sorry!

1. Is the bootloader on your device unlocked?
I have no idea. It bought it brand new, but I already had to debrick it once with Asus Flash Tool about a year ago. So raw firmware was flashed. I don't know whether flashing a raw rom with AFT requires unlocked bootloader or not.
2. Is there already any custom recovery like TWRP on your device?
As far as I know it has stock recovery.
3. Can you boot into fastboot protocol by holding Power on and Volume down together?
I think Power on & Vol down is the key combination for recovery mode. Power on & Vol up is the combination for fastboot. I can't access to recovery, but fastboot may partially work.
If you cannot get access neither through ADB or Fastboot, your device is bricked for good. Sorry!
Whit adb
Code:
adb devices
command has no response. With fastboot I have a response on the
Code:
fastboot devices
command, it returns some kind of an id. Beside this
Code:
fastboot continue
makes the device to turn off. Other fastboot commands (as I wrote) are returning with the "fastboot failed <remote failure>" response.
These are what I have tried so far:
reboot, reboot bootloader, update, flash (several images), erase cache, erase data

mucden1 said:
1. Is the bootloader on your device unlocked?
I have no idea. It bought it brand new, but I already had to debrick it once with Asus Flash Tool about a year ago. So raw firmware was flashed. I don't know whether flashing a raw rom with AFT requires unlocked bootloader or not.
Click to expand...
Click to collapse
People usually unlock their bootloader to root their device or install Custom ROM on it. I think your bootloader is still locked. On the other side in the left above corner of the dark screen should appear the hint "the device is unlocked" during the boot process.
For the TF300xx family there is an Asus unlock tool V8 available. I don't know if it is useable for your device. Please call Asus support and ask them about that. On the other hand there is a tutorial here: https://qitapso.com/how-to-unlock-asus-transformer-pad-tf303cl-bootloader/

Should I try to unlock the bootloader?

mucden1 said:
Should I try to unlock the bootloader?
Click to expand...
Click to collapse
Of course!
But it's on your own risk. You have to make the decision yourself.

ebonit said:
Of course!
But it's on your own risk. You have to make the decision yourself.
Click to expand...
Click to collapse
The link above goes to "AutorootTools" which is not a real sw, only promising download after an unwanted and long survey. I consider it as a dangerous site.

Cannot get oem unlock token oneplus 8 tmobile (in2017)

So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.

Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml

if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk

PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol

DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all

DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind

d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?

DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great

DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp

d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface

DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.

FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!

SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD

FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?

nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.

FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!

nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.