Does the 6T have a rollback ROM? - OnePlus 6T Questions & Answers

I've seen many OP6T threads link to a OP6 rollback ROM that won't work with the 6T.
Is there one specifically for the 6T or should I just use the MsmDownloadTool method to revert from Open Beta 5 back to stable?
Or am I overcomplicating this and can I just fastboot flash stuff? (I haven't actually looked at what's inside the zips yet)

As best as I can tell, no such rollback ROM exists and I should just go the MsmDownloadTool route.

You can flash whatever version you want using twrp.

Msmtool is still the easiest and cleanest way IMO.
The fastboot flashable image files work as well when zu flash them all. Depending on what you flash it'll completely wipe your device as well. It might help to flash some files without wipe if your OOS ROM bootloops or sth. So good to have both options.

A data wipe is no big deal, just want to make sure I know how to get the stable firmware on there. I'm just going with the MsmDownloadTool to do it.
I'm kinda surprised there isn't a more user-friendly way to revert back to stock. OnePlus kinda needlessly gave themselves a fairly pointless extra level of customer support to handle given that the official answer is "Contact Support".

Jaxidian said:
A data wipe is no big deal, just want to make sure I know how to get the stable firmware on there. I'm just going with the MsmDownloadTool to do it.
I'm kinda surprised there isn't a more user-friendly way to revert back to stock. OnePlus kinda needlessly gave themselves a fairly pointless extra level of customer support to handle given that the official answer is "Contact Support".
Click to expand...
Click to collapse
And A/B partitioning doesn't make this easier...

reppi said:
And A/B partitioning doesn't make this easier...
Click to expand...
Click to collapse
That's the conclusion I came to. MsmDownloadTool worked just fine, so no big deal.

Jaxidian said:
That's the conclusion I came to. MsmDownloadTool worked just fine, so no big deal.
Click to expand...
Click to collapse
I was just going to recommend that is the "rollback ROM."
It saved me a couple times in the past few days

Related

help installing twrp and then stock rom on top

Hello,
Can someone help me with some instructions to install twrp and then flash either stock rom or custom rom. I want to have twrp as the recovery so i can flash things in the future and also make twrp backups.
Im running stock 8.1 beta with unlocked bootloader
I know there are guides out there but all of them are 2-3 months old. Since then we've had the 8.1 beta.
Any help will be much appreciated.
ZAFAR- said:
Hello,
Can someone help me with some instructions to install twrp and then flash either stock rom or custom rom. I want to have twrp as the recovery so i can flash things in the future and also make twrp backups.
Im running stock 8.1 beta with unlocked bootloader
I know there are guides out there but all of them are 2-3 months old. Since then we've had the 8.1 beta.
Any help will be much appreciated.
Click to expand...
Click to collapse
You can't.
There is no TWRP for 8.1 so it isn't possible.
This phone has no traditional recovery. Recovery is part of boot.
That means that the boot image needs to be patched for tarp and still be able to boot the system.
Currently, or at least until 8.1 is no longer beta you will not see a tarp that can stay permanently and coexist with 8.1.
ZAFAR- said:
Hello,
Can someone help me with some instructions to install twrp and then flash either stock rom or custom rom. I want to have twrp as the recovery so i can flash things in the future and also make twrp backups.
Im running stock 8.1 beta with unlocked bootloader
I know there are guides out there but all of them are 2-3 months old. Since then we've had the 8.1 beta.
Any help will be much appreciated.
Click to expand...
Click to collapse
If you wanna flash a custom ROM, you can use TWRP (LOS 15.1 and AOSIP are both 8.1 ROMs that can be flashed with TWRP), but I suggest you get very comfortable with ADB and fastboot BEFORE you wipe your phone. As Tech_head said, TWRP gets flashed to the boot, not recovery, so you have to flash TWRP with fastboot each time you want to boot into it, it won't stick.
This phone is not real friendly for flashaholics. Also, be prepared to lose EVERYTHING on your phone if you start flashing custom ROMs, because if you start having problems or want to flash back to stock, you're going to need to wipe all your data (fastboot -w) (this wipes all your media too!). In fact, if you want to flash a custom ROM, you should wipe everything anyway, and don't count on TWRP being able to complete a nandroid backup or restore one. I haven't been able to once. Good luck, this phone's a *****!
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
gimpy1 said:
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
Click to expand...
Click to collapse
Its not that Essential is blocking any development of TWRP. Development for this phone, and all A/B partition phones for that matter, are really minimal right now, but especially the Essential because so few units were sold. Until Project Treble really gets going and more manufacturers start shipping A/B partition devices, you won't see much development for this phone. Eventually, someone will solve the issues with TWRP, but I doubt well ever see a lot of custom ROMs. When I say this phone's a *****, it's because of the issues with TWRP more than anything. Dirty flashing isn't working for me on AOSIP, Nandroid backups don't work, and flashing firmware can only be done using fastboot AFAIK (yes, with a computer). If you're not computer savvy, then you better pass on this phone if you want to run custom ROMs. It's a great phone even stock though, so up to you if you can settle for stock or u wanna learn more about ADB and fastboot, it's worth it IMO. If u want a phone recent that has good development, go with the OnePlus 5T, but even that phone can be a bit tricky for flashing, as I said, TWRP is not very compatible with Oreo 8.1 yet for any phone. You have to disable your pin/fingerprint each time you boot TWRP because they haven't figured out how to decrypt 8.1 yet. This is all common knowledge if you follow the development threads for these phones. The old days of flashing five ROMs in a day are over man, at least for the time being.
gimpy1 said:
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
Click to expand...
Click to collapse
A) LG phones are not root friendly. Only certain SKUs of any model (1 in maybe 8) can even bootloader unlock. Indeed, even rooting is problematic and only the result of security "flaws". If you are a flash-a-holic, you definitely don't want an LG. Or a Samsung, or any phone sold with carrier-specific hardware or firmware....IIRC the Samsung S8 took a calendar year to root.
B) The technical hurdle here on the Essential is also present on Pixel phones. Getting a Pixel will not free you from this.
The A/B partition scheme and boot layout is shared by Pixel and Essential. The easy flashing processes went away with the Nexus program. A/B isn't that bad-but you must learn fastboot and ADB commands. There aren't a whole lot of common one you really need, but you need familiarity with the toolset.
Thx, I will do some googling and reading.
The easiest way i found is to flash TWRP, Flash dump for your phone, then flash 8.1 boot.img so it don't bootloop. The recovery won't stay but you will be stock.
Download the dump for your phone from there
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
So flash TWRP
Flash dump from internal sd
flash stock boot image
gimpy1 said:
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
Click to expand...
Click to collapse
I mean no offense by this at all but one would think even a "semi-flashoholic" would be fairly well versed with Fastboot and ADB. Im curious how you have much experience with twrp if you dont know what those two things mean. Unless of course youre coming from an S3 or something and especially someone thats on verizons network. Theyve been pretty famously against unlocking bootloaders since i can remember. Also, it doesnt matter if youre buying off contract or get your phone through your carrier. Youre going to pay the same price in the long run either which way, and contrary to many believers that are stuck in that mind set of "they used to give free phones away or at most like $200" you were still paying the full 699.99-899.99 as you are now days . so my suggestion, buy straight from the source (google, lg, samsung, or even off amazon) and pay with a credit card because especially if you have a zero interest for x amount of time its going to be cheaper in most cases and you dont have to have that out of pocket cash for taxes on the device to pay that day. Ive worked for 3 out of 4 of the top carriers in my life and trust me, its the way to go. Also yes if you are looking for a root friendly phone to flash away on, this thing is not going to be your best choice either. Kick ass phone but not very developer/flash friendly.
Well, after considerable thought, I finally decided against going with the Essential or any unlocked bl.
I just received my LG (vs996) from Verizon day before yesterday.
gimpy1 said:
Well, after considerable thought, I finally decided against going with the Essential or any unlocked bl.
I just received my LG (vs996) from Verizon day before yesterday.
Click to expand...
Click to collapse
Good luck with that...just dumped my v20. LG can suck it.
Well, to each his own, I guess.
Pretty nice phone, but, in still learning to do things without root.
gimpy1 said:
Well, to each his own, I guess.
Pretty nice phone, but, in still learning to do things without root.
Click to expand...
Click to collapse
No root is the least of it...stuck on 7.0.0 forever, and its first and likely last os upgrade isn't likely to come until June 2018 at the soonest.
Pathetic for a supposed flagship.
I was an excited fool, and paid new retail at release. Never again am I buying an LG
Mine came with 8.0 (from Verizon).
gimpy1 said:
Mine came with 8.0 (from Verizon).
Click to expand...
Click to collapse
Oh that is right. I was confusing vs995 and vs996. Oh well.

Can anyone share a dump folder of .ops file? (python)

*EDIT 05-24
I had a problem where I would get stuck even after using MSMDOWNLOADTOOL completely. With the help of great minds,
#fullofhell #Dark Nightmare #Scott and frankly a god #Eliminater74 I could fix the phone completely. I am heading for modem work, which put me into this situation.
As of this point, I cannot find any misbehavior but I am quite new to this, so I can be deadly wrong. (Well but then, sensors are fine, calls , texts, data, wifi is working just fine. I don't know what else to check!)
I know as a fact that what happened to me is not really that rare (although it is quite rare, it happened before as well.)
So I was about to share how I fixed it but decided not because what I did was so out of experimental and I frankly have no idea if the same would work for others.
Tbh, if you are in the same position as I am, go ahead and contact the Oneplus service team. I did what I did only because I had to, I am Korean, and couldn't get it fixed.
If anyone, comes to this point and has absolutely no way to get it fixed, I will be glad to help,
(only if that person agrees that there is more chance to totally destroy it then fixing it XD.)
Again, Thank you so much Scott, dark nightmare. What you guys shared with me saved a bunch of time and you guys are what the forum truely needs!
P.S, Still couldn't find the moded MSMdownload tool. What can you recall what functions it had? Maybe enabled engineer mode?
I can't assist with your dump file, I'm just curious though how exactly did you brick your device?
Pain-N-Panic said:
I can't assist with your dump file, I'm just curious though how exactly did you brick your device?
Click to expand...
Click to collapse
Although it's pure stupidity, I guess it's worth sharing. I was messing around with the modem and somehow somewhere I broke proximity sensor.
So, I used fastboot flash tools including critical partitions. Which is the same process shared by amt911 "https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145". Once I was done with flashing, I could not reboot. Here, I could have just side load or try to find other way out but I decided to use msm tool, which locked my oem.
basically, I think it's critical partition that causes un-recoverable boot-loop to some of us. That is not fixed by msmdownloadtool for now.
Which, I am curious, do you think msm-download tool will wipe and flash every partitions? From what I searched so far, everyone seems to agree that msm tool will flash every partitions including the critical parts (which is not exactly true because I know for a fact it doesn't wipe out efs partition). If not, do you think there is a way to force it?
Thank you for your interest though! I am going quite sad and mad alone here!
Somehowko said:
Although it's pure stupidity, I guess it's worth sharing. I was messing around with the modem and somehow somewhere I broke proximity sensor.
So, I used fastboot flash tools including critical partitions. Which is the same process shared by amt911 "https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145". Once I was done with flashing, I could not reboot. Here, I could have just side load or try to find other way out but I decided to use msm tool, which locked my oem.
basically, I think it's critical partition that causes un-recoverable boot-loop to some of us. That is not fixed by msmdownloadtool for now.
Which, I am curious, do you think msm-download tool will wipe and flash every partitions? From what I searched so far, everyone seems to agree that msm tool will flash every partitions including the critical parts (which is not exactly true because I know for a fact it doesn't wipe out efs partition). If not, do you think there is a way to force it?
Thank you for your interest though! I am going quite sad and mad alone here!
Click to expand...
Click to collapse
Damn man, sorry to hear that. I've never had to mess with msm tool, thankfully. The fact that it locks the bootloader kind of scares me. From what I've read about the tool it does sound like it wipes/flashes all partitions including critical.
Are you able to unlock the BL in fastboot mode using the command?
Pain-N-Panic said:
Damn man, sorry to hear that. I've never had to mess with msm tool, thankfully. The fact that it locks the bootloader kind of scares me. From what I've read about the tool it does sound like it wipes/flashes all partitions including critical.
Are you able to unlock the BL in fastboot mode using the command?
Click to expand...
Click to collapse
As the bootloader is locked and I cannot boot, I am can't put enable oem-unlock on the data. Which means, yes I cannot unlock the bootloader as long as oneplus 6t doesn't have a loophole like oneplus 3T. I am pretty sure that was fixed though.
Well, I don't know if it's msm tool really. If I just started with that I would have been fine (at least I believe so). Yes I didn't wanted to lock the boot loader, which is why I used fastboot flash tool. But then, that's why I ended up here. So, if you end up in a situation where you might, might need msm tool or flash tool, always go with the msm tool !
For msm, I am quite certain it doesn't flash all partitions. I think there is some partition checkup somewhere. Here is why I think so
1) Completely formatted OS cannot be on a boot loop unless it's caused by hardware issue.
2) All partitions except vendor, system goes way too fast. It ends within 200 seconds for me. I would assume that kinda makes sense as it really is the problem of usb-pc hardware power but installing the image should take longer I think (but then I truly have no idea)
My conclusion is that the tool checks partition size before flashing, and does not touch / replace every file. I am probably wrong since it is
EDI tool after all, but I simply cannot believe msm tool cannot fix something that has nothing to do with the hardware.
I mean, imagine we can brake our newly formatted PC OS without any single components corrupted! (Is it even possible?)
I don't know man....with the bootloader locked you're not able to fastboot flash ANYTHING?
Somehowko said:
For msm, I am quite certain it doesn't flash all partitions.
Click to expand...
Click to collapse
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145
Scott said:
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145
Click to expand...
Click to collapse
Well, tbh, we know as a matter of fact it is not a complete flashing. I mean it clearly says flashing to partition _a only unlike previous versions of msm tools (ah, good days.) What I am curious of is if there is anything we can do about skipping partitions. I am suspecting using qfil would, through unpacking ops files. Although it seems like a long shot.
Btw, thank you for your interest!
Scott said:
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145
Click to expand...
Click to collapse
Msm tool has hidden functions, it's a pain but not impossible.
Search Google and gsm forums for readback mode, smt wipe, and imei/esn restore...
Siren siren... Watch out the xda police gunna blow down and remove my comment.. oh nooooo aghastt....
Btw u cannot use berklers script without an AES recovery key. There aren't any around as far as I know for fajita.
Easiest thing is if OnePlus bought device, get an exchange.. play dumb.. oops I dunno, your Android Q crap broke it..
Or if tmo bought, add insurance if u don't have it, play dumb. Get a new one. I did for a scratched screen..but made it about the modem not working, bc I erased it...
These corporations owe us nothing.
Get a new phone man
fullofhell said:
Msm tool has hidden functions, it's a pain but not impossible.
Search Google and gsm forums for readback mode, smt wipe, and imei/esn restore...
Get a new phone man
Click to expand...
Click to collapse
Thank you so much! I don't have to hassle with python anymore!!! That thing was making my brain fart!
Sadly, That's the only option that I got. As I am living in Korea and I cannot send a phone outside of a country (funny isn't it? they say battery hazard, I say licking Samsung's ass) I can't even get it fixed.
Frankly, I love my phone and I would go an extra mile even for a hint of getting it back to work again.
I will try to look for back up and smt wipe. Hopefully, I wouldn't totally destroy my phone. (again, hopefully.)
If you have any other information, please share with me!
Somehowko said:
Thank you so much! I don't have to hassle with python anymore!!! That thing was making my brain fart!
Sadly, That's the only option that I got. As I am living in Korea and I cannot send a phone outside of a country (funny isn't it? they say battery hazard, I say licking Samsung's ass) I can't even get it fixed.
Frankly, I love my phone and I would go an extra mile even for a hint of getting it back to work again.
I will try to look for back up and smt wipe. Hopefully, I wouldn't totally destroy my phone. (again, hopefully.)
If you have any other information, please share with me!
Click to expand...
Click to collapse
You're saying an msm reload didn't fix the device? Btw you can use the unlocked device msm tool as well as of version 9.0.11 I believe, just look for the modded tool that skips the model check, did you do a full system backup before tinkering? If so you can dd files back into place if msm doesn't overwrite them the way its supposed to, I've done some crazy things to the 6t, a bit surprised recovery didn't fix it for you...
And yeah FoH already pointed out that decrypt tool is useless to us.
Dark Nightmare said:
You're saying an msm reload didn't fix the device? Btw you can use the unlocked device msm tool as well as of version 9.0.11 I .
Click to expand...
Click to collapse
Are you talking about what
PHP:
Eliminater74
shared with us? if so, I tried to use back up before smt download but it fails. firehorse read data error 995.
And I didn't do the back up; I only flashed every partition with the fastboot-flash tool. I am quite surprised to see msm letting me down as well );
Can you share more if you know more?
Somehowko said:
Are you talking about what
PHP:
Eliminater74
shared with us? if so, I tried to use back up before smt download but it fails. firehorse read data error 995.
And I didn't do the back up; I only flashed every partition with the fastboot-flash tool. I am quite surprised to see msm letting me down as well );
Can you share more if you know more?
Click to expand...
Click to collapse
Na, there was another someone else had modded, it should be in the general forum, I believe it was linked in the new international conversion method, the one after my thread. If you simply flashed using the fastboot-flash-tool, then you should definitely be recoverable, attempt a msm reload, I believe you may have a usb port issue if you're having firehose failures, try using an onboard port and not the front ports.
Dark Nightmare said:
Na, there was another someone else had modded, it should be in the general forum, I believe it was linked in the new international conversion method, the one after my thread. If you simply flashed using the fastboot-flash-tool, then you should definitely be recoverable, attempt a msm reload, I believe you may have a usb port issue if you're having firehose failures, try using an onboard port and not the front ports.
Click to expand...
Click to collapse
That's weird. If I had a usb port issue it would say it during the msmdownloading wouldn't it? Msmdownload goes fine but I just can't use the readback function.
And thank you I will go and look for it!
Somehowko said:
That's weird. If I had a usb port issue it would say it during the msmdownloading wouldn't it? Msmdownload goes fine but I just can't use the readback function.
And thank you I will go and look for it!
Click to expand...
Click to collapse
qusb is weird, it would let me backup but not flash once, tried a different port and it worked fine for both, so I figured I'd suggest such, doesn't hurt to try after all?
Dark Nightmare said:
qusb is weird, it would let me backup but not flash once, tried a different port and it worked fine for both, so I figured I'd suggest such, doesn't hurt to try after all?
Click to expand...
Click to collapse
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!
Somehowko said:
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!
Click to expand...
Click to collapse
That's correct and if you're on windows 10 it may be a system update messing with the drivers, its dumb, but it actually affects the simplest of things.
Somehowko said:
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!
Click to expand...
Click to collapse
As crazy as it sounds three reboots and four different ports did the trcik!
And sincerely thank you! Although I couldn't find the modded msmtool you told me I was able to boot into the os finally.

Fresh op6t tmobile, best rom etc for pentesting platform

i have a op6t bootloader unlocked still on tmobile 10.3.3 oos. i want to flash the nethunter/andrax kernel on it so i can check em both out. i am wondering if i should bother trying to flash the international rom on it, or what might be the best rom to use as a base for a pentesting platform.
it is my first oneplus device, but i messed around with nethunter on the galaxy series and kali on maemo before it. ive just gotten the unlock token and flashed it, i tried to msm it to the international rom prior, but kept getting a 'packed image not found' type error. i guess it doesnt matter now, i can just use twrp. but any advice, or direction on what i should flash or install in what order would be Greatly appreciated, im just trying to read up on all of it as much as i can right now.
moisturerichsoy said:
i have a op6t bootloader unlocked still on tmobile 10.3.3 oos. i want to flash the nethunter/andrax kernel on it so i can check em both out. i am wondering if i should bother trying to flash the international rom on it, or what might be the best rom to use as a base for a pentesting platform.
it is my first oneplus device, but i messed around with nethunter on the galaxy series and kali on maemo before it. ive just gotten the unlock token and flashed it, i tried to msm it to the international rom prior, but kept getting a 'packed image not found' type error. i guess it doesnt matter now, i can just use twrp. but any advice, or direction on what i should flash or install in what order would be Greatly appreciated, im just trying to read up on all of it as much as i can right now.
Click to expand...
Click to collapse
Reading is good! You'll really need that as you're about to venture on a potential world of pain. I have the international version so it's been smooth sailing for me but I've read a lot about these TMO devices and either it'll work for you if you follow the right guides or it'll go south really fast. And when it does, there's an endless road back to square one. It can be an excellent learning experience and there will usually be a way out but it will require a lot of patience. If you don't have that, you might as well stay with stock. You know yourself best [emoji6]
Timmmmaaahh said:
Reading is good! You'll really need that as you're about to venture on a potential world of pain. I have the international version so it's been smooth sailing for me but I've read a lot about these TMO devices and either it'll work for you if you follow the right guides or it'll go south really fast. And when it does, there's an endless road back to square one. It can be an excellent learning experience and there will usually be a way out but it will require a lot of patience. If you don't have that, you might as well stay with stock. You know yourself best [emoji6]
Click to expand...
Click to collapse
super good to know, as it sounds like if i can get the msm flash to work, it will be just like an international one. or maybe i can twrp flash it to a newish international oos that will work well with nethunter. But i guess my first order of business should be twrp flash and pull a full backup just in case. i am indeed looking for an odyssey, ive been bricking arm devices since the nokia n800 days so im sure i can figure things out.
im thinking:
twrp
magisk
backup
flash newest internation oos (msm or twrp?)
flash nethunter/andrax kernel
install non chroot nethunter
install andrax
...
profit?
i dunno why but im unreasonably excited to get a pentesting phone running with a kernel that supports native monitor mode and packet injection
I got it all to work, with plenty of haphazard dirty flashing, and only like 3 softbricks where I had to go back to 9x with msm. So I'm on 10.3.7 with twrp, magisk, seems like I disabled encryption, cause I ran into that issue before, and I have no lockscreen code now. I doubt I could reproduce it all, but the nethunter/andrax kernel seemed to have stuck, after I got nethunter chroot installed, I verified monitor mode worked. Got andrax all installed too, everything seems to be functioning properly. Sooo many tools to play with now. It's weird, every time I did things properly, I'd end up bricking it, then I would try some convoluted dirty flash and it would work out just how I wanted it.
moisturerichsoy said:
I got it all to work, with plenty of haphazard dirty flashing, and only like 3 softbricks where I had to go back to 9x with msm. So I'm on 10.3.7 with twrp, magisk, seems like I disabled encryption, cause I ran into that issue before, and I have no lockscreen code now. I doubt I could reproduce it all, but the nethunter/andrax kernel seemed to have stuck, after I got nethunter chroot installed, I verified monitor mode worked. Got andrax all installed too, everything seems to be functioning properly. Sooo many tools to play with now. It's weird, every time I did things properly, I'd end up bricking it, then I would try some convoluted dirty flash and it would work out just how I wanted it.
Click to expand...
Click to collapse
Hey im going through some things with the install so i flashed a international rom after the last fix i did with a .bat file from another post which its running fine so far. so could you explain some details with how you went about it at least the decryption part this has me lost as in...
1= TWRP format data
2=flash all the things i need to flash
3= flash DM verity disable force encryption last
all within the twrp.img first boot? or is it all done after twrp is installed
first of all im fresh to all flashing roms and i have been reading like crazy haha just trying to clearify the missing info or lack of maybe.
moisturerichsoy said:
I got it all to work, with plenty of haphazard dirty flashing, and only like 3 softbricks where I had to go back to 9x with msm. So I'm on 10.3.7 with twrp, magisk, seems like I disabled encryption, cause I ran into that issue before, and I have no lockscreen code now. I doubt I could reproduce it all, but the nethunter/andrax kernel seemed to have stuck, after I got nethunter chroot installed, I verified monitor mode worked. Got andrax all installed too, everything seems to be functioning properly. Sooo many tools to play with now. It's weird, every time I did things properly, I'd end up bricking it, then I would try some convoluted dirty flash and it would work out just how I wanted it.
Click to expand...
Click to collapse
Dude could you please help me I can't get nethunter running for the life of me, so it sounds you flashed the kernel then flashed nethunter oos10 for the op6 using twrp but it worked for the op6t? I'm pretty new to phones had nethunter on a oneplus one but that was a cakewalk, I got a T-Mobile op6t running international
Hate to bump an old post but did anyone manage to figure out the flash order on this?
And if so care ta share I'll be forever in your debt

OnePlus 8 Pro refuses to install TWRP. Qualcomm Crash Dumps every time. Any advice?

I want to install TWRP as my recovery I've tried at least four different versions that are listed here and a few others from other links:
https://forum.xda-developers.com/t/...p-for-oneplus-8-8-pro-unified-stable.4101313/
I'm not having driver issues anymore so I'm working with adb and fastboot fine. All commands are going through fine and I've tried flashing to recovery_a and recovery_b. Factory resetting doesn't resolve the issue. Every walkthrough I find I get to says flash then boot to TWRP but every time I flash it qualcomm dumps and every time I boot to it it qualcomm dumps.
Is there something corrupted in my recovery I need to wipe somehow? If so how do I wipe it because the only command I found online that would run was fastboot -w and that didn't fix the issue either.
Honestly really annoying at this. This is my 4th OnePlus phone and I've never had so many issues flashing it.
Edit:
I have also tried to do whatever steps are needed to go back to base stock and OS and it doesn't seem to work either. Any help would be appreciated.
Edit 2:
I did it. For anyone who finds this thread in the future the MSM tool did finally work. This is the video I used in the end
(I muted it.) and the first few starts it failed. I went into the properties of the MSM exe and under compatibility checked ran as admin. I also did install the qualcomm driver at some point way before this so not sure if that helped. The MSM tool still didn't work until I started it, turned my phone off, held both volume buttons (not the power) while plugging the phone in. All the stuff online I saw had people starting the program at this point but mine had started already and was in a "waiting for device" state when it worked.
What a lifesaver. Won't be messing around with this again until TWRP is available.
Because you are unable to flash phone's Stock ROM take phone to authorized service center and let them fix it.
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Edit: not
Lossyx said:
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Click to expand...
Click to collapse
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
TheFloppyDisk said:
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
Click to expand...
Click to collapse
Meant to say it's **not** compatible with Android 11 yet.
Lossyx said:
Meant to say it's **not** compatible with Android 11 yet.
Click to expand...
Click to collapse
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
TheFloppyDisk said:
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
Click to expand...
Click to collapse
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Lossyx said:
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Click to expand...
Click to collapse
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
TheFloppyDisk said:
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
Click to expand...
Click to collapse
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Lossyx said:
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Click to expand...
Click to collapse
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
TheFloppyDisk said:
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
Click to expand...
Click to collapse
It is very sensitive to which USB port you use. For some people only USB2.0 works, for me USB3 works fine as long as it's chipset USB3. The second ASMedia controller doesn't work.
Also, use original cable, and switch off the phone completely, get MSM to the point it's waiting for device so start the download before connecting phone, then while holding the volume keys connect the USB cable and it should instantly start flashing.

Question I've tried so hard and got so far.

Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Enzucuni said:
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Click to expand...
Click to collapse
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
HermitDash said:
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
Click to expand...
Click to collapse
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Enzucuni said:
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Click to expand...
Click to collapse
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
HermitDash said:
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
Click to expand...
Click to collapse
I actually restored it but to no avail. Same errors as described
Enzucuni said:
I actually restored it but to no avail. Same errors as described
Click to expand...
Click to collapse
Welp, back to stock you go then haha ADB it to EDL then run the unbrick tool and you should be at 0
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Enzucuni said:
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Click to expand...
Click to collapse
Might not be stable on first release but yea that's in the rumor pipelines
Yeah, I think I'll wait. A12 is still really nice. Some bugs here and there but perfectly usable and battery is basically infinite.
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
You could try flashing the fastboot ROMs made by @ot_inc (it's not 100% safe for your data so make a backup in any case).
[Restore NothingOS & Magisk] Nothing Phone(1) Fastboot ROM(Full ROM) & boot.img Global v1.1.6
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.6 is available. Sorry for my poor English, I'm Japanese. https://reindex-ot.github.io/
forum.xda-developers.com
kriistofor said:
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
Click to expand...
Click to collapse
Where is the step by step ? The one that actually works ?
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
Umm.. no, you're not sounding harsh. And I've already done that: "google it" and stuff. This is why I post teh question here. This is not my first time at this lol !
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
You said, "Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm."
Where are you getting this from ?

Categories

Resources