-was on stable v0.23 with recovery v0.23.
-first stable ota v1.0 update lead to an installation error.
-according forum post i tried with manually updating recovery first to v1.0 but after that same installation error for the v1.0 rom
-saw second v1.0 ota update and thought now it is fixed, downloaded ota and installed, first boot qualcomm crasmode dump
-no chance for fastboot
-recovered phone with MSM tool to stock rom according manual from gadgetstouse com (edit: link was flagged?)
-all data lost
now i don’t know if i should try install v1.0 or v0.23??
i’m a little unhappy about such flaws in a stable version. was my first brick ever.
@elhdjrmlifq6 are you using Windows, if so, have you ruled out Drivers being an issue?
The trick is to have Windows Device Manager open alongside your “tools”. At evey step cross check with Device manager to see if a “Problem device” has occurred. In the first instance allow Windows update to try to resolve it.
unfortunately, tried installing the driver multiple different ways and no luck.
Ah yes, I did the same thing- I kept device manager open so I could tell that device was connected, etc.
One guide said to put windows into test mode which I think has been deprecated. I had to boot up from recovery to allow unsigned drivers. This got rid of the . Still no luck though.
Ive also tried 3 different types of USB ports
I spent a day and a half recently getting to grips with msm to restore a oneplus nine stuck in edl mode. When it works it takes about 5-6 mins, ha ha. Apart from the usual problems of trying a new process was my difficulty in using windows; I’m more used to linux.
Anyway, I turned the corner when I found a guide on oneplus community forum. I used the driver download from there, removed the drivers I had previously installed and then followed the instructions.
Of course it may be a coincidence that it worked when others attempts did not, but might be worth a go.
Anyone these days is using the e OS 1.0 installed via OTA without having any major issue on our OPO Nord??
I personally have the AC2003. I read few users with issues so before to proceed with the OTA update I want to be sure to not lose my data… (lazy to backup)
I currently have the 0.23-202204
Don’t do it!
At least 4 people lost everything.
My phone is permanently bricked which is a $400 loss.
The update is clearly flawed and there hasn’t really been a response from support.
You say you’re too lazy? I would’ve backed up but couldn’t figure out how to.
Definitely back up and don’t use this update
I think you are on the right track to try to optimise the “Device | cable | usb port | PC hardware” chain of things. But I wonder exactly what you meant by the quoted phrase? From your PC you really only want the port soldered to the motherboard, avoid any hub (bearing in mind some PC / laptop can use an internal hub to power one or more ports).
I would also try thinking of trying to borrow a different PC. This might seem extreme, but that end of the “hardware chain” may have unknowns which the drivers cannot accommodate. Just a guess.
Ah, I can’t see what I quoted…
My machine has a regular usb 2, usb 3, and a usb c. Tried connecting through all of them, but no luck.
I did use this machine for the initial conversion of this phone to /e/ os so, I would think that it would work for the msm tool but maybe not.
Fortunately I still have my Galaxy S9 as a backup
I do not mean to ‘dis’ your PC! I guess I am addressing the idea that things that have to get incorporated into these advanced tools and drivers is ‘support for every PC’.
More modern machines and ones offering more “advanced” (in general consumer use terms) USB capabilities might suffer from being able to do one “talking to Android” job and fail at another.
I think Windows tends to hide from the user, or deny, this type of weakness. Additionally Windows is not primarily designed for cross platform work. (Personal view, ofc!)
Thank you for sharing this guide. It worked for me without any problems. I am now running V1.0 stable on my OnePlus with the update that made the problem (not updated from 0.23).
And the OnePlus Nord install guide was updated (correct me if i’m wrong): Install /e/ on a OnePlus Nord - “avicii”
The part " Ensuring all firmware partitions are consistent" wasn’t there when i installed my phone. I guess there is the problem.
“Problem device” has occurred. In the first instance allow Windows update to try to resolve it.