Develop Bugs

How to wipe android partitons while NO access to Fastboot? PLZ help

Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill

TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
Here you can find a recovery guide:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I'd recommend methode 2, because it seems more east to do.
Good luck!

TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.

pvramk said:
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
Click to expand...
Click to collapse
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.

TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
............
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
well if you are rooted you can try using an app called flashify or flashfire to install twrp

pvramk said:
well if you are rooted you can try using an app called flashify or flashfire to install twrp
Click to expand...
Click to collapse
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?

TowChill said:
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
Click to expand...
Click to collapse
When the display shows the battery % check if fastboot devices shows your device?
If not I'm sorry, I would not be of any more help to you my friend.
Hope someone more knowledgeable comes along and clears your problem....

TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
If nothing works, try method 2 from the Hard Brick guide from Naman Bhalla.

Soft bricked OPO3, Fastboot with no recovery

Hi guys,
Rooted Oneplus 3 is soft bricked. Please help me!!! :crying:
:crying:Quick desription: Fastboot formatted it. My PC detects it.
Tried to Fastboot flash latest TWRP ("twrp-3.0.2-0-oneplus3.img") via CMD Prompt.
After that I get a message saying that the processed was "finished" (within 0.802s!).
Now I reboot+volume down and bootloop continues. Phone starts, I see the normal warnings I used to get after rooting it. Then I see the Oneplus logo for a fraction of a second and then it boots again and the process repeats itself.
I think it may be worth mentioning that the reason all this happened is an encryption problem that occurred while I was flashing a rom update with TWRP: After the flashing finished, got an error saying "unable to mount storage". Wiped cache+dalvik and then restarted. Got a black screen that did not display any signs of life after several minutes. Then turned it off and on by long press on the power button. Then I got an error saying that the encyption process was disrupted and that I have to wipe my phone (strange given that I did not select any encryption button in TWRP). Anyhow, then I fastboot formatted the phone and that's it.
Thank so much for anyone who can help!!!

fastboot flash recovery recovery.img (I recommend blu_spark's TWRP) reboot to recovery, if it doesn't work, try:
fastboot boot recovery recovery.img
See if you boot to recovery and then try flashing a custom ROM.

Hi Fobos, thanks for responding quickly.
I tried using fastboot boot command (with twrp-3.0.2-0-oneplus3.img). No luck with that.
Also, didn't find a downloadable blu_spark *.img version for twrp recovery. would you be so kind to add a link?
Thank you.

Now I think it's hard bricked ( Help!!!
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!

ppppp44 said:
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
Click to expand...
Click to collapse
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.

Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"

Kayembe said:
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Click to expand...
Click to collapse
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...

anup807 said:
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Click to expand...
Click to collapse
Hi Anup!
Thanks for the link to the Blu_Spark version of TWRP.
On CMD Prompt, tried to format recovery, console stopped responding. "Fastboot format recovery"...Just stops responding
Also tried "Fastboot delete recovery". I get a message saying "deleting recovery..." then also stops responding. Nothing happens from there.
I tried to use the OPO3 Root Toolkit. It does detect the fastboot device, but when I try to flash or boot or do anything else other than detection, it is unable to find the device. Says operation failed.
What now? :crying:

You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/

Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Check your cable (try another one), even reinstall your adb drivers on your machine (if Windows).
Let the device charge for 30 minutes at least then retry (charge with new cable too).

ppppp44 said:
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
Click to expand...
Click to collapse
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.

Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..

Kayembe said:
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Click to expand...
Click to collapse
Hey Kayembe,
I only get to fastboot mode. No Adb device detected. No recovery mode available.

ppppp44 said:
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Click to expand...
Click to collapse
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.

Machiel187 said:
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Click to expand...
Click to collapse
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks

ppppp44 said:
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.

Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
ok I somehow managed to flash Blu_Spark Twrp and got it to work.
Within TWRP, flashed OnePlus3Oxygen_16_OTA_051_all_1704112009_2521.zip
and also SuperSU.zip, and no_verity.zip.
Getting some errors.
Device still doesn't boot.
Attaching the log TXT here.
I am desperate... please help.,..

Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((

ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
try "default_password" for the password

ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
Go to Fastboot type 'fastboot erase userdata' (you have to reflash OOS tho.. Make sure you are on the latest TWRP. I'm not a fan of Bluspark but his TWRP is currently more up 2 date.

Redmi note 8 pro bootloop with no fastboot

Hello,
I was on stable global indian 10.4.4 (INMX), unlocked, rooted, twrp.
Then got notification of update, downloaded update, reboot (as prompted by updater app), update failed, error 7.
Rebooted phone to system. Updater said to download full rom now which i did,, and reboot again, same error.
I thought twrp might b incompatible with update so i flashed stock recovery n repeated all above.
Now phone stuck at bootloop and does not boot into recovery or fastboot by pressing vol+/- and power,, also pressing all three together is not working.
PC doesn't detect phone as it keeps rebooting in loop.
Any way to force boot in fastboot??

beachfl said:
When it very first shuts down (the redmi logo first disappears and it goes black), before it starts to boot up again, press and hold Volume Down and Power until it takes you to fastboot.
Click to expand...
Click to collapse
Cannt go to fastboot bro by this way

majidmjmn said:
I have exactly the same problem with my redmi note 8 pro after trying to flash another twrp on my rooted unlocked phone it juat shows redmi and then goes off,no recovery and no fastboot available!
I don't know about adb shell commands would you Please explain the instructions and procedure in more details
Tnx
Click to expand...
Click to collapse
same problem bro. let me know how you solve this problem please

yeswe61155 said:
Cannt go to fastboot bro by this way
Click to expand...
Click to collapse
If it is bootlooped... you can get to fastboot... keep trying... you just have to catch it at the right time.

Letting the battery run out, then charge and try to start in quick start

danyv77 said:
Letting the battery run out, then charge and try to start in quick start
Click to expand...
Click to collapse
Thank you. Will do that and update.

danyv77 said:
Letting the battery run out, then charge and try to start in quick start
Click to expand...
Click to collapse
Update : didn't work. Still went into same. Tried 4-5 times.

I think you have to open the back cover, disconnect the battery connector, connect it to computer, hopefully it will get detected as mediatek then you can follow this guide

danyv77 said:
Letting the battery run out, then charge and try to start in quick start
Click to expand...
Click to collapse
gugelgigel said:
I think you have to open the back cover, disconnect the battery connector, connect it to computer, hopefully it will get detected as mediatek then you can follow this guide
Click to expand...
Click to collapse
Unfortunately that didn't work either. Sent to Mi Service center, they tried EDL by opening back cover,, didn't work. Now sent phone to xiaomi by service center, i'll get either this one repaired or new one in a week. (as per Mi)
Surprisingly i wasn't the only one or first one to report this. There have been similar incidences earlier as well and even the ones that were on stock everything and locked bootloader. Apparently the new update 11.0.1 is troublesome. - as reported by Mi executive.

Here's my solution
I've got my brand new Redmi Note 8 Pro and just unlocked it yesterday. Today I install the Global ROM and it just work fine BUT I when further : root and install magisk... Then I got a recovery boot loop, I try to solve the issue by flashing another TWRP and then BAM no more fastboot and no more recovery, really bricked hard.
I was using this custom TWRP mention here: https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Please share this solution everywhere because that really solve my issue:
(1) Flash recovery using adb YESSSSS
Source: https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Enable your USB debugging bridge in switch via adb to the terminal:
./adb shell
Then you should be able to find your recovery partion with:
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
that should output something like this:
/dev/block/platform/7824900.sdhci/by-name/recovery
If this is the case you only have to put the recovery.img on your sd-card or the internal storage and you are one command from flashing:
dd of=$DEV if=/external_sd/recovery.img
Thats it! No binaries you have to install. No ****ty fastboot udev rules :S
You can enter into your new recovery system with:
./adb reboot recovery
2) Good now I was able to be back in the LR Team TWRP. From there I removed root and thus magisk, completely disabled DM Verify (because this custom TWRP install everything it can also remove it) and wonder happen, I was able to boot my phone and fastboot is back !

pmesolution.ca said:
I've got my brand new Redmi Note 8 Pro and just unlocked it yesterday. Today I install the Global ROM and it just work fine BUT I when further : root and install magisk... Then I got a recovery boot loop, I try to solve the issue by flashing another TWRP and then BAM no more fastboot and no more recovery, really bricked hard.
I was using this custom TWRP mention here: https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Please share this solution everywhere because that really solve my issue:
(1) Flash recovery using adb YESSSSS
Source: https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Enable your USB debugging bridge in switch via adb to the terminal:
./adb shell
Then you should be able to find your recovery partion with:
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
that should output something like this:
/dev/block/platform/7824900.sdhci/by-name/recovery
If this is the case you only have to put the recovery.img on your sd-card or the internal storage and you are one command from flashing:
dd of=$DEV if=/external_sd/recovery.img
Thats it! No binaries you have to install. No ****ty fastboot udev rules :S
You can enter into your new recovery system with:
./adb reboot recovery
2) Good now I was able to be back in the LR Team TWRP. From there I removed root and thus magisk, completely disabled DM Verify (because this custom TWRP install everything it can also remove it) and wonder happen, I was able to boot my phone and fastboot is back !
Click to expand...
Click to collapse
you should share this information in the other posts, to see if it works for others

djzero86 said:
you should share this information in the other posts, to see if it works for others
Click to expand...
Click to collapse
Yes I did share it to the other post which I followed the tutorial But I think my method will allow anyone having access to adb and not Fastboot to flash and boot a new TWRP image which could allow them to flash once again a ROM from the Recovery or modify the source code an fix their issue.

Redmi note 8 pro no recovery and fastboot
I have exactly the same problem with my redmi note 8 pro after trying to flash another twrp on my rooted unlocked phone it juat shows redmi and then goes off,no recovery and no fastboot available!
I don't know about adb shell commands would you Please explain the instructions and procedure in more details
Tnx

My phone keeps restart
I have the same issiue and my phone keeps restart i can't give any command to solve this proplem please help me

Similar issue,
I get the Redmi splash screen, and then it reboot after about 3 seconds. During the reboot cycle, which takes another few seconds - thats the only time my PC can detect the phone.
So Smart Phone Flash Tool can detect it for those few seconds, starts download but then timeouts after 2 minutes (status protocol err). I guess it loses connection.
Phone can't boot into recovery or fastboot. Is it hardbricked/beyond repair ?
More details:
https://forum.xda-developers.com/showpost.php?p=82467553&postcount=16

poster74 said:
Similar issue,
I get the Redmi splash screen, and then it reboot after about 3 seconds. During the reboot cycle, which takes another few seconds - thats the only time my PC can detect the phone.
So Smart Phone Flash Tool can detect it for those few seconds, starts download but then timeouts after 2 minutes (status protocol err). I guess it loses connection.
Phone can't boot into recovery or fastboot. Is it hardbricked/beyond repair ?
More details:
https://forum.xda-developers.com/showpost.php?p=82467553&postcount=16
Click to expand...
Click to collapse
How you brick your phone?

Flash without autorized account
Does any of you guys use the method that mentined in this site bellow
Just type how to flash redmi note 8 pro without authorized accound in google and clike on link proveded by romprovider..(link was deleted by xda so i coulden't share it)
Use it and let me know if it works for you...

Nasser Nody said:
I have the same issiue and my phone keeps restart i can't give any command to solve this proplem please help me
Click to expand...
Click to collapse
use the method that mentined in this site bellow
and let me know if it works for you...
just type how to flash redmi note 8 pro without authorized accound in google and clike on link proveded by romprovider..(link was deleted by xda so i coulden't share it)

majidmjmn said:
I have exactly the same problem with my redmi note 8 pro after trying to flash another twrp on my rooted unlocked phone it juat shows redmi and then goes off,no recovery and no fastboot available!
I don't know about adb shell commands would you Please explain the instructions and procedure in more details
Tnx
Click to expand...
Click to collapse
Now you all already solved this problem? plz mention me plz plz

yeswe61155 said:
Now you all already solved this problem? plz mention me plz plz
Click to expand...
Click to collapse
When it very first shuts down (the redmi logo first disappears and it goes black), before it starts to boot up again, press and hold Volume Down and Power until it takes you to fastboot.

Backup Files from bricked device?

Hi there,
looks like the latest Update for my OnePlus 9 Pro did bricked my device.
It vibrates repidly at bootup, that stopes when I have the SIM Pin Screen. After I entered the Pins I should get the Finger Print Lock Screen but it just startes to vibrating rapidly again and I get the Line with emergency Call under it to enter the password (no finger print screen). No Keyboard to enter the PW and screen turns black after a while but keeps vibrating rapidly even for hours.
I can hold Power button and restart or shutdown.
So I think it is bricked and I have to try a Factory Reset.
I can enter the recovery menu with VolDown+Power (only reset device and no clear cache option) and the EDL Mode VolUp+VolDown+Power.
Is there any chance to Backup my files in one of that modes?

Haven't you rooted your OnePlus 9 Pro? If not, I think you had better contact a customer service center of OnePlus for help.

Sadly not rooted. The customer service say: factory reset which deletes all the files ...
Any recommendations for an App that restores Files on Android after Factory Reset? One that Restores ALL kind of Files, not only Pictures, Movies and Music.
I hope I could save some of my Chatlogs of Threema (I only have a Backup of the ID, not the Chatlog).

Search&Destroy said:
Sadly not rooted. The customer service say: factory reset which deletes all the files ...
Any recommendations for an App that restores Files on Android after Factory Reset? One that Restores ALL kind of Files, not only Pictures, Movies and Music.
I hope I could save some of my Chatlogs of Threema (I only have a Backup of the ID, not the Chatlog).
Click to expand...
Click to collapse
Normally ADB works in recovery mode, could do a pull command, if firmware is A11 you could temp boot TWRP for some options...
Just a thought.

I cant find any device in recovery or fastboot mode.
I also tested my OnePlus 6.
The OP6 will be found via ADB, when I boot it up to Android.
But not sure if there is a special Driver needed for ADB in recovery or fastboot mode.

Search&Destroy said:
I cant find any device in recovery or fastboot mode.
I also tested my OnePlus 6.
The OP6 will be found via ADB, when I boot it up to Android.
But not sure if there is a special Driver needed for ADB in recovery or fastboot mode.
Click to expand...
Click to collapse
Did you install the latest OP USB drivers?

Do you have a Google account? And we're you signed in?

TheGhost1951 said:
Did you install the latest OP USB drivers?
Click to expand...
Click to collapse
No, where can i get them?
TheGhost1951 said:
Do you have a Google account? And we're you signed in?
Click to expand...
Click to collapse
Yes I have and the Device is/was logged in.

Search&Destroy said:
No, where can i get them?
Yes I have and the Device is/was logged in.
Click to expand...
Click to collapse
Then you should be able to MSM back to stock and during setup log back in to Google and it will restore all apps with data..... But before doing that try from fast boot fastboot boot twrp, connect USB flash drive and while in twrp use TWRP file explorer to copy from SD card to USB flash drive for documents and photos... If SD card is not available in twrp, the only recovery option you have is apps and app data from Google restore

But I cant install TWRP as long as I cant find the device via ADB right?
Because I cant find the OnePlus 9 Pro, I can only find my older OnePlus 6.
And in Recovery Menu (v1.2) there are only 3 Options: Wipe data (no wipe cache option), Reboot and power off.
Have the latest Stock Android available for the OP9Pro installed

Search&Destroy said:
But I cant install TWRP as long as I cant find the device via ADB right?
Because I cant find the OnePlus 9 Pro, I can only find my older OnePlus 6.
Click to expand...
Click to collapse
Can you get to fastboot? Then if so, in CMD window type fastboot devices and see if you phone sends back the serial number

Ahh here it is.
The PowerShell shows me the same Serial number as my OP9Pro shows me in FastBoot Mode (still nothing with adb devices listed)

Well I downloaded TWRP and did try to send it via 'fastboot boot twrp.img' but its not possible, because my device is locked.
All I get is:
FAILED (remote: 'boot is not allowed in Lock State')

Your best bet would be to boot into TWRP if you are running Android 11

Search&Destroy said:
Ahh here it is.
The PowerShell shows me the same Serial number as my OP9Pro shows me in FastBoot Mode (still nothing with adb devices listed)
Click to expand...
Click to collapse
You are not booted up to home screen to be seen by ADB normally...in fastboot mode if you have TWRP downloaded, try fastboot boot name_of_twrp_img.img and see if TWRP boots up. Cd to directory where TWRP image is located.

twrp can only boot when the bootloader is unlocked , with locked bootloader you cant boot twrp
and the stock recovery have no adb enabled

ChrisFeiveel84 said:
twrp can only boot when the bootloader is unlocked , with locked bootloader you cant boot twrp
and the stock recovery have no adb enabled
Click to expand...
Click to collapse
My mistake...

Search&Destroy said:
Well I downloaded TWRP and did try to send it via 'fastboot boot twrp.img' but its not possible, because my device is locked.
All I get is:
FAILED (remote: 'boot is not allowed in Lock State'what firmware were you on before this happened? Glo, EU or which?
Click to expand...
Click to collapse

What Firmware were you on?

Search&Destroy said:
Well I downloaded TWRP and did try to send it via 'fastboot boot twrp.img' but its not possible, because my device is locked.
All I get is:
FAILED (remote: 'boot is not allowed in Lock State')
Click to expand...
Click to collapse
I believe you only have two options left. Try to flash all the firmware images while in fastboot. If that can't be done, only thing left is to use the MSM tool which I know will wipe everything. But when you go to setup you phone, logging into your Google account, Google will restore apps and apps data....but you will lose the data on internal storage. Sorry that I can't be more help.

Question BootLoop not letting me access fastboot

Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit.
Vol down + power buttons does not work. Neither does volum up + power. But when I press vol up+vol down+power my PC emits sound of connected device. I think that it is a problem of A/B partition, but I need to get to fastboot to fix it.
Any solution? I have already tried battery running out.

marcos_rgn said:
... my PC emits sound of connected device.
Click to expand...
Click to collapse
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.

.

Renate said:
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.
Click to expand...
Click to collapse
This is with usblog.exe.
I have checked and adb devices and fastboot devices are empty even while device is connected (in that 3 seconds window). I have runned some commands with "wait-for-device" and they didnt work.

So you have the MediaTek ROM bootloader there.
I've played with some of the MediaTek stuff (and even started to write a native Windows MTK client), but I'm no expert.
There are two modes, 0e8d/0003 (ROM) and 0e8d/2000 (preloader).
You might look here: https://github.com/bkerler/mtkclient
Try holding the VolUp while rebooting to try to get 2000.

I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.

you can flash with this spflash tool to take back your phone.
SP Flash Tool v5.2044 Edited By Kurdish Gsm Team (Free Downlowd)
SP Flash Tool v5.2044 Modefiad Version With Auth Bypass Button
www.firmware4mobile.com
here is the video tutorial

Renate said:
I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.
Click to expand...
Click to collapse
I have stopped boot loop by flashing boot.img and vbmeta.img with MTK client, thank you!
Generally speaking, if I want to return to default ROM, what files should I flash? What are the "software pieces" that Magisk touches and modify?

marcos_rgn said:
What are the "software pieces" that Magisk touches and modify?
Click to expand...
Click to collapse
Normally, Magisk only needs to have the boot image replaced.
The instructions tell you to optionally make the vbmeta inactive, but Magisk ignores all that verification anyway.