Database Info

[FIX] Orange State Bootloop on OUKITEL K6000 Plus - HOW TO FIX

Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver

Please help I have error 4032 (BROM ERROR S_FT_ENABLE_DRAM_FAIL)

1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
this should solve that

STATUS_BROM_CMD_SEND_DA_FAIL
persists even after installing correct drivers?
Solution: Choose
Download Agent as DA-PL in SP flash tools. And follow the same guide.

Thank you so much for this post, just saved an Oukitel K6000 Plus. Just finished process, rebooting normally for first use. It's been stressfull hours, what a relieve.

slavedriver83 said:
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If
Click to expand...
Click to collapse
this helped me a lot with my ulefone armor 2, thanks

Fixed the orange state, thanks a lot for this guide.
Do you think I shall try again to upgrade to Android 8 anymore?

slavedriver83 said:
9. Using one hand only click and hold at the same time VOL UP + POWER button.
Click to expand...
Click to collapse
Thank you very much for the advice
I thought I put my phone in the trash when I read this.
But in point 9 I had to push only the VOL UP if I press the two buttons, the AP returns an error.

You saved mine as well, slavedriver!
And it is a Teclast Tpad A10S!
I had given it up.
Thanks a lot!

It works also on U20 plus. I had to select DA_SWSEC as Download Agent. Thank you so much!

Guide worked Perfectly for me.
My mobile was bricked in the same Bootloop. The guide worked perfectly for me. Thanks a lot for useful and detailed help.

I understand this thread is almost 1 year old. I tried this procedure and everything went well. The only problem the phone does not boot. It does turn on but nothing comes up. No boot menu no logo just a few flickering lights and a very dark background. Does anyone have any ideas?
OK6000 Plus

pvkid said:
I understand this thread is almost 1 year old. I tried this procedure and everything went well. The only problem the phone does not boot. It does turn on but nothing comes up. No boot menu no logo just a few flickering lights and a very dark background. Does anyone have any ideas?
OK6000 Plus
Click to expand...
Click to collapse
Tried this guide but SP shows the following messagge "STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060005) " (so it doesn't end with 3 but with 5)

Pyandroid said:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
this should solve that
Click to expand...
Click to collapse
Bro I got a different error just looks like:
ERROR STATUS_SEC_AUTH_FILE_NEEDED (0xc0030012)
Please help me out...I use "tecno spark 4 kc2"

slavedriver83 said:
Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver
Click to expand...
Click to collapse
Solution?
for:
ERROR STATUS_SEC_AUTH_FILE_NEEDED (0xc0030012)
"Tecno spark 4 kc2"

slavedriver83 said:
Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver
Click to expand...
Click to collapse
Hi, do I need my phone to be rooted to do this.
I unlocked bootloader in my gionee f205 from fastboot and now it is in orange state bootloop.
I haven't rooted my phone before doing it.

[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)

You can use it to revive your op6, if you can boot in fastboot and have done the stuff with drivers (qualcomm)
MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)
May 2018 Android patches
https://mega.nz/#F!CfBG0IgZ!Gmnu6B-a7yFyvMLNw_pz8w
https://www.androidfilehost.com/?fid=746163614322268729
Guide how to revive your op6:
First of all, you need to access to fastboot mode, if you can't , contact Oneplus support, then have a windows computer and download these file and drivers qualcomm ( https://androidfilehost.com/?fid=24052804347798730) and extract in one folder.
After you have all the file ready, plug in the phone to the computer, go in device manager and under port (COM) disinstall qualcomm one (oneplus 6) and then unplug.
Now you have to go in Windows test mode to not let him install default drivers, so:
windows key (on keyboard) + X, windows powershell (or normal prompt) administrator and write and enter: bcdedit /set testsigning on ( you will repeat the same process with "off" to stop the test mode after you will finish to do all the things).
Reboot the system and you could see in bottom right corner the test mode, now you are ready to install properly drivers.
Power off the phone, then hold for 5 seconds vol up and plug the usb to computer. Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process (https://www.youtube.com/watch?v=PpLvmID1wdI)
Right click con US8_BULK in device manager and update drivers by system files (go to the folder's drivers you had extracted before).
Now you should see qualcomm drivers under port (COM).
You are ready to let the tool to do all the stuff, so let plugged the phone, always powered off, right click on msmdownloadtool and execute as administrator.
You should see your device and click start to begin the process; if it gives you some error (like sahara or something else), unplug, power on, power off and the plug it again, now it should be fine.
And that's it, the tool will do all the work and, at the end, you will have like a brand new phone ready to a new setup.
EDIT: if you are stucked in bootloader, you have only to power off and continue with the part: ... hold for 5 seconds vol up... (it happened in page 4)
Please, consider to donate me something for the work and the risk (maybe idk). Thanks
https://www.paypal.me/Imadalek
Only BTC: 3P5PnpTLpfRp2LWTfh8AkL7GCU1kAGxvM4
Only ETH: 0xE3F462A1aC3dBa8bEc3179535C0b6688d9D13106
Only LTC: MGwHMU4qEB6pRX7apQEBYkUrm1iL7Sa2NY
(Thanks to @nytebird for the contribution)
If you want to buy another Oneplus 6, this is my referral to have 20€/$ discount on accessory:
https://www.oneplus.com/it/invite#2CQD9VHNXPFA2B

Awesome saw u on r/OnePlus telegram
How did you get these files?

Could be from phonandroid, since the tool is there for download since 5 days .

MickyFoley said:
Could be from phonandroid, since the tool is there for download since 5 days .
Click to expand...
Click to collapse
The international one? Are you sure? I have found only the chinese that puts Hydrogen OS restoring

OnePlus telegram? Someone pm me the link

Thanks for the tool :good::good:
Can someone upload it in any other site. I am unable to download. :crying:

anthonythangaraj said:
Thanks for the tool :good::good:
Can someone upload it in any other site. I am unable to download. :crying:
Click to expand...
Click to collapse
Check Desktop Site box in your browser.

Plz mirror the link .

hello would it be possible to have the same thing with the update 5.1.3 thanks in advance

lerieur said:
hello would it be possible to have the same thing with the update 5.1.3 thanks in advance
Click to expand...
Click to collapse
No way; the techs come to you with this

Pls reply anyone who tried this to restore op6. Proper files also pls link for proper guide

mirror plzz

Panssee said:
mirror plzz
Click to expand...
Click to collapse
I'm trying to get developer permission to android file host

milav said:
Pls reply anyone who tried this to restore op6. Proper files also pls link for proper guide
Click to expand...
Click to collapse
I will edit first post to explain all in detail

milav said:
Pls reply anyone who tried this to restore op6. Proper files also pls link for proper guide
Click to expand...
Click to collapse
done

Easiest way is to be in system and turn on adb debugging and run adb reboot edl then go about the install

joemossjr said:
Easiest way is to be in system and turn on adb debugging and run adb reboot edl then go about the install
Click to expand...
Click to collapse
If you have system access, there is no point to use this tool/guide I was able only to boot in fastboot

Test with 128 GB version about 10-15 minutes (with already installed drivers): OK
It runs like a new shipped OP6.

Fivegates said:
If you have system access, there is no point to use this tool/guide I was able only to boot in fastboot
Click to expand...
Click to collapse
Lol oh yeah

Qualcomm tool is not for fastboot or recovery mode, but for qualcomm drivers mode (USB to serial port).
So if you can boot to recovery or fastboot, probably don't need this pack.

[Guide] Unbrick Your UNLOCKED Lenovo P2a42

Hey Friends,
You must have seen very good days with Lenovo P2 but when there comes a bad day when your phone stops responding to button holds and restarts. You may or may not have a clue what to do to get your phone working again just like before.
I got into this situation where only thing my phone was able to operate was a RED LED on connecting it to my laptop. Then I had to read tens of pages on XDA to find answers to all my questions. If you are in such a situation and your phone is UNLOCKED then you have come to the right place. Procedure is quite simple but remember, I am writing this guide to define complete process from blackout to complete update so follow this guide as per your needs.
I faced this situation of Total Blackout / Dead Phone (Almost) with only Red LED working and it can be very scary. So, here is the simplest procedure you can follow. I want to appreciate all those people who helped me in finding a way to boot my phone with each and everything working. Long story short, let's get this done.
Tools Required:
I am mentioning here all the Tools you will need. I will urge you to download and save these tools in case you want to unbrick your phone any time:
1. Minimal ADB and Fastboot setup for PC
2. Lenovo USB drivers v1.1.33
3. Qualcomm USB Drivers
4. Qualcomm Flash Image Loader (QFIL) v2.0.1.9 for your PC in case you have corrupted your phone's IMEI and/ or Baseband
5. Blankflash.bat in case you want to recover from total blackout (Attached)
6. Stock MM S048 Firmware for Lenovo P2 in case phone doesn't boot
7. S048_ModemTelephony.zip in case your phone boots through Stock MM S048 but SIM isn't detected and IMEI is missing. I have made a complete modem zip file for installation through recovery.
8. S251_ModemTelephony.zip in case your phone is on latest firmware and doesn't detect SIM and has lost IMEI. I have made a complete modem zip file for installation through recovery.
9. QCN file for recovering baseband version and giving you most precious network signals. (Attached)
10. WinRAR or PeaZip for uncompressing files
I will recommend you to have a specific folder for keeping all these tools in a single place.
Procedure for Unbricking:
Before going with the procedure, make sure you have downloaded all the files you need, updated Lenovo and Qualcomm drivers etc. Here is the procedure:
1. If total blackout with red LED notification when connecting to PC: Unzip blankflash.zip to a folder in C drive. Now connect your P2 to PC through USB, press volume+, volume- and power button simultaneously and double click blankflash.bat. You might have no success in your first try. Just keep trying and it will load your phone to Fastboot. Restart your phone in TWRP if installed and install a working ROM for your phone after doing a wipe. If all is good and phone works OK then great but if you have lost IMEI and baseband then it is better to reinstate your phone through first MM stock ROM S048
2. Install S048 firmware through Minimal ADB and Fastboot - use flash instructions in .txt file.
3. Wait for startup of phone. Check if fingerprint, BT, WIFI and SIM work if all work then OK.
4. If fingerprint, BT, WIFI and SIM are not working then check IMEI through dialer. Dial *#06#. If IMEI is not available then install latest TWRP through Fastboot.
5. Start P2 in TWRP recovery and install S048_ModemTelephony.zip. Restart phone to see if WIFI and SIM work.
6. If SIM is detected but not giving signals and Baseband is shown as unknown then extract 000000_0.qcn file given in .7z and restore through QFIL and restart your phone into Fastboot.
7. Now, install stock recovery of S048 firmware through Fastboot and restart your phone.
8. Use your phone like you normally do and update your P2 till firmware S251 and see if everything works including calls. Update your phone through OTA.
9. After OTA installation, stock recovery may say that update failed. Just press Back, go into Wipe user data menu and Wipe Cache only. Restart your phone which will be updated to latest version and will ask you to update to a newer version. Allow it to download the next update.
10. After installation of S251 update, install latest TWRP through Fastboot and install most recent version of LOS 16 so that your vendor partition is stable and free from any bloated files. Now, use your phone just like you want to.
If you need further clarification then ask in this thread.

Bro my phone is not unlocked can i try thz one

Ranji007 said:
Bro my phone is not unlocked can i try thz one
Click to expand...
Click to collapse
You should download S048 and use flashall.bat inside that archive to install it all. However, if you lose IMEI or baseband then you can use modem and qcn files given in this thread.

alirazaagha said:
You should download S048 and use flashall.bat inside that archive to install it all. However, if you lose IMEI or baseband then you can use modem and qcn files given in this thread.
Click to expand...
Click to collapse
Bro now i wanna use ...minimal adb ..my phone is totally bricked only red light glowing

Ranji007 said:
Bro now i wanna use ...minimal adb ..my phone is totally bricked only red light glowing
Click to expand...
Click to collapse
don't worry just flash blank flash from the link given in the op, you will get the bootloader back

hackiee said:
don't worry just flash blank flash from the link given in the op, you will get the bootloader back
Click to expand...
Click to collapse
Bro how to connect my phone to blank flash...can u PLZZ help

hackiee said:
don't worry just flash blank flash from the link given in the op, you will get the bootloader back
Click to expand...
Click to collapse
Laptop is not detecting my device bro i installed all lenovo and Qualcomm drivers...any idea

Ranji007 said:
Laptop is not detecting my device bro i installed all lenovo and Qualcomm drivers...any idea
Click to expand...
Click to collapse
If red light blinks, your phone can be detected by your laptop. Check ports in device manager settings and you'll see a new port with Qualcomm 9800 series number. If that's there, try blankflash to start in fastboot. It might need some tries before startup. Be patient and keep trying till you are in fastboot.

alirazaagha said:
If red light blinks, your phone can be detected by your laptop. Check ports in device manager settings and you'll see a new port with Qualcomm 9800 series number. If that's there, try blankflash to start in fastboot. It might need some tries before startup. Be patient and keep trying till you are in fastboot.
Click to expand...
Click to collapse
Bro ..thanks for reply....in my phone red blink is glowing continuously ..but after connecting there is no change...can u say which buttons i want to press?

Ranji007 said:
Bro ..thanks for reply....in my phone red blink is glowing continuously ..but after connecting there is no change...can u say which buttons i want to press?
Click to expand...
Click to collapse
Press Volume+, Volume- and Power simultaneously and double click flashblank.bat. It might take some tries to finally install the scripts and start phone in fastboot. It took me 20+ tries to finally detect my phone through blankflash. Please, read OP completely.

alirazaagha said:
Press Volume+, Volume- and Power simultaneously and double click flashblank.bat. It might take some tries to finally install the scripts and start phone in fastboot. It took me 20+ tries to finally detect my phone through blankflash. Please, read OP completely.
Click to expand...
Click to collapse
Bro we want to connect each time removing usb cable and connect again like that ..we wanna do 20 times??

Ranji007 said:
Bro we want to connect each time removing usb cable and connect again like that ..we wanna do 20 times??
Click to expand...
Click to collapse
No. Keep USB connected. Try blankflash. If it doesn't detect phone or go ahead. Close command terminal, double click again and keep doing it till it processes the files. If it is stuck somewhere. Close terminal and try again.

alirazaagha said:
No. Keep USB connected. Try blankflash. If it doesn't detect phone or go ahead. Close command terminal, double click again and keep doing it till it processes the files. If it is stuck somewhere. Close terminal and try again.
Click to expand...
Click to collapse
Bro is there any solution ..i continuously pressed volume and power buttons connected to laptop and opening blank flash continuously for number of times ...but there was no reaction...only waiting for device is showing ? on my pc ...

Ranji007 said:
Bro is there any solution ..i continuously pressed volume and power buttons connected to laptop and opening blank flash continuously for number of times ...but there was no reaction...only waiting for device is showing ? on my pc ...
Click to expand...
Click to collapse
Check if your USB cable is alright and appropriate drivers are installed. Otherwise reinstall drivers, restart your PC and try again.

alirazaagha said:
Check if your USB cable is alright and appropriate drivers are installed. Otherwise reinstall drivers, restart your PC and try again.
Click to expand...
Click to collapse
Bro we want to change any settings in device manager ...?

Ranji007 said:
Bro we want to change any settings in device manager ...?
Click to expand...
Click to collapse
No. Just update drivers.

alirazaagha said:
No. Just update drivers.
Click to expand...
Click to collapse
Bro when u take to service center they said for u motherboard problem or something??

Ranji007 said:
Bro when u take to service center they said for u motherboard problem or something??
Click to expand...
Click to collapse
Fortunately, I never took it there.

alirazaagha said:
Fortunately, I never took it there.
Click to expand...
Click to collapse
My phone was fallen in water then i changed the display..few days after it stopped working ..and when i take to serive centre they said to change motherboard..but it's the 80% of phone price...so iam here ?..iam trying thiz method

Ranji007 said:
My phone was fallen in water then i changed the display..few days after it stopped working ..and when i take to serive centre they said to change motherboard..but it's the 80% of phone price...so iam here ..iam trying thiz method
Click to expand...
Click to collapse
I think you might have damaged some hardware. But anyway if you want to use blankflash, I have a method.
In lenovo p2 we have another mode called QDloader mode, in which we can use blankflash. For entering into this mode, it's little tricky but, can enter in one or two go.
So, here's how:
1. Switch off the mobile.
2. Press the volume up key,
3. While holding the volume up key, insert the usb cable and at the same time press the power button (this is the trick, we have to insert and hit at the same time).
And voila! :highfive: you will see black screen with only red notification led blinking.
we are into QDloader mode. Now use blankflash :good:

Bricked My phone, cant get into FastbootD to fix it

So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)

As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS

Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me

Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.

gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there

Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?

gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys

I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com

download the correct drivers and replace them in the device manager

gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!

worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time

Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.

Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse

Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com

Realme C21Y HardBrick - It says USB Device is faulty but disappears after 2 seconds - I can't enter download mode

I corrupted my phone's root/system/etc files and when I restarted it, it wouldn't turn on and got stuck on the realme logo. i hold my phone vol+ and - and power key and when the realme logo comes up, i release the power key, i think download mode opens, but it usb device is faulty for 1-2 seconds and disappears immediately, meanwhile in device manager it shows unknown device for 1-2 seconds and disappears. After 10-15 seconds there is a usb connection sound but nothing happens. I can send adb commands but I have to confirm the confirmation window but I cant.
Please help me, how can I fix it?

Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.

Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here

Renate said:
Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.
Click to expand...
Click to collapse
Yes, I get the unauthorized message as below. If I can somehow authorize it, I will be able to enter fastboot mode and flash the stock rom.
mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Okay, I'm trying

mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again

mvikrant97 said:
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again
Click to expand...
Click to collapse
I updated with Driver Booster, no luck.
I only tried the front USB ports, do I need the back ones? There are 2 2.0 and 1 3.0 port on the front
The computer is new so I don't think it's defective, the phone is charging and I was using it before it went brick.

I also modified the boot file to install a new GSI and used the following guide.
Spoiler
First, you need to unlock fastbootd:
1. Download the stock ROM version 91: Download and extract the .pac file Link
2. Install the SPD research tool and drivers: GDrive
3. Open it
4. Click on the single gear icon
5. Select the .pac file of the stock rom
6. Wait until it loads
7. Click on the two gear icon
8. Find BOOT in the list
9. Right-click on the path next to it
10. Download here and select boot_r1.img
11. Click OK and then click the arrow icon
12. Turn off your phone
13. Press and hold Power + VolumeDown until you see the text "Downloading"
14. Release the buttons after seeing
15. Wait until you see the text "Passed"
16. Click on the Stop icon, disconnect your phone and turn it on
[/ISPOILER]

@leanord Can you help me?

The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.

Renate said:
The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.
Click to expand...
Click to collapse
I don't fully understand your question, but I have the stock recovery, I didn't install TWRP, and I installed dotOS 5.2 as GSI. I think I corrupted the fastboot, download mode boot files in the root files. I will take it to the service center, but if you have a solution, you can write, I don't want to give money.

It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?

Renate said:
It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?
Click to expand...
Click to collapse
It may have been disabled or because I corrupted system files.

Wanted? I came, to flash the phone, you do not need to press anything except the volume keys, the power button is only a catalyst, you need to hold it down until the screen goes out, and then just Keep the volume - and flash as usual, the main thing is to keep it immediately plugged into the PC with a ready-made flasher

What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.

Luuukie said:
What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.
Click to expand...
Click to collapse
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing

leanord said:
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing
Click to expand...
Click to collapse
SP Flash Tool doesn't see my device so I can't flash it. If you mean Fastboot, I can't get into it.

By the way, that font that's showing up in my UsbLog is UGLY.
I readjusted things, you can download a new copy that is prettier.

Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.

Renate said:
Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.
Click to expand...
Click to collapse
I'm sorry, I don't know that much. But if you tell me the steps how to do it, I can do it.

@leanord when installing GSI, I flashed boot_r1.img from your Realme C21Y GSI installation guide, did you disable fastboot or something?