So I woke up this morning to a OnePlus updater notification saying that there was an update, but when I looked at the update it said i was up to date with the April Security patch. Thinking that OOS12 did some auto update thing I went to go update Magisk via OTA update. Well I then also saw Magisk had an update too and like an idiot i updated direct then in auto pilot mode updated OTA and rebooted. When it rebooted it dropped straight into recovery with this error: fs_mgr_mount_all. I didn't really think it was bad as i thought it was just Magisk messed up the boot.img so I grabbed the latest full zip for OOS12 and pulled the boot.img out and flashed it. Well it got worse, now is stuck on the "The boot loader is unlocked..." screen. When I go to fastboot I can't full flash the OOS12 image some reason the as the critical partitions are locked but when i unlock them they are unlocked. At this point i'm trying to recover the phone to a usable state befor i progress to rooting and such.
Watch out!
Read this before you continue:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
I would use MSM only now and stay on OOS11. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
if you need to recover your data read the first link very carefully.
Unfortunately I couldn't recover my data, mainly photos. But I got it back with the MSM tool.
Hello
My last OxygenOS update offered by the Oxygen Updater app went wrong, and it's my fault.
I exited the update before it was fully installed.
I tried to restore a very recent Nandroid backup with TWRP but the operation failed.
I then tried to factory reset the device but now the OnePlus 8 Pro does not restart: there are just the 2 white dots that revolve around the red dot.
I cannot connect the device to the PC because it is no longer in “developer” mode.
So I can't use ADB or Fasboot commands.
Do you have a solution so that I can copy the latest official firmware (OxygenOS 11) to the device and reinstall it from the "bootloader" or "recovery" mode?
Thanks a lot for your help.
Best regards
nadnan said:
Hello
My last OxygenOS update offered by the Oxygen Updater app went wrong, and it's my fault.
I exited the update before it was fully installed.
I tried to restore a very recent Nandroid backup with TWRP but the operation failed.
I then tried to factory reset the device but now the OnePlus 8 Pro does not restart: there are just the 2 white dots that revolve around the red dot.
I cannot connect the device to the PC because it is no longer in “developer” mode.
So I can't use ADB or Fasboot commands.
Do you have a solution so that I can copy the latest official firmware (OxygenOS 11) to the device and reinstall it from the "bootloader" or "recovery" mode?
Thanks a lot for your help.
Best regards
Click to expand...
Click to collapse
Hi there
Can you just wait for it to run out of battery, while charging try to enter EDL mode?
Thank you for your quick return.
I don't know this "EDL" mode.
Do you have a link for a tutorial on this?
Thanks again!!
What is EDL Mode? How to Enter EDL Mode on Any Qualcomm Device
This guide will have an in-depth look at the EDL Mode on Qualcomm devices and its associated importance. Android devices are always known to be at the
www.getdroidtips.com
Here it is
Edit: Try this also: https://www.xda-developers.com/oneplus-8-pro-unbrick-tool-now-available/
Thank you, thank you, thank you very much...
Best regards,
Jean-Noel
Related
Hello,
I own a Huawei P8 L09, bootloader unlocked, rooted and with TWRP recovery.
I tried this morning to flash a new rom using TWRP recovery.
Problem is that I do believe I wiped to many partitions and I ended up with a bootloop.
I could at first access 3 times the emui erecovery (btw, Wifi recovery failed) but not anymore (is it related to the battery level ? I don't know how much I still have)
Following a lot of threads here and on some other forums (I've been searching now for approx. 7 hours...) :
I downloaded a update stock ROM (B170 something), I extracted Boot, System, Recovery and Cust
I entered bootloader mode (it's the only mode I can go to; recovery No, Download mode neither)
and on my computer I typed in the cmd "fastboot flash recovery recovery.img" same with system, cust and boot.
All of them said "Okay" but the bootloop is still there and I can't acess any other mode or shut the device off.
Also, my bootloader indicate that i'm "unlocked" but when I try to do something as :
"fastboot erase cache" it says "remote: not allowed" or something like that.
I tried the SD card flash method but I can't even acess the 3-button mode (doesn't work - bootloop again).
Finally, I've got 2 questions :
1) Is there a solution ? Is there/was there anybody in the same situation ?
2) Does the battery level influence wether I may or not enter any mode ? like b.e. under 30% I can't access recovery or something like that ?
Thanks in advance for your help and sorry for my bad english.
Greetings from Belgium !
Jules
Hi!
I have the same situation as you do, All i know is that you can access the eRecovery only if you're plugged in.
But it's completely useless. Have you found any solutions yet?
Edit:
i struggled and i'm still struggling but i figured out that I need the recovery and boot img of the version i was on previously. In my case that is B350.
The main mirror is down but i managed to find another one: https://mega.nz/#!NAcgQY7Y!I4eRfkaq62J31csv_wZ8_nTzmUbWPX71JUicDysjus8
after flashing them i was able to partially flash (using vol+-&pwr) B170 (it only went up to 90% with my USB attached, fails without USB)
At my surprise it booted B170 even if it didn't complete, however right now it keeps rebooting every minute. I'll update if i manage to fix this
I have the same problem as you both. To flash boot.img and other files by fastboot we need to unlock bootloader. To unlock bootloader we need to have Imei, Product Id and SN, but I can't read it because phone won't turn on.
Anyone know how to get this info?
you can read these info from the packaging box!
I managed to fix my issues (i believe) by continuously flashing and flashing versions. I never really managed to fully OTA update to 100% due to some "CUST error" but from B350 i managed to "update" to B170, then to B200, then to B321a.
Now i just installed TWRP and rooted it and on the process of installing xposed (if possible).
I wasted a good 6-7 hours on everything already
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
TukAliveFra said:
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
Click to expand...
Click to collapse
you gonna pay for the repair..
Hi all,
I'm hoping someone can shed some light on this problem ..
Background:
- Was running Oxygen OS and went to update it to the new beta, booted into TWRP, flashed the file and rebooted - nothing happened, black screen with a constantly lit blue LED.
- Back into recovery but it didn't ask me for a pattern so it no longer recognised the encrypted partitions.
- Ah well, erased everything a few times and booted back into recovery to flash a new ROM, TWRP loads but no longer responds on the touchscreen, it's stuck at the "swipe to allow modifications to system partition" screen
- booted into fastboot, reflashed TWRP, same deal, Tried all 3 available versions but no difference. Also tried the clockworx build.
- flashed stock recovery and tried to sideload the rom but the first time it bombed out at 48% or so, now it just stops with "Xfer 0.0%" ..
- Saw this thread here https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169 and downloaded it but the MSM tool does not recognise any connected device even though I have "Qualcomm HS-USB QDLoader 9008 COM23" in the device manager
I'm going pretty nuts now so any tips appreciated :/
Cheers
K
Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!
on my phone TWRP shows no files on in any folder. can you pls help?
krrunch said:
Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!
Click to expand...
Click to collapse
Hi! I believe that I am in the same boat as you were. On short: was rooted & wanted to stock. Flashed stock recovery & last OS from oneplus site and got stuck in boot. Afterwards I was no longer able to see my device in the stock recovery adb install....
Can you give me a hand please! Thank you!
Edit: Got it to work with the qualcomm method
Hello,
You should install Hydrogen OS to unbrick your phone.
After that install TWRP and then install the full rom OOS 5.0.4.
Urgent help needed as I'm leaving the country at the end of the week o any help is appreciated!
Just successfully rooted my device:
Black, Unlocked, PRA-LX1, UK, Dual SIM
After doing so successfully, I attempted to flash LineageOS from the following link:
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-lineageos-15-1-hi6250-devices-t3811583
Although when I completed Step 6 on the Installation guide and rebooted the phone, I started seeing the message:
------------------
ERROR MODE
Attention!
Please update system again
(Green Android picture)
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
------------------
Despite this, I didn't receive a box with my phone due to being second hand, and I didn't see the model number on the receipt as it was from a reselling store. I didn't remember to note down the specific model number
It'd be extremely helpful if someone could possibly help just from the device description above as I'm not sure if it's safe for me to just attempt to flash every stock rom for every other LX1 device out there.
---------------------------------------------------------------
Update:
To restore this, I connected via fastboot with a working USB & flashed an original stock recovery in the video found here
(Just in case their download link ever goes down, I have uploaded the same copy to my MEGA, found here)
The recovery installed fine when using the command
fastboot flash recovery oeminfo.img
Click to expand...
Click to collapse
Whenever trying to flash any other recovery such as twrp before this fastboot stuck on a loading icon.
The stock recovery seems to be downloading the original firmware, too.
PRA-LX1C432B202 is presumably the model.
Both the bootloader and FRA were unlocked when everything else was inaccessible.
Looks like the custom ROM's recovery that you've flashed is not compatible with PRA-LX1. Try to flash stock recovery. If not working, then flash stock firmware.
Thanks @Botar230!
I didn't see your comment until just now after deciding to edit this post since I've gotten a step closer to restoring my device.
Your solution was the method I used although I didn't know my phone model, so I found a random solution which just worked for my device, and the eRecovery seems to be downloading the stock firmware anyways. Thanks again
Before flashing this lineage os you should update to EMUI8 to get treble support, i suppose you was running EMUI5, hence the error mode.
Ok, so I’m trying to fix this phone my friend messed up like a year ago and then gave up on..
Huawei P10 Lite
Build No: WAS-LX1C432B183
Bootloader: unlock
FRP: unlock
Rooted (or used to be I guess)
These are his notes from back then:
Flashed an unstable Lineage build and provided the wrong vendor.img –
tried to flash stock Nandroid backup through TWRP, which failed, phone was still running Lineage. Bugs got worse every reboot, finally stuck in bootloop on Lineage booting screen. Then did a full wipe and flashed stock ROM again - update_data_full_public.zip worked, update_full_WAS-L01_hw_eu.zip failed ("error:9")
finally flashed vendor.img the same way as with the wrong file in the beginning dd if=/external_sd/vendor.img of=/dev/block/bootdevice/by-name/vendor
now device can't mount /vendor anymore and bootlooping on the “ur device can’t be trusted” screen
Ok, so now I honestly don’t know what the last command actually does or if he got it wrong, he can't remember where he got it from and so far I didn't really find anything on it either..
I can now
• boot into erecovery, which starts but fails every time ("file does not exist"),
• do 3 button method, which gets to 5% then stuck again and returns to bootloop
• fastboot flash just about anything successfully according to logs – still bootloop
• use Unbrick option in the Multi Tool (which does the same as far as I can tell), again successful according to logs but still bootloop
• get into TWRP, flash stuff from there (stock, Lineage), also success but no change
I keep getting “failed to mount /vendor” in the logs though, and still can’t mount /vendor from TWRP and it says it’s 0MB.. I honestly don’t dare messing with partitions on my own as I’m not sure what the exact problem is..
Can someone please help?
Thanks already (and sorry this is so long..)
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Dantheman221 said:
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Click to expand...
Click to collapse
just download the Full OTA update in the thread section.
must downgrade first ur recovery to nougat then install update via recovery.
You can use TA-1021.
If you want Nougat Ver. then use Nokia OST.
Dantheman221 said:
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Click to expand...
Click to collapse
my Nokia 6 phone is also bricked. Please share if you find a solution.
Dantheman221 said:
I believe we all know here how hard flashing Nokia 6 phones are... they are unbelievably a PITA.
I have a TA-1025 Nokia 6, 7.1.1 Nougat. I have been trying to fix it for 3 days now with no success. Originally tried to reflash stock boot image at first with little success so I could flash Magisk. Ended up wiping out entire System partition and trying to reflash, getting nowhere. I then flashed a B02_Homebrew.zip which ended up with stock recovery and no root at all (and no ability to flash magisk despite having unlocked bootloader. great.) Downgraded bootloader again and am now stuck and unsure how to proceed.
Note I CANNOT get QFil to work without EDL mode, which requires me to tear my phone apart.
Any suggestions? Does anyone have any certified knowledge of how to fix and reflash stock Nokia 6? I don't want to take it to a dealer because they will update it and make it unrootable (and probably won't be able to even touch it since bootloader is unlocked.)
ATM, all I can boot to is TWRP recovery or Download Mode.
Help?
Click to expand...
Click to collapse
First flash stock recovery, then boot into stock recovery and flash latest OTA
Link for latest OTA got from Telegram (TA-1025 ) : https://android.googleapis.com/packages/ota-api/package/5d91fc596557fecf1ba49b9321b446c64e3acd06.zip
Note :Your bootloader will be remained unlocked. don't worry
Sharashchandra said:
First flash stock recovery, then boot into stock recovery and flash latest OTA
Link for latest OTA got from Telegram (TA-1025 ) : https://android.googleapis.com/packages/ota-api/package/5d91fc596557fecf1ba49b9321b446c64e3acd06.zip
Note :Your bootloader will be remained unlocked. don't worry
Click to expand...
Click to collapse
I'm stuck in EDL mode now, any fixes or tips on how to flash/patch? QFIL is saying 'Failed to switch to EDL Mode'
Dantheman221 said:
I'm stuck in EDL mode now, any fixes or tips on how to flash/patch? QFIL is saying 'Failed to switch to EDL Mode'
Click to expand...
Click to collapse
Is phone is totally dead?? what you are getting when you insert charger? how pc is detecting your device (go to device manager)?
Sharashchandra said:
Is phone is totally dead?? what you are getting when you insert charger? how pc is detecting your device (go to device manager)?
Click to expand...
Click to collapse
It shows up as a QualComm COMM port device. But before you get your hopes up, every time I have tried to flash it, it says "Failed to switch to EDL mode" :-/.