Database Develop

Mi5 dead! please some ideas!

Hi all,
I going to tell you the complete story and any ideas orsuggestions will be appreciated.
I bought my mi5 in July. It came with a fake ROM but Ichanged it to OFFICAL GLOBAL STABLE .
Since then, I used the device perfectly fine, and follow theMIUI forum regularly.
Then in November I applied for betatesting Team and theyaccepted me. As my bootloader was still locked, I tried option one from abovetutorial, so I directly downloaded in my phone the GLOBAL DEV ROM and Ichoosing the package I started using Nougat for about a month, more or less.
Then, the tragedy happened. I was in a bar, having my phonein my trousers back pocket, and I set down that way. One minute, no more. Thephone´s battery was around 70%. When I realized I quickly took it but it wasnot able to turn on… Nothing pressing power volume + or any combination… I came home and let it charging all night (wallcharger) and nothing the morning after.
I tried to connect it to my PC but nothing happened in the screen,but pressing Power Volume+ the Windowsdevice Manager recognized it as “Android phone”, so after reading some threads about bootloader issues I decidesto flash it. I requested permission and then flashed it with the latest CHINADEV version. The flashing was completed, but the phone still not turningon. NEXT STEP: Local Technical Service.
They had my phone during a week. They tried to change thescreen, nothing, the battery nothing, and I don’t know which other tests theyperformed but they called me back to tell they were not able of doing nothing.
Having the phone back at home, now I was not able to get thePC seeing it as Android phone again. Nothin. Desperate me, I continued to read in internet and found in XDA a video where basically, you open the phone (remove back, and some screws),short two pins, and the PC is able to see it through the Qualcomm USB driversin EDL mode. Then flashing IS POSSIBLE. That is true. I am able to flashing,and I have tried CHINAs, GLOBAL, older ROMs about a dozen. Always the flash processsucceed, but the phone still not turning on.
After flashing I let the phone the whole night plugged inthe PC usb. Nothing
Now is plugged again to the wall charger, but nothing.
There are many threads with different solutions, so guys,please, anyone with a good idea to try??
Many Many thanks in advanced

https://forum.xda-developers.com/mi-5/help/bricked-mi5-t3528810
Read this and
Use only the versions mentioned

this device is just a chinese junk i regret bought it , just after 2 days i bought it got hard bricked .
anyway flash 7.2.4 and if phone didnt boot use 3 button ( up + down + power ) for 1 minute or more and it must boot , it did work for me .

I just got brick yesterday and followed those instructions. It really worked. I was finally able to flash china dev 6.11.10. Latest dev said just "missed hello packet".
MiFlash version 2016.04 and china dev 6.11.10 was right combination for me. I connected Mi5 to PC while pressing vol- and power buttons, then I released them. I opened miflash, selected rom and chose "flash all". Flashing was completed. I tried to power on my phone pressing power button but nothing. But when I pressed vol- and power, I was able to get to fastboot mode. Rest is history. I flashed TWRP, booted to it and flashed LineageOS again.
Hope it works for you too!

xmmn said:
this device is just a chinese junk i regret bought it , just after 2 days i bought it got hard bricked .
anyway flash 7.2.4 and if phone didnt boot use 3 button ( up + down + power ) for 1 minute or more and it must boot , it did work for me .
Click to expand...
Click to collapse
Which 7.2.4 please??

[email protected] said:
Which 7.2.4 please??
Click to expand...
Click to collapse
hope it work for u . i read some people + me got device booted with this .
gemini_global_images_V7.2.4.0.MAAMIDC_20160129.0000.14_6.0_global
you can download from xiaomininja just search in google

xmmn said:
hope it work for u . i read some people + me got device booted with this .
gemini_global_images_V7.2.4.0.MAAMIDC_20160129.0000.14_6.0_global
you can download from xiaomininja just search in google
Click to expand...
Click to collapse
not worked

Nbkdnssr said:
I just got brick yesterday and followed those instructions. It really worked. I was finally able to flash china dev 6.11.10. Latest dev said just "missed hello packet".
MiFlash version 2016.04 and china dev 6.11.10 was right combination for me. I connected Mi5 to PC while pressing vol- and power buttons, then I released them. I opened miflash, selected rom and chose "flash all". Flashing was completed. I tried to power on my phone pressing power button but nothing. But when I pressed vol- and power, I was able to get to fastboot mode. Rest is history. I flashed TWRP, booted to it and flashed LineageOS again.
Hope it works for you too!
Click to expand...
Click to collapse
im not able to find the rom... could you help me?

[email protected] said:
im not able to find the rom... could you help me?
Click to expand...
Click to collapse
Sorry, it was global dev 6.11.10 that I used, not china dev.
I downloaded it via this link: http://xiaomininja.com/2016/11/11/m...1-10-is-out-download-it-here-for-your-device/

Nbkdnssr said:
Sorry, it was global dev 6.11.10 that I used, not china dev.
I downloaded it via this link: http://xiaomininja.com/2016/11/11/m...1-10-is-out-download-it-here-for-your-device/
Click to expand...
Click to collapse
Thanka for your hel but finally not worked...

Did you already tried to pressing and hold vol up + power button then at the same time repeatedly pressing vol down button until mi logo appear..?, id not yet..just try this method repeatedly.

JJeamy said:
Did you already tried to pressing and hold vol up + power button then at the same time repeatedly pressing vol down button until mi logo appear..?, id not yet..just try this method repeatedly.
Click to expand...
Click to collapse
I am trying that but screen is istill black.. maybe is a hardware issue? it is weird having flash working fine, isn´t it?

[email protected] said:
I am trying that but screen is istill black.. maybe is a hardware issue? it is weird having flash working fine, isn´t it?
Click to expand...
Click to collapse
Yup..it's weird thing...i suspect there's a hardware issue too..
But anyway..did you already tried to flashing fastboot rom with QFIL (qualcomm tool) too..?, if not yet..just try it..you can follow tutorial from this youtube here , just bypassing the step for installing any driver if your phone already detected as qualcomm port in your pc.
I try this method to get back my friend Mi4c from dead with condition like this too..just edl or qualcomm port while connect in device manager, then after flashing with this tool..i've try to power on with vol up + power and repeatedly vol down method above..then mi logo appear.
Hope your phone get back turn on soon..

JJeamy said:
Yup..it's weird thing...i suspect there's a hardware issue too..
But anyway..did you already tried to flashing fastboot rom with QFIL (qualcomm tool) too..?, if not yet..just try it..you can follow tutorial from this youtube here , just bypassing the step for installing any driver if your phone already detected as qualcomm port in your pc.
I try this method to get back my friend Mi4c from dead with condition like this too..just edl or qualcomm port while connect in device manager, then after flashing with this tool..i've try to power on with vol up + power and repeatedly vol down method above..then mi logo appear.
Hope your phone get back turn on soon..
Click to expand...
Click to collapse
Can you help me to find a correct ROM to try?

[email protected] said:
Can you help me to find a correct ROM to try?
Click to expand...
Click to collapse
You can try this official global stable fastboot rom that's still based android 6.0 here
If above direct link doesn't work..just visit this link , then choose "Xiaomi Mi5 Global Stable or China Stable Version Fastboot File Download..
If getting error while flashing..just put extracted folder of fastboot rom in the root of your system..ie C:\[folder_fasboot_rom]

Hi all,
After a million tests, now the phone is able to go to fastboot mode easly just pressing power&volume- (even having a black screen...) Any idea to see if this is still worth to fight?
Regards!

[email protected] said:
Hi all,
After a million tests, now the phone is able to go to fastboot mode easly just pressing power&volume- (even having a black screen...) Any idea to see if this is still worth to fight?
Regards!
Click to expand...
Click to collapse
Just try typing command "fastboot oem device-info" to see the status of your bootloader...is it still at unlocked or already relocked..?
If still at unlocked state..you can flashing fastboot rom with miflash tool.
Anyway what about QFIL method above that i said before..?, any change happen after flashing with this tool..?

[email protected] said:
not worked
Click to expand...
Click to collapse
Did you test it?
Keyvannn said:
Solved with this way
Originally Posted by adwinp
1: if you're detecting it as qcom 9008, there's a good chance it's in EDL mode, which is good news
2: download MiFlash from here: https://www.androidfilehost.com/?fid=24521665358595574
3: download the latest dev rom from here: http://update.miui.com/updates/v1/fu...ni&b=X&r=cn&n=
4: Extract the files to C:\
5: Open MiFlash & point the folder to the root ROM folder, example: C:\gemini_foo_bar, NOT C:\gemini_foo_bar\images
6: connect your phone & select flash all (1st option from the left, bottom of MiFlash tool)
This might take a few tries (example - you might receive "missed hello packets)
Once you're done, you can stay with the China Dev, unlock the bootloader & flash a xiaomi.eu rom, or CM.
Good luck.
Click to expand...
Click to collapse
------
I do this way several time but with updated miflash and fastboot rom and nothing happen.
But with this mi flash and global stable 7.2.4 and only selected #all flash#
My phone flashed
Im very happy
Thanks alot
Sorry for my bad english
Click to expand...
Click to collapse

Keyvannn said:
Did you test it?
Click to expand...
Click to collapse
I tried this and not worked for me...

JJeamy said:
Just try typing command "fastboot oem device-info" to see the status of your bootloader...is it still at unlocked or already relocked..?
If still at unlocked state..you can flashing fastboot rom with miflash tool.
Anyway what about QFIL method above that i said before..?, any change happen after flashing with this tool..?
Click to expand...
Click to collapse
I havent tried yet QFIL, but I will and let you know... Thanks so much!

Xiaomi Mi A2 bricked after Update.

So, I just got a brand new Xiaomi Mi A2 and it went well during one week.
Last Saturday, during an OTA official update the phone asked to reboot and never came back to life. It is stuck in the android logo.
I read some info online that said it can be flashed using fastboot and MI flashing tool. I tried to do it with the official rom, but once bootloader is locked, I was unable to do so.... Found other people saying that I could flash it using test point, but it required that I opened my phone...I don't want to lose my warranty and I'm not sure if that it will work either...
Please help me.

Ecd18 said:
...Last Saturday, during an OTA official update the phone asked to reboot and never came back to life. It is stuck in the android logo.
I read some info online that said it can be flashed using fastboot and MI flashing tool. I tried to do it with the official rom, but once bootloader is locked, I was unable to do so.... Found other people saying that I could flash it using test point, but it required that I opened my phone...I don't want to lose my warranty and I'm not sure if that it will work either...Please help me.
Click to expand...
Click to collapse
Why don't you use your warranty bringing this brick to official dealer?
As you have not unlocked phone, the only 2 variants you have: official service or test point (opening back cover and so on////)

I though that the A/B partition thing was making the phone unbrickable from system update...

Aerobatic said:
Why don't you use your warranty bringing this brick to official dealer?
As you have not unlocked phone, the only 2 variants you have: official service or test point (opening back cover and so on////)
Click to expand...
Click to collapse
Once I have bought it from a Chinese website, I would have to send it back to China and wait for their decision....Which would cost me a lot (shipping it from Portugal to China) and would make me wait about one month for the problem to be solved...
If I was 100% sure that test point method would work, I would rather do that. Solving the problem in one day.

Unlock the bootloader via Fastboot the instructions are on this site then your be able to flash the stock rom.

vuittion said:
Unlock the bootloader via Fastboot the instructions are on this site then your be able to flash the stock rom.
Click to expand...
Click to collapse
I have already tried using "fastboot flashing unlock_critical", but I just obtained an error... Is that what you are talking about?
Thank you in advance.

Ecd18 said:
I have already tried using "fastboot flashing unlock_critical", but I just obtained an error... Is that what you are talking about?
Thank you in advance.
Click to expand...
Click to collapse
fastboot oem unlock
fastboot oem unlock_critical
But first you need to enable oem unlocking from developer options. I have no idea how you can do that without a working system.

onbeskarakterli said:
fastboot oem unlock
fastboot oem unlock_critical
But first you need to enable oem unlocking from developer options. I have no idea how you can do that without a working system.
Click to expand...
Click to collapse
Yeah, I have tried "fastboot oem unlock_critical" too, same result.... How the hell can Xiaomi sent out an update that bricks their phones? If I open up the phone I will lose warranty for sure, but if I don't I'm just gonna be stuck with a brick for one month...
Also, I'm not 100% sure that test point method will work out well

Gokh said:
I though that the A/B partition thing was making the phone unbrickable from system update...
Click to expand...
Click to collapse
I missed your response earlier...
Do you know about the efficiency of test point method?

Did you have oem unlock and usb debugging enabled before you did the update

vuittion said:
Did you have oem unlock and usb debugging enabled before you did the update
Click to expand...
Click to collapse
No, it was an OTA update... I did not expected that to happen...

Ecd18 said:
No, it was an OTA update... I did not expected that to happen...
Click to expand...
Click to collapse
I had listen about a button combination 4 changing slot but I haven't try it, u can try it you don't loose nothing. U have to enter at fastboot with power button and volume - button, when u r at fastboot try the combination power button with volume + button and restart. If it will work tell me to know 4 future use.

vagsvag said:
I had listen about a button combination 4 changing slot but I haven't try it, u can try it you don't loose nothing. U have to enter at fastboot with power button and volume - button, when u r at fastboot try the combination power button with volume + button and restart. If it will work tell me to know 4 future use.
Click to expand...
Click to collapse
How long should I press "volume + button and restart"? Till the android logo appears?
Thank you in advance

Ecd18 said:
How long should I press "volume + button and restart"? Till the android logo appears?
Thank you in advance
Click to expand...
Click to collapse
It is not working i tried it.

vagsvag said:
It is not working i tried it.
Click to expand...
Click to collapse
Do you think Xiaomi will release a tool to recovery these phones?

Ecd18 said:
Do you think Xiaomi will release a tool to recovery these phones?
Click to expand...
Click to collapse
I think that xiaomi has lost the game about android one. Maybe you try a factory reset via recovery, if you don't know how to do this push power button and volume + button until you go to an empty screen with a died android and u push again power button and volume + button once to enter recovery, then wipe data and factory reset.

I've the same issue here with the phone from a firend. Never had such a nightmare with another phone (just something similar with sony)
I don't understand why they making such a "running circle"... Phone won't start after a normal OTA update, now i want to reflash the stock--> bootloader unlock required --> cannot be unocked because OEM unlock was not enabled.... OMG what a stupid system...
So gentleman, i think there is no solution for that and he have to return th phone to the seller, right?

vagsvag said:
I think that xiaomi has lost the game about android one. Maybe you try a factory reset via recovery, if you don't know how to do this push power button and volume + button until you go to an empty screen with a died android and u push again power button and volume + button once to enter recovery, then wipe data and factory reset.
Click to expand...
Click to collapse
The problem is that the phone go to recovery mode...just fastboot. Which is uselees because I haven´t enable oem unlock...

Makavelli- said:
I've the same issue here with the phone from a firend. Never had such a nightmare with another phone (just something similar with sony)
I don't understand why they making such a "running circle"... Phone won't start after a normal OTA update, now i want to reflash the stock--> bootloader unlock required --> cannot be unocked because OEM unlock was not enabled.... OMG what a stupid system...
So gentleman, i think there is no solution for that and he have to return th phone to the seller, right?
Click to expand...
Click to collapse
Some local store is charging me €35 to open up the phone and recover it through test point method... I think I'm gonna do it.
Better lose my warranty and have my phone within a day, than wait a hole month for the sellers solution...

Could you try this:
https://www.htcmania.com/showthread.php?t=1472420

Mi9 Global - Accidentally locked bootloader and stock in recovery/fastboot

Hi,
Recently purchased a Mi 9 Global version, got the OTA update to MIUI 11, and everything was well. It is a superb phone, but I like to have root on my phones (mostly for Adblocking and System2, better control overall). I tried to install TWRP (custom version for Mi9) because I wanted to install Magisk/Root or try a different rom eventually. Anyway... I made a huge mistake. After trying to reboot, I noticed things had gone wrong, and was stuck in a boot loop. I guess I panicked and tried to flash the phone back to the latest global MIUI rom (Version 11, Android 10, from official site), using the Xiaomi Flash App but I did not uncheck the "clean and lock bootloader" checkbox on the bottom right of the app, which is somehow enabled by default. The flash failed at that time, for unknown reason, but it seems like it succeeded in locking my bootloader, with an empty partition, except for fastboot access and Mi Recovery module. I have to admit I've always been pretty lucky with all my previous flashes on other devices, and I guess I got a little careless. That was pretty stupid of me, in retrospect.
Since then, I am stuck in either Mi Recovery or Fastboot, and it seems that my originally Global Mi 9 with unlock bootloader has now a locked bootloader. Any attempt at either using the Xiaomi Flash utility gives me an error message ("Erase boot error"), and if I boot into Fastboot and try to flash TWRP, I get the "Remote:Erase is not allowed in Lock State" error.
From what I understand, my options are pretty limited now. The phone is still powered on, stuck in Recovery mode and rebooting every 5 or 10 minutes by itself (probably a way to avoid screen burn-in?), but I can't seem to be able to shut it down in anyway, as there are no fastboot commands to send a shutdown signal. And no matter what button combination I press, the phone always ends up rebooting.
I tried the Xiaomi Unlocker utility, but it needs the phone to be out of recovery to check the credentials binding the phone to my account. All data on the phone has been wiped already, so that's not an option. Two options I have seen :
1. Open the battery cover (required a heat gun and risky), to short some pins and try to flash while there is a short to circumvent the security. I'm not that brave yet, and since the phone is still running and has probably about 80% battery, I don't want to use a heat gun on the device.
2. Shady stuff involving paying 30 or 40 Euros to a random guy who can somehow make everything work magically by remotely logging in on my computer via Teamviewer (Not happening in a million years).
I'm wondering if there is an alternative, other than bringing the device to an official Xiaomi store (I'm in Bangkok and they do have one official shop at Fortune Town), but even then, I don't know if they'll just tell me I got myself an expensive paperweight.
Any help/insight regarding this issue would be much, much appreciated!

Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.

g_seva said:
Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.
Click to expand...
Click to collapse
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.

Twomby said:
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.
Click to expand...
Click to collapse
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.

g_seva said:
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.
Click to expand...
Click to collapse
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.

To enter fastboot mode, long press the volume down key and the power key. Then unlock bootloader with Xiaomi app.

zahdekar said:
To enter fastboot mode, long press the volume down key and the power key. Then flash stock rom.
Click to expand...
Click to collapse
I have managed to enter fastboot mode, as described in my initial post. The problem is that when I try to flash, I get the following error: "Flashing not allowed in lock state".

Twomby said:
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.
Click to expand...
Click to collapse
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.

g_seva said:
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.
Click to expand...
Click to collapse
From what I understand, the "normal mode" needs the tool to be able to access the OS while it's running. I don't have an OS. I will give it a shot tomorrow (3 AM here, exhausted, and don't want to boot into Windows again!), but my hopes are not so high. Anyway, thanks for the help, much appreciated! Will let you know what happens! Cheers!

https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help

zahdekar said:
https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help
Click to expand...
Click to collapse
I've stumbled upon this link earlier today. But it's 404 on my end. Can you access it from where you are? Thanks!

http://c.mi.com/thread-2251372-1-1.html
This is on page 4

zahdekar said:
http://c.mi.com/thread-2251372-1-1.html
This is on page 4
Click to expand...
Click to collapse
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!

Twomby said:
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!
Click to expand...
Click to collapse
I have the same problem! "The system has been destroyed" (((
And mi unlock tool not work abount 2 days (authorization not passes)

https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.

zahdekar said:
https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.
Click to expand...
Click to collapse
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!

Twomby said:
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!
Click to expand...
Click to collapse
Hello @Twomby did you managed to get it working it the end?

Same issue here
Hi,
I am encouraging the same issue. Does someone found a solution to this?

tago4ever said:
Hi,
I am encouraging the same issue. Does someone found a solution to this?
Click to expand...
Click to collapse
I came across this Mi8 thread, not sure if it's possible on the Mi9, but he seems to have been able to flash it through EDL mode, you might ask him the question: https://xiaomi.eu/community/threads/mi-8-bricked-from-nowhere.55723/#post-543605
There's also this Mi9 thread: https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966

Pixel 5 Stuck on boot loop

Hi All,
I'm hoping someone will be able to help as I've spent most of the day chasing my tail it seems.
My 'stock' (non-rooted/non-flashed) Pixel 5 went into a boot loop randomly last night.
I've restarted, I've gone into the recovery mode and have tried to flash an OTA via ADB (which may not sound like much but is an achievement for someone with my limited technical skills), it's getting to 94% and then I'm receiving an error on the cmd prompt saying 'adb: failed to read command: No error' but on the phone itself it says that is was a 'success' status 0.
I've tried the current OTA and the developer version and I'm getting the above issue on both.
I tried copying the 'zip' to a USB stick and have plugged that in using the USB A to USB C dongle that comes with the pixel but I'm receiving an error stating that it cannot be initiated.
Can anyone suggest a possible next step? I have some files that I've realised don't go to my cloud backup and they are important to me so I'd like to if possible not have to wipe the device.
Many thanks.

Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.

l7777 said:
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
Click to expand...
Click to collapse
Hi, thanks for taking the time to respond. Everything was downloaded yesterday so is up to date. I re-downloaded just now and checked again and am still getting the same.
(~94%) adb: failed to read command: No error on cmd
Install from ADB completed with status 0 on the phone.
Is there a simple guide on how to flash-all (for someone as not technical as me) that you can point me towards?

Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.

did you try a different cable or usb port? borrow your friend's pc perhaps?

l7777 said:
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
Click to expand...
Click to collapse
Hi, thanks for this, I'll try another sideload with the April update and attempt it from another laptop, if that still doesn't work then I'll try the flash as you suggest.

swangjang said:
did you try a different cable or usb port? borrow your friend's pc perhaps?
Click to expand...
Click to collapse
I tried a different cable and port but not another laptop. I'll try that next after trying the April update.
Thanks.

tinhsoftware said:
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
Click to expand...
Click to collapse
Hi, no not yet. I think this will be the last step before I factory reset. Will try another cable, laptop and the April OTA this evening when I have time.
Thanks.

WFHbot said:
Hi, no not yet. I think this will be the last step before I factory reset. Will try another cable, laptop and the April OTA this evening when I have time.
Thanks.
Click to expand...
Click to collapse
Also a note on trying to use the web flash utility. Make sure to look at the advanced options on the installation page, it gives you an option to flash the latest update without wiping your device at all.
That could help in getting the phone running again so you can recover your important files, before deciding to do a compete wipe, if that's what you have planned.
Just look around the settings carefully before flashing and everything should go well .

The same thing happened to me, it must have been the April update, I updated my phone, everything seemed to work and then all of the sudden I was watching a video last night and the phone rebooted itself and kept being stuck in boot, it won't load the os but it keeps restarting itself.
I tried accesing recovery mode but on the bootloader screen it won't let me use the volume keys to start the phone in recovery mode or to try and hard reset it, while on the bootloader screen it resets itself... :/ I'll give google a call

Chad_Petree said:
The same thing happened to me, it must have been the April update, I updated my phone, everything seemed to work and then all of the sudden I was watching a video last night and the phone rebooted itself and kept being stuck in boot, it won't load the os but it keeps restarting itself.
I tried accesing recovery mode but on the bootloader screen it won't let me use the volume keys to start the phone in recovery mode or to try and hard reset it, while on the bootloader screen it resets itself... :/ I'll give google a call
Click to expand...
Click to collapse
That sucks. Hopefully they'll be able to do something more than just a factory reset.
I've tried sideloading the April update and that also failed at 94%. Will try another laptop in a while and see if that works, then try the flash as suggested above, if not then it's a factory reset for me.

ProjectAlly said:
Also a note on trying to use the web flash utility. Make sure to look at the advanced options on the installation page, it gives you an option to flash the latest update without wiping your device at all.
That could help in getting the phone running again so you can recover your important files, before deciding to do a compete wipe, if that's what you have planned.
Just look around the settings carefully before flashing and everything should go well .
Click to expand...
Click to collapse
Thanks, will have a look around and see what I can work out. It's looking like I'll have to go this route...
DO I need to unlock the bootloader do do this flash?

tinhsoftware said:
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
Click to expand...
Click to collapse
Thanks, will have a look and see if this works.
DO I need to unlock the bootloader do do this flash? If so, would this wipe the device?

WFHbot said:
Thanks, will have a look and see if this works.
DO I need to unlock the bootloader do do this flash? If so, would this wipe the device?
Click to expand...
Click to collapse
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip

l7777 said:
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
Click to expand...
Click to collapse
Thanks, I tried that. Edited the file and tried running the flash-all.bat file but it's giving me an error:
Setting current slot to 'b' FAILED (remote: 'Fastboot command (set_active: ) is not allowed when locked')
fastboot: error: Command failed
Not sure what I'm doing wrong. Am I missing a step? Should the phone be on a certain menu when running the bat file?

l7777 said:
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
Click to expand...
Click to collapse
Is that a fact? I haven't had a bl unlock for many years now but I thought I could only do an OTA flash from fastboot with a locked bootloader. I know I can factory reset but other than that .. So if I loaded the beta 12 I could go back and flash a factory image? I would certainly flip the OEM switch first just in case.

bobby janow said:
Is that a fact? I haven't had a bl unlock for many years now but I thought I could only do an OTA flash from fastboot with a locked bootloader. I know I can factory reset but other than that .. So if I loaded the beta 12 I could go back and flash a factory image? I would certainly flip the OEM switch first just in case.
Click to expand...
Click to collapse
That's a good question. I assumed it was possible otherwise why have a factory image available. The consensus seems to be mixed though.
OP: I just did an update from January to April and yes I also got the error at 94% from ADB but the phone reported status 0. Booted up no problem. Have you tried booting into safe mode? Is USB Debugging on? Can you get a logcat of the attempted boot?

l7777 said:
That's a good question. I assumed it was possible otherwise why have a factory image available. The consensus seems to be mixed though.
OP: I just did an update from January to April and yes I also got the error at 94% from ADB but the phone reported status 0. Booted up no problem. Have you tried booting into safe mode? Is USB Debugging on? Can you get a logcat of the attempted boot?
Click to expand...
Click to collapse
Hi,
I've tried booting into safe mode by keeping the volume down button pressed but no luck.
I'm pretty sure that the USB debugging is enabled, but not 100% certain.
How would I go about getting logcat of the attempted boot?
Thanks for all the help thus far.

WFHbot said:
Hi,
I've tried booting into safe mode by keeping the volume down button pressed but no luck.
I'm pretty sure that the USB debugging is enabled, but not 100% certain.
How would I go about getting logcat of the attempted boot?
Thanks for all the help thus far.
Click to expand...
Click to collapse
You'll have to factory reset in recovery. I had something similar happen yesterday morning. The reboot was done by me on the way to work though. A factory reset fixed it. Of course all user data was wiped, but Google backups did a good job of restoring almost everything I wanted restored (except for apps not on the G Play Store of course). You'll need to sign into everything again, but most things won't be lost including root.

Question NE2215_11_C22 Update

Today Got update C22 for 2215
And After Rebooting it shows
'Warning Your device is Modified and is not secure' Like thing at start Logo..
Anyone facing this warning.??
It's showing after C22 update

Unlocked bootloader or something ?

Xpid3r said:
Today Got update C22 for 2215
And After Rebooting it shows
'Warning Your device is Modified and is not secure' Like thing at start Logo..
Anyone facing this warning.??
It's showing after C22 update
Click to expand...
Click to collapse
Hi,
I have just updated right now with Oxygen Updater, I am currently rooted and with an unlocked bootloader. I done the OTA patch within Magisk and allowed the device to reboot but now I am in a bricked state.
Upon boot I now receive a message:
"Orange State, Your device has been unlocked and can't be trusted, Your Device will boot in 5 seconds"
And now I am in a bricked state of:
"QUALCOMM - CrashDump Mode"
I can access fastboot mode and Recovery mode but I hope I don't have to hash my device and start over.

rasseru16 said:
Hi,
I have just updated right now with Oxygen Updater, I am currently rooted and with an unlocked bootloader. I done the OTA patch within Magisk and allowed the device to reboot but now I am in a bricked state.
Upon boot I now receive a message:
"Orange State, Your device has been unlocked and can't be trusted, Your Device will boot in 5 seconds"
And now I am in a bricked state of:
"QUALCOMM - CrashDump Mode"
I can access fastboot mode and Recovery mode but I hope I don't have to hash my device and start over.
Click to expand...
Click to collapse
This typically happens because you had magisk modules enabled when you updated.
Try holding down all the buttons this should force it to switch back to the other slot with the older update still installed. Then you can download the last full update for your older version and flash that.

Xpid3r said:
Today Got update C22 for 2215
And After Rebooting it shows
'Warning Your device is Modified and is not secure' Like thing at start Logo..
Anyone facing this warning.??
It's showing after C22 update
Click to expand...
Click to collapse
Yeah I got "Orange State Your device is unlocked blah blah blah..."
I heard from the Pixel folks that they lost the ability to unlock their bootloader recently and this may be part of that. Google is slowly squeezing down on uncontrollable devices so this may be the start of the pain to maintain root on this device.

Funny, just the other day I thought to myself that it's ironic the older OnePlus devices have that on startup, but this one doesn't. Seems it was an oversight.

Is there any chance you'd be willing to provide the boot.img for C.22? I'm trying to patch it with magisk

SuperBrolySSJ said:
Is there any chance you'd be willing to provide the boot.img for C.22? I'm trying to patch it with magisk
Click to expand...
Click to collapse
This should be the C22 stock boot.img

This orange message appeared also in the stable A13 updates for the OP9pro. Seems that's something we have to live with.

Deacon-Frost said:
This orange message appeared also in the stable A13 updates for the OP9pro. Seems that's something we have to live with.
Click to expand...
Click to collapse
That's strange.. Oneplus will loose their customer's At this rate of Strictness

metrixx02 said:
Unlocked bootloader or something ?
Click to expand...
Click to collapse
Already Had magisk Installed..
I Restore Images then Update then Install to Inactive slot...
After Rebooting it Occurs.. Orange State

Xpid3r said:
Already Had magisk Installed..
I Restore Images then Update then Install to Inactive slot...
After Rebooting it Occurs.. Orange State
Click to expand...
Click to collapse
İ don't understand ur phone bricked or not ?

metrixx02 said:
İ don't understand ur phone bricked or not ?
Click to expand...
Click to collapse
No, phone is in Running Condition.. it auto reboots after 5 sec..

Same experience with me, phone is stable but get the warning since C22 update, is this not normal?

On rooted NE2215 C.22 now. That Orange State on boot gets me uneasy.. Everything else seems stable. My NFC gpay works lol.

So I'm in this state right now...orange screen followed by Crashdump mode., after updating to C22. And yes, I failed to disable the Magisk modules, but did uninstall then reinstall, etc.
What do I do now? I am clueless as to how to proceed.
Many thanks for your help

BeachNYC said:
So I'm in this state right now...orange screen followed by Crashdump mode., after updating to C22. And yes, I failed to disable the Magisk modules, but did uninstall then reinstall, etc.
What do I do now? I am clueless as to how to proceed.
Many thanks for your help
Click to expand...
Click to collapse
Boot in Safe Mode.. then Uninstall All the Magisk modules, After that restart normally

Try this for getting out of Qualcomm Crash Dump Mode:
https://forum.xda-developers.com/t/...e-rom-root-and-recovery.4525451/post-87806713

Xpid3r said:
Boot in Safe Mode.. then Uninstall All the Magisk modules, After that restart normally
Click to expand...
Click to collapse
Thanks! Worked!

BeachNYC said:
Thanks! Worked!
Click to expand...
Click to collapse
Glad it worked