Hello community!
So I've downloaded OTA update and went to Magisk to install it in inactive slot as usual, but suddenly, I'm stuck in fastboot loop. All it says is
Boot reaseon: fs_mgr_mount_all unable to parse kernel log
I've tried to clear cache but didn't work.
Please help me, because I'm waiting for important call and I'm with no phone now
Thank you in advance
Every step you take now has the potential to kill your phone. Because i guess your tried to update to A12.
Please read this:
[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
In my opinion the only thing you can and should do now is to use MSM Tool. But you will loose your data.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
The only thing i would try is to boot the boot.img from the ota you installed recently or from the version you used before.
Related
UPDATE: I SUCCEEDED IN FIXING IT.
Hello Everyone,
I recently got a Nokia 5, used it for about 2months then the 8.1 Update came which messed up the camera
[camera app always crashing]; It was working perfectly before I updated to Oreo 8.1 so I decided to change
to Nougat.
I wasnt aware there were protocols to follow before downgrading and then went ahead to Flash Nokia5_Android_8.0_Oreo_v5.220_Update.zip via ADB. It got to (47%) and gave out a sort of error, then exited to reboot the phone, since then my phone has been stuck at "No Command" Screen.
I've tried flashing with December 2017 Update before Flashing Finally with Nougat 7.1 ROM using OST LA 6.0.4, but it stops at a point while flashing o OST saying "Connection Failed, 0xc6da" . I am frustrated and tired plus I have limited data to keep changing roms. Please Can anybody help me out of this nightmare? Please! Please!
Please ask me anything, I'll answer. Thanks in anticipation!!!!
I attached a snapshot of what information my recovery menu has.
Hi. Recently, I did all it was necessary to install CyanogenMod 14.1 on my Honor 8 Lite PRA-LA1 including unlocking the bootloader, installing TWRP and others. Now, I want to revert to the stock OS. The problem is even by searching on and on, I wasn't successful. For the sake of one time clarity for me and other people that may need to do the same things as I want to do, please guide me on how to revert to the stock OS (Android 7 or the new EMUI 8) of my particular device as I already feel hopeless to get to that point. I came across many broken download links, incomplete and ambiguous guides and others.
Thanks a lot.
Hi, you can use HURUpdater to return to stock. Please see the link below:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
I have used it with success.
Good luck.
I used Huawei erecovery and it automatically does everything. Wait 20 minutes after installing and it will do several bootloop
Hi everyone,
I had issues with the update of my OnePlus 5 as stated on this thread : https://forum.xda-developers.com/oneplus-5/help/oneplus-5-update-fails-t3866533
I tried the solutions that were given to me but it wouldn't work, since TWRP kept returning ERROR 7.
I finally managed to install OnePlus5Oxygen_23_OTA_040_all_1811051816_c6670cf.zip thanks to twrp-3.2.1-1-cheeseburger.img without getting any error but my phone got stuck at the "Dots turning" logo when I boot.
I looked around a lot trying to find a solution and as far as I understood, it may be due to the addition of Treble to OnePlus. I tried to wipe everything thanks to TWRP and flash my phone back to OxygenOS 5.1.3: OnePlus5Oxygen_23_OTA_036_all_1806131715_b5381c0ef26d9e.zip but it's still stuck.
Could anyone help me ?
Thanks a lot
This guide will help you: https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
A HUGE thank you ! It worked perfectly.
Note for people who might see this thread : it locked my bootloader, I had to unlock it back (and wipe all data). Flashed TWRP and Magisk, everything works perfectly
Hello everyone. it's been a week that I work on this problem but I can't solve it myself despite having made numerous attempts. the situation is this: installing lineage os when the system restarted the 6t got stuck in the bootlader. I installed qualcom drivers from here
https://androidfilehost.com/?fid=11410963190603879743
and downloaded msm https://androidfilehost.com/?fid=17248734326145733776
I disabled windows secure boot and installed optional qualcomm drivers on windows... the 6t is correctly recognized as Qualcomm 9008 in the device manager in port 9 but I also tried in the 7 and it is always correct.
I tried other divers (after removing the previous ones) and other versions of msm but I always give the same error : param preload... device not match images.
I have read many discussions and tried many things but I can not solve. someone is willing to help me. Thanks guys.
I also tried uninstalling the drivers and reinstalling these:
QUD.WIN.1.1 Installer-10037.3 Setup.zip | by Dark Nightmare for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
using this version of msm:
6T_MsmDownloadTool_v4.0.58_OOS_v9.0.12.rar | Tool by iaTa for OnePlus 6T
[TOOL] 6T MsmDownloadTool v4.0.58 (OOS v9.0.12) https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
androidfilehost.com
the problem is not solved but changed to: (recording dawnload time in red) images do no match with teh phone!
i can't figure out if it's a msm or driver version problem or maybe something else ...
I don't know what the exact problem. If you have installed magisk or modify something to your phone, sometime msm will fail to recognized or flash..
rom
But if your phone can boot into fastboot mode, try to flash fastboot ROM it might help
Fastboot rom.
[ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if...
forum.xda-developers.com
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
sun-k said:
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
Click to expand...
Click to collapse
if you get a warning in MSM tool: 'images do not match the phone', you are flashing the wrong image. That could happen to a branded phone. So, if you have a T-Mobile branded phone, either convert it to Global first (that tool has 'device check' disabled), or use T-Mobile MSM tool.
Your other option is to contact OnePlus support and they can help you remotely. I got into a similar bind with my 6t a year and ½ ago and nothing I was attempting worked. It was very frustrating. Ultimately I contacted OnePlus and they got me back up and running in no time. I was a little upset that I had to resort to relying on the manufacturer but also relieved to have a working device again and also thankful that it was an option, even if I would've preferred to have fixed it myself. Good luck.
PS - something to be aware of, I'm not 100% sure that it was a result of OnePlus' involvement/remotely flashing the device but somehow I ended up with a new/different IMEI. This created a world of difficulty with my cellular carrier (VZW) - I had finagled a OnePlus 8 out of them by citing manufacturers defect (I had coverage through VZW despite purchasing the phone directly from OnePlus) but they said the OnePlus 6t they received had a different IMEI than what they expected to receive, which makes absolutely no sense and this is the only possible explanation I could come up with. It ultimately saved me from having to pay for retail for the OnePlus 8 but not without a lot of headaches in between. Oh and lemme just say that having a VZW OnePlus with a locker bootloader sucks, I can't wait to get away from this thing and back to something I can root (I only pulled this maneuver in order to buy myself some time as I wasn't thrilled with the 1+9)
I woke up to see my phone bricked (Wouldn't switch on or fastboot). USB debugging was off so there was no way other than test point method (As i went through various forums). After some effort and following tutorial of flashing firmware using QPIL; my phone switched back on with all data intact. After 4-5 hrs of usage, screen suddenly jammed with discoloration and phone went dead again. SInce then i'm trying to do everything i find doable but to no use.
Latest QFIL logs are attached below.
This is method that i followed for 1st successful and later failed flash https://miui.blog/redmi-note-7/unbr...623217910c3c6800fac97f9a13ef43f#comment-15595
I tried MIUI 10, 11, 12 Global.
Will be grateful if someone can help since i have lot of imp data on my phone.