Database Users

2017g DFU mode investigation

This thread is for users who have a 2017g model that is stuck in DFU mode.
If you would like to assist in the investigation, please reply here. I'll be sending links to test programs to try to diagnose and repair devices.
With any luck, we can get the devices back to normal within a few days.

Reserved

I had this problem, but luckily I could send it back and get a new one on warranty. I was very careful when unlocking the new one ?
Skickat från min ZTE A2017G via Tapatalk

Can more people who are stuck in DFU mode PLEASE contact tennear? I worked with him before and he really knows what he is doing. He's the only one who I think could be able to help you restore your device to working state.
Please help him, so A2017g users like me know they have a trick up their sleeve in the case the BL unlock goes awfully wrong
Thank you.

@tennear keep us updated. I'm planning to give up root in order to get this week's B08 update and i'm not sure if flashing the system with twrp will go smoothly.
Thank you for you work and dedication to help other people.

I have two people that are able to help now. But more is always better. If you have a G model and you can access DFU (regardless if you are bricked or not), you can help test. Linux is my preferred OS, but I can also build for Win64 if needed.

razorsbk said:
@tennear keep us updated. I'm planning to give up root in order to get this week's B08 update and i'm not sure if flashing the system with twrp will go smoothly.
Thank you for you work and dedication to help other people.
Click to expand...
Click to collapse
If you are Lock bootloader and have TWRP you CAN flash B08 , just need to mod. The updater_script in other for the B08 to be install, but YOU WON'T BE ABLE TO ROOT unless you unlock bootloader and I'll be posting something about that later today or coming days.

DrakenFX said:
If you are Lock bootloader and have TWRP you CAN flash B08 , just need to mod. The updater_script in other for the B08 to be install, but YOU WON'T BE ABLE TO ROOT unless you unlock bootloader and I'll be posting something about that later today or coming days.
Click to expand...
Click to collapse
I'm rooted without unlocking bootloader (tenfar's method).
So you are saying I can flash the upcoming update safely from TWRP by editing updater script and removing getprop & assertprop lines from it?
I also have system modifications.
Sent from my ZTE A2017G using Tapatalk

razorsbk said:
I'm rooted without unlocking bootloader (tenfar's method).
So you are saying I can flash the upcoming update safely from TWRP by editing updater script and removing getprop & assertprop lines from it?
I also have system modifications.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
Ok, I don't want to go off topic here, but YES you'll need to edit updater_script and look and bookmark if possible my thread about Updates ,I'll be posting B08 as soon the full update hits ZTE site. If you want to talk about Updates post there , so we can keep this thread on topic.

I agree. See you there.
Sent from my ZTE A2017G using Tapatalk

tennear said:
I have two people that are able to help now. But more is always better. If you have a G model and you can access DFU (regardless if you are bricked or not), you can help test. Linux is my preferred OS, but I can also build for Win64 if needed.
Click to expand...
Click to collapse
I have a G model and I am using Linux (based on ArchLinux). I can use Windows 10 if needed, so OS should not be a problem.
So if you need some testing, I can help

Hi, I would love to help,
I have a G model and I have TWRP and unlocked bootloader but u can access DFU mode
I am using windows

I'm afraid that I have not been successful getting out of DFU mode. I have tried several things, but the device refuses to switch into EDL mode.
According to the user who has a bricked device, he got bricked by running "axon7backup -d" without any image files present. The tool wrote something to both boot and recovery partitions. I don't know what that something is -- zeros, random data, ... who knows.
So it seems that if you are careful and only flash recovery properly, the device should not brick. But I cannot test -- someone else will need to confirm.
Now that this investigation is concluded, I will be posting my own tool shortly.
Always remember: to avoid bricking your device, never flash both boot and recovery at the same time.

^^Is there even a reason to flash the boot/kernel? The main reason why most of us would use the axonbackup tool is to flash twrp.

gpz1100 said:
^^Is there even a reason to flash the boot/kernel? The main reason why most of us would use the axonbackup tool is to flash twrp.
Click to expand...
Click to collapse
The only reason why tenfar had the tool to Flash boot is because he had the boot sign and pre-rooted for Lock bootloader units.

^^Got it. I thought about keeping the BL locked, but decided unlocking it would cause fewer headaches and be less restrictive.

That is correct, there is no real reason to flash your boot partition now that the images provided by tenfar are not compatible with the latest updates from ZTE.
However, the real danger remains: if you run "axon7backup -d" with no files to write, it is reported to write bad data over both boot and recovery and brick your device.
I highly recommend using my tool instead. I can guarantee that it will never write both boot and recovery in the same session.

tennear said:
That is correct, there is no real reason to flash your boot partition now that the images provided by tenfar are not compatible with the latest updates from ZTE.
However, the real danger remains: if you run "axon7backup -d" with no files to write, it is reported to write bad data over both boot and recovery and brick your device.
I highly recommend using my tool instead. I can guarantee that it will never write both boot and recovery in the same session.
Click to expand...
Click to collapse
The command help indicates -d is to dump only. My understanding is nothing is written to the phone when reading from it? Are you saying that's not the case?

gpz1100 said:
The command help indicates -d is to dump only. My understanding is nothing is written to the phone when reading from it? Are you saying that's not the case?
Click to expand...
Click to collapse
Yes, that is what I am saying. According to a PM that I received, the user ran "axon7backup -d" without any other files in the directory. The tool flashed something to both boot and recovery partitions. No idea what it flashed. But then the device was bricked. And because 2017g cannot enter EDL mode directly, there is no way to unbrick.

hi i have china version of axon 7 A2017 and have the same problem with my device (stuck in dfu mode after Flashing SuperSU).Will there ever be a way to fix this problem? I am depered :crying:.

Asus Zenpad 10 (Z300M) Boot Loop after update

Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you

Same problem. When WiFi is ON.
When I put WiFi OFF - the tablet works fine.
Last firmware doesn't help, reset too. I think there is no solution at this moment, except maybe to flash an old firmware with Android 6.
I'll replace it in store. No idea about Asus control quality of their firmware... but this problem is pretty common.

???
Belnadifia said:
Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you
Click to expand...
Click to collapse
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach

coolbeans2016 said:
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach
Click to expand...
Click to collapse
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.

I'll give you that
diplomatic said:
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.
Click to expand...
Click to collapse
The link on the Z380M is what threw a flag for me because that Asus tab isnt rootable. If this is some combo of slipups between tools & devices that lines up just right to get TWRP on its not described very well in the OP. Using the 5.132 (?) you can not readback with that option.ini file.... so what am I missing? The bootloader unlock app isn't written for this tablet is it? written for the zenphone 2 (3)?

Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.

Just want to mention for anyone else struggling with this issue, what fixed it for me:
I found the reboot would only happen when wifi was turned on, and even more weird, it would only happen when connected to specific wifi networks. After doing a factory reset I was able to set it up again by tethering to the wifi on my phone. I then found that I actually was able to connect to the problematic wifi network but only by setting a static IP! This has completely resolved the issue for me.

Thaniks
diplomatic said:
Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.
Click to expand...
Click to collapse
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls

coolbeans2016 said:
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls
Click to expand...
Click to collapse
Ohhh... ok. No problem man. Just please get your facts straight before posting next time. Good luck. BTW, I'm not sure if you saw this post on the TWRP thread from 2 weeks ago. You didn't reply.
diplomatic said:
What is the error that you got when trying to flash it? Can you post a screenshot of the Download tab along with the Help/About dialog box?
Click to expand...
Click to collapse

Oneplus 6T bricked in fastboot loop...Please help!

Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!

OP6TNewb said:
Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!
Click to expand...
Click to collapse
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.

Problem SOLVED!!!
justibasa said:
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.
Click to expand...
Click to collapse
Thanks for your follow up.
Just want to let you now that I fixed it using the Stock Fastboot tool posted here
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
I just did exactly as instructed; my phone was already stuck in fastboot so I plugged to my PC and ran the flash-all.bat file. I really didn't think it would work because the phone did not seem to respond or do anything. I went to the toilet, came back and it was reset to factory!!!! Amazing.
Thank you so much @mauronofrio for posting this amazing tool. You saved my bricked phone! I sent you a donation for your assistance. Thanks again.

Just for future reference, as long as you can get this phone into fastboot, you should be fine. For now that's where all the flashing happens until we get a custom recovery.
But I'm glad to hear you fixed it lol

Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.

Pain-N-Panic said:
Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.
Click to expand...
Click to collapse
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.

OP6TNewb said:
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.
Click to expand...
Click to collapse
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?

Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
They probably have gone off to brag to their friends about what happened. Lol
I, too, am curious about what he did. It's been so long since I first began tinkering, but certainly remember some times I goofed.
Sent from my ONEPLUS A6013 using Tapatalk

Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!

OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
I forgot to mention one thing which may also be the reason. Initially, before using Adam Conways instructions, I started with the steps on High on Android (Max Lee) for the OP6 but on their download page, I mistakenly downloaded the twrp zip for the 5T and I flashed it. This initially cause the device to brick but I got it back into fastboot and into recovery and thats when I flashed the OTHER twrp file above. After I did this, I could no longer get into recover and was stuck in fastboot only.
So you can see that I made multiple errrors and I am not sure which one lead to what. Thank goodness OnePlus is friendly to rooting so I could save the phone!

OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
Ah, I see. Looks like you flashed a kernel zip instead.

Im not a noob, but have been so out of practice with the latest Android ROMS and flashing and the changes in the partition arrangements. I managed to soft brick my phone as well and this post totally saved the day! Mauronofrio totally deserves a donation and I also gave one.
Thanks XDA! This place has saved me many times and helped me get the most of all my Android devices!

Hey guys. i am also no noob in flashing/rooting my devices.
Don thishundres of times.
Today my OP6T has shown an Magisk update (before it was 21.4 + Magisk Manager) and now it showed the popup to update -> done and error "bad image format" (i think for the kernel). Rebooted and now i am stuck in the same fastboot bootloop.
Tried to boot up TWRP with "fastboot boot tmrp.img" sadly it doesnt boot.
Any hints how i can recover my phone without wiping everything?
maybe @mauronofrio has an idea?
thx a lot

Other users facing the same issue with magisk 22, see here: https://forum.xda-developers.com/t/...oot-roms-for-oneplus-6t.3862516/post-84553217

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 ?