Oneplus 7t Pro 5G McLaren question about flashing ROM - OnePlus 7T Pro 5G McLaren Questions & Answers

Yo, first timer in this form sor advance apologies if I get one or two thing wrong.
I successfully unlock the bootloader on my oneplus 7t pro 5G McLaren from T-Mobile.
My next step is to flash it with a custom rom. I already searched in this website and found some information about my device
1. I need to flash trwp in two slot (a and b). I don't know if that the same with all the device.
2. There are many trwp version and I have to pick the right one. And that my question which trwp do I need to flash to make it work? Do I really need to flash trwp to make it work? Do I really need to flash DATA. I already reset my phone before posting here. iF so how do I find my data and what format does it need to be in to do it? Any article or advice is welcomed
Thanks

Related

Need Beginner's Guide, so Custom Rom can be installed

***UPDATE***
Thanks to reply, I have now successfully done everything I set out to do, and created follow-up guide!
You can find it HERE
Original Post below:
Hello Everyone!
I'd like to start off saying I used to have a Nexus 4, with TWRP and Lollipop-based CyanogenMod. I was able to install this all by myself, and keep both TWRP and the ROM updated. I also flashed custom radio to unlock the LTE capability on that phone. My tool of choice to help customize the phone was Nexus Root toolkit.
I was able to follow guides posted long ago on these forums, to do what I wanted with the Nexus 4 back in 2013/2014, but it seems I'm not so capable these days. I've hit such a roadblock with lack of root and constant stutters/slowdowns with everyday use on my current device, the Axon 7, that I must get away from the stock software. I heard it was not so easy with other devices, and while a few devs have posted wonderful guides for users, it's just not enough for a true beginner like me. From skimming guides posted, it seems like devs already expect you to have installed custom recovery, or unlocked bootloader. Then when I try to do these things, so I can move onto custom ROM, it seems the guides are out of date or just not step-by-step enough for me to use, and I don't want to take a risk and brick my device trying things that I'm not sure about. I'm a power user through and through, but not so up-to-date or knowledgeable enough to be able to follow the guides already on the forums. Consider me 1 out of 5 on tech level for Android software.
Here's the model/software already on my device: Stock everything, from bootloader and recovery, to ROM.
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
will my ROM of choice have Daydream VR support? if not what would be needed?
this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through how to use it once installed to help me unlock bootloader/root on another device, Zenphone Zoom if anyone is interested.
PLEASE, don't link me to other guides for any part of this process, if the steps are thorough and relevant, please copy here, of course with all due credit given to original poster.
Feel free to let me know if more info about my knowledge level or device is needed to help you work on my request.
Thanks for reading, here's to several years more of everyone enjoying this wonderful device!
ok there is three real steps, but it can be aheadache, mainly because you didn't unlock before going to nougat.
Step 1. Downgrade to B29 Marshmallow - go here https://www.zteusa.com/axon-7/ and on the support tab in software updates is a full B29 software package. Download it, unzip it once, then put the update.zip file on your SD card.
- on the phone, in developers options, turn on OEM unlocking (it is needed to flash from sd card)
- boot phone to recovery, choose update from sd card, pick the update.zip from the sdcard, the phone will flash the B29 software. It is a bit slow, let it do what it needs to do.
Step 2. Unlock phone and install TWRP - go here https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 download the miflash program, fastboot unlock program, and twrp for B29.
- instructions are all there, just do what it says.
Step 3, Install LineageOS - https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679 very straight forward. Don't forget to install first the bootloader, then the rom, then gapps.
What makes this so hard is not being easily able to unlock in nougat. Most of us here unlocked way before marshmallow
No need to downgrade to b29.
lafester said:
No need to downgrade to b29.
Click to expand...
Click to collapse
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
gpz1100 said:
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
Click to expand...
Click to collapse
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Help needed
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
kaiso said:
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
Click to expand...
Click to collapse
Did you downgrade to Marshmallow B29 first or skip this step?
[email protected] said:
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
Click to expand...
Click to collapse
I'm praying that someone will compile the information spread about into 3 guides that are model specific so people like us won't rack our heads trying to figure out what on earth to do.
[email protected] said:
Hello Everyone!
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
1with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
2will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
3will my ROM of choice have Daydream VR support? if not what would be needed?
4this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
5NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through
Click to expand...
Click to collapse
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
nolimit78 said:
I'll keep on saying this as much as I need to, I get where you're coming from. There's a lot of data about the correct way of doing things. Best thing to do is read and search. When I got my phone B29 was the new hotness and there was a bunch of older data floating around that I had to sift through. But I did it, I sifted and found my own way and combined two different methods to get my phone rooted and flashed with LOS. Honestly, the trial and error, the searching, the sifting is totally worthwhile because while this device is /DIFFERENT/ compared to methods for HTC and Samsung products, it's not harder. It's better to get yourself properly antiquated to the device you plan on flashing/hacking/rooting because there is /always/ a chance for bricking. Then another thread will be created asking for help to unbrick. Take the time, read now, read everything, understand your device, then push forward.
Click to expand...
Click to collapse
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
nolimit78 said:
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
Click to expand...
Click to collapse
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
KyJelly69 said:
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
Click to expand...
Click to collapse
Yup.
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
[email protected] said:
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Click to expand...
Click to collapse
Thank you for the guide, but I managed to get everything done without having to downagrade from Nougat. I was having issues with my Windows variant recognizing my phone after drivers were installed so I used Linux Mint 18.1 and everything went smooth as a whistle. I think the mods should pin your thread post.
I followed the rootjunkie YouTube videos, worked perfectly and the files were all available.
Sent from my ZTE A2017U using Tapatalk

X720, X722 and X727 uses the same ROM?

hi guys, i have the X722, i can use ROMs of X727 and X720?
No the x722 has no custom ROMs. You'll soft brick the phone if you try to load any ROMs from other variants onto it, to my knowledge.
:crying::crying::crying::crying::crying::crying:
I try install Miui 8 rom... i forgot to do backup, and i try by fastboot install...
And now a has a hard brick... and i don't find any QFil file to bring my phone back...
:crying:
I also soft bricked my Le Eco Pro 3
vsrocha said:
:crying::crying::crying::crying::crying::crying:
I try install Miui 8 rom... i forgot to do backup, and i try by fastboot install...
And now a has a hard brick... and i don't find any QFil file to bring my phone back...
:crying:
Click to expand...
Click to collapse
Unfortunately, I also soft bricked my Le Eco Pro 3
I tried for 16 hours to resolve the issue and could not. However, after I did the research I now understand what I did wrong. Also, I got rid of the phone. Though I will probably order another one and be much more careful next time.
For anyone else reading this post : don't trust every comment here. Some people will give incorrect or incomplete info, such as advice to wipe the system to get around encryption.
* That's what I did and after successfully unlocking the boot-loader, I find that my system was somehow encrypted.. I did not encrypt my phone so I am not sure how this happened. In my haste, I did not create a recovery, I thought that is what the official Leeco twrp was for?
Options?
I too read about the Qfil tool, at the time I was having trouble downloading the files so I attempted to wing it... and failed.
I see now that I did not spend enough time on this complex option.
Update:
here is the exact instructions for using the Qfil method. ( this link provides step by step, and is tedious, but appears to work.
Sigh! I attempted to post a link and could not, due to being new on this site.
No doubt, I found the best instructions that I have seen yet on the Qfil Process.
Its on the unoffical Leeco Repair site : tora33 #comment-15320 this post is much more extensive than some other posts by Tora33 linked from XDA
Again, I can't post the actual link here! Just search for : unoffical Leeco Repair site : tora33 #comment-15320
Potential other options
J tag brick repair service website : brickedmyphone they charge $45 to repair a bricked phone.[/U
[*] This video seems very promising! Unfortunately, I wasn't able to find this video before now.
Since I am new here I am not allowed to help you by posting links!
search YouTube for How to unbrick any bricked letv phone without loosing data ( easiest way ) in Hindi.
Yes its in Hindi, but you will still understand because he used some English and it seems that he has built a fairly useful tool. Although, its still easy to get the gist of what he is telling us and he apparently built a program to repair a bricked Leeco phones, and he has other videos
[*] Finally Google : LeEco X820 Max 2 Super Unbrick Guide ( gizmochina. website) seems to be another complete solution.
I hope this helps you!
How to unbrick any bricked letv phone without loosing data ( easiest way ) in hindi.
https://www.youtube.com/watch?v=m0o4QtNXljg
1. He shows us that his phone is stuck on the logo and his recovery won't boot (it should start in 5 seconds).
2. He says to go to the stuck bootloader page, press the power on/off button and volume down button continuously to get into Download(?) mode.
3. Connect your phone to your PC and use your unbrick tool of choice. The tool linked in the video description is for the LeEco Le 2 x526, NOT the x720/x722/Le Pro3 models. So I wouldn't recommend you use it unless someone here can confirm that they used it with their Le Pro3 successfully.
4. Assuming this program works with all LeEco phones (not confirmed yet), continue with the process on your Le Pro3.
5. A cmd prompt will come up after you connect your phone and start the program. The instructions are in English. Choose an option--first install adb/fastboot drivers if you haven't already, then press 3 to Unlock the Bootloader. Check the bootloader's status by pressing 4. If it says "device unlock: true", it's unlocked.
6. Flash TWRP by pressing 5. I don't know which version of TWRP this program flashes, and whether or not it's compatible with the LeEco Pro3.
7. Then press 6 to reboot your phone into TWRP. You can now remove your cable and flash your ROM (most probably stock). Your phone is unbricked.
8. If your phone lost your data, you can connect via OTG storage and transfer ROMs and firmware/zip files to your phone using OTG. Reflash eUI 5.8 because 5.9 will most probably bootloader lock and brick your device again. Remember to select "swipe to allow modification" and "allow disable".
You might want to use the tool mentioned here to unlock the bootloader if the tool used in this Youtube video doesn't work (you'll have to add your phone's files to it though): https://forum.xda-developers.com/showpost.php?p=73988576&postcount=66
Also check this link (as tsongming mentioned): http://www.leeco.re/topic/1340-urgent-x800-no-turn-on-after-fastboot-process-rom/#comment-15320
tsongming said:
Unfortunately, I also soft bricked my Le Eco Pro 3
I tried for 16 hours to resolve the issue and could not. However, after I did the research I now understand what I did wrong. Also, I got rid of the phone. Though I will probably order another one and be much more careful next time.
Click to expand...
Click to collapse
Hey, good on you for figuring out what went wrong and sharing it with the rest of us!
Whatever you do, don't order a Chinese phone from like Gearbest, Geekbuying, Aliexpress, LightinTheBox, and all those other wholesale websites. They even shamelessly put their crappy vendor ROMs on Xiaomi phones. They put vendor ROMs on their phones that send data back to god-knows-which servers in China. Well, even OnePlus and LeEco do it natively, but I trust them over some shady wholesaler. If you absolutely want an LeEco, buy it through Amazon U.S. or Amazon India, Flipkart, etc. An official retailer is best.
Otherwise I recommend Motorola phones, even though I hate mine. They're generally cheap, they're stock, and they're a much safer option.
sk8223 said:
How to unbrick any bricked letv phone without loosing data ( easiest way ) in hindi.
1. He shows us that his phone is stuck on the logo and his recovery won't boot (it should start in 5 seconds).
2. He says to go to the stuck bootloader page, press the power on/off button and volume down button continuously to get into Download(?) mode.
3. Connect your phone to your PC and use your unbrick tool of choice. The tool linked in the video description is for the LeEco Le 2 x526, NOT the x720/x722/Le Pro3 models. So I wouldn't recommend you use it unless someone here can confirm that they used it with their Le Pro3 successfully.
4. Assuming this program works with all LeEco phones (not confirmed yet), continue with the process on your Le Pro3.
5. A cmd prompt will come up after you connect your phone and start the program. The instructions are in English. Choose an option--first install adb/fastboot drivers if you haven't already, then press 3 to Unlock the Bootloader. Check the bootloader's status by pressing 4. If it says "device unlock: true", it's unlocked.
6. Flash TWRP by pressing 5. I don't know which version of TWRP this program flashes, and whether or not it's compatible with the LeEco Pro3.
7. Then press 6 to reboot your phone into TWRP. You can now remove your cable and flash your ROM (most probably stock). Your phone is unbricked.
8. If your phone lost your data, you can connect via OTG storage and transfer ROMs and firmware/zip files to your phone using OTG. Reflash eUI 5.8 because 5.9 will most probably bootloader lock and brick your device again. Remember to select "swipe to allow modification" and "allow disable".
You might want to use the tool mentioned here to unlock the bootloader if the tool used in this Youtube video doesn't work (you'll have to add your phone's files to it though): https://forum.xda-developers.com/showpost.php?p=73988576&postcount=66
Also check this link (as tsongming mentioned): http://www.leeco.re/topic/1340-urgent-x800-no-turn-on-after-fastboot-process-rom/#comment-15320
Hey, good on you for figuring out what went wrong and sharing it with the rest of us!
Whatever you do, don't order a Chinese phone from like Gearbest, Geekbuying, Aliexpress, LightinTheBox, and all those other wholesale websites. They even shamelessly put their crappy vendor ROMs on Xiaomi phones. They put vendor ROMs on their phones that send data back to god-knows-which servers in China. Well, even OnePlus and LeEco do it natively, but I trust them over some shady wholesaler. If you absolutely want an LeEco, buy it through Amazon U.S. or Amazon India, Flipkart, etc. An official retailer is best.
Otherwise I recommend Motorola phones, even though I hate mine. They're generally cheap, they're stock, and they're a much safer option.
Click to expand...
Click to collapse
Thanks for the detailed steps, and providing the actual links, it will definitely help people.
Btw, I bought another LeEco Pro 3, from Amazon. At $199 its the best deal available for a device that has a Snapdragon 821processor, among all of its other features.
Right now, I am still using stock. Soon, I will unlock the bootloader, install TWRP, and root the phone.
I have become accustomed to the stock software and would stick with it for a while if it was running Nougat
To be honest, I am still a noob with installing custom ROMS, in case I ever decide to go back to stock, do you have a preferred method of backing up the stock software prior to installing a custom ROM?
I know that I can create a recovery within TWRP and back that up... us that sufficient enough, or is Titanium a better option?
Thanks again.
tsongming said:
Thanks for the detailed steps, and providing the actual links, it will definitely help people.
Btw, I bought another LeEco Pro 3, from Amazon. At $199 its the best deal available for a device that has a Snapdragon 821processor, among all of its other features.
Right now, I am still using stock. Soon, I will unlock the bootloader, install TWRP, and root the phone.
I have become accustomed to the stock software and would stick with it for a while if it was running Nougat
To be honest, I am still a noob with installing custom ROMS, in case I ever decide to go back to stock, do you have a preferred method of backing up the stock software prior to installing a custom ROM?
I know that I can create a recovery within TWRP and back that up... us that sufficient enough, or is Titanium a better option?
Thanks again.
Click to expand...
Click to collapse
The Le Pro3 is a great phone... on an official ROM, and if it's the x727 variant. The x720 variant is good too, but much harder to find a native SafetyNet ROM for it. Stock passes SafetyNet integrity checks. It's good that you bought it from Amazon. You'll most likely be getting a native SafetyNet-passing device and a decent warranty. Even on eUI, LeEco phones are viable. Especially if you're used to iOS. What I absolutely despise, though, are shop ROMs, and now I'm stuck with one. :crying:
Backing up stock? The moment you get the phone, set it up as normal but don't add any information if you don't have to to it. Like skip the Google account setup and whatnot (if you can). Unlock the bootloader & put TWRP on it. Make a Nandroid backup of your stock unmodified firmware. Heck, even just backing up your fully-setup ROM is fine. Just make sure you erase data, cache, etc. before flashing it (and remove the other ROM you're using).
Otherwise you'll find stock factory images for your device here on XDA if you need to go back. Download them before getting your phone if you don't want to wait.
I prefer Nandroid backups, but if you want to backup apps one by one, use Titanium Backup. I don't really like doing that anymore because Nandroids are more convenient, but if there's an app you absolutely need to add to all of your ROMs, then back up the app separately.
sk8223 said:
The Le Pro3 is a great phone... on an official ROM, and if it's the x727 variant. The x720 variant is good too, but much harder to find a native SafetyNet ROM for it. Stock passes SafetyNet integrity checks. It's good that you bought it from Amazon. You'll most likely be getting a native SafetyNet-passing device and a decent warranty. Even on eUI, LeEco phones are viable. Especially if you're used to iOS. What I absolutely despise, though, are shop ROMs, and now I'm stuck with one. :crying:
Backing up stock? The moment you get the phone, set it up as normal but don't add any information if you don't have to to it. Like skip the Google account setup and whatnot (if you can). Unlock the bootloader & put TWRP on it. Make a Nandroid backup of your stock unmodified firmware. Heck, even just backing up your fully-setup ROM is fine. Just make sure you erase data, cache, etc. before flashing it (and remove the other ROM you're using).
Otherwise you'll find stock factory images for your device here on XDA if you need to go back. Download them before getting your phone if you don't want to wait.
I prefer Nandroid backups, but if you want to backup apps one by one, use Titanium Backup. I don't really like doing that anymore because Nandroids are more convenient, but if there's an app you absolutely need to add to all of your ROMs, then back up the app separately.
Click to expand...
Click to collapse
Thank you for you very good detailed advice. Its truly appreciated.
I was decrying the shop ROM a lot but it's okay. I thought it'd be a lot worse than it is, but at least it lets me play the games I want to play on it without issue (so far...). I'm debloating it soon. Gonna remove all the LeEco apps. I hope kernel sources get released for the x722 but I ain't holding my breath.

Sim unlocked OP7T Pro Mclaren 5G attempt to flash the OP7T Pro Global Build

Everything I've been reading says that the OP7T Pro Mclaren and The OP7T Pro share the exact same software from OP, but when you flash the Mclaren phone it knows to unlock the Mclaren features/themes. This means you can flash the Mclaren edition phones with the software already available from OP.
The question is can you flash the Mclaren 5G from T-Mobile with this same Global version and get the same results. I know this was true for the OP7 Pro on T-Mobile, but this is a different version of the Mclaren than the International one.
I would assume the main issue would be the 5G radio and maybe all the radios for that matter, but is anyone out there with a Sim Unlocked (do not need to be bootloader unlocked) T-Mobile OP7T Pro Mclaren 5G willing to try flashing the Global software?
As I've mentioned before, there's no way to recover this phone from a bad flash or hard brick. Even just flashing the system partition would be insanely risky and probably lead to a loss of 5G, at least in the GUI.
LLStarks said:
As I've mentioned before, there's no way to recover this phone from a bad flash or hard brick. Even just flashing the system partition would be insanely risky and probably lead to a loss of 5G, at least in the GUI.
Click to expand...
Click to collapse
I completely understand that there is no T-mobile software to fall back on in case of disaster. What i'm wondering about is the OnePlus side of things. Are they going to have to release a separate Mclaren 5G stock/global system or will we be able to use the 7T Pro global version? If we need to wait for a stand-alone Mclaren 5G OnePlus stock system we might be waiting a long time.
Assuming there's a way to flash back I'd test it out. I don't use 5g at all I have it disabled right now so losing that functionality is not a big issue for me.
I've flashed my T-Mobile 6t and OnePlus 7 Pro before so now I impatiently await a solution for .y McLaren edition.
Can't wait for this to be tried out. I don't need or use 5g so I'd be willing to give it up to ditch the tmobile software.
Wondering the same. I don't mind losing 5G, would love to get updates straight from OP instead of waiting months for Tmobile to get their act together.
Yep, T-Mobile is slower than molasses ???
You guys will break your device. It will not boot, and there will be things broken that can't be fixed as of right now. No amount of fastboot restoring will do the trick. I mean you can fastboot restore and it will boot but things will remain broken even after a restore.
DanDroidOS said:
You guys will break your device. It will not boot, and there will be things broken that can't be fixed as of right now. No amount of fastboot restoring will do the trick. I mean you can fastboot restore and it will boot but things will remain broken even after a restore.
Click to expand...
Click to collapse
The ota done did it for me today for hours on end. Qualcomm ****. Only had work laptop Fastboot not working because i guess i turned off file transfer a few days ago. Then all a sudden it did. Had to download that flash.zip package thats floating around here somewhere. Did that. Didnt work. Recovery>erase all
Didnt work
Over and over. Manually in folder: flash boot boot_b boot_b.img
As well as a
Didnt work
Reversed it
Didnt work
A to a and b and vice versa
Didnt work
Did it the first way again and all a sudden im back on.
Fashcat said:
The ota done did it for me today for hours on end. Qualcomm ****. Only had work laptop Fastboot not working because i guess i turned off file transfer a few days ago. Then all a sudden it did. Had to download that flash.zip package thats floating around here somewhere. Did that. Didnt work. Recovery>erase all
Didnt work
Over and over. Manually in folder: flash boot boot_b boot_b.img
As well as a
Didnt work
Reversed it
Didnt work
A to a and b and vice versa
Didnt work
Did it the first way again and all a sudden im back on.
Click to expand...
Click to collapse
Well, I'm gonna give it another shot then
DanDroidOS said:
Well, I'm gonna give it another shot then
Click to expand...
Click to collapse
Im getting this in my update. Still not sure what happened. Backed up everything and followed directions to the T on dealing with magisk
But this is what i was seeing earlier and at one point i think it downloaded but didnt install but i reboot to check if it would after the fact but crash dump instead. Oof
Hala bir gelişme varmı bu konuda
Bu konuda bir gelişme var mı?
Any progress on this?
oneplus 7t pro 5g mclaren T-mobile automatically answer incoming calls plz help me.

Random bootloaders coming up flashing but no rom and no data on sims card

This oneplus6t is gettin on my nerves. Everytime i do the same thing it does something different. when i put on twrp and flash a rom i get this new bootloader that doesnt really let me do anything. Sometimes it just keeps going into fastboot. when the new bootloader comes up i got to put twrp back on and after doing it like 5 times i get tired of it. Is it a partition thing? Why is rooting so much harder then when i did it a few years ago.....................
Anyway i need help getting a rom on my phone. Thankfully the phone seems to back up oxygen cuz after a few factory resets oxygen just RANDOMLY came up even though i flashed another rom. TWRP and magisk is on the phone. Im also trying to get data working on my phone. I took the sims card(Verzion) out and put it in my Sgalaxy 7 for the time being and data works just fine on that.
O.P.P said:
This oneplus6t is gettin on my nerves. Everytime i do the same thing it does something different. when i put on twrp and flash a rom i get this new bootloader that doesnt really let me do anything. Sometimes it just keeps going into fastboot. when the new bootloader comes up i got to put twrp back on and after doing it like 5 times i get tired of it. Is it a partition thing? Why is rooting so much harder then when i did it a few years ago.....................
Anyway i need help getting a rom on my phone. Thankfully the phone seems to back up oxygen cuz after a few factory resets oxygen just RANDOMLY came up even though i flashed another rom. TWRP and magisk is on the phone. Im also trying to get data working on my phone. I took the sims card(Verzion) out and put it in my Sgalaxy 7 for the time being and data works just fine on that.
Click to expand...
Click to collapse
you're using oxygenos on your other slot now, did you format data before or after flashing your rom? if you haven't then that's why you keep going to fastboot/bootloader mode
@O.P.P.
There are other AB partition devices that are much more of a mess to use. ?? It's one of those things where you have to understand it. It took me a minute and I bricked a Motorola G7 Power a few times during my quest to learn about AB partition devices. Thank God for Blank flash files and all the people who helped me unbrick my G7 Power more than a few times. I guess I'm a slow learner. I feel your pain though. One day it just all made sense for me after reading countless information about it all. You'll understand it. Made me feel really dumb when I finally did.
I recommend reading Funk Wizards guide over in guides section of the forums for OnePlus 6/t. The data not working ...I Are your imei # present or are the gone? In that guide the op tells how to backup your efs using terminal commands. If and when you get your device working again I would most definitely get those backed up and throw them on your PC or usb drive or a cloud or all of the above. This is important because if you have a situation come up where your imei is gone and you have no data you can fastboot flash these backed up bin files to your device and restore your imei and get data working. I've read there has been some users who didn't backup these two bin files and we're not able to get data and imei restored.
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
I would head over to msm tool thread and maybe give that a go. Msm tool is an awesome tool and much of the time a last resort depending on what's going on... If you have a T-Mobile model device be sure and use the patched tool. You'll see all that on msm tool thread. Hope this helps some..
Edit
Sounds like maybe you needed to format data after your install process. If you don't it usually sends you back to twrp or bootloader mode ..
Sent from my OnePlus6T using XDA Labs

Dad helping son - Oneplus 6t stuck in fastboot - device not recognized

Hello all,
I am trying to help my son fix some of his Oneplus 6t phones. Please bear with me as I am not the most tech savvy. He uses the phones for a business and I like to try to help out.
He has 5 Oneplus 6t devices, 3 are stuck in fastboot and 2 went into qualcomm crash dump errors. These issues happened when he tried to install a custom rom, Arrow OS.
I wanted to help him factory restore the phones so that we could try again. I downloaded the following:
1) Oneplus 6t USB drivers - https://oneplususbdrivers.com/oneplus-6t-usb-driver-download/
2) Qualcomm USB drivers - https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3) A decrypted Oxygeon OS MSM download tool - https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
We ran the MSM tool as administrator and plugged in the phone with a black screen, while holding the up and down volume button. Only sometimes it was recognized / connected. When we clicked start in the MSM tool, I ran into a few potential issues.
1) Image files do not match device
2) Waiting for device (just keeps counting)
Also, often the device was not recognized, and we could not get it to work.
In the device manager, it does not show the correct device. It gives some error / device not recognized issue. I am not sure if this is related. I tried re-installing the drivers, as well as trying on a second computer. The cable we are using is able to detect non-corrupt Oneplus 6t devices fine, so I do not believe that is the issue. Also an important note, some of the devices may be T-mobile branded but I am not sure which, if any.
Does anyone know what are the next steps or things I can try? I would really like to get these devices working for him so he can continue with his business. Sadly I cannot afford to replace or rebuy the devices. I fear I am making a simple mistake somewhere but am not sure where.
Thanks for your help in advance.
It's highly likely you may need the Verizon version of the factory image you can reset with MSM Tool
Do NOT Use the patched version of the MSM Tool unless you are sure you are flashing a correct compatible image with your phone
Following what I have written here to install the correct drivers may help you
[Fix] [Guide] Device not showing in Fastboot or MSM Tool (Windows)
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who...
forum.xda-developers.com
HelpOneplus6t said:
Hello all,
I am trying to help my son fix some of his Oneplus 6t phones. Please bear with me as I am not the most tech savvy. He uses the phones for a business and I like to try to help out.
He has 5 Oneplus 6t devices, 3 are stuck in fastboot and 2 went into qualcomm crash dump errors. These issues happened when he tried to install a custom rom, Arrow OS.
I wanted to help him factory restore the phones so that we could try again. I downloaded the following:
1) Oneplus 6t USB drivers - https://oneplususbdrivers.com/oneplus-6t-usb-driver-download/
2) Qualcomm USB drivers - https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3) A decrypted Oxygeon OS MSM download tool - https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
We ran the MSM tool as administrator and plugged in the phone with a black screen, while holding the up and down volume button. Only sometimes it was recognized / connected. When we clicked start in the MSM tool, I ran into a few potential issues.
1) Image files do not match device
2) Waiting for device (just keeps counting)
Also, often the device was not recognized, and we could not get it to work.
In the device manager, it does not show the correct device. It gives some error / device not recognized issue. I am not sure if this is related. I tried re-installing the drivers, as well as trying on a second computer. The cable we are using is able to detect non-corrupt Oneplus 6t devices fine, so I do not believe that is the issue. Also an important note, some of the devices may be T-mobile branded but I am not sure which, if any.
Does anyone know what are the next steps or things I can try? I would really like to get these devices working for him so he can continue with his business. Sadly I cannot afford to replace or rebuy the devices. I fear I am making a simple mistake somewhere but am not sure where.
Thanks for your help in advance.
Click to expand...
Click to collapse
Did you figure it out?
FireRattus said:
It's highly likely you may need the Verizon version of the factory image you can reset with MSM Tool
Do NOT Use the patched version of the MSM Tool unless you are sure you are flashing a correct compatible image with your phone
Following what I have written here to install the correct drivers may help you
[Fix] [Guide] Device not showing in Fastboot or MSM Tool (Windows)
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, thank you for your response.
I'm not sure the issue you had is the same as mine. My Oneplus 6T does not show up in the device manager at all.
I tried doing the unsigned device drivers thing, but when I select the folder that contains the onplus_android_winusb folder, it says it cannot find the drivers.
Sadly I think I have to give up on this one I am not very tech savvy and really don't know what else I can do.
I was able to fix one of the phones. I tried using fajita_41_J.50_210121 as my MSM recovery and it worked.
The fact that it worked implies to me my issue doesn't lie with the drivers, but rather which MSM file I am using, is this a good assumption?
If so, how can I figure out which files to use? I tried that same file on the 4 other phones, but would always get Sahara communication error.
HelpOneplus6t said:
I was able to fix one of the phones. I tried using fajita_41_J.50_210121 as my MSM recovery and it worked.
The fact that it worked implies to me my issue doesn't lie with the drivers, but rather which MSM file I am using, is this a good assumption?
If so, how can I figure out which files to use? I tried that same file on the 4 other phones, but would always get Sahara communication error.
Click to expand...
Click to collapse
This is what I was trying to say, you probably have the Verizon version, you need to make absolutely sure the MSM recovery files you are using are for that phone model
I bought my phone as global but they sent me a unlocked Verizon model, I found out because I couldn't flash it with MSM tool until I used the Verizon versions files
FireRattus said:
This is what I was trying to say, you probably have the Verizon version, you need to make absolutely sure the MSM recovery files you are using are for that phone model
I bought my phone as global but they sent me a unlocked Verizon model, I found out because I couldn't flash it with MSM tool until I used the Verizon versions files
Click to expand...
Click to collapse
Hi,
I believe you are right, that makes sense.
I see that the 1 phone that was fixable is very slightly different than the other 4- it doesn't have an IMEI code on the back, so likely it was a different version or something.
Where do I find the right recovery files? I searched for Verizon Oneplus 6t MSM Download Tool but I don't see anything different.
Sorry for my incompetence, I appreciate your help
I was able to fix a few more phones using the Tmobile 9.0.13 MSM Tool here:
[TOOL] T-Mobile OnePlus 6T MSMDownloadTool [Firmware 9.0.13] [8/9]
Okay folks, took forever to find, but we finally have it, the T-Mobile OnePlus 6T MSMDownloadTool, your brick savior, bootloader relocker, among other things, I will include a basic faq at the end. Requirements: 1. Windows PC 2. OnePlus 6T -...
forum.xda-developers.com
2 of the phones didn't work, they have Sahara communication errors still. I am not sure how to locate the right MSM tools for these- any ideas?
Furthermore, I flashed 9.0.13 from the MSM tool, but I would like to update to specifically 10.3.11, how can I do that?
HelpOneplus6t said:
Furthermore, I flashed 9.0.13 from the MSM tool, but I would like to update to specifically 10.3.11, how can I do that?
Click to expand...
Click to collapse
That is the same version I flash with MSM Tool I think
You should follow the instructions here for the Verizon version https://forum.xda-developers.com/t/guide-sim-unlock-t-mobile-version-all-type-of-imei-supported.3915269/
You can unlock the verizon variant by using a custom patched MSM Tool
After you have followed those instructions to have it unlocked on the international version rom
Then you are able to just flash the Normal OOS Flashable Update Zips via TWRP or the built in updater
Download them here https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3865396/
This allows you to update to the latest OOS 10 or 11
I really don't know about your other phones, Are they definitely OnePlus 6Ts ? I am only aware of the global and verizon variants, so if it's not either of those, I am not sure it's a OnePlus 6T
I managed to fix them by flashing the T-mobile version. This worked, but then I needed to unlock them since they were T-mobile locked. I converted them to the international version earlier successfully.
I am on 9.0.11 stock now! All I need to do really is update to 10.3.11
I will try following the links you have provided.
They are definitely 6ts
Thanks for your continued help.
FireRattus said:
That is the same version I flash with MSM Tool I think
You should follow the instructions here for the Verizon version https://forum.xda-developers.com/t/guide-sim-unlock-t-mobile-version-all-type-of-imei-supported.3915269/
You can unlock the verizon variant by using a custom patched MSM Tool
After you have followed those instructions to have it unlocked on the international version rom
Then you are able to just flash the Normal OOS Flashable Update Zips via TWRP or the built in updater
Download them here https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3865396/
This allows you to update to the latest OOS 10 or 11
I really don't know about your other phones, Are they definitely OnePlus 6Ts ? I am only aware of the global and verizon variants, so if it's not either of those, I am not sure it's a OnePlus 6T
Click to expand...
Click to collapse
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
HelpOneplus6t said:
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
Click to expand...
Click to collapse
Yes you are right but you do not need to download Every single update
I have found that these are the files I need to upgrade, I keep them saved for easy access
Code:
1-OnePlus6TOxygen_34_OTA_024_all_1909112343_d5b1905(9.0.17).zip
2-OnePlus6TOxygen_34_OTA_047_all_2007171912_ac6dc9b(10.3.5).zip
3-OnePlus6TOxygen_34.J.48_OTA_048_all_2010042240_dbd576b615(10.3.6).zip
4-OnePlus6TOxygen_34.J.55_OTA_055_all_2107132253_b2cbbb97b4eee(10.3.12).zip
If you wanted 10.3.11 instead of 10.3.12, I don't see why that wouldn't work
These are all the full upgrade zips, but if you have a locked bootloader and use the official update method through the settings, I have been able to use the smaller OnePlus6TOxygen_34.J.55_OTA_048-055_patch_2107132253_b96081(10.3.6-10.3.12).zip Upgrade Zip to go from 10.3.6 to 10.3.12
HelpOneplus6t said:
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
Click to expand...
Click to collapse
I have actually found from testing that I did not need to flash the 10.3.5 or 10.3.6 Zips and could go from 9.0.17 to 10.3.12 if I used the full flashable update zips
so I am not sure why it failed for you
You are so awesome, thank you that worked flawlessly (the 4 separate upgrades). Throughout this thread I was able to:
Go from a soft bricked device, use the Tmobile MSM download tool to restore it, use a normal MSM download tool to convert it to the international variant, then upgrade it to 10.3.11.
My last question is regarding root, we are looking to root the device with magisk/twrp. I haven't done it in a few years so am a bit rusty on the process. It is a Oneplus 6t on 10.3.11, do you know where I can find the relevant files?
I see the latest fajita (oneplus 6t) files here: https://dl.twrp.me/fajita/
I'm a bit hesitant to use them because:
1) I'm not sure if I should use the latest ones, or an older version. I think I tried using the latest ones for something before and it messed something up.
2) I see people post online that I may need Enchilada files instead, even though that is for the Oneplus 6t, or that I need a mauronofrio twrp file instead, so I would prefer to wait for a decisive answer.
Thanks again for your help, you saved the day and my son is so elated
HelpOneplus6t said:
You are so awesome, thank you that worked flawlessly (the 4 separate upgrades). Throughout this thread I was able to:
Go from a soft bricked device, use the Tmobile MSM download tool to restore it, use a normal MSM download tool to convert it to the international variant, then upgrade it to 10.3.11.
My last question is regarding root, we are looking to root the device with magisk/twrp. I haven't done it in a few years so am a bit rusty on the process. It is a Oneplus 6t on 10.3.11, do you know where I can find the relevant files?
I see the latest fajita (oneplus 6t) files here: https://dl.twrp.me/fajita/
I'm a bit hesitant to use them because:
1) I'm not sure if I should use the latest ones, or an older version. I think I tried using the latest ones for something before and it messed something up.
2) I see people post online that I may need Enchilada files instead, even though that is for the Oneplus 6t, or that I need a mauronofrio twrp file instead, so I would prefer to wait for a decisive answer.
Thanks again for your help, you saved the day and my son is so elated
Click to expand...
Click to collapse
I am glad I could help and I do understand the hesitation, it is smart to be careful and not flash the wrong recovery file, the only time I have truly bricked a phone was by flashing the wrong recovery
I use the fajita twrp from the official source that you linked but the version you want to use does depend on your android version
You can get a crash dump error by using the latest TWRP on older OOS
I have been using Jaguar ROM for the OnePlus6T
My own installation process is as follows and WILL WIPE ALL DATA ON THE PHONE
Assuming you are coming from Latest Official OOS 10 (10.3.12)
Enable Developer mode and OEM Unlocking (In the Hidden Developer Settings)
(Optionally enable USB Debugging to adb reboot to bootloader)
(You may have to Disable Driver Signature Enforcement on Windows 10/11 to install correct drivers)
Reboot your phone to Fastboot by holding volume up and down during power up or with "adb reboot bootloader" in terminal, allowing the connection on your phone.
In Terminal
fastboot flashing unlock
FastBoot to TWRP 3.5.2
fastboot boot twrp.img
Install TWRP 3.5.2 .zip and Reboot to TWRP
WIPE Data Factory Reset and type YES to confirm and Reboot to TWRP
Flash the ROM and then flash TWRP 3.5.2
Reboot to TWRP Again
Flash ROM again then TWRP again
Reboot once then flash magisk etc via twrp
The process is more simple to just install magisk on stock OOS and I hope soon Jaguar will update to android 12, then the latest twrp should work with it
You will of course also need to have the android platform tools installed
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Worst case scenario I have found with OP6T, like not able to boot into recovery or anything
I can just do a factory flash with MSM tool using the patched version and then follow the above steps again
Everything is working, thanks so much for your help- I will pay it forward.

Categories

Resources